WO2022153545A1 - Terminal et procédé de communication sans fil - Google Patents

Terminal et procédé de communication sans fil Download PDF

Info

Publication number
WO2022153545A1
WO2022153545A1 PCT/JP2021/001532 JP2021001532W WO2022153545A1 WO 2022153545 A1 WO2022153545 A1 WO 2022153545A1 JP 2021001532 W JP2021001532 W JP 2021001532W WO 2022153545 A1 WO2022153545 A1 WO 2022153545A1
Authority
WO
WIPO (PCT)
Prior art keywords
pusch
uci
data channel
uplink
pucch
Prior art date
Application number
PCT/JP2021/001532
Other languages
English (en)
Japanese (ja)
Inventor
優元 ▲高▼橋
聡 永田
チーピン ピ
ジン ワン
ラン チン
Original Assignee
株式会社Ｎｔｔドコモ
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 株式会社Ｎｔｔドコモ filed Critical 株式会社Ｎｔｔドコモ
Priority to PCT/JP2021/001532 priority Critical patent/WO2022153545A1/fr
Priority to CN202180090677.7A priority patent/CN116711433A/zh
Publication of WO2022153545A1 publication Critical patent/WO2022153545A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling

Definitions

  • the present disclosure relates to terminals and wireless communication methods that support priority or multiplexing processing of uplink traffic.
  • 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
  • DCI Downlink Control Information
  • UL uplink
  • Non-Patent Document 1 UL traffic terminals (User Equipment, UE) having different priorities is agreed (for example, Non-Patent Document 1).
  • Non-Patent Document 2 a mechanism for omitting (skipping) UL transmission when a plurality of UL transmissions overlap in the time direction is also being studied.
  • the handling of multiple UL transmissions having the same or different priorities may differ depending on the content of the UL transmission (channel type, etc.).
  • the following disclosure is made in view of such a situation, and an object thereof is to provide a terminal and a wireless communication method capable of efficiently and appropriately processing a plurality of UL transmissions having the same or different priorities. do.
  • One aspect of the present disclosure is a transmission unit (radio signal transmission / reception unit 210) that transmits an uplink control channel, a first uplink data channel, and a second uplink data channel, the uplink control channel, the first uplink data channel, and the first uplink data channel.
  • a transmission unit radio signal transmission / reception unit 210 that transmits an uplink control channel, a first uplink data channel, and a second uplink data channel, the uplink control channel, the first uplink data channel, and the first uplink data channel.
  • the two uplink data channels have the same priority, the first uplink data channel and the second uplink data channel overlap in the time direction, the uplink transmission is omitted, and the first uplink data channel or the second uplink data channel is used.
  • It is a terminal (UE200) including a control unit (control unit 270) that controls transmission in the uplink based on multiplexing of uplink control information to the uplink data channel.
  • One aspect of the present disclosure is a transmission unit (radio signal transmission / reception unit 210) that transmits an uplink control channel, a first uplink data channel, and a second uplink data channel, the uplink control channel, the first uplink data channel, and the first uplink data channel.
  • the two uplink data channels have different priorities, the first uplink data channel and the second uplink data channel overlap in the time direction, the uplink transmission is omitted, the first uplink data channel or the second uplink data.
  • It is a terminal (UE200) including a control unit (control unit 270) that controls transmission in the uplink based on multiplexing of uplink control information to the channel and priority / multiplexing processing in the terminal.
  • One aspect of the present disclosure is a step in which a terminal transmits an uplink control channel, a first uplink data channel, and a second uplink data channel, and the terminal is the uplink control channel, the first uplink data channel, and the second uplink data channel.
  • the uplink data channels have the same priority
  • the first uplink data channel and the second uplink data channel overlap in the time direction
  • the uplink transmission is omitted, and the first uplink data channel or the second uplink data channel is used.
  • It is a wireless communication method including a step of controlling transmission in the uplink based on multiplexing of uplink control information to a data channel.
  • One aspect of the present disclosure is a step in which a terminal transmits an uplink control channel, a first uplink data channel, and a second uplink data channel, and the terminal is the uplink control channel, the first uplink data channel, and the second uplink data channel.
  • the uplink data channels have different priorities, the first uplink data channel and the second uplink data channel overlap in the time direction, the uplink transmission is omitted, the first uplink data channel or the second uplink data channel.
  • This is a wireless communication method including a step of controlling transmission in the uplink based on multiplexing of uplink control information to the terminal and priority / multiplexing processing in the terminal.
  • FIG. 1 is an overall schematic configuration diagram of the wireless communication system 10.
  • FIG. 2 is a diagram showing a configuration example of a wireless frame, a subframe, and a slot used in the wireless communication system 10.
  • FIG. 3 is a functional block configuration diagram of the UE 200.
  • FIG. 4 is a diagram showing a timeline of DG PUSCH, CG PUSCH, and PUCCH according to Option 1-1: Case 1.
  • FIG. 5 is an operation flow diagram of the UE according to Option 1-1: Case 1.
  • FIG. 6 is a diagram showing a timeline of DG PUSCH, CG PUSCH, and PUCCH according to Option 1-1: Case 2.
  • FIG. 1 is an overall schematic configuration diagram of the wireless communication system 10.
  • FIG. 2 is a diagram showing a configuration example of a wireless frame, a subframe, and a slot used in the wireless communication system 10.
  • FIG. 3 is a functional block configuration diagram of the UE 200.
  • FIG. 4 is a diagram showing a timeline of DG
  • FIG. 7 is a diagram showing a timeline of DG PUSCH, CG PUSCH, and PUCCH according to Option 1-1: Case 3.
  • FIG. 8 is a diagram showing a timeline of DG PUSCH, CG PUSCH, and PUCCH according to Option 1-1: Case 4.
  • FIG. 9 is a diagram showing a timeline of DG PUSCH, CG PUSCH, and PUCCH according to Option 1-1: Case 5.
  • FIG. 10 is a diagram showing a timeline of 1DG PUSCH, CG PUSCH, and PUCCH related to Option 1-2: Case.
  • FIG. 11 is a diagram showing a timeline of DG PUSCH, CG PUSCH, and PUCCH according to Option 1-2: Case 2.
  • FIG. 11 is a diagram showing a timeline of DG PUSCH, CG PUSCH, and PUCCH according to Option 1-2: Case 2.
  • FIG. 12 is a diagram showing a timeline of DG PUSCH, CG PUSCH, and PUCCH according to Option 1-2: Case 3.
  • FIG. 13 is a diagram showing a timeline of DG PUSCH, CG PUSCH, and PUCCH according to Option 1-1: Case 4.
  • FIG. 14 is a diagram showing a timeline of DG PUSCH, CG PUSCH, and PUCCH according to Option 1-1: Case 5.
  • FIG. 15 is a diagram showing a timeline of DG PUSCH, CG PUSCH, and PUCCH according to Option 1-3: Case 1.
  • FIG. 16 is an operation flow diagram of the UE according to Option 1-3: Case 1.
  • FIG. 16 is an operation flow diagram of the UE according to Option 1-3: Case 1.
  • FIG. 17 is a diagram showing a timeline of DG PUSCH, CG PUSCH, and PUCCH according to Option 1-3: Case 2.
  • FIG. 18 is a diagram showing a timeline of DG PUSCH, CG PUSCH, and PUCCH according to Option 1-3: Case 3.
  • FIG. 19 is a diagram showing a timeline of DG PUSCH, CG PUSCH, and PUCCH according to Option 1-3: Case 4.
  • FIG. 20 is a diagram showing a timeline of DG PUSCH, CG PUSCH, and PUCCH according to Option 1-3: Case 5.
  • FIG. 21 is a diagram showing a timeline of DG PUSCH, CG PUSCH, and PUCCH according to Option 2-1: Case 1.
  • FIG. 18 is a diagram showing a timeline of DG PUSCH, CG PUSCH, and PUCCH according to Option 1-3: Case 3.
  • FIG. 18 is a diagram showing a timeline of DG PUSCH, CG PUSCH, and P
  • FIG. 22 is a diagram showing a timeline of DG PUSCH, CG PUSCH, and PUCCH according to Option 2-1: Case 2.
  • FIG. 23 is a diagram showing a timeline of DG PUSCH, CG PUSCH, and PUCCH according to Option 2-1: Case 3.
  • FIG. 24 is a diagram showing a timeline of DG PUSCH, CG PUSCH, and PUCCH according to Option 2-1: Case 4.
  • FIG. 25 is a diagram showing a timeline of DG PUSCH, CG PUSCH, and PUCCH according to Option 2-1: Case 5.
  • FIG. 26 is a diagram showing a timeline of DG PUSCH, CG PUSCH and PUCCH according to Option 2-1: Case 6.
  • FIG. 27 is a diagram showing a timeline of DG PUSCH, CG PUSCH, and PUCCH according to Option 2-2: Case 1.
  • FIG. 28 is a diagram showing a timeline of DG PUSCH, CG PUSCH, and PUCCH according to Option 2-2: Case 2.
  • FIG. 29 is a diagram showing a timeline of DG PUSCH, CG PUSCH and PUCCH according to Option 2-2: Case 3.
  • FIG. 30 is a diagram showing a timeline of DG PUSCH, CG PUSCH and PUCCH according to Option 2-2: Case 4.
  • FIG. 31 is a diagram showing a timeline of DG PUSCH, CG PUSCH, and PUCCH according to Option 2-2: Case 5.
  • FIG. 28 is a diagram showing a timeline of DG PUSCH, CG PUSCH, and PUCCH according to Option 2-2: Case 2.
  • FIG. 29 is a diagram showing a timeline of DG PUSCH, CG PUSCH and PUCCH according
  • FIG. 32 is a diagram showing a timeline of DG PUSCH, CG PUSCH, and PUCCH according to Option 2-2: Case 6.
  • FIG. 33 is a diagram showing a timeline of DG PUSCH, CG PUSCH, and PUCCH according to Option 2-3: Case 1.
  • FIG. 34 is a diagram showing a timeline of DG PUSCH, CG PUSCH, and PUCCH according to Option 2-3: Case 2.
  • FIG. 35 is a diagram showing a timeline of DG PUSCH, CG PUSCH, and PUCCH according to Option 2-3: Case 3.
  • FIG. 36 is a diagram showing a timeline of DG PUSCH, CG PUSCH, and PUCCH according to Option 2-3: Case 4.
  • FIG. 33 is a diagram showing a timeline of DG PUSCH, CG PUSCH, and PUCCH according to Option 2-3: Case 1.
  • FIG. 34 is a diagram showing a timeline of DG PUSCH, CG PUSCH, and PUCCH according to Option
  • FIG. 37 is a diagram showing a timeline of DG PUSCH, CG PUSCH, and PUCCH according to Option 2-3: Case 5.
  • FIG. 38 is a diagram showing a timeline of DG PUSCH, CG PUSCH, and PUCCH according to Option 2-3: Case 6.
  • FIG. 39 is a diagram showing a timeline of DG PUSCH, CG PUSCH, and PUCCH according to Option 2-4: Case 7.
  • FIG. 40 is a diagram showing a timeline of DG PUSCH, CG PUSCH, and PUCCH according to Option 2-4: Case 8.
  • FIG. 41 is a diagram showing a timeline of DG PUSCH, CG PUSCH, and PUCCH according to Option 2-4: Case 9.
  • FIG. 39 is a diagram showing a timeline of DG PUSCH, CG PUSCH, and PUCCH according to Option 2-4: Case 9.
  • FIG. 39 is a diagram showing a timeline of DG PUSCH, CG PUSCH, and PUCCH
  • FIG. 42 is a diagram showing a timeline of DG PUSCH, CG PUSCH, and PUCCH according to Option 2-5: Case 7.
  • FIG. 43 is a diagram showing a timeline of DG PUSCH, CG PUSCH, and PUCCH according to Option 2-5: Case 8.
  • FIG. 44 is a diagram showing a timeline of DG PUSCH, CG PUSCH and PUCCH according to Option 2-5: Case 9.
  • FIG. 45 is a diagram showing a timeline of DG PUSCH, CG PUSCH and PUCCH according to Option 2-6: Case 7.
  • FIG. 46 is a diagram showing a timeline of DG PUSCH, CG PUSCH, and PUCCH according to Option 2-6: Case 8.
  • FIG. 47 is a diagram showing a timeline of DG PUSCH, CG PUSCH and PUCCH according to Option 2-6: Case 9.
  • FIG. 48 is a diagram showing an example of the hardware configuration of gNB100 and UE200.
  • FIG. 1 is an overall schematic configuration diagram of the wireless communication system 10 according to the present embodiment.
  • the wireless communication system 10 is a wireless communication system according to 5G New Radio (NR), and includes Next Generation-Radio Access Network 20 (hereinafter, NG-RAN20, and user terminal 200 (hereinafter, UE200)). ..
  • NR 5G New Radio
  • NG-RAN20 Next Generation-Radio Access Network 20
  • UE200 user terminal 200
  • NG-RAN20 includes a radio base station 100 (hereinafter, gNB100).
  • gNB100 radio base station 100
  • 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.
  • NG-RAN20 actually includes multiple NG-RAN Nodes, 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”.
  • the gNB100 is a wireless base station that complies with NR, and executes wireless communication according to UE200 and NR.
  • gNB100 and UE200 are Massive MIMO that generates a beam with higher directivity by controlling radio signals transmitted from multiple antenna elements, carrier aggregation (CA) that uses multiple component carriers (CC) in a bundle, and It can also support dual connectivity (DC), which communicates simultaneously between the UE and multiple NG-RAN Nodes.
  • Massive MIMO that generates a beam with higher directivity by controlling radio signals transmitted from multiple antenna elements
  • CA carrier aggregation
  • CC component carriers
  • DC dual connectivity
  • Wireless communication system 10 supports 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 120kHz (240kHz may be included) is used, and a bandwidth (BW) of 50 to 400MHz may be used.
  • the wireless communication system 10 may support a higher frequency band than the FR2 frequency band. Specifically, the wireless communication system 10 can support a frequency band exceeding 52.6 GHz and up to 114.25 GHz.
  • Cyclic Prefix-Orthogonal Frequency Division Multiplexing CP-OFDM
  • DFT-S-OFDM Discrete Fourier Transform-Spread
  • SCS Sub-Carrier Spacing
  • DFT-S-OFDM may be applied not only to uplink (UL) but also to downlink (DL).
  • FIG. 2 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 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 differ depending on the SCS.
  • the SCS may be wider than 240 kHz (eg, 480 kHz, 960 kHz, as shown in FIG. 3).
  • the time direction (t) shown in FIG. 2 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.
  • DCI Downlink Control Information
  • DCI may be interpreted as control information transmitted on the downlink, including scheduling information, data modulation, and channel code rate information required for each user (UE) to demodulate the data.
  • DCI format 2_4 may be used in order to secure (preempt) the uplink (UL) transmission having a high priority and cancel the UL transmission having a low priority.
  • DCI format 2_4 may be used to notify a group of UEs of the physical resource block (PRB) and OFDM symbols that cancel the corresponding UL transmission from the UE 200. That is, DCI format 2_4 may be interpreted as a format for notifying the PRB and OFDM symbols that have canceled UL transmission. Note that cancellation may be read as cancellation, suspension, cancellation, or the like.
  • PRB physical resource block
  • DCI format 2_4 may be displayed in the following format.
  • Cancellation indication 1 Cancellation indication 2,..., Cancellation indication N UE200 transmits UL based on UL Cancellation Indication (may be called UL CI) indicated by DCI format 2_4, specifically PUSCH (Physical Uplink Shared Channel) or Sounding Reference Signal. You can cancel transmissions such as (SRS). In addition, PUCCH (Physical Uplink Control Channel) may be canceled by UL CI.
  • UL CI Physical Uplink Shared Channel
  • SRS Sounding Reference Signal
  • the wireless communication system 10 may support multiplexing (Intra-UE multiplexing) of UL traffic having different priorities within the UE 200.
  • the UE 200 multiplexes low-priority (LP) traffic and high-priority (HP) traffic, and transmits the result of multiplexing the traffic (multiplexed result) via UL. You can do it.
  • LP low-priority
  • HP high-priority
  • priority processing within UE200 of UL traffic with different priorities may be supported.
  • the UE200 may send HP traffic with priority and may not send (drop) LP traffic.
  • Traffic may be read as channel, data channel, control channel, path, data, control data, and the like. Further, LP may be expressed as a first priority and HP may be expressed as a second priority (or vice versa). Multiple results may be read as outcome, outcome, outcome or output.
  • FIG. 3 is a functional block configuration diagram of the UE 200.
  • 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, an encoding / decoding unit 250, a data transmission / reception unit 260, and a control unit 270.
  • the gNB100 radio base station
  • the wireless signal transmitter / receiver 210 transmits / receives a wireless signal according to NR.
  • the wireless signal transmitter / receiver 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 radio signal transmission / reception unit 210 can transmit UL traffic having different priorities via a predetermined UL channel.
  • the radio signal transmitter / receiver 210 can transmit a multiplex result in which low priority (LP) traffic (first traffic) and high priority (HP) traffic (second traffic) are multiplexed. ..
  • LP low priority
  • HP high priority
  • the wireless signal transmitter / receiver 210 can transmit various UL channels. Specifically, the radio signal transmission / reception unit 210 can transmit the uplink control channel, the first uplink data channel, and the second uplink data channel of the physical (PHY) layer (layer 1). In the present embodiment, the wireless signal transmission / reception unit 210 constitutes a transmission unit.
  • PUSCH may include CG (Configured Grant) PUSCH (first uplink data channel) and DG (Dynamic Grant) PUSCH.
  • the CG PUSCH may be transmitted without requiring the transmission of a scheduling request (SR) or the reception of a UL Grant (DG).
  • DG PUSCH may be transmitted according to UL Grant.
  • 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, etc.).
  • 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, DFT-S-OFDM may be used not only for uplink (UL) but also for 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 known reference signal (pilot signal) between the base station and the terminal of each terminal for estimating the fading channel used for data demodulation.
  • 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), PositioningReferenceSignal (PRS) for position information, and the like. ..
  • 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. may be included.
  • 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)
  • PBCH Broadcast Channel
  • the data channels include PDSCH (Physical Downlink Shared Channel) and PUSCH (Physical Uplink Shared Channel). Data may mean data transmitted over a data channel.
  • PDSCH Physical Downlink Shared Channel
  • PUSCH Physical Uplink Shared Channel
  • PUCCH may be interpreted as a UL physical channel used for UCI (Uplink Control Information) transmission.
  • UCI can be transmitted by either PUCCH or PUSCH depending on the situation. Note that DCI may always be transmitted via PDCCH and may not be transmitted via PDSCH.
  • UCI may include at least one of hybrid ARQ (HARQ: Hybrid automatic repeat request) ACK / NACK, scheduling request (SR) from UE200, and Channel State Information (CSI).
  • HARQ Hybrid automatic repeat request
  • SR scheduling request
  • CSI Channel State Information
  • timing and radio resources for transmitting PUCCH may be controlled by DCI as well as the data channel.
  • the encoding / decoding unit 250 executes data division / concatenation and channel coding / decoding for each predetermined communication destination (gNB100 or other gNB).
  • the encoding / decoding unit 250 divides the data output from the data transmitting / receiving unit 260 into a predetermined size, and executes channel coding for the divided data. Further, the encoding / 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 wireless link control layer (RLC), and a packet data convergence protocol layer (PDCP)). Assemble / disassemble.
  • 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 can execute UL traffic multiplexing processing having different priorities.
  • control unit 270 has a traffic having a low priority (first priority) (first traffic) and a high priority higher than the low priority (second priority different from the first priority). It is possible to execute multiplexing processing with traffic having traffic (which may be expressed as priority) (second traffic). Note that multiplexing may be read as terms such as multiplexing, composition or superimposition. Further, as described above, the traffic may be read as a channel, a data channel, a control channel, a path, data, control data, or the like.
  • the control unit 270 multiplexes a plurality of low priority (LP) traffic (first traffic), multiplexes a plurality of high priority (HP) traffic (second traffic), and multiplex the plurality of LP traffic.
  • the multiplex result may be further multiplexed with the multiplex result in which multiple HP traffics are multiplexed.
  • control unit 270 may generate a multiplex result by multiplexing one or more LP traffic and one or more HP traffic.
  • control unit 270 may generate a multiple result by multiplexing a plurality of LP traffics, and may generate a multiple result by multiplexing the multiple result and one or more HP traffics. Conversely, the control unit 270 may generate a multiple result by multiplexing a plurality of HP traffic, and may generate a multiple result by multiplexing the multiple result and one or more LP traffic.
  • the method of multiplexing LP traffic and HP traffic is not limited to these methods.
  • the control unit 270 executes a plurality of processes for multiplexing one or a plurality of LP traffic and one or a plurality of HP traffic, and further multiplexes the plurality of multiplexing results in a hierarchical multiplexing process. May be executed. Further, the number of layers of multiplexing processing may be increased.
  • the control unit 270 determines the time between CGPUSCH and DGPUSCH. Transmission in UL may be controlled based on duplication in direction, omission of transmission of UL (may be called UL skipping), and multiplexing of UCI (uplink control information) to CG PUSCH or DG PUSCH.
  • control unit 270 determines which PUSCH to transmit when a collision (which may be called overlap, overlap, etc.) occurs between the DG PUSCH and the CG PUSCH in the time direction. good.
  • the control unit 270 may multiplex the UCI to the PUSCH. Further, the control unit 270 may execute UL skipping of the PUSCH (either DG PUSCH or CG PUSCH) determined not to transmit.
  • transmission in UL does not necessarily have to be controlled based on all of CG PUSCH and DG PUSCH overlapping in the time direction, UL skipping, and UCI multiplexing to CG PUSCH or DG PUSCH.
  • the control unit 270 determines the time direction between the CG PUSCH and the DG PUSCH.
  • UL based on duplication in, UL skipping, UCI (uplink control information) multiplexing to CG PUSCH or DG PUSCH, and Intra-UE prioritization / multiplexing (intra-terminal priority / multiplexing). Transmission may be controlled.
  • control unit 270 may determine which PUSCH to transmit when the control unit 270 causes a collision between the DG PUSCH and the CG PUSCH in the time direction. Next, when the PUCCH overlaps with the PUSCH determined to be transmitted, the control unit 270 may multiplex the UCI to the PUSCH. Further, the control unit 270 may execute UL skipping of the PUSCH (either DG PUSCH or CG PUSCH) determined not to transmit. Further, the control unit 270 may execute Intra-UE prioritization / multiplexing when PUCCH and PUSCH having different priorities overlap.
  • -Case 1-1 Only DG PUSCH overlaps with PUCCH MAC generates MAC PDU for DG PUSCH, and UCI is multiplexed with DG PUSCH.
  • CG PUSCH Only CG PUSCH overlaps with PUCCH MAC generates a MAC PDU for CG PUSCH and distributes the MAC PDU to the physical layer (PHY). UCI is multiplexed with CG PUSCH.
  • DG PUSCH and CG PUSCH overlap DG PUSCH and CG PUSCH overlap, DG PUSCH / CG PUSCH overlaps with PUCCH MAC generates MAC PDU for DG PUSCH, and UCI is multiplexed with DG PUSCH.
  • MAC does not generate TB (Transport Block) for CG PUSCH that overlaps with DG PUSCH of the same serving cell.
  • CG PUSCH is discarded and is not involved in subsequent physical layer procedures.
  • DG PUSCH and CG PUSCH overlap overlap
  • DG PUSCH and PUCCH overlap overlap
  • MAC generates a MAC PDU for DG PUSCH, and UCI is multiplexed with DG PUSCH.
  • CG PUSCH is discarded and is not involved in subsequent physical layer procedures.
  • DG PUSCH and CG PUSCH do not overlap
  • DG PUSCH and CG PUSCH overlap PUCCH and overlap MAC generates MAC PDU for DG PUSCH
  • the collision between DG PUSCH and CG PUSCH which shakes the different priorities of 3GPP Release 17, it is necessary to consider UL skipping and CG / DG / UCI with different priorities.
  • the main issues are DG / CG collision handling, UL skipping, UCI multiplexing within the same priority, and the order of prioritization within the UE for PUCCH / PUSCH of different priorities.
  • DG / CG collision processing for determining DG PUSCH or CG PUSCH (when DG PUSCH and CG PUSCH overlap) can be transmitted, and the others may be canceled or skipped.
  • Overriding CG PUSCH The DG PUSCH timeline may be checked.
  • the canceled (skipped) PUSCH overlaps with another PUCCH that does not overlap with the uncancelled (skipped) PUSCH, it may operate according to one of the following.
  • Option 1 Replace the reference instruction of "CG PUSCH start symbol” with "overlap PUCCH start symbol that does not overlap with the oldest CG PUSCH start symbol and DG PUSCH".
  • ⁇ Option 2 The timeline of DG PUSCH that overrides CG PUSCH such as 3GPP Release 16 is applied.
  • DG / CG collision processing may affect UCI multiplexing in step 2, so option 1 may be recommended. If ⁇ 2 cannot meet the DG override timeline, as in Case 1 ( Figure 4), the UE may not be ready to send PUCCH).
  • Step 2 After excluding the PUSCH canceled / skipped in step 1, if the PUCCH overlaps with the PUSCH, UCI multiplexing may be performed. The multiplexing timeline may be checked.
  • Step 3 UL skipping of CG PUSCH or DG PUSCH is executed.
  • CG PUSCH may be canceled / skipped. Otherwise, an error may occur.
  • Step 3 UL skipping If there is no TB to send for DG PUSCH (UL skipping is enabled), DG PUSCH may be skipped. As a result, only PUCCH is transmitted.
  • DG PUSCH may be sent.
  • PUCCH and DG PUSCH may be transmitted.
  • FIG. 5 shows the operation flow of the UE according to the above-mentioned option 1-1: case 1.
  • CG PUSCH may be canceled / skipped.
  • UCI multiplexing excluding CG PUSCH-Alternative 1 Due to overlapping PUCCH, DG PUSCH and CG PUSCH, the UCI multiplexing timeline may be considered.
  • the UCI may be multiplexed with DG PUSCH. Otherwise, an error may occur.
  • Step 3 UL skipping Since the UCI is multiplexed on the DG PUSCH, the DG PUSCH may be transmitted. As a result, a UCI-multiplexed DG PUSCH may be transmitted.
  • CG PUSCH may be canceled / skipped.
  • Step 2 UCI multiplexing excluding CG PUSCH In this case, there is no difference between alternative 1 and alternative 2. Also, if the UCI multiplexing timeline is satisfied, the UCI may be multiplexed with DG PUSCH. Otherwise, an error may occur.
  • Step 3 UL skipping Since the UCI is multiplexed on the DG PUSCH, the DG PUSCH may be transmitted. As a result, a UCI-multiplexed DG PUSCH may be transmitted.
  • Step 2 UCI multiplexing excluding CG PUSCH In this case, there is no difference between alternative 1 and alternative 2. Also, if the UCI multiplexing timeline is satisfied, the UCI may be multiplexed with DG PUSCH. Otherwise, an error may occur.
  • Step 3 UL skipping Since the UCI is multiplexed on the DG PUSCH, the DG PUSCH may be transmitted. As a result, a UCI-multiplexed DG PUSCH may be transmitted.
  • ⁇ 1 meets the DG override timeline -Option 1: It may be checked whether ⁇ 2 satisfies the override timeline of DG. CG PUSCH may be canceled / skipped if ⁇ 2 meets the DG override timeline. Otherwise, an error may occur.
  • CG PUSCH may be canceled / skipped.
  • PUCCH # 1 may be sent at any time.
  • the UCI of PUCCH # 2 may be multiplexed to DG PUSCH when the UCI multiplexing timeline between DG PUSCH and PUCCH # 2 is satisfied. Otherwise, an error may occur.
  • Step 3 UL skipping Since the UCI is multiplexed on the DG PUSCH, the DG PUSCH may be transmitted. As a result, a DG PUSCH in which the UCI of PUCCH # 1 and PUCCH # 2 is multiplexed may be transmitted.
  • Step 2 DG / CG collision processing (when DG and CG PUSCH overlap).
  • the DG timeline that overrides the CG may be checked.
  • the UCI multiplexed on PUSCH may be discarded together.
  • Step 3 UL skipping for CG or DG PUSCH after DG / CG collision processing.
  • Step 1 UCI Multiplexing If the multiplexing timeline is satisfied, the UCI may be multiplexed into the CG PUSCH. Otherwise, an error may occur.
  • CG PUSCH may be canceled / skipped. UCIs multiplexed on CG PUSCH may also be discarded.
  • Step 3 UL skipping If there is no TB to send for DG PUSCH (UL skipping is enabled), DG PUSCH may be skipped. As a result, UL transmission does not have to be performed.
  • DG PUSCH may be sent. As a result, DG PUSCH may be transmitted.
  • CG PUSCH may be canceled / skipped.
  • Step 3 UL skipping Since the UCI is multiplexed on the DG PUSCH, the DG PUSCH may be transmitted. As a result, a UCI-multiplexed DG PUSCH may be transmitted.
  • CG PUSCH may be canceled / skipped.
  • Step 3 UL skipping Since the UCI is multiplexed on the DG PUSCH, the DG PUSCH may be transmitted. As a result, a UCI-multiplexed DG PUSCH may be transmitted.
  • DG / CG collision processing The override timeline may always be filled. CG PUSCH may be canceled / skipped.
  • Step 3 UL skipping Since the UCI is multiplexed on the DG PUSCH, the DG PUSCH may be transmitted. As a result, a UCI-multiplexed DG PUSCH may be transmitted.
  • the UCI of PUCCH # 2 may be multiplexed with DG PUSCH. If not, an error may occur.
  • CG PUSCH may be canceled / skipped.
  • the UCI of PUCCH # 1 multiplexed with CG PUSCH may also be discarded.
  • Step 3 UL skipping Since the UCI is multiplexed on the DG PUSCH, the DG PUSCH may be transmitted. As a result, a DG PUSCH in which the UCI of PUCCH # 2 is multiplexed may be transmitted.
  • Step 2 UL skipping of CG or DG PUSCH If there are no TBs to be transferred and the UCI is not multiplexed in PUSCH (for DG PUSCH, UL skipping is enabled), it may be skipped. If it doesn't work this way, you can't skip PUSCH.
  • Step 3 DG / CG collision processing (when DG and CG PUSCH overlap).
  • the DG timeline that overrides the CG may be checked.
  • the UCI multiplexed on PUSCH may be discarded together.
  • -Alternative 1 DG / CG collision processing considering the UL skipping result of step 2 If the DG timeline that overrides CG PUSCH is satisfied and DG PUSCH is skipped in step 2, a MAC PDU for CG PUSCH is generated. , May be delivered to PHY.
  • the MAC PDU for CG PUSCH does not have to be generated even if CG PUSCH cannot be skipped as a result of step 2.
  • DG / CG collision processing that does not consider the UL skipping result of step 2. For example, if the timeline of DG exceeding CG PUSCH is satisfied, it does not matter whether or not DG PUSCH is skipped in step 2. , MAC PDU for CG PUSCH does not have to be generated.
  • Step 1 UCI Multiplexing If the multiplexing timeline is satisfied, the UCI may be multiplexed into the CG PUSCH. Otherwise, an error may occur.
  • Step 2 UL skipping If there is no TB to send for DG PUSCH (UL skipping is enabled), DG PUSCH may be skipped. Since UCI is multiplexed with CG PUSCH, CG PUSCH does not have to be skipped.
  • ⁇ 1 meets the DG override timeline -Alternative 1: If DG PUSCH is not skipped in step 2, CG PUSCH may be canceled / skipped. UCIs multiplexed on CG PUSCH may also be discarded. As a result, only DG PUSCH may be transmitted. If DG PUSCH is skipped in step 2, CG PUSCH may be transmitted. As a result, the UCI multiplexed CG PUSCH may be transmitted.
  • CG PUSCH may be canceled / skipped regardless of whether or not DG PUSCH was skipped in step 2.
  • UCIs multiplexed on CG PUSCH may also be discarded. As a result, if TB is not transmitted to DG PUSCH, UL transmission does not have to be performed. Otherwise, DG PUSCH may be sent.
  • FIG. 16 shows an operation flow diagram of the UE according to Option 1-3: Case 1.
  • Step 2 UL skipping Since the UCI is multiplexed on the DG PUSCH, the DG PUSCH may be transmitted.
  • CG PUSCH may be canceled / skipped.
  • a UCI-multiplexed DG PUSCH may be transmitted.
  • Step 2 UL skipping Since the UCI is multiplexed on the DG PUSCH, the DG PUSCH may be transmitted.
  • CG PUSCH may be canceled / skipped.
  • a UCI-multiplexed DG PUSCH may be transmitted.
  • Step 2 UL skipping Since the UCI is multiplexed on the DG PUSCH, the DG PUSCH may be transmitted.
  • DG / CG collision processing The override timeline may always be filled. CG PUSCH may be canceled / skipped. As a result, a UCI-multiplexed DG PUSCH may be transmitted.
  • the UCI of PUCCH # 2 may be multiplexed with DG PUSCH. If not, an error may occur.
  • Step 2 UL skipping Since the UCI is multiplexed on the DG PUSCH, the DG PUSCH may be transmitted.
  • CG PUSCH may be canceled / skipped.
  • the UCI of PUCCH # 1 multiplexed with CG PUSCH may also be discarded.
  • the DG PUSCH in which the UCI of PUCCH # 2 is multiplexed may be transmitted.
  • DG / CG collision may mean that DG PUSCH and CG PUSCH overlap in the time domain on the same component carrier (CC).
  • UL transmission behavior and timeline inspection include DG / CG collision handling, UL skipping, same priority UCI multiplexing, and intra-UE prioritization (intra-UE prioritization). Intra-UE prioritization) may be taken into consideration when deciding.
  • the order of DG / CG collision handling, UL skipping, UCI multiplexing within the same priority, and intra-UE prioritization for PUCCH / PUSCH with different priorities may be as follows:
  • DG / CG collision processing for determining DG PUSCH or CG PUSCH (when DG and CG PUSCH overlap) can be transmitted, and the others may be canceled or skipped.
  • the DG / CG collision processing timeline may be checked.
  • -Option 1 The start symbol of PUCCH may be considered in the timeline check of collision processing (similar to option 1 of option 1-1).
  • -Option 2 There are no additional considerations in the original DG / CG collision processing timeline for the applicable case.
  • Step 2 After excluding the PUSCH canceled / skipped in step 1, if the PUCCH overlaps with the PUSCH, the UCI may be multiplexed with the same priority. The multiplexing timeline may be checked.
  • Step 3 UL skipping of CG or DG PUSCH is executed.
  • Step 4 Prioritize within the UE when the output PUCCH and PUSCH with different priorities overlap.
  • LP (low priority) channels that overlap with HP (high priority) channels may be dropped.
  • the order of step 3 and step 4 may be exchanged.
  • Step 2 UCI multiplexing Since the LP DG PUSCH is canceled / skipped in step 1, UCI multiplexing does not have to be performed.
  • Step 3 UL skipping HP CG PUSCH may be skipped if there is no TB to send to HP CG PUSCH. As a result, LP PUCCH may be transmitted. Otherwise, HP CG PUSCH may be sent. As a result, LP PUCCH and HP CG PUSCH may be transmitted.
  • Step 2 The UCI multiplexing LP DG PUSCH is canceled / skipped in step 1, so the LP PUCCH does not have to be multiplexed.
  • HP UCI may be multiplexed into HP CG PUSCH.
  • Step 3 UL skipping HP CG PUSCH cannot be skipped because HP UCI is multiplexed with HP CG PUSCH.
  • Step 4 Prioritize within UE (not required) As a result, HP CG PUSCH in which LP PUCCH and HP UCI are multiplexed may be transmitted.
  • Step 2 UCI multiplexing Since the LP CG PUSCH is canceled / skipped in step 1, UCI multiplexing does not have to be performed.
  • Step 3 UL skipping If there is no TB to send for HP DG PUSCH (UL skipping is enabled), HP DG PUSCH may be skipped. As a result, LP PUCCH may be transmitted. Otherwise, HP DG PUSCH may be sent. As a result, LP PUCCH and HP DG PUSCH may be transmitted.
  • Step 2 Since the UCI multiplexing LP CG PUSCH is canceled / skipped in step 1, the LP PUC CH does not have to be multiplexed. HP UCI may be multiplexed on HP DG PUSCH.
  • Step 3 UL skipping HP DG PUSCH cannot be skipped because HP UCI is multiplexed over HP DG PUSCH.
  • Step 4 Prioritize within UE (not required) As a result, HP UCI multiplexed LP PUCCH and HP DG PUSCH may be transmitted.
  • Step 2 DG / CG collision processing (when DG PUSCH and CG PUSCH overlap).
  • the DG / CG collision processing timeline may be checked.
  • the UCI multiplexed on PUSCH may be discarded together.
  • Step 3 UL skipping for CG PUSCH or DG PUSCH after DG / CG collision processing If there are no TBs to be transferred and the UCI is not multiplexed in PUSCH (for DG PUSCH, UL skipping is enabled), it may be skipped. If it doesn't work this way, you can't skip PUSCH.
  • Step 4 Prioritize within the UE when the output PUCCH and PUSCH with different priorities overlap.
  • LP channels that overlap with HP channels may be dropped.
  • the order of step 3 and step 4 may be exchanged.
  • Step 1 UCI Multiplexing LP UCI may be multiplexed into LP DG PUSCH.
  • DG / CG collision processing The operation of HP CG PUSCH and LP DG PUSCH has not been decided yet.
  • the CG PUSCH is transmitted and the LP PUSCH is canceled / skipped when the required timeline is met.
  • LP UCI multiplexed with LP DG PUSCH may also be discarded.
  • Step 3 UL skipping HP CG PUSCH may be skipped if there is no TB to send to HP CG PUSCH. As a result, UL transmission does not have to be performed. Otherwise, HP CG PUSCH may be sent. As a result, HP CG PUSCH may be transmitted.
  • Step 1 UCI Multiplexation LP UCI may be multiplexed to LP DG PUSCH and HP UCI may be multiplexed to HP CG PUSCH.
  • DG / CG collision processing The operation of HP CG PUSCH and LP DG PUSCH has not been decided yet.
  • the CG PUSCH is transmitted and the LP PUSCH is canceled / skipped when the required timeline is met.
  • LP UCI multiplexed with LP DG PUSCH may also be discarded.
  • Step 3 UL skipping HP CG PUSCH cannot be skipped because HP UCI is multiplexed with HP CG PUSCH.
  • Step 4 Prioritize within UE (not required) As a result, an HP CG PUSCH with HP UCI multiplexed may be transmitted.
  • DG / CG collision processing The operation of DG PUSCH and LP CG PUSCH has not been decided yet.
  • the HP DG PUSCH is transmitted and the LP CG PUSCH is canceled / skipped when the required timeline is met.
  • LP UCI multiplexed on LP CG PUSCH may also be discarded.
  • Step 3 UL skipping If there is no TB to send for HP DG PUSCH (UL skipping is enabled), HP DG PUSCH may be skipped. As a result, UL transmission does not have to be performed. Otherwise, HP DG PUSCH may be sent. As a result, HP DG PUSCH may be transmitted.
  • Step 1 UCI Multiplexation LP UCI may be multiplexed to LP CG PUSCH and HP UCI may be multiplexed to HP DG PUSCH.
  • Step 3 UL skipping HP DG PUSCH cannot be skipped because HP UCI is multiplexed with HP DG PUSCH.
  • Step 4 Prioritize within UE (not required) As a result, the HP DG PUSCH with the HP UCI multiplexed may be transmitted.
  • Step 2 UL skipping of CG or DG PUSCH after DG / CG collision processing If there are no TBs to be transferred and the UCI is not multiplexed in PUSCH (for DG PUSCH, UL skipping is enabled), it may be skipped. If it doesn't work this way, you can't skip PUSCH.
  • Step 3 DG / CG collision processing (when DG and CG PUSCH overlap).
  • the DG / CG overlap timeline may be checked.
  • the UCI multiplexed on PUSCH may be discarded together.
  • -Alternative 1 DG / CG collision processing considering the UL skipping result of step 2. For example, if the timeline is filled and one PUSCH is skipped in step 2, a MAC PDU for the other PUSCH is generated. If there is a TB for the other PUSCH, it may be delivered to the PHY.
  • -Alternative 2 DG / CG collision processing that does not consider the UL skipping result of step 2-Step 4:: Prioritization within the UE when overlapping between output PUCCH and PUSCH with different priorities. LP channels that overlap with HP channels may be dropped.
  • Step 1 UCI Multiplexing LP UCI may be multiplexed into LP DG PUSCH.
  • Step 2 UL skipping LP DG PUSCH cannot be skipped because LP UCI is multiplexed.
  • HP CG PUSCH may be skipped if there is no TB to send to HP CG PUSCH. If it doesn't work this way, you can't skip the HP CG PUSCH.
  • Option 1 An error case in which both two overlapping CG PUSCH / DG PUSCH cannot be skipped.
  • Option 2 Use step 3 instead of the error case to solve the problem.
  • -Alternative 1 DG / CG collision processing considering the UL skipping result of step 2 If HP CG PUSCH is skipped, LP DG PUSCH can be transmitted. As a result, the LP DG PUSCH with the LP UCI multiplexed may be transmitted. Otherwise, LP DG PUSCH may be canceled / skipped. LP UCI multiplexed with LP DG PUSCH may also be discarded. As a result, HP CG PUSCH may be transmitted.
  • LP DG PUSCH may be canceled or skipped regardless of whether or not HP CG PUSCH is skipped. If HP CG PUSCH is skipped, UL transmission does not have to be performed. Otherwise, HP CG PUSCH may be sent.
  • Step 1 UCI Multiplexation LP UCI may be multiplexed to LP DG PUSCH and HP UCI may be multiplexed to HP CG PUSCH.
  • Step 2 UL skipping HP CG and LP DG PUSCH cannot be skipped because UCI is multiplexed for HP and LP PUSCH.
  • Option 1 Make an error case where both overlapping two CG / DG cannot be skipped.
  • Option 2 Use step 3 instead of the error case to solve the problem.
  • LP DG PUSCH may be canceled / skipped in both alternative 1 and alternative 2.
  • LPUCI multiplexed with LPDGPUSCH may also be discarded.
  • HP CG PUSCH in which HP UCI is multiplexed may be transmitted.
  • UCI multiplexing LP UCI may be multiplexed into LP CG PUSCH.
  • Step 2 UL skipping LP CG PUSCH cannot be skipped because LP UCI is multiplexed.
  • HP DG PUSCH may be skipped if there is no TB to send to HP DG PUSCH. If it doesn't work this way, you can't skip the HP DG PUSCH.
  • Option 1 Make an error case where both overlapping two CG / DG cannot be skipped.
  • Option 2 Use step 3 instead of the error case to solve the problem.
  • -Alternative 1 DG / CG collision processing considering the UL skipping result of step 2 If HP DG PUSCH is skipped, LP CG PUSCH can be transmitted. As a result, the LP CG PUSCH in which the LP UCI is multiplexed may be transmitted. Otherwise, LP CG PUSCH may be canceled / skipped. LP UCI multiplexed on LP CG PUSCH may also be discarded. As a result, HP DG PUSCH may be transmitted.
  • LP CG PUSCH may be canceled / skipped regardless of whether HP DG PUSCH is skipped or not. If HP DG PUSCH is skipped, UL transmission does not have to be performed. Otherwise, HP DG PUSCH may be sent.
  • Step 1 UCI Multiplexation LP UCI may be multiplexed to LP CG PUSCH and HP UCI may be multiplexed to HP DG PUSCH.
  • Step 2 UL skipping HP DG and LP CG PUSCH cannot be skipped because UCI is multiplexed for HP and LP PUSCH.
  • Option 1 Make an error case where both overlapping two CG / DG cannot be skipped.
  • Option 2 Use step 3 instead of the error case to solve the problem.
  • LPCG PUSCH may be canceled / skipped in both alternative 1 and alternative 2.
  • LPUCI multiplexed on LPCGPUSCH may also be discarded.
  • HP DG PUSCH in which HP UCI is multiplexed may be transmitted.
  • Step 1 If PUCCH overlaps with PUSCH, multiplex UCI with the same priority.
  • the multiplexing timeline may be checked.
  • Step 2 UL skipping of CG or DG PUSCH after DG / CG collision processing If there are no TBs to be transferred and the UCI is not multiplexed in PUSCH (for DG PUSCH, UL skipping is enabled), it may be skipped. If it doesn't work this way, you can't skip PUSCH.
  • Option 2 Error case is not defined. If both the colliding CG and DG PUSCH cannot be skipped, the PDU to be generated or the PUSCH that can be transmitted may be determined according to step 3 and / or step 4.
  • Step 3 Prioritization within the UE when overlapping between output PUCCH and PUSCH with different priorities.
  • LP channels that overlap with HP channels may be dropped.
  • Step 4 DG / CG collision processing (when DG and CG PUSCH overlap).
  • the DG / CG collision processing timeline may be checked.
  • the UCI multiplexed on PUSCH may be discarded together.
  • Step 2 UL skipping If both of the two overlapping CG / DGs cannot be skipped, one of the following may be performed.
  • Option 2 Use step 4 instead of the error case to solve the problem.
  • Step 3 In-UE prioritization LP DG PUSCH overlaps with HP PUCCH and may be canceled.
  • Step 4 DG / CG collision processing LP DG PUSCH was canceled in step 3. If HP CG PUSCH is skipped in step 2, HP PUCCH may be transmitted. If you do not skip HP CG PUSCH in step 2, HP CG PUSCH and HP PUCCH may be sent.
  • Step 2 UL skipping If both of the two overlapping CG / DGs cannot be skipped, one of the following may be performed.
  • Option 2 Use step 4 instead of the error case to solve the problem.
  • LP CG PUSCH overlaps with HP PUCCH and may be canceled.
  • LP PUCCH overlaps with HP DG PUSCH and may be canceled.
  • Step 4 DG / CG collision processing LP CG PUSCH is canceled in step 3. If HP DG PUSCH was skipped in step 2, HP PUCCH may be sent. If HP DG PUSCH is not skipped in step 2, HP CG PUSCH and HP PUCCH may be sent.
  • Step 2 Prioritize within the UE when overlapping between output PUCCH and PUSCH with different priorities. LP channels that overlap with HP channels may be dropped.
  • Step 3 UL skipping for CG or DG PUSCH after DG / CG collision processing If there are no TBs to be transferred and the UCI is not multiplexed in PUSCH (for DG PUSCH, UL skipping is enabled), it may be skipped. If it doesn't work this way, you can't skip PUSCH.
  • step 4 may be followed to determine which PDU to generate or which PUSCH to send.
  • DG / CG collision processing (when DG and CG PUSCH overlap)
  • the DG / CG collision processing timeline may be checked.
  • the UCI multiplexed on PUSCH may be discarded together.
  • the two alternatives (as alternatives 1 and 2 of options 2-3) may be the result from step 3 with or without considering UL skipping.
  • Step 2 In-UE prioritization LP DG PUSCH overlaps with HP PUCCH and may be canceled.
  • Step 3 UL skipping HP CG PUSCH may be skipped if there is no TB to send to HP CG PUSCH.
  • Step 4 DG / CG collision processing LP DG PUSCH was canceled in step 2. If you skipped the HP CG PUSCH in step 3, the HP PUCCH may be sent. If HP CG PUSCH is not skipped in step 3, HP CG PUSCH and HP PUCCH may be transmitted.
  • Prioritization within UE LP CG PUSCH may be canceled as it overlaps with HP PUCCH.
  • LP PUCCH overlaps with HP DG PUSCH and may be canceled.
  • Step 3 UL skipping HP DG PUSCH may be skipped if there is no TB to send to HP DG PUSCH.
  • Step 4 DG / CG collision processing LP CG PUSCH was canceled in step 2. If HP DG PUSCH was skipped in step 3, HP PUCCH may be sent. If HP DG PUSCH is not skipped in step 3, HP DG PUSCH and HP PUCCH may be transmitted.
  • Step 2 Prioritization within the UE when overlapping between output PUCCH and PUSCH with different priorities. LP channels that overlap with HP channels may be dropped.
  • Step 3 DG / CG collision processing (when DG and CG PUSCH overlap).
  • the DG / CG collision processing timeline may be checked. If PUSCH is canceled / skipped, UCIs multiplexed on PUSCH may be discarded together.
  • Step 4 UL skipping of CG or DG PUSCH after DG / CG collision processing If there are no TBs to be transferred and the UCI is not multiplexed in PUSCH (for DG PUSCH, UL skipping is enabled), it may be skipped. If it doesn't work this way, you can't skip PUSCH.
  • Step 2 In-UE prioritization LP DG PUSCH overlaps with HP PUCCH and may be canceled.
  • Step 3 DG / CG collision processing LP DG PUSCH was canceled in step 2.
  • Step 4 UL skipping HP CG PUSCH may be skipped if there is no TB to send to HP CG PUSCH. As a result, HP PUCCH may be transmitted. If there is a TB to send for HP CG PUSCH, HP CG PUSCH may be sent. This result: HP CG PUSCH and HP PUCCH may be sent.
  • Prioritization within UE LP CG PUSCH may be canceled as it overlaps with HP PUCCH.
  • LP PUCCH overlaps with HP DG PUSCH and may be canceled.
  • Step 3 DG / CG collision processing LP CG PUSCH was canceled in step 2.
  • Step 4 UL skipping HP DG PUSCH may be skipped if there is no TB to send to HP DG PUSCH. As a result. HP PUCCH may be sent. If you have a TB to send to HP DG PUSCH, you may send HP DG PUSCH. You may send HP DG PUSCH and HP PUCCH.
  • PUSCH cancellation / skipping may be performed by the MAC layer or the PHY layer. Also, if the timeline is not satisfied by any of the optional steps described above, it may be treated as an error case.
  • the above-mentioned options may be set by the parameters of the upper layer (for example, RRC). For example, it may be reported as UE capability information (UE capability), or it may be specified as a 3GPP specification. In addition, specific options may be determined by the combination of the parameter settings of the upper layer and the reported UE abilities.
  • RRC Radio Resource Control
  • the UE may report whether it supports UL skipping for DG PUSCH.
  • the UE may report whether it supports CG / DG / UCI overlap processing with the same priority.
  • the UE may also report whether it supports CG / DG / UCI overlap processing with different priorities.
  • the UE 200 has a CG PUSCH when the PUCCH (uplink control channel), CG PUSCH (first uplink data channel) and DG PUSCH (second uplink data channel) have the same priority. Transmission in UL can be controlled based on temporal overlap between and DG PUSCH, UL skipping, and UCI (uplink control information) multiplexing to CG PUSCH or DG PUSCH.
  • PUCCH uplink control channel
  • CG PUSCH first uplink data channel
  • DG PUSCH second uplink data channel
  • CGPUSCH and DGPUSCH overlap in the time direction.
  • the plurality of UL transmissions can be processed efficiently and appropriately.
  • the wireless communication system 10 may be a wireless communication system according to a method called Beyond 5G, 5G Evolution, or 6G.
  • each functional block is 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 that makes transmission function is called a transmitting unit (transmitting unit) or a transmitter (transmitter).
  • transmitting unit transmitting unit
  • transmitter transmitter
  • FIG. 48 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. 3) is realized by any hardware element of the computer device or a combination of the hardware elements.
  • 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 composed of 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, an optical magnetic disk (for example, a compact disk, a digital versatile disk, or 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 memory 1002 and 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, keyboard, mouse, microphone, switch, button, sensor, etc.) that accepts 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), an Application Specific Integrated Circuit (ASIC), a Programmable Logic Device (PLD), and a Field Programmable Gate Array (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, broadcast information (Master Information Block)). (MIB), System Information Block (SIB)), other signals or a combination thereof.
  • DCI Downlink Control Information
  • UCI Uplink Control Information
  • RRC signaling eg RRC signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block)).
  • MIB System Information Block
  • SIB System Information Block
  • RRC signaling may also be referred to as an RRC message, for example, 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 the present disclosure may be performed by its upper node.
  • various operations performed for communication with a terminal are performed by the base station and other network nodes other than the base station (for example, 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. Input / output information can be overwritten, updated, or added. The output information may be deleted. The input information may be transmitted to another device.
  • 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 by any other name, 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 absolute values, relative values from predetermined values, or using other 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 small indoor base station (Remote Radio)). Communication services can also be provided by Head: RRH).
  • a base station subsystem eg, a small indoor base station (Remote Radio)
  • Communication services can also be provided by Head: RRH).
  • cell refers to a part or all of a base station that provides communication services in this coverage and at least one of the coverage areas of a 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, the 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 applies 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 radio 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. Subframes may further consist of one or more slots in the time domain.
  • the subframe may have a fixed time length (eg, 1 ms) that is independent of numerology.
  • the numerology may be a communication parameter that applies to at least one of the transmission and reception of a signal or channel.
  • Numerology includes, for example, SubCarrier Spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, wireless frame configuration, transmission / reception.
  • SCS SubCarrier Spacing
  • TTI transmission time interval
  • 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 may be indicated.
  • 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. Slots may be in numerology-based time units.
  • OFDM Orthogonal Frequency Division Multiplexing
  • SC-FDMA Single Carrier Frequency Division Multiple Access
  • the slot may include a plurality of mini slots. Each minislot may consist of one or more symbols in the time domain.
  • the mini-slot may also 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 have 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 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. It 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 radio 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.
  • the 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.
  • a TTI having a time length of 1 ms may be called a normal TTI (TTI in LTE Rel.8-12), a normal TTI, a long TTI, a normal subframe, a normal subframe, a long subframe, a slot, or the like.
  • TTIs shorter than normal TTIs may also 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 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, etc.) may represent a subset of consecutive common RBs (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, mini slots and symbols are merely examples.
  • the number of subframes contained in a wireless frame the number of slots per subframe or wireless 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, 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 domain.
  • Electromagnetic energy 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 applicable 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”, “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. Thus, 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). (For example, searching in a table, database or another data structure), ascertaining may be regarded as “judgment” or “decision”.
  • judgment and “decision” are receiving (for example, receiving information), transmitting (for example, transmitting information), input (input), output (output), and access.
  • Accessing (for example, accessing data in memory) may be regarded as "judgment” or “decision”.
  • judgment and “decision” mean that 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”.
  • Wireless communication system 20 NG-RAN 100 gNB 200 UE 210 Radio signal transmission / reception unit 220 Amplifier unit 230 Modulation / demodulation unit 240 Control signal / reference signal processing unit 250 Coding / decoding unit 260 Data transmission / reception unit 270 Control unit 1001 Processor 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)
  • Mobile Radio Communication Systems (AREA)

