CN116711433A

CN116711433A - Terminal and wireless communication method

Info

Publication number: CN116711433A
Application number: CN202180090677.7A
Authority: CN
Inventors: 高桥优元; 永田聪; 皮启平; 王静; 陈岚
Original assignee: NTT Docomo Inc
Current assignee: NTT Docomo Inc
Priority date: 2021-01-18
Filing date: 2021-01-18
Publication date: 2023-09-05
Also published as: WO2022153545A1

Abstract

The terminal transmits an uplink control channel, a 1 st uplink data channel and a 2 nd uplink data channel. When the uplink control channel, the 1 st uplink data channel and the 2 nd uplink data channel have the same priority, the terminal controls transmission in the uplink according to repetition of the 1 st uplink data channel and the 2 nd uplink data channel in the time direction, omission of uplink transmission, and multiplexing of uplink control information to the 1 st uplink data channel or the 2 nd uplink data channel.

Description

Terminal and wireless communication method

Technical Field

The present disclosure relates to a terminal supporting priority or multiplexing processing of uplink traffic and a wireless communication method.

Background

In the third Generation partnership project (3GPP:3rd Generation Partnership Project), the fifth Generation mobile communication system (also referred to as 5G, new Radio, or Next Generation (NG)) is normalized, and the Next Generation, referred to as Beyond 5G, 5G event, or 6G, is also being normalized.

In release 16 of 3GPP, format2_4 (format 2_4) in which downlink control information (DCI: downlink Control Information) is introduced may cancel UL transmission with a low priority in order to ensure (preempt) Uplink (UL) transmission with a high priority.

In release 17 of 3GPP, multiplexing processing and the like in terminals (UE: user Equipment) having UL services with different priorities are agreed (for example, non-patent document 1).

Also, a mechanism of omitting (skip) UL transmission in the case where a plurality of UL transmissions are repeated in the time direction has been studied (non-patent document 2).

Prior art literature

Non-patent literature

Non-patent document 1: "Enhanced Industrial Internet of Things (IoT) and ultra-reliable and low latency communication", month 7 of RP-201310,3GPP TSG RAN Meeting#88e,3GPP,2020

Non-patent document 2: "RAN1 Chairman's Notes",3GPP TSG RAN WG1 Meeting#102-e, e-Meeting,3GPP, month 8 in 2020

Disclosure of Invention

However, the processing for a plurality of UL transmissions having the same or different priorities may be different depending on the content (channel type, etc.) of the UL transmission.

Accordingly, the following disclosure has been 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.

One embodiment of the present disclosure is a terminal (UE 200) having: a transmitting unit (wireless signal transmitting/receiving unit 210) that transmits an uplink control channel, a 1 st uplink data channel, and a 2 nd uplink data channel; and a control unit (control unit 270), wherein when the uplink control channel, the 1 st uplink data channel, and the 2 nd uplink data channel have the same priority, the control unit (control unit 270) controls transmission in the uplink according to repetition of the 1 st uplink data channel and the 2 nd uplink data channel in the time direction, omission of uplink transmission, and multiplexing of uplink control information to the 1 st uplink data channel or the 2 nd uplink data channel.

One embodiment of the present disclosure is a terminal (UE 200) having: a transmitting unit (wireless signal transmitting/receiving unit 210) that transmits an uplink control channel, a 1 st uplink data channel, and a 2 nd uplink data channel; and a control unit (control unit 270), wherein when the uplink control channel, the 1 st uplink data channel, and the 2 nd uplink data channel have different priorities, the control unit (control unit 270) controls transmission in the uplink according to repetition of the 1 st uplink data channel and the 2 nd uplink data channel in the time direction, transmission omission of the uplink, multiplexing of uplink control information to the 1 st uplink data channel or the 2 nd uplink data channel, and intra-terminal priority/multiplexing processing.

One embodiment of the present disclosure is a wireless communication method including the steps of: the terminal transmits an uplink control channel, a 1 st uplink data channel and a 2 nd uplink data channel; and controlling, by the terminal, transmission in the uplink according to repetition of the 1 st uplink data channel and the 2 nd uplink data channel in a time direction, omission of transmission of an uplink, and multiplexing of uplink control information to the 1 st uplink data channel or the 2 nd uplink data channel when the uplink control channel, the 1 st uplink data channel, and the 2 nd uplink data channel have the same priority.

One embodiment of the present disclosure is a wireless communication method including the steps of: the terminal transmits an uplink control channel, a 1 st uplink data channel and a 2 nd uplink data channel; and controlling the transmission in the uplink by the terminal according to repetition of the 1 st uplink data channel and the 2 nd uplink data channel in the time direction, omission of transmission of an uplink, multiplexing of uplink control information to the 1 st uplink data channel or the 2 nd uplink data channel, and intra-terminal priority/multiplexing processing in the case that the uplink control channel, the 1 st uplink data channel and the 2 nd uplink data channel have different priorities.

Drawings

Fig. 1 is a schematic overall configuration diagram of a wireless communication system 10.

Fig. 2 is a diagram showing a configuration example of radio frames, subframes, and slots 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 the following options 1-1: fig. 1 illustrates a timeline of DG PUSCH, CG PUSCH, and PUCCH.

Fig. 5 is a diagram of the following options 1-1: the operation flow chart of the UE in case 1.

Fig. 6 is a diagram of the following options 1-1: fig. 2 is a diagram of a timeline of DG PUSCH, CG PUSCH, and PUCCH.

Fig. 7 is a diagram showing the following options 1-1: fig. 3 is a diagram of a timeline of DG PUSCH, CG PUSCH, and PUCCH.

Fig. 8 is a diagram showing the following options 1-1: fig. 4 is a diagram of a timeline of DG PUSCH, CG PUSCH, and PUCCH.

Fig. 9 is a diagram showing the following options 1-1: fig. 5 illustrates a timeline of DG PUSCH, CG PUSCH, and PUCCH.

Fig. 10 is a diagram showing the following options 1-2: fig. 1 illustrates a timeline of DG PUSCH, CG PUSCH, and PUCCH.

Fig. 11 is a diagram showing the following options 1-2: fig. 2 is a diagram of a timeline of DG PUSCH, CG PUSCH, and PUCCH.

Fig. 12 is a diagram showing the following options 1-2: fig. 3 is a diagram of a timeline of DG PUSCH, CG PUSCH, and PUCCH.

Fig. 13 is a diagram showing the following options 1-1: fig. 4 is a diagram of a timeline of DG PUSCH, CG PUSCH, and PUCCH.

Fig. 14 is a diagram showing the following options 1-1: fig. 5 illustrates a timeline of DG PUSCH, CG PUSCH, and PUCCH.

Fig. 15 is a diagram showing the following options 1-3: fig. 1 illustrates a timeline of DG PUSCH, CG PUSCH, and PUCCH.

Fig. 16 is a diagram of options 1-3: the operation flow chart of the UE in case 1.

Fig. 17 is a diagram showing the following options 1-3: fig. 2 is a diagram of a timeline of DG PUSCH, CG PUSCH, and PUCCH.

Fig. 18 is a diagram showing the following options 1-3: fig. 3 is a diagram of a timeline of DG PUSCH, CG PUSCH, and PUCCH.

Fig. 19 is a diagram showing the following options 1-3: fig. 4 is a diagram of a timeline of DG PUSCH, CG PUSCH, and PUCCH.

Fig. 20 is a diagram showing the following options 1-3: fig. 5 illustrates a timeline of DG PUSCH, CG PUSCH, and PUCCH.

Fig. 21 is a diagram showing the following options 2-1: fig. 1 illustrates a timeline of DG PUSCH, CG PUSCH, and PUCCH.

Fig. 22 is a diagram showing the following options 2-1: fig. 2 is a diagram of a timeline of DG PUSCH, CG PUSCH, and PUCCH.

Fig. 23 is a diagram showing the following options 2-1: fig. 3 is a diagram of a timeline of DG PUSCH, CG PUSCH, and PUCCH.

Fig. 24 is a diagram showing the following options 2-1: fig. 4 is a diagram of a timeline of DG PUSCH, CG PUSCH, and PUCCH.

Fig. 25 is a diagram showing the following options 2-1: fig. 5 illustrates a timeline of DG PUSCH, CG PUSCH, and PUCCH.

Fig. 26 is a diagram showing the following options 2-1: fig. 6 is a diagram of a timeline of DG PUSCH, CG PUSCH, and PUCCH.

Fig. 27 is a diagram showing the following options 2-2: fig. 1 illustrates a timeline of DG PUSCH, CG PUSCH, and PUCCH.

Fig. 28 is a diagram showing the following options 2-2: fig. 2 is a diagram of a timeline of DG PUSCH, CG PUSCH, and PUCCH.

Fig. 29 is a diagram showing the following options 2-2: fig. 3 is a diagram of a timeline of DG PUSCH, CG PUSCH, and PUCCH.

Fig. 30 is a diagram showing the following options 2-2: fig. 4 is a diagram of a timeline of DG PUSCH, CG PUSCH, and PUCCH.

Fig. 31 is a diagram showing the following options 2-2: fig. 5 illustrates a timeline of DG PUSCH, CG PUSCH, and PUCCH.

Fig. 32 is a diagram showing the following options 2-2: fig. 6 is a diagram of a timeline of DG PUSCH, CG PUSCH, and PUCCH.

Fig. 33 is a diagram showing the following options 2-3: fig. 1 illustrates a timeline of DG PUSCH, CG PUSCH, and PUCCH.

Fig. 34 is a diagram showing the following options 2-3: fig. 2 is a diagram of a timeline of DG PUSCH, CG PUSCH, and PUCCH.

Fig. 35 is a diagram showing the following options 2-3: fig. 3 is a diagram of a timeline of DG PUSCH, CG PUSCH, and PUCCH.

Fig. 36 is a diagram showing the following options 2-3: fig. 4 is a diagram of a timeline of DG PUSCH, CG PUSCH, and PUCCH.

Fig. 37 is a diagram showing the following options 2-3: fig. 5 illustrates a timeline of DG PUSCH, CG PUSCH, and PUCCH.

Fig. 38 is a diagram showing the following options 2-3: fig. 6 is a diagram of a timeline of DG PUSCH, CG PUSCH, and PUCCH.

Fig. 39 is a diagram showing the following options 2-4: fig. 7 is a diagram of a timeline of DG PUSCH, CG PUSCH, and PUCCH.

Fig. 40 is a diagram showing and option 2-4: fig. 8 illustrates a timeline of DG PUSCH, CG PUSCH, and PUCCH.

Fig. 41 is a diagram showing and option 2-4: fig. 9 is a diagram of a timeline of DG PUSCH, CG PUSCH, and PUCCH.

Fig. 42 is a diagram showing and option 2-5: fig. 7 is a diagram of a timeline of DG PUSCH, CG PUSCH, and PUCCH.

Fig. 43 is a diagram showing and option 2-5: fig. 8 illustrates a timeline of DG PUSCH, CG PUSCH, and PUCCH.

FIG. 44 is a diagram showing and options 2-5: fig. 9 is a diagram of a timeline of DG PUSCH, CG PUSCH, and PUCCH.

