WO2022097724A1 - Terminal - Google Patents

Terminal Download PDF

Info

Publication number
WO2022097724A1
WO2022097724A1 PCT/JP2021/040837 JP2021040837W WO2022097724A1 WO 2022097724 A1 WO2022097724 A1 WO 2022097724A1 JP 2021040837 W JP2021040837 W JP 2021040837W WO 2022097724 A1 WO2022097724 A1 WO 2022097724A1
Authority
WO
WIPO (PCT)
Prior art keywords
uci
omega
coding
rate
scaling factor
Prior art date
Application number
PCT/JP2021/040837
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 WO2022097724A1 publication Critical patent/WO2022097724A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/54—Allocation or scheduling criteria for wireless resources based on quality criteria

Definitions

  • the present disclosure relates to a terminal that executes wireless communication, particularly a terminal that executes multiplexing of uplink control information with respect to an uplink control channel.
  • the 3rd Generation Partnership Project (3GPP) specifies the 5th generation mobile communication system (also called 5G, New Radio (NR) or Next Generation (NG)), and next-generation specifications called Beyond 5G, 5G Evolution or 6G. We are also proceeding with the conversion.
  • 5G New Radio
  • NG Next Generation
  • Release 15 of 3GPP supports multiplexing of two or more uplink channels (PUCCH (Physical Uplink Control Channel) and PUSCH (Physical Uplink Shared Channel)) transmitted in the same slot.
  • PUCCH Physical Uplink Control Channel
  • PUSCH Physical Uplink Shared Channel
  • the following disclosure is made in view of such a situation, and an object thereof is to provide a terminal capable of appropriately executing channel coding of uplink control information multiplexed on the uplink control channel.
  • One aspect of the present disclosure is a terminal, wherein a control unit that multiplexes two or more uplink control information having different priorities to an uplink control channel, and the two or more uplink control information are multiplexed.
  • a communication unit that transmits an uplink signal using an uplink control channel is provided, and the control unit includes at least two or more uplink control information in channel coding of the two or more uplink control information.
  • the gist is to apply a specific scaling factor to either uplink control information.
  • FIG. 1 is an overall schematic configuration diagram of the wireless communication system 10.
  • FIG. 2 is a diagram showing a frequency range used in the wireless communication system 10.
  • FIG. 3 is a diagram showing a configuration example of a wireless frame, a subframe, and a slot used in the wireless communication system 10.
  • FIG. 4 is a functional block configuration diagram of the UE 200.
  • FIG. 5 is a diagram showing an operation example.
  • FIG. 6 is a diagram showing an example of the hardware configuration of the UE 200.
  • FIG. 1 is an overall schematic configuration diagram of the wireless communication system 10 according to the embodiment.
  • the wireless communication system 10 is a wireless communication system according to 5G New Radio (NR), and includes a Next Generation-Radio Access Network 20 (hereinafter, NG-RAN20) and a terminal 200 (hereinafter, UE200).
  • NR 5G New Radio
  • NG-RAN20 Next Generation-Radio Access Network 20
  • UE200 terminal 200
  • the wireless communication system 10 may be a wireless communication system according to a method called Beyond 5G, 5G Evolution or 6G.
  • NG-RAN20 includes a radio base station 100A (hereinafter, gNB100A) and a radio base station 100B (hereinafter, gNB100B).
  • gNB100A radio base station 100A
  • gNB100B radio base station 100B
  • the specific configuration of the wireless communication system 10 including the number of gNBs and UEs is not limited to the example shown in FIG.
  • the NG-RAN20 actually contains multiple NG-RANNodes, specifically gNB (or ng-eNB), and is connected to a core network (5GC, not shown) according to 5G.
  • NG-RAN20 and 5GC may be simply expressed as "network”.
  • GNB100A and gNB100B are radio base stations according to 5G, and execute wireless communication according to UE200 and 5G.
  • gNB100A, gNB100B and UE200 are Massive MIMO (Multiple-Input Multiple-Output) and multiple component carriers (CC) that generate beam BM with higher directivity by controlling radio signals transmitted from multiple antenna elements.
  • CC multiple component carriers
  • the DC may include MR-DC (Multi-RAT Dual Connectivity) using MCG (Master Cell Group) and SCG (Secondary Cell Group).
  • MR-DC examples include EN-DC (E-UTRA-NR Dual Connectivity), NE-DC (NR-EUTRA Dual Connectivity) and NR-DC (NR-NR Dual Connectivity).
  • EN-DC E-UTRA-NR Dual Connectivity
  • NE-DC NR-EUTRA Dual Connectivity
  • NR-DC NR-NR Dual Connectivity
  • CCs (cells) used in CA may be considered to form the same cell group.
  • MCG and SCG may be considered to constitute the same cell group.
  • the wireless communication system 10 supports a plurality of frequency ranges (FR).
  • FIG. 2 shows the frequency range used in the wireless communication system 10.
  • the wireless communication system 10 corresponds to FR1 and FR2.
  • the frequency bands of each FR are as follows.
  • FR1 410 MHz to 7.125 GHz
  • FR2 24.25 GHz to 52.6 GHz
  • SCS Sub-Carrier Spacing
  • BW bandwidth
  • FR2 has a higher frequency than FR1, and SCS of 60, or 120 kHz (240 kHz may be included) is used, and a bandwidth (BW) of 50 to 400 MHz may be used.
  • SCS may be interpreted as numerology. Numerology is defined in 3GPP TS38.300 and corresponds to one subcarrier interval in the frequency domain.
  • the wireless communication system 10 also supports a higher frequency band than the FR2 frequency band. Specifically, the wireless communication system 10 corresponds to a frequency band exceeding 52.6 GHz and up to 114.25 GHz. Such a high frequency band may be referred to as "FR2x" for convenience.
  • Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) with a larger Sub-Carrier Spacing (SCS) / Discrete Fourier Transform-Spread (DFT-S-OFDM) may be applied.
  • CP-OFDM Cyclic Prefix-Orthogonal Frequency Division Multiplexing
  • SCS Sub-Carrier Spacing
  • DFT-S-OFDM Discrete Fourier Transform-Spread
  • FIG. 3 shows a configuration example of a wireless frame, a subframe, and a slot used in the wireless communication system 10.
  • one slot is composed of 14 symbols, and the larger (wider) the SCS, the shorter the symbol period (and slot period).
  • the SCS is not limited to the interval (frequency) shown in FIG. For example, 480 kHz, 960 kHz, etc. may be used.
  • the number of symbols constituting one slot does not necessarily have to be 14 symbols (for example, 28, 56 symbols).
  • the number of slots per subframe may vary from SCS to SCS.
  • the time direction (t) shown in FIG. 3 may be referred to as a time domain, a symbol period, a symbol time, or the like.
  • the frequency direction may be referred to as a frequency domain, a resource block, a subcarrier, a BWP (Bandwidth Part), or the like.
  • FIG. 4 is a functional block configuration diagram of UE200.
  • the UE 200 includes a radio signal transmission / reception unit 210, an amplifier unit 220, a modulation / demodulation unit 230, a control signal / reference signal processing unit 240, a coding / decoding unit 250, a data transmission / reception unit 260, and a control unit 270. ..
  • the radio signal transmission / reception unit 210 transmits / receives a radio signal according to NR.
  • the radio signal transmission / reception unit 210 corresponds to Massive MIMO, a CA that bundles a plurality of CCs, and a DC that simultaneously communicates between the UE and each of the two NG-RAN Nodes.
  • the amplifier unit 220 is composed of PA (Power Amplifier) / LNA (Low Noise Amplifier) and the like.
  • the amplifier unit 220 amplifies the signal output from the modulation / demodulation unit 230 to a predetermined power level. Further, the amplifier unit 220 amplifies the RF signal output from the radio signal transmission / reception unit 210.
  • the modulation / demodulation unit 230 executes data modulation / demodulation, transmission power setting, resource block allocation, etc. for each predetermined communication destination (gNB100 or other gNB).
  • Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) / Discrete Fourier Transform-Spread (DFT-S-OFDM) may be applied to the modulation / demodulation unit 230. Further, the DFT-S-OFDM may be used not only for the uplink (UL) but also for the downlink (DL).
  • the control signal / reference signal processing unit 240 executes processing related to various control signals transmitted / received by the UE 200 and processing related to various reference signals transmitted / received by the UE 200.
  • control signal / reference signal processing unit 240 receives various control signals transmitted from the gNB 100 via a predetermined control channel, for example, control signals of the radio resource control layer (RRC). Further, the control signal / reference signal processing unit 240 transmits various control signals to the gNB 100 via a predetermined control channel.
  • a predetermined control channel for example, control signals of the radio resource control layer (RRC).
  • RRC radio resource control layer
  • the control signal / reference signal processing unit 240 executes processing using a reference signal (RS) such as Demodulation Reference Signal (DMRS) and Phase Tracking Reference Signal (PTRS).
  • RS reference signal
  • DMRS Demodulation Reference Signal
  • PTRS Phase Tracking Reference Signal
  • DMRS is a reference signal (pilot signal) known between the base station and the terminal of each terminal for estimating the fading channel used for data demodulation.
  • the PTRS is a terminal-specific reference signal for the purpose of estimating phase noise, which is a problem in high frequency bands.
  • the reference signal may include ChannelStateInformation-ReferenceSignal (CSI-RS), SoundingReferenceSignal (SRS), and PositioningReferenceSignal (PRS) for location information.
  • CSI-RS ChannelStateInformation-ReferenceSignal
  • SRS SoundingReferenceSignal
  • PRS PositioningReferenceSignal
  • control channels include PDCCH (Physical Downlink Control Channel), PUCCH (Physical Uplink Control Channel), RACH (Random Access Channel), Random Access Radio Network Temporary Identifier (RA-RNTI), Downlink Control Information (DCI), and Physical Broadcast Channel (PBCH) etc. are included.
  • PDCCH Physical Downlink Control Channel
  • PUCCH Physical Uplink Control Channel
  • RACH Random Access Channel
  • RA-RNTI Random Access Radio Network Temporary Identifier
  • DCI Downlink Control Information
  • PBCH Physical Broadcast Channel
  • the data channels include PDSCH (Physical Downlink Shared Channel) and PUSCH (Physical Uplink Shared Channel).
  • Data means data transmitted over a data channel.
  • the data channel may be read as a shared channel.
  • the control signal / reference signal processing unit 240 uses an uplink control channel (PUCCH) in which two or more uplink control information (UCI (Uplink Control Information)) having different priorities are multiplexed. It constitutes a communication unit that transmits a link signal.
  • the uplink signal transmitted via PUCCH contains at least UCI.
  • the UCI may include an acknowledgment (HARQ-ACK) for one or more TBs.
  • the UCI may include an SR (Scheduling Request) that requests the scheduling of resources, or may include a CSI (Channel State Information) that represents the state of the channel.
  • the coding / decoding unit 250 executes data division / concatenation and channel coding / decoding for each predetermined communication destination (gNB100 or other gNB).
  • the coding / decoding unit 250 divides the data output from the data transmission / reception unit 260 into predetermined sizes, and executes channel coding for the divided data. Further, the coding / decoding unit 250 decodes the data output from the modulation / demodulation unit 230 and concatenates the decoded data.
  • the data transmission / reception unit 260 executes transmission / reception of Protocol Data Unit (PDU) and Service Data Unit (SDU).
  • the data transmitter / receiver 260 is a PDU / SDU in a plurality of layers (such as a medium access control layer (MAC), a radio link control layer (RLC), and a packet data convergence protocol layer (PDCP)). Assemble / disassemble the.
  • the data transmission / reception unit 260 executes data error correction and retransmission control based on the hybrid ARQ (Hybrid automatic repeat request).
  • the control unit 270 controls each functional block constituting the UE 200.
  • the control unit 270 constitutes a control unit that multiplexes two or more UCIs having different priorities to the PUCCH.
  • the control unit 270 applies a specific scaling factor to at least one of the two or more UCIs in the channel coding of the two or more UCIs.
  • the specific scaling factor may be referred to as omega_LP_HP, omega_HP, or omega_LP.
  • the specific scaling factor is a parameter used in the case where the coding rates of two or more UCIs having different priorities are separately determined.
  • omega_LP_HP may be a parameter applied to LPUCI or a parameter applied to HPUCI.
  • the specific scaling factor satisfies the condition of 0 ⁇ omega_LP_HP (omega_HP or omega_HP) ⁇ 1.
  • the channel coding will be described below. Specifically, the channel coding of UCI in the case of multiplexing different UCIs to PUCCH will be described. Here, the case of multiplexing LP UCI and HP UCI will be illustrated.
  • the UCI may be one or more information elements selected from HARQ-ACK, SR, CSI Part 1, and CSI Part 2.
  • Application Example 1 describes a specific scaling factor (omega_LP_HP) applied to any one of LP UCI and HP UCI. Here it applies to LP UCI to omega_LP_HP.
  • HP UCI coding rate may be the coding rate applied to HP UCI or the coding rate applied to the HP (High Priority) PUCCH resource.
  • These coding rates are the coding rates before omega_LP_HP is multiplied, and may be the coding rate (original coding rate) used in the case where UCIs having different priorities are not multiplexed.
  • the LP UCI coordination may be a coding rate obtained by multiplying HP_UCI_coding_rate by omega_LP_HP.
  • Application example 2 The application example 2 will be described below.
  • Application example 2 describes a specific scaling factor (omega_LP_HP) applied to any one of LP UCI and HP UCI. Here it applies to HP UCI to omega_LP_HP.
  • HP_UCI_coding_rate may be the coding rate obtained by dividing LP_UCI_coding_rate by omega_LP_HP.
  • HP_UCI_coding_rate may be the coding rate obtained by multiplying LP_UCI_coding_rate by the reciprocal of omega_LP_HP.
  • the LPUCI coding rate may be the coding rate applied to LPUCI or the coding rate applied to LP (LowPriority) PUCCH resources. These coding rates are the coding rates before omega_LP_HP is multiplied, and may be the coding rate (original coding rate) used in the case where UCIs having different priorities are not multiplexed.
  • Application Example 3 describes a specific scaling factor (omega_LP_HP) applied to any one of LP UCI and HP UCI.
  • a specific scaling factor (omega_LP_HP) applied to any one of LP UCI and HP UCI.
  • PUCCH format is any one of PUCCH Format 2
  • PUCCH Format 3 and PUCCH Format 4 will be described.
  • Application example 3 describes a case where LP_UCI_coding_rate can be changed without changing HP_UCI_coding_rate.
  • HP UCI coding rate may be the coding rate applied to HP UCI or the coding rate applied to the HP (High Priority) PUCCH resource.
  • These coding rates are the coding rates before omega_LP_HP is multiplied, and may be referred to as the original coding rate.
  • LP_UCI_coding_rate min (omega_LP_HP * HP_UCI_coding_rate, Upper_bound_LP_UCI_coding_rate).
  • Upper_bound_LP_UCI_coding_rate represents the upper limit of LPUCI coordination, and is calculated based on the total number of REs (Resource Elements) of PUCCH resources where LP_UCI is multiplexed, HP_UCI_coding_rate, HPUCIpayload, and LPUCIpayload.
  • the LPUCI payload may be a payload without LPUCI bit bundling or partial dropping, or a payload with LPUCI bit bundling or partial dropping. good.
  • Application example 4 describes a specific scaling factor (omega_LP_HP) applied to any one of LP UCI and HP UCI.
  • a case where the PUCCH format is any one of PUCCH Format 2 PUCCH Format 3 and PUCCH Format 4 will be described.
  • Application example 4 describes a case where both LP_UCI_coding_rate and HP_UCI_coding_rate can be changed.
  • the HP UCI coordination (HP_UCI_coding_rate) and LP UCI coding rate (LP_UCI_coding_rate) may be calculated based on the total number of REs in the PUCCH resource where LP UCI and HP UCI are multiplexed, HP UCI payload, and LP UCI payload. ..
  • the LPUCI payload may be a payload without LPUCI bit bundling or partial dropping, or a payload with LPUCI bit bundling or partial dropping. good.
  • LP_UCI_coding_rate is a coding rate obtained by multiplying HP_UCI_coding_rate by omega_LP_HP may be imposed.
  • Application example 5 The application example 5 will be described below.
  • Application Example 5 describes a case where the specific scaling factor (omega_LP) applied to the LP UCI and the specific scaling factor (omega_HP) applied to the HP UCI are defined separately.
  • Application example 5 illustrates a case where omega_HP is provided without omega_LP being provided.
  • the HP UCI coding rate (HP_UCI_coding_rate) may be the coding rate obtained by multiplying the original coding rate by omega_HP.
  • the original coding rate may be the coding rate applied to the HP UCI or the coding rate applied to the HP PUCCH resource.
  • LP_UCI_coding_rate min (HP_UCI_coding_rate, original coding rate).
  • the original coding rate may be the coding rate applied to the LP UCI, or may be the coding rate applied to the LP PUCCH resource.
  • Application example 6 The application example 6 will be described below.
  • Application Example 6 describes a case where the specific scaling factor (omega_LP) applied to the LP UCI and the specific scaling factor (omega_HP) applied to the HP UCI are defined separately.
  • Application example 5 illustrates a case where omega_LP is provided without providing omega_HP.
  • HP UCI coordination may be the coding rate applied to HP UCI or the coding rate applied to HP PUCCH resources. These coding rates may be referred to as original coding rates.
  • the LP UCI coding rate (LP_UCI_coding_rate) may be the coding rate obtained by multiplying the original coding rate by omega_LP.
  • the original coding rate may be the coding rate applied to the LP UCI, or may be the coding rate applied to the LP PUCCH resource.
  • Application example 7 The application example 7 will be described below.
  • Application Example 7 describes a case where the specific scaling factor (omega_LP) applied to the LP UCI and the specific scaling factor (omega_HP) applied to the HP UCI are defined separately.
  • Application example 7 illustrates a case where both omega_LP and omega_HP are provided.
  • the HP UCI coding rate (HP_UCI_coding_rate) may be the coding rate obtained by multiplying the original coding rate by omega_HP.
  • the original coding rate may be the coding rate applied to the HP UCI or the coding rate applied to the HP PUCCH resource.
  • the LP UCI coding rate (LP_UCI_coding_rate) may be the coding rate obtained by multiplying the original coding rate by omega_LP.
  • the original coding rate may be the coding rate applied to the LP UCI, or may be the coding rate applied to the LP PUCCH resource.
  • Application example 8 describes a case where the specific scaling factor (omega_LP) applied to the LP UCI and the specific scaling factor (omega_HP) applied to the HP UCI are defined separately.
  • the PUCCH format is any one of PUCCH Format 2, PUCCH Format 3 and PUCCH Format 4 will be described.
  • Application example 8 illustrates a case where omega_HP is provided without omega_LP being provided.
  • the HP UCI coding rate (HP_UCI_coding_rate) may be the coding rate obtained by multiplying the original coding rate by omega_HP.
  • the original coding rate may be the coding rate applied to the HP UCI or the coding rate applied to the HP PUCCH resource.
  • LP_UCI_coding_rate min (Upper_bound_LP_UCI_coding_rate, HP_UCI_coding_rate, original coding rate).
  • Upper_bound_LP_UCI_coding_rate represents the upper limit of LPUCI coordination, and is calculated based on the total number of REs (Resource Elements) of PUCCH resources where LP_UCI is multiplexed, HP_UCI_coding_rate, HPUCIpayload, and LPUCIpayload.
  • the LPUCI payload may be a payload without LPUCI bit bundling or partial dropping, or a payload with LPUCI bit bundling or partial dropping. good.
  • the original coding rate may be the coding rate applied to the LP UCI, or may be the coding rate applied to the LP PUCCH resource.
  • Application example 9 The application example 9 will be described below.
  • Application Example 9 describes a case where the specific scaling factor (omega_LP) applied to the LP UCI and the specific scaling factor (omega_HP) applied to the HP UCI are defined separately.
  • the PUCCH format is any one of PUCCH Format 2, PUCCH Format 3 and PUCCH Format 4 will be described.
  • Application example 9 illustrates a case where omega_LP is provided without providing omega_HP.
  • HP UCI coordination may be the coding rate applied to HP UCI or the coding rate applied to HP PUCCH resources. These coding rates may be referred to as original coding rates.
  • LP_UCI_coding_rate min (Upper_bound_LP_UCI_coding_rate, omega_LP * original coding rate).
  • Upper_bound_LP_UCI_coding_rate represents the upper limit of LPUCI coordination, and is calculated based on the total number of REs (Resource Elements) of PUCCH resources where LP_UCI is multiplexed, HP_UCI_coding_rate, HPUCIpayload, and LPUCIpayload.
  • the LPUCI payload may be a payload without LPUCI bit bundling or partial dropping, or a payload with LPUCI bit bundling or partial dropping. good.
  • the original coding rate may be the coding rate applied to the LP UCI, or may be the coding rate applied to the LP PUCCH resource.
  • Application example 10 describes a case where the specific scaling factor (omega_LP) applied to the LP UCI and the specific scaling factor (omega_HP) applied to the HP UCI are defined separately.
  • the PUCCH format is any one of PUCCH Format 2, PUCCH Format 3 and PUCCH Format 4 will be described.
  • Application example 10 illustrates a case where both omega_LP and omega_HP are provided.
  • the HP UCI coding rate (HP_UCI_coding_rate) may be the coding rate obtained by multiplying the original coding rate by omega_HP.
  • the original coding rate may be the coding rate applied to the HP UCI or the coding rate applied to the HP PUCCH resource.
  • LP_UCI_coding_rate min (Upper_bound_LP_UCI_coding_rate, omega_LP * original coding rate).
  • Upper_bound_LP_UCI_coding_rate represents the upper limit of LPUCI coordination, and is calculated based on the total number of REs (Resource Elements) of PUCCH resources where LP_UCI is multiplexed, HP_UCI_coding_rate, HPUCIpayload, and LPUCIpayload.
  • the LPUCI payload may be a payload without LPUCI bit bundling or partial dropping, or a payload with LPUCI bit bundling or partial dropping. good.
  • the original coding rate may be the coding rate applied to the LP UCI, or may be the coding rate applied to the LP PUCCH resource.
  • Radio resource control message The UE 200 may apply a specific scaling factor based on a radio resource control message (RRC message) including an information element that specifies a specific scaling factor.
  • RRC message radio resource control message
  • the RRC message may include an information element that identifies the omega_LP_HP described above.
  • omega_LP_HP is a parameter used in the above-mentioned application examples 1 to 4.
  • omega_LP_HP may be associated with UCIs that have different priorities from each other.
  • UCIs having different priorities may include LP HARQ-ACK and HP HARQ-ACK, or may include HP HARQ-ACK and LP CSI.
  • omega_LP_HP which is commonly applied to UCIs having different priorities, may be set regardless of the combination of HP UCI and LP UCI multiplexed on PUCCH. Separate omega_LP_HP may be set for each combination of HP UCI and LP UCI multiplexed on PUCCH. The combination of HP UCI and LP UCI may be referred to as multiple cases.
  • the RRC message may include an information element that identifies omega_HP as described above.
  • omega_HP is a parameter used in the above-mentioned application examples 5, 7, 8 and 10.
  • omega_HP may be associated with a UCI (HP UCI) that has a high priority.
  • HP UCI may include HP HARQ-ACK or may include HP SR.
  • omega_HP which is commonly applied to UCIs having different priorities, may be set regardless of the combination of HP UCI and LP UCI multiplexed on PUCCH. Separate omega_HP may be set for each combination of HP UCI and LP UCI multiplexed on PUCCH.
  • the RRC message may include an information element that identifies omega_LP as described above.
  • omega_LP is a parameter used in the above-mentioned application examples 6, 7, 9, and 10.
  • omega_LP may be associated with a UCI (LP UCI) having a lower priority.
  • LPUCI may include LPHARQ-ACK or LPCSI.
  • omega_LP which is commonly applied to UCIs having different priorities, may be set regardless of the combination of HP UCI and LP UCI multiplexed on PUCCH. Separate omega_LP may be set for each combination of HP UCI and LP UCI multiplexed on PUCCH.
  • Downlink Control Information UE200 may apply a specific scaling factor based on downlink control information (DCI) including an information element that specifies a specific scaling factor.
  • DCI downlink control information
  • the RRC message may be used to set the possible values for a particular scaling factor.
  • the DCI may include fields to store informational elements that explicitly specify the set set by the RRC message.
  • a specific DCI format peculiar to UE200 may be used as the DCI format.
  • the specific DCI format may include a DCI format that schedules PDSCH with HARQ-ACK, or may include other DCI formats that schedule PUCCHs. In such cases, DCI may have the fields shown below.
  • DCI may include a field for storing the information element that identifies omega_LP_HP described above.
  • omega_LP_HP is a parameter used in the above-mentioned application examples 1 to 4.
  • the DCI may include a field for storing an information element that identifies any one of the above-mentioned omega_HP and omega_LP (omega_XP).
  • omega_HP is a parameter used in the above-mentioned application examples 5, 7, 8 and 10.
  • omega_LP is a parameter used in the above-mentioned application examples 6, 7, 9, and 10.
  • omega_XP contained in DCI for HP UCI may be interpreted as omega_HP.
  • Omega_XP contained in DCI for LP UCI may be interpreted as omega_LP.
  • DCI may include a field for storing the above-mentioned information element specifying omega_HP and a field for storing the information element specifying omega_LP.
  • the DCI for HP UCI may include an information element that identifies omega_LP_HP and an information element that identifies omega_XP, which is interpreted as omega_HP.
  • the DCI for LP UCI may include an information element that identifies omega_LP_HP and an information element that identifies omega_XP, which is interpreted as omega_LP.
  • DCI has a field for storing the above-mentioned information element that identifies omega_LP_HP, a field for storing the above-mentioned information element that identifies omega_HP, and a field for storing the information element that identifies omega_LP. It may be included.
  • the constraint may include the condition that omega_LP_HP contained in the DCI for HP UCI must not be different from omega_LP_HP contained in the DCI for LP UCI.
  • the constraint may include the condition that omega_LP_HP contained in the DCI for HP UCI is applied without applying the omega_LP_HP contained in the DCI for LP UCI.
  • the constraint may include the condition that the omega_LP_HP contained in the DCI for HP UCI is applied instead of the omega_LP_HP contained in the DCI for HP UCI.
  • the constraint may include the condition that omega_HP contained in the DCI for HP UCI must not differ from omega_LP contained in the DCI for LP UCI.
  • the constraint may include the condition that omega_HP contained in the DCI for HP UCI is applied without applying the omega_LP contained in the DCI for LP UCI.
  • the constraint may include the condition that the omega_HP contained in the DCI for HP UCI is not applied, but the omega_LP contained in the DCI for LP UCI is applied.
  • a specific DCI format may be used as the DCI format.
  • the specific DCI format may include a newly introduced DCI format or may include an existing DCI format (0_0, 0_1, 0_2, 1_0, 1_1, 1_2) without scheduling data or PUCCH.
  • the specific DCI format commonly applied to the group may include an existing format (GroupCommonDCIFormat) or a newly introduced DCI format. In such cases, DCI may have the fields shown below.
  • DCI may include a field for storing the information element that identifies omega_LP_HP described above.
  • omega_LP_HP is a parameter used in the above-mentioned application examples 1 to 4.
  • DCI may include a field for storing the above-mentioned information element that identifies omega_HP.
  • omega_HP is a parameter used in the above-mentioned application examples 5, 7, 8 and 10.
  • DCI may include a field for storing the information element that identifies omega_LP described above.
  • omega_LP is a parameter used in the above-mentioned application examples 6, 7, 9, and 10.
  • DCI may include a field for storing the above-mentioned information element specifying omega_HP and a field for storing the above-mentioned information element specifying omega_LP.
  • DCI may include a field for storing the above-mentioned information element specifying omega_LP_HP and a field for storing the above-mentioned information element specifying omega_HP.
  • DCI may include a field for storing the above-mentioned information element specifying omega_LP_HP and a field for storing the above-mentioned information element specifying omega_LP.
  • the DCI has a field for storing the above-mentioned information element that identifies omega_LP_HP, a field for storing the above-mentioned information element that identifies omega_HP, and a field for storing the above-mentioned information element that identifies omega_LP. , May be included.
  • the information element (specific scaling factor) included in DCI may be applied to all UCI multiplexing regardless of the combination of HP UCI and LP UCI multiplexed on PUCCH.
  • the specific scaling factor may be applied to a multiple case set as a combination of HP UCI and LP UCI (hereinafter referred to as multiple cases) to be multiplexed on PUCCH. Multiple cases may be set by RRC messages.
  • the DCI may include a field that stores a specific scaling factor that is different for each multiple case. The DCI may distinguish the combination of UCIs to which a particular scaling factor applies by number. For example, omega_LP_HP_1 may be applied to a combination of LP HARQ-ACK and HP HARQ-ACK, and omega_LP_HP_2 may be applied to a combination of HP HARQ-ACK and LP HARQ-ACK. omega_HP_1 may be applied to HP HARQ-ACK and omega_HP_2 may be applied to HP SR. omega_LP_1 may be applied to LP HARQ-ACK and omega_LP_2 may be applied to LP CSI.
  • the specific scaling factor may be applied to multiple cases specified by DCI. Two or more multiple cases may be set by the RRC message, and one of the set multiple cases may be specified by DCI. As mentioned above, DCI may include fields that store specific scaling factors that are different for each multiple case. The DCI may distinguish the combination of UCIs to which a particular scaling factor applies by number.
  • a mechanism for deactivating a specific scaling factor may be introduced.
  • a timer for measuring the period for which the specific scaling factor is applied may be introduced, and the specific scaling factor may be deactivated by the expiration of the timer.
  • the timer may measure the period in units of symbols or may measure the period in units of slots.
  • a DCI may be introduced that includes an information element that directs the deactivation of a particular scaling factor.
  • the UE 200 may transmit a UE Capability including an information element regarding the application of a specific scaling factor to the NG-RAN 20.
  • the UE200 may apply a specific scaling factor based on the capabilities of the UE200.
  • the information element regarding the application of the specific scaling factor may be an information element indicating that the UE 200 corresponds to the multiplexing of UCIs having different priorities.
  • the information element regarding the application of the specific scaling factor may be an information element indicating that the UE 200 corresponds to the specific scaling factor.
  • step S10 the UE 200 transmits a message including the UE Capability to the NG-RAN 20.
  • UE Capability may include informational elements regarding the application of specific scaling factors.
  • UE100 receives an RRC message from NG-RAN20.
  • the RRC message may include an information element that identifies a particular scaling factor.
  • the RRC message may include an information element that specifies the setting of possible values for a particular scaling factor.
  • the RRC message may contain informational elements that specify the settings of the multiset to which a particular scaling factor applies.
  • UE200 receives one or more DCIs from NG-RAN20 via PDCCH.
  • the DCI may include information elements that specify a particular scaling factor.
  • the DCI format may be the specific DCI format described above.
  • step S13 the UE 200 transmits an uplink signal using a PUCCH in which UCIs having different priorities are multiplexed.
  • the UE 200 executes UCI channel coding having different priorities from each other by using a newly introduced specific scaling factor. According to such a configuration, in the case where UCIs having different priorities are multiplexed on the PUCCH, the channel coding of the UCIs multiplexed on the PUCCH can be appropriately executed.
  • the specific scaling factor (omega_LP_HP, omega_HP, omega_LP) may be set by the upper layer parameter.
  • the specific scaling factor may be predetermined in the wireless communication system.
  • the specific scaling factor is set by the upper layer parameter and may be reported from UE200 to NG-RAN20 as UECapability.
  • an information element that specifies a specific scaling factor may be included in the MAC CE message.
  • the application of DCI described above may be realized by MAC CE notification.
  • the priority may be set as follows.
  • the HARQ-ACK priority may be higher than the SR priority.
  • the priority for URLLC Ultra Reliable and Low Latency Communications
  • eMBB enhanced Mobile BroadBand
  • the block configuration diagram (FIG. 4) used in the description of the above-described embodiment shows a block of functional units.
  • These functional blocks are realized by any combination of at least one of hardware and software.
  • the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one physically or logically coupled device, or two or more physically or logically separated devices can be directly or indirectly (eg, for example). , Wired, wireless, etc.) and may be realized using these plurality of devices.
  • the functional block may be realized by combining the software with the one device or the plurality of devices.
  • Functions include judgment, decision, judgment, calculation, calculation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, solution, selection, selection, establishment, comparison, assumption, expectation, and assumption. Broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, assigning, etc., but limited to these I can't.
  • a functional block (configuration unit) that makes transmission function is called a transmitting unit (transmitting unit) or a transmitter (transmitter).
  • the realization method is not particularly limited.
  • FIG. 6 is a diagram showing an example of the hardware configuration of the device.
  • the device may be 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, and the like.
  • the word “device” can be read as a circuit, device, unit, etc.
  • the hardware configuration of the device may be configured to include one or more of each of the devices shown in the figure, or may be configured not to include some of the devices.
  • Each functional block of the device (see FIG. 4) is realized by any hardware element of the computer device or a combination of the hardware elements.
  • each function in the device is such that the processor 1001 performs an operation by loading predetermined software (program) on the hardware such as the processor 1001 and the memory 1002, and controls the communication by the communication device 1004, or the memory. It is realized by controlling at least one of reading and writing of data in 1002 and storage 1003.
  • predetermined software program
  • Processor 1001 operates, for example, an operating system to control the entire computer.
  • the processor 1001 may be configured by a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, and the like.
  • CPU central processing unit
  • the processor 1001 reads a program (program code), a software module, 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.
  • a program program code
  • a program that causes a computer to execute at least a part of the operations described in the above-described embodiment is used.
  • the various processes described above may be executed by one processor 1001 or may be executed simultaneously or sequentially by two or more processors 1001.
  • Processor 1001 may be implemented by one or more chips.
  • the program may be transmitted from the network via a telecommunication line.
  • the memory 1002 is a computer-readable recording medium, and is composed of at least one such as ReadOnlyMemory (ROM), ErasableProgrammableROM (EPROM), Electrically ErasableProgrammableROM (EEPROM), and RandomAccessMemory (RAM). May be done.
  • the memory 1002 may be referred to as a register, a cache, a main memory (main storage device), or the like.
  • the memory 1002 can store a program (program code), a software module, or the like that can execute the method according to the embodiment of the present disclosure.
  • the storage 1003 is a computer-readable recording medium, for example, an optical disk such as Compact Disc ROM (CD-ROM), a hard disk drive, a flexible disk, a photomagnetic disk (for example, a compact disk, a digital versatile disk, a Blu-ray). It may consist of at least one (registered trademark) disk), smart card, flash memory (eg, card, stick, key drive), floppy (registered trademark) disk, magnetic strip, and the like.
  • Storage 1003 may be referred to as auxiliary storage.
  • the recording medium described above may be, for example, a database, server or other suitable medium containing at least one of the memory 1002 and the storage 1003.
  • the communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, a communication module, or the like.
  • the communication device 1004 includes, for example, a high frequency switch, a duplexer, a filter, a frequency synthesizer, etc. in order to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). It may be composed of.
  • FDD frequency division duplex
  • TDD time division duplex
  • the input device 1005 is an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that accepts an input from the outside.
  • the output device 1006 is an output device (for example, a display, a speaker, an LED lamp, etc.) that outputs to the outside.
  • the input device 1005 and the output device 1006 may have an integrated configuration (for example, a touch panel).
  • Bus 1007 may be configured using a single bus or may be configured using different buses for each device.
  • the device includes hardware such as a microprocessor, a digital signal processor (Digital Signal Processor: DSP), ApplicationSpecific IntegratedCircuit (ASIC), ProgrammableLogicDevice (PLD), and FieldProgrammableGateArray (FPGA).
  • the hardware may implement some or all of each functional block.
  • processor 1001 may be implemented using at least one of these hardware.
  • information notification includes physical layer signaling (eg Downlink Control Information (DCI), Uplink Control Information (UCI), higher layer signaling (eg RRC signaling, Medium Access Control (MAC) signaling, Master Information Block). (MIB), System Information Block (SIB)), other signals or combinations thereof.
  • DCI Downlink Control Information
  • UCI Uplink Control Information
  • RRC signaling eg RRC signaling, Medium Access Control (MAC) signaling, Master Information Block). (MIB), System Information Block (SIB)
  • RRC signaling may also be referred to as an RRC message, eg, RRC Connection Setup. ) Message, RRC Connection Reconfiguration message, etc. may be used.
  • LTE LongTermEvolution
  • LTE-A LTE-Advanced
  • SUPER3G IMT-Advanced
  • 4G 4th generation mobile communication system
  • 5G 5th generation mobile communication system
  • FutureRadioAccess FAA
  • NewRadio NR
  • W-CDMA registered trademark
  • GSM registered trademark
  • CDMA2000 Code Division Multiple Access 2000
  • UMB UltraMobileBroadband
  • IEEE802.11 Wi-Fi (registered trademark)
  • IEEE802.16 WiMAX®
  • IEEE802.20 Ultra-WideBand
  • Bluetooth® Ultra-WideBand
  • other systems that utilize appropriate systems and at least one of the next-generation systems extended based on them. It may be applied to one.
  • a plurality of systems may be applied in combination (for example, a combination of at least one of LTE and LTE-A and 5G).
  • the specific operation performed by the base station in this disclosure may be performed by its upper node (upper node).
  • various operations performed for communication with the terminal are the base station and other network nodes other than the base station (eg, MME or). It is clear that it can be done by at least one of (but not limited to, S-GW, etc.).
  • S-GW network node
  • the case where there is one network node other than the base station is illustrated above, it may be a combination of a plurality of other network nodes (for example, MME and S-GW).
  • Information and signals can be output from the upper layer (or lower layer) to the lower layer (or upper layer).
  • Input / output may be performed via a plurality of network nodes.
  • the input / output information may be stored in a specific location (for example, memory) or may be managed using a management table.
  • the input / output information may be overwritten, updated, or added.
  • the output information may be deleted.
  • the entered information may be transmitted to other devices.
  • the determination may be made by a value represented by 1 bit (0 or 1), by a boolean value (Boolean: true or false), or by comparing numerical values (for example, a predetermined value). It may be done by comparison with the value).
  • the notification of predetermined information (for example, the notification of "being X") is not limited to the explicit one, but is performed implicitly (for example, the notification of the predetermined information is not performed). May be good.
  • Software whether referred to as software, firmware, middleware, microcode, hardware description language, or other names, is an instruction, instruction set, code, code segment, program code, program, subprogram, software module.
  • Applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, features, etc. should be broadly interpreted.
  • software, instructions, information, etc. may be transmitted and received via a transmission medium.
  • a transmission medium For example, a website, where the software uses at least one of wired technology (coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), etc.) and wireless technology (infrared, microwave, etc.).
  • wired technology coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), etc.
  • wireless technology infrared, microwave, etc.
  • the information, signals, etc. described in this disclosure may be represented using any of a variety of different techniques.
  • data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description are voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any of these. It may be represented by a combination of.
  • a channel and a symbol may be a signal (signaling).
  • the signal may be a message.
  • the component carrier (CC) may be referred to as a carrier frequency, a cell, a frequency carrier, or the like.
  • system and “network” used in this disclosure are used interchangeably.
  • the information, parameters, etc. described in the present disclosure may be expressed using an absolute value, a relative value from a predetermined value, or another corresponding information. It may be represented.
  • the radio resource may be one indicated by an index.
  • Base Station BS
  • Wireless Base Station Wireless Base Station
  • NodeB NodeB
  • eNodeB eNodeB
  • gNodeB gNodeB
  • Base stations are sometimes referred to by terms such as macrocells, small cells, femtocells, and picocells.
  • the base station can accommodate one or more (for example, three) cells (also called sectors). When a base station accommodates multiple cells, the entire base station coverage area can be divided into multiple smaller areas, each smaller area being a base station subsystem (eg, a remote radio for indoor use). Communication services can also be provided by Head: RRH).
  • RRH Remote Radio Head
  • cell refers to a part or all of the coverage area of at least one of the base station providing communication services in this coverage and the base station subsystem.
  • MS Mobile Station
  • UE user equipment
  • terminal terminal
  • Mobile stations can be used by those skilled in the art as subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless. It may also be referred to as a terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable term.
  • At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a communication device, or the like.
  • At least one of the base station and the mobile station may be a device mounted on the mobile body, a mobile body itself, or the like.
  • the moving body may be a vehicle (eg, car, airplane, etc.), an unmanned moving body (eg, drone, self-driving car, etc.), or a robot (manned or unmanned). ) May be.
  • at least one of the base station and the mobile station includes a device that does not necessarily move during communication operation.
  • at least one of a base station and a mobile station may be an Internet of Things (IoT) device such as a sensor.
  • IoT Internet of Things
  • the base station in the present disclosure may be read as a mobile station (user terminal, the same shall apply hereinafter).
  • communication between a base station and a mobile station has been replaced with communication between a plurality of mobile stations (for example, it may be called Device-to-Device (D2D), Vehicle-to-Everything (V2X), etc.).
  • D2D Device-to-Device
  • V2X Vehicle-to-Everything
  • Each aspect / embodiment of the present disclosure may be applied to the configuration.
  • the mobile station may have the functions of the base station.
  • words such as "up” and “down” may be read as words corresponding to communication between terminals (for example, "side”).
  • the upstream channel, the downstream channel, and the like may be read as a side channel.
  • the mobile station in the present disclosure may be read as a base station.
  • the base station may have the functions of the mobile station.
  • the wireless frame may be composed of one or more frames in the time domain. Each one or more frames in the time domain may be referred to as a subframe.
  • the subframe may be further composed of one or more slots in the time domain.
  • the subframe may have a fixed time length (eg, 1 ms) that does not depend on numerology.
  • the numerology may be a communication parameter applied to at least one of transmission and reception of a signal or channel.
  • Numerology includes, for example, SubCarrier Spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (Transmission Time Interval: TTI), number of symbols per TTI, wireless frame configuration, transmission / reception. It may indicate at least one of a specific filtering process performed by the machine in the frequency domain, a specific windowing process performed by the transmitter / receiver in the time domain, and the like.
  • the slot may be composed of one or more symbols (Orthogonal Frequency Division Multiplexing (OFDM) symbol, Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol, etc.) in the time region.
  • the slot may be a unit of time based on numerology.
  • the slot may include a plurality of mini slots.
  • Each minislot may be composed of one or more symbols in the time domain. Further, the mini-slot may be referred to as a sub-slot.
  • a minislot may consist of a smaller number of symbols than the slot.
  • PDSCH (or PUSCH) transmitted in time units larger than the minislot may be referred to as PDSCH (or PUSCH) mapping type A.
  • the PDSCH (or PUSCH) transmitted using the minislot may be referred to as PDSCH (or PUSCH) mapping type B.
  • the wireless frame, subframe, slot, minislot and symbol all represent the time unit when transmitting a signal.
  • the radio frame, subframe, slot, minislot and symbol may use different names corresponding to each.
  • one subframe may be referred to as a transmission time interval (TTI)
  • TTI transmission time interval
  • TTI transmission time interval
  • TTI transmission time interval
  • TTI transmission time interval
  • TTI transmission time interval
  • TTI slot or one minislot
  • at least one of the subframe and TTI may be a subframe (1ms) in existing LTE, a period shorter than 1ms (eg, 1-13 symbols), or a period longer than 1ms. May be.
  • the unit representing TTI may be called a slot, a mini slot, or the like instead of a subframe.
  • TTI refers to, for example, the minimum time unit of scheduling in wireless communication.
  • a base station schedules each user terminal to allocate wireless resources (frequency bandwidth that can be used in each user terminal, transmission power, etc.) in TTI units.
  • the definition of TTI is not limited to this.
  • TTI may be a transmission time unit such as a channel-encoded data packet (transport block), a code block, or a code word, or may be a processing unit such as scheduling or link adaptation.
  • the time interval for example, the number of symbols
  • the transport block, code block, code word, etc. may be shorter than the TTI.
  • one or more TTIs may be the minimum time unit for scheduling. Further, the number of slots (number of mini-slots) constituting the minimum time unit of the scheduling may be controlled.
  • TTI with a time length of 1 ms may be called normal TTI (TTI in LTE Rel.8-12), normal TTI, long TTI, normal subframe, normal subframe, long subframe, slot, etc.
  • TTIs shorter than normal TTIs may be referred to as shortened TTIs, short TTIs, partial TTIs (partial or fractional TTIs), shortened subframes, short subframes, minislots, subslots, slots and the like.
  • the long TTI (for example, normal TTI, subframe, etc.) may be read as a TTI having a time length of more than 1 ms
  • the short TTI (for example, shortened TTI, etc.) may be read as a TTI less than the TTI length of the long TTI and 1 ms. It may be read as a TTI having the above TTI length.
  • the resource block (RB) is a resource allocation unit in the time domain and the frequency domain, and may include one or a plurality of continuous subcarriers in the frequency domain.
  • the number of subcarriers contained in RB may be the same regardless of numerology, and may be, for example, 12.
  • the number of subcarriers contained in the RB may be determined based on numerology.
  • the time domain of RB may include one or more symbols, and may have a length of 1 slot, 1 mini slot, 1 subframe, or 1 TTI.
  • Each 1TTI, 1 subframe, etc. may be composed of one or a plurality of resource blocks.
  • One or more RBs include 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, and the like. May be called.
  • Physical RB Physical RB: PRB
  • SCG sub-carrier Group
  • REG resource element group
  • PRB pair an RB pair, and the like. May be called.
  • the resource block may be composed of one or a plurality of resource elements (ResourceElement: RE).
  • RE resource elements
  • 1RE may be a radio resource area of 1 subcarrier and 1 symbol.
  • Bandwidth Part (which may also be called partial bandwidth) may represent a subset of consecutive common resource blocks for a neurology in a carrier. good.
  • the common RB may be specified by the index of the RB with respect to the common reference point of the carrier.
  • PRBs may be defined in a BWP and numbered within that BWP.
  • BWP may include BWP for UL (UL BWP) and BWP for DL (DL BWP).
  • BWP for UL
  • DL BWP BWP for DL
  • One or more BWPs may be set in one carrier for the UE.
  • At least one of the configured BWPs may be active, and the UE may not expect to send or receive a given signal / channel outside the active BWP.
  • “cell”, “carrier” and the like in this disclosure may be read as “BWP”.
  • the above-mentioned structures such as wireless frames, subframes, slots, minislots and symbols are merely examples.
  • the number of subframes contained in a radio frame the number of slots per subframe or radio frame, the number of minislots contained within a slot, the number of symbols and RBs contained in a slot or minislot, included in RB.
  • the number of subcarriers, as well as the number of symbols in the TTI, the symbol length, the cyclic prefix (CP) length, and other configurations can be changed in various ways.
  • connection means any direct or indirect connection or connection between two or more elements and each other. It can include the presence of one or more intermediate elements between two “connected” or “combined” elements.
  • the connection or connection between the elements may be physical, logical, or a combination thereof.
  • connection may be read as "access”.
  • the two elements use at least one of one or more wires, cables and printed electrical connections, and as some non-limiting and non-comprehensive examples, the radio frequency region.
  • Electromagnetic energies with wavelengths in the microwave and light (both visible and invisible) regions, etc. can be considered to be “connected” or “coupled” to each other.
  • the reference signal can also be abbreviated as Reference Signal (RS), and may be called a pilot (Pilot) depending on the applied standard.
  • RS Reference Signal
  • Pilot pilot
  • each of the above devices may be replaced with a "part”, a “circuit”, a “device”, or the like.
  • references to elements using designations such as “first” and “second” as used in this disclosure does not generally limit the quantity or order of those elements. These designations can be used in the present disclosure as a convenient way to distinguish between two or more elements. Therefore, references to the first and second elements do not mean that only two elements can be adopted there, or that the first element must somehow precede the second element.
  • determining and “determining” used in this disclosure may include a wide variety of actions.
  • “Judgment” and “decision” are, for example, judgment (judging), calculation (calculating), calculation (computing), processing (processing), derivation (deriving), investigation (investigating), search (looking up, search, inquiry). It may include (eg, searching in a table, database or another data structure), ascertaining as “judgment” or “decision”.
  • judgment and “decision” are receiving (for example, receiving information), transmitting (for example, transmitting information), input (input), output (output), and access. It may include (for example, accessing data in memory) to be regarded as “judgment” or “decision”.
  • judgment and “decision” are considered to be “judgment” and “decision” when the things such as solving, selecting, choosing, establishing, and comparing are regarded as “judgment” and “decision”. Can include. That is, “judgment” and “decision” may include considering some action as “judgment” and “decision”. Further, “judgment (decision)” may be read as “assuming", “expecting”, “considering” and the like.
  • the term "A and B are different” may mean “A and B are different from each other”.
  • the term may mean that "A and B are different from C”.
  • Terms such as “separate” and “combined” may be interpreted in the same way as “different”.
  • Radio communication system 20 NG-RAN 100 gNB 200 UE 210 Wireless signal transmitter / receiver 220 Amplifier 230 Modulator / demodulator 240 Control signal / reference signal processing 250 Encoding / decoding 260 Data transmitter / receiver 270 Control 1001 Processor 1002 Memory 1003 Storage 1004 Communication device 1005 Input device 1006 Output device 1007 Bus

