WO2024181530A1 - Terminal, procédé de communication sans fil et station de base - Google Patents

Terminal, procédé de communication sans fil et station de base Download PDF

Info

Publication number
WO2024181530A1
WO2024181530A1 PCT/JP2024/007539 JP2024007539W WO2024181530A1 WO 2024181530 A1 WO2024181530 A1 WO 2024181530A1 JP 2024007539 W JP2024007539 W JP 2024007539W WO 2024181530 A1 WO2024181530 A1 WO 2024181530A1
Authority
WO
WIPO (PCT)
Prior art keywords
dmrs
ports
port
occ
cdm
Prior art date
Application number
PCT/JP2024/007539
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 株式会社Ｎｔｔドコモ
Publication of WO2024181530A1 publication Critical patent/WO2024181530A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/06—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/24—Cell structures
    • H04W16/28—Cell structures using beam steering
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H04W72/232—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal the control data signalling from the physical layer, e.g. DCI signalling

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
  • multi-port reference signals e.g., demodulation reference signals (DMRS)
  • DMRS demodulation reference signals
  • one of the objectives of this disclosure is to provide a terminal, a wireless communication method, and a base station that use an appropriate combination of DMRS ports.
  • a terminal has a receiver that receives downlink control information indicating multiple demodulation reference signal (DMRS) ports in two code division multiplexing (CDM) groups for a physical downlink shared channel using a rank greater than four and including two codewords, and a controller that determines whether one of the two CDM groups corresponds to the two codewords or one of the two codewords.
  • DMRS demodulation reference signal
  • CDM code division multiplexing
  • a suitable combination of DMRS ports can be used.
  • FIG. 1 shows an example of an existing DMRS port table for DMRS configuration type 1/2 for PDSCH.
  • FIG. 2 shows an example of an existing DMRS port table for DMRS configuration type 1/2 for PUSCH.
  • Figures 3A-3C are diagrams showing an example of a new OCC (Orthogonal Cover Code).
  • 4A-4B are diagrams showing an example of association of CDM groups, DMRS ports, and OCCs in Extension Type 1/Extended Type 2.
  • FIG. 6 shows an example of an antenna port table according to embodiment #1.
  • 7A and 7B show an example of an antenna port table according to embodiment #2.
  • FIG. 8 shows an example of an antenna port table according to variation #1.
  • FIG. 9 shows an example of an antenna port table according to variation #2.
  • FIG. 10 shows an example of an antenna port table according to variation #3.
  • FIG. 11 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment.
  • FIG. 12 is a diagram illustrating an example of the configuration of a base station according to an embodiment.
  • FIG. 13 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment.
  • FIG. 14 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment.
  • FIG. 15 is a diagram illustrating an example of a vehicle according to an embodiment.
  • DMRS Demodulation Reference Signal
  • UE User Equipment
  • MCS modulation and coding scheme
  • DMRS mapping type A or B For the time domain, DMRS mapping type A or B is configured.
  • DMRS position l_0 is counted by the symbol index in the slot.
  • l_0 is configured by the parameter (dmrs-TypeA-Position) in the MIB or common serving cell configuration (ServingCellConfigCommon).
  • DMRS position 0 (reference point l) means the first symbol of the slot or each frequency hop.
  • DMRS mapping type B DMRS position l_0 is counted by the symbol index in the PDSCH/PUSCH. l_0 is always 0.
  • DMRS position 0 (reference point l) means the first symbol of the PDSCH/PUSCH or each frequency hop.
  • DMRS location is defined by a table in the specification and depends on the duration of PDSCH/PUSCH. The location of additional DMRS is fixed.
  • DMRS setting type 1 For the frequency domain, (PDSCH/PUSCH) DMRS setting type 1 or 2 is set.
  • DMRS setting type 2 is applicable only to CP-OFDM.
  • Single symbol DMRS or double symbol DMRS is configured.
  • Single-symbol DMRS is normally used (mandatory in Rel. 15).
  • the number of additional DMRS is ⁇ 0,1,2,3 ⁇ .
  • Single-symbol DMRS supports both frequency hopping enabled and disabled. If maxLength in the uplink DMRS configuration (DMRS-UplinkConfig) is not set, single-symbol DMRS is used.
  • Double symbol DMRS is used for more DMRS ports (especially Multi User Multi Input Multi Output (MU-MIMO)).
  • double symbol DMRS the number of additional DMRS (symbols) is ⁇ 0,1 ⁇ . Double symbol DMRS is supported when frequency hopping is disabled. If the maxLength in the uplink DMRS configuration (DMRS-UplinkConfig) is 2 (len2), whether it is single symbol DMRS or double symbol DMRS is determined by DCI or configured grant.
  • the possible setting patterns for DMRS are the following combinations: DMRS setting type 1, DMRS mapping type A, single symbol DMRS DMRS setting type 1, DMRS mapping type A, double symbol DMRS DMRS setting type 1, DMRS mapping type B, single symbol DMRS DMRS setting type 1, DMRS mapping type B, double symbol DMRS DMRS setting type 2, DMRS mapping type A, single symbol DMRS DMRS setting type 2, DMRS mapping type A, double symbol DMRS DMRS setting type 2, DMRS mapping type B, single symbol DMRS DMRS setting type 2, DMRS mapping type B, double symbol DMRS mapping type 2, DMRS mapping type B, double symbol DMRS mapping type B, double symbol DMRS mapping type B, double symbol DMRS mapping type B, double symbol DMRS setting type 2, DMRS mapping type B, double symbol DMRS mapping type B, double symbol DMRS setting type 2, DMRS mapping type B, double symbol DMRS mapping type B, double symbol DMRS setting type 2, DMRS mapping
  • CDM Code Division Multiplexing
  • DMRS setting type 1 and single symbol DMRS four DMRS ports can be used.
  • FD OCC Frequency Domain OCC
  • FDM Frequency Division Multiplexing
  • each DMRS CDM group two DMRS ports are multiplexed by an FD OCC of length 2, and two DMRS ports are multiplexed by a TD OCC (Time Domain OCC). Between multiple DMRS CDM groups (two DMRS CDM groups), two DMRS ports are multiplexed by FDM.
  • each DMRS CDM group two DMRS ports are multiplexed by an FD OCC of length 2. Between multiple DMRS CDM groups (three DMRS CDM groups), three DMRS ports are multiplexed by FDM.
  • each DMRS CDM group 12 DMRS ports can be used.
  • two DMRS ports are multiplexed by an FD OCC of length 2, and two DMRS ports are multiplexed by a TD OCC.
  • three DMRS ports are multiplexed by FDM.
  • DMRS mapping type B is shown, but DMRS mapping type A is similar.
  • DMRS ports 1000-1007 can be used for DMRS setting type 1
  • DMRS ports 1000-1011 can be used for DMRS setting type 2.
  • DMRS ports 0-7 can be used for DMRS setting type 1
  • DMRS ports 0-11 can be used for DMRS setting type 2.
  • DMRS demodulation reference signals
  • CSI-RS CSI-RS
  • a different DMRS port/CSI-RS port may be set for each layer.
  • SU-MIMO Single User MIMO
  • MU-MIMO Multi User MIMO
  • a different DMRS port/CSI-RS port may be set for each layer within one UE and for each UE.
  • multiple-port DMRS can be supported with up to eight ports for Type 1 DMRS (in other words, DMRS setting type 1) and up to 12 ports for Type 2 DMRS (in other words, DMRS setting type 2) by using Frequency Division Multiplexing (FDM), Frequency Domain Orthogonal Cover Code (FD-OCC), Time Domain OCC (TD-OCC), etc.
  • FDM Frequency Division Multiplexing
  • FD-OCC Frequency Domain Orthogonal Cover Code
  • TD-OCC Time Domain OCC
  • a comb-like transmission frequency pattern (comb-like resource set) is used for the FDM.
  • Cyclic Shift (CS) is used for the FD-OCC.
  • the TD-OCC can be applied only to double-symbol DMRS.
  • the OCC disclosed herein may be interchangeably read as orthogonal code, orthogonalization, cyclic shift, etc.
  • the DMRS type may also be referred to as the DMRS configuration type.
  • DMRS that are resource-mapped in units of two consecutive (adjacent) symbols may be called double-symbol DMRS, and DMRS that are resource-mapped in units of one symbol may be called single-symbol DMRS.
  • Either DMRS may be mapped to one or more symbols per slot depending on the length of the data channel.
  • the DMRS mapped to the start of the data symbol may be called a front-loaded DMRS, and the DMRS additionally mapped to other positions may be called an additional DMRS.
  • Comb and CS may be used for orthogonalization.
  • up to four antenna ports (APs) may be supported by using two types of Comb and two types of CS (Comb2+2CS).
  • Comb, CS and TD-OCC may be used for orthogonalization.
  • up to eight APs may be supported using two types of Comb, two types of CS and TD-OCC ( ⁇ 1,1 ⁇ and ⁇ 1,-1 ⁇ ).
  • FD-OCC may be used for orthogonalization.
  • up to six APs may be supported by applying an orthogonal code (2-FD-OCC) to two adjacent resource elements (REs) in the frequency direction.
  • FD-OCC and TD-OCC may be used for orthogonalization.
  • up to 12 APs may be supported by applying an orthogonal code (2-FD-OCC) to two adjacent REs in the frequency direction and a TD-OCC ( ⁇ 1,1 ⁇ and ⁇ 1,-1 ⁇ ) to two adjacent REs in the time direction.
  • 2-FD-OCC orthogonal code
  • TD-OCC ⁇ 1,1 ⁇ and ⁇ 1,-1 ⁇
  • a group of DMRS ports that are orthogonalized by the FD-OCC/TD-OCC as described above is also called a Code Division Multiplexing (CDM) group.
  • CDM Code Division Multiplexing
  • Different CDM groups are orthogonal because they are FDM-multiplexed.
  • the orthogonality of the applied OCC may be lost due to channel fluctuations, etc.
  • signals within the same CDM group are received with different reception powers, a near-far problem may occur and orthogonality may not be guaranteed.
  • the DMRS mapped to a resource element (RE) may correspond to a sequence obtained by multiplying the DMRS sequence by a parameter (which may be called a sequence element, etc.) w f (k') of the FD-OCC and a parameter (which may be called a sequence element, etc.) w t (l') of the TD-OCC.
  • OCC length 2
  • Rel. 15 Type 1/Type 2 DMRS ports e.g., rel.15 Type1/Type2 DMRS ports
  • the two existing DMRS port tables for PDSCH mentioned above correspond to DMRS setting types 1 and 2, respectively.
  • p indicates the antenna port number
  • ⁇ indicates the parameter for shifting (offsetting) the frequency resource.
  • FDM is applied to antenna ports 1000-1001 and antenna ports 1002-1003 (and also antenna ports 1004-1005 in the case of Type 2) by applying different values of ⁇ . Therefore, antenna ports 1000-1003 (or 1000-1005) corresponding to single-symbol DMRS are orthogonalized using FD-OCC and FDM.
  • the antenna ports 1000-1007 (or 1000-1011) corresponding to double symbol DMRS are orthogonalized using FD-OCC, TD-OCC, and FDM.
  • CP-OFDM For CP-OFDM only, the following are being considered: specifying a larger number of orthogonal DMRS ports for DL/UL MU-MIMO (without increasing DMRS overhead); common design between DL and UL DMRS; up to 24 orthogonal DMRS ports; doubling the maximum number of orthogonal DMRS ports for both single-symbol DMRS and double-symbol DMRS for each applicable DMRS configuration type.
  • ⁇ Option 1> Introduction of a new OCC with a length greater than the existing OCC (e.g. 4 or 6).
  • the items to be considered include the possibility of performance degradation when the delay spread is large, the possibility of scheduling restrictions, and backward compatibility.
  • TD-OCC on non-contiguous multiple DMRS symbols (eg, TD-OCC on front-loaded/additional DMRS).
  • considerations include possible performance degradation at high UE speeds, possible scheduling restrictions (e.g., how frequency hopping is applied), possible restrictions on DMRS configuration (e.g., limiting the number of additional DMRS), and backward compatibility.
  • ⁇ Option 3> Increase the number of CDM groups (e.g. increase the number of combs/FDMs).
  • issues to be considered include the possibility of performance degradation when the delay spread is large, and backward compatibility.
  • ⁇ Option 4> Reuse symbols for additional DMRS to increase the number of orthogonal DMRS ports.
  • considerations include the possibility of performance degradation at high UE speeds, the possibility of DMRS configuration restrictions (e.g., limiting the number of additional DMRS), and backward compatibility.
  • TD-OCC Use of TD-OCC on non-contiguous multiple DMRS symbols in combination with FD-OCC/FDM (reuse additional DMRS symbols to improve channel estimation performance).
  • considerations include possible performance degradation at high UE speeds, possible scheduling restrictions (e.g., how frequency hopping is applied), possible restrictions on DMRS configuration (e.g., limiting the number of additional DMRS), and backward compatibility.
  • Options 1/3 may be supported.
  • TD OCC may be supported.
  • the difference between options 2 and 5 may be whether they support semi-static switching based on RRC or dynamic switching based on DCI between FD-OCC and TD-OCC.
  • option 5 of the above-mentioned method for increasing the number of DMRS ports as in the example of FIG. 3, a new FD-OCC of length 4 is applied, and a new TD-OCC of length 2 is applied to multiple discontinuous DMRS symbols, and the number of DMRS ports in one CDM group may be 4.
  • the receiving side can separate the signals by decoding either the FD-OCC or the TD-OCC, which is more advantageous than option 1/3.
  • the receiving side can decode using only the FD-OCC.
  • problems such as degradation of characteristics (orthogonality) during high-speed movement due to the use of TD-OCC, or delay in PDSCH decoding due to the inability to start channel estimation even when only the preceding DMRS symbol is received and the need to receive additional DMRS symbols, arise, the receiving side can decode using only the FD-OCC.
  • problems such as degradation of characteristics (orthogonality) when the delay spread is large due to the use of FD-OCC arise, the receiving side can decode using only the TD-OCC.
  • a new FD-OCC of length 6 is applied, and a new TD-OCC of length 2 may be applied to multiple non-contiguous DMRS symbols.
  • DMRS ports for Type 1/Type 2 for Rel. 18 and later may be referred to as, for example, Rel. 18 enhanced type 1/enhanced type 2 DMRS ports.
  • Enhanced type 1/enhanced type 2 may be referred to as eType 1/eType 2.
  • Rel. 18 eType1/eType2 DMRS ports may be defined with DMRS ports with FD-OCC length > 2.
  • the FD-OCC length of a Rel. 18 eType1/eType2 DMRS port may be 4.
  • a port index p #1000-1015.
  • DMRS port #1000-#1007 the same DMRS port index as the Rel. 15 DMRS ports may be used.
  • DMRS port #1008-#1015 a different DMRS port index (DMRS port #1008-#1015) may be used.
  • DMRS ports with new FD-OCC #0 1, the same DMRS port index (DMRS port #1000-#1011) as Rel. 15 DMRS ports may be used.
  • DMRS ports with new FD-OCC #2 3, a different DMRS port index (DMRS port #1012-#1023) than Rel. 15 DMRS ports may be used.
  • FD-OCC of length 4 and TD-OCC of length 2 are supported as new OCCs for DMRS (extended type 1/extended type 2 DMRS) of PDSCH/PUSCH.
  • Figures 3A to 3C are diagrams showing examples of new OCCs.
  • FD-OCC and TD-OCC may be simply referred to as OCCs.
  • a length 4 FD-OCC based on a 4-row, 4-column Walsh matrix may be defined.
  • the Walsh matrix may be interpreted as a Hadamard code (e.g., a Hadamard code).
  • An OCC based on a Walsh matrix (sequence) is useful for DL reception (e.g., reception of PDSCH).
  • a length 4 OCC based on cyclic shift may be defined.
  • Cyclic shift based OCC is useful for UL transmission (e.g., PUSCH transmission).
  • a TD-OCC of length 2 may be defined.
  • a table for Extended Type 1/Extended Type 2 DMRS (association of port index, CDM group index, and new OCC index) may be defined.
  • the port index of the PDSCH may be indicated by a number obtained by adding 1000 to the port index of the PUSCH.
  • the new FD-OCC may be any of the OCCs listed above.
  • the first and second halves of OCCs #0 and #1 (OCCs corresponding to OCC indexes 0 and 1) of length 4 are the same as, for example, OCCs #0 and #1 (OCCs corresponding to OCC indexes 0 and 1) of length 2 shown in Figure 3C.
  • OCC FD-OCC/TD-OCC corresponding to OCC index i
  • OCC#i OCC#i
  • Some of the new FD-OCC's multiple series may be associated with a Rel. 15 DMRS port index.
  • the Rel. 15 DMRS port table for DMRS configuration type 1 and the Rel. 15 DMRS port table for DMRS configuration type 2 may be used.
  • DMRS maximum length and maxLength may be interpreted interchangeably.
  • the existing FD-OCC, the FD-OCC of length 2, the Rel. 15 FD-OCC, and wf (k') may be interchanged.
  • the new FD-OCC, the FD-OCC longer than 2, the Rel. 18 FD-OCC, and wf (k') may be interchanged.
  • CDM group multiple DMRS ports that are mapped to the same RE (time and frequency resource) may be referred to as a DMRS CDM group.
  • FIG. 4A is a diagram showing an example of association between a CDM group, a DMRS port, and an OCC in an extended type 1.
  • FIG. 4B is a diagram showing an example of association between a CDM group, a DMRS port, and an OCC in an extended type 2.
  • the DMRS ports in FIG. 4A and FIG. 4B may be called extended DMRS ports. Note that FIG. 4A and FIG. 4B are applicable to both single symbol DMRS and double symbol DMRS.
  • DMRS ports can be used for DMRS setting extension type 1 and single symbol DMRS.
  • DMRS CDM group#0-1 four DMRS ports (port#0-1, 8-9, port#2-3, 10-11) are multiplexed by an FD-OCC (FD-OCC#0-3) of length 4.
  • FD-OCC#0-3 FD-OCC#0-3 of length 4.
  • DMRS setting extension type 1 and double symbol DMRS eight more DMRS ports (ports #4-7, 12-15) can be used.
  • each DMRS CDM group (CDM group #0-1), four DMRS ports (ports #4-5, 12-13, port #6-7, 14-15) are multiplexed by an FD-OCC #0-3 of length 4.
  • two DMRS ports are multiplexed by FDM.
  • two DMRS ports in the time direction are multiplexed by a TD-OCC #0-1 of length 2. That is, multiple (two) CDM groups with the same index are multiplexed by TDM.
  • the DMRS ports corresponding to CDM group #0 are ⁇ port#0,1,8,9 ⁇ and ⁇ port#4,5,12,13 ⁇
  • the DMRS ports corresponding to CDM group #1 are ⁇ port#2,3,10,11 ⁇ and ⁇ port#6,7,14,15 ⁇ .
  • 12 DMRS ports can be used for DMRS setting extension type 2 and single symbol DMRS.
  • each DMRS CDM group (CDM group #0-2), four DMRS ports (ports #0-1, 12-13, port #2-3, 14-15, port #4-5, 16-17) are multiplexed by an FD-OCC (FD-OCC #0-3) of length 4.
  • FD-OCC #0-3 FD-OCC #0-3
  • DMRS ports #6-11, 18-23) 12 more DMRS ports (ports #6-11, 18-23) can be used.
  • each DMRS CDM group (CDM group #0-2)
  • four DMRS ports (ports #6-7, 18-19, port #8-9, 20-21, port #10-11, 22-23) are multiplexed by an FD-OCC #0-3 of length 4.
  • three DMRS ports are multiplexed by FDM.
  • two DMRS ports in the time direction are multiplexed by a TD-OCC #0-1 of length 2. That is, multiple (two) CDM groups with the same index are multiplexed by TDM.
  • the DMRS ports corresponding to CDM group #0 are ⁇ port#0,1,12,13 ⁇ and ⁇ port#6,7,18,19 ⁇
  • the DMRS ports corresponding to CDM group #1 are ⁇ port#2,3,14,15 ⁇ and ⁇ port#8,9,20,21 ⁇
  • the DMRS ports corresponding to CDM group #2 are ⁇ port#4,5,16,17 ⁇ and ⁇ port#10,11,22,23 ⁇ .
  • the DMRS port for PDSCH is determined by p+1000.
  • MU-MIMO Scheduling Constraints For MU-MIMO, multiple DMRSs for multiple UEs are multiplexed. Multiple DMRSs may be CDMed using different OCCs within one CDM group, or FDMed using different subcarriers (Comb) between multiple CDM groups. In CDM, a problem occurs due to the difference in distance from the base station to multiple UEs (far-near problem). If FD-OCC is used in a flat fading environment, no inter-symbol interference occurs, but if FD-OCC is used in a frequency selective fading environment, inter-symbol interference occurs and quality deteriorates. To prevent this, MU-MIMO scheduling constraints (existing MU-MIMO scheduling constraints) are specified.
  • DMRS configuration type 1 if a UE is scheduled with one codeword (CW) and assigned an antenna port mapping with indices ⁇ 2, 9, 10, 11, 30 ⁇ in the existing antenna port table for DMRS configuration type 1, or if the UE is scheduled with two CWs, the UE may assume that the remaining orthogonal antenna ports are not associated with transmitting PDSCH to another UE.
  • CW codeword
  • the UE may adhere to at least one of the following constraints:
  • Constraint 1 Existing MU-MIMO scheduling constraints apply, which means that many DMRS ports cannot be used by other UEs, e.g., for ranks greater than 4, 2CW, if category 1/2 DMRS port combinations are used, the free ports cannot be used by other UEs.
  • Constraint 2 The MU-MIMO scheduling constraints are updated.
  • the UE may comply with at least one of the following constraints: --Constraint 2-1 No existing MU-MIMO scheduling constraints: There may be no MU-MIMO scheduling constraints for Rel. 18 DMRS ports. --Constraint 2-2 Some new MU-MIMO scheduling constraints are introduced. --Constraint 2-3 There is no MU-MIMO scheduling constraint across different CDM groups, and a new MU-MIMO scheduling constraint within one CDM group is introduced.
  • the MU-MIMO scheduling constraint in constraint 1 may be that in extended type 2, when a DMRS port combination using two CDM groups #0 and #1 is indicated, a DMRS port in another CDM group #2 cannot be applied to another UE.
  • the MU-MIMO scheduling constraint in constraint 2-3 may be such that, in extended type 2, when a DMRS port combination using two CDM groups #0 and #1 is indicated, a DMRS port in another CDM group #2 may be assigned to another UE.
  • the antenna port table in Figure 5 includes DMRS port combination #0 ⁇ 0,1,2,3,8 ⁇ , DMRS port combination #1 ⁇ 0,1,2,3,8,10 ⁇ , DMRS port combination #2 ⁇ 0,1,2,3,8,9,10 ⁇ , and DMRS port combination #3 ⁇ 0,1,2,3,8,9,10,11 ⁇ for the two codeword (CW) case (CW0 is enabled, CW1 is enabled).
  • DMRS port combinations #0 to #3 may be associated with antenna port field values 0 to 3, respectively. In each of the DMRS port combinations #0 to #3, there are cases where one CDM group (multiple DMRS ports in one CDM group) corresponds to two codewords.
  • Such an antenna port table can cause problems such as a high processing load on the UE and the UE being unable to support 2CW for PDSCH with ranks higher than 4. If such problems occur, there is a risk of a decrease in communication throughput/communication quality.
  • the inventors therefore came up with a method for specifying antenna ports.
  • 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
  • information elements IEs
  • settings etc.
  • MAC Control Element CE
  • 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
  • CORESET pool may be read as CORESET pool index and vice versa.
  • the notation "Rel. XX” indicates a 3GPP release.
  • the release number “XX” is an example and may be replaced with another number.
  • DMRS, DL DMRS, UL DMRS, PDSCH DMRS, and PUSCH DMRS may be interpreted as interchangeable.
  • RE may be read as interchangeable.
  • orthogonal sequence OCC, FD OCC, and TD OCC may be interpreted as interchangeable.
  • DMRS port, antenna port, port, DMRS port index may be interchanged.
  • DMRS CDM group, CDM group, DMRS group, DMRS CDM group(s) without data, etc. may be interchanged.
  • antenna port indication and antenna port field may be interchanged.
  • DMRS configuration type, DMRS type, and the RRC parameter "dmrs-Type" may be interchanged.
  • DMRS maximum length, DMRS maximum number of symbols, DMRS number of symbols, and the RRC parameter "maxLength" may be interchanged.
  • DMRS type 1 may mean that the RRC parameter "dmrs-Type" is not set (e.g., the RRC parameter "dmrs-Type" is absent in the DMRS configuration (DMRS-DownlinkConfig information element/DMRS-UplinkConfig information element)), or that 1 (or type 1) is set as the RRC parameter related to the DMRS type.
  • CDM group list may be interchangeable.
  • CDM group subset may be interchangeable.
  • the rank, transmission rank, number of layers, and number of antenna ports may be interchangeable.
  • the application of one codeword and the number of layers being four or less may be interchangeable.
  • the application of two codewords and the number of layers being greater than four may be interchangeable.
  • transform precoding is configured
  • transform precoding is enabled
  • a table may be interpreted as one or more tables.
  • 8Tx and UL transmission of more than 4 layers/ranks may be interpreted interchangeably.
  • Rel. 15 DMRS port, Rel. 15 Type 1/2 DMRS port, and existing DMRS port may be interchangeable.
  • Rel. 18 DMRS port, Rel. 18 Extended Type 1/2 DMRS port, and new DMRS port may be interchangeable.
  • a Rel. 18 DMRS port may correspond to a DMRS port with a total number of ports that is twice or more (e.g., two times, three times, four times, ...) that of a Rel. 15 DMRS port.
  • a DMRS in which the use of a Rel. 15 DMRS port is set or the use of a Rel. 18 DMRS port is not set (enabled) may be referred to as a Rel. 15 DMRS.
  • a DMRS in which the use of a Rel. 18 DMRS port is set (enabled) may be referred to as a Rel. 18 DMRS.
  • a DMRS for type 1/2 may be referred to as a Rel. 15 type 1/2 DMRS, simply type 1/2 DMRS, etc.
  • a DMRS for extended type 1/2 may be referred to as a Rel. 18 extended type 1/2 DMRS, simply extended type 1/2 DMRS, etc.
  • Rel. 15 DMRS configuration type, DMRS configuration type, and type may be interchangeable.
  • Rel. 18 DMRS configuration type, extended DMRS configuration type, extended type, and e-type may be interchangeable.
  • the antenna port table, the antenna port instruction table, the association between the antenna port field value and the DMRS port, the association between the antenna port field value and the DMRS port, the number of DMRS CDM groups without data and the DMRS port, and the association between the antenna port field value and the DMRS port, the number of DMRS CDM groups without data and the DMRS port and the number of preceding symbols may be read as interchangeable.
  • the DMRS port combination, the combination of DMRS ports, and one or more DMRS ports corresponding to one value of the antenna port field may be read as interchangeable.
  • the value of the antenna port field may be interpreted as a row index.
  • the terms "the Rel. 18 DMRS port is set” and “the DMRS extension type 1/2 is set” may be interpreted as interchangeable.
  • the antenna port field value, the number of DMRS CDM groups without data, and the DMRS port are merely examples, and other values may be specified.
  • Each embodiment may be applied to the DMRS of the PDSCH or the DMRS of the PUSCH.
  • the PUSCH DMRS port index may be expressed as p, and the PDSCH DMRS port index may be expressed as p+1000. Furthermore, p may be replaced with Value (row index) in the table of the present disclosure.
  • DMRS port combinations in the existing antenna port table may be reused. In this case, only DMRS ports among DMRS ports 0 to 7 may be specified for DMRS extension type 1, and only DMRS ports among DMRS ports 0 to 11 may be specified for DMRS extension type 2.
  • the DMRS port of the PDSCH may be specified by the antenna port field in the DCI format for scheduling the PDSCH (e.g., DCI format 1_1/1_2).
  • the DMRS port of the PUSCH may be specified by the antenna port field in the DCI format for scheduling the PUSCH (e.g., DCI format 0_1/0_2).
  • the UE may refer to a new antenna port table (which may also be called an antenna port table, antenna port indication table, etc.) to determine the antenna port that corresponds to the value of the antenna port field.
  • a new antenna port table which may also be called an antenna port table, antenna port indication table, etc.
  • the new antenna port table may be a table for Rel.18 Extended Type 1/2 DMRS ports.
  • the new DMRS port combination of Category 2 may be a combination in which X is added to the port index in the DMRS port combination of Category 1.
  • X may be a number equal to or greater than 8 (e.g., 8) in the case of eType 1, and may be a number equal to or greater than 12 (e.g., 12) in the case of eType 2.
  • the above X may be predefined in a standard, may be set in the UE by higher layer signaling, or may be determined based on the UE capabilities.
  • the X may be called an offset indicator (offset index), or simply an offset.
  • Category 3 legacy and new DMRS ports may, for example, fall into the following combinations: Number of ranks in the CDM group: 3 or 4.
  • CDM group index 0,1 for eType1. 0,1,2 for eType2.
  • the number of CDM groups without data 1, 2 for eType 1; 1, 2, 3 for eType 2.
  • legacy DMRS ports and new DMRS ports of Category 3 do not have to include all of the above combinations.
  • the number of CDM groups without data corresponding to legacy DMRS ports and new DMRS ports of Category 3 may be specified as either 1 and/or 2 (corresponding code points) in the antenna port table for eType1, and may be specified as either 1, 2, and/or 3 (corresponding code points) in the antenna port table for eType2.
  • a Category 3 DMRS port may be a legacy DMRS port and a new DMRS port of a particular rank (e.g., rank 3/4) within the same CDM group.
  • the above combination may be applied in at least a single TRP.
  • CDM group for ranks up to 4, only one CDM group may be used per UE.
  • multiple CDM groups may be used per UE.
  • an example of an antenna port table for PDSCH DMRS is shown, but the scope of coverage of the present disclosure is not limited to this.
  • the antenna port table (method of configuring the antenna port table) in the following embodiment may be appropriately interpreted as an antenna port table (method of configuring the antenna port table) for PUSCH DMRS.
  • the DCI in the following embodiments may correspond to a DCI format for PDSCH (e.g., DCI format 1_1/1_2) or a DCI format for PUSCH (e.g., DCI format 0_1/0_2).
  • a DCI format for PDSCH e.g., DCI format 1_1/1_2
  • a DCI format for PUSCH e.g., DCI format 0_1/0_2
  • the antenna port table for PUSCH DMRS may include only DMRS ports for one rank, unlike the antenna port table for PDSCH DMRS.
  • the UE may be instructed on the number of ranks (number of layers) for PUSCH DMRS, for example, using the precoding information and number of layers fields.
  • the antenna port table in the following embodiment shows an example in which all of the above category 1-3 DMRS port combinations are included in any of the DCI code points (or row entries in the table), but is not limited to this.
  • an antenna port table that does not include at least one of the category 1, 2, and 3 DMRS port combinations may be constructed/used based on the contents of this disclosure.
  • the "Notes" column is supplementary explanation and may not be included in the table (may not be specified).
  • not all rows may be specified for each category (some rows may be omitted), and rows (combinations) that are not listed may be specified/added.
  • the correspondence between the combination of DMRS port indexes and the number of DMRS CDM groups without data, row indexes, and corresponding entries may be different. That is, the order of the rows may be changed.
  • the index (Value) of the subsequent rows may be moved up.
  • each antenna port table shown below may be specified separately for each of the above (1) and (2) or for each category.
  • the antenna port table to be used may be switched depending on the applied scenario (single TRP/multi-TRP, or any of categories 1 to 3). By switching the antenna port table (the number of rows) depending on the scenario, it is possible to flexibly and efficiently specify the antenna port table.
  • the antenna port table may be specified as a single table that combines the above (1) and (2).
  • the DMRS port of the PDSCH may be indicated not only by the antenna port field in the DCI format for scheduling the PDSCH (e.g., DCI format 1_1/1_2), but also by other existing fields, new DCI fields, or a combination of these fields with the antenna port field.
  • a specific DMRS port may be indicated by combining a new indicator with an existing field such as the Time Domain Resource Assignment/Allocation (TDRA) field/Frequency Domain Resource Assignment/Allocation (FDRA) field.
  • TDRA Time Domain Resource Assignment/Allocation
  • FDRA Frequency Domain Resource Assignment/Allocation
  • the example antenna port table in each embodiment shows a portion corresponding to the case of 2CW (CW0 enabled, CW1 enabled), but may also include a portion corresponding to the case of 1CW (CW0 enabled, CW1 disabled).
  • an antenna port table may be defined in the specification that includes DMRS port combination #4 ⁇ 0,1,2,3,10 ⁇ , DMRS port combination #5 ⁇ 0,1,8,2,3,10 ⁇ , DMRS port combination #6 ⁇ 0,1,8,2,3,10,11 ⁇ , and DMRS port combination #7 ⁇ 0,1,8,9,2,3,10,11 ⁇ in addition to DMRS port combinations #0 to #3.
  • DMRS port combinations #0 to #7 may be associated with antenna port field values 0 to 7, respectively.
  • DMRS port combination #4 for rank 5 DMRS port ⁇ 0,1 ⁇ may correspond to CW0 and CDM group 0, and DMRS port ⁇ 2,3,10 ⁇ may correspond to CW1 and CDM group 1.
  • DMRS port combination #5 for rank 6 DMRS port ⁇ 0,1,8 ⁇ may correspond to CW0 and CDM group 0, and DMRS port ⁇ 2,3,10 ⁇ may correspond to CW1 and CDM group 1.
  • DMRS port combination #6 for rank 7 DMRS port ⁇ 0,1,8 ⁇ may correspond to CW0 and CDM group 0, and DMRS port ⁇ 2,3,10,11 ⁇ may correspond to CW1 and CDM group 1.
  • DMRS port combination #7 for rank 8 DMRS ports ⁇ 0,1,8,9 ⁇ may correspond to CW0 and CDM group 0, and DMRS ports ⁇ 2,3,10,11 ⁇ may correspond to CW1 and CDM group 1.
  • one CW corresponds to a DMRS port in one CDM group.
  • the processing load of the UE is reduced.
  • the UE can use the appropriate DMRS port.
  • a specification may define antenna port table #0 including DMRS port combinations #0 to #3, and antenna port table #1 including DMRS port combinations #4 to #7.
  • DMRS port combinations #0 to #3 may be associated with antenna port field values 0 to 3 in antenna port table #0, respectively.
  • DMRS port combinations #4 to #7 may be associated with antenna port field values 0 to 3 in antenna port table #1, respectively.
  • one CW corresponds to a DMRS port in one CDM group.
  • multiple CWs are not mapped to a single CDM group, reducing the processing load on the UE.
  • the UE can use the appropriate DMRS port.
  • DMRS port combinations #0 to #3 or DMRS port combinations #4 to #7 may be set/instructed (switched) by the RRC IE/MAC CE/DCI, or may be determined (switched) based on the reported UE capability values.
  • antenna port field values 0 to 3 in embodiment #1 or antenna port field values 4 to 7 in embodiment #1 may be set/instructed (switched) by the RRC IE/MAC CE/DCI, or may be determined (switched) based on the reported value of the UE capabilities.
  • antenna port table 0 in embodiment #2 or antenna port table 1 in embodiment #2 may be set/instructed (switched) by the RRC IE/MAC CE/DCI, or may be determined (switched) based on the reported value of the UE capabilities.
  • DMRS port combinations #4 to #7 may be basic features, and DMRS port combinations #0 to #3 may be optional features. UEs that support DMRS port combinations #0 to #3 may also support DMRS port combinations #4 to #7. This functionality/UE capability reduces the processing load on the UE. High-performance UEs can report whether they support DMRS port combinations #0 to #3 via UE capabilities.
  • the antenna port table may include DMRS port combination #0 ⁇ 0,1,2,3,10 ⁇ , DMRS port combination #1 ⁇ 0,1,8,2,3,10 ⁇ , DMRS port combination #2 ⁇ 0,1,8,2,3,10,11 ⁇ , and DMRS port combination #3 ⁇ 0,1,8,9,2,3,10,11 ⁇ .
  • one CW may correspond to one CDM group. In other DMRS port combinations, one CW may correspond to multiple CDM groups.
  • DMRS port combinations #0 to #3 may be defined in the specification.
  • DMRS port combinations #0 to #3 may be associated with antenna port field values 8 to 11, respectively, or with other antenna port field values greater than or equal to 4.
  • An antenna port table #0 including other DMRS port combinations of embodiment #2 and an antenna port table #1 including DMRS port combinations #0 to #3 may be defined in the specification.
  • FIG. 8 shows an example of antenna port table #1 for variation #1.
  • DMRS port combinations #0 to #3 may be associated with antenna port field values 0 to 3 in antenna port table #1, respectively.
  • One or more antenna port tables may include DMRS port combination #0 ⁇ 0,1,2,3,14 ⁇ , DMRS port combination #1 ⁇ 0,1,12,2,3,14 ⁇ , DMRS port combination #2 ⁇ 0,1,12,2,3,14,15 ⁇ , and DMRS port combination #3 ⁇ 0,1,12,13,2,3,14,15 ⁇ .
  • one CW may correspond to one CDM group. In other DMRS port combinations, one CW may correspond to multiple CDM groups.
  • DMRS port combinations #0 to #3 may be defined in the specification.
  • DMRS port combinations #0 to #3 may be associated with antenna port field values 8 to 11, respectively, or with other antenna port field values greater than or equal to 4.
  • An antenna port table #0 including other DMRS port combinations of embodiment #2 and an antenna port table #1 including DMRS port combinations #0 to #3 may be defined in the specification.
  • FIG. 9 shows an example of antenna port table #1 for variation #2.
  • DMRS port combinations #0 to #3 may be associated with antenna port field values 0 to 3 in antenna port table #1, respectively.
  • One or more antenna port tables may include DMRS port combination #0 ⁇ 0,1,2,3,14 ⁇ , DMRS port combination #1 ⁇ 0,1,12,2,3,14 ⁇ , DMRS port combination #2 ⁇ 0,1,12,2,3,14,15 ⁇ , and DMRS port combination #3 ⁇ 0,1,12,13,2,3,14,15 ⁇ .
  • one CW may correspond to one CDM group. In other DMRS port combinations, one CW may correspond to multiple CDM groups.
  • DMRS port combinations #0 to #3 may be defined in the specification.
  • DMRS port combinations #0 to #3 may be associated with antenna port field values 8 to 11, respectively, or with other antenna port field values greater than or equal to 4.
  • An antenna port table #0 including other DMRS port combinations of embodiment #2 and an antenna port table #1 including DMRS port combinations #0 to #3 may be defined in the specification.
  • FIG. 10 shows an example of antenna port table #1 for variation #3.
  • DMRS port combinations #0 to #3 may be associated with antenna port field values 0 to 3 in antenna port table #1, respectively.
  • 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 by the UE from the BS) 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 a new Logical Channel ID (LCID) in the MAC subheader that is not specified in existing standards.
  • LCID Logical Channel ID
  • 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. Supporting a greater number of DMRS ports for PDSCH/PUSCH than in existing specifications. - Support a greater number of DMRS ports than existing specifications by using TD-OCC/FD-OCC/FDM for DMRS of PDSCH/PUSCH. Supports FD OCC of length 4/6. Supports Category 1/2/3 (Category 1/2/3 DMRS ports, Category 1/2/3 DMRS port combinations). Supporting MU-MIMO constraints. Supports DMRS port combinations #4 to #7. Supports DMRS port combinations #0 to #3.
  • 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
  • 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 information indicating that the functions of each embodiment are enabled, any RRC parameters for a specific release (e.g., Rel. 18/19), etc.
  • the UE may, for example, apply Rel. 15/16 operations.
  • Appendix 1 a receiver for receiving downlink control information indicating a plurality of demodulation reference signal (DMRS) ports in two code division multiplexing (CDM) groups for a physical downlink shared channel using a rank greater than four and including two codewords; and a control unit for determining whether one of the two CDM groups corresponds to the two codewords or one of the two codewords.
  • DMRS demodulation reference signal
  • CDM code division multiplexing
  • a first association is defined between a plurality of values of an antenna port field in the downlink control information and a plurality of combinations of the plurality of DMRS ports;
  • a second association is defined between multiple values of an antenna port field in the downlink control information and multiple combinations of the multiple DMRS ports;
  • the first association includes a first case in which the one CDM group corresponds to the two codewords; 4.
  • the second association includes a second case in which the one CDM group corresponds to the one codeword.
  • 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. 11 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 certain 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.
  • SS, SSB, etc. may also be called reference signals.
  • 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 12 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.
  • the control unit 110, the transceiver unit 120, the transceiver antenna 130, and the transmission line interface 140 may each be provided in one or more units.
  • 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 to 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 downlink control information indicating multiple demodulation reference signal (DMRS) ports in two code division multiplexing (CDM) groups for a physical downlink shared channel using a rank greater than four and including two codewords.
  • the controller 110 may determine whether one of the two CDM groups corresponds to the two codewords or one of the two codewords.
  • 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 measurement unit 223 may derive channel measurements for CSI calculation based on channel measurement resources.
  • the channel measurement resources may be, for example, non-zero power (NZP) CSI-RS resources.
  • the measurement unit 223 may derive interference measurements for CSI calculation based on interference measurement resources.
  • the interference measurement resources may be at least one of NZP CSI-RS resources for interference measurement, CSI-Interference Measurement (IM) resources, etc.
  • CSI-IM may be called CSI-Interference Management (IM) or may be interchangeably read as Zero Power (ZP) CSI-RS.
  • CSI-RS, NZP CSI-RS, ZP CSI-RS, CSI-IM, CSI-SSB, etc. may be read as interchangeable.
  • 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 downlink control information indicating multiple demodulation reference signal (DMRS) ports in two code division multiplexing (CDM) groups for a physical downlink shared channel using a rank greater than four and including two codewords.
  • the controller 210 may determine whether one of the two CDM groups corresponds to the two codewords or one of the two codewords.
  • the control unit 210 may determine whether the one CDM group corresponds to the two code words or the one code word based on at least one of the capability information reported by the terminal, the received configuration, and the received instruction.
  • An association may be defined between multiple values of an antenna port field in the downlink control information and multiple combinations of the multiple DMRS ports.
  • the association may include a first case in which the one CDM group corresponds to the two codewords, and a second case in which the one CDM group corresponds to the one codeword.
  • a first association may be defined between multiple values of an antenna port field in the downlink control information and multiple combinations of the multiple DMRS ports.
  • a second association may be defined between multiple values of an antenna port field in the downlink control information and multiple combinations of the multiple DMRS ports.
  • the first association may include a first case in which the one CDM group corresponds to the two codewords.
  • the second association may include a second case in which the one CDM group corresponds to the one codeword.
  • 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, selection, 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. 14 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 configurations 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, a communication module, etc.
  • 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, for example, 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, subframe, slot, minislot, and symbol all represent time units when transmitting a signal.
  • a different name may be used for radio frame, subframe, slot, minislot, and symbol. Note that the time units such as frame, subframe, slot, minislot, and 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 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, etc. in this disclosure are not limiting in any respect. Furthermore, the formulas, etc. 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).
  • the antenna port may be interchangeably read as an antenna port for any signal/channel (e.g., a demodulation reference signal (DMRS) port).
  • the resource may be interchangeably read as a resource for any signal/channel (e.g., a reference signal resource, an SRS resource, etc.).
  • the resource may include time/frequency/code/space/power resources.
  • the spatial domain transmission filter may include at least one of a spatial domain transmission filter and a spatial domain reception filter.
  • beam SRS Resource Indicator (SRI), CORESET, CORESET pool, PDSCH, PUSCH, codeword (CW), transport block (TB), RS, etc. may be interpreted as interchangeable.
  • TCI state downlink TCI state
  • DL TCI state downlink TCI state
  • UL TCI state uplink TCI state
  • unified TCI state common TCI state
  • joint TCI state etc.
  • QCL QCL
  • QCL assumptions QCL relationship
  • QCL type information QCL property/properties
  • specific QCL type e.g., Type A, Type D
  • specific QCL type e.g., Type A, Type D
  • index identifier
  • indicator indication, resource ID, etc.
  • sequence list, set, group, cluster, subset, etc.
  • TCI state ID may be interchangeable.
  • TCI state ID may be interchangeable as “set of spatial relationship information (TCI state)", “one or more pieces of spatial relationship information”, etc.
  • TCI state and TCI may be interchangeable.
  • Spatial relationship information and spatial relationship may be interchangeable.
  • 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. 15 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 also 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 (decision) may be considered to mean “judging (deciding)” resolving, selecting, choosing, establishing, comparing, etc.
  • judgment (decision) may be considered to mean “judging (deciding)” some kind of action.
  • judgment (decision) may be interpreted interchangeably with the actions described above.
  • expect may be read as “be expected”.
  • "expect(s)" ("" may be expressed, for example, as a that clause, a to infinitive, etc.) may be read as “be expected".
  • "does not expect" may be read as "be not expected".
  • "An apparatus A is not expected" may be read as "An apparatus B other than apparatus A does not expect" (for example, if apparatus A is a UE, apparatus B may be a base station).
  • 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.”
  • timing, time, duration, time instance, any time unit e.g., slot, subslot, symbol, subframe
  • period occasion, resource, etc.

Landscapes

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

Abstract

Selon un aspect de la présente divulgation, un terminal comprend : une unité de réception qui reçoit des informations de commande de liaison descendante destinées à un canal physique partagé de liaison descendante qui utilise un rang supérieur ou égal à 4 et contient deux mots de code, les informations de commande de liaison descendante indiquant une pluralité de ports de signaux de référence de démodulation (DMRS) dans deux groupes de multiplexage par répartition en code (CDM) ; et une unité de commande qui détermine si l'un des deux groupes de CDM correspond aux deux mots de code ou à l'un des deux mots de code.
PCT/JP2024/007539 2023-03-02 2024-02-29 Terminal, procédé de communication sans fil et station de base WO2024181530A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2023-031858 2023-03-02
JP2023031858 2023-03-02

Publications (1)

Publication Number Publication Date
WO2024181530A1 true WO2024181530A1 (fr) 2024-09-06

Family

ID=92589935

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2024/007539 WO2024181530A1 (fr) 2023-03-02 2024-02-29 Terminal, procédé de communication sans fil et station de base

Country Status (1)

Country Link
WO (1) WO2024181530A1 (fr)

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
BO GAO, ZTE: "DMRS enhancement for UL/DL MU-MIMO and 8 Tx UL SU-MIMO", 3GPP DRAFT; R1-2300184; TYPE DISCUSSION; NR_MIMO_EVO_DL_UL-CORE, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. 3GPP RAN 1, no. Athens, GR; 20230227 - 20230303, 17 February 2023 (2023-02-17), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052247333 *
PETER GAAL, QUALCOMM INCORPORATED: "Design for increased number of orthogonal DMRS ports", 3GPP DRAFT; R1-2301398; TYPE DISCUSSION; NR_MIMO_EVO_DL_UL-CORE, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. 3GPP RAN 1, no. Athens, GR; 20230227 - 20230303, 17 February 2023 (2023-02-17), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052248531 *

Similar Documents

Publication Publication Date Title
WO2024181530A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024106243A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024157399A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024157400A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024116354A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024116353A1 (fr) Terminal, procédé de communication sans fil, et station de base
WO2024142295A1 (fr) Terminal, procédé de communication sans fil, et station de base
WO2024100737A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024106428A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024106429A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024142296A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024209696A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024209695A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024095427A1 (fr) Terminal, procédé de communication sans fil, et station de base
WO2024075270A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024095426A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024095428A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024085008A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024085007A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024080026A1 (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
WO2024038599A1 (fr) Terminal, procédé de communication sans fil, et station de base
WO2024085203A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024038598A1 (fr) Terminal, procédé de communication sans fil et station de base