Fig. 45 is a diagram showing and option 2-6: fig. 7 is a diagram of a timeline of DG PUSCH, CG PUSCH, and PUCCH.

Fig. 46 is a diagram showing the following options 2-6: fig. 8 illustrates a timeline of DG PUSCH, CG PUSCH, and PUCCH.

Fig. 47 is a diagram showing and option 2-6: fig. 9 is a diagram of a timeline of DG PUSCH, CG PUSCH, and PUCCH.

Fig. 48 is a diagram showing an example of the hardware configuration of the gNB 100 and the UE 200.

Detailed Description

Embodiments will be described below with reference to the drawings. The same functions and structures are denoted by the same or similar symbols, and description thereof is omitted as appropriate.

(1) Overall outline structure of radio communication system

Fig. 1 is a schematic overall configuration diagram of a radio communication system 10 according to the present embodiment. The Radio communication system 10 is a Radio communication system according to a New air interface (NR: new Radio) of 5G, and includes a Next Generation Radio access network 20 (Next Generation-Radio Access Network) (hereinafter, referred to as NG-RAN 20) and a User Equipment 200 (hereinafter, referred to as UE 200).

The NG-RAN 20 includes a radio base station 100 (hereinafter referred to as a gNB 100). In addition, the specific structure of the wireless communication system 10 including the number of gnbs and UEs is not limited to the example shown in fig. 1.

The NG-RAN 20 actually comprises a plurality of NG-RAN nodes, in particular a plurality of gnbs (or NG-enbs), connected to a core network (5 GC, not shown) according to 5G. In addition, the NG-RAN 20 and 5GC may be simply expressed as a "network".

The gNB 100 is a radio base station according to NR, and performs radio communication according to NR with the UE 200. The gNB 100 and the UE 200 can support a large scale MIMO (Massive MIMO) that generates a beam with higher directivity by controlling wireless signals transmitted from a plurality of antenna elements, carrier Aggregation (CA) that bundles a plurality of Component Carriers (CCs), and Dual Connection (DC) that simultaneously communicates between the UE and a plurality of NG-RAN nodes, respectively, and the like.

The wireless communication system 10 supports FR1 and FR2. The frequency bands of the respective FRs are as follows.

·FR1：410MHz～7.125GHz

·FR2：24.25GHz～52.6GHz

In FR1, a subcarrier Spacing (SCS: sub-Carrier Spacing) of 15, 30 or 60kHz can be used, using a Bandwidth (BW) of 5-100 MHz. FR2 has a higher frequency than FR1, and can use SCS of 60 or 120kHz (240 kHz may be included) and use Bandwidth (BW) of 50 to 400 MHz.

The wireless communication system 10 may support a frequency band higher than the frequency band of FR2. Specifically, the wireless communication system 10 is capable of supporting frequency bands in excess of 52.6GHz up to 114.25 GHz.

In addition, cyclic Prefix-orthogonal frequency division multiplexing (CP-OFDM: cyclic Prefix-Orthogonal Frequency Division Multiplexing)/discrete Fourier transform-Spread OFDM (DFT-S-OFDM: discrete Fourier Transform-Spread) with a larger subcarrier Spacing (SCS: sub-Carrier Spacing) may be applied. Also, DFT-S-OFDM is applied not only to Uplink (UL) but also to Downlink (DL).

Fig. 2 shows an example of the structure of radio frames, subframes, and slots used in the wireless communication system 10.

As shown in fig. 2, 1 slot is composed of 14 symbols, and the larger (wide) the SCS is, the shorter the symbol period (slot period) is. The number of symbols constituting 1 slot may not necessarily be 14 symbols (for example, 28 or 56 symbols). Furthermore, the number of slots per subframe may also be different according to SCS. Also, the SCS may be wider than 240kHz (e.g., 480kHz, 960kHz as shown in FIG. 3).

In addition, the time direction (t) shown in fig. 2 may also be referred to as a time domain, a symbol period, a symbol time, or the like. In addition, the frequency direction may also be referred to as a frequency domain, a resource block, a subcarrier, BWP (Bandwidth part), or the like.

In addition, in the wireless communication system 10, a plurality of pieces of downlink control information (DCI: downlink Control Information) may be used. The DCI may also be interpreted as control information transmitted in a downlink including scheduling information, data modulation, and channel coding rate information required for each User (UE) to demodulate data, and the like.

In particular, in the present embodiment, in order to ensure (preempt) Uplink (UL) transmission with a higher priority and cancel UL transmission with a lower priority, DCI format 2_4 (DC format 2_4) may be used. DCI format 2_4 may be used to inform a group of UEs of a Physical Resource Block (PRB) and an OFDM symbol to cancel a corresponding UL transmission from UE 20. That is, DCI format 2_4 may also be interpreted as a format informing PRBs and OFDM symbols where UL transmission is canceled. In addition, cancellation may be replaced with cancellation, stop, suspension, or the like.

DCI format 2_4 may be indicated in the following form.

Cancellation indication 1,Cancellation indication 2, … …, cancellation indication N UE 200 can cancel UL transmission, specifically, transmission of PUSCH (Physical Uplink Shared Channel (physical uplink shared channel), uplink data channel), sounding reference signal (SRS: sounding Reference Signal) or the like, according to a cancel instruction (Cancellation Indication) of UL indicated by DCI format 2_4 (may also be referred to as UL CI). The UL CI may cancel PUCCH (Physical Uplink Control Channel (physical uplink control channel) and uplink control channel).

Further, in the wireless communication system 10, multiplexing (Intra-UE multiplexing) of UL traffic having different priorities within the UE 200 may be supported. Specifically, the UE 200 may multiplex a Low Priority (LP) service and a High Priority (HP) service and transmit the result of multiplexing the service (multiplexing result) via UL.

And, priority handling (Intra-UE prioritization) of UL traffic with different priorities within the UE 200 may be supported. For example, the UE 200 may prioritize the transmission of HP traffic and not the transmission (drop) of LP traffic.

Traffic may also be replaced with channels, data channels, control channels, paths, data or control data, etc. In addition, LP may also be expressed as priority 1 and HP may also be expressed as (or conversely) priority 2. The multiplexed results may also be replaced with results (outomes), achievements, conversions, outputs, or the like.

(2) Functional block structure of radio communication system

Next, the functional block configuration of the wireless communication system 10 will be described. Specifically, the functional block configuration of the UE 200 will be described.

Fig. 3 is a functional block configuration diagram of the UE 200. As shown in fig. 3, the UE 200 includes a radio signal transmitting/receiving unit 210, an amplifying unit 220, a modem unit 230, a control signal/reference signal processing unit 240, an encoding/decoding unit 250, a data transmitting/receiving unit 260, and a control unit 270. The gNB 100 (radio base station) may have substantially the same functional block configuration.

The radio signal transmitting/receiving section 210 transmits/receives a radio signal according to NR. The radio signal transmitting/receiving section 210 supports a large-scale MIMO (Massive MIMO), CA binding a plurality of CCs, DC for simultaneously performing communication between the UE and two NG-RAN nodes, and the like.

In particular, in the present embodiment, the radio signal transmitting/receiving unit 210 can transmit UL traffic having different priorities via a predetermined UL channel. Specifically, the wireless signal transmitting/receiving unit 210 can transmit the multiplexing result of the service (1 st service) having the Low Priority (LP) and the service (2 nd service) having the High Priority (HP) multiplexed.

The radio signal transmitting/receiving section 210 can transmit various UL channels. Specifically, the wireless signal transmitting/receiving unit 210 can transmit an uplink control channel, a 1 st uplink data channel, and a 2 nd uplink data channel of a Physical (PHY) layer (layer 1). In the present embodiment, the wireless signal transmitting/receiving unit 210 constitutes a transmitting unit.

More specifically, the radio signal transmitting/receiving unit 210 can transmit PUCCH and PUSCH. The PUSCH may include a CG (Configured Grant) PUSCH (1 st uplink data channel) and a DG (Dynamic Grant) PUSCH. CG PUSCH may be transmitted without transmission of a Scheduling Request (SR) or reception of UL Grant (DG). On the other hand, DG PUSCH may be transmitted according to UL Grant (UL Grant).

The amplifying unit 220 is configured by PA (Power Amplifier)/LNA (Low Noise Amplifier ) or the like. The amplifying section 220 amplifies the signal output from the modem section 230 to a predetermined power level. The amplifying unit 220 amplifies the RF signal output from the wireless signal transmitting/receiving unit 210.

The modem unit 230 performs data modulation/demodulation, transmission power setting, resource block allocation, and the like for each predetermined communication target (gNB 100, etc.). In the modem unit 230, cyclic Prefix-orthogonal frequency division multiplexing (CP-OFDM: cyclic Prefix-Orthogonal Frequency Division Multiplexing)/discrete fourier transform-Spread (DFT-S-OFDM: discrete Fourier Transform-Spread OFDM) may be applied. Further, DFT-S-OFDM is used not only for Uplink (UL) but also for Downlink (DL).

The control signal/reference signal processing unit 240 performs processing related to various control signals transmitted and received by the UE 200 and processing related to various reference signals transmitted and received by the UE 200.

Specifically, the control signal/reference signal processing unit 240 receives various control signals transmitted from the gNB 100 via a predetermined control channel, for example, a control signal of a radio resource control layer (RRC). The control signal/reference signal processing unit 240 transmits various control signals to the gNB 100 via a predetermined control channel.

The control signal/reference signal processing unit 240 performs processing using Reference Signals (RS) such as demodulation reference signals (DMRS: demodulation Reference Signal) and phase tracking reference signals (PTRS: phase Tracking Reference Signal).

The DMRS is a terminal-specific reference signal (Pilot) known between base stations and terminals for estimating a fading channel used for data demodulation. PTRS is a reference signal dedicated to a terminal for the purpose of estimating phase noise that is a problem in a high frequency band.

The Reference signals may include, in addition to DMRS and PTRS, a channel state information Reference Signal (CSI-RS: channel State Information-Reference Signal), a sounding Reference Signal (SRS: sounding Reference Signal), a positioning Reference Signal for position information (PRS: positioning Reference Signal), and the like.

In addition, the channels include control channels and data channels. The control channel may include a PDCCH (Physical Downlink Control Channel: physical downlink control channel), a PUCCH (Physical Uplink Control Channel: physical uplink control channel), a RACH (including a random access channel (Random Access Channel), downlink control information (DCI: downlink Control Information) of a random access radio network temporary identifier (RA-RNTI: random Access Radio Network Temporary Identifier)), a physical broadcast channel (PBCH: physical Broadcast Channel), and the like.

The data channel includes PDSCH (Physical Downlink Shared Channel: physical downlink shared channel), PUSCH (Physical Uplink Shared Channel: physical uplink shared channel), and the like. Data may mean data transmitted via a data channel.

The PUCCH may also be interpreted as a UL physical channel for transmission of UCI (Uplink Control Information: uplink control information). UCI can be transmitted through either PUCCH or PUSCH depending on the situation. The DCI may be always transmitted through the PDCCH or may be transmitted without passing through the PDSCH.

The UCI may include at least any one of ACK/NACK of a hybrid automatic retransmission request (HARQ: hybrid automatic repeat request), a Scheduling Request (SR) from the UE 200, and channel state information (CSI: channel State Information).

