Terminal, base station, and communication method
The system dynamically switches between DFT-s-OFDM and CP-OFDM for PUSCH transmission based on specific conditions to enhance uplink signal efficiency and coverage in 5G systems, addressing the challenges of high-frequency band propagation losses and channel fluctuations.
Patent Information
- Application Number
- PCT/JP2023/017671
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-11
- Publication Date
- 2024-11-14
AI Technical Summary
Current 5G mobile communication systems face challenges in efficiently managing uplink signal transmission, particularly in high-frequency bands where radio wave propagation loss is significant, leading to deteriorated reception quality and limited coverage, especially for cell-edge terminals with instantaneous channel fluctuations.
A terminal and base station system that dynamically switches the PUSCH transmission waveform between DFT-s-OFDM and CP-OFDM based on specific conditions such as repetition, number of transmission layers, frequency domain resource allocation, and DMRS settings, without adding a transmission waveform notification field to the DCI, to enhance coverage and transmission efficiency.
This approach allows for improved uplink signal transmission efficiency and coverage by dynamically adapting the transmission waveform to environmental conditions, ensuring high-quality communication even in low SINR environments without increasing DCI overhead.
Smart Images

Figure JP2023017671_14112024_PF_FP_ABST
Abstract
Description
Terminal, base station and communication method
[0001] The present disclosure relates to a terminal, a base station, and a communication method.
[0002] In recent years, the expansion and diversification of wireless services has led to the expectation of rapid development of the Internet of Things (IoT). Mobile communications are now being used in a wide range of applications, from smartphones and other information terminals to automobiles, homes, home appliances, and industrial equipment. To support this diversification, significant improvements in the performance and functionality of mobile communication systems are required, addressing various requirements, such as increased system capacity, an increased number of connected devices, and low latency. Fifth-generation mobile communication systems (5G) boast high-capacity and ultra-high-speed data transfer (eMBB: enhanced Mobile Broadband), massive machine-type communication (mMTC: massive Machine-Type Communication), and ultra-reliable and low-latency communication (URLLC), providing flexible wireless communications to meet diverse needs.
[0003] The 3rd Generation Partnership Project (3GPP), an international standardization organization, is working on the specification of New Radio (NR) as one of the 5G wireless interfaces.
[0004] 3GPP TS38.104 V15.18.0, “NR Base Station (BS) radio transmission and reception (Release 15),” September 2022.RP-202928, “New WID on NR coverage enhancements,” China Telecom, December 2020.RP-220937, “Revised WID on Further NR coverage enhancements,” China Telecom, March 2022.3GPP TS38.211 V17.4.0, “NR Physical channels and modulation (Release 17),” December 2022.3GPP TS38.212 V17.5.0, “NR Multiplexing and channel coding (Release 17),” March 2023.3GPP TS38.213 V17.5.0, “NR Physical layer procedures for control (Release 17),” March 2023.3GPP TS38.214 V17.5.0, “NR Physical layer procedures for data (Release 17),” March 2023.
[0005] However, there is room for further consideration regarding the method of transmitting signals in the uplink.
[0006] Non-limiting examples of the present disclosure contribute to providing a terminal, a base station, and a communication method that can appropriately transmit signals in the uplink.
[0007] A terminal according to one embodiment of the present disclosure includes a control circuit that switches the transmission waveform of an uplink signal to a first transmission waveform when conditions related to parameters and settings for transmitting the uplink signal are met, and a transmission circuit that transmits the uplink signal using the first transmission waveform.
[0008] These comprehensive or specific aspects may be realized as a system, an apparatus, a method, an integrated circuit, a computer program, or a recording medium, or may be realized as any combination of a system, an apparatus, a method, an integrated circuit, a computer program, and a recording medium.
[0009] According to one embodiment of the present disclosure, signals can be transmitted appropriately in the uplink.
[0010] Further advantages and benefits of one embodiment of the present disclosure will become apparent from the specification and drawings. Such advantages and / or benefits may be provided by some embodiments and features described in the specification and drawings, respectively, but not necessarily all of them may be provided to obtain one or more identical features.
[0011] 1. A diagram showing an example of a method for determining a transmission waveform for a Physical Uplink Shared Channel (PUSCH). 2. A block diagram showing an example configuration of a portion of a base station. 3. A block diagram showing an example configuration of a portion of a terminal. 4. A flowchart showing an example operation of a terminal. 5. A flowchart showing an example operation of a terminal. 6. A block diagram showing an example configuration of a base station. 7. A block diagram showing an example configuration of a terminal. 8. A diagram of an example architecture of a 3GPP NR system. 9. A schematic diagram showing functional separation between NG-RAN and 5GC. 10. A sequence diagram of the RRC (Radio Resource Control) connection setup / reconfiguration procedure. 11. A schematic diagram showing usage scenarios for enhanced Mobile BroadBand (eMBB), massive Machine Type Communications (mMTC), and Ultra Reliable and Low Latency Communications (URLLC). 12. A block diagram showing an example 5G system architecture for a non-roaming scenario.
[0012] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings.
[0013] In NR, for example, in addition to frequency bands below 6 GHz, such as the 700 MHz to 3.5 GHz band (also referred to as Frequency Range 1 (FR1)), which have been used for cellular communications, millimeter wave bands such as the 28 GHz or 39 GHz band (also referred to as Frequency Range 2 (FR2)), which can ensure wide bandwidth, can be utilized (see, for example, Non-Patent Document 1). Furthermore, for example, in FR1, there is a possibility that a frequency band such as the 3.5 GHz band, which is higher than the frequency bands used in Long Term Evolution (LTE) or 3G (3rd Generation mobile communication systems), will be used.
[0014] The higher the frequency band, the greater the radio wave propagation loss and the more likely it is that radio wave reception quality will deteriorate. Therefore, when NR uses a frequency band higher than that of LTE or 3G, it is expected to ensure a communication area (or coverage) equivalent to that of radio access technologies (RATs) such as LTE or 3G, in other words, to ensure appropriate communication quality. For example, 3GPP Release 17 (e.g., referred to as "Rel. 17") and Release 18 (e.g., referred to as "Rel. 18") have considered methods for improving coverage in NR (see, for example, Non-Patent Document 2 and Non-Patent Document 3).
[0015] In NR, a terminal (e.g., also referred to as user equipment (UE)) transmits and receives data in accordance with, for example, a layer 1 control signal (e.g., DCI: Downlink Control Information) on a downlink control channel (e.g., PDCCH: Physical Downlink Control Channel) from a base station (e.g., also referred to as gNB) or a resource allocation indicated by layer 3 Radio Resource Control (RRC) (see, for example, Non-Patent Documents 4 to 7).
[0016] In the uplink (UL), for example, a terminal transmits an uplink data channel (for example, a Physical Uplink Shared Channel (PUSCH)) in accordance with resource allocation (for example, a Grant or UL grant) from a base station.
[0017] NR supports Discrete Fourier Transform-spread-Orthogonal Frequency Division Multiplexing (DFT-s-OFDM) and Cyclic Prefix-OFDM (CP-OFDM) as PUSCH transmission waveforms.
[0018] Compared with CP-OFDM, DFT-s-OFDM has a lower peak-to-average power ratio (PAPR) of the transmitted signal and higher power utilization efficiency, making it a transmission waveform that can ensure wide uplink coverage. CP-OFDM also has high compatibility with Multiple-Input Multiple-Output (MIMO), making it an effective transmission waveform for high-efficiency transmission (e.g., multi-rank or multi-layer transmission in spatial multiplexing transmission) in a high-reception quality (e.g., signal-to-interference and noise power ratio (SINR)) environment.
[0019] In NR up to Rel. 17, the PUSCH transmission waveform is set semi-statically by RRC. Figure 1 shows an example of a method for determining the PUSCH transmission waveform in NR up to Rel. 17.
[0020] For example, the transmission waveform of Message 3 (Msg.3) PUSCH in the 4-step random access procedure is determined based on the parameter "msg3-transformPrecoder" set by RRC.
[0021] Also, for example, the transmission waveform of Message A (Msg.A) PUSCH in the 2-step random access procedure is determined based on the parameter "msgA-transformPrecoder" set by RRC. Note that if msgA-transformPrecoder is not set by RRC, the transmission waveform of Msg.A PUSCH may be determined based on msg3-transformPrecoder.
[0022] Furthermore, for example, the transmission waveform of a PUSCH (for example, DG-PUSCH: Dynamic Grant-PUSCH) that is dynamically scheduled by DCI format 0-0 is determined based on the parameter "msg3-transformPrecoder" set by RRC.
[0023] Furthermore, for example, the transmission waveform of a PUSCH (for example, DG-PUSCH) dynamically scheduled by DCI format 0-1 or DCI format 0-2 is determined based on a parameter "transformPrecoder" included in a pusch-Config information element (IE) configured by RRC. Note that if transformPrecoder is not configured by RRC, the transmission waveform of a PUSCH dynamically scheduled by DCI format 0-1 or DCI format 0-2 may be determined based on msg3-transformPrecoder.
[0024] Furthermore, for example, the transmission waveform of a PUSCH (for example, Configured grant-PUSCH (CG-PUSCH)) transmitted based on resource allocation instructed by RRC, which is layer 3, or semi-static resource allocation by Activation DCI, is determined based on a parameter "transformPrecoder" included in configuredGrantConfig IE, which is configured by RRC. Note that when transformPrecoder is not configured by RRC, the transmission waveform of the CG-PUSCH may be determined based on msg3-transformPrecoder.
[0025] In addition, in NR up to Release 17, the number of transmission layers for PUSCH transmission using DFT-s-OFDM is set to (or limited to) one.
[0026] In a typical cellular system, it is expected that DFT-s-OFDM will be configured to ensure coverage for terminals at the cell edge, where improved uplink coverage is expected.
[0027] However, even in a cell edge terminal, there may be a situation where a high reception quality (e.g., SINR) is ensured to transmit a PUSCH due to instantaneous fluctuations in a channel or an interference environment. In such a case, if the transmission waveform is set quasi-statically (e.g., when there are constraints on the setting), it is difficult for a cell edge terminal with the transmission waveform set to DFT-s-OFDM to switch the transmission waveform to CP-OFDM in accordance with instantaneous fluctuations in the channel or interference environment and perform highly efficient transmission (e.g., multiple layer transmission using MIMO spatial multiplexing), and it may not be possible to improve the transmission efficiency of the cell edge terminal.
[0028] On the other hand, for example, if the transmit waveform is set to CP-OFDM by transformPrecoder or msg3-transformPrecoder with priority given to improving transmission efficiency, the uplink coverage performance may be degraded in terminals in low SINR environments, such as cell edge terminals.
[0029] For example, one method for dynamically switching the transmission waveform of the PUSCH is to add a field (transmission waveform notification field) for notifying the transmission waveform to the DCI. However, introducing the transmission waveform notification field into the DCI increases the number of DCI bits.
[0030] For example, in the case of a PUSCH scheduled by DCI format 0-0, it is desirable to be able to use DCI format 0-0 regardless of RRC reconfiguration. Furthermore, changing the DCI size of DCI format 0-0 is undesirable in order to maintain the same DCI payload size in a common search space between terminals of different releases. Therefore, for a PUSCH scheduled by DCI format 0-0, the method of dynamically switching the transmission waveform by adding a transmission waveform notification field to the DCI is not suitable.
[0031] Furthermore, DCI formats 0-2 are DCIs designed for URLLC, and it is desirable to improve the reliability of DCI reception by reducing the number of DCI bits as much as possible. Therefore, for PUSCHs scheduled using DCI formats 0-2, the method of dynamically switching the transmission waveform by adding a transmission waveform notification field to the DCI is not suitable.
[0032] In one non-limiting embodiment of the present disclosure, a method for dynamically switching the transmission waveform of a PUSCH without adding a transmission waveform notification field to a DCI will be described.
[0033] In a non-limiting embodiment of the present disclosure, a terminal switches the transmission waveform to DFT-s-OFDM under conditions related to PUSCH transmission parameters or settings, and transmits a PUSCH. For example, information related to PUSCH transmission parameters or settings used as a condition for switching the transmission waveform may include at least one of information on PUSCH repetition transmission (Repetition), information on the number of transmission layers, information on frequency domain resource allocation, and information on DMRS (DeModulation Reference Signal) settings. This allows for improved spectral efficiency or transmission efficiency to be achieved using CP-OFDM, while ensuring coverage using DFT-s-OFDM in a cell edge or low SINR environment where operational efficiency or coverage performance is degraded using CP-OFDM. Furthermore, operation is possible in which coverage is ensured by dynamically configuring DFT-s-OFDM without adding a transmission waveform notification field to DCI.
[0034] Non-limiting embodiments of the present disclosure will be described below.
[0035] [Overview of Communication System] A communication system according to each embodiment of the present disclosure includes, for example, at least one base station and at least one terminal.
[0036] FIG. 2 is a block diagram showing a configuration example of a portion of a base station 100 according to an embodiment of the present disclosure, and FIG. 3 is a block diagram showing a configuration example of a portion of a terminal 200 according to an embodiment of the present disclosure.
[0037] In the base station 100 shown in Fig. 2, a control unit (e.g., corresponding to a control circuit) switches the transmission waveform of an uplink signal (e.g., PUSCH) to a first transmission waveform (e.g., DFT-s-OFDM) when conditions related to transmission parameters and settings of the uplink signal are satisfied. A receiving unit (e.g., corresponding to a receiving circuit) receives the uplink signal using the first transmission waveform.
[0038] In terminal 200 shown in Fig. 3, a control unit (e.g., corresponding to a control circuit) switches the transmission waveform of an uplink signal (e.g., PUSCH) to a first transmission waveform (e.g., DFT-s-OFDM) when conditions related to parameters and settings for transmission of the uplink signal are satisfied. A transmission unit (e.g., a transmission circuit) transmits the uplink signal using the first transmission waveform.
[0039] (Embodiment 1) Base station 100 (e.g., base station / network) semi-statically sets a transmission waveform for terminal 200 using transformPrecoder or msg3-transformPrecoder, which are higher layer parameters, similar to NR up to Rel. 17. For example, terminal 200 can be configured with a semi-static transmission waveform for CP-OFDM using transformPrecoder or msg3-transformPrecoder.
[0040] In this embodiment, terminal 200 switches the transmission waveform to DFT-s-OFDM and transmits PUSCH based on one or more of the following conditions:
[0041] <Condition 1: Presence or Absence of Repetition, or Number of Repetitions> Terminal 200 may determine to switch the transmission waveform of the PUSCH to DFT-s-OFDM, for example, based on the presence or absence of repetition in PUSCH transmission. For example, when repetition is applied to PUSCH transmission, terminal 200 switches the transmission waveform to DFT-s-OFDM and transmits the PUSCH. On the other hand, when repetition is not applied to PUSCH transmission, terminal 200 transmits the PUSCH by applying a transmission waveform (for example, CP-OFDM) that is semi-statically set by transformPrecoder or msg3-transformPrecoder.
[0042] Furthermore, terminal 200 may determine to switch the transmission waveform of PUSCH to DFT-s-OFDM based on, for example, the number of repetitions of PUSCH. For example, if the number of repetitions is N or more (or greater than N), terminal 200 switches the transmission waveform to DFT-s-OFDM and transmits PUSCH. On the other hand, if the number of repetitions is less than N (or equal to or less than N), terminal 200 transmits PUSCH by applying a transmission waveform (for example, CP-OFDM) that is quasi-statically set by transformPrecoder or msg3-transformPrecoder.
[0043] Here, the value of threshold N may be given in advance according to the standard, or may be set (or notified) to terminal 200 by RRC or other signaling.
[0044] <Condition 2: Number of Transmission Layers> Terminal 200 may determine whether to switch the transmission waveform of the PUSCH to DFT-s-OFDM, for example, based on the number of transmission layers (or the number of ranks) in PUSCH transmission.
[0045] As described above, in existing NR, DFT-s-OFDM supports one-layer transmission. In this case, for example, when PUSCH transmission is one-layer transmission, terminal 200 switches the transmission waveform to DFT-s-OFDM and transmits the PUSCH. On the other hand, when PUSCH transmission is multi-layer transmission, terminal 200 transmits the PUSCH by applying a transmission waveform (e.g., CP-OFDM) quasi-statically set by transformPrecoder or msg3-transformPrecoder.
[0046] Furthermore, for example, when DFT-s-OFDM supports multi-layer transmission, terminal 200 may switch the transmission waveform to DFT-s-OFDM based on the number of transmission layers, which is one or more. For example, when the number of transmission layers is equal to or less than N (or is smaller than N), terminal 200 switches the transmission waveform to DFT-s-OFDM and transmits the PUSCH. On the other hand, when the number of transmission layers is greater than N (or is equal to or greater than N), terminal 200 transmits the PUSCH by applying a transmission waveform (for example, CP-OFDM) that is semi-statically set by transformPrecoder or msg3-transformPrecoder.
[0047] Here, the value of threshold N may be given in advance according to the standard, or may be set (or notified) to terminal 200 by RRC or other signaling.
[0048] <Condition 3: Frequency Domain Resource Allocation Type, Number of Frequency Domain Allocated Resource Blocks (RBs), or Number of Cluster Resource Blocks> Terminal 200 may determine to switch the transmission waveform of the PUSCH to DFT-s-OFDM, for example, based on resource allocation in PUSCH transmission (e.g., frequency resource allocation).
[0049] Terminal 200 may determine switching of the transmission waveform of the PUSCH based on, for example, the frequency resource allocation type of the PUSCH transmission. For example, when the frequency resource allocation type of the PUSCH transmission is Type 1 (e.g., contiguous RB allocation or allocation in which the starting RB and the number of RBs are notified), terminal 200 switches the transmission waveform to DFT-s-OFDM and transmits the PUSCH. On the other hand, when PUSCH transmission is Type 0 (e.g., non-contiguous RB allocation or bitmap allocation using RB / RBG (RB group)), terminal 200 transmits the PUSCH by applying a transmission waveform (e.g., CP-OFDM) semi-statically set by transformPrecoder or msg3-transformPrecoder.
[0050] Furthermore, terminal 200 may determine switching of the transmission waveform of the PUSCH based on, for example, the number of allocated RBs in frequency domain resource allocation for PUSCH transmission. For example, when the number of allocated RBs is equal to or less than N (or is less than N), terminal 200 switches the transmission waveform to DFT-s-OFDM and transmits the PUSCH. On the other hand, when the number of allocated RBs is greater than N (or is equal to or greater than N), terminal 200 transmits the PUSCH by applying a transmission waveform (for example, CP-OFDM) that is semi-statically set by transformPrecoder or msg3-transformPrecoder.
[0051] Here, the value of threshold N may be given in advance according to the standard, or may be set (or notified) to terminal 200 by RRC or other signaling.
[0052] Furthermore, for example, when DFT-s-OFDM supports Clustered DFT-s-OFDM, which can allocate multiple clusters consisting of consecutive RBs, terminal 200 may determine whether to switch the transmission waveform of the PUSCH based on, for example, the number of RBs that make up the cluster.
[0053] For example, when the number of RBs constituting a cluster is equal to or less than N (or is less than N), terminal 200 switches the transmission waveform to DFT-s-OFDM and transmits the PUSCH. On the other hand, when the number of RBs constituting a cluster is greater than N (or is equal to or greater than N), terminal 200 transmits the PUSCH by applying a transmission waveform (for example, CP-OFDM) that is semi-statically set by transformPrecoder or msg3-transformPrecoder.
[0054] Here, the value of the threshold N may be predetermined in accordance with the standard, or may be set (or notified) by RRC or other signaling.
[0055] The cluster used to determine whether to switch the transmission waveform may be the cluster with the largest number of RBs, or the cluster with the smallest number of RBs, or may be a cluster with a specific index.
[0056] Furthermore, for example, when DFT-s-OFDM supports Clustered DFT-s-OFDM, which is capable of allocating multiple clusters each consisting of consecutive RBs, terminal 200 may determine whether to switch the transmission waveform of the PUSCH based on, for example, the number of clusters.
[0057] For example, when the number of clusters is equal to or less than N (or less than N), terminal 200 switches the transmission waveform to DFT-s-OFDM and transmits the PUSCH. On the other hand, when the number of clusters is greater than N (or greater than or equal to N), terminal 200 transmits the PUSCH by applying a transmission waveform (for example, CP-OFDM) that is semi-statically set by transformPrecoder or msg3-transformPrecoder.
[0058] Here, the value of the threshold N may be predetermined in accordance with the standard, or may be set (or notified) by RRC or other signaling.
[0059] <Condition 4: DMRS Type or Number of Additional DMRS Symbols> Terminal 200 may determine to switch the transmission waveform of the PUSCH to DFT-s-OFDM, for example, based on the DMRS configuration for PUSCH transmission.
[0060] Terminal 200 may determine switching of the PUSCH transmission waveform based on, for example, the DMRS type in PUSCH transmission. For example, in existing NR, DFT-s-OFDM supports DMRS type=Type 1 but does not support DMRS type=Type 2. In this case, for example, when the DMRS type of PUSCH transmission is Type 1, terminal 200 switches the transmission waveform to DFT-s-OFDM and transmits the PUSCH. On the other hand, when the DMRS type of PUSCH transmission is Type 2, terminal 200 transmits the PUSCH by applying a transmission waveform (for example, CP-OFDM) semi-statically set by transformPrecoder or msg3-transformPrecoder.
[0061] Note that the DMRS type supported by DFT-s-OFDM is not limited to Type 1 and may support other types. Also, the DMRS type is not limited to Type 1 and Type 2 and may include other types.
[0062] Furthermore, terminal 200 may determine switching of the transmission waveform of the PUSCH based on, for example, the number of additional DMRS symbols in the DMRS configuration of PUSCH transmission. For example, if the number of additional DMRS symbols is N or more (or greater than N), terminal 200 switches the transmission waveform to DFT-s-OFDM and transmits the PUSCH. On the other hand, if the number of additional DMRS symbols is less than N (or equal to or less than N), terminal 200 transmits the PUSCH by applying a transmission waveform (for example, CP-OFDM) semi-statically configured by transformPrecoder or msg3-transformPrecoder.
[0063] Here, the value of the threshold N may be predetermined in accordance with the standard, or may be set (or notified) by RRC or other signaling.
[0064] The conditions for switching the transmission waveform have been explained above.
[0065] Terminal 200 may switch the transmission waveform of the PUSCH to DFT-s-OFDM based on, for example, any one of the four conditions described above. For example, terminal 200 may switch the transmission waveform of the PUSCH to DFT-s-OFDM based on condition 1.
[0066] Alternatively, terminal 200 may switch the transmission waveform of the PUSCH to DFT-s-OFDM based on, for example, two or more of the four conditions described above.
[0067] When multiple conditions are used, for example, when any one of the multiple conditions satisfies the condition for switching the transmission waveform to DFT-s-OFDM, terminal 200 may switch the transmission waveform to DFT-s-OFDM. For example, when all of the multiple conditions do not satisfy the condition for switching the transmission waveform to DFT-s-OFDM, terminal 200 may transmit the PUSCH by applying a transmission waveform (for example, CP-OFDM) that is semi-statically set by transformPrecoder or msg3-transformPrecoder.
[0068] Furthermore, for example, when the conditions for switching the transmission waveform to DFT-s-OFDM are satisfied under all of a plurality of conditions, terminal 200 may switch the transmission waveform to DFT-s-OFDM. For example, when any one of a plurality of conditions does not satisfy the condition for switching the transmission waveform to DFT-s-OFDM, terminal 200 may transmit the PUSCH by applying a transmission waveform (for example, CP-OFDM) that is semi-statically set by transformPrecoder or msg3-transformPrecoder.
[0069] Furthermore, for example, when M (or M or more) conditions among a plurality of conditions satisfy the condition for switching the transmission waveform to DFT-s-OFDM, terminal 200 may switch the transmission waveform to DFT-s-OFDM. Here, the value of M may be given in advance according to the standard, or may be configured (or notified) to terminal 200 by RRC or other signal.
[0070] Furthermore, for example, the terminal 200 may be configured (or notified) by RRC or other signal as to which (one or more) of the four conditions described above to use to switch the transmission waveform to DFT-s-OFDM (e.g., information regarding the conditions to be applied).
[0071] Here, the above-described condition for switching the transmission waveform to DFT-s-OFDM is generally a PUSCH transmission parameter or setting that can be applied to PUSCH transmission in a low SINR environment. When such a condition is satisfied, it is useful for terminal 200 to apply DFT-s-OFDM to transmit the PUSCH, thereby improving coverage and transmission characteristics.
[0072] Furthermore, in the present embodiment, for example, information related to a parameter or setting of PUSCH transmission (for example, information related to at least one of PUSCH repetition, the number of transmission layers, frequency domain resource allocation, and DMRS setting) may be reported to terminal 200 by dynamic signaling such as DCI. This makes it possible to dynamically switch the transmission waveform without the overhead of adding a transmission waveform notification field to DCI in an environment where improvements in coverage and transmission characteristics are expected.
[0073] [Example of Operation of Terminal 200] FIG. 4 is a flowchart showing an example of operation of terminal 200.
[0074] In FIG. 4, terminal 200 acquires at least one upper layer parameter such as transformPrecoder and msg3-transformPrecoder (S101).
[0075] Terminal 200 acquires information on conditions for switching the transmission waveform of the PUSCH to DFT-s-OFDM (S102). The information on conditions for switching the transmission waveform of the PUSCH to DFT-s-OFDM may include, for example, information on an applicable condition among the above-mentioned four conditions, and may include information on parameters and settings (for example, Repetition, number of layers, RB setting, DMRS setting, or threshold value) used in the above-mentioned four conditions.
[0076] The terminal 200 determines whether or not a condition for switching the PUSCH transmission waveform to DFT-s-OFDM is met (S103).
[0077] If the condition for switching the PUSCH transmission waveform to DFT-s-OFDM is met (S103: Yes), terminal 200 sets (or switches) the PUSCH transmission waveform to DFT-s-OFDM and transmits the PUSCH (S104).
[0078] On the other hand, if the condition for switching the PUSCH transmission waveform to DFT-s-OFDM is not met (S103: No), terminal 200 transmits PUSCH by applying a transmission waveform (for example, CP-OFDM) set by at least one of transformPrecoder and msg3-transformPrecoder (S105).
[0079] As described above, in the present embodiment, terminal 200 switches the PUSCH transmission waveform to DFT-s-OFDM when conditions related to PUSCH transmission parameters and settings are satisfied, and transmits the PUSCH using DFT-s-OFDM. For example, when the PUSCH transmission waveform is set to CP-OFDM by higher layer parameters (e.g., transformPrecoder or msg3-transformPrecoder), terminal 200 determines to switch to DFT-s-OFDM based on the conditions.
[0080] This allows terminal 200 to dynamically switch the transmission waveform of the PUSCH in accordance with, for example, instantaneous fluctuations in the channel or interference environment, without adding a transmission waveform notification field to the DCI. Thus, according to this embodiment, terminal 200 can appropriately transmit signals in the uplink.
[0081] (Variation 1) As described above, in NR, the transmission waveform of a PUSCH (DG-PUSCH) that is dynamically scheduled by DCI format 0-0 is determined based on msg3-transformPrecoder, which is a parameter set by RRC.
[0082] Furthermore, the transmission waveform of a PUSCH (DG-PUSCH) dynamically scheduled by DCI format 0-1 or DCI format 0-2 is determined based on transformPrecoder, which is a parameter included in the pusch-Config IE configured by RRC. Furthermore, if transformPrecoder is not configured by RRC, the transmission waveform of a PUSCH dynamically scheduled by DCI format 0-1 or DCI format 0-2 is determined based on msg3-transformPrecoder.
[0083] Furthermore, the transmission waveform of a PUSCH (CG-PUSCH) that transmits a PUSCH by resource allocation instructed by RRC, which is layer 3, or semi-static resource allocation by Activation DCI is determined based on transformPrecoder, which is a parameter included in configuredGrantConfig IE set by RRC. Furthermore, if transformPrecoder is not set by RRC, the transmission waveform of the CG-PUSCH is determined based on msg3-transformPrecoder.
[0084] In the first modification, for example, the method of the first embodiment described above may be applied to determining the default transmission waveform.
[0085] Here, determining a default transmission waveform refers to a case where a transmission waveform is determined based on msg3-transformPrecoder. For example, determining a default transmission waveform may be at least one of determining a transmission waveform of a PUSCH (DG-PUSCH) dynamically scheduled by DCI format 0-0, determining a transmission waveform of a PUSCH dynamically scheduled by DCI format 0-1 or DCI format 0-2 when transformPrecoder is not configured by RRC, and determining a transmission waveform of a CG-PUSCH when transformPrecoder is not configured by RRC.
[0086] The base station 100 (e.g., a base station / network) semi-statically sets the transmission waveform for the terminal 200 using the upper layer parameter transformPrecoder or msg3-transformPrecoder, for example, similar to NR up to Rel. 17.
[0087] For example, terminal 200 can set, to CP-OFDM, a quasi-static transmission waveform for at least one of a PUSCH dynamically scheduled by DCI format 0-0, a PUSCH dynamically scheduled by DCI format 0-1 or DCI format 0-2 when transformPrecoder is not configured by RRC, and a CG-PUSCH when transformPrecoder is not configured by RRC.
[0088] In Modification 1, when determining a default transmission waveform (for example, when msg3-transformPrecoder is set and transformPrecoder is not set), terminal 200 may determine to switch the transmission waveform of PUSCH to DFT-s-OFDM based on the conditions described in Embodiment 1. On the other hand, when determining a transmission waveform different from the default transmission waveform (for example, when msg3-transformPrecoder and transformPrecoder are set), terminal 200 may determine the transmission waveform based on transformPrecoder.
[0089] For example, terminal 200 may switch the transmission waveform of at least one of the PUSCH dynamically scheduled by DCI format 0-0, the PUSCH dynamically scheduled by DCI format 0-1 or DCI format 0-2 when transformPrecoder is not configured by RRC, and the CG-PUSCH when transformPrecoder is not configured by RRC to DFT-s-OFDM and transmit the PUSCH based on any one or more of the following conditions:
[0090] <Condition 1: Presence or Absence of Repetition, or Number of Repetitions> Terminal 200 may determine to switch the transmission waveform of the PUSCH to DFT-s-OFDM, for example, based on the presence or absence of repetition in PUSCH transmission. For example, when repetition is applied to PUSCH transmission, terminal 200 switches the transmission waveform to DFT-s-OFDM and transmits the PUSCH. On the other hand, when repetition is not applied to PUSCH transmission, terminal 200 transmits the PUSCH by applying a transmission waveform (for example, CP-OFDM) that is semi-statically set by transformPrecoder or msg3-transformPrecoder.
[0091] Furthermore, terminal 200 may determine to switch the transmission waveform of PUSCH to DFT-s-OFDM based on, for example, the number of repetitions of PUSCH. For example, if the number of repetitions is N or more (or greater than N), terminal 200 switches the transmission waveform to DFT-s-OFDM and transmits PUSCH. On the other hand, if the number of repetitions is less than N (or equal to or less than N), terminal 200 transmits PUSCH by applying a transmission waveform (for example, CP-OFDM) that is quasi-statically set by transformPrecoder or msg3-transformPrecoder.
[0092] Here, the value of threshold N may be given in advance according to the standard, or may be set (or notified) to terminal 200 by RRC or other signaling.
[0093] <Condition 2: Number of Transmission Layers> Terminal 200 may determine whether to switch the transmission waveform of the PUSCH to DFT-s-OFDM, for example, based on the number of transmission layers (or the number of ranks) in PUSCH transmission.
[0094] As described above, in existing NR, DFT-s-OFDM supports one-layer transmission. In this case, for example, when PUSCH transmission is one-layer transmission, terminal 200 switches the transmission waveform to DFT-s-OFDM and transmits the PUSCH. On the other hand, when PUSCH transmission is multi-layer transmission, terminal 200 transmits the PUSCH by applying a transmission waveform (e.g., CP-OFDM) quasi-statically set by transformPrecoder or msg3-transformPrecoder.
[0095] Furthermore, for example, when DFT-s-OFDM supports multi-layer transmission, terminal 200 may switch the transmission waveform to DFT-s-OFDM based on the number of transmission layers, which is one or more. For example, when the number of transmission layers is equal to or less than N (or is smaller than N), terminal 200 switches the transmission waveform to DFT-s-OFDM and transmits the PUSCH. On the other hand, when the number of transmission layers is greater than N (or is equal to or greater than N), terminal 200 transmits the PUSCH by applying a transmission waveform (for example, CP-OFDM) that is semi-statically set by transformPrecoder or msg3-transformPrecoder.
[0096] Here, the value of threshold N may be given in advance according to the standard, or may be set (or notified) to terminal 200 by RRC or other signaling.
[0097] <Condition 3: Frequency Domain Resource Allocation Type, Number of Frequency Domain Allocated Resource Blocks (RBs), or Number of Cluster Resource Blocks> Terminal 200 may determine to switch the transmission waveform of the PUSCH to DFT-s-OFDM, for example, based on resource allocation in PUSCH transmission (e.g., frequency resource allocation).
[0098] Terminal 200 may determine switching of the transmission waveform of the PUSCH based on, for example, the frequency resource allocation type of the PUSCH transmission. For example, when the frequency resource allocation type of the PUSCH transmission is Type 1 (e.g., contiguous RB allocation or allocation in which the starting RB and the number of RBs are notified), terminal 200 switches the transmission waveform to DFT-s-OFDM and transmits the PUSCH. On the other hand, when PUSCH transmission is Type 0 (e.g., non-contiguous RB allocation or bitmap allocation using RB / RBG (RB group)), terminal 200 transmits the PUSCH by applying a transmission waveform (e.g., CP-OFDM) semi-statically set by transformPrecoder or msg3-transformPrecoder.
[0099] Furthermore, terminal 200 may determine switching of the transmission waveform of the PUSCH based on, for example, the number of allocated RBs in frequency domain resource allocation for PUSCH transmission. For example, when the number of allocated RBs is equal to or less than N (or is less than N), terminal 200 switches the transmission waveform to DFT-s-OFDM and transmits the PUSCH. On the other hand, when the number of allocated RBs is greater than N (or is equal to or greater than N), terminal 200 transmits the PUSCH by applying a transmission waveform (for example, CP-OFDM) that is semi-statically set by transformPrecoder or msg3-transformPrecoder.
[0100] Here, the value of threshold N may be given in advance according to the standard, or may be set (or notified) to terminal 200 by RRC or other signaling.
[0101] Furthermore, for example, when DFT-s-OFDM supports Clustered DFT-s-OFDM, which can allocate multiple clusters consisting of consecutive RBs, terminal 200 may determine whether to switch the transmission waveform of the PUSCH based on, for example, the number of RBs that make up the cluster.
[0102] For example, when the number of RBs constituting a cluster is equal to or less than N (or is less than N), terminal 200 switches the transmission waveform to DFT-s-OFDM and transmits the PUSCH. On the other hand, when the number of RBs constituting a cluster is greater than N (or is equal to or greater than N), terminal 200 transmits the PUSCH by applying a transmission waveform (for example, CP-OFDM) that is semi-statically set by transformPrecoder or msg3-transformPrecoder.
[0103] Here, the value of the threshold N may be predetermined in accordance with the standard, or may be set (or notified) by RRC or other signaling.
[0104] The cluster used to determine whether to switch the transmission waveform may be the cluster with the largest number of RBs, or the cluster with the smallest number of RBs, or may be a cluster with a specific index.
[0105] Furthermore, for example, when DFT-s-OFDM supports Clustered DFT-s-OFDM, which is capable of allocating multiple clusters each consisting of consecutive RBs, terminal 200 may determine whether to switch the transmission waveform of the PUSCH based on, for example, the number of clusters.
[0106] For example, when the number of clusters is equal to or less than N (or less than N), terminal 200 switches the transmission waveform to DFT-s-OFDM and transmits the PUSCH. On the other hand, when the number of clusters is greater than N (or greater than or equal to N), terminal 200 transmits the PUSCH by applying a transmission waveform (for example, CP-OFDM) that is semi-statically set by transformPrecoder or msg3-transformPrecoder.
[0107] Here, the value of the threshold N may be predetermined in accordance with the standard, or may be set (or notified) by RRC or other signaling.
[0108] <Condition 4: DMRS Type or Number of Additional DMRS Symbols> Terminal 200 may determine to switch the transmission waveform of the PUSCH to DFT-s-OFDM, for example, based on the DMRS configuration for PUSCH transmission.
[0109] Terminal 200 may determine switching of the PUSCH transmission waveform based on, for example, the DMRS type in PUSCH transmission. For example, in existing NR, DFT-s-OFDM supports DMRS type=Type 1 but does not support DMRS type=Type 2. In this case, for example, when the DMRS type of PUSCH transmission is Type 1, terminal 200 switches the transmission waveform to DFT-s-OFDM and transmits the PUSCH. On the other hand, when the DMRS type of PUSCH transmission is Type 2, terminal 200 transmits the PUSCH by applying a transmission waveform (for example, CP-OFDM) semi-statically set by transformPrecoder or msg3-transformPrecoder.
[0110] Note that the DMRS type supported by DFT-s-OFDM is not limited to Type 1 and may support other types. Also, the DMRS type is not limited to Type 1 and Type 2 and may include other types.
[0111] Furthermore, terminal 200 may determine whether to switch the transmission waveform of the PUSCH based on, for example, the number of additional DMRS symbols in the DMRS configuration of PUSCH transmission.
[0112] For example, if the number of additional DMRS symbols is N or more (or greater than N), terminal 200 switches the transmission waveform to DFT-s-OFDM and transmits the PUSCH. On the other hand, if the number of additional DMRS symbols is less than N (or equal to or less than N), terminal 200 transmits the PUSCH by applying a transmission waveform (e.g., CP-OFDM) that is semi-statically set by transformPrecoder or msg3-transformPrecoder.
[0113] Here, the value of the threshold N may be predetermined in accordance with the standard, or may be set (or notified) by RRC or other signaling.
[0114] The conditions for switching the transmission waveform have been explained above.
[0115] Terminal 200 may switch the transmission waveform of the PUSCH to DFT-s-OFDM based on, for example, any one of the four conditions described above. For example, terminal 200 may switch the transmission waveform of the PUSCH to DFT-s-OFDM based on condition 1.
[0116] Alternatively, terminal 200 may switch the transmission waveform of the PUSCH to DFT-s-OFDM based on, for example, two or more of the four conditions described above.
[0117] When multiple conditions are used, for example, when any one of the multiple conditions satisfies the condition for switching the transmission waveform to DFT-s-OFDM, terminal 200 may switch the transmission waveform to DFT-s-OFDM. For example, when all of the multiple conditions do not satisfy the condition for switching the transmission waveform to DFT-s-OFDM, terminal 200 may transmit the PUSCH by applying a transmission waveform (for example, CP-OFDM) that is semi-statically set by transformPrecoder or msg3-transformPrecoder.
[0118] Furthermore, for example, when the conditions for switching the transmission waveform to DFT-s-OFDM are satisfied under all of a plurality of conditions, terminal 200 may switch the transmission waveform to DFT-s-OFDM. For example, when any one of a plurality of conditions does not satisfy the condition for switching the transmission waveform to DFT-s-OFDM, terminal 200 may transmit the PUSCH by applying a transmission waveform (for example, CP-OFDM) that is semi-statically set by transformPrecoder or msg3-transformPrecoder.
[0119] Furthermore, for example, when M (or M or more) conditions among a plurality of conditions satisfy the condition for switching the transmission waveform to DFT-s-OFDM, terminal 200 may switch the transmission waveform to DFT-s-OFDM. Here, the value of M may be given in advance according to the standard, or may be configured (or notified) to terminal 200 by RRC or other signal.
[0120] Furthermore, for example, the terminal 200 may be configured (or notified) by RRC or other signal as to which (one or more) of the four conditions described above to use to switch the transmission waveform to DFT-s-OFDM (e.g., information regarding the conditions to be applied).
[0121] The above has described methods for determining a default transmission waveform (for example, a transmission waveform of a PUSCH (DG-PUSCH) dynamically scheduled by DCI format 0-0, a transmission waveform of a PUSCH dynamically scheduled by DCI format 0-1 or DCI format 0-2 when transformPrecoder is not configured by RRC, and a transmission waveform of a CG-PUSCH when transformPrecoder is not configured by RRC).
[0122] On the other hand, for example, when transformPrecoder is configured by RRC, a transmission waveform that is semi-statically set by transformPrecoder may be applied to the transmission waveform of a PUSCH that is dynamically scheduled by DCI format 0-1 or DCI format 0-2 and the transmission waveform of a CG-PUSCH.
[0123] In this way, according to the first variant, it is possible to dynamically switch the PUSCH transmission waveform (e.g., default transmission waveform) determined based on msg3-transformPrecoder, which is a cell-specific RRC, in an environment where improvement in coverage or transmission characteristics is expected, without the overhead of adding a transmission waveform notification field to DCI.
[0124] (Embodiment 2) As described above, in NR, the transmission waveform of Msg.3 PUSCH is determined based on Msg.3-transformPrecoder, which is a parameter set by RRC. In this way, the transmission waveform of Msg.3 PUSCH is determined based on Msg.3-transformPrecoder, which is a parameter set by cell-specific RRC. For this reason, for example, when DFT-s-OFDM, which is a transmission waveform suitable for terminals expected to ensure coverage, is set by cell-specific RRC, terminals that can transmit Mg.3 PUSCH while ensuring a high SINR may find it difficult to perform highly efficient transmission using CP-OFDM, and the frequency utilization efficiency of the entire cell may decrease. On the other hand, when CP-OFDM is set by cell-specific RRC, the coverage performance of terminals at the cell edge may deteriorate.
[0125] Therefore, in the present embodiment, when terminal 200 applies multiple Physical Random Access Channel (PRACH) transmission or PRACH repetition to transmit PRACH (or Message 1 (Msg.1)), it ignores the transmission waveform setting by Mg.3-transformPrecoder and determines the transmission waveform of Mg.3 PUSCH to be DFT-s-OFDM. On the other hand, when terminal 200 applies multiple PRACH transmission or PRACH repetition to transmit PRACH, it determines the transmission waveform of Mg.3 PUSCH in accordance with the setting of Mg.3-transformPrecoder.
[0126] Here, terminal 200 that supports multiple PRACH transmission or PRACH repetition capability may also support, for example, a capability that allows selection of a transmission waveform without relying on notification of Msg.3-transformPrecoder. Note that the capability that allows selection of a transmission waveform without relying on notification of Msg.3-transformPrecoder may be a capability that dynamically switches the transmission waveform of Mg.3 PUSCH, or may be a capability that ignores the CP-OFDM setting for Mg.3 PUSCH by Msg.3-transformPrecoder.
[0127] Generally, different RACH resources are used for a PRACH that does not employ repetition and for a PRACH that employs multiple PRACH transmission or PRACH repetition. Therefore, according to the present embodiment, base station 100 can identify the transmission waveform of Msg.3 PUSCH transmitted by terminal 200 (e.g., a transmission waveform based on DFT-s-OFDM or msg3-transformPrecoder) depending on the presence or absence of RACH repetition. Furthermore, base station 100 does not need additional RACH resources to identify the transmission waveform of Msg.3 PUSCH.
[0128] Furthermore, in the present embodiment, when terminal 200 ignores the setting of Msg.3-transformPrecoder and determines the transmission waveform of Msg.3 PUSCH (for example, a signal in a random access procedure) to be DFT-s-OFDM, it may apply the method of embodiment 1 to determining the transmission waveform for a PUSCH (for example, DG-PUSCH or CG-PUSCH) after the random access procedure.
[0129] On the other hand, when terminal 200 determines the transmission waveform of Msg.3 PUSCH in accordance with the setting of Msg.3-transformPrecoder, terminal 200 may apply the transmission waveform semi-statically set by transformPrecoder or Msg.3-transformPrecoder to a PUSCH after the random access procedure (e.g., DG-PUSCH or CG-PUSCH).
[0130] Base station 100 (e.g., base station / network) semi-statically configures a transmission waveform for terminal 200 using transformPrecoder or Msg.3-transformPrecoder, which are higher layer parameters, similar to NR up to Rel. 17. For example, terminal 200 can be configured with a semi-static transmission waveform for CP-OFDM using transformPrecoder or Msg.3-transformPrecoder.
[0131] In the present embodiment, when terminal 200 determines the transmission waveform of Msg.3 PUSCH to be DFT-s-OFDM while ignoring the setting of Msg.3-transformPrecoder, terminal 200 determines to switch the transmission waveform of PUSCH transmitted after Msg.3 PUSCH to DFT-s-OFDM based on one or more of the following conditions:
[0132] <Condition 1: Presence or Absence of Repetition, or Number of Repetitions> Terminal 200 may determine to switch the transmission waveform of the PUSCH to DFT-s-OFDM, for example, based on the presence or absence of repetition in PUSCH transmission. For example, when repetition is applied to PUSCH transmission, terminal 200 switches the transmission waveform to DFT-s-OFDM and transmits the PUSCH. On the other hand, when repetition is not applied to PUSCH transmission, terminal 200 transmits the PUSCH by applying a transmission waveform (for example, CP-OFDM) that is semi-statically set by transformPrecoder or msg3-transformPrecoder.
[0133] Furthermore, terminal 200 may determine to switch the transmission waveform of PUSCH to DFT-s-OFDM based on, for example, the number of repetitions of PUSCH. For example, if the number of repetitions is N or more (or greater than N), terminal 200 switches the transmission waveform to DFT-s-OFDM and transmits PUSCH. On the other hand, if the number of repetitions is less than N (or equal to or less than N), terminal 200 transmits PUSCH by applying a transmission waveform (for example, CP-OFDM) that is quasi-statically set by transformPrecoder or msg3-transformPrecoder.
[0134] Here, the value of threshold N may be given in advance according to the standard, or may be set (or notified) to terminal 200 by RRC or other signaling.
[0135] <Condition 2: Number of Transmission Layers> Terminal 200 may determine whether to switch the transmission waveform of the PUSCH to DFT-s-OFDM, for example, based on the number of transmission layers (or the number of ranks) in PUSCH transmission.
[0136] As described above, in existing NR, DFT-s-OFDM supports one-layer transmission. In this case, for example, when PUSCH transmission is one-layer transmission, terminal 200 switches the transmission waveform to DFT-s-OFDM and transmits the PUSCH. On the other hand, when PUSCH transmission is multi-layer transmission, terminal 200 transmits the PUSCH by applying a transmission waveform (e.g., CP-OFDM) quasi-statically set by transformPrecoder or msg3-transformPrecoder.
[0137] Furthermore, for example, when DFT-s-OFDM supports multi-layer transmission, terminal 200 may switch the transmission waveform to DFT-s-OFDM based on the number of transmission layers, which is one or more. For example, when the number of transmission layers is equal to or less than N (or is smaller than N), terminal 200 switches the transmission waveform to DFT-s-OFDM and transmits the PUSCH. On the other hand, when the number of transmission layers is greater than N (or is equal to or greater than N), terminal 200 transmits the PUSCH by applying a transmission waveform (for example, CP-OFDM) that is semi-statically set by transformPrecoder or msg3-transformPrecoder.
[0138] Here, the value of threshold N may be given in advance according to the standard, or may be set (or notified) to terminal 200 by RRC or other signaling.
[0139] <Condition 3: Frequency Domain Resource Allocation Type, Number of Frequency Domain Allocated Resource Blocks (RBs), or Number of Cluster Resource Blocks> Terminal 200 may determine to switch the transmission waveform of the PUSCH to DFT-s-OFDM, for example, based on resource allocation in PUSCH transmission (e.g., frequency resource allocation).
[0140] Terminal 200 may determine switching of the transmission waveform of the PUSCH based on, for example, the frequency resource allocation type of the PUSCH transmission. For example, when the frequency resource allocation type of the PUSCH transmission is Type 1 (e.g., contiguous RB allocation or allocation in which the starting RB and the number of RBs are notified), terminal 200 switches the transmission waveform to DFT-s-OFDM and transmits the PUSCH. On the other hand, when PUSCH transmission is Type 0 (e.g., non-contiguous RB allocation or bitmap allocation using RB / RBG (RB group)), terminal 200 transmits the PUSCH by applying a transmission waveform (e.g., CP-OFDM) semi-statically set by transformPrecoder or msg3-transformPrecoder.
[0141] Furthermore, terminal 200 may determine switching of the transmission waveform of the PUSCH based on, for example, the number of allocated RBs in frequency domain resource allocation for PUSCH transmission. For example, when the number of allocated RBs is equal to or less than N (or is less than N), terminal 200 switches the transmission waveform to DFT-s-OFDM and transmits the PUSCH. On the other hand, when the number of allocated RBs is greater than N (or is equal to or greater than N), terminal 200 transmits the PUSCH by applying a transmission waveform (for example, CP-OFDM) that is semi-statically set by transformPrecoder or msg3-transformPrecoder.
[0142] Here, the value of threshold N may be given in advance according to the standard, or may be set (or notified) to terminal 200 by RRC or other signaling.
[0143] Furthermore, for example, when DFT-s-OFDM supports Clustered DFT-s-OFDM, which can allocate multiple clusters consisting of consecutive RBs, terminal 200 may determine whether to switch the transmission waveform of the PUSCH based on, for example, the number of RBs that make up the cluster.
[0144] For example, when the number of RBs constituting a cluster is equal to or less than N (or is less than N), terminal 200 switches the transmission waveform to DFT-s-OFDM and transmits the PUSCH. On the other hand, when the number of RBs constituting a cluster is greater than N (or is equal to or greater than N), terminal 200 transmits the PUSCH by applying a transmission waveform (for example, CP-OFDM) that is semi-statically set by transformPrecoder or msg3-transformPrecoder.
[0145] Here, the value of the threshold N may be predetermined in accordance with the standard, or may be set (or notified) by RRC or other signaling.
[0146] The cluster used to determine whether to switch the transmission waveform may be the cluster with the largest number of RBs, or the cluster with the smallest number of RBs, or may be a cluster with a specific index.
[0147] Furthermore, for example, when DFT-s-OFDM supports Clustered DFT-s-OFDM, which is capable of allocating multiple clusters each consisting of consecutive RBs, terminal 200 may determine whether to switch the transmission waveform of the PUSCH based on, for example, the number of clusters.
[0148] For example, when the number of clusters is equal to or less than N (or less than N), terminal 200 switches the transmission waveform to DFT-s-OFDM and transmits the PUSCH. On the other hand, when the number of clusters is greater than N (or greater than or equal to N), terminal 200 transmits the PUSCH by applying a transmission waveform (for example, CP-OFDM) that is semi-statically set by transformPrecoder or msg3-transformPrecoder.
[0149] Here, the value of the threshold N may be predetermined in accordance with the standard, or may be set (or notified) by RRC or other signaling.
[0150] <Condition 4: DMRS Type or Number of Additional DMRS Symbols> Terminal 200 may determine to switch the transmission waveform of the PUSCH to DFT-s-OFDM, for example, based on the DMRS configuration for PUSCH transmission.
[0151] Terminal 200 may determine switching of the PUSCH transmission waveform based on, for example, the DMRS type in PUSCH transmission. For example, in existing NR, DFT-s-OFDM supports DMRS type=Type 1 but does not support DMRS type=Type 2. In this case, for example, when the DMRS type of PUSCH transmission is Type 1, terminal 200 switches the transmission waveform to DFT-s-OFDM and transmits the PUSCH. On the other hand, when the DMRS type of PUSCH transmission is Type 2, terminal 200 transmits the PUSCH by applying a transmission waveform (for example, CP-OFDM) semi-statically set by transformPrecoder or msg3-transformPrecoder.
[0152] Note that the DMRS type supported by DFT-s-OFDM is not limited to Type 1 and may support other types. Also, the DMRS type is not limited to Type 1 and Type 2 and may include other types.
[0153] Furthermore, terminal 200 may determine switching of the transmission waveform of the PUSCH based on, for example, the number of additional DMRS symbols in the DMRS configuration of PUSCH transmission. For example, if the number of additional DMRS symbols is N or more (or greater than N), terminal 200 switches the transmission waveform to DFT-s-OFDM and transmits the PUSCH. On the other hand, if the number of additional DMRS symbols is less than N (or equal to or less than N), terminal 200 transmits the PUSCH by applying a transmission waveform (for example, CP-OFDM) semi-statically configured by transformPrecoder or msg3-transformPrecoder.
[0154] Here, the value of the threshold N may be predetermined in accordance with the standard, or may be set (or notified) by RRC or other signaling.
[0155] The conditions for switching the transmission waveform have been explained above.
[0156] Terminal 200 may switch the transmission waveform of the PUSCH to DFT-s-OFDM based on, for example, any one of the four conditions described above. For example, terminal 200 may switch the transmission waveform of the PUSCH to DFT-s-OFDM based on condition 1.
[0157] Alternatively, terminal 200 may switch the transmission waveform of the PUSCH to DFT-s-OFDM based on, for example, two or more of the four conditions described above.
[0158] When multiple conditions are used, for example, when any one of the multiple conditions satisfies the condition for switching the transmission waveform to DFT-s-OFDM, terminal 200 may switch the transmission waveform to DFT-s-OFDM. For example, when all of the multiple conditions do not satisfy the condition for switching the transmission waveform to DFT-s-OFDM, terminal 200 may transmit the PUSCH by applying a transmission waveform (for example, CP-OFDM) that is semi-statically set by transformPrecoder or msg3-transformPrecoder.
[0159] Furthermore, for example, when the conditions for switching the transmission waveform to DFT-s-OFDM are satisfied under all of a plurality of conditions, terminal 200 may switch the transmission waveform to DFT-s-OFDM. For example, when any one of a plurality of conditions does not satisfy the condition for switching the transmission waveform to DFT-s-OFDM, terminal 200 may transmit the PUSCH by applying a transmission waveform (for example, CP-OFDM) that is semi-statically set by transformPrecoder or msg3-transformPrecoder.
[0160] Furthermore, for example, when M (or M or more) conditions among a plurality of conditions satisfy the condition for switching the transmission waveform to DFT-s-OFDM, terminal 200 may switch the transmission waveform to DFT-s-OFDM. Here, the value of M may be given in advance according to the standard, or may be configured (or notified) to terminal 200 by RRC or other signal.
[0161] Furthermore, for example, the terminal 200 may be configured (or notified) by RRC or other signal as to which (one or more) of the four conditions described above to use to switch the transmission waveform to DFT-s-OFDM (e.g., information regarding the conditions to be applied).
[0162] An example of operation has been described above in which terminal 200 ignores the setting of Mg.3-transformPrecoder when determining the transmission waveform of Msg.3 PUSCH and determines that the transmission waveform of Msg.3 PUSCH is DFT-s-OFDM.
[0163] On the other hand, when the transmission waveform of Msg.3 PUSCH is determined according to the setting of Msg.3-transformPrecoder, terminal 200 may transmit the PUSCH by applying the transmission waveform set semi-statically by transformPrecoder or Msg.3-transformPrecoder.
[0164] According to the present embodiment, when terminal 200 switches the transmission waveform of Msg.3 PUSCH to DFT-s-OFDM in order to improve coverage performance during a random access procedure (e.g., during initial access), it is possible to dynamically switch the transmission waveform even after the random access procedure in an environment where improvement in coverage or transmission characteristics is expected, without the overhead of adding a transmission waveform notification field to DCI.
[0165] [Example of Operation of Terminal 200] FIG. 5 is a flowchart showing an example of operation of terminal 200.
[0166] In FIG. 5, terminal 200 acquires upper layer parameters such as msg3-transformPrecoder (S201).
[0167] The terminal 200 determines whether PRACH repetition (or multiple PRACH transmission) is applied (S202).
[0168] If PRACH repetition is applied (S202: Yes), terminal 200 ignores the setting of Msg.3-transformPrecoder, sets the transmission waveform of Msg.3 PUSCH to DFT-s-OFDM, and transmits Msg.3 PUSCH (S203).
[0169] The terminal 200 acquires transformPrecoder (S204).
[0170] Terminal 200 acquires information regarding conditions for switching the transmission waveform of the PUSCH to DFT-s-OFDM (S205). The information regarding conditions for switching the transmission waveform of the PUSCH to DFT-s-OFDM may include, for example, information regarding a setting of an applicable condition among the above-mentioned four conditions, and may include information regarding parameters and settings (for example, Repetition, number of layers, RB setting, DMRS setting, or threshold value) used in the above-mentioned four conditions.
[0171] The terminal 200 determines whether or not a condition for switching the PUSCH transmission waveform to DFT-s-OFDM is met (S206).
[0172] If the condition for switching the PUSCH transmission waveform to DFT-s-OFDM is met (S206: Yes), terminal 200 sets (or switches) the PUSCH transmission waveform to DFT-s-OFDM and transmits the PUSCH (S207).
[0173] If PRACH repetition is not applied in the process of S202 (S202: No), terminal 200 transmits Msg.3 PUSCH using the transmission waveform set by Msg.3-transformPrecoder (S208). Terminal 200 acquires transformPrecoder (S209).
[0174] Furthermore, if PRACH repetition is not applied in the process of S202 (S202: No), or if the condition for switching the PUSCH transmission waveform to DFT-s-OFDM is not satisfied in the process of S206 (S206: No), terminal 200 transmits PUSCH by applying a transmission waveform (for example, CP-OFDM) set by at least one of transformPrecoder and msg3-transformPrecoder (S210).
[0175] As described above, in the present embodiment, when terminal 200 determines that the transmission waveform of Msg.3 PUSCH is DFT-s-OFDM while ignoring the setting of msg3-transformPrecoder, it determines to switch the transmission waveform of PUSCHs transmitted after Msg.3 PUSCH to DFT-s-OFDM based on conditions related to PUSCH transmission parameters and settings. As a result, when terminal 200 switches the transmission waveform of Mg.3 PUSCH to DFT-s-OFDM while ignoring the setting of msg3-transformPrecoder, it is possible to dynamically switch the transmission waveform of PUSCHs in accordance with instantaneous fluctuations in the channel or interference environment in an environment where improvement in coverage or transmission characteristics is expected, even for transmission of PUSCHs after Mg.3 PUSCH. Therefore, according to the present embodiment, terminal 200 can appropriately transmit signals on the uplink.
[0176] Note that, in the present embodiment, a case has been described in which terminal 200 determines whether to switch to DFT-s-OFDM, ignoring the higher layer parameter settings for Mg.3 PUSCH, depending on whether multiple PRACH transmission or PRACH repetition is applied, but the determination criteria are not limited to this. For example, similar to Embodiment 1, terminal 200 may determine whether to switch to DFT-s-OFDM, ignoring the higher layer parameter settings for Mg.3 PUSCH, based on conditions related to PUSCH transmission parameters or settings.
[0177] (Modification 2) In Modification 2, for example, the method of the above-described second embodiment may be applied to determining a default transmission waveform.
[0178] Here, the determination of a default transmission waveform refers to a case where the transmission waveform is determined based on Msg.3-transformPrecoder, as described above. For example, the determination of a default transmission waveform may be at least one of the determination of a transmission waveform of a PUSCH (DG-PUSCH) dynamically scheduled by DCI format 0-0, the determination of a transmission waveform of a PUSCH dynamically scheduled by DCI format 0-1 or DCI format 0-2 when transformPrecoder is not configured by RRC, and the determination of a transmission waveform of a CG-PUSCH when transformPrecoder is not configured by RRC.
[0179] In the second modification, when terminal 200 transmits a PRACH by applying multiple PRACH transmission or PRACH repetition, similarly to the second embodiment, terminal 200 ignores the setting of Msg.3-transformPrecoder and determines the transmission waveform of Mg.3 PUSCH to be DFT-s-OFDM. In this case, terminal 200 that supports the capability of multiple PRACH transmission or PRACH repetition may also support, for example, a capability that allows selection of a transmission waveform without relying on notification of Mg.3-transformPrecoder. Here, the capability that allows selection of a transmission waveform without relying on notification of Mg.3-transformPrecoder may be a capability that dynamically switches the transmission waveform of Mg.3 PUSCH, or may be a capability that ignores the setting of CP-OFDM by Mg.3-transformPrecoder for Mg.3 PUSCH.
[0180] In the second modification, when terminal 200 determines the transmission waveform of Msg.3 PUSCH to be DFT-s-OFDM while ignoring the setting of Msg.3-transformPrecoder, the method of the second embodiment described above may be applied to determining the default transmission waveform of a PUSCH transmitted after Msg.3 PUSCH (for example, the transmission waveform of a PUSCH when transformPrecoder is not set).
[0181] The base station 100 (e.g., a base station / network) semi-statically sets the transmission waveform for the terminal 200 using the higher layer parameter transformPrecoder or Msg.3-transformPrecoder, similar to NR up to Rel. 17.
[0182] For example, terminal 200 can configure CP-OFDM with semi-static transmission waveforms for a PUSCH that is dynamically scheduled by DCI format 0-0, a PUSCH that is dynamically scheduled by DCI format 0-1 or DCI format 0-2 when transformPrecoder is not configured by RRC, and a CG-PUSCH when transformPrecoder is not configured by RRC.
[0183] In the second modification, when terminal 200 determines the transmission waveform of Msg.3 PUSCH to be DFT-s-OFDM while ignoring the setting of Mg.3-transformPrecoder, terminal 200 may switch the transmission waveform of at least one of the following to DFT-s-OFDM based on one or more of the following conditions, namely, a PUSCH dynamically scheduled by DCI format 0-0, a PUSCH dynamically scheduled by DCI format 0-1 or DCI format 0-2 when transformPrecoder is not set by RRC, and a CG-PUSCH when transformPrecoder is not set by RRC, and transmit the PUSCH.
[0184] <Condition 1: Presence or Absence of Repetition, or Number of Repetitions> Terminal 200 may determine to switch the transmission waveform of the PUSCH to DFT-s-OFDM, for example, based on the presence or absence of repetition in PUSCH transmission. For example, when repetition is applied to PUSCH transmission, terminal 200 switches the transmission waveform to DFT-s-OFDM and transmits the PUSCH. On the other hand, when repetition is not applied to PUSCH transmission, terminal 200 transmits the PUSCH by applying a transmission waveform (for example, CP-OFDM) that is semi-statically set by transformPrecoder or msg3-transformPrecoder.
[0185] Furthermore, terminal 200 may determine to switch the transmission waveform of PUSCH to DFT-s-OFDM based on, for example, the number of repetitions of PUSCH. For example, if the number of repetitions is N or more (or greater than N), terminal 200 switches the transmission waveform to DFT-s-OFDM and transmits PUSCH. On the other hand, if the number of repetitions is less than N (or equal to or less than N), terminal 200 transmits PUSCH by applying a transmission waveform (for example, CP-OFDM) that is quasi-statically set by transformPrecoder or msg3-transformPrecoder.
[0186] Here, the value of threshold N may be given in advance according to the standard, or may be set (or notified) to terminal 200 by RRC or other signaling.
[0187] <Condition 2: Number of Transmission Layers> Terminal 200 may determine whether to switch the transmission waveform of the PUSCH to DFT-s-OFDM, for example, based on the number of transmission layers (or the number of ranks) in PUSCH transmission.
[0188] As described above, in existing NR, DFT-s-OFDM supports one-layer transmission. In this case, for example, when PUSCH transmission is one-layer transmission, terminal 200 switches the transmission waveform to DFT-s-OFDM and transmits the PUSCH. On the other hand, when PUSCH transmission is multi-layer transmission, terminal 200 transmits the PUSCH by applying a transmission waveform (e.g., CP-OFDM) quasi-statically set by transformPrecoder or msg3-transformPrecoder.
[0189] Furthermore, for example, when DFT-s-OFDM supports multi-layer transmission, terminal 200 may switch the transmission waveform to DFT-s-OFDM based on the number of transmission layers, which is one or more. For example, when the number of transmission layers is equal to or less than N (or is smaller than N), terminal 200 switches the transmission waveform to DFT-s-OFDM and transmits the PUSCH. On the other hand, when the number of transmission layers is greater than N (or is equal to or greater than N), terminal 200 transmits the PUSCH by applying a transmission waveform (for example, CP-OFDM) that is semi-statically set by transformPrecoder or msg3-transformPrecoder.
[0190] Here, the value of threshold N may be given in advance according to the standard, or may be set (or notified) to terminal 200 by RRC or other signaling.
[0191] <Condition 3: Frequency Domain Resource Allocation Type, Number of Frequency Domain Allocated Resource Blocks (RBs), or Number of Cluster Resource Blocks> Terminal 200 may determine to switch the transmission waveform of the PUSCH to DFT-s-OFDM, for example, based on resource allocation in PUSCH transmission (e.g., frequency resource allocation).
[0192] Terminal 200 may determine switching of the transmission waveform of the PUSCH based on, for example, the frequency resource allocation type of the PUSCH transmission. For example, when the frequency resource allocation type of the PUSCH transmission is Type 1 (e.g., contiguous RB allocation or allocation in which the starting RB and the number of RBs are notified), terminal 200 switches the transmission waveform to DFT-s-OFDM and transmits the PUSCH. On the other hand, when PUSCH transmission is Type 0 (e.g., non-contiguous RB allocation or bitmap allocation using RB / RBG (RB group)), terminal 200 transmits the PUSCH by applying a transmission waveform (e.g., CP-OFDM) semi-statically set by transformPrecoder or msg3-transformPrecoder.
[0193] Furthermore, terminal 200 may determine switching of the transmission waveform of the PUSCH based on, for example, the number of allocated RBs in frequency domain resource allocation for PUSCH transmission. For example, when the number of allocated RBs is equal to or less than N (or is less than N), terminal 200 switches the transmission waveform to DFT-s-OFDM and transmits the PUSCH. On the other hand, when the number of allocated RBs is greater than N (or is equal to or greater than N), terminal 200 transmits the PUSCH by applying a transmission waveform (for example, CP-OFDM) that is semi-statically set by transformPrecoder or msg3-transformPrecoder.
[0194] Here, the value of threshold N may be given in advance according to the standard, or may be set (or notified) to terminal 200 by RRC or other signaling.
[0195] Furthermore, for example, when DFT-s-OFDM supports Clustered DFT-s-OFDM, which can allocate multiple clusters consisting of consecutive RBs, terminal 200 may determine whether to switch the transmission waveform of the PUSCH based on, for example, the number of RBs that make up the cluster.
[0196] For example, when the number of RBs constituting a cluster is equal to or less than N (or is less than N), terminal 200 switches the transmission waveform to DFT-s-OFDM and transmits the PUSCH. On the other hand, when the number of RBs constituting a cluster is greater than N (or is equal to or greater than N), terminal 200 transmits the PUSCH by applying a transmission waveform (for example, CP-OFDM) that is semi-statically set by transformPrecoder or msg3-transformPrecoder.
[0197] Here, the value of the threshold N may be predetermined in accordance with the standard, or may be set (or notified) by RRC or other signaling.
[0198] The cluster used to determine whether to switch the transmission waveform may be the cluster with the largest number of RBs, or the cluster with the smallest number of RBs, or may be a cluster with a specific index.
[0199] Furthermore, for example, when DFT-s-OFDM supports Clustered DFT-s-OFDM, which is capable of allocating multiple clusters each consisting of consecutive RBs, terminal 200 may determine whether to switch the transmission waveform of the PUSCH based on, for example, the number of clusters.
[0200] For example, when the number of clusters is equal to or less than N (or less than N), terminal 200 switches the transmission waveform to DFT-s-OFDM and transmits the PUSCH. On the other hand, when the number of clusters is greater than N (or greater than or equal to N), terminal 200 transmits the PUSCH by applying a transmission waveform (for example, CP-OFDM) that is semi-statically set by transformPrecoder or msg3-transformPrecoder.
[0201] Here, the value of the threshold N may be predetermined in accordance with the standard, or may be set (or notified) by RRC or other signaling.
[0202] <Condition 4: DMRS Type or Number of Additional DMRS Symbols> Terminal 200 may determine to switch the transmission waveform of the PUSCH to DFT-s-OFDM, for example, based on the DMRS configuration for PUSCH transmission.
[0203] Terminal 200 may determine switching of the PUSCH transmission waveform based on, for example, the DMRS type in PUSCH transmission. For example, in existing NR, DFT-s-OFDM supports DMRS type=Type 1 but does not support DMRS type=Type 2. In this case, for example, when the DMRS type of PUSCH transmission is Type 1, terminal 200 switches the transmission waveform to DFT-s-OFDM and transmits the PUSCH. On the other hand, when the DMRS type of PUSCH transmission is Type 2, terminal 200 transmits the PUSCH by applying a transmission waveform (for example, CP-OFDM) semi-statically set by transformPrecoder or msg3-transformPrecoder.
[0204] Note that the DMRS type supported by DFT-s-OFDM is not limited to Type 1 and may support other types. Also, the DMRS type is not limited to Type 1 and Type 2 and may include other types.
[0205] Furthermore, terminal 200 may determine whether to switch the transmission waveform of the PUSCH based on, for example, the number of additional DMRS symbols in the DMRS configuration of PUSCH transmission.
[0206] For example, if the number of additional DMRS symbols is N or more (or greater than N), terminal 200 switches the transmission waveform to DFT-s-OFDM and transmits the PUSCH. On the other hand, if the number of additional DMRS symbols is less than N (or equal to or less than N), terminal 200 transmits the PUSCH by applying a transmission waveform (e.g., CP-OFDM) that is semi-statically set by transformPrecoder or msg3-transformPrecoder.
[0207] Here, the value of the threshold N may be predetermined in accordance with the standard, or may be set (or notified) by RRC or other signaling.
[0208] The conditions for switching the transmission waveform have been explained above.
[0209] Terminal 200 may switch the transmission waveform of the PUSCH to DFT-s-OFDM based on, for example, any one of the four conditions described above. For example, terminal 200 may switch the transmission waveform of the PUSCH to DFT-s-OFDM based on condition 1.
[0210] Alternatively, terminal 200 may switch the transmission waveform of the PUSCH to DFT-s-OFDM based on, for example, two or more of the four conditions described above.
[0211] When multiple conditions are used, for example, when any one of the multiple conditions satisfies the condition for switching the transmission waveform to DFT-s-OFDM, terminal 200 may switch the transmission waveform to DFT-s-OFDM. For example, when all of the multiple conditions do not satisfy the condition for switching the transmission waveform to DFT-s-OFDM, terminal 200 may transmit the PUSCH by applying a transmission waveform (for example, CP-OFDM) that is semi-statically set by transformPrecoder or msg3-transformPrecoder.
[0212] Furthermore, for example, when the conditions for switching the transmission waveform to DFT-s-OFDM are satisfied under all of a plurality of conditions, terminal 200 may switch the transmission waveform to DFT-s-OFDM. For example, when any one of a plurality of conditions does not satisfy the condition for switching the transmission waveform to DFT-s-OFDM, terminal 200 may transmit the PUSCH by applying a transmission waveform (for example, CP-OFDM) that is semi-statically set by transformPrecoder or msg3-transformPrecoder.
[0213] Furthermore, for example, when M (or M or more) conditions among a plurality of conditions satisfy the condition for switching the transmission waveform to DFT-s-OFDM, terminal 200 may switch the transmission waveform to DFT-s-OFDM. Here, the value of M may be given in advance according to the standard, or may be configured (or notified) to terminal 200 by RRC or other signal.
[0214] Furthermore, for example, the terminal 200 may be configured (or notified) by RRC or other signal as to which (one or more) of the four conditions described above to use to switch the transmission waveform to DFT-s-OFDM (e.g., information regarding the conditions to be applied).
[0215] The above has described a method for determining a default transmission waveform when terminal 200 ignores the setting of Mg.3-transformPrecoder and determines the transmission waveform of Msg.3 PUSCH to be DFT-s-OFDM.
[0216] On the other hand, when the transmission waveform of Mg.3 PUSCH is determined in accordance with the setting of Msg.3-transformPrecoder, terminal 200 may transmit the PUSCH by applying the transmission waveform semi-statically set by transformPrecoder or Msg.3-transformPrecoder. Furthermore, terminal 200 transmits the PUSCH by applying the transmission waveform semi-statically set by transformPrecoder to the transmission waveform of PUSCH dynamically scheduled by DCI format 0-1 or DCI format 0-2 when transformPrecoder is set and the transmission waveform of CG-PUSCH.
[0217] According to the second modification, when terminal 200 switches the transmission waveform of Msg.3 PUSCH to DFT-s-OFDM in order to improve coverage performance during a random access procedure (e.g., during initial access), it is possible to continue to dynamically switch the transmission waveform of PUSCH, which can be determined based on Msg.3-transformPrecoder, which is a cell-specific RRC, even after the random access procedure, without the overhead of adding a transmission waveform notification field to DCI in an environment where improvement in coverage or transmission characteristics is expected.
[0218] In determining the transmission waveform of Msg.3 PUSCH, if terminal 200 ignores the setting of Msg.3-transformPrecoder and determines the transmission waveform of Msg.3 PUSCH to be DFT-s-OFDM, terminal 200 may determine at least one (for example, a default transmission waveform) of the transmission waveform of PUSCH dynamically scheduled by DCI format 0-0, the transmission waveform of PUSCH dynamically scheduled by DCI format 0-1 or DCI format 0-2 when transformPrecoder is not set by RRC, and the transmission waveform of CG-PUSCH when transformPrecoder is not set by RRC, in accordance with one of the following methods (Option 1 or Option 2):
[0219] <Option 1> In Option 1, when terminal 200 ignores the setting of Mg.3-transformPrecoder and determines the transmission waveform of Msg.3 PUSCH to be DFT-s-OFDM, terminal 200 determines at least one of the transmission waveform of PUSCH dynamically scheduled by DCI format 0-0, the transmission waveform of PUSCH dynamically scheduled by DCI format 0-1 or DCI format 0-2 when transformPrecoder is not set by RRC, and the transmission waveform of CG-PUSCH when transformPrecoder is not set by RRC, to be the transmission waveform set by Mg.3-transformPrecoder.
[0220] Furthermore, when terminal 200 determines the transmission waveform of Msg.3 PUSCH in accordance with the setting of Msg.3-transformPrecoder, terminal 200 may set the transmission waveform semi-statically set by Msg.3-transformPrecoder as the default transmission waveform, and transmit the PUSCH.
[0221] <Option 2> In Option 2, when terminal 200 ignores the setting of Mg.3-transformPrecoder and determines the transmission waveform of Msg.3 PUSCH to be DFT-s-OFDM in determining the transmission waveform of Msg.3 PUSCH, terminal 200 determines, as the transmission waveform applied to Msg.3, at least one of the transmission waveform of PUSCH dynamically scheduled by DCI format 0-0, the transmission waveform of PUSCH dynamically scheduled by DCI format 0-1 or DCI format 0-2 when transformPrecoder is not set by RRC, and the transmission waveform of CG-PUSCH when transformPrecoder is not set by RRC.
[0222] On the other hand, when terminal 200 determines the transmission waveform of Msg.3 PUSCH in accordance with the setting of Msg.3-transformPrecoder, terminal 200 may set the transmission waveform semi-statically set by Msg.3-transformPrecoder as the default transmission waveform and transmit the PUSCH.
[0223] [Configuration of Base Station] Fig. 6 is a block diagram showing an example configuration of base station 100. In Fig. 6, base station 100 has a control unit 101, a higher-level control signal generation unit 102, a downlink control information generation unit 103, an encoding unit 104, a modulation unit 105, a signal allocation unit 106, a transmission unit 107, a reception unit 108, an extraction unit 109, a demodulation unit 110, and a decoding unit 111.
[0224] At least one of the control unit 101, higher-level control signal generation unit 102, downlink control information generation unit 103, coding unit 104, modulation unit 105, signal allocation unit 106, extraction unit 109, demodulation unit 110, and decoding unit 111 shown in Fig. 6 may be included in the control unit shown in Fig. 2. Furthermore, the receiving unit 108 shown in Fig. 6 may be included in the receiving unit shown in Fig. 2.
[0225] The control unit 101, for example, determines information related to uplink transmission (e.g., PUSCH transmission) for terminal 200, and outputs the determined information to at least one of the higher control signal generation unit 102 and the downlink control information generation unit 103. The information related to PUSCH transmission may include, for example, information related to a transmission waveform (e.g., transformPrecoder, msg3-transformPrecoder, or information related to a condition for switching the transmission waveform to DFT-s-OFDM), time domain resource allocation information (e.g., Time Domain Resource Allocation (TDRA) or Repetition), information related to the number of transmission layers, frequency domain resource allocation information (e.g., Frequency Domain Resource Allocation (FDRA)), or information related to DMRS configuration. Furthermore, the control unit 101 outputs the determined information to the extraction unit 109, the demodulation unit 110, and the decoding unit 111.
[0226] Furthermore, the control unit 101 determines, for example, information related to a downlink signal for transmitting a higher control signal or downlink control information (for example, a modulation and coding scheme (MCS) and radio resource allocation), and outputs the determined information to the coding unit 104, the modulation unit 105, and the signal allocation unit 106. Furthermore, the control unit 101 outputs, for example, information related to the downlink signal (for example, a data signal or a higher control signal) to the downlink control information generation unit 103.
[0227] The higher-level control signal generating section 102 generates a higher-level layer control signal bit string based on information input from the control section 101 , for example, and outputs the higher-level layer control signal bit string to the encoding section 104 .
[0228] The downlink control information generating unit 103 generates a downlink control information (e.g., DCI) bit string based on, for example, information input from the control unit 101, and outputs the generated DCI bit string to the encoding unit 104. Note that the control information may be transmitted to multiple terminals.
[0229] For example, based on information input from the control unit 101, the coding unit 104 codes the bit sequence input from the higher control signal generation unit 102 or the DCI bit sequence input from the downlink control information generation unit 103. The coding unit 104 outputs the coded bit sequence to the modulation unit 105.
[0230] The modulation unit 105 modulates the coded bit sequence input from the coding unit 104, for example, based on information input from the control unit 101, and outputs the modulated signal (for example, a symbol sequence) to the signal allocation unit 106.
[0231] The signal allocation unit 106 maps the symbol sequence (including, for example, a downlink data signal or a control signal) input from the modulation unit 105 to the radio resource, for example, based on information indicating the radio resource input from the control unit 101. The signal allocation unit 106 outputs the downlink signal onto which the signal has been mapped to the transmission unit 107.
[0232] The transmitting unit 107 performs, for example, orthogonal frequency division multiplexing (OFDM) transmission waveform generation processing on the signal input from the signal allocating unit 106. Furthermore, in the case of OFDM transmission that adds a cyclic prefix (CP), the transmitting unit 107 performs inverse fast Fourier transform (IFFT) processing on the signal and adds the CP to the signal after the IFFT. Furthermore, the transmitting unit 107 performs RF processing, such as D / A conversion or up-conversion, on the signal and transmits the radio signal to the terminal 200 via an antenna.
[0233] The receiving unit 108 performs RF processing such as downconvert or A / D conversion on an uplink signal received from the terminal 200 via an antenna. In addition, in the case of OFDM transmission, the receiving unit 108 performs Fast Fourier Transform (FFT) processing on the received signal, for example, and outputs the resulting frequency domain signal to the extracting unit 109.
[0234] The extraction unit 109 extracts, for example, based on information input from the control unit 101, a radio resource portion from which an uplink signal (e.g., PUSCH) is transmitted, from the received signal input from the receiving unit 108, and outputs the extracted radio resource portion to the demodulation unit 110.
[0235] The demodulation unit 110 demodulates the uplink signal (e.g., PUSCH) input from the extraction unit 109, based on, for example, information input from the control unit 101. The demodulation unit 110 outputs the demodulation result to, for example, the decoding unit 111.
[0236] The decoding unit 111 performs error correction decoding of the uplink signal (e.g., PUSCH) based on, for example, information input from the control unit 101 and the demodulation result input from the demodulation unit 110, and obtains a decoded received bit sequence.
[0237] [Terminal Configuration] Fig. 7 is a block diagram showing an exemplary configuration of a terminal 200 according to an embodiment of the present disclosure. For example, in Fig. 7, the terminal 200 includes a receiving unit 201, an extracting unit 202, a demodulating unit 203, a decoding unit 204, a control unit 205, an encoding unit 206, a modulating unit 207, a signal allocating unit 208, and a transmitting unit 209.
[0238] At least one of extraction unit 202, demodulation unit 203, decoding unit 204, control unit 205, encoding unit 206, modulation unit 207, and signal allocation unit 208 shown in Fig. 7 may be included in the control unit shown in Fig. 3. Furthermore, transmission unit 209 shown in Fig. 7 may be included in the transmission unit shown in Fig. 3.
[0239] The receiving unit 201 receives, for example, a downlink signal (e.g., a downlink data signal or downlink control information) from the base station 100 via an antenna, and performs RF processing such as downconverting or A / D conversion on the radio received signal to obtain a received signal (baseband signal). Furthermore, when receiving an OFDM signal, the receiving unit 201 performs FFT processing on the received signal to convert it into the frequency domain. The receiving unit 201 outputs the received signal to the extracting unit 202.
[0240] For example, based on information relating to the radio resource of the downlink control information input from the control unit 205, the extraction unit 202 extracts a radio resource portion that may include the downlink control information from the received signal input from the receiving unit 201, and outputs the extracted radio resource portion to the demodulation unit 203. Furthermore, based on information relating to the radio resource of the data signal input from the control unit 205, the extraction unit 202 extracts a radio resource portion that includes the downlink data signal, and outputs the extracted radio resource portion to the demodulation unit 203.
[0241] The demodulation unit 203 demodulates the signal (for example, PDCCH or PDSCH) input from the extraction unit 202 based on information input from the control unit 205 , for example, and outputs the demodulation result to the decoding unit 204 .
[0242] The decoding unit 204 performs error correction decoding of the PDCCH or PDSCH using, for example, the demodulation result input from the demodulation unit 203, and obtains, for example, an upper layer control signal or downlink control information. The decoding unit 204 outputs the upper layer control signal and the downlink control information to the control unit 205. Furthermore, the decoding unit 204 may generate a response signal (for example, ACK / NACK) based on the decoding result of the PDSCH.
[0243] The control unit 205 performs uplink transmission control (including, for example, determining a transmission waveform for PUSCH transmission) according to the above-described method, based on, for example, information related to PUSCH transmission obtained from a signal (for example, an upper layer control signal or downlink control information) input from the decoding unit 204. The control unit 205 outputs the determined information to, for example, the encoding unit 206 and the signal allocation unit 208.
[0244] The encoding unit 206 encodes an uplink data signal (UL data signal) or an uplink control signal, for example, based on information input from the control unit 205. The encoding unit 206 outputs the encoded bit string to the modulation unit 207.
[0245] The modulation unit 207 modulates, for example, the coded bit sequence input from the coding unit 206 and outputs the modulated signal (symbol sequence) to the signal allocation unit 208 .
[0246] The signal allocation unit 208 maps the signal (e.g., a sequence) input from the modulation unit 207 to a radio resource, for example, based on information input from the control unit 205. The signal allocation unit 208 outputs the uplink signal onto which the signal is mapped to the transmission unit 209, for example.
[0247] The transmitter 209 generates a transmission signal waveform, such as OFDM, for the signal input from the signal allocation unit 208. Furthermore, in the case of OFDM transmission using a CP, for example, the transmitter 209 performs IFFT processing on the signal and adds a CP to the signal after the IFFT. Alternatively, when the transmitter 209 generates a single-carrier waveform, a DFT unit (not shown) may be added after the modulator 207 or before the signal allocation unit 208. Furthermore, the transmitter 209 performs RF processing, such as D / A conversion and up-conversion, on the transmission signal, and transmits the radio signal to the base station 100 via an antenna.
[0248] (Other Embodiments) (1) The above-described embodiments, modifications, other transmission waveform determination methods, and quasi-static transmission waveform determination methods similar to existing NR (for example, a method of transmitting a PUSCH by applying a transmission waveform quasi-statically set by transformPrecoder or msg3-transformPrecoder) may be applied differently depending on the type of PUSCH transmission. Also, even when one embodiment or modification is applied, the condition for switching the transmission waveform to DFT-s-OFDM may be applied differently depending on the type of PUSCH transmission.
[0249] For example, types of PUSCH transmission include a PUSCH dynamically scheduled by DCI format 0-0, a PUSCH dynamically scheduled by DCI format 0-1 or DCI format 0-2 when transformPrecoder is set by RRC, a PUSCH dynamically scheduled by DCI format 0-1 or DCI format 0-2 when transformPrecoder is not set by RRC, a CG-PUSCH when transformPrecoder is set by RRC, and a CG-PUSCH when transformPrecoder is not set by RRC.
[0250] For example, a quasi-static transmission waveform determination method similar to existing NR may be applied to a PUSCH dynamically scheduled by DCI format 0-0. Also, for example, the above-described embodiment, modification, or another transmission waveform determination method may be applied to a PUSCH dynamically scheduled by DCI format 0-1 or DCI format 0-2 when transformPrecoder is not configured by RRC.
[0251] (2) The above-described embodiments, modifications, other transmission waveform determination methods, and quasi-static transmission waveform determination methods similar to existing NR (e.g., a method of transmitting a PUSCH by applying a transmission waveform quasi-statically set by transformPrecoder or msg3-transformPrecoder) may be applied differently to a terrestrial network (TN) and a non-terrestrial network (NTN).
[0252] For example, the above-mentioned embodiments, variations, or other transmission waveform determination methods may be applied to NTNs where coverage expansion is expected, and a quasi-static transmission waveform determination method similar to that of existing NRs may be applied to TNs.
[0253] Furthermore, for example, the above-described embodiment, modification, or other transmit waveform determination method may be applied to both the TN and the NTN, and the conditions for switching the transmit waveform to DFT-s-OFDM may be different between the TN and the NTN. For example, the number of conditions for switching the transmit waveform to DFT-s-OFDM (e.g., the number of conditions to be applied out of the above-described four conditions, or the above-described value of M) may be different between the TN and the NTN.
[0254] (3) The above-described embodiments, modifications, other transmission waveform determination methods, and quasi-static transmission waveform determination methods similar to existing NR (e.g., a method of transmitting a PUSCH by applying a transmission waveform that is quasi-statically set by transformPrecoder or msg3-transformPrecoder) may be applied differently depending on the frequency range.
[0255] For example, the above-described embodiment, variant, or other transmission waveform determination method may be applied to FR2, where coverage expansion is expected, and a quasi-static transmission waveform determination method similar to that of the existing NR may be applied to FR1.
[0256] Furthermore, for example, the above-described embodiment, modification, or other transmit waveform determination method may be applied to both FR1 and FR2, and the conditions for switching the transmit waveform to DFT-s-OFDM may be different between FR1 and FR2. For example, the number of conditions for switching the transmit waveform to DFT-s-OFDM (e.g., the number of conditions to be applied out of the above-described four conditions, or the above-described value of M) may be different between FR1 and FR2.
[0257] (4) The above-described embodiments, modifications, other transmission waveform determination methods, and quasi-static transmission waveform determination methods similar to existing NR (e.g., a method of transmitting a PUSCH by applying a transmission waveform quasi-statically set by transformPrecoder or msg3-transformPrecoder) may be applied differently to communication between a base station and a terminal (Uu) and communication between terminals (Sidelink communication).
[0258] For example, the above-mentioned embodiment, variant example, or other transmission waveform determination method may be applied to Uu where coverage expansion is expected, and a quasi-static transmission waveform determination method similar to existing NR may be applied to Sidelink.
[0259] Furthermore, for example, the above-described embodiment, modification, or other transmit waveform determination method may be applied to both Uu and Sidelink, and the conditions for switching the transmit waveform to DFT-s-OFDM may be different between Uu and Sidelink. For example, the number of conditions for switching the transmit waveform to DFT-s-OFDM (e.g., the number of conditions to be applied out of the above-described four conditions, or the above-described value of M) may be different between Uu and Sidelink.
[0260] (5) The above-described embodiments, variants, other transmission waveform determination methods, and quasi-static transmission waveform determination methods similar to existing NR (for example, a method of transmitting a PUSCH by applying a transmission waveform quasi-statically set by transformPrecoder or msg3-transformPrecoder) may be applied differently between licensed band operation and unlicensed band operation.
[0261] For example, the above-described embodiment, modification, or other transmission waveform determination method may be applied to both the licensed band and the unlicensed band, and the conditions for switching the transmission waveform to DFT-s-OFDM may be different between the licensed band and the unlicensed band. For example, the number of conditions for switching the transmission waveform to DFT-s-OFDM (e.g., the number of conditions to be applied out of the above-described four conditions, or the above-described value of M) may be different between the licensed band and the unlicensed band.
[0262] (6) The above-described embodiments, modifications, other transmission waveform determination methods, and quasi-static transmission waveform determination methods similar to existing NR (for example, a method of transmitting a PUSCH by applying a transmission waveform quasi-statically set by transformPrecoder or msg3-transformPrecoder) may be applied differently to terminals that achieve low cost, such as RedCap (Reduced Capability terminal), and to normal terminals.
[0263] For example, the above-described embodiment, modification, or other transmission waveform determination method may be applied to both the RedCap terminal and the normal terminal, and the conditions for switching the transmission waveform to DFT-s-OFDM may be different between the RedCap terminal and the normal terminal. For example, the number of conditions for switching the transmission waveform to DFT-s-OFDM (for example, the number of conditions to be applied out of the above-described four conditions, or the above-described value of M) may be different between the RedCap terminal and the normal terminal.
[0264] (7) The above-described embodiments, modifications, and other transmit waveform determination methods are not limited to switching the transmit waveform from CP-OFDM to DFT-s-OFDM. For example, if a transmit waveform with better coverage performance than DFT-s-OFDM is adopted, "CP-OFDM" in the above-described embodiments, modifications, and other transmit waveform determination methods may be replaced with "DFT-s-OFDM," and "DFT-s-OFDM" in the above-described embodiments, modifications, and other transmit waveform determination methods may be replaced with a transmit waveform with better coverage performance than DFT-s-OFDM.
[0265] Furthermore, in each of the above-described embodiments, the transmission waveforms are not limited to the two types of DFT-s-OFDM and CP-OFDM, but may be other transmission waveforms, and the number of applicable transmission waveforms may be three or more.
[0266] (8) In each of the above-described embodiments, the channel used for uplink transmission is not limited to the PUSCH and may be another channel. Furthermore, the type of information to be transmitted is not limited to data and may be another type of information (e.g., an uplink control signal). Furthermore, an embodiment of the present disclosure is not limited to uplink transmission and may be applied to downlink transmission or sidelink transmission.
[0267] The present disclosure may be applied to communication between terminals, such as sidelink communication, for example.
[0268] Furthermore, in the present disclosure, the downlink control channel, downlink data channel, uplink control channel, and uplink data channel are not limited to PDCCH, PDSCH, PUCCH, and PUSCH, respectively, and may be control channels with other names.
[0269] Furthermore, in the present disclosure, RRC signaling is assumed as higher layer signaling, but it may be replaced with Medium Access Control (MAC) signaling and notification by DCI, which is physical layer signaling.
[0270] (Supplementary Note) Information indicating whether the terminal 200 supports the functions, operations, or processes described in each of the above-described embodiments and each supplementary note may be transmitted (or notified) from the terminal 200 to the base station 100, for example, as capability information or capability parameters of the terminal 200.
[0271] The capability information may include an information element (IE) that individually indicates whether or not the terminal 200 supports at least one of the functions, operations, or processes described in the above-described embodiments, modifications, and supplements. Alternatively, the capability information may include an information element that indicates whether or not the terminal 200 supports a combination of any two or more of the functions, operations, or processes described in the above-described embodiments, modifications, and supplements.
[0272] For example, the base station 100 may determine (or decide or assume) the functions, operations, or processes that the terminal 200 that transmitted the capability information supports (or does not support) based on the capability information received from the terminal 200. The base station 100 may perform operations, processes, or controls according to the determination result based on the capability information. For example, the base station 100 may control uplink-related processing based on the capability information received from the terminal 200.
[0273] Note that the fact that terminal 200 does not support some of the functions, operations, or processes described in the above-described embodiments, modifications, and supplementary notes may be interpreted as meaning that such some of the functions, operations, or processes are restricted in terminal 200. For example, information or a request regarding such restrictions may be notified to base station 100.
[0274] Information regarding the capabilities or limitations of terminal 200 may, for example, be defined in a standard, or may be implicitly notified to base station 100 in association with information known at base station 100 or information transmitted to base station 100.
[0275] The above has described the embodiments, modifications, and supplementary notes according to a non-limiting example of the present disclosure.
[0276] (Control Signal) In the present disclosure, a downlink control signal (information) related to the present disclosure may be a signal (information) transmitted by a PDCCH of a physical layer, or may be a signal (information) transmitted by a MAC CE (Control Element) or RRC of a higher layer. Also, the downlink control signal may be a signal (information) that is specified in advance.
[0277] The uplink control signal (information) related to the present disclosure may be a signal (information) transmitted on a PUCCH in the physical layer, or a signal (information) transmitted on a MAC CE or RRC in a higher layer. The uplink control signal may also be a predefined signal (information). The uplink control signal may also be replaced with uplink control information (UCI), 1st stage sidelink control information (SCI), or 2nd stage SCI.
[0278] (Base Station) In the present disclosure, a base station may be a TRP (Transmission Reception Point), a cluster head, an access point, an RRH (Remote Radio Head), an eNodeB (eNB), a gNodeB (gNB), a BS (Base Station), a BTS (Base Transceiver Station), a parent device, a gateway, or the like. In sidelink communication, the base station may be replaced with a terminal. The base station may be a relay device that relays communication between an upper node and a terminal. The base station may be a roadside unit.
[0279] (Uplink / Downlink / Sidelink) The present disclosure may be applied to any of the uplink, downlink, and sidelink. For example, the present disclosure may be applied to the uplink PUSCH, PUCCH, and PRACH, the downlink PDSCH, PDCCH, and PBCH, and the sidelink PSSCH (Physical Sidelink Shared Channel), PSCCH (Physical Sidelink Control Channel), and PSBCH (Physical Sidelink Broadcast Channel).
[0280] The PDCCH, PDSCH, PUSCH, and PUCCH are examples of a downlink control channel, a downlink data channel, an uplink data channel, and an uplink control channel. The PSCCH and PSSCH are examples of a sidelink control channel and a sidelink data channel. The PBCH and PSBCH are examples of broadcast channels, and the PRACH is an example of a random access channel.
[0281] (Data Channel / Control Channel) The present disclosure may be applied to either a data channel or a control channel. For example, the channels of the present disclosure may be replaced with data channels such as PDSCH, PUSCH, and PSSCH, and control channels such as PDCCH, PUCCH, PBCH, PSCCH, and PSBCH.
[0282] (Reference Signal) In the present disclosure, a reference signal is a signal known by both a base station and a terminal, and may also be referred to as an RS (Reference Signal) or a pilot signal. The reference signal may be any of DMRS, CSI-RS (Channel State Information - Reference Signal), TRS (Tracking Reference Signal), PTRS (Phase Tracking Reference Signal), CRS (Cell-specific Reference Signal), and SRS (Sounding Reference Signal).
[0283] (Time Interval) In the present disclosure, the unit of time resource is not limited to one or a combination of slots and symbols, but may be, for example, a time resource unit such as a frame, a superframe, a subframe, a slot, a time slot, a subslot, a minislot, a symbol, an OFDM (Orthogonal Frequency Division Multiplexing Access) symbol, or an SC-FDMA (Single Carrier-Frequency Division Multiple Access) symbol, or another time resource unit. Furthermore, the number of symbols included in one slot is not limited to the number of symbols exemplified in the above-mentioned embodiment, and may be another number of symbols.
[0284] (Frequency Band) The present disclosure may be applied to either a licensed band or an unlicensed band.
[0285] (Communication) The present disclosure may be applied to communication between a base station and a terminal (Uu link communication), communication between terminals (Sidelink communication), and V2X (Vehicle to Everything) communication. For example, the channels of the present disclosure may be replaced with PSCCH, PSSCH, PSFCH (Physical Sidelink Feedback Channel), PSBCH, PDCCH, PUCCH, PDSCH, PUSCH, or PBCH.
[0286] The present disclosure may be applied to a terrestrial network, a non-terrestrial network (NTN) using satellites or highly advanced pseudo satellites (HAPS), or a terrestrial network in which the transmission delay is large compared to the symbol length or slot length, such as a network with a large cell size or an ultra-wideband transmission network.
[0287] (Antenna Port) An antenna port refers to a logical antenna (antenna group) consisting of one or more physical antennas. In other words, an antenna port does not necessarily refer to a single physical antenna, but may refer to an array antenna consisting of multiple antennas, etc. For example, the number of physical antennas an antenna port is composed of is not specified, and it is specified as the smallest unit by which a terminal can transmit a reference signal. In addition, an antenna port may also be specified as the smallest unit by which a weighting of a precoding vector is multiplied.
[0288] 5G NR System Architecture and Protocol Stack 3GPP continues work on the next release of fifth-generation cellular technology (also referred to simply as "5G"), which includes the development of new radio access technology (NR) operating in the frequency range up to 100 GHz. The first version of the 5G standard was completed at the end of 2017, allowing for the prototyping and commercial deployment of 5G NR-compliant devices (e.g., smartphones).
[0289] For example, the system architecture generally assumes a Next Generation - Radio Access Network (NG-RAN) comprising gNBs. The gNBs provide UE-side termination of the NG radio access user plane (SDAP / PDCP / RLC / MAC / PHY) and control plane (RRC) protocols. The gNBs are connected to each other via an Xn interface. The gNBs are also connected to a Next Generation Core (NGC) via a Next Generation (NG) interface, more specifically to an Access and Mobility Management Function (AMF) (e.g., a specific core entity performing AMF) via an NG-C interface, and to a User Plane Function (UPF) (e.g., a specific core entity performing UPF) via an NG-U interface. The NG-RAN architecture is shown in Figure 8 (see, for example, 3GPP TS 38.300 v15.6.0, section 4).
[0290] The NR user plane protocol stack (see, for example, 3GPP TS 38.300, section 4.4.1) includes a Packet Data Convergence Protocol (PDCP) sublayer (see Section 6.4 of TS 38.300), a Radio Link Control (RLC) sublayer (see Section 6.3 of TS 38.300), and a Medium Access Control (MAC) sublayer (see Section 6.2 of TS 38.300), which are terminated on the network side in the gNB. A new Access Stratum (AS) sublayer (Service Data Adaptation Protocol (SDAP)) has also been introduced above PDCP (see, for example, Section 6.5 of 3GPP TS 38.300). A control plane protocol stack has also been defined for the NR (see, for example, Section 4.4.2 of TS 38.300). An overview of Layer 2 functions is provided in Section 6 of TS 38.300. The functions of the PDCP sublayer, RLC sublayer, and MAC sublayer are listed in clauses 6.4, 6.3, and 6.2 of TS 38.300, respectively. The functions of the RRC layer are listed in clause 7 of TS 38.300.
[0291] For example, the Medium-Access-Control layer handles logical channel multiplexing and scheduling and scheduling-related functions, including handling various numerologies.
[0292] For example, the physical layer (PHY) is responsible for coding, PHY HARQ processing, modulation, multi-antenna processing, and mapping of signals to appropriate physical time-frequency resources. The physical layer also handles mapping of transport channels to physical channels. The physical layer provides services to the MAC layer in the form of transport channels. A physical channel corresponds to a set of time-frequency resources used for transmitting a specific transport channel, and each transport channel is mapped to a corresponding physical channel. For example, physical channels include the Physical Random Access Channel (PRACH), the Physical Uplink Shared Channel (PUSCH), and the Physical Uplink Control Channel (PUCCH) as uplink physical channels, and the Physical Downlink Shared Channel (PDSCH), the Physical Downlink Control Channel (PDCCH), and the Physical Broadcast Channel (PBCH) as downlink physical channels.
[0293] NR use cases / deployment scenarios may include enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communication (mMTC), which have diverse requirements in terms of data rate, latency, and coverage. For example, eMBB is expected to support peak data rates (20 Gbps in the downlink and 10 Gbps in the uplink) and effective (user-experienced) data rates approximately three times higher than those offered by IMT-Advanced. On the other hand, URLLC imposes stricter requirements on ultra-low latency (0.5 ms for user plane latency in both UL and DL) and high reliability (1-10-5 within 1 ms). Finally, mMTC preferably requires high connection density (1,000,000 devices / km in urban environments).2 ), wide coverage in adverse environments, and extremely long battery life (15 years) for a low-cost device may be desired.
[0294] Therefore, OFDM numerology (e.g., subcarrier spacing, OFDM symbol length, cyclic prefix (CP) length, number of symbols per scheduling interval) suitable for one use case may not be valid for another use case. For example, low-latency services may preferably require a shorter symbol length (and therefore a larger subcarrier spacing) and / or fewer symbols per scheduling interval (also referred to as TTI) than mMTC services. Furthermore, deployment scenarios with large channel delay spreads may preferably require a longer CP length than scenarios with short delay spreads. The subcarrier spacing may be optimized accordingly to maintain similar CP overhead. NR may support one or more subcarrier spacing values. Correspondingly, subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, etc. are currently considered. The symbol length Tu and subcarrier spacing Δf are directly related by the formula Δf = 1 / Tu. Similar to LTE systems, the term "resource element" can be used to mean the smallest resource unit consisting of one subcarrier for the length of one OFDM / SC-FDMA symbol.
[0295] In the new radio system 5G-NR, for each numerology and each carrier, a resource grid of subcarriers and OFDM symbols is defined for each uplink and downlink. Each element of the resource grid is called a resource element and is specified based on a frequency index in the frequency domain and a symbol position in the time domain (see 3GPP TS 38.211 v15.6.0).
[0296] <Functional Separation Between NG-RAN and 5GC in 5G NR> Figure 9 shows the functional separation between NG-RAN and 5GC. The logical node of NG-RAN is gNB or ng-eNB. 5GC has logical nodes AMF, UPF, and SMF.
[0297] For example, gNB and ng-eNB host the following main functions: - Radio Resource Management functions such as Radio Bearer Control, Radio Admission Control, Connection Mobility Control, dynamic allocation (scheduling) of resources to UEs in both uplink and downlink; - IP header compression, ciphering and integrity protection of data; - AMF selection at UE attach time if routing to the AMF cannot be determined from the information provided by the UE; - Routing of user plane data towards the UPF; - Routing of control plane information towards the AMF; - Connection setup and release; - Scheduling and transmission of paging messages; - Scheduling and transmission of system broadcast information (sourced from the AMF or Operation, Admission, Maintenance (OAM)); - Configuration of measurements and measurement reports for mobility and scheduling; - Transport level packet marking in the uplink; - Session management; Support for network slicing; - QoS flow management and mapping to data radio bearers; - Support for UEs in RRC_INACTIVE state; - NAS message delivery function; - Radio access network sharing; - Dual connectivity; - Close coordination between NR and E-UTRA.
[0298] The Access and Mobility Management Function (AMF) hosts the following main functions: - Termination of Non-Access Stratum (NAS) signaling; - Security of NAS signaling; - Security control of Access Stratum (AS); - Signaling between Core Network (CN) nodes for mobility between 3GPP access networks; - Reachability to idle mode UEs (including control and execution of paging retransmissions); - Registration area management; - Support for intra-system and inter-system mobility; - Access authentication; - Access authorization including checking of roaming rights; - Mobility management control (subscription and policy); - Support for network slicing; - Selection of Session Management Function (SMF).
[0299] Furthermore, the User Plane Function (UPF) hosts the following main functions: - anchor point for intra-RAT / inter-RAT mobility (if applicable); - external PDU (Protocol Data Unit) session point for interconnection with data networks; - packet routing and forwarding; - packet inspection and policy rule enforcement for the user plane part; - traffic usage reporting; - uplink classifier to support routing of traffic flows to the data network; - branching point to support multi-homed PDU sessions; - QoS processing for the user plane (e.g. packet filtering, gating, UL / DL rate enforcement); - uplink traffic validation (mapping of SDF to QoS flows); - downlink packet buffering and triggering of downlink data notifications.
[0300] Finally, the Session Management Function (SMF) hosts the following main functions: session management; allocation and management of IP addresses for UEs; selection and control of UPF; configuration of traffic steering in the User Plane Function (UPF) to route traffic to the appropriate destination; policy enforcement and QoS of the control part; downlink data notification.
[0301] <RRC connection setup and reconfiguration procedure> Figure 10 shows some of the interactions between the UE, gNB, and AMF (5GC entities) when the UE transitions from RRC_IDLE to RRC_CONNECTED in the NAS part (see TS 38.300 v15.6.0).
[0302] RRC is a higher layer signaling (protocol) used to configure the UE and gNB. With this transition, the AMF prepares UE context data (including, for example, PDU session context, security keys, UE radio capabilities, UE security capabilities, etc.) and sends it to the gNB along with an INITIAL CONTEXT SETUP REQUEST. The gNB then activates AS security together with the UE. This is done by the gNB sending a SecurityModeCommand message to the UE, and the UE responding with a SecurityModeComplete message to the gNB. The gNB then sends an RRCReconfiguration message to the UE, and upon receiving an RRCReconfigurationComplete from the UE, the gNB performs reconfiguration to set up Signaling Radio Bearer 2 (SRB2) and Data Radio Bearer (DRB). For signaling-only connections, the steps related to RRCReconfiguration are omitted because SRB2 and DRB are not set up. Finally, the gNB notifies the AMF that the setup procedure is complete with an INITIAL CONTEXT SETUP RESPONSE.
[0303] Therefore, the present disclosure provides a 5th Generation Core (5GC) entity (e.g., AMF, SMF, etc.) that includes: a control circuit that, upon operation, establishes a Next Generation (NG) connection with a gNodeB; and a transmitter that, upon operation, transmits an initial context setup message to the gNodeB via the NG connection so that a signaling radio bearer between the gNodeB and a user equipment (UE) is set up. Specifically, the gNodeB transmits Radio Resource Control (RRC) signaling, including a resource allocation configuration information element (IE), to the UE via the signaling radio bearer. The UE then transmits in uplink or receives in downlink based on the resource allocation configuration.
[0304] <IMT Usage Scenarios Beyond 2020> Figure 11 shows some use cases for 5G NR. The 3rd Generation Partnership Project New Radio (3GPP NR) is considering three use cases envisioned by IMT-2020 to support a wide variety of services and applications. The first phase of specifications for enhanced mobile broadband (eMBB) has been completed. Current and future work includes standardization for ultra-reliable and low-latency communications (URLLC) and massive machine-type communications (mMTC), in addition to expanding support for eMBB. Figure 11 shows some examples of envisioned usage scenarios for IMT beyond 2020 (see, for example, ITU-R M.2083 Figure 2).
[0305] The URLLC use case has stringent performance requirements, such as throughput, latency, and availability. It is envisioned as one of the enabling technologies for future applications, such as wireless control of industrial production or manufacturing processes, remote medical surgery, automated power transmission and distribution in smart grids, and road safety. URLLC's ultra-high reliability is supported by identifying technologies that meet the requirements set by TR 38.913. Key requirements for NR URLLC in Release 15 include a target user plane latency of 0.5 ms on the uplink (UL) and 0.5 ms on the downlink (DL). The overall URLLC requirement for a single packet transmission is a block error rate (BLER) of 1E-5 for a 32-byte packet size with a user plane latency of 1 ms.
[0306] From a physical layer perspective, reliability can be improved in many possible ways. Current room for reliability improvement includes defining a separate CQI table for URLLC, more compact DCI formats, PDCCH repetition, etc. However, this room can be expanded to achieve ultra-high reliability as NR (with respect to the key requirements of NR URLLC) becomes more stable and developed. Specific use cases for NR URLLC in Release 15 include Augmented Reality / Virtual Reality (AR / VR), e-health, e-safety, and mission-critical applications.
[0307] Additionally, the technology enhancements targeted by NR URLLC aim to improve latency and reliability. Technology enhancements for latency improvement include configurable numerology, non-slot-based scheduling with flexible mapping, grant-free (configured grant) uplink, slot-level repetition in the data channel, and preemption in the downlink. Preemption means that a transmission with already allocated resources is stopped and the already allocated resources are used for another transmission with a later requested lower latency / higher priority. Therefore, a previously allowed transmission is preempted by a later transmission. Preemption is applicable regardless of the specific service type. For example, a transmission of service type A (URLLC) may be preempted by a transmission of service type B (eMBB, etc.). Technology enhancements for reliability improvement include a dedicated CQI / MCS table for a target BLER of 1E-5.
[0308] The use case of mMTC (massive machine type communication) is characterized by a very large number of connected devices that typically transmit relatively small amounts of data that are not sensitive to delays. These devices are required to be low-cost and have very long battery life. From the NR perspective, utilizing very narrow bandwidth portions is one solution that saves power and extends battery life from the UE's perspective.
[0309] As mentioned above, the scope of reliability improvement in NR is expected to be broader. One of the key requirements for all cases, for example, URLLC and mMTC, is high or ultra-high reliability. Several mechanisms can improve reliability from a radio perspective and a network perspective. Generally, there are two to three key areas that can help improve reliability. These areas include compact control channel information, repetition of data channels / control channels, and diversity in the frequency, time, and / or spatial domains. These areas are generally applicable to reliability improvement regardless of the specific communication scenario.
[0310] For NR URLLC, further use cases with more stringent requirements are envisaged, such as factory automation, transportation, and power distribution, with high reliability (up to 10-6 level reliability), high availability, packet size up to 256 bytes, time synchronization up to a few μs (depending on the use case, the value can be 1 μs or a few μs depending on the frequency range and low latency in the order of 0.5 ms to 1 ms (e.g., 0.5 ms latency on the targeted user plane)).
[0311] Furthermore, for NR URLLC, there may be several technical enhancements from the physical layer perspective. These technical enhancements include PDCCH (Physical Downlink Control Channel) enhancements for compact DCI, PDCCH repetition, and increased PDCCH monitoring. Also, UCI (Uplink Control Information) enhancements relate to enhanced Hybrid Automatic Repeat Request (HARQ) and CSI feedback enhancements. There may also be PUSCH enhancements related to minislot-level hopping and retransmission / repetition enhancements. The term "minislot" refers to a Transmission Time Interval (TTI) that contains fewer symbols than a slot (a slot comprises 14 symbols).
[0312] <QoS Control> The 5G Quality of Service (QoS) model is based on QoS flows and supports both QoS flows that require a guaranteed flow bit rate (Guaranteed Bit Rate QoS flows (GBR)) and QoS flows that do not require a guaranteed flow bit rate (non-GBR QoS flows). Thus, at the NAS level, a QoS flow is the finest granularity of QoS classification in a PDU session. A QoS flow is identified within a PDU session by a QoS Flow ID (QFI) carried in an encapsulation header over the NG-U interface.
[0313] For each UE, 5GC establishes one or more PDU sessions. For each UE, the NG-RAN establishes at least one Data Radio Bearer (DRB) for each PDU session, e.g., as shown above with reference to FIG. 10. Additional DRBs for the QoS flows of that PDU session can be configured later (when this is up to the NG-RAN). The NG-RAN maps packets belonging to different PDU sessions to different DRBs. NAS-level packet filters in the UE and 5GC associate UL and DL packets with QoS flows, while AS-level mapping rules in the UE and NG-RAN associate UL and DL QoS flows with DRBs.
[0314] Figure 12 shows the non-roaming reference architecture for 5G NR (see TS 23.501 v16.1.0, section 4.23). An Application Function (AF) (e.g., an external application server hosting 5G services, as illustrated in Figure 11) interacts with the 3GPP core network to provide services. For example, it may access a Network Exposure Function (NEF) to support applications that affect traffic routing, or interact with a policy framework for policy control (e.g., QoS control) (see Policy Control Function (PCF)). Based on operator deployment, Application Functions considered trusted by the operator can interact directly with the associated Network Functions. Application Functions not permitted by the operator to directly access Network Functions interact with the associated Network Functions using an external exposure framework via the NEF.
[0315] Figure 12 further illustrates further functional units of the 5G architecture, namely, Network Slice Selection Function (NSSF), Network Repository Function (NRF), Unified Data Management (UDM), Authentication Server Function (AUSF), Access and Mobility Management Function (AMF), Session Management Function (SMF), and Data Network (DN, e.g., operator-provided services, Internet access, or third-party services). All or part of the core network functions and application services may be deployed and run in a cloud computing environment.
[0316] Therefore, the present disclosure provides an application server (e.g., an AF in a 5G architecture) comprising: a transmitter that, in operation, sends a request including QoS requirements for at least one of a URLLC service, an eMMB service, and an mMTC service to at least one of 5GC functions (e.g., an NEF, an AMF, an SMF, a PCF, an UPF, etc.) to establish a PDU session including a radio bearer between a gNodeB and a UE according to the QoS requirements; and a control circuit that, in operation, performs a service using the established PDU session.
[0317] The term "portion" used in this disclosure may be interchangeably used with other terms such as "circuitry," "device," "unit," or "module."
[0318] The present disclosure can be realized by software, hardware, or software in conjunction with hardware. Each functional block used in the description of the above embodiments may be partially or entirely realized as an LSI, which is an integrated circuit, and each process described in the above embodiments may be partially or entirely controlled by a single LSI or a combination of LSIs. The LSI may be composed of individual chips, or may be composed of a single chip that includes some or all of the functional blocks. The LSI may have data input and output. Depending on the degree of integration, the LSI may also be called an IC, system LSI, super LSI, or ultra LSI.
[0319] The integrated circuit method is not limited to LSI, and may be realized by a dedicated circuit, a general-purpose processor, or a dedicated processor. Also, a field programmable gate array (FPGA) that can be programmed after LSI manufacturing, or a reconfigurable processor that can reconfigure the connections and settings of circuit cells within the LSI, may be used. The present disclosure may be realized as digital processing or analog processing.
[0320] Furthermore, if an integrated circuit technology that can replace LSI emerges due to advances in semiconductor technology or other derivative technologies, it is natural that such technology may be used to integrate functional blocks. The application of biotechnology, etc. is also a possibility.
[0321] The present disclosure can be implemented in any type of apparatus, device, or system (collectively referred to as a communication apparatus) having a communication function. The communication apparatus may include a radio transceiver and processing / control circuitry. The radio transceiver may include a receiver and a transmitter, or both as functions. The radio transceiver (transmitter and receiver) may include a radio frequency (RF) module and one or more antennas. The RF module may include an amplifier, an RF modulator / demodulator, or the like. Non-limiting examples of communication devices include telephones (e.g., cell phones, smartphones), tablets, personal computers (PCs) (e.g., laptops, desktops, notebooks), cameras (e.g., digital still / video cameras), digital players (e.g., digital audio / video players), wearable devices (e.g., wearable cameras, smartwatches, tracking devices), game consoles, digital book readers, telehealth / telemedicine devices, communication-enabled vehicles or mobile transportation (e.g., cars, airplanes, ships), and combinations of the above devices.
[0322] The communication devices are not limited to portable or mobile devices, but also include any kind of non-portable or fixed equipment, devices, and systems, such as smart home devices (such as home appliances, lighting equipment, smart meters or measuring devices, control panels, etc.), vending machines, and any other "things" that may exist on an IoT (Internet of Things) network.
[0323] Communications include data communications via cellular systems, wireless LAN systems, communication satellite systems, and the like, as well as data communications via combinations of these.
[0324] A communications apparatus also includes devices such as controllers and sensors connected or coupled to a communications device that performs the communications functions described in this disclosure, such as controllers and sensors that generate control and data signals used by the communications device to perform the communications functions of the communications apparatus.
[0325] The communication apparatus also includes infrastructure facilities, such as base stations, access points, and any other apparatus, device, or system that communicates with or controls the various apparatuses listed above, but are not limited to these.
[0326] A terminal according to one embodiment of the present disclosure includes a control circuit that switches the transmission waveform of an uplink signal to a first transmission waveform when conditions related to parameters and settings for transmitting the uplink signal are met, and a transmission circuit that transmits the uplink signal using the first transmission waveform.
[0327] In one embodiment of the present disclosure, the parameters and the settings include at least one of information regarding repeated transmission of the uplink signal, information regarding the number of transmission layers of the uplink signal, information regarding frequency domain resource allocation of the uplink signal, and information regarding the setting of a demodulation reference signal for the uplink signal.
[0328] In one embodiment of the present disclosure, the control circuit determines to switch to the first transmission waveform when the repetitive transmission is applied to the uplink signal.
[0329] In an embodiment of the present disclosure, the control circuit determines to switch to the first transmission waveform when the number of repeated transmissions of the uplink signal is equal to or greater than a threshold value.
[0330] In one embodiment of the present disclosure, the control circuit determines to switch to the first transmission waveform when the transmission of the uplink signal is one-layer transmission.
[0331] In an embodiment of the present disclosure, the control circuit determines to switch to the first transmission waveform when the number of transmission layers of the uplink signal is equal to or less than a threshold.
[0332] In one embodiment of the present disclosure, the control circuit determines to switch to the first transmission waveform when the type of the frequency domain resource allocation of the uplink signal is allocation of consecutive resource blocks.
[0333] In an embodiment of the present disclosure, the control circuit determines to switch to the first transmission waveform when the number of allocated resource blocks in the frequency domain resource allocation of the uplink signal is equal to or less than a threshold.
[0334] In an embodiment of the present disclosure, the control circuit determines to switch to the first transmission waveform when the type of the demodulation reference signal setting for the uplink signal is a specified type.
[0335] In an embodiment of the present disclosure, the control circuit determines to switch to the first transmission waveform when the number of symbols of an additional demodulation reference signal in the setting of the demodulation reference signal of the uplink signal is equal to or greater than a threshold.
[0336] In one embodiment of the present disclosure, when the transmission waveform of the uplink signal is set to a second transmission waveform by an upper layer parameter, the control circuit determines to switch to the first transmission waveform based on the condition.
[0337] In one embodiment of the present disclosure, when a first upper layer parameter is set and a second upper layer parameter is not set, the control circuit determines to switch to the first transmission waveform based on the condition, and when the second upper layer parameter is set, determines the transmission waveform based on the second upper layer parameter.
[0338] In one embodiment of the present disclosure, the uplink signal includes a first signal in a random access procedure and a second signal after the random access procedure, and when the control circuit determines the transmission waveform of the first signal to be the first transmission waveform while ignoring the setting of a first upper layer parameter, it determines to switch to the first transmission waveform for the second signal based on the condition.
[0339] In one embodiment of the present disclosure, when the transmission waveform of the first signal is set to the first transmission waveform ignoring the setting of a first upper layer parameter and a second upper layer parameter is not set, the control circuit determines to switch to the first transmission waveform for the second signal based on the condition.
[0340] A base station according to one embodiment of the present disclosure includes a control circuit that switches the transmission waveform of an uplink signal to a first transmission waveform when conditions related to parameters and settings for transmitting the uplink signal are met, and a receiving circuit that receives the uplink signal using the first transmission waveform.
[0341] In a communication method according to one embodiment of the present disclosure, a terminal switches the transmission waveform of an uplink signal to a first transmission waveform when conditions related to parameters and settings for transmitting the uplink signal are met, and transmits the uplink signal using the first transmission waveform.
[0342] In a communication method according to one embodiment of the present disclosure, a base station switches the transmission waveform of an uplink signal to a first transmission waveform when conditions related to parameters and settings for transmitting the uplink signal are met, and receives the uplink signal using the first transmission waveform.
[0343] One embodiment of the present disclosure is useful in wireless communication systems.
[0344] 100 Base station 101, 205 Control unit 102 Upper control signal generation unit 103 Downlink control information generation unit 104, 206 Encoding unit 105, 207 Modulation unit 106, 208 Signal allocation unit 107, 209 Transmission unit 108, 201 Reception unit 109, 202 Extraction unit 110, 203 Demodulation unit 111, 204 Decoding unit 200 Terminal
Claims
1. A terminal comprising: a control circuit that switches the transmission waveform of an uplink signal to a first transmission waveform when conditions related to parameters and settings for transmitting the uplink signal are satisfied; and a transmission circuit that transmits the uplink signal using the first transmission waveform.
2. The terminal according to claim 1, wherein the parameters and the settings include at least one of information regarding repeated transmission of the uplink signal, information regarding the number of transmission layers of the uplink signal, information regarding frequency domain resource allocation of the uplink signal, and information regarding settings of a demodulation reference signal for the uplink signal.
3. The terminal according to claim 2, wherein the control circuit determines to switch to the first transmission waveform when the repetitive transmission is applied to the uplink signal.
4. The terminal according to claim 2, wherein the control circuit decides to switch to the first transmission waveform when the number of repeated transmissions of the upstream signal is equal to or greater than a threshold value.
5. The terminal according to claim 2, wherein the control circuit determines to switch to the first transmission waveform when the transmission of the uplink signal is one-layer transmission.
6. The terminal according to claim 2, wherein the control circuit determines to switch to the first transmission waveform when the number of transmission layers of the uplink signal is equal to or less than a threshold value.
7. The terminal according to claim 2, wherein the control circuit determines to switch to the first transmission waveform when the type of the frequency domain resource allocation of the uplink signal is an allocation of consecutive resource blocks.
8. The terminal according to claim 2, wherein the control circuit determines to switch to the first transmission waveform when a number of allocated resource blocks in the frequency domain resource allocation of the uplink signal is equal to or smaller than a threshold.
9. The terminal according to claim 2, wherein the control circuit determines to switch to the first transmission waveform when the type of the demodulation reference signal set for the uplink signal is a specified type.
10. The terminal according to claim 2, wherein the control circuit decides to switch to the first transmission waveform when the number of symbols of an additional demodulation reference signal in the setting of the demodulation reference signal of the uplink signal is equal to or greater than a threshold value.
11. The terminal according to claim 1, wherein the control circuit determines to switch to the first transmission waveform based on the condition when the transmission waveform of the uplink signal is set to a second transmission waveform by an upper layer parameter.
12. The terminal according to claim 11, wherein the control circuit determines to switch to the first transmission waveform based on the condition when a first upper layer parameter is set and a second upper layer parameter is not set, and determines a transmission waveform based on the second upper layer parameter when the second upper layer parameter is set.
13. The terminal of claim 1, wherein the uplink signal includes a first signal in a random access procedure and a second signal after the random access procedure, and when the control circuit determines the transmission waveform of the first signal to be the first transmission waveform ignoring the setting of a first upper layer parameter, it determines to switch to the first transmission waveform for the second signal based on the condition.
14. The terminal according to claim 13, wherein the control circuit determines, based on the condition, to switch to the first transmission waveform for the second signal when the transmission waveform of the first signal is set to the first transmission waveform ignoring the setting of a first upper layer parameter and a second upper layer parameter is not set.
15. A base station comprising: a control circuit that switches the transmission waveform of an uplink signal to a first transmission waveform when conditions related to parameters and settings for transmitting the uplink signal are satisfied; and a receiving circuit that receives the uplink signal using the first transmission waveform.
16. A communications method, in which a terminal switches a transmission waveform of an uplink signal to a first transmission waveform when conditions related to parameters and settings for transmitting the uplink signal are satisfied, and transmits the uplink signal using the first transmission waveform.
17. A communications method, comprising: a base station switching a transmission waveform of an uplink signal to a first transmission waveform when conditions related to parameters and settings for transmitting the uplink signal are satisfied; and receiving the uplink signal using the first transmission waveform.
Citation Information
Patent Citations
Terminal device and base station device
JP2019062344A
User terminal, wireless base station, and wireless communication method
WO2016163502A1
User equipment and radio communication method
WO2019163113A1
Terminal, wireless communication method and base station
WO2023012953A1