Landscapes

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

Abstract

Le présent terminal comprend : une unité de commande qui multiplexe au moins deux éléments d'informations de commande de liaison montante présentant des priorités différentes par rapport à un canal de commande de liaison montante ; et une unité de communication qui transmet un signal de liaison montante au moyen du canal de commande de liaison montante dans lequel les au moins deux éléments d'informations de commande de liaison montante sont multiplexés, dans le codage de canal des au moins deux éléments d'informations de commande de liaison montante, l'unité de commande applique un facteur de mise à l'échelle spécifique à au moins un élément d'informations de commande de liaison montante des au moins deux éléments d'informations de commande de liaison montante.
PCT/JP2021/040837 2020-11-06 2021-11-05 Terminal WO2022097724A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2020186143 2020-11-06
JP2020-186143 2020-11-06

Publications (1)

Publication Number Publication Date
WO2022097724A1 true WO2022097724A1 (fr) 2022-05-12

Family

ID=81458333

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2021/040837 WO2022097724A1 (fr) 2020-11-06 2021-11-05 Terminal

Country Status (1)

Country Link
WO (1) WO2022097724A1 (fr)

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON: "Intra-UE multiplexing enhancements", 3GPP DRAFT; R1-2007567, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. E-meeting; 20201026 - 20201113, 24 October 2020 (2020-10-24), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051946419 *
NTT DOCOMO, INC.: "Discussion on intra-UE multiplexing/prioritization for Rel.17 URLLC", 3GPP DRAFT; R1-2009185, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20201026 - 20201113, 23 October 2020 (2020-10-23), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051945516 *
SHARP: "Enhancements on intra-UE UCI multiplexing and PUSCH prioritization", 3GPP DRAFT; R1-2009136, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20201026 - 20201113, 24 October 2020 (2020-10-24), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051946853 *
SONY: "Considerations in intra-UE UL multiplexing", 3GPP DRAFT; R1-2008358, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20201026 - 20201113, 23 October 2020 (2020-10-23), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051946644 *