The timing of transmitting PUCCH and radio resources may be controlled by DCI in the same manner as the data channel.

The encoding/decoding section 250 performs division/concatenation of data, channel encoding/decoding, and the like for each predetermined communication target (gNB 100 or other gnbs).

Specifically, the encoding/decoding section 250 divides the data outputted from the data transmitting/receiving section 260 into predetermined sizes, and performs channel encoding on the divided data. The encoding/decoding unit 250 decodes the data output from the modem unit 230, and concatenates the decoded data.

The data transmitting/receiving section 260 performs transmission/reception of protocol data units (PDU: protocol Data Unit) and service data units (SDU: service Data Unit). Specifically, the data transmitting/receiving section 260 performs assembly/disassembly of PDUs/SDUs in a plurality of layers (medium access control layer (MAC), radio link control layer (RLC), packet data convergence protocol layer (PDCP), etc.), and the like. The data transceiver 260 performs error correction and retransmission control of data according to a hybrid automatic retransmission request (HARQ: hybrid automatic repeat request).

The control unit 270 controls each functional block constituting the UE 200. In particular, in the present embodiment, the control unit 270 can perform multiplexing processing of UL traffic having different priorities.

Specifically, the control unit 270 can execute multiplexing processing of a service (1 st service) having a low priority (1 st priority) and a service (2 nd service) having a higher priority (also expressed as a 2 nd priority different from the 1 st priority) having a higher priority than the low priority. Multiplexing may be replaced by multiplexing, combining, or overlapping terms. In addition, as described above, traffic may be replaced with channels, data channels, control channels, paths, data, control data, or the like.

The control section 270 may multiplex a plurality of Low Priority (LP) services (1 st service), and multiplex a plurality of High Priority (HP) services (2 nd service), and further multiplex a multiplexing result obtained by multiplexing a plurality of LP services and a multiplexing result obtained by multiplexing a plurality of HP services.

Further, the control section 270 may also generate a multiplexing result by multiplexing one or more LP services with one or more HP services.

Alternatively, the control unit 270 may generate a multiplexing result by multiplexing a plurality of LP services, and generate a multiplexing result by multiplexing the multiplexing result with one or more HP services. In contrast, the control section 270 may also generate a multiplexing result by multiplexing a plurality of HP services, and generate a multiplexing result by multiplexing the multiplexing result with one or more LP services.

In addition, the multiplexing method of the LP service and the HP service is not limited to these modes. For example, the control unit 270 may perform processing for multiplexing one or more LP services with one or more HP services a plurality of times, and perform multiplexing processing at a hierarchy level in which the plurality of multiplexing results are further multiplexed. In addition, the multiplexing process may have more levels.

In addition, when PUCCH (uplink control channel), CG PUSCH (1 st uplink data channel), and DG PUSCH (2 nd uplink data channel) have the same priority, the control unit 270 may control transmission in UL according to repetition of CG PUSCH and DG PUSCH in the time direction, omission of UL transmission (may also be referred to as UL skip), and multiplexing of UCI (uplink control information) to CG PUSCH or DG PUSCH.

Specifically, when a collision between DG PUSCH and CG PUSCH in the time direction (may also be referred to as repetition, overlap, or the like) occurs, the control unit 270 may determine which PUSCH to transmit. Next, when the PUCCH overlaps with the PUSCH determined to be transmitted, control unit 270 may multiplex UCI with the PUSCH. The control unit 270 may execute UL skip of PUSCH (either DG PUSCH or CG PUSCH) determined not to be transmitted.

In addition, transmission in UL may not necessarily be controlled according to repetition of CG PUSCH and DG PUSCH in the time direction, UL skip, and multiplexing of UCI to CG PUSCH or DG PUSCH.

In addition, when PUCCH (uplink control channel), CG PUSCH (1 st uplink data channel), and DG PUSCH (2 nd uplink data channel) have different priorities, the control unit 270 may control transmission in UL according to repetition of CG PUSCH and DG PUSCH in the time direction, multiplexing of UCI (uplink control information) to CG PUSCH or DG PUSCH, and Intra-terminal priority/multiplexing processing.

Specifically, when a collision between DG PUSCH and CG PUSCH in the time direction occurs, the control unit 270 may determine which PUSCH to transmit. Next, when the PUCCH overlaps with the PUSCH determined to be transmitted, control unit 270 may multiplex UCI with the PUSCH. The control unit 270 may execute UL skip of PUSCH (either DG PUSCH or CG PUSCH) determined not to be transmitted. Also, in the case where PUCCHs having different priorities overlap with PUSCHs, the control unit 270 may execute Intra-UE prioritization/multiplexing.

(3) Operation of a wireless communication system

Next, an operation of the wireless communication system 10 will be described. Specifically, operations related to collision processing between DG PUSCH and CG PUSCH, multiplexing of UCI, transmission omission of UL (UL scheduling), and Intra-UE prioritization/multiplexing when transmission of CG, DG, and UCI is repeated will be described.

(3.1) precondition

In releases 15 and 16 of 3GPP, the following is assumed for overlapping CG/DG/UCI having the same priority.

Case 1-1: only DG PUSCH overlaps PUCCH

The MAC generates a MAC PDU for DG PUSCH, and UCI is multiplexed to DG PUSCH.

Case 1-2: CG PUSCH and PUCCH only overlapping

The MAC generates a MAC PDU for CG PUSCH and distributes the MAC PDU to a physical layer (PHY). UCI is multiplexed to CG PUSCH.

Case 1-3: DG PUSCH overlaps CG PUSCH, DG PUSCH/CG PUSCH overlaps PUCCH

The MAC generates a MAC PDU for DG PUSCH, and UCI is multiplexed to DG PUSCH. The MAC does not generate a Transport Block (TB) for CG PUSCH overlapping with DG PUSCH of the same serving cell. CG PUSCH is discarded and does not participate in the subsequent physical layer procedure.

Case 1-4: DG PUSCH overlaps CG PUSCH, DG PUSCH overlaps PUCCH

The MAC generates a MAC PDU for DG PUSCH, and UCI is multiplexed to DG PUSCH. TB (Transport Block) for CG PUSCH overlapping with DG PUSCH of the same serving cell is not generated. CG PUSCH is discarded and does not participate in the subsequent physical layer procedure.

Case 1-5: DG PUSCH and CG PUSCH are not overlapped, and DG PUSCH and CG PUSCH are overlapped with PUCCH

The MAC generates a MAC PDU for DG PUSCH, and UCI is multiplexed to DG PUSCH.

Cases 1-6: DG PUSCH and CG PUSCH overlap, CG PUSCH and PUCCH overlap, and in this case, research has been continued in release 16 of 3 GPP.

With respect to UL skip of releases 15, 16 of 3GPP considering CG/DG/UCI with the same priority, no behavior is decided for the above case. The main problems are DG/CG conflict processing, UL skip and UCI multiplexing sequence.

Furthermore, regarding the collision of DG PUSCH and CG PUSCH with different priorities in release 17 of 3GPP, UL skip and CG/DG/UCI with different priorities need to be considered. In this case, the main problems are DG/CG collision processing, UL scheduling, UCI multiplexing within the same priority, and order of priority assignment within UEs for PUCCH/PUSCH of different priorities.

(3.2) working example 1

In case a (PUCCH, CG PUSCH, and DG PUSCH of the same priority), the behavior of UL transmission and time line check (may also be referred to as integration in the time direction, etc.) may be determined in consideration of DG/CG collision processing, UL skip, UCI multiplexing. The order of DG/CG conflict processing, UL skip and UCI multiplexing is as follows.

(option 1-1)

Step 1: DG/CG conflict handling for deciding DG PUSCH or CG PUSCH (in case DG PUSCH overlaps CG PUSCH) is transmittable, other handling may be cancelled or skipped. The time line of DG PUSCH of the overwriting CG PUSCH may be checked (check).

In the case where the cancelled (skipped) PUSCH is repeated with other PUCCHs that are not repeated with the non-cancelled (skipped) PUSCH, the operation may be performed as follows.

Option 1: the reference indication of "the start symbol of CG PUSCH" is replaced with "the earliest symbol among the start symbols of CG PUSCH and the start symbol of overlapping PUCCH that does not overlap DG PUSCH".

Option 2: a timeline of DG PUSCH that overwrites CG PUSCH is applied as in release 16 of 3 GPP.

Analysis: DG/CG conflict handling may have an impact on UCI multiplexing of step 2 and therefore option 1 may be recommended. In the case where Δ2 cannot satisfy the DG-overwritten time line as in the case of case 1 (fig. 4), the UE may not be ready to transmit the PUCCH.

Step 2: UCI multiplexing may be performed in a case where PUCCH overlaps PUSCH after excluding PUSCH cancelled/skipped in step 1. The multiplexed time line may also be checked.

Instead of 1: the multiplexing timeline is checked without regard to PUSCH cancelled/skipped by step 1.

Replacement of 2: the multiplexing timeline is checked considering PUSCH cancelled/skipped by step 1.

Step 3: and executing CG PUSCH or UL skip of DGPUSCH.

In case there is no forwarded TB and UCI is not multiplexed with PUSCH (in case DG PUSCH, UL skip is valid), it may be skipped. When not operating in this way, PUSCH cannot be skipped.

(option 1-1: case 1 (FIGS. 4, 5))

The operation sequence for each assumed case will be described below. In this option, the processing of steps 1 to 3 (the same applies hereinafter) may be performed.

Step 1: DG/CG conflict handling

In the case where Δ1 does not satisfy the overwrite timeline of DG, an error may occur.

In case delta1 satisfies the overwrite timeline of DG,

option 1: it is checked whether Δ2 satisfies the overwrite timeline of DG.

CG PUSCH may be cancelled/skipped if the overwriting timeline is met. In other cases, errors may occur.

Option 2: CG PUSCH is cancelled/skipped.

Step 2: UCI multiplexing excluding CG PUSCH

A timeline of either replacement 1 or replacement 2 may be satisfied. Further, since CG PUSCH is canceled, UCI multiplexing may not be performed.

Step 3: UL skip ping

In the case where there is no TB transmitted for DG PUSCH (in the case where UL skip is valid), DG PUSCH may be skipped. As a result, only PUCCH is transmitted.

In the case where there is a TB transmitted to DG PUSCH, DG PUSCH may be transmitted. As a result, PUCCH and DG PUSCH can be transmitted.

Fig. 5 shows the same options as option 1-1 described above: the operation flow of the UE in case 1.

(option 1-1: case 2 (FIG. 6))

Step 1: DG/CG conflict handling

In the case where Δ1 satisfies the overwrite timeline of DG, there is no distinction between option 1 and option 2 in this case. Furthermore, CG PUSCH may also be cancelled/skipped.

Step 2: UCI multiplexing excluding CG PUSCH

Instead of 1: due to the repeated PUCCH, DG PUSCH and CG PUSCH, UCI multiplexing time lines may be considered.

Replacement of 2: due to the repeated PUCCH, DG PUSCH, UCI multiplexing timeline may be considered.

In case the timeline is satisfied, UCI may be multiplexed on DG PUSCH. In other cases, errors may occur.

