WO2024171433A1 - Équipement utilisateur, procédé de communication sans fil, et station de base - Google Patents

Équipement utilisateur, procédé de communication sans fil, et station de base Download PDF

Info

Publication number
WO2024171433A1
WO2024171433A1 PCT/JP2023/005739 JP2023005739W WO2024171433A1 WO 2024171433 A1 WO2024171433 A1 WO 2024171433A1 JP 2023005739 W JP2023005739 W JP 2023005739W WO 2024171433 A1 WO2024171433 A1 WO 2024171433A1
Authority
WO
WIPO (PCT)
Prior art keywords
pusch
dci
type
dmrs
waveform
Prior art date
Application number
PCT/JP2023/005739
Other languages
English (en)
Japanese (ja)
Inventor
尚哉 芝池
祐輝 松村
聡 永田
Original Assignee
株式会社Ｎｔｔドコモ
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 株式会社Ｎｔｔドコモ filed Critical 株式会社Ｎｔｔドコモ
Priority to PCT/JP2023/005739 priority Critical patent/WO2024171433A1/fr
Publication of WO2024171433A1 publication Critical patent/WO2024171433A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L27/00—Modulated-carrier systems
    • H04L27/26—Systems using multi-frequency codes

Definitions

  • This disclosure relates to terminals, wireless communication methods, and base stations in next-generation mobile communication systems.
  • LTE Long Term Evolution
  • UMTS Universal Mobile Telecommunications System
  • Non-Patent Document 1 LTE-Advanced (3GPP Rel. 10-14) was specified for the purpose of achieving higher capacity and greater sophistication over LTE (Third Generation Partnership Project (3GPP (registered trademark)) Release (Rel.) 8, 9).
  • LTE 5th generation mobile communication system
  • 5G+ 5th generation mobile communication system
  • 6G 6th generation mobile communication system
  • NR New Radio
  • E-UTRA Evolved Universal Terrestrial Radio Access
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • DFT-s-OFDM Discrete Fourier Transform-Spread-Orthogonal Frequency Division Multiplexing
  • CP-OFDM Cyclic Prefix-Orthogonal Frequency Division Multiplexing
  • RRC Radio Resource Control
  • one of the objectives of this disclosure is to provide a terminal, a wireless communication method, and a base station that can appropriately switch waveforms.
  • a terminal has a receiving unit that receives information regarding the type of demodulation reference signal (DMRS) for a physical uplink shared channel (PUSCH), and a control unit that controls to apply a specific DMRS type when dynamic waveform switching for the PUSCH is configured.
  • DMRS demodulation reference signal
  • PUSCH physical uplink shared channel
  • waveform switching can be performed appropriately.
  • FIG. 1 is a diagram showing the DCI size of option 1-1.
  • FIG. 2 is a diagram showing the DCI sizes of options 1-2.
  • FIG. 3 is a flowchart showing an example of a process according to the embodiment 0.1.
  • FIG. 4 is a flowchart showing an example of a process according to embodiment 0.2.
  • Figure 5 shows the definition of the DCI fields PTRS-DMRS association and DMRS sequence initialization.
  • Figure 6 is a diagram showing examples of setting patterns for useInterlacePUCCH-PUSCH, resourceAllocation, and RA type.
  • FIG. 7 is a flowchart illustrating an example of processing according to the third embodiment.
  • FIG. 8 is a diagram illustrating an example of a MAC payload.
  • FIG. 9 is a diagram showing an example of the number of bits in the RAR grant field.
  • FIG. 10 is a diagram showing an example of the values of the TPC command.
  • FIG. 11 is a diagram showing an example of a Backoff Parameter value.
  • FIG. 12 is a diagram illustrating an example of an antenna port field of DCI format 0_1.
  • FIG. 13 is a diagram illustrating an example of a DMRS type setting when dynamic waveform switching is set.
  • 14A and 14B are diagrams showing an example of how to interpret code points in a specific field of DCI when dynamic waveform switching is configured and DMRS type 2 is configured.
  • FIG. 15 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment.
  • FIG. 16 is a diagram illustrating an example of the configuration of a base station according to an embodiment.
  • FIG. 17 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment.
  • FIG. 18 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment.
  • FIG. 19 is a diagram illustrating an example of a vehicle according to an embodiment.
  • CP-OFDM and DFT-s-OFDM In the uplink (UL) of a wireless communication system (for example, NR), in addition to a multicarrier waveform, a Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) waveform, a single carrier waveform, a Discrete Fourier Transform-Spread-Orthogonal Frequency Division Multiplexing (DFT-s-OFDM) waveform is supported.
  • the term "waveform” refers to at least one of a CP-OFDM waveform (a CP-OFDM-based waveform) and a DFT-s-OFDM waveform (a DFT-s-OFDM-based waveform).
  • CP-OFDM allows for more flexible frequency resource allocation. For example, both contiguous and non-contiguous Physical Resource Block (PRB) allocations are permitted. In addition, contiguous PRB allocations are not limited to multiples of 2, 3, or 5.
  • FDM Frequency Division Multiplexing
  • DMRS DeModulation Reference Signal
  • PUSCH PUSCH
  • DFT-s-OFDM (or DFT-S-OFDM/DFTS-OFDM) has significant constraints on frequency resource allocation, but has a low Peak to Average Power Ratio (PAPR) and is suitable for power-limited UEs.
  • PAPR Peak to Average Power Ratio
  • CP-OFDM has a higher communication throughput than DFT-s-OFDM.
  • SNR SNR
  • MCS modulation and coding method
  • CP-OFDM has a higher communication throughput than DFT-s-OFDM, but when the SNR (MCS) is low (modulation and coding method is QPSK), DFT-s-OFDM has a higher communication throughput than CP-OFDM.
  • the preferred waveform differs depending on the SNR (MCS).
  • the network switches the waveform based on the signal-to-noise ratio (SNR).
  • SNR signal-to-noise ratio
  • TransformPrecoder the transform precoder
  • PUSCH Physical Uplink Shared Channel
  • PUSCH-Config Radio Resource Control
  • RRC Radio Resource Control
  • the sizes of some DCI fields in DCI formats are affected by waveform switching, as shown in (1) to (6) below.
  • the DCI size is affected by the transform precoder.
  • the DCI size varies depending on the resource assignment type. Also, the supported resource assignment varies depending on the waveform. CP-OFDM supports resource assignment types 0, 1, and 2, and DFT-s-OFDM supports resource assignment types 1 and 2. (6) In the "Frequency hopping flag" field, the DCI size varies depending on the resource allocation type. As described above, different waveforms support different resource allocations.
  • the UE may receive a setting indicating that the conversion precoder for the PUSCH is dynamically switched between disabled and enabled by the DCI/MAC CE. The UE may then receive an instruction indicating the enablement or disablement of the conversion precoder for the PUSCH by the DCI/MAC CE.
  • dynamic switching by the DCI/MAC CE may simply be referred to as dynamic switching.
  • the UE may be configured in advance by higher layer signaling or the like to dynamically switch (be able to switch) the waveform/conversion precoder. Regardless of the presence or absence of the setting, dynamic switching of the conversion precoder by the DCI/MAC CE may be possible.
  • DCI signaling-based dynamic waveform switching may be performed implicitly or explicitly.
  • a 1-bit field indicating the CP-OFDM or DFT-s-OFDM waveform to be used for the PUSCH may be included in the DCI (explicit signaling).
  • the UE may determine/identify the CP-OFDM or DFT-s-OFDM waveform to be used for the PUSCH depending on specific conditions such as scheduling information in the DCI (implicit signaling). In this case, the existing DCI format is not changed.
  • dynamic UL waveform switching based on MAC CE signaling may be performed.
  • a 1-bit field indicating the CP-OFDM or DFT-s-OFDM waveform to be used for PUSCH may be included in the MAC CE (explicit signaling).
  • the UE may determine/identify the CP-OFDM or DFT-s-OFDM waveform to be used for PUSCH based on an existing field in the MAC CE (implicit signaling).
  • the DCI format in the present disclosure may indicate, for example, DCI format 0_0/0_1/0_2, or may be another format (for example, DCI format 0_3 for notifying waveform switching).
  • a group-common DCI such as DCI format 2_x may be used.
  • waveform switching may be applied a certain time after the UE receives DCI format 2_x and transmits an ACK.
  • the switching between disabling and enabling the transform precoder (waveform switching) in this disclosure may be waveform switching in the same BWP (switching the waveform without switching the BWP). For example, since a different transform precoder can be set for each BWP, it is possible to switch the transform precoder by switching the BWP, but since a delay occurs due to the BWP switching, the delay can be suppressed by switching between disabling and enabling the transform precoder in the same BWP.
  • the UE may receive an instruction from the DCI/MAC CE indicating whether to enable or disable the conversion precoder for PUSCH, and may switch the waveform (CP-OFDM/DFT-s-OFDM) to be used for PUSCH based on the instruction.
  • the waveform CP-OFDM/DFT-s-OFDM
  • the total DCI size of the DCI format may be constant regardless of whether the transform precoder is disabled or enabled.
  • the size of the DCI format may be set/determined by higher layer signaling (RRC). In other words, the size of the DCI format may not depend on the DCI/MAC CE.
  • the size of each DCI field may differ depending on whether the transform precoder is disabled or enabled.
  • the DCI fields are, for example, "Precoding information and number of layers”, “Antenna ports”, “DMRS sequence initialization”, “PTRS-DMRS association”, “Frequency resource assignment”, and “Frequency hopping flag”.
  • the DCI size may differ as shown in (1) to (6) of the existing specifications described above.
  • the total size of the DCI format may be the larger of the size of each DCI format when the transform precoder is disabled and the size of each DCI format when the transform precoder is enabled.
  • the UE may read each DCI field from the least significant bit (LSB) depending on the size of each DCI field. Alternatively, the UE may read each DCI field from the most significant bit (MSB).
  • LSB least significant bit
  • MSB most significant bit
  • Figure 1 shows the DCI size of option 1-1.
  • the number of DCI bits (total of DCIFields #1 to #4) when the transform precoder is disabled is 10 bits
  • the number of DCI bits when the transform precoder is enabled is 7 bits.
  • the larger DCI size, 10 bits is used as the total DCI size when dynamic switching of the transform precoder is set.
  • the smaller DCI bits are mapped from the left (least significant bit) but may also be mapped from the right (most significant bit). That is, the UE may read each DCI field from the least significant bit or from the most significant bit.
  • Option 1-1 allows for a smaller total DCI size compared to option 1-2, which will be described later.
  • the UE may read each DCI field from the least significant bit (LSB) depending on the size of each DCI field. Alternatively, the UE may read each DCI field from the most significant bit (MSB).
  • LSB least significant bit
  • MSB most significant bit
  • Figure 2 shows the DCI size of option 1-2.
  • DCI Field #1 the larger of the DCI field size when the transform precoder is disabled (2 bits) and the DCI field size when the transform precoder is enabled (1 bit) is 2 bits.
  • the smaller DCI bits are mapped starting from the left (least significant bit), but they may also be mapped starting from the right (most significant bit). That is, the UE may read each DCI field starting from the least significant bit, or from the most significant bit.
  • the bit at the start position of each field (the bit range used for each field) is the same whether the transform precoder is disabled or enabled.
  • the start position of DCI Field #1 is the first bit
  • the start position of DCI Field #2 is the third bit
  • the start position of DCI Field #3 is the sixth bit
  • the start position of DCI Field #4 is the eighth bit. This makes it easier for the UE to detect each field.
  • FDRA type Frequency Domain Resource Allocation
  • Type 1 Bitmap based allocation (i.e. may be non-contiguous).
  • Type 1 Contiguous allocation based on Resource Indication Value (RIV).
  • Type 2 Interlaced arrangement (for NR-).
  • Type 0 Applicable to CP-OFDM only.
  • Type 1 Applicable to both CP-OFDM and DFTS-OFDM.
  • Type 2 Applicable to both CP-OFDM and DFTS-OFDM.
  • resourceAllocationType0 or resourceAllocationType1 is used when transmitting type 1 UL data without grant.
  • resourceAllocationType0 is set, type 0 is used, and if resourceAllocationType1 is set, type 1 is used.
  • type 0 or type 1 is indicated by the scheduling DCI (MSB of FDRA). If useInterlacePUCCH-PUSCH is set, type 2 is used.
  • the waveform was set by Radio Resource Control (RRC), so that reconfiguration of RRC was required to switch the waveform. This may increase signaling overhead and reduce communication throughput. Therefore, as described above, the waveform can be easily (fast) switched by dynamically switching the conversion precoder for PUSCH (switching by DCI/MAC CE).
  • RRC Radio Resource Control
  • DCI/MAC CE switching by DCI/MAC CE
  • the inventors therefore came up with the idea of a terminal that dynamically switches between disabling and enabling the conversion precoder for PUSCH (waveform switching).
  • A/B and “at least one of A and B” may be interpreted as interchangeable. Also, in this disclosure, “A/B/C” may mean “at least one of A, B, and C.”
  • Radio Resource Control RRC
  • RRC parameters RRC parameters
  • RRC messages higher layer parameters, fields, information elements (IEs), settings, etc.
  • IEs information elements
  • CE Medium Access Control
  • update commands activation/deactivation commands, etc.
  • higher layer signaling may be, for example, Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, or any combination thereof.
  • RRC Radio Resource Control
  • MAC Medium Access Control
  • the MAC signaling may use, for example, a MAC Control Element (MAC CE), a MAC Protocol Data Unit (PDU), etc.
  • the broadcast information may be, for example, a Master Information Block (MIB), a System Information Block (SIB), Remaining Minimum System Information (RMSI), Other System Information (OSI), etc.
  • MIB Master Information Block
  • SIB System Information Block
  • RMSI Remaining Minimum System Information
  • OSI System Information
  • the physical layer signaling may be, for example, Downlink Control Information (DCI), Uplink Control Information (UCI), etc.
  • DCI Downlink Control Information
  • UCI Uplink Control Information
  • index identifier
  • indicator indicator
  • resource ID etc.
  • sequence list, set, group, cluster, subset, etc.
  • the application/use of CP-OFDM and the transform precoder being disabled (disabled) may be read as interchangeable.
  • the application/use of DFT-s-OFDM and the transform precoder being enabled (enabled) may be read as interchangeable.
  • the transform precoder being disabled/enabled, the transform precoder being switched, and the waveform (CP-OFDM/DFT-s-OFDM) being switched may be read as interchangeable.
  • the PUSCH waveform, waveform, and transform precoder may be read as interchangeable.
  • CP-OFDM and CP-OFDM waveform may be read as interchangeable.
  • DFT-s-OFDM and DFT-s-OFDM waveform may be read as interchangeable. Enabled and on may be read as interchangeable. Disabled and off may be read as interchangeable. "When it is possible to dynamically switch the PUSCH waveform" and "When it is configured to dynamically switch the PUSCH waveform" may be read
  • the UE may receive a configuration indicating that the transform precoder for the PUSCH is dynamically switched between disabled and enabled by the DCI/MAC CE.
  • the UE may then receive an indication indicating the enablement or disablement of the transform precoder for the PUSCH by the DCI/MAC CE. That is, the UE may be capable of dynamically switching the PUSCH waveform.
  • the processes of the following several embodiments may be applied.
  • the PUSCH waveform when the PUSCH waveform can be dynamically switched, at least one of the methods described above (dynamic switching between disabling and enabling the transform precoder) may be applied.
  • transformPrecoder is expected to have values corresponding to enabled (i.e., DFT-s-OFDM), disabled (i.e., CP-OFDM), or no restriction.
  • the setting of the RRC parameter transformPrecoder affects the DCI size, which affects the processing load and communication overhead of the UE, so it is preferable to clarify it.
  • any of the following configurations may be applied to an RRC parameter transform precoder.
  • the RRC parameter transformPrecoder may be set to enabled. This reduces the DCI size assumed by the UE. That is, the NW (base station, gNB) can set the DCI size to be small, thereby suppressing communication overhead.
  • the RRC parameter transformPrecoder may be set to Disabled. This allows the UE to assume the same DCI size as CP-OFDM even when the PUSCH waveform is switched to DFT-s-OFDM, thereby reducing the processing load of the UE.
  • FIG. 3 is a flowchart showing an example of the process of embodiment 0.1.
  • the UE receives a setting indicating that dynamic switching of the PUSCH waveform is possible (step S101)
  • the UE receives the RRC parameter transformPrecoder set to enabled/disabled (step S102).
  • transformPrecoders There are multiple transformPrecoders as RRC parameters, but the transformPrecoder referenced by the UE may differ for each case (each timing). For example, the following options 1 and 2 may be applied. If dynamic switching of the PUSCH waveform is configured, the processing of the following options 1 and 2 may be applied at a timing before the instruction to dynamically switch the PUSCH waveform is issued.
  • the UE may refer to/consider the transformPrecoder in the RRC IE (e.g., PUSCH-Config or ConfiguredGrantConfig) corresponding to the PUSCH to be transmitted. This option may be applied to the UE after a dedicated (UE-specific) RRC configuration.
  • RRC IE e.g., PUSCH-Config or ConfiguredGrantConfig
  • the UE may refer to/consider the transformPrecoder in a specific RRC IE regardless of the type of PUSCH (e.g., msg3-transformPrecoder in RACH-ConfigCommon). This option may be applied to the UE before a dedicated (UE-specific) RRC configuration.
  • the UE may receive a value/setting based on any of the following aspects/options as the maximum rank (maxRank) of the RRC parameter. That is, the UE may assume the application of any of the following aspects/options for the value/setting of maxRank.
  • maxRank is a parameter indicating the maximum value of the transmission rank (layer) of UL (PUSCH). The UE controls the transmission of PUSCH based on maxRank.
  • the maxRank may be set to a specific value or a value smaller than a specific value.
  • the specific value may be, for example, determined (fixed) in a specification. Alternatively, the specific value may be set/indicated by the RRC/MAC CE/DCI. For example, when dynamic switching of the PUSCH waveform is configured, the maxRank (specific value) may be 1.
  • maxRank is limited, for example if maxRank can only be set to 1, the bit width of the Transmitted Precoding Matrix Indicator (TPMI) will be the same regardless of the PUSCH waveform. In other words, the DCI size will be the same, which reduces the processing load on the UE.
  • TPMI Transmitted Precoding Matrix Indicator
  • FIG. 4 is a flowchart showing an example of the process of embodiment 0.2.
  • FIG. 4 shows an example of aspect 2 above.
  • Figure 5 shows the definition of the DCI field PTRS-DMRS association and DMRS sequence initialization.
  • DMRS sequence initialization is 0 bits when DFTS-OFDM is applied, and is 1 bit when CP-OFDM is applied.
  • the UE may process (assume) specific fields of the scheduling DCI for the PUSCH based on specific rules.
  • the particular field of the DCI may be at least one of a DeModulation Reference Signal (DMRS) sequence initialization field and a Phase Tracking Reference Signal (PTRS)-DMRS association field.
  • DMRS DeModulation Reference Signal
  • PTRS Phase Tracking Reference Signal
  • a particular rule may be that the UE ignores certain fields in the DCI.
  • the particular waveform may be DFT-s-OFDM or CP-OFDM.
  • the UE ignores at least one of the DMRS sequence initialization field and the PTRS-DMRS association field of the DCI.
  • the UE may ignore that field. This can reduce the processing load on the UE.
  • the number of bits in each DCI field/total DCI size may follow the rules for CP-OFDM.
  • the number of bits in each DCI field/total DCI size may not follow the rules for CP-OFDM.
  • ⁇ Problem 2> As described above (FDRA type), type 0 RA cannot be used for DFT-s-OFDM, so if the PUSCH waveform is switched to DFT-s-OFDM, type 1 or type 2 must be used.
  • the RRC parameters indicating the PUSCH waveform always correspond to the setting/indication of the FDRA type.
  • the setting of FDRA and the interlace use indication (useInterlacePUCCH-PUSCH) is not clear.
  • the UE may receive a specific field of the DCI and a specific RRC parameter corresponding to the scheduling of the PUSCH based on a specific rule (or may assume reception of the specific field of the DCI and the specific RRC parameter).
  • the UE may control the PUSCH transmission based on the specific field of the received DCI and the specific RRC parameter.
  • the particular field of the DCI may be the FDRA or the frequency hopping flag.
  • the specific RRC parameter may be resource allocation (resourceAllocation) or interlace use indication for PUCCH and PUSCH (useInterlacePUCCH-PUSCH).
  • the particular waveform may be DFT-s-OFDM or CP-OFDM.
  • a specific rule may be that resourceAllocation is either resourceAllcationType1 or dynamicSwitch. If resourceAllocation is dynamicSwitch, the Most Significant bit (MSB) of the FDRA must be "1". That is, type 1 of the FDRA must be indicated. This specific rule may be applied when useInterlacePUCCH-PUSCH is not set.
  • the specific rule may be that resourceAllocation is of resourceAllcationType1.
  • the specific rule may be that the frequency hopping flag is determined according to at least one of resourceAllocation and FDRA based on the specific rule.
  • a specific rule may be that useInterlacePUCCH-PUSCH (use of interlace for PUCCH and PUSCH) is set to enabled (use of interlace for PUCCH and PUSCH).
  • the UE may receive (or may assume to receive) configuration information (RRC parameters) indicating dynamic switching (dynamicSwitch) as resourceAllocation and indication information (DCI) indicating type 1 as FDRA.
  • RRC parameters configuration information
  • DCI resourceAllocation and indication information
  • the UE may control PUSCH transmission based on the configuration information and indication information.
  • the UE may receive (or may assume reception of) configuration information (RRC parameters) indicating type 1 (resourceAllocationType1) as resourceAllocation.
  • RRC parameters configuration information
  • the UE may control PUSCH transmission based on the configuration information.
  • the UE may receive (or may assume reception of) configuration information indicating that, for example, the PUSCH waveform is dynamically switchable and DFT-s-OFDM is instructed for the PUSCH, useInterlacePUCCH-PUSCH (use of interlace for PUCCH and PUSCH) is enabled.
  • the UE may control PUSCH transmission based on the configuration information.
  • Fig. 6 is a diagram showing an example of a setting pattern of useInterlacePUCCH-PUSCH, resourceAllocation, and RA type.
  • the following (1) and (2) may be applied to the setting patterns shown in Fig. 6.
  • (1) When the default value of transformPrecoder is disabled (CP-OFDM is indicated/used), the UE can expect any pattern, but when it is enabled (DFT-s-OFDM is indicated/used), patterns 1-1 and 1-3 may not be applicable.
  • the default value of transformPrecoder is enabled, the UE can expect patterns other than patterns 1-1 and 1-3 that apply DCI indicating type 0, but may expect any pattern when CP-OFDM is indicated/used.
  • the processing of this embodiment may be applied regardless of the waveform specified for the PUSCH.
  • the UE may control the specific fields of the DCI corresponding to the scheduling of the PUSCH and the specific RRC parameters based on the specific rules.
  • ⁇ Problem 3> When the PUSCH waveform can be dynamically switched, the type of PUSCH that can be applied is not clear. For example, it is not clear whether message 3 (Msg3)/message A (msg3-TransformPrecoder/msgA-TransformPrecoder) can be applied as the PUSCH. Also, it is not clear whether CG-PUSCH (transformPrecoder of ConfiguredGrantConfig) can be applied as the PUSCH. Also, when dynamic switching of the PUSCH waveform is supported for these PUSCHs, it is not clear what kind of processing is performed.
  • Msg3/message A msg3-TransformPrecoder/msgA-TransformPrecoder
  • CG-PUSCH TransformPrecoder of ConfiguredGrantConfig
  • the UE may apply the dynamic switching of the PUSCH waveform only to a specific type of PUSCH. That is, when the UE receives a configuration indicating that the PUSCH waveform is dynamically switched, the UE may control only the specific type of PUSCH to be dynamically switched based on the DCI/MAC CE.
  • the specific type of PUSCH may be, for example, at least one of the following (1) to (4).
  • DG DCI Grant
  • CG Type 1 Configured Grant
  • CG-PUSCH PUSCH transmission configured by higher layer signaling
  • Type 2 CG-PUSCH PUSCH transmission configured by higher layer signaling and activated/deactivated by DCI
  • RAR PUSCH scheduled by a random access response (RAR) (message 3 PUSCH or message A PUSCH).
  • RAR can be a contention-based random access (CBRA) RAR or a contention-free random access (CFRA) RAR.
  • CBRA contention-based random access
  • CFRA contention-free random access
  • the base station gNB knows the UE and its channel condition and can adjust the waveform appropriately.
  • FIG. 7 is a flowchart showing an example of processing according to the third embodiment.
  • the UE receives a setting indicating that dynamic switching of the PUSCH waveform is possible (step S301)
  • the UE controls so that only the waveform of a specific type of PUSCH is dynamically switched based on the DCI/MAC CE (step S302).
  • Dynamic switching of the waveform of type 1 CG-PUSCH (PUSCH transmission configured by higher layer signaling) may be applied, and at least one of the following methods (1-1) to (1-4) may be supported.
  • the above-mentioned method in dynamic switching between disabling and enabling the transform precoder
  • the UE may receive an explicit indication via DCI indicating whether transformPrecoder is enabled/disabled (DFT-s-OFDM/CP-OFDM) (explicit signaling).
  • the UE may receive an implicit indication via DCI indicating whether transformPrecoder is enabled/disabled (DFT-s-OFDM/CP-OFDM) (implicit signaling).
  • the UE may receive an explicit instruction in a MAC CE indicating whether transformPrecoder is enabled/disabled (DFT-s-OFDM/CP-OFDM) (explicit signaling).
  • the UE may receive an implicit indication by the MAC CE indicating whether transformPrecoder is enabled/disabled (DFT-s-OFDM/CP-OFDM) (implicit signaling).
  • the methods (1-1) to (1-4) may be applied to type 1 CG-PUSCH separately from other types of PUSCH (type 2 CG-PUSCH, DG-PUSCH). Alternatively, the methods (1-1) to (1-4) may be applied to type 1 CG-PUSCH in the same manner as the methods for other types of PUSCH.
  • DCI is not used for scheduling. Therefore, when the above (1-1) and (1-2) are applied, it is preferable to define a new DCI. For example, either of the following (2-1) or (2-2) may be applied as the DCI for the above (1-1) and (1-2).
  • a DCI for scheduling UL/DL unicast data may be applied. Note that the UL/DL-SCH scheduled by the DCI may not actually exist.
  • a DCI for scheduling other than unicast data may be applied. For example, this DCI may be applied when a group common DCI is used.
  • the methods (1-1) to (1-4) may be applied to type 2 CG-PUSCH separately from other types of PUSCH (type 1 CG-PUSCH, DG-PUSCH). Alternatively, the methods (1-1) to (1-4) may be applied to type 2 CG-PUSCH in the same manner as the methods for other types of PUSCH.
  • a DCI for activation/deactivation is used in the conventional type 2 CG-PUSCH, that DCI may be reused. Specifically, either of the following (2-1) or (2-2) may be applied as the DCI for (1-1) or (1-2) above.
  • a DCI for scheduling UL/DL unicast data may be applied.
  • the UL/DL-SCH scheduled by the DCI may not actually exist.
  • a DCI for activating/deactivating a type 2 CG-PUSCH may be applied.
  • a DCI for scheduling other than unicast data may be applied. For example, this DCI may be applied when a group common DCI is used.
  • PUSCH PUSCH scheduled by random access response (RAR)
  • RAR random access response
  • the UE may receive an explicit/implicit indication via the RAR indicating whether transformPrecoder is enabled/disabled (DFT-s-OFDM/CP-OFDM).
  • the methods (1-1) to (1-5) may be applied to the message 3/message A PUSCH separately from other types of PUSCH (type 1/type 2 CG-PUSCH, DG-PUSCH). Alternatively, the methods (1-1) to (1-5) may be applied to the message 3/message A PUSCH in the same manner as the methods for other types of PUSCH.
  • DCI may be reused. Specifically, either of the following (2-1) or (2-2) may be applied as the DCI for the above (1-1) or (1-2).
  • a DCI for scheduling UL/DL unicast data may be applied.
  • the DCI may be DCI 1_0 with a Cyclic Redundancy Check (CRC) scrambled by the RA Radio Network Temporary Identifier (RNTI) or the message B RNTI.
  • CRC Cyclic Redundancy Check
  • RNTI Radio Network Temporary Identifier
  • a DCI for scheduling other than unicast data may be applied. For example, this DCI may be applied when a group common DCI is used.
  • the UE may support at least one of the following (3-1) and (3-2) regarding RAR-based instructions.
  • the UE may dynamically switch the waveform of Message 3 PUSCH or Message A PUSCH based on at least one of the MAC subheader or MAC payload for the RAR.
  • the reserved bit (R) in the MAC subheader/MAC payload for RAR may be cleared and used for dynamic waveform switching.
  • the "R" in the first octet of the MAC payload shown in FIG. 8 i.e., next to the Timing Advance Command
  • (3-2) It may be implicitly indicated based on the existing RAR grant field (UL Grant) shown in Figure 9.
  • MCS Modulation and Coding Scheme
  • the enable/disable of the transformPrecoder may be set for the message 3/message A PUSCH.
  • the value corresponding to the TPC command for the message 3 PUSCH in the UL Grant ( Figures 9 and 10) is a specific value or is greater than/less than a specific threshold
  • the enable/disable of the transformPrecoder may be set for the message 3/message A PUSCH.
  • the enable/disable of the transformPrecoder may be set for the message 3/message A PUSCH.
  • the enable/disable of the transformPrecoder may be set for the message 3/message A PUSCH.
  • This embodiment may be applied when a specific condition is met.
  • the specific condition may be that the PRACH that triggers the RAR is transmitted on a specific RA resource based on the RACH resource partition configuration.
  • the DCI may indicate switching between CP-OFDM and DFT-S-OFDM waveforms.
  • DMRS type 2 (or DMRS type 1) can be set for CP-OFDM (similar to existing systems (e.g., before Rel. 17 NR)).
  • DMRS type 2 cannot be configured in existing systems, but if dynamic waveform switching is configured/supported, there may be cases where DMRS type 2 is configured for DFT-S-OFDM. This is because DCI instructions (e.g., waveform switching) are dynamically performed by RRC setting changes (DMRS type setting).
  • DMRS-Type DMRS type
  • the UE may be controlled to apply a specific DMRS type (e.g., DMRS type 1) regardless of the waveform (CP-OFDM or DFT-S-OFDM) indicated by DCI/DMRS type set by RRC.
  • DMRS type 1 a specific DMRS type
  • CP-OFDM or DFT-S-OFDM a specific DMRS type
  • DCI/DMRS type set by RRC a specific DMRS type
  • the UE may assume/apply at least one of the following options 6-1 to 6-2 for the DMRS type (dmrs-Type) of the PUSCH DMRS.
  • the dynamic waveform switching setting may be interpreted as enabling/activating dynamic waveform switching.
  • the base station may control the UE to set only type 1 as the DMRS type for PUSCH.
  • the setting of DMRS type 2 by RRC may be restricted/prohibited.
  • DMRS type 1 may be applied regardless of the waveform (CP-OFDM or DFT-S-OFDM) indicated by the DCI.
  • the UE may control to apply DMRS type 1 to both waveforms (CP-OFDM and DFT-S-OFDM).
  • the UE may assume/expect/determine that DMRS type 1 is configured for the PUSCH DMRS.
  • the setting of the DMRS type of the PUSCH by RRC may be omitted.
  • DMRS type 1 When dynamic waveform switching is configured, the following DMRS types may be supported/allowed: DMRS type 1 and DMRS type 2 (see FIG. 13).
  • the base station may control the UE to set DMRS type 1 or DMRS type 2 as the DMRS type of the PUSCH.
  • the setting of DMRS type 2 by the RRC may be permitted.
  • the UE may interpret that the DMRS type (e.g., dmrs-Type) of the PUSCH is configured as type 1. In other words, the UE may ignore the DMRS type 2 setting and apply DMRS type 1.
  • DMRS type e.g., dmrs-Type
  • DMRS type 1 may be applied regardless of the DMRS type configured in RRC.
  • a DMRS type (dmrs-Type) to be applied may be determined based on a waveform indicated by the DCI.
  • the UE may determine the DMRS type to apply based on the waveform (CP-OFDM or DFT-S-OFDM) indicated by the DCI/DMRS type set in the RRC.
  • the waveform CP-OFDM or DFT-S-OFDM
  • the UE may assume/apply at least one of the following options 7-1 to 7-2 for the DMRS type (dmrs-Type) of the PUSCH DMRS.
  • the DCI used to indicate DFT-S-OFDM may be the DCI used to schedule the PUSCH.
  • the base station may control the UE to set only type 1 as the DMRS type for PUSCH.
  • the setting of DMRS type 2 by RRC may be restricted/prohibited.
  • DMRS type 1 may be applied regardless of the waveform (CP-OFDM or DFT-S-OFDM) indicated by the DCI.
  • the UE may control to apply DMRS type 1 to both waveforms (CP-OFDM and DFT-S-OFDM).
  • the UE may assume/expect/determine that DMRS type 1 is configured for the PUSCH DMRS.
  • the setting of the DMRS type of the PUSCH by RRC may be omitted.
  • DMRS type 1 and DMRS type 2 may be supported/allowed as DMRS types.
  • the base station may control the UE to set DMRS type 1 or DMRS type 2 as the DMRS type of the PUSCH.
  • the setting of DMRS type 2 by the RRC may be permitted.
  • DMRS type 2 is configured, dynamic waveform switching is configured, and DFT-S-OFDM is indicated by DCI, the UE may interpret that type 1 is configured as the DMRS type (e.g., dmrs-Type) for the PUSCH. In other words, if DFT-S-OFDM is indicated by DCI, the UE may ignore the DMRS type 2 setting and apply DMRS type 1.
  • DMRS type 2 if DMRS type 2 is configured, dynamic waveform switching is configured, and DFT-S-OFDM is not indicated by DCI (e.g., CP-OFDM is indicated), the UE may interpret that DMRS type 2 is configured as the DMRS type (e.g., dmrs-Type) of the PUSCH. In other words, the UE may apply DMRS type 2 when DFT-S-OFDM is not indicated by DCI (e.g., CP-OFDM is indicated).
  • DCI e.g., CP-OFDM is indicated
  • DMRS type 2 when dynamic waveform switching is configured and DMRS type 2 is configured in RRC, the application of DMRS type 2 may be determined based on the waveform specified by DCI. Note that when dynamic waveform switching is configured and DMRS type 1 is configured in RRC, control may be performed to apply DMRS type 1 regardless of the waveform specified by DCI.
  • DMRS type 2 can be applied, making it possible to flexibly control the DMRS type to be applied depending on the waveform.
  • DMRS type 2 is configured as the DMRS type (e.g., dmrs-Type)
  • a certain field e.g., antenna port field
  • the UE may interpret a specific field (e.g., antenna port field) included in the DCI based on a specific rule.
  • the DCI may be a DCI used for scheduling the PUSCH.
  • the specific rule may be, for example, at least one of the following options 8-1 to 8-2.
  • bit width e.g., bitwidth
  • the bit width (e.g., bitwidth) of the antenna port field is determined taking into account that the dmrs-Type is DMRS type 2 (i.e., in accordance with the setting of dmrs-Type), but the UE may interpret the indication by the antenna port field by interpreting only a portion of the bits (or using a portion of the bits).
  • the number of some bits may be the same as the number of antenna port fields (or the number of bits/code points) for which Type 2 is set for dmrs-Type 1. In this disclosure, some/some of the bits may be read as some/some of the DCI code points.
  • the determination of the bit width of the antenna port field of the DCI may differ from the interpretation of the antenna port field.
  • the bit width/number of code points of the antenna port field of the DCI may be determined based on DMRS Type 2, and the antenna port field of the DCI may be interpreted assuming DMRS Type 1.
  • the number of DCI codepoint portions may be the same as the number of antenna port fields (or number of bits/number of codepoints) for which Type 2 is configured for dmrs-Type 1.
  • bit width (e.g., bitwidth) of the antenna port field is determined taking into account that the dmrs-Type is DMRS type 1 (i.e., ignoring the setting of dmrs-Type), and the UE may interpret the indication by the antenna port field taking into account that the dmrs-Type is DMRS type 1.
  • the determination of the bit width of the antenna port field of the DCI and the interpretation of the antenna port field may be the same.
  • the bit width of the antenna port field of the DCI may be determined based on DMRS Type 1, and the interpretation of the antenna port field of the DCI may also be performed assuming DMRS Type 1.
  • both the bit width and interpretation of the antenna port field can be assumed to be DMRS type 1. It is also possible to suppress an increase in the overhead of the antenna port field.
  • the DMRS type (e.g., dmrs-Type) is set to DMRS type 2, and DFT-S-OFDM is indicated by the DCI, a specific field (e.g., antenna port field) included in the DCI may be interpreted based on a specific rule.
  • DWS dynamic waveform switching
  • the UE may interpret a predetermined field (e.g., an antenna port field) included in the DCI based on a predetermined rule.
  • the DCI may be a DCI used for scheduling a PUSCH.
  • the predetermined rule may be, for example, at least one of the following options 9-1 to 9-2.
  • bit width e.g., bitwidth
  • the bit width of the antenna port field is determined taking into account that the dmrs-Type is DMRS type 2 (i.e., in accordance with the setting of dmrs-Type), but the UE may interpret the indication by the antenna port field by interpreting only a portion of the bits (or using a portion of the bits).
  • the number of some bits may be the same as the number of antenna port fields (or the number of bits/code points) for which Type 2 is set for dmrs-Type 1. In this disclosure, some/some of the bits may be read as some/some of the DCI code points.
  • the determination of the bit width of the antenna port field of the DCI may be different from the interpretation of the antenna port field.
  • the bit width of the antenna port field of the DCI may be determined based on DMRS type 2, and the interpretation of the antenna port field of the DCI may be performed assuming DMRS type 1.
  • the number of DCI codepoint portions may be the same as the number of antenna port fields (or number of bits/number of codepoints) for which Type 2 is configured for dmrs-Type 1.
  • the bit width of the antenna port field of the DCI and the interpretation of the antenna port field may be determined based on DMRS type 2.
  • Figures 14A and 14B show an example of the antenna port field of DCI when dynamic waveform switching is configured and the DMRS type (e.g., dmrs-Type) is set to Type 2.
  • DMRS type e.g., dmrs-Type
  • Antenna port field example 1 When DFT-S-OFDM is indicated by DCI scheduling PUSCH, the bit width (or the number of bits of the field) may be set to 3 bits. In this case, the UE may interpret it in the same way as when Type 1 is set as the DMRS type (e.g., dmrs-Type). For example, only the least significant bit (LSB) of the 2 bits may be interpreted (see FIG. 14A).
  • DMRS type e.g., dmrs-Type
  • the bit width (or the number of bits in the field) may be set to 3 bits.
  • the UE may interpret it in the same way as when type 2 is set as the DMRS type (e.g., dmrs-Type). For example, it may interpret it using all 3 bits.
  • Antenna port field example 2 When DFT-S-OFDM is indicated by the DCI that schedules the PUSCH, the bit width (or the number of bits of the field) may be set to 3 bits. In this case, the UE may interpret using a predetermined number (here, 5) of the 8 code points generated by the 3 bits. In this case, the remaining 3 code points/fields may be reserved bits/reserved code points (see FIG. 14B).
  • the bit width (or the number of bits in the field) may be set to 3 bits.
  • the UE may interpret using all code points (here, 8) generated by the 3 bits.
  • PUSCH DMRS transmission can be performed appropriately by flexibly controlling the determination/interpretation of the bit width of the antenna port field of the DCI based on the waveform indicated by the DCI.
  • bit width (e.g., bitwidth) of the antenna port field is determined taking into account that the dmrs-Type is DMRS type 1 (i.e., ignoring the dmrs-Type setting), and the UE may interpret the indication by the antenna port field taking into account that the dmrs-Type is type 1.
  • the determination of the bit width of the antenna port field of the DCI and the interpretation of the antenna port field may be the same.
  • the bit width of the antenna port field of the DCI may be determined based on DMRS Type 1, and the interpretation of the antenna port field of the DCI may also be performed assuming DMRS Type 1.
  • both the bit width and interpretation of the antenna port field can be performed assuming DMRS type 1. It is also possible to suppress an increase in the overhead of the antenna port field.
  • any information may be notified to the UE (from a network (NW) (e.g., a base station (BS))) (in other words, any information is received from the BS by the UE) using physical layer signaling (e.g., DCI), higher layer signaling (e.g., RRC signaling, MAC CE), a specific signal/channel (e.g., PDCCH, PDSCH, reference signal), or a combination thereof.
  • NW network
  • BS base station
  • the MAC CE may be identified by including in the MAC subheader a new Logical Channel ID (LCID) that is not specified in existing standards.
  • LCID Logical Channel ID
  • the notification When the notification is made by a DCI, the notification may be made by a specific field of the DCI, a Radio Network Temporary Identifier (RNTI) used to scramble Cyclic Redundancy Check (CRC) bits assigned to the DCI, the format of the DCI, etc.
  • RNTI Radio Network Temporary Identifier
  • CRC Cyclic Redundancy Check
  • notification of any information to the UE in the above-mentioned embodiments may be performed periodically, semi-persistently, or aperiodically.
  • notification of any information from the UE (to the NW) may be performed using physical layer signaling (e.g., UCI), higher layer signaling (e.g., RRC signaling, MAC CE), a specific signal/channel (e.g., PUCCH, PUSCH, PRACH, reference signal), or a combination thereof.
  • physical layer signaling e.g., UCI
  • higher layer signaling e.g., RRC signaling, MAC CE
  • a specific signal/channel e.g., PUCCH, PUSCH, PRACH, reference signal
  • the MAC CE may be identified by including a new LCID in the MAC subheader that is not specified in existing standards.
  • the notification may be transmitted using PUCCH or PUSCH.
  • notification of any information from the UE may be performed periodically, semi-persistently, or aperiodically.
  • At least one of the above-mentioned embodiments may be applied when a specific condition is satisfied, which may be specified in a standard or may be notified to a UE/BS using higher layer signaling/physical layer signaling.
  • At least one of the above-described embodiments may be applied only to UEs that have reported or support a particular UE capability.
  • the specific UE capabilities may indicate at least one of the following: - Supporting specific processing/operations/control/information for at least one of the above embodiments.
  • the above-mentioned specific UE capabilities may be capabilities that are applied across all frequencies (commonly regardless of frequency), capabilities per frequency (e.g., one or a combination of a cell, band, band combination, BWP, component carrier, etc.), capabilities per frequency range (e.g., Frequency Range 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2), capabilities per subcarrier spacing (SubCarrier Spacing (SCS)), or capabilities per Feature Set (FS) or Feature Set Per Component-carrier (FSPC).
  • FR1 Frequency Range 1
  • FR2 FR2, FR3, FR4, FR5, FR2-1, FR2-2
  • SCS subcarrier Spacing
  • FS Feature Set
  • FSPC Feature Set Per Component-carrier
  • the specific UE capabilities may be capabilities that are applied across all duplexing methods (commonly regardless of the duplexing method), or may be capabilities for each duplexing method (e.g., Time Division Duplex (TDD) and Frequency Division Duplex (FDD)).
  • TDD Time Division Duplex
  • FDD Frequency Division Duplex
  • At least one of the above-mentioned embodiments may be applied when the UE configures/activates/triggers specific information related to the above-mentioned embodiments (or performs the operations of the above-mentioned embodiments) by higher layer signaling/physical layer signaling.
  • the specific information may be any RRC parameters for a specific release (e.g., Rel. 18/19), etc.
  • the UE may, for example, apply Rel. 15/16 operations.
  • a terminal having a receiving unit that receives information regarding a type of demodulation reference signal (DMRS) for a physical uplink shared channel (PUSCH), and a control unit that controls to apply a specific DMRS type when dynamic waveform switching for the PUSCH is set.
  • DMRS demodulation reference signal
  • PUSCH physical uplink shared channel
  • the control unit controls the first DMRS type to be applied to the PUSCH to which the single carrier waveform is applied when a second DMRS type is set as the DMRS type for the PUSCH and a single carrier waveform is applied to the PUSCH.
  • the terminal according to claim 1 [Appendix 3] The terminal according to claim 1 or 2, wherein the control unit determines whether or not the second DMRS type is applied based on information on a waveform of the PUSH indicated by downlink control information (DCI) used to schedule the PUSH.
  • DCI downlink control information
  • the control unit determines at least one of the bit width of a specified field of downlink control information used for scheduling the PUSH and interprets the specified field, taking into account the first DMRS type.
  • Wired communication system A configuration of a wireless communication system according to an embodiment of the present disclosure will be described below.
  • communication is performed using any one of the wireless communication methods according to the above embodiments of the present disclosure or a combination of these.
  • FIG. 15 is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment.
  • the wireless communication system 1 (which may simply be referred to as system 1) may be a system that realizes communication using Long Term Evolution (LTE) specified by the Third Generation Partnership Project (3GPP), 5th generation mobile communication system New Radio (5G NR), or the like.
  • LTE Long Term Evolution
  • 3GPP Third Generation Partnership Project
  • 5G NR 5th generation mobile communication system New Radio
  • the wireless communication system 1 may also support dual connectivity between multiple Radio Access Technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)).
  • MR-DC may include dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), dual connectivity between NR and LTE (NR-E-UTRA Dual Connectivity (NE-DC)), etc.
  • RATs Radio Access Technologies
  • MR-DC may include dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), dual connectivity between NR and LTE (NR-E-UTRA Dual Connectivity (NE-DC)), etc.
  • E-UTRA Evolved Universal Terrestrial Radio Access
  • EN-DC E-UTRA-NR Dual Connectivity
  • NE-DC NR-E-UTRA Dual Connectivity
  • the LTE (E-UTRA) base station (eNB) is the master node (MN), and the NR base station (gNB) is the secondary node (SN).
  • the NR base station (gNB) is the MN, and the LTE (E-UTRA) base station (eNB) is the SN.
  • the wireless communication system 1 may support dual connectivity between multiple base stations within the same RAT (e.g., dual connectivity in which both the MN and SN are NR base stations (gNBs) (NR-NR Dual Connectivity (NN-DC))).
  • dual connectivity in which both the MN and SN are NR base stations (gNBs) (NR-NR Dual Connectivity (NN-DC))).
  • gNBs NR base stations
  • N-DC Dual Connectivity
  • the wireless communication system 1 may include a base station 11 that forms a macrocell C1 with a relatively wide coverage, and base stations 12 (12a-12c) that are arranged within the macrocell C1 and form a small cell C2 that is narrower than the macrocell C1.
  • a user terminal 20 may be located within at least one of the cells. The arrangement and number of each cell and user terminal 20 are not limited to the embodiment shown in the figure. Hereinafter, when there is no need to distinguish between the base stations 11 and 12, they will be collectively referred to as base station 10.
  • the user terminal 20 may be connected to at least one of the multiple base stations 10.
  • the user terminal 20 may utilize at least one of carrier aggregation (CA) using multiple component carriers (CC) and dual connectivity (DC).
  • CA carrier aggregation
  • CC component carriers
  • DC dual connectivity
  • Each CC may be included in at least one of a first frequency band (Frequency Range 1 (FR1)) and a second frequency band (Frequency Range 2 (FR2)).
  • Macro cell C1 may be included in FR1
  • small cell C2 may be included in FR2.
  • FR1 may be a frequency band below 6 GHz (sub-6 GHz)
  • FR2 may be a frequency band above 24 GHz (above-24 GHz). Note that the frequency bands and definitions of FR1 and FR2 are not limited to these, and for example, FR1 may correspond to a higher frequency band than FR2.
  • the user terminal 20 may communicate using at least one of Time Division Duplex (TDD) and Frequency Division Duplex (FDD) in each CC.
  • TDD Time Division Duplex
  • FDD Frequency Division Duplex
  • the multiple base stations 10 may be connected by wire (e.g., optical fiber conforming to the Common Public Radio Interface (CPRI), X2 interface, etc.) or wirelessly (e.g., NR communication).
  • wire e.g., optical fiber conforming to the Common Public Radio Interface (CPRI), X2 interface, etc.
  • NR communication e.g., NR communication
  • base station 11 which corresponds to the upper station
  • IAB Integrated Access Backhaul
  • base station 12 which corresponds to a relay station
  • the base station 10 may be connected to the core network 30 directly or via another base station 10.
  • the core network 30 may include at least one of, for example, an Evolved Packet Core (EPC), a 5G Core Network (5GCN), a Next Generation Core (NGC), etc.
  • EPC Evolved Packet Core
  • 5GCN 5G Core Network
  • NGC Next Generation Core
  • the core network 30 may include network functions (Network Functions (NF)) such as, for example, a User Plane Function (UPF), an Access and Mobility management Function (AMF), a Session Management Function (SMF), a Unified Data Management (UDM), an Application Function (AF), a Data Network (DN), a Location Management Function (LMF), and Operation, Administration and Maintenance (Management) (OAM).
  • NF Network Functions
  • UPF User Plane Function
  • AMF Access and Mobility management Function
  • SMF Session Management Function
  • UDM Unified Data Management
  • AF Application Function
  • DN Data Network
  • LMF Location Management Function
  • OAM Operation, Administration and Maintenance
  • the user terminal 20 may be a terminal that supports at least one of the communication methods such as LTE, LTE-A, and 5G.
  • a wireless access method based on Orthogonal Frequency Division Multiplexing may be used.
  • OFDM Orthogonal Frequency Division Multiplexing
  • CP-OFDM Cyclic Prefix OFDM
  • DFT-s-OFDM Discrete Fourier Transform Spread OFDM
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single Carrier Frequency Division Multiple Access
  • the radio access method may also be called a waveform.
  • other radio access methods e.g., other single-carrier transmission methods, other multi-carrier transmission methods
  • a downlink shared channel (Physical Downlink Shared Channel (PDSCH)) shared by each user terminal 20, a broadcast channel (Physical Broadcast Channel (PBCH)), a downlink control channel (Physical Downlink Control Channel (PDCCH)), etc. may be used as the downlink channel.
  • PDSCH Physical Downlink Shared Channel
  • PBCH Physical Broadcast Channel
  • PDCCH Physical Downlink Control Channel
  • an uplink shared channel (Physical Uplink Shared Channel (PUSCH)) shared by each user terminal 20, an uplink control channel (Physical Uplink Control Channel (PUCCH)), a random access channel (Physical Random Access Channel (PRACH)), etc. may be used as an uplink channel.
  • PUSCH Physical Uplink Shared Channel
  • PUCCH Physical Uplink Control Channel
  • PRACH Physical Random Access Channel
  • SIB System Information Block
  • PDSCH User data, upper layer control information, System Information Block (SIB), etc.
  • SIB System Information Block
  • PUSCH User data, upper layer control information, etc.
  • MIB Master Information Block
  • PBCH Physical Broadcast Channel
  • Lower layer control information may be transmitted by the PDCCH.
  • the lower layer control information may include, for example, downlink control information (Downlink Control Information (DCI)) including scheduling information for at least one of the PDSCH and the PUSCH.
  • DCI Downlink Control Information
  • the DCI for scheduling the PDSCH may be called a DL assignment or DL DCI
  • the DCI for scheduling the PUSCH may be called a UL grant or UL DCI.
  • the PDSCH may be interpreted as DL data
  • the PUSCH may be interpreted as UL data.
  • a control resource set (COntrol REsource SET (CORESET)) and a search space may be used to detect the PDCCH.
  • the CORESET corresponds to the resources to search for DCI.
  • the search space corresponds to the search region and search method of PDCCH candidates.
  • One CORESET may be associated with one or multiple search spaces. The UE may monitor the CORESET associated with a search space based on the search space configuration.
  • a search space may correspond to PDCCH candidates corresponding to one or more aggregation levels.
  • One or more search spaces may be referred to as a search space set. Note that the terms “search space,” “search space set,” “search space setting,” “search space set setting,” “CORESET,” “CORESET setting,” etc. in this disclosure may be read as interchangeable.
  • the PUCCH may transmit uplink control information (UCI) including at least one of channel state information (CSI), delivery confirmation information (which may be called, for example, Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK/NACK, etc.), and a scheduling request (SR).
  • UCI uplink control information
  • CSI channel state information
  • HARQ-ACK Hybrid Automatic Repeat reQuest ACKnowledgement
  • ACK/NACK ACK/NACK
  • SR scheduling request
  • the PRACH may transmit a random access preamble for establishing a connection with a cell.
  • downlink, uplink, etc. may be expressed without adding "link.”
  • various channels may be expressed without adding "Physical” to the beginning.
  • a synchronization signal (SS), a downlink reference signal (DL-RS), etc. may be transmitted.
  • a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS), a demodulation reference signal (DMRS), a positioning reference signal (PRS), a phase tracking reference signal (PTRS), etc. may be transmitted.
  • the synchronization signal may be, for example, at least one of a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS).
  • a signal block including an SS (PSS, SSS) and a PBCH (and a DMRS for PBCH) may be called an SS/PBCH block, an SS Block (SSB), etc.
  • the SS, SSB, etc. may also be called a reference signal.
  • a measurement reference signal Sounding Reference Signal (SRS)
  • a demodulation reference signal DMRS
  • UL-RS uplink reference signal
  • DMRS may also be called a user equipment-specific reference signal (UE-specific Reference Signal).
  • the base station 16 is a diagram showing an example of a configuration of a base station according to an embodiment.
  • the base station 10 includes a control unit 110, a transceiver unit 120, a transceiver antenna 130, and a transmission line interface 140. Note that one or more of each of the control unit 110, the transceiver unit 120, the transceiver antenna 130, and the transmission line interface 140 may be provided.
  • this example mainly shows the functional blocks of the characteristic parts of this embodiment, and the base station 10 may also be assumed to have other functional blocks necessary for wireless communication. Some of the processing of each part described below may be omitted.
  • the control unit 110 controls the entire base station 10.
  • the control unit 110 can be configured from a controller, a control circuit, etc., which are described based on a common understanding in the technical field to which this disclosure pertains.
  • the control unit 110 may control signal generation, scheduling (e.g., resource allocation, mapping), etc.
  • the control unit 110 may control transmission and reception using the transceiver unit 120, the transceiver antenna 130, and the transmission path interface 140, measurement, etc.
  • the control unit 110 may generate data, control information, sequences, etc. to be transmitted as signals, and transfer them to the transceiver unit 120.
  • the control unit 110 may perform call processing of communication channels (setting, release, etc.), status management of the base station 10, management of radio resources, etc.
  • the transceiver unit 120 may include a baseband unit 121, a radio frequency (RF) unit 122, and a measurement unit 123.
  • the baseband unit 121 may include a transmission processing unit 1211 and a reception processing unit 1212.
  • the transceiver unit 120 may be composed of a transmitter/receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, etc., which are described based on a common understanding in the technical field to which the present disclosure relates.
  • the transceiver unit 120 may be configured as an integrated transceiver unit, or may be composed of a transmission unit and a reception unit.
  • the transmission unit may be composed of a transmission processing unit 1211 and an RF unit 122.
  • the reception unit may be composed of a reception processing unit 1212, an RF unit 122, and a measurement unit 123.
  • the transmitting/receiving antenna 130 can be configured as an antenna described based on common understanding in the technical field to which this disclosure pertains, such as an array antenna.
  • the transceiver 120 may transmit the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc.
  • the transceiver 120 may receive the above-mentioned uplink channel, uplink reference signal, etc.
  • the transceiver 120 may form at least one of the transmit beam and the receive beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), etc.
  • digital beamforming e.g., precoding
  • analog beamforming e.g., phase rotation
  • the transceiver 120 may perform Packet Data Convergence Protocol (PDCP) layer processing, Radio Link Control (RLC) layer processing (e.g., RLC retransmission control), Medium Access Control (MAC) layer processing (e.g., HARQ retransmission control), etc., on data and control information obtained from the control unit 110, and generate a bit string to be transmitted.
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • MAC Medium Access Control
  • HARQ retransmission control HARQ retransmission control
  • the transceiver 120 may perform transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, Discrete Fourier Transform (DFT) processing (if necessary), Inverse Fast Fourier Transform (IFFT) processing, precoding, and digital-to-analog conversion on the bit string to be transmitted, and output a baseband signal.
  • transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, Discrete Fourier Transform (DFT) processing (if necessary), Inverse Fast Fourier Transform (IFFT) processing, precoding, and digital-to-analog conversion on the bit string to be transmitted, and output a baseband signal.
  • channel coding which may include error correction coding
  • DFT Discrete Fourier Transform
  • IFFT Inverse Fast Fourier Transform
  • the transceiver unit 120 may perform modulation, filtering, amplification, etc., on the baseband signal to a radio frequency band, and transmit the radio frequency band signal via the transceiver antenna 130.
  • the transceiver unit 120 may perform amplification, filtering, demodulation to a baseband signal, etc. on the radio frequency band signal received by the transceiver antenna 130.
  • the transceiver 120 may apply reception processing such as analog-to-digital conversion, Fast Fourier Transform (FFT) processing, Inverse Discrete Fourier Transform (IDFT) processing (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal, and acquire user data, etc.
  • reception processing such as analog-to-digital conversion, Fast Fourier Transform (FFT) processing, Inverse Discrete Fourier Transform (IDFT) processing (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal, and acquire user data, etc.
  • FFT Fast Fourier Transform
  • IDFT Inverse Discrete Fourier Transform
  • filtering demapping
  • demodulation which may include error correction decoding
  • MAC layer processing which may include error correction decoding
  • the transceiver 120 may perform measurements on the received signal.
  • the measurement unit 123 may perform Radio Resource Management (RRM) measurements, Channel State Information (CSI) measurements, etc. based on the received signal.
  • the measurement unit 123 may measure received power (e.g., Reference Signal Received Power (RSRP)), received quality (e.g., Reference Signal Received Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR), Signal to Noise Ratio (SNR)), signal strength (e.g., Received Signal Strength Indicator (RSSI)), propagation path information (e.g., CSI), etc.
  • RSRP Reference Signal Received Power
  • RSSI Received Signal Strength Indicator
  • the measurement results may be output to the control unit 110.
  • the transmission path interface 140 may transmit and receive signals (backhaul signaling) between devices included in the core network 30 (e.g., network nodes providing NF), other base stations 10, etc., and may acquire and transmit user data (user plane data), control plane data, etc. for the user terminal 20.
  • devices included in the core network 30 e.g., network nodes providing NF
  • other base stations 10, etc. may acquire and transmit user data (user plane data), control plane data, etc. for the user terminal 20.
  • the transmitter and receiver of the base station 10 in this disclosure may be configured with at least one of the transmitter/receiver 120, the transmitter/receiver antenna 130, and the transmission path interface 140.
  • the transceiver 120 may transmit information (e.g., dmrs-Type) regarding the type of demodulation reference signal (DMRS) for the physical uplink shared channel (PUSCH).
  • information e.g., dmrs-Type
  • DMRS demodulation reference signal
  • the control unit 110 may determine that a specific DMRS type is applied to the PUSCH (e.g., a PUSCH that applies a single carrier waveform (e.g., DFT-S-OFDM)/multicarrier waveform (CP-OFDM)).
  • a specific DMRS type is applied to the PUSCH (e.g., a PUSCH that applies a single carrier waveform (e.g., DFT-S-OFDM)/multicarrier waveform (CP-OFDM)).
  • the (User terminal) 17 is a diagram showing an example of the configuration of a user terminal according to an embodiment.
  • the user terminal 20 includes a control unit 210, a transceiver unit 220, and a transceiver antenna 230. Note that the control unit 210, the transceiver unit 220, and the transceiver antenna 230 may each include one or more.
  • this example mainly shows the functional blocks of the characteristic parts of this embodiment, and the user terminal 20 may also be assumed to have other functional blocks necessary for wireless communication. Some of the processing of each part described below may be omitted.
  • the control unit 210 controls the entire user terminal 20.
  • the control unit 210 can be configured from a controller, a control circuit, etc., which are described based on a common understanding in the technical field to which this disclosure pertains.
  • the control unit 210 may control signal generation, mapping, etc.
  • the control unit 210 may control transmission and reception using the transceiver unit 220 and the transceiver antenna 230, measurement, etc.
  • the control unit 210 may generate data, control information, sequences, etc. to be transmitted as signals, and transfer them to the transceiver unit 220.
  • the transceiver unit 220 may include a baseband unit 221, an RF unit 222, and a measurement unit 223.
  • the baseband unit 221 may include a transmission processing unit 2211 and a reception processing unit 2212.
  • the transceiver unit 220 may be composed of a transmitter/receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, etc., which are described based on a common understanding in the technical field to which the present disclosure relates.
  • the transceiver unit 220 may be configured as an integrated transceiver unit, or may be composed of a transmission unit and a reception unit.
  • the transmission unit may be composed of a transmission processing unit 2211 and an RF unit 222.
  • the reception unit may be composed of a reception processing unit 2212, an RF unit 222, and a measurement unit 223.
  • the transmitting/receiving antenna 230 can be configured as an antenna described based on common understanding in the technical field to which this disclosure pertains, such as an array antenna.
  • the transceiver 220 may receive the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc.
  • the transceiver 220 may transmit the above-mentioned uplink channel, uplink reference signal, etc.
  • the transceiver 220 may form at least one of the transmit beam and receive beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), etc.
  • digital beamforming e.g., precoding
  • analog beamforming e.g., phase rotation
  • the transceiver 220 may perform PDCP layer processing, RLC layer processing (e.g., RLC retransmission control), MAC layer processing (e.g., HARQ retransmission control), etc. on the data and control information acquired from the controller 210, and generate a bit string to be transmitted.
  • RLC layer processing e.g., RLC retransmission control
  • MAC layer processing e.g., HARQ retransmission control
  • the transceiver 220 may perform transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, DFT processing (if necessary), IFFT processing, precoding, and digital-to-analog conversion on the bit string to be transmitted, and output a baseband signal.
  • transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, DFT processing (if necessary), IFFT processing, precoding, and digital-to-analog conversion on the bit string to be transmitted, and output a baseband signal.
  • Whether or not to apply DFT processing may be based on the settings of transform precoding.
  • the transceiver unit 220 transmission processing unit 2211
  • the transceiver unit 220 may perform DFT processing as the above-mentioned transmission processing in order to transmit the channel using a DFT-s-OFDM waveform, and when transform precoding is not enabled, it is not necessary to perform DFT processing as the above-mentioned transmission processing.
  • the transceiver unit 220 may perform modulation, filtering, amplification, etc., on the baseband signal to a radio frequency band, and transmit the radio frequency band signal via the transceiver antenna 230.
  • the transceiver unit 220 may perform amplification, filtering, demodulation to a baseband signal, etc. on the radio frequency band signal received by the transceiver antenna 230.
  • the transceiver 220 may apply reception processing such as analog-to-digital conversion, FFT processing, IDFT processing (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal to acquire user data, etc.
  • reception processing such as analog-to-digital conversion, FFT processing, IDFT processing (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal to acquire user data, etc.
  • the transceiver 220 may perform measurements on the received signal. For example, the measurement unit 223 may perform RRM measurements, CSI measurements, etc. based on the received signal.
  • the measurement unit 223 may measure received power (e.g., RSRP), received quality (e.g., RSRQ, SINR, SNR), signal strength (e.g., RSSI), propagation path information (e.g., CSI), etc.
  • the measurement results may be output to the control unit 210.
  • the transmitting unit and receiving unit of the user terminal 20 in this disclosure may be configured by at least one of the transmitting/receiving unit 220 and the transmitting/receiving antenna 230.
  • the transceiver 220 may receive information regarding the type of demodulation reference signal (DMRS) for the physical uplink shared channel (PUSCH).
  • DMRS demodulation reference signal
  • PUSCH physical uplink shared channel
  • control unit 210 may control the PUSCH to apply a specific DMRS type to a single-carrier waveform (e.g., DFT-S-OFDM).
  • a specific DMRS type e.g., DFT-S-OFDM.
  • the control unit 210 may control to apply the first DMRS type to the PUSCH (e.g., a PUSCH to which a single carrier waveform (e.g., DFT-S-OFDM)/multicarrier waveform (CP-OFDM) is applied).
  • a single carrier waveform e.g., DFT-S-OFDM
  • CP-OFDM multicarrier waveform
  • the control unit 210 may determine whether or not to apply the second DMRS type based on information about the PUSCH waveform indicated in the downlink control information (DCI) used to schedule the PUSCH.
  • DCI downlink control information
  • control unit 210 may control to perform at least one of determining the bit width of a specified field of the downlink control information used for scheduling the PUSCH and interpreting the specified field, taking into account the first DMRS type.
  • each functional block may be realized using one device that is physically or logically coupled, or may be realized using two or more devices that are physically or logically separated and directly or indirectly connected (for example, using wires, wirelessly, etc.).
  • the functional blocks may be realized by combining the one device or the multiple devices with software.
  • the functions include, but are not limited to, judgement, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, deeming, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment.
  • a functional block (component) that performs the transmission function may be called a transmitting unit, a transmitter, and the like. In either case, as mentioned above, there are no particular limitations on the method of realization.
  • a base station, a user terminal, etc. in one embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure.
  • FIG. 18 is a diagram showing an example of the hardware configuration of a base station and a user terminal according to one embodiment.
  • the above-mentioned base station 10 and user terminal 20 may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.
  • the terms apparatus, circuit, device, section, unit, etc. may be interpreted as interchangeable.
  • the hardware configuration of the base station 10 and the user terminal 20 may be configured to include one or more of the devices shown in the figures, or may be configured to exclude some of the devices.
  • processor 1001 may be implemented by one or more chips.
  • the functions of the base station 10 and the user terminal 20 are realized, for example, by loading specific software (programs) onto hardware such as the processor 1001 and memory 1002, causing the processor 1001 to perform calculations, control communications via the communication device 1004, and control at least one of the reading and writing of data in the memory 1002 and storage 1003.
  • the processor 1001 for example, runs an operating system to control the entire computer.
  • the processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, registers, etc.
  • CPU central processing unit
  • control unit 110 210
  • transmission/reception unit 120 220
  • etc. may be realized by the processor 1001.
  • the processor 1001 also reads out programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes according to these.
  • the programs used are those that cause a computer to execute at least some of the operations described in the above embodiments.
  • the control unit 110 (210) may be realized by a control program stored in the memory 1002 and running on the processor 1001, and similar implementations may be made for other functional blocks.
  • Memory 1002 is a computer-readable recording medium and may be composed of at least one of, for example, Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EPROM (EEPROM), Random Access Memory (RAM), and other suitable storage media. Memory 1002 may also be called a register, cache, main memory, etc. Memory 1002 can store executable programs (program codes), software modules, etc. for implementing a wireless communication method according to one embodiment of the present disclosure.
  • ROM Read Only Memory
  • EPROM Erasable Programmable ROM
  • EEPROM Electrically EPROM
  • RAM Random Access Memory
  • Memory 1002 may also be called a register, cache, main memory, etc.
  • Memory 1002 can store executable programs (program codes), software modules, etc. for implementing a wireless communication method according to one embodiment of the present disclosure.
  • Storage 1003 is a computer-readable recording medium and may be composed of at least one of a flexible disk, a floppy disk, a magneto-optical disk (e.g., a compact disk (Compact Disc ROM (CD-ROM)), a digital versatile disk, a Blu-ray disk), a removable disk, a hard disk drive, a smart card, a flash memory device (e.g., a card, a stick, a key drive), a magnetic stripe, a database, a server, or other suitable storage medium.
  • Storage 1003 may also be referred to as an auxiliary storage device.
  • the communication device 1004 is hardware (transmitting/receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also called, for example, a network device, a network controller, a network card, or a communication module.
  • the communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc., to realize at least one of Frequency Division Duplex (FDD) and Time Division Duplex (TDD).
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • the above-mentioned transmitting/receiving unit 120 (220), transmitting/receiving antenna 130 (230), etc. may be realized by the communication device 1004.
  • the transmitting/receiving unit 120 (220) may be implemented as a transmitting unit 120a (220a) and a receiving unit 120b (220b) that are physically or logically separated.
  • the input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that accepts input from the outside.
  • the output device 1006 is an output device (e.g., a display, a speaker, a Light Emitting Diode (LED) lamp, etc.) that outputs to the outside.
  • the input device 1005 and the output device 1006 may be integrated into one structure (e.g., a touch panel).
  • each device such as the processor 1001 and memory 1002 is connected by a bus 1007 for communicating information.
  • the bus 1007 may be configured using a single bus, or may be configured using different buses between each device.
  • the base station 10 and the user terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized using the hardware.
  • the processor 1001 may be implemented using at least one of these pieces of hardware.
  • a channel, a symbol, and a signal may be read as mutually interchangeable.
  • a signal may also be a message.
  • a reference signal may be abbreviated as RS, and may be called a pilot, a pilot signal, or the like depending on the applied standard.
  • a component carrier may also be called a cell, a frequency carrier, a carrier frequency, or the like.
  • a radio frame may be composed of one or more periods (frames) in the time domain.
  • Each of the one or more periods (frames) constituting a radio frame may be called a subframe.
  • a subframe may be composed of one or more slots in the time domain.
  • a subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.
  • the numerology may be a communication parameter that is applied to at least one of the transmission and reception of a signal or channel.
  • the numerology may indicate, for example, at least one of the following: SubCarrier Spacing (SCS), bandwidth, symbol length, cyclic prefix length, Transmission Time Interval (TTI), number of symbols per TTI, radio frame configuration, a specific filtering process performed by the transceiver in the frequency domain, a specific windowing process performed by the transceiver in the time domain, etc.
  • SCS SubCarrier Spacing
  • TTI Transmission Time Interval
  • radio frame configuration a specific filtering process performed by the transceiver in the frequency domain
  • a specific windowing process performed by the transceiver in the time domain etc.
  • a slot may consist of one or more symbols in the time domain (such as Orthogonal Frequency Division Multiplexing (OFDM) symbols, Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols, etc.).
  • OFDM Orthogonal Frequency Division Multiplexing
  • SC-FDMA Single Carrier Frequency Division Multiple Access
  • a slot may also be a time unit based on numerology.
  • a slot may include multiple minislots. Each minislot may consist of one or multiple symbols in the time domain. A minislot may also be called a subslot. A minislot may consist of fewer symbols than a slot.
  • a PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (PUSCH) mapping type A.
  • a PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (PUSCH) mapping type B.
  • a radio frame, a subframe, a slot, a minislot, and a symbol all represent time units when transmitting a signal.
  • a different name may be used for a radio frame, a subframe, a slot, a minislot, and a symbol, respectively.
  • the time units such as a frame, a subframe, a slot, a minislot, and a symbol in this disclosure may be read as interchangeable.
  • one subframe may be called a TTI
  • multiple consecutive subframes may be called a TTI
  • one slot or one minislot may be called a TTI.
  • at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (e.g., 1-13 symbols), or a period longer than 1 ms.
  • the unit representing the TTI may be called a slot, minislot, etc., instead of a subframe.
  • TTI refers to, for example, the smallest time unit for scheduling in wireless communication.
  • a base station schedules each user terminal by allocating radio resources (such as frequency bandwidth and transmission power that can be used by each user terminal) in TTI units.
  • radio resources such as frequency bandwidth and transmission power that can be used by each user terminal
  • the TTI may be a transmission time unit for a channel-coded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc.
  • the time interval e.g., the number of symbols
  • the time interval in which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.
  • one or more TTIs may be the minimum time unit of scheduling.
  • the number of slots (minislots) that constitute the minimum time unit of scheduling may be controlled.
  • a TTI having a time length of 1 ms may be called a normal TTI (TTI in 3GPP Rel. 8-12), normal TTI, long TTI, normal subframe, normal subframe, long subframe, slot, etc.
  • a TTI shorter than a normal TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.
  • a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms
  • a short TTI e.g., a shortened TTI, etc.
  • TTI length shorter than the TTI length of a long TTI and equal to or greater than 1 ms.
  • a resource block is a resource allocation unit in the time domain and frequency domain, and may include one or more consecutive subcarriers in the frequency domain.
  • the number of subcarriers included in an RB may be the same regardless of numerology, and may be, for example, 12.
  • the number of subcarriers included in an RB may be determined based on numerology.
  • an RB may include one or more symbols in the time domain and may be one slot, one minislot, one subframe, or one TTI in length.
  • One TTI, one subframe, etc. may each be composed of one or more resource blocks.
  • one or more RBs may be referred to as a physical resource block (Physical RB (PRB)), a sub-carrier group (Sub-Carrier Group (SCG)), a resource element group (Resource Element Group (REG)), a PRB pair, an RB pair, etc.
  • PRB Physical RB
  • SCG sub-carrier Group
  • REG resource element group
  • PRB pair an RB pair, etc.
  • a resource block may be composed of one or more resource elements (REs).
  • REs resource elements
  • one RE may be a radio resource area of one subcarrier and one symbol.
  • a Bandwidth Part which may also be referred to as a partial bandwidth, may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by an index of the RB relative to a common reference point of the carrier.
  • PRBs may be defined in a BWP and numbered within the BWP.
  • the BWP may include a UL BWP (BWP for UL) and a DL BWP (BWP for DL).
  • BWP UL BWP
  • BWP for DL DL BWP
  • One or more BWPs may be configured for a UE within one carrier.
  • At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal/channel outside the active BWP.
  • BWP bitmap
  • radio frames, subframes, slots, minislots, and symbols are merely examples.
  • the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, as well as the number of symbols in a TTI, the symbol length, and the cyclic prefix (CP) length can be changed in various ways.
  • the information, parameters, etc. described in this disclosure may be represented using absolute values, may be represented using relative values from a predetermined value, or may be represented using other corresponding information.
  • a radio resource may be indicated by a predetermined index.
  • the names used for parameters and the like in this disclosure are not limiting in any respect. Furthermore, the formulas and the like using these parameters may differ from those explicitly disclosed in this disclosure.
  • the various channels (PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not limiting in any respect.
  • the information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies.
  • the data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.
  • information, signals, etc. may be output from a higher layer to a lower layer and/or from a lower layer to a higher layer.
  • Information, signals, etc. may be input/output via multiple network nodes.
  • Input/output information, signals, etc. may be stored in a specific location (e.g., memory) or may be managed using a management table. Input/output information, signals, etc. may be overwritten, updated, or added to. Output information, signals, etc. may be deleted. Input information, signals, etc. may be transmitted to another device.
  • a specific location e.g., memory
  • Input/output information, signals, etc. may be overwritten, updated, or added to.
  • Output information, signals, etc. may be deleted.
  • Input information, signals, etc. may be transmitted to another device.
  • the notification of information is not limited to the aspects/embodiments described in this disclosure, and may be performed using other methods.
  • the notification of information in this disclosure may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB)), etc.), Medium Access Control (MAC) signaling), other signals, or a combination of these.
  • DCI Downlink Control Information
  • UCI Uplink Control Information
  • RRC Radio Resource Control
  • MIB Master Information Block
  • SIB System Information Block
  • MAC Medium Access Control
  • the physical layer signaling may be called Layer 1/Layer 2 (L1/L2) control information (L1/L2 control signal), L1 control information (L1 control signal), etc.
  • the RRC signaling may be called an RRC message, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, etc.
  • the MAC signaling may be notified, for example, using a MAC Control Element (CE).
  • CE MAC Control Element
  • notification of specified information is not limited to explicit notification, but may be implicit (e.g., by not notifying the specified information or by notifying other information).
  • the determination may be based on a value represented by a single bit (0 or 1), a Boolean value represented by true or false, or a comparison of numerical values (e.g., with a predetermined value).
  • Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
  • Software, instructions, information, etc. may also be transmitted and received via a transmission medium.
  • a transmission medium For example, if the software is transmitted from a website, server, or other remote source using at least one of wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and/or wireless technologies (such as infrared, microwave, etc.), then at least one of these wired and wireless technologies is included within the definition of a transmission medium.
  • wired technologies such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)
  • wireless technologies such as infrared, microwave, etc.
  • Network may refer to the devices included in the network (e.g., base stations).
  • precoding "precoder,” “weight (precoding weight),” “Quasi-Co-Location (QCL),” “Transmission Configuration Indication state (TCI state),” "spatial relation,” “spatial domain filter,” “transmit power,” “phase rotation,” “antenna port,” “antenna port group,” “layer,” “number of layers,” “rank,” “resource,” “resource set,” “resource group,” “beam,” “beam width,” “beam angle,” “antenna,” “antenna element,” and “panel” may be used interchangeably.
  • Base Station may also be referred to by terms such as macrocell, small cell, femtocell, picocell, etc.
  • a base station can accommodate one or more (e.g., three) cells.
  • a base station accommodates multiple cells, the entire coverage area of the base station can be divided into multiple smaller areas, and each smaller area can also provide communication services by a base station subsystem (e.g., a small base station for indoor use (Remote Radio Head (RRH))).
  • RRH Remote Radio Head
  • the term "cell” or “sector” refers to a part or the entire coverage area of at least one of the base station and base station subsystems that provide communication services in this coverage.
  • a base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control/operate based on the information.
  • MS Mobile Station
  • UE User Equipment
  • a mobile station may also be referred to as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.
  • At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a wireless communication device, etc.
  • at least one of the base station and the mobile station may be a device mounted on a moving object, the moving object itself, etc.
  • the moving body in question refers to an object that can move, and the moving speed is arbitrary, and of course includes the case where the moving body is stationary.
  • the moving body in question includes, but is not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, artificial satellites, drones, multicopters, quadcopters, balloons, and objects mounted on these.
  • the moving body in question may also be a moving body that moves autonomously based on an operating command.
  • the moving object may be a vehicle (e.g., a car, an airplane, etc.), an unmanned moving object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned).
  • a vehicle e.g., a car, an airplane, etc.
  • an unmanned moving object e.g., a drone, an autonomous vehicle, etc.
  • a robot manned or unmanned
  • at least one of the base station and the mobile station may also include devices that do not necessarily move during communication operations.
  • at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.
  • IoT Internet of Things
  • FIG. 19 is a diagram showing an example of a vehicle according to an embodiment.
  • the vehicle 40 includes a drive unit 41, a steering unit 42, an accelerator pedal 43, a brake pedal 44, a shift lever 45, left and right front wheels 46, left and right rear wheels 47, an axle 48, an electronic control unit 49, various sensors (including a current sensor 50, a rotation speed sensor 51, an air pressure sensor 52, a vehicle speed sensor 53, an acceleration sensor 54, an accelerator pedal sensor 55, a brake pedal sensor 56, a shift lever sensor 57, and an object detection sensor 58), an information service unit 59, and a communication module 60.
  • various sensors including a current sensor 50, a rotation speed sensor 51, an air pressure sensor 52, a vehicle speed sensor 53, an acceleration sensor 54, an accelerator pedal sensor 55, a brake pedal sensor 56, a shift lever sensor 57, and an object detection sensor 58
  • an information service unit 59 including a communication module 60.
  • the drive unit 41 is composed of at least one of an engine, a motor, and a hybrid of an engine and a motor, for example.
  • the steering unit 42 includes at least a steering wheel (also called a handlebar), and is configured to steer at least one of the front wheels 46 and the rear wheels 47 based on the operation of the steering wheel operated by the user.
  • the electronic control unit 49 is composed of a microprocessor 61, memory (ROM, RAM) 62, and a communication port (e.g., an Input/Output (IO) port) 63. Signals are input to the electronic control unit 49 from various sensors 50-58 provided in the vehicle.
  • the electronic control unit 49 may also be called an Electronic Control Unit (ECU).
  • ECU Electronic Control Unit
  • Signals from the various sensors 50-58 include a current signal from a current sensor 50 that senses the motor current, a rotation speed signal of the front wheels 46/rear wheels 47 acquired by a rotation speed sensor 51, an air pressure signal of the front wheels 46/rear wheels 47 acquired by an air pressure sensor 52, a vehicle speed signal acquired by a vehicle speed sensor 53, an acceleration signal acquired by an acceleration sensor 54, a depression amount signal of the accelerator pedal 43 acquired by an accelerator pedal sensor 55, a depression amount signal of the brake pedal 44 acquired by a brake pedal sensor 56, an operation signal of the shift lever 45 acquired by a shift lever sensor 57, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. acquired by an object detection sensor 58.
  • the information service unit 59 is composed of various devices, such as a car navigation system, audio system, speakers, displays, televisions, and radios, for providing (outputting) various information such as driving information, traffic information, and entertainment information, and one or more ECUs that control these devices.
  • the information service unit 59 uses information acquired from external devices via the communication module 60, etc., to provide various information/services (e.g., multimedia information/multimedia services) to the occupants of the vehicle 40.
  • various information/services e.g., multimedia information/multimedia services
  • the information service unit 59 may include input devices (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, a touch panel, etc.) that accept input from the outside, and may also include output devices (e.g., a display, a speaker, an LED lamp, a touch panel, etc.) that perform output to the outside.
  • input devices e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, a touch panel, etc.
  • output devices e.g., a display, a speaker, an LED lamp, a touch panel, etc.
  • the driving assistance system unit 64 is composed of various devices that provide functions for preventing accidents and reducing the driver's driving load, such as a millimeter wave radar, a Light Detection and Ranging (LiDAR), a camera, a positioning locator (e.g., a Global Navigation Satellite System (GNSS)), map information (e.g., a High Definition (HD) map, an Autonomous Vehicle (AV) map, etc.), a gyro system (e.g., an Inertial Measurement Unit (IMU), an Inertial Navigation System (INS), etc.), an Artificial Intelligence (AI) chip, and an AI processor, and one or more ECUs that control these devices.
  • the driving assistance system unit 64 also transmits and receives various information via the communication module 60 to realize a driving assistance function or an autonomous driving function.
  • the communication module 60 can communicate with the microprocessor 61 and components of the vehicle 40 via the communication port 63.
  • the communication module 60 transmits and receives data (information) via the communication port 63 between the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, shift lever 45, left and right front wheels 46, left and right rear wheels 47, axles 48, the microprocessor 61 and memory (ROM, RAM) 62 in the electronic control unit 49, and the various sensors 50-58 that are provided on the vehicle 40.
  • the communication module 60 is a communication device that can be controlled by the microprocessor 61 of the electronic control unit 49 and can communicate with an external device. For example, it transmits and receives various information to and from the external device via wireless communication.
  • the communication module 60 may be located either inside or outside the electronic control unit 49.
  • the external device may be, for example, the above-mentioned base station 10 or user terminal 20.
  • the communication module 60 may also be, for example, at least one of the above-mentioned base station 10 and user terminal 20 (it may function as at least one of the base station 10 and user terminal 20).
  • the communication module 60 may transmit at least one of the signals from the various sensors 50-58 described above input to the electronic control unit 49, information obtained based on the signals, and information based on input from the outside (user) obtained via the information service unit 59 to an external device via wireless communication.
  • the electronic control unit 49, the various sensors 50-58, the information service unit 59, etc. may be referred to as input units that accept input.
  • the PUSCH transmitted by the communication module 60 may include information based on the above input.
  • the communication module 60 receives various information (traffic information, signal information, vehicle distance information, etc.) transmitted from an external device and displays it on an information service unit 59 provided in the vehicle.
  • the information service unit 59 may also be called an output unit that outputs information (for example, outputs information to a device such as a display or speaker based on the PDSCH (or data/information decoded from the PDSCH) received by the communication module 60).
  • the communication module 60 also stores various information received from external devices in memory 62 that can be used by the microprocessor 61. Based on the information stored in memory 62, the microprocessor 61 may control the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, shift lever 45, left and right front wheels 46, left and right rear wheels 47, axles 48, various sensors 50-58, and the like provided on the vehicle 40.
  • the base station in the present disclosure may be read as a user terminal.
  • each aspect/embodiment of the present disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple user terminals (which may be called, for example, Device-to-Device (D2D), Vehicle-to-Everything (V2X), etc.).
  • the user terminal 20 may be configured to have the functions of the base station 10 described above.
  • terms such as "uplink” and "downlink” may be read as terms corresponding to terminal-to-terminal communication (for example, "sidelink").
  • the uplink channel, downlink channel, etc. may be read as the sidelink channel.
  • the user terminal in this disclosure may be interpreted as a base station.
  • the base station 10 may be configured to have the functions of the user terminal 20 described above.
  • operations that are described as being performed by a base station may in some cases be performed by its upper node.
  • a network that includes one or more network nodes having base stations, it is clear that various operations performed for communication with terminals may be performed by the base station, one or more network nodes other than the base station (such as, but not limited to, a Mobility Management Entity (MME) or a Serving-Gateway (S-GW)), or a combination of these.
  • MME Mobility Management Entity
  • S-GW Serving-Gateway
  • each aspect/embodiment described in this disclosure may be used alone, in combination, or switched between depending on the implementation.
  • the processing procedures, sequences, flow charts, etc. of each aspect/embodiment described in this disclosure may be rearranged as long as there is no inconsistency.
  • the methods described in this disclosure present elements of various steps using an exemplary order, and are not limited to the particular order presented.
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • LTE-B LTE-Beyond
  • SUPER 3G IMT-Advanced
  • 4th generation mobile communication system 4th generation mobile communication system
  • 5G 5th generation mobile communication system
  • 6G 6th generation mobile communication system
  • xG x is, for example, an integer or decimal
  • Future Radio Access FX
  • GSM Global System for Mobile communications
  • CDMA2000 Code Division Multiple Access
  • UMB Ultra Mobile Broadband
  • IEEE 802.11 Wi-Fi
  • IEEE 802.16 WiMAX (registered trademark)
  • IEEE 802.20 Ultra-WideBand (UWB), Bluetooth (registered trademark), and other appropriate wireless communication methods, as well as next-generation systems that are expanded, modified,
  • the phrase “based on” does not mean “based only on,” unless expressly stated otherwise. In other words, the phrase “based on” means both “based only on” and “based at least on.”
  • any reference to elements using designations such as “first,” “second,” etc., used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and second element does not imply that only two elements may be employed or that the first element must precede the second element in some way.
  • determining may encompass a wide variety of actions. For example, “determining” may be considered to be judging, calculating, computing, processing, deriving, investigating, looking up, search, inquiry (e.g., looking in a table, database, or other data structure), ascertaining, etc.
  • Determining may also be considered to mean “determining” receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in a memory), etc.
  • “Judgment” may also be considered to mean “deciding” to resolve, select, choose, establish, compare, etc.
  • judgment may also be considered to mean “deciding” to take some kind of action.
  • the "maximum transmit power" referred to in this disclosure may mean the maximum value of transmit power, may mean the nominal UE maximum transmit power, or may mean the rated UE maximum transmit power.
  • connection and “coupled,” or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are “connected” or “coupled” to each other.
  • the coupling or connection between the elements may be physical, logical, or a combination thereof. For example, "connected” may be read as "accessed.”
  • a and B are different may mean “A and B are different from each other.”
  • the term may also mean “A and B are each different from C.”
  • Terms such as “separate” and “combined” may also be interpreted in the same way as “different.”

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Un équipement utilisateur (UE) selon un aspect de la présente divulgation comprend : une unité de réception qui reçoit des informations relatives au type d'un signal de référence de démodulation (DMRS) pour un canal physique de liaison montante (PUSCH); et une unité de commande qui effectue une commande de façon à appliquer un type de DMRS spécifique si une commutation de forme d'onde dynamique pour le PUSCH est définie.
PCT/JP2023/005739 2023-02-17 2023-02-17 Équipement utilisateur, procédé de communication sans fil, et station de base WO2024171433A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/JP2023/005739 WO2024171433A1 (fr) 2023-02-17 2023-02-17 Équipement utilisateur, procédé de communication sans fil, et station de base

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2023/005739 WO2024171433A1 (fr) 2023-02-17 2023-02-17 Équipement utilisateur, procédé de communication sans fil, et station de base