Abstract

Ce terminal transmet un canal de commande de liaison montante, un premier canal de données de liaison montante et un second canal de données de liaison montante. Si le canal de commande de liaison montante, le premier canal de données de liaison montante, et le second canal de données de liaison montante ont la même priorité, le terminal commande une transmission de liaison montante sur la base d'un chevauchement dans la direction temporelle entre le premier canal de données de liaison montante et le second canal de données de liaison montante, des omissions de transmission de liaison montante, et le multiplexage d'informations de commande de liaison montante au premier canal de données de liaison montante ou au second canal de données de liaison montante.
PCT/JP2021/001532 2021-01-18 2021-01-18 Terminal et procédé de communication sans fil WO2022153545A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/JP2021/001532 WO2022153545A1 (fr) 2021-01-18 2021-01-18 Terminal et procédé de communication sans fil
CN202180090677.7A CN116711433A (zh) 2021-01-18 2021-01-18 终端以及无线通信方法

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2021/001532 WO2022153545A1 (fr) 2021-01-18 2021-01-18 Terminal et procédé de communication sans fil

Publications (1)

Publication Number Publication Date
WO2022153545A1 true WO2022153545A1 (fr) 2022-07-21

Family

ID=82447043

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2021/001532 WO2022153545A1 (fr) 2021-01-18 2021-01-18 Terminal et procédé de communication sans fil

Country Status (2)

Country Link
CN (1) CN116711433A (fr)
WO (1) WO2022153545A1 (fr)

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "UL PUSCH skipping without intra-UE prioritization", 3GPP DRAFT; R2-2100340, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Electronic meeting; 20210125 - 20210205, 14 January 2021 (2021-01-14), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051972650 *
HUAWEI, HISILICON: "Updates to RAN2 aspects of PUSCH with UL skipping", 3GPP DRAFT; R2-2101776, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Online; 20210125 - 20210205, 15 January 2021 (2021-01-15), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051974641 *
MODERATOR (VIVO): "Summary of email discussion [103-e-NR-7.1CRs-08]-phase 2", 3GPP DRAFT; R1-2009774, 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, 14 November 2020 (2020-11-14), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051954423 *
MODERATOR (VIVO): "Summary of email discussion [103-e-NR-L1enh-URLLC-07]", 3GPP DRAFT; R1-2009684, 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, 11 November 2020 (2020-11-11), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051953515 *

Also Published As

Publication number Publication date
CN116711433A (zh) 2023-09-05

Similar Documents

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

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: 21919438

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 202180090677.7

Country of ref document: CN

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21919438

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: JP