Step 3: UL skip ping

UCI is multiplexed to DG PUSCH and thus DG PUSCH can be transmitted. As a result, DG PUSCH to which UCI is multiplexed can be transmitted.

(option 1-1: cases 3, 4 (FIGS. 7, 8))

(case 3)

Step 1: DG/CG conflict handling

Step 2: UCI multiplexing excluding CG PUSCH

In this case, there is no difference between the substitution 1 and the substitution 2. Further, UCI may be multiplexed on DG PUSCH in case the UCI multiplexing timeline is satisfied. In other cases, errors may occur.

Step 3: UL skip ping

(case 4)

Step 1: DG/CG conflict handling

The overwrite timeline can always be satisfied. Furthermore, CG PUSCH may also be cancelled/skipped.

Step 2: UCI multiplexing excluding CG PUSCH

Step 3: UL skip ping

(option 1-1: case 5 (FIG. 9))

Step 1: DG/CG conflict handling

In case delta1 satisfies the overwrite timeline of DG,

option 1: a check can be made as to whether Δ2 satisfies the overwrite timeline for DG. In the case where Δ2 satisfies the overwrite timeline of DG, CG PUSCH may be cancelled/skipped. In other cases, errors may occur.

Option 2: CG PUSCH may be cancelled/skipped.

Step 2: UCI multiplexing excluding CG PUSCH

For PUCCH#1

Instead of 1: in the case where PUCCH #1 and CG PUSCH are repeated, UCI multiplexing time lines may be considered, and PUCCH #1 may be transmitted. In other cases, errors may occur.

Replacement of 2: CG PUSCH may not be considered in the timeline. PUCCH #1 may be transmitted at any time.

For PUCCH#2

In the case of PUCCH #2, UCI of PUCCH #2 may be multiplexed to DG PUSCH when a DG PUSCH and UCI multiplexing timeline of PUCCH #2 are satisfied. In other cases, errors may occur.

Step 3: UL skip ping

UCI is multiplexed to DG PUSCH and thus DG PUSCH can be transmitted. As a result, DG PUSCH obtained by multiplexing UCI of PUCCH #1 and PUCCH #2 can be transmitted.

(options 1-2)

Step 1: UCI multiplexing (in case of PUCCH repetition with PUSCH). The multiplexed time line may also be checked.

Step 2: DG/CG conflict handling (in case DG overlaps CG PUSCH), the timeline of DG overwriting CG may be checked.

In case that PUSCH is cancelled/skipped, UCI multiplexed to PUSCH may be discarded together.

Step 3: CG after DG/CG conflict processing or UL skip for DG PUSCH.

In case there is no forwarded TB and UCI is not multiplexed through PUSCH (in case DG PUSCH, UL skip is valid), it may be skipped. When not operating in this way, PUSCH cannot be skipped.

(option 1-2: case 1 (FIG. 10))

Step 1: UCI multiplexing

In case of satisfying the multiplexing timeline, UCI may be multiplexed to CG PUSCH. In other cases, errors may occur.

Step 2: DG/CG conflict handling

In the case where Δ1 satisfies the overwrite timeline of DG, CG PUSCH may be cancelled/skipped. UCI multiplexed to CG PUSCH may also be discarded.

Step 3: UL skip ping

In the case where there is no TB transmitted for DG PUSCH (in the case where UL skip is valid), DG PUSCH may be skipped. As a result, UL transmission is not required.

In the case where there is a TB transmitted to DG PUSCH, DG PUSCH may be transmitted. As a result, DG PUSCH can be transmitted.

(option 1-2: cases 2, 3 (FIGS. 11, 12))

(case 2)

Step 1: UCI multiplexing

The UCI may be multiplexed to the DG PUSCH in case of satisfying multiplexing scheduling considering repeated PUCCH, DG PUSCH, CG PUSCH. In other cases, errors may occur.

Step 2: DG/CG conflict handling

In the case where Δ1 satisfies the overwrite timeline of DG, CG PUSCH may be cancelled/skipped.

Step 3: UL skip ping

(case 3)

Step 1: UCI multiplexing

The UCI may be multiplexed to the DG PUSCH in case of satisfying multiplexing scheduling considering repeated PUCCH and DG PUSCH. In other cases, errors may occur.

Step 2: DG/CG conflict handling

Step 3: UL skip ping

(option 1-1: cases 4 and 5 (FIGS. 13 and 14))

(case 4)

Step 1: UCI multiplexing

Step 2: DG/CG conflict handling

The overwrite timeline can always be satisfied. CG PUSCH may also be cancelled/skipped.

Step 3: UL skip ping

(case 5)

Step 1: UCI multiplexing

In the case of PUCCH #1, UCI of PUCCH #1 may be multiplexed to CG PUSCH if the UCI multiplexing time lines of CG PUSCH and PUCCH #1 are satisfied, otherwise, may be set as an error.

In the case of PUCCH #2, UCI of PUCCH #2 may be multiplexed to DG PUSCH when DG PUSCH and UCI multiplexing timeline of PUCCH #2 are satisfied. In the opposite case, errors may occur.

Step 2: DG/CG conflict handling

In the case where Δ1 satisfies the overwrite timeline of DG, CG PUSCH may be cancelled/skipped. UCI of PUCCH #1 multiplexed to CG PUSCH may also be discarded.

Step 3: UL skip ping

UCI is multiplexed to DG PUSCH and thus DG PUSCH can be transmitted. As a result, DG PUSCH in which UCI of PUCCH #2 is multiplexed can be transmitted.

(options 1-3)

Step 1: UCI multiplexing (in case of PUCCH repetition with PUSCH). The multiplexed timeline may be verified.

Step 2: UL skiping of CG or DG PUSCH

In case there is no forwarded TB and UCI is not multiplexed in PUSCH (in case DG PUSCH, UL skip is valid), it may be skipped. When not operating in this way, PUSCH cannot be skipped.

Option 1: as a result of step 2, both CG and DG PUSCH in which collision occurs cannot be skipped.

Option 2: an error condition is not defined. When both CG and DG PUSCH in which collision occurs cannot be skipped, it is possible to determine which PDU to generate or which PUSCH to transmit in step 3.

Step 3: DG/CG conflict handling (in case DG overlaps CG PUSCH), the timeline of DG overwriting CG may be checked.

In case of canceling/skipping PUSCH, UCI multiplexed to PUSCH may be discarded together.

Instead of 1: DG/CG conflict handling considering UL skip result of step 2

If the time line of the DG for overwriting the CG PUSCH is satisfied and the DG PUSCH is skipped in step 2, a MAC PDU for the CG PUSCH may be generated and delivered to the PHY.

If the DG timeline exceeding the CG PUSCH is satisfied and the DG PUSCH cannot be skipped in step 2, the MAC PDU for the CG PUSCH may not be generated even if the CG PUSCH cannot be skipped as a result of step 2.

Replacement of 2: DG/CG conflict handling without considering UL skip result of step 2

For example, when a timeline of DG exceeding CG PUSCH is satisfied, MAC PDU for CG PUSCH may not be generated, regardless of whether DG PUSCH is skipped in step 2.

(options 1-3: case 1 (FIGS. 15, 16))

Step 1: UCI multiplexing

Step 2: UL skip ping

In the case where there is no TB transmitted for DG PUSCH (in the case where UL skip is valid), DG PUSCH may be skipped. UCI is multiplexed to CG PUSCH, and therefore CG PUSCH may not be skipped.

Step 3: DG/CG conflict handling

In the case where Δ1 does not satisfy DG of the overwriting time axis, an error may occur.

In case delta1 satisfies the overwrite timeline of DG,

instead of 1: in the case where DG PUSCH is not skipped in step 2, CG PUSCH may be cancelled/skipped. UCI multiplexed to CG PUSCH may also be discarded. As a result, only DG PUSCH can be transmitted. Further, in the case where DG PUSCH is skipped in step 2, CG PUSCH may be transmitted. As a result, the UCI-multiplexed CG PUSCH can be transmitted.

Replacement of 2: CG PUSC may be cancelled/skipped regardless of whether DG PUSCH is skipped in step 2. UCI multiplexed to CG PUSCH may also be discarded. As a result, when TB is not transmitted to DG PUSCH, UL transmission may not be performed. Otherwise, DG PUSCH may be transmitted.

Fig. 16 shows the following options 1-3: the operation flow chart of the UE in case 1.

(options 1-3: cases 2, 3 (FIGS. 17, 18))

(case 2)

Step 1: UCI multiplexing

Step 2: UL skip ping

UCI is multiplexed to DG PUSCH and thus DG PUSCH can be transmitted.

Step 3: DG/CG conflict handling

In the case where Δ1 satisfies DG overwrite timeline, CG PUSCH may be cancelled/skipped. As a result, DG PUSCH to which UCI is multiplexed can be transmitted.

(case 3)

Step 1: UCI multiplexing

Step 2: UL skip ping

UCI is multiplexed to DG PUSCH and thus DG PUSCH can be transmitted.

Step 3: DG/CG conflict handling

(options 1-3: cases 4, 5 (FIGS. 19, 20))

(case 4)

Step 1: UCI multiplexing

Step 2: UL skip ping

UCI is multiplexed to DG PUSCH and thus DG PUSCH can be transmitted.

Step 3: DG/CG conflict handling

The overwrite timeline can always be satisfied. CG PUSCH may also be cancelled/skipped. As a result, DG PUSCH to which UCI is multiplexed can be transmitted.

(case 5)

Step 1: UCI multiplexing.

In the case of PUCCH #1, if UCI multiplexing time lines of CG PUSCH and PUCCH #1 are satisfied, UCI of PUCCH #1 may be multiplexed to CG PUSCH, and in the opposite case, an error may occur.

Step 2: UL skip ping

UCI is multiplexed to DG PUSCH and thus DG PUSCH can be transmitted.

Step 3: DG/CG conflict handling

In the case where Δ1 satisfies DG overwrite timeline, CG PUSCH may be cancelled/skipped. UCI of PUCCH #1 multiplexed to CG PUSCH may also be discarded. As a result, DG PUSCH in which UCI of PUCCH #2 is multiplexed can be transmitted.

In addition, "DG/CG collision" may mean that DG PUSCH overlaps CG PUSCH in the time domain on the same Component Carrier (CC).

In the case where the time line is not satisfied in any of the above-mentioned steps of the options, it may be handled as an error case.

(3.3) working example 2

In the case of (PUCCH, CG PUSCH, and DG PUSCH with different priorities), UL transmission behavior and time line check can be determined in consideration of DG/CG collision processing, UL scheduling, UCI multiplexing with the same priority, and Intra-UE priority assignment (Intra-UE prioritization). The order of DG/CG collision processing for PUCCH/PUSCH having different priorities, UL scheduling, UCI multiplexing within the same priority, and order of priority assignment within UE may be as follows.

(option 2-1)

Step 1: DG/CG conflict handling (in case of DG overlapping CG PUSCH) for deciding DG PUSCH or CG PUSCH is transmittable, other handling may be cancelled or skipped. The timeline for DG/CG conflict handling may be checked.

In the case where there is another PUCCH of the same priority multiplexed with the cancelled (skipped) PUSCH (assuming the case of not cancelled/skipped PUSCH), the operation may be performed as follows.