Similar Documents

Publication Publication Date Title
WO2022079876A1 (fr) Terminal
WO2021199348A1 (fr) Terminal
WO2022097724A1 (fr) Terminal
WO2022102718A1 (fr) Terminal
WO2022102714A1 (fr) Terminal
WO2022113232A1 (fr) Terminal, station de base et procédé de communication sans fil
WO2022102670A1 (fr) Terminal
WO2022085156A1 (fr) Terminal
WO2022102669A1 (fr) Terminal
WO2022079872A1 (fr) Terminal
WO2022074842A1 (fr) Terminal
WO2022074843A1 (fr) Terminal
WO2022137559A1 (fr) Terminal et procédé de communication sans fil
WO2022153505A1 (fr) Terminal et station de base radio
WO2022029973A1 (fr) Terminal
WO2021199387A1 (fr) Terminal
WO2021192063A1 (fr) Terminal
WO2022029972A1 (fr) Terminal
WO2021199388A1 (fr) Terminal
WO2022153545A1 (fr) Terminal et procédé de communication sans fil
WO2022153509A1 (fr) Terminal, station de base et procédé de communication radio
WO2021214921A1 (fr) Terminal
WO2022085201A1 (fr) Terminal
WO2022137569A1 (fr) Terminal, station de base et procédé de communication sans fil
WO2022239078A1 (fr) Terminal, système de communication radio et procédé de communication radio

Legal Events

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

Ref document number: 21889276

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21889276

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: JP