Publications (1)

Publication Number Publication Date
WO2024171433A1 true WO2024171433A1 (fr) 2024-08-22

Family

ID=92421373

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2023/005739 WO2024171433A1 (fr) 2023-02-17 2023-02-17 Équipement utilisateur, procédé de communication sans fil, et station de base

Country Status (1)

Country Link
WO (1) WO2024171433A1 (fr)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023012954A1 (fr) * 2021-08-04 2023-02-09 株式会社Ｎｔｔドコモ Terminal, procédé de communication sans fil et station de base

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023012954A1 (fr) * 2021-08-04 2023-02-09 株式会社Ｎｔｔドコモ Terminal, procédé de communication sans fil et station de base

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
SHINYA KUMAGAI, NTT DOCOMO, INC.: "Discussion on dynamic switching between DFT-S-OFDM and CP-OFDM", 3GPP DRAFT; R1-2212011; TYPE DISCUSSION; NR_COV_ENH2-CORE, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. 3GPP RAN 1, no. Toulouse, FR; 20221114 - 20221118, 7 November 2022 (2022-11-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052222575 *
XIANGHUI HAN, ZTE: "Discussion on dynamic waveform switching", 3GPP DRAFT; R1-2211049; TYPE DISCUSSION; NR_COV_ENH2-CORE, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. 3GPP RAN 1, no. Toulouse, FR; 20221114 - 20221118, 7 November 2022 (2022-11-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052221614 *

Similar Documents

Publication Publication Date Title
WO2024171433A1 (fr) Équipement utilisateur, procédé de communication sans fil, et station de base
WO2024069706A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024069708A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024069707A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024209667A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024209666A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024085130A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024095468A1 (fr) Terminal, procédé de communication sans fil, et station de base
WO2024095469A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024075279A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024171383A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024171382A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024095363A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024095364A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024122035A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024209645A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024157357A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024157358A1 (fr) Terminal, procédé de communication sans fil, et station de base
WO2024080027A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024181362A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024181361A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024134881A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024134882A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024075273A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024201856A1 (fr) Terminal, procédé de communication sans fil et station de base

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23922767

Country of ref document: EP

Kind code of ref document: A1