Option 1: the starting symbol of the PUCCH may also be considered in the timeline verification for collision handling (similar to option 1 of options 1-1)

Option 2: for the corresponding case, there are no additional considerations in the original DG/CG conflict handling timeline.

Step 2: after excluding the PUSCH cancelled/skipped in step 1, UCI may be multiplexed with the same priority order in the case where PUCCH overlaps PUSCH. The multiplexed timeline may be verified.

Replacement of 2: the UCI multiplexing timeline is checked considering PUSCH cancelled/skipped through step 1.

Step 3: UL skip of CG or DG PUSCH is performed.

Step 4: in-UE prioritization in the case where overlap occurs between output PUCCHs and PUSCHs having different priorities.

LP (low priority) channels overlapping HP (high priority) channels may be discarded. In addition, as a variation, the order of step 3 and step 4 may be exchanged.

(option 2-1: cases 1, 2, 3 (FIG. 21, FIG. 22, FIG. 23))

The operation sequence for each assumed case will be described below. In this option, the processing of steps 1 to 4 may be performed.

(case 1 and 2)

Step 1: DG/CG conflict handling

The actions of the HP CG PUSCH and the LP DGPUSCH have not been determined. Here, assuming that CG PUSCH is transmitted, LP PUSCH is cancelled/skipped if a necessary time line is satisfied.

Step 2: UCI multiplexing

Since LP DG PUSCH is cancelled/skipped in step 1, UCI multiplexing may not be performed.

Step 3: UL skip ping

In the case where there is no TB transmitted to the HP CG PUSCH, the HP CG PUSCH may be skipped. As a result, the LP PUCCH can be transmitted. Otherwise, the HP CG PUSCH may be transmitted. As a result, the LP PUCCH and the HP CG PUSCH can be transmitted.

Step 4: in-UE prioritization (not required)

(case 3)

Step 1: DG/CG conflict handling

Step 2: UCI multiplexing

Since the LP DG PUSCH is cancelled/skipped in step 1, the LP PUCCH may not be multiplexed. The HP UCI may be multiplexed to the HP CG PUSCH.

Step 3: UL skip ping

Since the HP UCI is multiplexed to the HP CG PUSCH, the HP CG PUSCH cannot be skipped.

Step 4: in-UE prioritization (not required)

As a result, the LP PUCCH and the HP CG PUSCH to which the HP UCI is multiplexed can be transmitted.

(option 2-1: cases 4, 5, 6 (FIG. 24, FIG. 25, FIG. 26))

(case 4, 5)

Step 1: DG/CG conflict handling

The actions of HP DG PUSCH and LP CG PUSCH have not been determined. Here, assuming that the HP DG PUSCH is transmitted, the LP CG PUSCH is cancelled/skipped if the necessary time line is satisfied.

Step 2: UCI multiplexing

Since the LP CG PUSCH is cancelled/skipped in step 1, UCI multiplexing may not be performed.

Step 3: UL skip ping

In the case where there is no TB transmitted for the HP DG PUSCH (in the case where UL skip is valid), the HP DG PUSCH may be skipped. As a result, the LP PUCCH can be transmitted. Otherwise, the HP DG PUSCH may be transmitted. As a result, the LP PUCCH and the HP DG PUSCH can be transmitted.

Step 4: in-UE prioritization (not required)

(case 6)

Step 1: DG/CG conflict handling

Step 2: UCI multiplexing

Since the LP CG PUSCH is cancelled/skipped in step 1, the LP PUCCH may not be multiplexed. The HP UCI may be multiplexed to the HP DG PUSCH.

Step 3: UL skip ping

HP UCI is multiplexed to HP DG PUSCH, and thus, HP DG PUSCH cannot be skipped.

Step 4: in-UE prioritization (not required)

As a result, the LP PUCCH and the HP DG PUSCH to which the HP UCI is multiplexed can be transmitted.

(option 2-2)

Step 1: in case that the PUCCH overlaps with the PUSCH, UCI may be multiplexed in the same priority. The multiplexed timeline may be checked.

Step 2: DG/CG conflict handling (in case of CG PUSCHDG PUSCH overlapping) the time line of DG/CG conflict handling can be checked.

Step 3: CG PUSCH after DG/CG Conflict processing or UL skip for DG PUSCH

In case there is no forwarded TB and UCI is not multiplexed to PUSCH (in case DG PUSCH, UL skip is valid), it may be skipped. When not operating in this way, PUSCH cannot be skipped.

LP channels overlapping the HP channels may be discarded. In addition, as a variation, the order of step 3 and step 4 may be exchanged.

(option 2-2: cases 1, 2, 3 (FIG. 27, FIG. 28, FIG. 29))

(case 1 and 2)

Step 1: UCI multiplexing

The LP UCI may be multiplexed to the LP DG PUSCH.

Step 2: DG/CG conflict handling

The actions of the HP CG PUSCH and the LP DGPUSCH have not been determined. Here, assuming that CG PUSCH is transmitted, LP PUSCH is cancelled/skipped if a necessary time line is satisfied. The LP UCI multiplexed in the LP DG PUSCH may also be discarded.

Step 3: UL skip ping

In the case where there is no TB transmitted to the HP CG PUSCH, the HP CG PUSCH may be skipped. As a result, UL transmission is not required. Otherwise, the HP CG PUSCH may be transmitted. As a result, the HP CG PUSCH can be transmitted.

Step 4: in-UE prioritization (not required)

(case 3)

Step 1: UCI multiplexing

The LP UCI may be multiplexed to the LP DG PUSCH and the HP UCI may be multiplexed to the HP CG PUSCH.

Step 2: DG/CG conflict handling

Step 3: UL skip ping

Step 4: in-UE prioritization (not required)

As a result, the HP CG PUSCH in which UCI is HP-multiplexed can be transmitted.

(option 2-2: cases 4, 5, 6 (FIG. 30, FIG. 31, FIG. 32))

(case 4, 5)

Step 1: UCI multiplexing

The LP UCI may be multiplexed to the LP CG PUSCH.

Step 2: DG/CG conflict handling

The actions of DG PUSCH and LP CG PUSCH have not been determined. Here, assuming that the HP DG PUSCH is transmitted, the LP CG PUSCH is cancelled/skipped if the necessary time line is satisfied. The LP UCI multiplexed to the LP CG PUSCH may also be discarded.

Step 3: UL skip ping

In the case where there is no TB transmitted for the HP DG PUSCH (in the case where UL skip is valid), the HP DG PUSCH may be skipped. As a result, UL transmission is not required. Otherwise, the HP DG PUSCH may be transmitted. As a result, the HP DG PUSCH can be transmitted.

Step 4: in-UE prioritization (not required)

(case 6)

Step 1: UCI multiplexing

The LP UCI may be multiplexed to the LP CG PUSCH and the HP UCI may be multiplexed to the HP DG PUSCH.

Step 2: DG/CG conflict handling

The actions of HP DG PUSCH and LP CG PUSCH have not been determined. Here, assuming that the HP DG PUSCH is transmitted, the LP CG PUSCH is cancelled/skipped if the necessary time line is satisfied. The LP UCI multiplexed to the LP CG PUSCH may also be discarded.

Step 3: UL skip ping

HP UCI is multiplexed to HP DG PUSCH, and thus, HP DG PUSCH cannot be skipped.

Step 4: in-UE prioritization (not required)

As a result, the HP DG PUSCH to which the HP UCI is multiplexed can be transmitted.

(options 2-3)

Step 1: in case that the PUCCH overlaps with the PUSCH, UCI may be multiplexed in the same priority. The timeline for DG/CG conflict handling may be checked.

Step 2: CG after DG/CG conflict treatment or UL skip of DG PUSCH

In case there is no forwarded TB and UCI is not multiplexed on PUSCH (in case DG PUSCH, UL skip is valid), it may be skipped. When not operating in this way, PUSCH cannot be skipped.

Step 3: DG/CG conflict handling (in case DG overlaps CG PUSCH). The DG/CG overlapping time lines may be checked.

Instead of 1: DG/CG conflict handling considering UL skip result of step 2

For example, when the timeline is satisfied and one PUSCH is skipped in step 2, a MAC PDU for the other PUSCH may be generated, and if a TB for the other PUSCH exists, the MAC PDU may be transmitted to the PHY.

Step 4: in-UE prioritization in the case of overlap between output PUCCH and PUSCH with different priorities. LP channels overlapping the HP channels may be discarded.

(option 2-3: cases 1, 2 (FIG. 33, FIG. 34))

(case 1 and 2)

Step 1: UCI multiplexing

The LP UCI may be multiplexed to the LP DG PUSCH.

Step 2: UL skip ping

Since the LP UCI is multiplexed, the LP DG PUSCH cannot be skipped. In the case where there is no TB transmitted to the HP CG PUSCH, the HP CG PUSCH may be skipped. When the operation is not performed in this way, the HP CG PUSCH cannot be skipped.

Option 1: the error condition is set such that both the repeated 2 CG PUSCH/DG PUSCH cannot be skipped.

Option 2: the problem is solved by using step 3 instead of the error case.

Step 3: DG/CG conflict handling

The actions of the HP CG PUSCH and the LP DGPUSCH have not been determined. Here, assuming that the HP CG PUSCH is transmitted, the LP DG PUSCH is cancelled/skipped if the necessary time line is satisfied.

Instead of 1: DG/CG conflict handling considering UL skip result of step 2

When the HP CG PUSCH is skipped, the LP DG PUSCH can be transmitted. As a result, the LP DG PUSCH to which the LP UCI is multiplexed can be transmitted. Otherwise, the LP DG PUSCH may be cancelled/skipped. The LP UCI multiplexed in the LP DG PUSCH may also be discarded. As a result, the HP CG PUSCH can be transmitted.

Replacement of 2: LP DG PUSCH may be cancelled or skipped, regardless of whether HP CG PUSCH is skipped. In the case where the HP CG PUSCH is skipped, UL transmission may not be performed. Otherwise, the HP CG PUSCH may be transmitted.

Step 4: in-UE prioritization (not required)

(option 2-3: case 3 (FIG. 35))

Step 1: UCI multiplexing

Step 2: UL skip ping

UCI is multiplexed for HP and LP PUSCH, and therefore, HP CG and LP DG PUSCH cannot be skipped.

Option 1: an error condition is set in which both repeated 2 CG/DGs cannot be skipped.

Option 2: the problem is solved by using step 3 instead of the error case.

Step 3: DG/CG conflict handling

In both substitution 1 and substitution 2, the LP DG PUSCH may be cancelled/skipped. The LP UCI multiplexed in the LP DG PUSCH may also be discarded. As a result, the HP CG PUSCH in which UCI is HP-multiplexed can be transmitted.

Step 4: in-UE prioritization (not required)

(option 2-3: cases 4, 5 (FIG. 36, FIG. 37))

Step 1: UCI multiplexing

The LP UCI may be multiplexed to the LP CG PUSCH.

Step 2: UL skip ping

Since the LP UCI is multiplexed, the LP CG PUSCH cannot be skipped. In the absence of a TB sent to the HP DG PUSCH, the HP DG PUSCH may be skipped. When the operation is not performed in this way, the HP DG PUSCH cannot be skipped.

Option 2: the problem is solved by using step 3 instead of the error case.

Step 3: DG/CG conflict handling

Instead of 1: DG/CG conflict handling considering UL skip result of step 2

When the HP DG PUSCH is skipped, the LP CG PUSCH can be transmitted. As a result, the LP CG PUSCH in which the LP UCI is multiplexed can be transmitted. In other cases, the LP CG PUSCH may be cancelled/skipped. The LP UCI multiplexed to the LP CG PUSCH may also be discarded. As a result, the HP DG PUSCH can be transmitted.

Replacement of 2: LP CG PUSCH may be cancelled/skipped regardless of whether HP DG PUSCH is skipped. When the HP DG PUSCH is skipped, UL transmission may not be performed. Otherwise, the HP DG PUSCH may be transmitted.

Step 4: in-UE prioritization (not required)

(option 2-3: case 6 (FIG. 38))

Step 1: UCI multiplexing

Step 2: UL skip ping

UCI is multiplexed for HP and LP PUSCH, and therefore, HP DG and LP CG PUSCH cannot be skipped.

Option 2: the problem is solved by using step 3 instead of the error case.

Step 3: DG/CG conflict handling

In both substitution 1 and substitution 2, the LP CG PUSCH may be cancelled/skipped. The LP UCI multiplexed to the LP CG PUSCH may also be discarded. As a result, the HP DG PUSCH to which the HP UCI is multiplexed can be transmitted.

Step 4: in-UE prioritization (not required)

(options 2-4)

Step 1: when the PUCCH overlaps with the PUSCH, UCI is multiplexed with the same priority. The multiplexed timeline may be checked.

Step 2: CG after DG/CG conflict treatment or UL skip of DG PUSCH

Option 2: an error condition is not defined. If both CG and DG PUSCH in which collision occurs cannot be skipped, the generated PDU or PUSCH that can be transmitted may be determined in accordance with step 3 and/or step 4.

Step 3: in-UE prioritization in the case where overlap occurs between output PUCCHs and PUSCHs having different priorities.

LP channels overlapping the HP channels may be discarded.

Step 4: DG/CG conflict handling (in case DG overlaps CG PUSCH). The timeline for DG/CG conflict handling may be checked.

Instead of 1: the result of steps 2 and 3 is DG/CG conflict handling taking into account UL skip ping and in-UE prioritization

For example, when the timeline is satisfied and one PUSCH is skipped or canceled in steps 2 and 3, a MAC PDU for the other PUSCH may be generated, and if a TB for the other PUSCH exists, the MAC PDU may be transmitted to the PHY.

Replacement of 2: the result of steps 2 and 3 is DG/CG conflict handling without regard to UL skip ping and prioritization in UE

(options 2-4: cases 7, 8 (FIGS. 39, 40))

Step 1: UCI multiplexing

In this case, UCI multiplexing may not be performed.

Step 2: UL skip ping

If both of the 2 CG/DG overlapping cannot be skipped, the operation may be performed in accordance with any of the following.

Option 1: an error condition is set.

Option 2: step 4 is used to solve the problem instead of the error case.

Step 3: in-UE prioritization

Since LP DG PUSCH and HP PUCCH are repeated, they may be cancelled.

Step 4: DG/CG conflict handling

In step 3, LP DG PUSCH is cancelled. In case that the HP CG PUSCH is skipped in step 2, the HP PUCCH may be transmitted. In the case where the HP CG PUSCH is not skipped in step 2, the HP CG PUSCH and the HP PUCCH may be transmitted.

(options 2-4: case 9 (FIG. 41))

Step 1: UCI multiplexing

In this case, UCI multiplexing may not be performed.

Step 2: UL skip ping

Option 1: an error condition is set.

Option 2: step 4 is used to solve the problem instead of the error case.

Step 3: in-UE prioritization

LP CG PUSCH is repeated with HP PUCCH and, therefore, can be cancelled. Since the LP PUCCH is repeated with the HP DG PUSCH, it can be cancelled.

Step 4: DG/CG conflict handling

In step 3, the LP CG PUSCH is cancelled. In case that the HP DG PUSCH is skipped in step 2, the HP PUCCH may be transmitted. In the case where the HP DG PUSCH is not skipped in step 2, the HP CG PUSCH and the HP PUCCH may be transmitted.

(options 2-5)

Step 2: in-UE prioritization in the case where overlap occurs between output PUCCHs and PUSCHs having different priorities. LP channels overlapping the HP channels may be discarded.

Step 3: UL skip ping for CG or DG PUSCH after DG/CG conflict processing

Option 1: as a result of step 3, both CG and DG PUSCH in which collision occurs cannot be skipped.

Option 2: an error condition is not defined. If both CG and DG PUSCH where collision occurs cannot be skipped, it is possible to determine which PDU to generate or which PUSCH to transmit in accordance with step 4.

Step 4: DG/CG conflict handling (in case DG overlaps CG PUSCH)

The timeline for DG/CG conflict handling may be checked.

In case of canceling/skipping PUSCH, UCI multiplexed to PUSCH may be discarded together. The 2 alternatives (alternative 1 and alternative 2 as options 2-3) may take into account UL skiping, may not take into account UL skiping, or may be the result from step 3.

(options 2-5: cases 7, 8 (FIG. 42, FIG. 43))

Step 1: UCI multiplexing

In this case, UCI multiplexing may not be performed.

Step 2: in-UE prioritization

Since LP DG PUSCH and HP PUCCH are repeated, they may be cancelled.

Step 3: UL skip ping

In the case where there is no TB transmitted to the HP CG PUSCH, the HP CG PUSCH may be skipped.

Step 4: DG/CG conflict handling

In step 2, LP DG PUSCH is cancelled. In case that the HP CG PUSCH is skipped in step 3, the HP PUCCH may be transmitted. In the case where the HP CG PUSCH is not skipped in step 3, the HP CG PUSCH and the HP PUCCH may be transmitted.

(options 2-5: case 9 (FIG. 44))

Step 1: UCI multiplexing

In this case, UCI multiplexing may not be performed.

Step 2: in-UE prioritization

Step 3: UL skip ping

In the absence of a TB sent to the HP DG PUSCH, the HP DG PUSCH may be skipped.

Step 4: DG/CG conflict handling

In step 2, the LP CG PUSCH is cancelled. In case that the HP DG PUSCH is skipped in step 3, the HP PUCCH may be transmitted. In the case where the HP DG PUSCH is not skipped in step 3, the HP DG PUSCH and the HP PUCCH may be transmitted.

(options 2-6)

Step 3: DG/CG conflict handling (in case DG overlaps CG PUSCH). The timeline for DG/CG conflict handling may be checked. In case of canceling/skipping PUSCH, UCI multiplexed to PUSCH may be discarded together.

Step 4: CG after DG/CG conflict treatment or UL skip of DG PUSCH

(options 2-6: cases 7, 8, 9 (FIG. 45, FIG. 46, FIG. 47))

(case 7, 8)

Step 1: UCI multiplexing

In this case, UCI multiplexing may not be performed.

Step 2: in-UE prioritization

Since LP DG PUSCH and HP PUCCH are repeated, they may be cancelled.

Step 3: DG/CG conflict handling

In step 2, LP DG PUSCH is cancelled.

Step 4: UL skip ping

In the case where there is no TB transmitted to the HP CG PUSCH, the HP CG PUSCH may be skipped. As a result, the HP PUCCH can be transmitted. If there is a TB transmitted as the HP CG PUSCH, the HP CG PUSCH may be transmitted. As a result, HP CG PUSCH and HP PUCCH can be transmitted.

(case 9)

Step 1: UCI multiplexing

In this case, UCI multiplexing may not be performed.

Step 2: in-UE prioritization

Step 3: DG/CG conflict handling

In step 2, the LP CG PUSCH is cancelled.

Step 4: UL skip ping

In the absence of a TB sent to the HP DG PUSCH, the HP DG PUSCH may be skipped. As a result, the HP PUCCH can be transmitted. In the case where there is a TB transmitted to the HP DG PUSCH, the HP DG PUSCH may be transmitted. HP DG PUSCH and HP PUCCH may also be transmitted.

In addition, according to release 16 of 3GPP, consider the option of "execute Intra-UE multiplexing with priority first, followed by Intra-UE prioritization". This option can also be interpreted as considering only UCI multiplexing within the same priority before intra-UE priority assignment for PUCCHs/PUSCHs with different priorities in the above-described operation example.

The cancellation/skipping of PUSCH may be performed by the MAC layer or the PHY layer. Further, in the case where the time line is not satisfied in any of the above-mentioned steps of options, it is possible to handle as an error case.

The options described above may be set by parameters of a higher layer (e.g., RRC). For example, the capability information (UE capability) of the UE may be reported, or may be defined as a specification of 3 GPP. Furthermore, the specific options may be decided using a combination of the settings of the parameters of the higher layers and the reported capabilities of the UE.

(UE capability)

The UE may report whether UL skip of DG PUSCH is supported.

The UE may report whether to support the overlapping processing of CG/DG/UCI with the same priority.

Furthermore, the UE may report whether overlapping processing of CG/DG/UCI with different priorities is supported.

(4) action/Effect

According to the above embodiment, the following operational effects can be obtained. Specifically, as described above, when PUCCH (uplink control channel), CG PUSCH (1 st uplink data channel), and DG PUSCH (2 nd uplink data channel) have the same priority, UE 200 can control transmission in UL according to repetition of CG PUSCH and DG PUSCH in the time direction, transmission omission of UL (UL scheduling), and multiplexing of UCI (uplink control information) to CG PUSCH or DG PUSCH.

In addition, in the case where PUCCH (uplink control channel), CG PUSCH (1 st uplink data channel), and DG PUSCH (2 nd uplink data channel) have different priorities, UE 200 can control transmission in UL according to repetition of CG PUSCH and DG PUSCH in the time direction, multiplexing of UL (UL scheduling), UCI (uplink control information) to CG PUSCH or DG PUSCH, and Intra-terminal priority/multiplexing.

Therefore, even in the case of processing a plurality of UL transmissions having the same or different priorities, the plurality of UL transmissions can be efficiently and appropriately processed.

(5) Other embodiments

While the embodiment has been described above, it is obvious that the present invention is not limited to the description of the embodiment, and various modifications and improvements can be made by those skilled in the art.

For example, in the above-described embodiment, the wireless communication system according to 5G (NR) is assumed, but the wireless communication system 10 may be a wireless communication system according to a scheme called Beyond 5G, 5G evaluation, or 6G.

The block diagram (fig. 3) used in the description of the above embodiment shows blocks in units of functions. These functional blocks (structures) are realized by any combination of at least one of hardware and software. The implementation method of each functional block is not particularly limited. That is, each functional block may be realized by using one device physically or logically combined, or may be realized by directly or indirectly (for example, by using a wire, a wireless, or the like) connecting two or more devices physically or logically separated from each other, and using these plural devices. The functional blocks may also be implemented by combining software with the above-described device or devices.

Functionally, there are judgment, decision, judgment, calculation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, establishment, comparison, assumption, expectation, view, broadcast (broadcast), notification (notification), communication (communication), forwarding (forwarding), configuration, reconfiguration (allocation), allocation (allocating, mapping), assignment (allocation), and the like, but not limited thereto. For example, a functional block (configuration unit) that causes transmission to function is called a transmitter (transmitting unit) or a transmitter (transmitter). In short, the implementation method is not particularly limited as described above.

The above-described gNB 100 and UE 200 (the apparatus) may also function as a computer that performs the processing of the wireless communication method of the present disclosure. Fig. 48 is a diagram showing an example of a hardware configuration of the apparatus. As shown in fig. 48, the device may be configured as a computer device including a processor 1001, a memory 1002 (memory), a storage 1003 (storage), a communication device 1004, an input device 1005, an output device 1006, a bus 1007, and the like.

In addition, in the following description, the term "means" may be replaced with "circuit", "device", "unit", or the like. The hardware configuration of the apparatus may be configured to include one or more of the illustrated apparatuses, or may be configured to include no part of the apparatus.

Each functional block of the apparatus (see fig. 3) is realized by any hardware element or a combination of hardware elements in the computer apparatus.

In addition, each function in the device is realized by the following method: predetermined software (program) is read into hardware such as the processor 1001 and the memory 1002, and the processor 1001 performs an operation to control communication by the communication device 1004 or to control at least one of reading and writing of data in the memory 1002 and the memory 1003.

The processor 1001 controls the entire computer by, for example, operating an operating system. The processor 1001 may be configured by a Central Processing Unit (CPU) including an interface with peripheral devices, a control device, an arithmetic device, a register, and the like.

Further, the processor 1001 reads out a program (program code), a software module, data, or the like from at least one of the memory 1003 and the communication device 1004 to the memory 1002, and executes various processes accordingly. As the program, a program that causes a computer to execute at least a part of the operations described in the above embodiments is used. Further, although the above-described various processes are described as being executed by one processor 1001, the above-described various processes may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may also be mounted by more than one chip. In addition, the program may also be transmitted from the network via a telecommunication line.

The Memory 1002 is a computer-readable recording medium, and may be constituted by at least one of a Read Only Memory (ROM), an erasable programmable Read Only Memory (EPROM: erasable Programmable ROM), an electrically erasable programmable Read Only Memory (EEPROM: electrically Erasable Programmable ROM), a random access Memory (RAM: random Access Memory), and the like. The memory 1002 may also be referred to as a register, a cache, a main memory (main storage), or the like. The memory 1002 may store programs (program codes), software modules, and the like capable of performing the methods according to one embodiment of the present disclosure.

The memory 1003 is a computer-readable recording medium, and may be configured of at least one of an optical disk such as a Compact Disc ROM (CD-ROM), a hard disk drive, a Floppy disk, a magneto-optical disk (for example, a Compact Disc, a digital versatile Disc, a Blu-ray (registered trademark) Disc), a smart card, a flash memory (for example, a card, a stick, a Key drive), a pivotable (registered trademark) Disc, a magnetic stripe, and the like. Memory 1003 may also be referred to as secondary storage. The recording medium may be, for example, a database, a server, or other suitable medium including at least one of the memory 1002 and the storage 1003.

The communication device 1004 is hardware (transceiver device) for performing communication between computers via at least one of a wired network and a wireless network, and is also called a network device, a network controller, a network card, a communication module, or the like, for example.

The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, and the like, for example, in order to realize at least one of frequency division duplexing (Frequency Division Duplex: FDD) and time division duplexing (Time Division Duplex: TDD).

The input device 1005 is an input apparatus (for example, a keyboard, a mouse, a microphone, a switch, a key, a sensor, or the like) that receives an input from the outside. The output device 1006 is an output apparatus (for example, a display, a speaker, an LED lamp, or the like) that performs output to the outside. The input device 1005 and the output device 1006 may be integrally formed (for example, a touch panel).

The processor 1001 and the memory 1002 are connected by a bus 1007 for communicating information. The bus 1007 may be formed by a single bus or may be formed by different buses between devices.

The device may be configured to include hardware such as a microprocessor, a digital signal processor (Digital Signal Processor:dsp), an application specific integrated circuit (asic: application Specific Integrated Circuit), a programmable logic device (pld: programmable Logic Device), and a field programmable gate array (fpga: field Programmable Gate Array), or may be configured to implement a part or all of the functional blocks by the hardware. For example, the processor 1001 may also be implemented using at least one of these hardware.

Further, the notification of the information is not limited to the form/embodiment described in the present disclosure, and may be performed using other methods. For example, the notification of the information may be implemented by physical layer signaling (e.g., downlink control information (DCI: downlink Control Information), uplink control information (UCI: uplink Control Information), higher layer signaling (e.g., RRC signaling, medium access control (MAC: medium Access Control) signaling), broadcast information (master information block (MIB: master Information Block), system information block (SIB: system Information Block)), other signals, or a combination thereof.

The various forms/embodiments described in the present disclosure may also be applied to at least one of long term evolution (LTE: long Term Evolution), LTE-Advanced (LTE-a), upper 3G, IMT-Advanced, fourth generation mobile communication system (4G:4th generation mobile communication system), fifth generation mobile communication system (5G:5th generation mobile communication system), future Radio access (FRA: future Radio Access), new air interface (NR: new Radio), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, ultra mobile broadband (UMB: ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, ultra WideBand (UWB: ultra-wide-band), bluetooth (registered trademark), systems using other suitable systems, and next generation systems extended accordingly. Further, a plurality of systems (for example, a combination of 5G and at least one of LTE and LTE-a) may be applied in combination.

The processing procedure, sequence, flow, and the like of each form/embodiment described in the present disclosure can be replaced without contradiction. For example, for the methods described in this disclosure, elements of the various steps are presented using an illustrated order, but are not limited to the particular order presented.

In the present disclosure, a specific operation performed by a base station may be performed by an upper node (upper node) thereof, as the case may be. In a network composed of one or more network nodes (network nodes) having a base station, it is apparent that various operations performed for communication with a terminal may be performed by at least one of the base station and other network nodes (for example, MME or S-GW, etc. are considered, but not limited thereto) other than the base station. In the above, the case where one other network node other than the base station is illustrated, but the other network node may be a combination of a plurality of other network nodes (for example, MME and S-GW).

Information, signals (information, etc.) can be output from a higher layer (or a lower layer) to a lower layer (or a higher layer). Or may be input or output via a plurality of network nodes.

The input or output information may be stored in a specific location (e.g., a memory), or may be managed using a management table. The input or output information may be rewritten, updated, or written. The outputted information may also be deleted. The entered information may also be sent to other devices.

The determination may be performed by a value (0 or 1) represented by 1 bit, may be performed by a Boolean value (true or false), or may be performed by a comparison of values (e.g., a comparison with a predetermined value).

The various forms and embodiments described in this disclosure may be used alone, in combination, or switched depending on the implementation. Note that the notification of the predetermined information is not limited to being explicitly performed (for example, notification of "yes" or "X"), and may be performed implicitly (for example, notification of the predetermined information is not performed).

With respect to software, whether referred to as software, firmware, middleware, microcode, hardware description language, or by other names, should be broadly interpreted to refer to a command, a set of commands, code, a code segment, program code, a program (program), a subroutine, a software module, an application, a software package, a routine, a subroutine, an object, an executable, a thread of execution, a procedure, a function, or the like.

In addition, software, commands, information, etc. may be transmitted and received via a transmission medium. For example, in the case where software is transmitted from a website, server, or other remote source using at least one of a wired technology (coaxial cable, fiber optic cable, twisted pair, digital subscriber line (Digital Subscriber Line: DSL), etc.) and wireless technology (infrared, microwave, etc.), at least one of the wired and wireless technologies is included in the definition of transmission medium.

Information, signals, etc. described in this disclosure may also be represented using any of a variety of different technologies. For example, data, commands, instructions (commands), information, signals, bits, symbols, chips (chips), and the like may be referenced throughout the above description by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or photons, or any combination thereof.

In addition, the terms described in the present disclosure and the terms necessary for understanding the present disclosure may be replaced with terms having the same or similar meanings. For example, at least one of the channel and the symbol may be a signal (signaling). In addition, the signal may also be a message. The component carrier (Component Carrier: CC) may also be referred to as a carrier frequency, a cell, a frequency carrier, or the like.

The terms "system" and "network" as used in this disclosure are used interchangeably.

In addition, information, parameters, and the like described in this disclosure may be expressed using absolute values, relative values to predetermined values, or other information corresponding thereto. For example, radio resources may also be indicated by an index.

The names used for the above parameters are non-limiting in any respect. Further, the numerical formulas and the like using these parameters may also be different from those explicitly disclosed in the present disclosure. Since the various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by all appropriate names, the various names assigned to these various channels and information elements are non-limiting in any respect.

In the present disclosure, terms such as "Base Station (BS)", "radio Base Station", "fixed Station", "NodeB", "eNodeB (eNB)", "gndeb (gNB)", "access point", "transmission point (transmission point)", "reception point", "transmission point (transmission/reception point)", "cell", "sector", "cell group", "carrier", "component carrier", and the like may be used interchangeably. The terms macrocell, microcell, femtocell, picocell, and the like are also sometimes used to refer to a base station.

A base station can accommodate one or more (e.g., 3) cells (also referred to as sectors). In the case of a base station accommodating multiple cells, the coverage area of the base station can be divided into multiple smaller areas as a whole, each of which can also provide communication services through a base station subsystem (e.g., a small base station (Remote Radio Head (remote radio head): RRH) for indoor use).

The term "cell" or "sector" refers to a part or the whole of an coverage area of at least one of a base station and a base station subsystem that perform communication services within the coverage area.

In the present disclosure, terms such as "Mobile Station (MS)", "User terminal (UE)", "User Equipment (UE)", and "terminal" may be used interchangeably.

For mobile stations, those skilled in the art are sometimes referred to by the following terms: a subscriber station, mobile unit (mobile unit), subscriber unit, wireless unit, remote unit, mobile device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, or some other suitable terminology.

At least one of the base station and the mobile station may be referred to as a transmitting apparatus, a receiving apparatus, a communication apparatus, 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 mobile body may be a vehicle (e.g., an automobile, an airplane, etc.), a mobile body that moves unmanned (e.g., an unmanned aerial vehicle, an autopilot, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station also includes a device that does not necessarily move during a communication operation. For example, at least one of the base station and the mobile station may be an internet of things (IoT: internet of Things) device of a sensor or the like.

In addition, the base station in the present disclosure may be replaced with a mobile station (user terminal, the same applies hereinafter). For example, various forms/embodiments of the present disclosure may also be applied with respect to a structure in which communication between a base station and a mobile station is replaced with communication between a plurality of mobile stations (e.g., may also be referred to as Device-to-Device (D2D), vehicle-to-Everything (V2X), etc.). In this case, the mobile station may have a function of the base station. Further, the terms "upstream" and "downstream" may be replaced with terms (e.g., "side") corresponding to the inter-terminal communication. For example, the uplink channel, the downlink channel, and the like may be replaced with side channels.

Likewise, the mobile station in the present disclosure may be replaced with a base station. In this case, the base station may have a function of the mobile station.

A radio frame may be made up of one or more frames in the time domain. In the time domain, one or more of the frames may be referred to as subframes. A subframe may further be composed of one or more slots in the time domain. The subframes may also be a fixed length of time (e.g., 1 ms) independent of the parameter set (numerology).

The parameter set may be a communication parameter applied to at least one of transmission and reception of a certain signal or channel. The parameter set may represent, for example, at least one of a subcarrier spacing (SubCarrier Spacing: SCS), a bandwidth, a symbol length, a cyclic prefix length, a transmission time interval (Transmission Time Interval: TTI), a number of symbols per TTI, a radio frame structure, a specific filtering process performed by the transceiver in the frequency domain, a specific windowing process performed by the transceiver in the time domain, and the like.

A slot may be formed in the time domain from one or more symbols (orthogonal frequency division multiplexing (OFDM: orthogonal Frequency Division Multiplexing) symbols, SC-FDMA (Single Carrier Frequency Division Multiple Access: single carrier frequency division multiple access) symbols, etc.). A slot may be a unit of time based on a set of parameters.

A slot may contain multiple mini-slots. Each mini-slot may be made up of one or more symbols in the time domain. In addition, the mini-slot may also be referred to as a sub-slot. Mini-slots may be made up of a fewer number of symbols than slots. PDSCH (or PUSCH) transmitted in units of time greater than the mini-slot may be referred to as PDSCH (or PUSCH) mapping type (type) a. PDSCH (or PUSCH) transmitted using mini-slots may be referred to as PDSCH (or PUSCH) mapping type (type) B.

The radio frame, subframe, slot, mini-slot, and symbol each represent a unit of time when a signal is transmitted. The radio frame, subframe, slot, mini-slot, and symbol may each use corresponding other designations.

For example, 1 subframe may also be referred to as a Transmission Time Interval (TTI), a plurality of consecutive subframes may also be referred to as TTIs, and 1 slot or 1 mini-slot may also be referred to as TTIs. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in the conventional LTE, may be a period (e.g., 1-13 symbols) shorter than 1ms, or may be a period longer than 1 ms. In addition, a unit indicating a TTI may not be referred to as a subframe, but may be referred to as a slot, a mini-slot, or the like.

Here, TTI refers to, for example, a scheduled minimum time unit in wireless communication. For example, in the LTE system, a base station performs scheduling for allocating radio resources (bandwidth, transmission power, and the like that can be used for each user terminal) to each user terminal in TTI units. In addition, the definition of TTI is not limited thereto.

The TTI may be a transmission time unit of a data packet (transport block), a code block, a codeword, or the like after channel coding, or may be a processing unit such as scheduling or link adaptation. In addition, when a TTI is given, the time interval (e.g., number of symbols) in which a transport block, a code block, a codeword, etc. is actually mapped may be shorter than the TTI.

In addition, in the case where 1 slot or 1 mini slot is referred to as a TTI, more than one TTI (i.e., more than one slot or more than one mini slot) may constitute a minimum time unit of scheduling. In addition, the number of slots (the number of mini slots) constituting the minimum time unit of scheduling can be controlled.

A TTI having a time length of 1ms may also be referred to as a normal TTI (TTI in LTE rel.8-12), normal TTI (normal TTI), long TTI (long TTI), normal subframe (normal subframe), long (long) subframe, slot, etc. A TTI that is shorter than a normal TTI may be referred to as a shortened TTI, a short TTI (short TTI), a partial or fractional TTI, a shortened subframe, a short (short) subframe, a mini-slot, a sub-slot, a slot, etc.

In addition, for long TTIs (long TTIs) (e.g., normal TTIs, subframes, etc.), a TTI having a time length exceeding 1ms may be substituted, and for short TTI (short TTI) (e.g., shortened TTI, etc.), a TTI having a TTI length less than the long TTI (long TTI) and having a TTI length of 1ms or more may be substituted.

A Resource Block (RB) is a resource allocation unit of a time domain and a frequency domain, in which one or more consecutive subcarriers (subcarriers) may be included. The number of subcarriers contained in the RB may be the same regardless of the parameter set, for example, 12. The number of subcarriers included in the RB may also be determined according to the parameter set.

Further, the time domain of the RB may contain one or more symbols, which may be 1 slot, 1 mini slot, 1 subframe, or 1TTI in length. A 1TTI, a 1 subframe, etc. may each be composed of one or more resource blocks.

In addition, one or more RBs may be referred to as Physical Resource Blocks (PRBs), subcarrier groups (Sub-Carrier groups: SCGs), resource element groups (Resource Element Group: REGs), PRB pairs, RB peering.

Furthermore, a Resource block may also be composed of one or more Resource Elements (REs). For example, 1RE may be a radio resource region of 1 subcarrier and 1 symbol.

The Bandwidth Part (Bandwidth Part: BWP) (which may also be referred to as partial Bandwidth, etc.) may represent a subset of consecutive common RBs (common resource blocks: common resource blocks) for a certain parameter set in a certain carrier. Here, the common RB may be determined by an index of the RB with reference to a common reference point of the carrier. PRBs may be defined in a certain BWP and numbered within the BWP.

BWP may include BWP for UL (UL BWP) and BWP for DL (DL BWP). One or more BWP may be set for the UE within the 1 carrier.

At least one of the set BWP may be active, and a case where the UE transmits and receives a predetermined signal/channel outside the active BWP may not be envisaged. In addition, "cell", "carrier", etc. in the present disclosure may be replaced with "BWP".

The structure of the radio frame, subframe, slot, mini slot, symbol, etc. described above is merely an example. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of mini-slots included in a slot, the number of symbols and RBs included in a slot or mini-slot, the number of subcarriers included in an RB, and the structure of the number of symbols, symbol length, cyclic Prefix (CP) length, etc. within a TTI may be variously changed.

The terms "connected," "coupled," or any variation of these terms are intended to refer to any direct or indirect connection or coupling between two or more elements, including the case where one or more intervening elements may be present between two elements that are "connected" or "coupled" to each other. The combination or connection of the elements may be physical, logical, or a combination of these. For example, "connection" may also be replaced with "access". As used in this disclosure, two elements may be considered to be "connected" or "joined" to each other using at least one of one or more wires, cables, and printed electrical connections, and as some non-limiting and non-inclusive examples, electromagnetic energy or the like having wavelengths in the wireless frequency domain, the microwave region, and the optical (both visible and invisible) region.

The Reference Signal may be simply referred to as Reference Signal (RS) or Pilot (Pilot) depending on the applied standard.

As used in this disclosure, the recitation of "according to" is not intended to mean "according to" unless explicitly recited otherwise. In other words, the term "according to" means "according to only" and "according to at least" both.

The "unit" in the structure of each device may be replaced with "part", "circuit", "device", or the like.

Any reference to elements referred to using "1 st", "2 nd", etc. as used in this disclosure also does not entirely define the number or order of these elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, references to elements 1 and 2 do not indicate that only two elements can be taken or that in any form element 1 must precede element 2.

Where the terms "include", "comprising" and variations thereof are used in this disclosure, these terms are intended to be inclusive as well as the term "comprising". Also, the term "or" as used in this disclosure means not exclusive or.

In the present disclosure, for example, where an article is added by translation as in a, an, and the in english, the present disclosure may also include a case where a noun following the article is in plural.

The terms "determining" and "determining" used in the present disclosure may include various operations. The "judgment" and "determination" may include, for example, a matter in which judgment (determination), calculation (calculation), processing (processing), derivation (development), investigation (investigation), search (lookup up, search, inquiry) (for example, search in a table, database, or other data structure), confirmation (evaluation), or the like are regarded as a matter in which "judgment" and "determination" are performed. Further, "determining" and "deciding" may include a matter in which reception (e.g., reception of information), transmission (e.g., transmission of information), input (input), output (output), access (e.g., access of data in a memory) is performed as a matter in which "determining" and "deciding" are performed. Further, "judging" and "determining" may include the matters of performing a decision (resolving), a selection (selecting), a selection (setting), a establishment (establishing), a comparison (comparing), and the like as matters of performing "judging" and "determining". That is, the terms "determine" and "determining" may include what is considered to be any action. The "judgment (decision)" may be replaced by "assumption", "expectation", "consider", or the like.

In the present disclosure, the term "a is different from B" may also mean that "a is different from B". In addition, the term may mean that "a and B are different from C, respectively. The terms "separate," coupled, "and the like may also be construed as" different.

The present disclosure has been described in detail above, but it should be clear to those skilled in the art that the present disclosure is not limited to the embodiments described in the present disclosure. The present disclosure can be implemented as modifications and variations without departing from the spirit and scope of the present disclosure as defined by the claims. Accordingly, the description of the present disclosure is intended to be illustrative, and not in any limiting sense.

Description of the reference numerals

10: a wireless communication system;

20：NG-RAN；

100：gNB；

200：UE；

210: a wireless signal transmitting/receiving unit;

220: an amplifying section;

230: a modulation/demodulation unit;

240: a control signal/reference signal processing unit;

250: an encoding/decoding section;

260: a data transmitting/receiving unit;

270: a control unit;

1001: a processor;

1002: a memory;

1003: a memory;

1004: a communication device;

1005: an input device;

1006: an output device;

1007: a bus.

Claims

1. A terminal, wherein the terminal has:

A transmitting unit that transmits an uplink control channel, a 1 st uplink data channel, and a 2 nd uplink data channel; and

and a control unit configured to control transmission in the uplink based on repetition of the 1 st uplink data channel and the 2 nd uplink data channel in the time direction, omission of uplink transmission, and multiplexing of uplink control information to the 1 st uplink data channel or the 2 nd uplink data channel when the uplink control channel, the 1 st uplink data channel, and the 2 nd uplink data channel have the same priority.

2. A terminal, wherein the terminal has:

and a control unit configured to control transmission in the uplink based on repetition of the 1 st uplink data channel and the 2 nd uplink data channel in a time direction, omission of uplink transmission, multiplexing of uplink control information to the 1 st uplink data channel or the 2 nd uplink data channel, and intra-terminal priority/multiplexing processing when the uplink control channel, the 1 st uplink data channel, and the 2 nd uplink data channel have different priorities.

3. A wireless communication method, wherein the wireless communication method comprises the steps of:

the terminal transmits an uplink control channel, a 1 st uplink data channel and a 2 nd uplink data channel; and

and when the uplink control channel, the 1 st uplink data channel and the 2 nd uplink data channel have the same priority, the terminal controls the transmission in the uplink according to the repetition of the 1 st uplink data channel and the 2 nd uplink data channel in the time direction, the omission of the uplink transmission and the multiplexing of uplink control information to the 1 st uplink data channel or the 2 nd uplink data channel.

4. A wireless communication method, wherein the wireless communication method comprises the steps of:

and when the uplink control channel, the 1 st uplink data channel and the 2 nd uplink data channel have different priorities, the terminal controls the transmission in the uplink according to repetition of the 1 st uplink data channel and the 2 nd uplink data channel in the time direction, omission of uplink transmission, multiplexing of uplink control information to the 1 st uplink data channel or the 2 nd uplink data channel and in-terminal priority/multiplexing processing.