Terminals and wireless communication methods

Abstract

A terminal that comprises: a reception unit that, during data transmission to a plurality of terminals, receives data via a downlink channel; a transmission unit that sends feedback on the data; and a control unit that controls the feedback. The feedback includes first feedback in a format whereby negative responses are sent and positive responses are not. The control unit determines the processing method for a first uplink channel that pertains to the first feedback and a second uplink channel that is different from the first uplink channel, in accordance with the handling method for the first feedback if there is a temporal overlap of the first uplink channel and the second uplink channel.

Description

Technical Field

[0001] The present disclosure relates to a terminal compatible with multicast / broadcast services and a wireless communication method.

Background Art

[0002] The 3rd Generation Partnership Project (3GPP) is standardizing the 5th generation mobile communication system (also referred to as 5G, New Radio (NR) or Next Generation (NG)), and is also promoting the standardization of the next generation, which is called Beyond 5G, 5G Evolution or 6G.

[0003] In Release 17 of 3GPP, it targets the service of simultaneously transmitting data (which may also be called distribution) to a plurality of specific or unspecific terminals (User Equipment, UE) in NR, which is called Multicast and Broadcast Services (tentative name) (Non-Patent Document 1).

[0004] In MBS, for example, as a method of transmitting feedback on data received by a UE (HARQ feedback), a first method (NACK-only feedback) of transmitting a negative acknowledgment (NACK) without transmitting an affirmative acknowledgment (ACK), and a second method (ACK / NACK feedback) of transmitting both an affirmative acknowledgment (ACK) and a negative acknowledgment (NACK) are supported.

Prior Art Documents

Non-Patent Documents

[0005]

Non-Patent Document 1

[0006] Incidentally, when two or more NACK-only feedbacks are obtained in a single slot where PUCCH is scheduled, several handling methods for handling two or more NACK-only feedbacks have been considered. Furthermore, when a PUCCH related to NACK-only feedback overlaps temporally with other uplink channels (PUCCH or PUSCH), methods for multiplexing a PUCCH related to NACK-only feedback with other uplink channels have also been considered.

[0007] Against this backdrop, the inventors, after diligent study, found a need to clarify the operation of the UE by considering a method for handling NACK-only feedback in cases where the PUCCH related to NACK-only feedback overlaps temporally with other uplink channels.

[0008] Therefore, the present invention has been made in view of these circumstances, and aims to provide a terminal and wireless communication method that can clarify the operation by assuming a method for handling NACK-only feedback in cases where a PUCCH related to NACK-only feedback overlaps in time with other uplink channels.

[0009] One aspect of the disclosure is a terminal comprising, in data distribution to multiple terminals, a receiving unit that receives data via a downlink channel, a transmitting unit that transmits feedback for the data, and a control unit that controls the feedback, wherein the feedback includes a first feedback that transmits a negative response without transmitting an affirmative response, and the control unit determines a processing method for the first uplink channel and the second uplink channel according to a handling method for the first feedback when the first uplink channel relating to the first feedback temporally overlaps with a second uplink channel different from the first uplink channel.

[0010] One aspect of the disclosure is a wireless communication method comprising: step A of receiving data via a downlink channel in data distribution to a plurality of terminals; step B of transmitting feedback for the data, wherein the feedback includes a first feedback of a type that transmits a negative response without transmitting an acknowledgment; and step C of determining a processing method for the first uplink channel and the second uplink channel according to a handling method for the first feedback when the first uplink channel for the first feedback temporally overlaps with a second uplink channel different from the first uplink channel. [Brief explanation of the drawing]

[0011] [Figure 1] Figure 1 is a schematic diagram of the overall configuration of the wireless communication system 10. [Figure 2] Figure 2 shows the frequency range used in the wireless communication system 10. [Figure 3] Figure 3 shows an example of the configuration of wireless frames, subframes, and slots used in the wireless communication system 10. [Figure 4] Figure 4 is a functional block diagram of the UE200. [Figure 5] Figure 5 is a functional block diagram of the gNB100. [Figure 6]FIG. 6 is a diagram showing a configuration example of PTM transmission method 1 and PTM transmission method 2. [Figure 7] FIG. 7 is a diagram for explaining the problem. [Figure 8] FIG. 8 is a diagram for explaining an operation example. [Figure 9] FIG. 9 is a diagram for explaining an operation example. [Figure 10] FIG. 10 is a diagram for explaining an operation example. [Figure 11] FIG. 11 is a diagram for explaining an operation example. [Figure 12] FIG. 12 is a diagram for explaining an operation example. [Figure 13] FIG. 13 is a diagram for explaining an operation example. [Figure 14] FIG. 14 is a diagram for explaining an operation example. [Figure 15] FIG. 15 is a diagram showing an example of the hardware configuration of gNB100 and UE200. [Figure 16] FIG. 16 is a diagram showing a configuration example of vehicle 2001. DETAILED DESCRIPTION OF THE INVENTION

[0012] Hereinafter, embodiments will be described based on the drawings. Note that the same or similar reference numerals are assigned to the same functions and configurations, and the description thereof will be omitted as appropriate.

[0013] [Embodiment] (1) Overall schematic configuration of the wireless communication system FIG. 1 is an overall schematic configuration diagram of a wireless communication system 10 according to an embodiment. The wireless communication system 10 is a wireless communication system according to 5G New Radio (NR), and includes a Next Generation - Radio Access Network 20 (hereinafter, NG - RAN20) and a terminal 200 (hereinafter, UE (User Equipment) 200).

[0014] Note that the wireless communication system 10 may also be a wireless communication system according to a scheme called Beyond 5G, 5G Evolution, or 6G.

[0015] NG-RAN20 includes a base station 100 (hereinafter, gNB100). Note that the specific configuration of the wireless communication system 10 including the number of gNB100 and UE200 is not limited to the example shown in FIG. 1.

[0016] Actually, NG-RAN20 includes a plurality of NG-RAN Nodes, specifically, gNB (or ng-eNB), and is connected to a core network (5GC, not shown) according to 5G. Note that NG-RAN20 and 5GC may simply be expressed as "network".

[0017] gNB100 is a wireless base station according to 5G and performs wireless communication with UE200 according to 5G. gNB100 and UE200 can support Massive MIMO (Multiple-Input Multiple-Output) that generates a more directional beam BM by controlling wireless signals transmitted from a plurality of antenna elements, carrier aggregation (CA) that bundles and uses a plurality of component carriers (CC), and dual connectivity (DC) that communicates with two or more transport blocks simultaneously between the UE and each of the two NG-RAN Nodes.

[0018] In addition, the wireless communication system 10 supports a plurality of frequency ranges (FR). FIG. 2 shows the frequency ranges used in the wireless communication system 10.

[0019] As shown in FIG. 2, the wireless communication system 10 supports FR1 and FR2. The frequency bands of each FR are as follows.

[0020] ·FR1: 410 MHz to 7.125 GHz ·FR2: 24.25 GHz to 52.6 GHz In FR1, a Sub-Carrier Spacing (SCS) of 15, 30, or 60 kHz may be used, and a bandwidth (BW) of 5 to 100 MHz may be used. FR2 is a higher frequency than FR1, and a 60 or 120 kHz (240 kHz may be included) SCS may be used, and a bandwidth (BW) of 50 to 400 MHz may be used.

[0021] Note that SCS may also be interpreted as numerology. Numerology is defined in 3GPP TS38.300 and corresponds to a single subcarrier interval in the frequency domain.

[0022] Furthermore, the wireless communication system 10 also supports higher frequency bands than the FR2 frequency band. Specifically, the wireless communication system 10 supports frequency bands exceeding 52.6 GHz up to 71 GHz or 114.25 GHz. Such high frequency bands may be conveniently referred to as "FR2x".

[0023] To address the problem of increased phase noise in high-frequency bands, when using bandwidths exceeding 52.6 GHz, Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) / Discrete Fourier Transform - Spread (DFT-S-OFDM) with a larger Sub-Carrier Spacing (SCS) may be applied.

[0024] Figure 3 shows an example of the configuration of wireless frames, subframes, and slots used in the wireless communication system 10.

[0025] As shown in Figure 3, one slot consists of 14 symbols, and the larger (wider) the SCS, the shorter the symbol period (and slot period). The SCS is not limited to the interval (frequency) shown in Figure 3. For example, 480 kHz, 960 kHz, etc., may be used.

[0026] Furthermore, the number of symbols constituting one slot does not necessarily have to be 14 (for example, 28 symbols, 56 symbols). In addition, the number of slots per subframe may differ depending on the SCS.

[0027] The time direction (t) shown in Figure 3 may also be called the time domain, symbol period, or symbol time. The frequency direction may also be called the frequency domain, resource block, subcarrier, or bandwidth part (BWP).

[0028] DMRS is a type of reference signal, prepared for various channels. Here, unless otherwise specified, it may refer to the DMRS for the downlink data channel, specifically the PDSCH (Physical Downlink Shared Channel). However, the DMRS for the uplink data channel, specifically the PUSCH (Physical Uplink Shared Channel), may be interpreted as being the same as the DMRS for the PDSCH.

[0029] DMRS can be used for channel estimation in a device, for example, as part of coherent demodulation in the UE200. DMRS may only be present in the resource block (RB) used for PDSCH transmission.

[0030] A DMRS may have multiple mapping types. Specifically, a DMRS may have mapping type A and mapping type B. In mapping type A, the first DMRS is placed on the second or third symbol of the slot. In mapping type A, the DMRS may be mapped relative to the slot boundary, regardless of where in the slot the actual data transmission begins. The reason the first DMRS is placed on the second or third symbol of the slot may be interpreted as being placed after the control resource sets (CORESET).

[0031] In mapping type B, the first DMRS may be placed on the first symbol of the data allocation. That is, the position of the DMRS may be given relative to where the data is located, rather than relative to the slot boundary.

[0032] Furthermore, DMRS may have multiple types. Specifically, DMRS may have Type 1 and Type 2. Type 1 and Type 2 differ in their frequency domain mapping and the maximum number of orthogonal reference signals. Type 1 is a single-symbol DMRS that can output up to four orthogonal signals, while Type 2 is a double-symbol DMRS that can output up to eight orthogonal signals.

[0033] (2) Functional block configuration of the wireless communication system Next, the functional block configuration of the wireless communication system 10 will be described.

[0034] First, we will describe the functional block configuration of the UE200.

[0035] Figure 4 is a functional block diagram of the UE200. As shown in Figure 4, the UE200 comprises a wireless signal transmission / reception unit 210, an amplifier unit 220, a modulation / demodulation unit 230, a control signal / reference signal processing unit 240, an encoding / decoding unit 250, a data transmission / reception unit 260, and a control unit 270.

[0036] The wireless signal transceiver unit 210 transmits and receives wireless signals in accordance with NR. The wireless signal transceiver unit 210 supports Massive MIMO, CA which uses multiple CCs bundled together, and DC which communicates simultaneously between the UE and each of the two NG-RAN Nodes.

[0037] The amplifier section 220 consists of components such as a PA (Power Amplifier) ​​and an LNA (Low Noise Amplifier). The amplifier section 220 amplifies the signal output from the modulation / demodulation section 230 to a predetermined power level. The amplifier section 220 also amplifies the RF signal output from the wireless signal transmission / reception section 210.

[0038] The modulation / demodulation unit 230 performs data modulation / demodulation, transmit power setting, and resource block allocation for each predetermined communication destination (gNB100 or other gNB). The modulation / demodulation unit 230 may apply Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) / Discrete Fourier Transform - Spread (DFT-S-OFDM). Furthermore, DFT-S-OFDM may be used not only for the uplink (UL) but also for the downlink (DL).

[0039] The control signal / reference signal processing unit 240 performs processing related to various control signals transmitted and received by the UE200, and processing related to various reference signals transmitted and received by the UE200.

[0040] Specifically, the control signal / reference signal processing unit 240 receives various control signals transmitted from the gNB100 via a predetermined control channel, such as control signals for the radio resource control layer (RRC). The control signal / reference signal processing unit 240 also transmits various control signals to the gNB100 via a predetermined control channel.

[0041] The control signal / reference signal processing unit 240 performs processing using reference signals (RS) such as the Demodulation Reference Signal (DMRS) and the Phase Tracking Reference Signal (PTRS).

[0042] DMRS is a terminal-specific, known reference signal (pilot signal) between the base station and the terminal used to estimate the fading channel used for data demodulation. PTRS is a terminal-specific reference signal intended to estimate phase noise, which is a problem in the high-frequency band.

[0043] In addition to DMRS and PTRS, the reference signals may also include Channel State Information-Reference Signal (CSI-RS), Sounding Reference Signal (SRS), and Positioning Reference Signal (PRS) for location information.

[0044] Furthermore, channels include control channels and data channels. Control channels include PDCCH (Physical Downlink Control Channel), PUCCH (Physical Uplink Control Channel), RACH (Random Access Channel), Downlink Control Information (DCI) including Random Access Radio Network Temporary Identifier (RA-RNTI), and Physical Broadcast Channel (PBCH), among others.

[0045] Furthermore, data channels include PDSCH (Physical Downlink Shared Channel) and PUSCH (Physical Uplink Shared Channel), among others. "Data" refers to data transmitted through a data channel. A data channel can also be interpreted as a shared channel.

[0046] Here, the control signal / reference signal processing unit 240 may receive downlink control information (DCI). The DCI includes fields that store existing fields such as DCI Formats, Carrier indicator (CI), BWP indicator, FDRA (Frequency Domain Resource Assignment), TDRA (Time Domain Resource Assignment), MCS (Modulation and Coding Scheme), HPN (HARQ Process Number), NDI (New Data Indicator), and RV (Redundancy Version).

[0047] The value stored in the DCI Format field is an information element that specifies the DCI format. The value stored in the CI field is an information element that specifies the CC to which the DCI applies. The value stored in the BWP indicator field is an information element that specifies the BWP to which the DCI applies. The BWP that can be specified by the BWP indicator is set by an information element (BandwidthPart-Config) included in the RRC message. The value stored in the FDRA field is an information element that specifies the frequency domain resource to which the DCI applies. The frequency domain resource is identified by the value stored in the FDRA field and an information element (RA Type) included in the RRC message. The value stored in the TDRA field is an information element that specifies the time domain resource to which the DCI applies. The time domain resource is identified by the value stored in the TDRA field and an information element (pdsch-TimeDomainAllocationList, push-TimeDomainAllocationList) included in the RRC message. The time domain resource may also be identified by the value stored in the TDRA field and the default table. The value stored in the MCS field is an information element that specifies the MCS to which the DCI applies. The MCS is identified by the value stored in MCS and the MCS table. The MCS table may be specified by the RRC message or identified by RNTI scrambling. The value stored in the HPN field is an information element that specifies the HARQ Process to which DCI is applied. The value stored in NDI is an information element that determines whether the data to which DCI is applied is initial transmission data. The value stored in the RV field is an information element that specifies the redundancy of the data to which DCI is applied.

[0048] In this embodiment, the control signal / reference signal processing unit 240 constitutes a transmitting unit that transmits feedback to the data. As will be described later, the data may include data related to MBS (Multicast and Broadcast Services). Two methods are supported for transmitting feedback (hereinafter referred to as HARQ feedback): a first method that transmits a negative response (NACK) without transmitting an acknowledgment (ACK) (hereinafter referred to as NACK-only feedback), and a second method that transmits both an acknowledgment (ACK) and a negative response (NACK) (hereinafter referred to as ACK / NACK feedback). NACK-only feedback is an example of the first feedback, and ACK / NACK feedback is an example of the second feedback.

[0049] The encoding / decoding unit 250 performs data splitting / concatenation and channel coding / decoding for each predetermined communication destination (gNB100 or other gNB).

[0050] Specifically, the encoding / decoding unit 250 divides the data output from the data transmission / reception unit 260 into predetermined sizes and performs channel coding on the divided data. The encoding / decoding unit 250 also decodes the data output from the modulation / demodulation unit 230 and concatenates the decoded data.

[0051] The data transmission / reception unit 260 performs the transmission and reception of Protocol Data Units (PDUs) and Service Data Units (SDUs). Specifically, the data transmission / reception unit 260 performs assembly / decomposition of PDUs / SDUs at multiple layers (such as the Media Access Control Layer (MAC), Radio Link Control Layer (RLC), and Packet Data Convergence Protocol Layer (PDCP)). In addition, the data transmission / reception unit 260 performs error correction and retransmission control of data based on HARQ (Hybrid Automatic Repeat Request).

[0052] In this embodiment, the data transmission / reception unit 260 constitutes a receiving unit that receives data via a downlink channel in data distribution to multiple terminals. Data distribution to multiple terminals may be referred to as MBS (Multicast and Broadcast Services). The downlink channel may include PDSCH (multicast) transmitted by multicast, or PDSCH (unicast) transmitted by unitycast. Hereinafter, PDSCH (multicast) and PDSCH (unicast) will be collectively referred to as PDSCH (multicast / unicast). Reception of PDSCH (multicast / unicast) may be read as reception of data via PDSCH (multicast / unicast).

[0053] The control unit 270 controls each functional block that constitutes the UE200. In this embodiment, the control unit 270 constitutes a control unit that controls feedback. When the first uplink channel (hereinafter referred to as MBS PUCCH) related to the first feedback for PDSCH (multicast) reception (hereinafter referred to as NACK-only feedback) overlaps in time with a second uplink channel different from the first uplink channel (for example, Unicast PUSCH / PUCCH, i.e., Unicast PUSCH transmission, or PUCCH transmission in response to PDSCH (unicast) reception, or PUCCH transmission including at least one of SR / CSI), the control unit 270 determines how to process the first uplink channel and the second uplink channel according to the handling method for NACK-only feedback.

[0054] Here, the first uplink channel may be referred to as the MBS PUCCH to distinguish it from the second uplink channel. The second uplink channel is an uplink channel used outside of MBS and may be scheduled by a UL grant included in the DCI.

[0055] Secondly, the functional block configuration of the gNB100 will be described.

[0056] Figure 5 is a functional block diagram of the gNB100. As shown in Figure 5, the gNB100 has a receiving unit 110, a transmitting unit 120, and a control unit 130.

[0057] The receiving unit 110 receives various signals from the UE200. The receiving unit 110 may also receive the UL signal via PUCCH or PUSCH. In this embodiment, the receiving unit 110 may also receive the feedback described above.

[0058] The transmitter 120 transmits various signals to the UE200. The transmitter 120 may also transmit DL signals via PDCCH or PDSCH. In this embodiment, the transmitter 120 may transmit PDSCH (multicast / unicast) in the MBS. The transmission of PDSCH (multicast / unicast) may be interpreted as the transmission of data via PDSCH (multicast / unicast).

[0059] The control unit 130 controls the gNB100. In an embodiment, the control unit 130 may assume that when the first uplink channel (MBS PUCCH) relating to the first feedback (NACK-only feedback) overlaps in time with a second uplink channel (e.g., Unicast PUSCH / PUCCH) which is different from the first uplink channel, the processing method for the first uplink channel and the second uplink channel is determined according to the handling method for the NACK-only feedback.

[0060] (3) Provision of MBS The wireless communication system 10 may provide multicast and broadcast services (MBS).

[0061] For example, in stadiums and halls, it is conceivable that numerous UE200s are located within a certain geographical area and that many UE200s receive the same data simultaneously. In such cases, using MBS (Mobile-Based Broadcasting) is more effective than unicast.

[0062] Unicast can be interpreted as one-to-one communication between a specific UE200 (which may also be specified by its unique identifier) ​​and the network.

[0063] Multicast can be interpreted as communication between a network and multiple specific UE200 devices (multicast identification information may also be specified). Note that the number of UE200 devices receiving incoming multicast data may ultimately be just one.

[0064] Broadcasting can be interpreted as communication between the network and an unspecified number of devices, directed at all UE200s. Multicast / broadcast data may be identical copies, but some content, such as the header, may differ. Multicast / broadcast data may be transmitted (distributed) simultaneously, but strict simultaneity is not necessarily required, and propagation delays and / or processing delays within RAN nodes may be included.

[0065] The UE200 in question may have a Wireless Resource Control Layer (RRC) in any of the following states: idle, connected, or inactive. The inactive state can be interpreted as a state in which some RRC settings are maintained.

[0066] In MBS, three methods are envisioned for scheduling multicast / broadcast PDSCH, specifically for scheduling MBS packets (which can be interpreted as data). Note that RRC connected UE may be interpreted as RRC idle UE or RRC inactive UE.

[0067] ·PTM transmission method 1 (PTM-1): • For the MBS group of an RRC-connected UE, schedule a group-common PDSCH (Physical Downlink Control Channel) using a group-common PDCCH. • The CRC and PDSCH of PDCCH are scrambled by the group-common RNTI (Radio Network Temporary Identifier, also known as G-RNTI). ·PTM transmission method 2 (PTM-2): • For an RRC-connected UE's MBS group, schedule a group-common PDSCH using a UE-specific PDCCH. • PDCCH CRCs are scrambled by UE-specific RNTIs. PDSCH is scrambled by group-common RNTI. ·PTP transmission method: • For RRC-connected UEs, schedule UE-specific PDSCHs using UE-specific PDCCHs. The CRC and PDSCH of PDCCH are scrambled by a UE-specific RNTI. This means that MBS packets are transmitted via unicast. Figure 6 shows example configurations for PTM transmission methods 1 and 2. Note that the UE-specific PDCCH / PDSCH can be identified by the target UE, but does not need to be identifiable by other UEs within the same MBS group. The group-common PDCCH / PDSCH is transmitted using the same time / frequency resources and can be identified by all UEs within the same MBS group. Furthermore, the names of PTM transmission methods 1 and 2 are provisional and may be referred to by other names as long as the above-described operations are performed.

[0068] In point-to-point (PTP) distribution, a RAN node may wirelessly distribute individual copies of MBS data packets to individual UEs. In point-to-multipoint (PTM) distribution, a RAN node may wirelessly distribute a single copy of MBS data packets to a set of UEs.

[0069] Furthermore, in order to improve the reliability of MBS, two feedback methods are envisioned for HARQ (Hybrid Automatic Repeat Request) feedback, specifically for HARQ feedback to multicast / broadcast PDSCH.

[0070] Option 1: Both ACK and NACK feedback (ACK / NACK feedback) • If the UE successfully receives and decodes the PDSCH signal, it sends an ACK. If the UE fails to receive and decode the PDSCH signal, it will send a NACK. • PUCCH (Physical Uplink Control Channel) resource settings: Allows you to configure PUCCH-Config for multicast. PUCCH Resources: Shared / orthogonal between UEs depends on the network settings. • HARQ-ACK CB (codebook): Supports type-1 and type-2 (CB decision algorithm (specified in 3GPP TS38.213)) • Multiplexing: Unicast or multicast can be applied. Option 2: NACK-only feedback A UE that successfully receives and decodes PDSCH does not send an ACK (no response). If the UE fails to receive and decode the PDSCH signal, it will send a NACK. • In a given UE, PUCCH resource settings can be configured separately for unicast and groupcast (multicast). Note that ACK may also be called a positive acknowledgement, and NACK may be called a negative acknowledgement. HARQ may also be called an automatic retransmission request.

[0071] Enabling or disabling Option 1 or Option 2 may be done by either of the following methods:

[0072] • RRC and Downlink Control Information (DCI) RRC only Furthermore, the following is envisioned for Semi-persistent Scheduling (SPS) of multicast / broadcast PDSCH.

[0073] • Uses SPS group-common PDSCH • As a UE capability, multiple SPS group-common PDSCHs can be configured. • HARQ feedback is available for SPS group-common PDSCH. • At least group-common PDCCH (downlink control channel) activation / deactivation is possible. Note that "deactivation" may be replaced with other synonymous terms such as "release." For example, "activation" may be replaced with "start," "start," or "trigger," and "deactivation" may be replaced with "end," "stop," or "stop."

[0074] SPS is a scheduling method used in contrast to dynamic scheduling, and may also be called semi-fixed, semi-persistent, or semi-permanent scheduling, and may be interpreted as Configured Scheduling (CS).

[0075] Scheduling can be interpreted as the process of allocating resources for transmitting data. Dynamic scheduling can be interpreted as a mechanism in which all PDSCHs are scheduled by DCI (e.g., DCI 1_0, DCI 1_1, or DCI 1_2). SPS can be interpreted as a mechanism in which PDSCH transmissions are scheduled by higher-layer signaling such as RRC messages.

[0076] Furthermore, regarding the physical layer, there may be scheduling categories for time-domain scheduling and frequency-domain scheduling.

[0077] Furthermore, multicast, groupcast, broadcast, and MBS may be interpreted interchangeably. Multicast PDSCH and PDSCH scrambled by group common RNTI may also be interpreted interchangeably.

[0078] Furthermore, the terms data and packet may be interpreted interchangeably and may be considered synonymous with terms such as signal and data unit. Also, transmission, reception, transmission, and distribution may be interpreted interchangeably.

[0079] (4) Challenges The following describes the challenges related to NACK-only feedback.

[0080] Firstly, when two or more NACK-only feedbacks are obtained in a single slot where PUCCH is scheduled, the following handling methods have been considered for handling two or more NACK-only feedbacks.

[0081] Handling method 1 is a method for converting NACK-only feedback to ACK / NACK feedback. Specifically, the UE200 can multiplex HARQ-ACK bits by converting NACK-only feedback to ACK / NACK feedback.

[0082] Handling method 2 is a method that supports the transmission of PUCCHs for two or more NACK-only feedbacks within a specific time period (here, a slot). Specifically, the specific time period is divided into two or more unit time periods (e.g., sub-slots), and the UE200 can transmit one PUCCH for one NACK-only feedback for each sub-slot.

[0083] Handling method 3 is a method that supports the transmission of two or more PUCCHs related to NACK-only feedback within a specific time period (here, a slot). Specifically, without dividing the specific time period into two or more unit time periods (e.g., sub-slots), the UE200 can transmit two or more PUCCHs related to NACK-only feedback within a slot. That is, two PUCCHs, each containing information related to NACK-only feedback, can be transmitted within a slot.

[0084] Handling method 4 is a method of associating a combination of two or more NACK-only feedback (HARQ-ACK bits) with a specific sequence or resource related to PUCCH. In such cases, the UE200 transmits combinations that include NACK, and does not transmit combinations that consist only of ACK.

[0085] Handling method 5 is a method for bundling two or more NACK-only feedbacks (HARQ-ACK bits). For example, if at least one of the two or more NACK-only feedbacks has a NACK, these two or more NACK-only feedbacks are bundled together and treated as a single NACK feedback. If none of them have a NACK, none of the NACK-only feedbacks are treated.

[0086] Under these circumstances, as shown in Figure 7, there is a possibility that a PUCCH related to NACK-only feedback for a Group-common PDSCH may overlap in time with a PUCCH that includes a PUSCH and / or at least one other HARQ-ACK / SR / CSI. In such a case, unless the operation of the UE is clarified according to the NACK-only feedback handling method described above, the gNB100 will not be able to determine whether or not NACK-only feedback is being sent.

[0087] (5) Example of operation The following describes examples of how to address the aforementioned issues. These examples will be explained for each method of handling NACK-only feedback.

[0088] (5.1) Handling Method 1 As described above, handling method 1 is a method for converting NACK-only feedback to ACK / NACK feedback. UE200 determines how to process MBS PUCCH and Unicast PUSCH / PUCCH depending on whether handling method 1 is applied.

[0089] Whether handling method 1 applies may be predefined in the wireless communication network 10 and may be implicitly or explicitly specified by at least one of the RRC message, MAC CE message, and DCI. The specification may be interpreted as setting, updating, instructing, activating, deactivating, etc. Alternatively, whether handling method 1 applies may be determined based on the number of NACK-only feedbacks, or based on the number of NACK-only feedbacks that temporally overlap with the PUCCH containing the PUSCH and / or at least one of the other HARQ-ACK / SR / CSIs.

[0090] Firstly, UE200 may perform Option 1 shown below when Handling Method 1 is applied.

[0091] In Option 1-1, UE200 may multiplex MBS PUCCH (HARQ ACK / NACK) and Unicast PUCCH (SR or CSI) if their priority indices are the same, or it may drop one of them based on a higher layer parameter (e.g., simultaneousHARQ-ACK-CSI).

[0092] In Option 1-2, the UE200 may multiplex HARQ ACK / NACK onto the Unicast PUSCH if the priority index of the MBS PUCCH (HARQ ACK / NACK) is the same as the priority index of the Unicast PUSCH.

[0093] In options 1-3, UE200 may be multiplexed by concatenating each subcodebook if the priority index of MBS PUCCH (HARQ ACK / NACK) is the same as the priority index of Unicast PUCCH (HARQ-ACK / NACK), or by generating a codebook from each PDSCH-to-PUCCH offset k1 and TDRA Table.

[0094] In options 1-4, if the priority index of the MBS PUCCH (HARQ ACK / NACK) differs from the priority index of the Unicast PUSCH, the UE200 may drop the one with the lower priority index, or it may duplicate both based on the higher layer parameters, or it may drop one of them.

[0095] Secondly, if handling method 1 is not applicable, UE200 may perform the following options:

[0096] Option 2a describes the case where the MBS PUCCH overlaps in time with the Unicast PUSCH.

[0097] In option 2a-1, the UE200 may multiplex the NACK-only feedback with the Unicast PUSCH and send the Unicast PUSCH. In this case, the UE200 does not need to send the MBS PUSCH.

[0098] In option 2a-2, the UE200 may send an MBS PUSCH without multiplexing the NACK-only feedback into the Unicast PUSCH. In such a case, the UE200 may or may not send a Unicast PUSCH.

[0099] In option 2a-3, the UE200 may multiplex NACK-only feedback with the Unicast PUSCH and send both the Unicast PUSCH and the MBS PUSCH.

[0100] In option 2a-4, the UE200 does not need to send an MBS PUSCH by not multiplexing the NACK-only feedback into the Unicast PUSCH. In such cases, the UE200 may or may not send a Unicast PUSCH.

[0101] In option 2a-5, UE200 may apply one of options 2a-1 to 2a-4 depending on whether or not a NACK was generated for the Group-common PDSCH. For example, UE200 may apply option 2a-4 if no NACK was generated for the Group-common PDSCH. UE200 may apply option 2a-1 or option 2a-2 if a NACK was generated for the Group-common PDSCH.

[0102] In option 2a-6, the UE200 may apply any of options 2a-1 to 2a-4 based on the number of bits in the NACK-only feedback. For example, the UE200 may apply option 2a-1 if the number of bits in the NACK-only feedback is 2 bits or less. In such cases, the UE200 may multiplex the NACK-only feedback to the Unicast PUSCH by puncturing the Unicast PUSCH. The UE200 may apply option 2a-4 if the number of bits in the NACK-only feedback is greater than 2 bits.

[0103] In option 2a-7, the UE200 may apply any of options 2a-1 to 2a-4 based on the PUCCH format of the MBS PUCCH for NACK-only feedback.

[0104] In Option 2a-8, the UE200 may apply any of Options 2a-1 to 2a-4 based on the parameters shown below. The parameters may include one or more parameters selected from RRC parameters, MAC CE, DCI format, DCI fields, RNTI for scrambling PDCCH (CRC of DCI), CORSET, search space, and UE Capability.

[0105] In option 2a-9, the method for multiplexing NACK-only feedback for the MBS onto the Unicast PUSCH may differ from the method for multiplexing HARQ-ACK / NACK for the Group-common PDSCH onto the Unicast PUSCH. For example, the UE200 may puncture the Unicast PUSCH regardless of the number of bits in the NACK-only feedback and then multiplex the NACK-only feedback onto the Unicast PUSCH.

[0106] In option 2a-10, the UL DAI (Downlink Assignment Index) of the UL grant (DCI) that schedules the Unicast PUSCH may be a value that assumes the NACK-only feedback is multiplexed onto the Unicast PUSCH. In such a case, the UE200 may multiplex the NACK-only feedback onto the Unicast PUSCH based on the UL DAI of the UL grant (DCI) that schedules the Unicast PUSCH. Alternatively, the UL DAI of the UL grant (DCI) that schedules the Unicast PUSCH may be a value that assumes the NACK-only feedback is not multiplexed onto the Unicast PUSCH. In such a case, the UE200 does not have to multiplex the NACK-only feedback onto the Unicast PUSCH based on the UL DAI of the UL grant (DCI) that schedules the Unicast PUSCH.

[0107] Furthermore, UE200 does not need to anticipate receiving a DCI (DL Assignment) that schedules a Group-common PDSCH corresponding to NACK-only feedback which may be multiplexed to a Unicast PUSCH, after a UL grant (DCI) that schedules a Unicast PUSCH. UE200 also does not need to anticipate receiving a DCI that schedules an MBS PUCCH (NACK-only feedback) which may temporally overlap with a Unicast PUSCH, after a UL grant (DCI) that schedules a Unicast PUSCH.

[0108] In option 2a-11, UE200 may send an ACK to the Group-common PDSCH if it has successfully received / decoded the Group-common PDSCH and has an opportunity to send a HARQ-ACK. For example, UE200 may multiplex an ACK to the Group-common PDSCH with a Unicast PUSCH if there is a Unicast PUSCH that overlaps with the MBS PUCCH in time (e.g., option 2a-1). In other words, UE200 may determine that there is a time overlap between the MBS PUCCH and the Unicast PUSCH / PUCCH even if it is not necessary to send NACK-only feedback.

[0109] Option 2a-12 allows UE200 to send an ACK to the Group-common PDSCH if it has successfully received / decoded the Group-common PDSCH and has an opportunity to send a HARQ-ACK, regardless of whether NACK-only feedback is configured or instructed. For example, UE200 may multiplex an ACK to the Group-common PDSCH with a Unicast PUSCH if there is a Unicast PUSCH that overlaps in time with the MBS PUCCH, regardless of whether NACK-only feedback is configured or instructed (e.g., Option 2a-1). In other words, UE200 may determine that there is a time overlap between the MBS PUCCH and the Unicast PUSCH / PUCCH even if it is not necessary to send NACK-only feedback.

[0110] Option 2b describes the case where the MBS PUCCH overlaps in time with the Unicast PUCCH. In the following, the MBS PUCCH will be referred to as PUCCH X and the Unicast PUCCH as PUCCH Y. The UCI (NACK-only feedback) related to PUCCH X will be referred to as UCI X, and the UCI related to PUCCH Y will be referred to as UCI X.

[0111] In option 2b-1, UE200 may multiplex PUCCH X and PUCCH Y on a PUCCH other than PUCCH X and PUCCH Y (hereinafter referred to as PUCCH Z). The PUCCH that multiplexes UCI X may be predefined in the wireless communication network 10, and may be a PUCCH with a high priority index. UE200 does not have to transmit either PUCCH X or PUCCH Y.

[0112] In option 2b-2, UE200 may drop either PUCCH X or PUCCH Y and transmit the other. Which of PUCCH X or PUCCH Y to transmit may be predefined in the wireless communication network 10 and may be determined based on the priority index of PUCCH X and PUCCH Y. The priority index may be identified by the priority indicator of the DCI that schedules PUCCH X and PUCCH Y. If the priority index of PUCCH X and PUCCH Y is the same, UE200 may drop either PUCCH. If the priority indices of PUCCH X and PUCCH Y are different, UE200 may drop the PUCCH with the lower priority index and transmit the PUCCH with the lower priority index.

[0113] In option 2b-3, the UE200 may transmit UCI X as PUCCH X and UCI Y as PUCCH Y without multiplexing PUCCH X and PUCCH Y.

[0114] In option 2b-4, UE200 may apply one of options 2b-1 to 2b-3 depending on whether or not a NACK has been generated for the Group-common PDSCH.

[0115] In option 2b-5, UE200 may apply any of options 2b-1 to 2b-3 based on the number of bits in UCI X, or the total number of bits in UCI X and UCI Y.

[0116] In option 2b-6, the UE200 may apply any of options 2b-1 to 2b-3 based on at least one PUCCH format, either PUCCH X or PUCCH Y.

[0117] In option 2b-7, the UE200 may apply any of options 2b-1 to 2b-3 based on the parameters shown below. The parameters may include one or more parameters selected from RRC parameters, MAC CE, DCI format, DCI fields, RNTI for scrambling PDCCH (DCI CRC), CORSET, search space, and UE Capability.

[0118] In option 2a-8, UE200 may send an ACK to the Group-common PDSCH if it has successfully received / decoded the Group-common PDSCH and has an opportunity to send a HARQ-ACK. For example, if UE200 decides to send PUCCH Y because PUCCH X and PUCCH Y overlap in time, it may multiplex an ACK to the Group-common PDSCH with PUCCH Y. Alternatively, if UE200 decides to send PUCCH Y because PUCCH X, PUCCH Y, and PUCCH X overlap in time, it may multiplex an ACK to the Group-common PDSCH with PUCCH Y. In other words, UE200 may determine that there is a time overlap between the MBS PUCCH and the Unicast PUSCH / PUCCH even if it is not necessary to send NACK-only feedback.

[0119] In option 2a-9, UE200 may send an ACK to the Group-common PDSCH if it has successfully received / decoded the Group-common PDSCH and has an opportunity to send a HARQ-ACK, regardless of whether NACK-only feedback is configured or instructed. For example, if PUCCH X and PUCCH Y overlap in time and UE200 decides to send PUCCH Y, UE200 may multiplex an ACK to the Group-common PDSCH with PUCCH Y, regardless of whether NACK-only feedback is configured or instructed. Alternatively, if PUCCH X, PUCCH Y, and PUCCH X overlap in time and UE200 decides to send PUCCH Y, UE200 may multiplex an ACK to the Group-common PDSCH with PUCCH Y, regardless of whether NACK-only feedback is configured or instructed. In other words, UE200 may determine that there is a time overlap between the MBS PUCCH and the Unicast PUSCH / PUCCH even if it is not necessary to send NACK-only feedback.

[0120] (5.2) Handling Method 2 As described above, handling method 2 is a method of sending one PUCCH for NACK-only feedback per sub-slot. When handling method 2 is applied, UE200 determines, based on specific conditions, whether the MBS PUCCH overlaps in time with the Unicast PUSCH / PUCCH.

[0121] Whether handling method 2 applies may be predefined in the wireless communication network 10 and may be implicitly or explicitly specified by at least one of the RRC message, MAC CE message, and DCI. The specification may be interpreted as setting, updating, instructing, activating, deactivating, etc.

[0122] For example, consider a case where, as shown in Figure 8, two MBS PUCCHs (PUCCH#1 and PUCCH#2 in Figure 8) and a Unicast PUSCH (simply PUSCH in Figure 8) are scheduled during a specific period (Slot). Although Figure 8 illustrates a Unicast PUSCH, the second uplink channel may also be a Unicast PUCCH.

[0123] In such cases, the specific condition is determined on a sub-slot basis. That is, the specific condition is the condition for determining whether the resources related to the Unicast PUSCH overlap with other MBS PUCCH (NACK-only feedback) when a Unicast PUSCH is scheduled in the same sub-slot where an MBS PUCCH (NACK-only feedback) is scheduled.

[0124] The UE200 determines how to process MBS PUCCH and Unicast PUSCH / PUCCH based on whether or not specific conditions are met.

[0125] Firstly, in Case 1, PUCCH#1 overlaps in time with PUSCH, but PUSCH, which overlaps in time with PUCCH#1, does not overlap in time with PUCCH#2. Therefore, UE200 determines that the specific condition is not met. The behavior of UE200 in the case where the specific condition is not met may be as shown below.

[0126] For example, since PUCCH#1 and PUSCH overlap in time, UE200 may implement the multiplexing method related to handling method 1 (option 2 described above). Alternatively, UE200 may use the multiplexing method related to handling method 5 described later. On the other hand, since PUCCH#2 does not overlap in time with PUSCH, UE200 may transmit PUCCH#2 as is.

[0127] Secondly, in Case 2, PUCCH#1 overlaps in time with PUSCH, and PUSCH, which overlaps in time with PUCCH#1, also overlaps in time with PUCCH#2. Therefore, UE200 determines that the specific condition is met. The operation of UE200 in the case where the specific condition is met may be option 3 shown below.

[0128] In option 3-1, UE200 does not need to assume that certain conditions are met.

[0129] In option 3-2, UE200 may drop either PUCCH#1 or PUCCH#2.

[0130] In Option 3-3, UE200 may multiplex PUCCH#1 and PUCCH#2. The multiplexing method may be one related to Handling Method 1, Handling Method 4, and Handling Method 5.

[0131] In option 3-4, the UE200 may apply the behavior of options 3-1 to 3-3 based on at least one of the channel type and information type of the Unicast PUSCH / PUCCH.

[0132] (5.3) Handling Method 3 As described above, handling method 3 is a method for sending PUCCHs related to two or more NACK-only feedbacks. When handling method 3 is applied, UE200 determines, based on specific conditions, whether the MBS PUCCH overlaps in time with the Unicast PUSCH / PUCCH.

[0133] Whether handling method 3 applies may be predefined in the wireless communication network 10 and may be implicitly or explicitly specified by at least one of the RRC message, MAC CE message, and DCI. The specification may be interpreted as setting, updating, instructing, activating, deactivating, etc.

[0134] For example, consider a case where, as shown in Figure 9, two MBS pushes (PUCCH#1 and PUCCH#2 in Figure 9) related to two or more NACK-only feedbacks are scheduled during a specific period (Slot), and a Unicast push (simply called PUSCH in Figure 9) is also scheduled. Although Figure 9 illustrates a Unicast push, the second uplink channel may also use a Unicast push.

[0135] In such cases, the specific condition is determined on a slot basis. That is, the specific condition is the condition for determining whether the resources related to the Unicast PUSCH overlap with other MBS PUCCHs (NACK-only feedback) when a Unicast PUSCH is scheduled in the same slot where an MBS PUCCH (NACK-only feedback) is scheduled.

[0136] The UE200 determines how to process MBS PUCCH and Unicast PUSCH / PUCCH based on whether or not specific conditions are met.

[0137] Firstly, in Case 1, PUCCH#1 overlaps in time with PUSCH, but PUSCH, which overlaps in time with PUCCH#1, does not overlap in time with PUCCH#2. Therefore, UE200 determines that the specific condition is not met. The behavior of UE200 in the case where the specific condition is not met may be as shown below.

[0138] For example, since PUCCH#1 and PUSCH overlap in time, UE200 may implement the multiplexing method related to handling method 1 (option 2 described above). Alternatively, UE200 may use the multiplexing method related to handling method 5 described later. On the other hand, since PUCCH#2 does not overlap in time with PUSCH, UE200 may transmit PUCCH#2 as is.

[0139] Secondly, in Case 2, PUCCH#1 overlaps in time with PUSCH, and PUSCH, which overlaps in time with PUCCH#1, also overlaps in time with PUCCH#2. Therefore, UE200 determines that the specific condition is met. The operation of UE200 in the case where the specific condition is met may be option 4 shown below.

[0140] In Option 4-1, UE200 does not need to assume that certain conditions are met.

[0141] In option 4-2, UE200 may drop either PUCCH#1 or PUCCH#2.

[0142] In option 4-3, UE200 may multiplex PUCCH#1 and PUCCH#2. The multiplexing method may be the multiplexing method associated with handling method 1, handling method 4, and handling method 5.

[0143] In Option 4-4, the UE200 may apply the behavior of Options 3-1 to 3-3 based on at least one of the channel type and information type of the Unicast PUSCH / PUCCH.

[0144] (5.4) Handling Method 4 As described above, handling method 4 is a method of associating a combination of two or more NACK-only feedback (HARQ-ACK bits) with a specific sequence or specific resource related to PUCCH. When handling method 4 is applied, UE200 determines, based on specific conditions, whether or not the MBS PUCCH temporally overlaps with the Unicast PUSCH / PUCCH.

[0145] Whether handling method 4 applies may be predefined in the wireless communication network 10 and may be implicitly or explicitly specified by at least one of the RRC message, MAC CE message, and DCI. The specification may be interpreted as setting, updating, instructing, activating, deactivating, etc.

[0146] For example, as shown in Figure 10, we will explain the case in which 3 bits of HARQ-ACK are associated with the PUCCH resource. Note that, since this is a process related to NACK-only feedback, combinations where all bits are ACK ("111" in Figure 10) do not need to be associated with the PUCCH resource.

[0147] Under these circumstances, the UE200 may determine whether certain conditions are met based on the options shown below. The following example illustrates the case where PUCCH resource #2 is selected. PUSCH is also shown as an example of a second uplink channel.

[0148] In option 5-1, the specific condition may be that the Unicast PUSCH overlaps in time with all candidate PUCCH resources that could be selected as a PUCCH resource. The specific condition may be deemed satisfied if the Unicast PUSCH overlaps in time with at least some of the candidate PUCCH resources. Alternatively, the specific condition may be deemed satisfied if the Unicast PUSCH overlaps in time with all of the candidate PUCCH resources.

[0149] For example, as shown in Figure 11, for PUSCH#1 (Unicast PUSCH), since PUSCH#1 overlaps temporally with at least a portion of Resource0 to Resource6 for all of Resource0 to Resource6, UE200 determines that a specific condition is met.

[0150] In cases where certain conditions are met, the operation of UE200 may be as follows. For example, UE200 may perform a multiplexing method related to handling method 1 (option 2 described above). Alternatively, UE200 may use a multiplexing method related to handling method 5, which will be described later.

[0151] On the other hand, regarding PUSCH#2 (Unicast PUSCH), since PUSCH#2 does not overlap in time with Resource4 to Resource6, UE200 determines that the specific conditions are not met.

[0152] In cases where certain conditions are not met, i.e., where some candidate PUCCH resources and Unicast PUSCHs do not overlap in time, UE200 may behave as shown below. For example, UE200 does not need to anticipate such cases. UE200 may send an MBS PUCCH (Resource2 in Figure 11) without sending PUSCH#2.

[0153] Option 5-2 assumes that a PUCCH is treated as a virtual PUCCH (e.g., Reference PUCCH) defined based on a PUCCH resource, and the specific condition may be that the Reference PUCCH and Unicast PUCCH overlap in time. The specific condition may be deemed satisfied if at least a portion of the Reference PUCCH and the Unicast PUCCH overlap in time. Alternatively, the specific condition may be deemed satisfied if the entire Reference PUCCH and the Unicast PUCCH overlap in time.

[0154] For example, as shown in Figure 12, since at least a portion of the Reference PUCCH and the PUSCH (Unicast PUSCH) overlap in time, the UE200 determines that certain conditions are met.

[0155] In cases where certain conditions are met, the operation of UE200 may be as follows. For example, UE200 may perform a multiplexing method related to handling method 1 (option 2 described above). Alternatively, UE200 may use a multiplexing method related to handling method 5, which will be described later.

[0156] Reference PUCCH may be defined by all candidate PUCCH resources, by any candidate PUCCH resource selected from among the candidate PUCCH resources, or may be defined separately from the candidate PUCCH resources. Alternatively, it may be a PUCCH resource derived from all candidate PUCCH resources. For example, it may be a PUCCH resource of consecutive symbols, from the first symbol of the first PUCCH resource among all candidate PUCCH resources to the last symbol of the last PUCCH resource among all candidate PUCCH resources.

[0157] In option 5-3, the specific condition may be the condition that Unicast PUSCH is scheduled at the same time (e.g., slot) in which a candidate PUCCH resource is scheduled, i.e., the condition overlaps at the same time (e.g., slot). In such cases, Unicast PUSCH does not need to overlap with the candidate PUCCH resource in a given time unit (e.g., symbol).

[0158] For example, as shown in Figure 13, a Unicast PUSCH (simply referred to as PDSCH in Figure 13) does not overlap with a candidate PUCCH resource in a given time unit (e.g., symbol), but because it is scheduled at the same specific time (e.g., slot) as the candidate PUCCH resource, UE200 may determine that a specific condition is met.

[0159] In cases where certain conditions are met, the operation of UE200 may be as follows. For example, UE200 may perform a multiplexing method related to handling method 1 (option 2 described above). Alternatively, UE200 may use a multiplexing method related to handling method 5, which will be described later.

[0160] In option 5-4, the specific condition may be that at least one of the candidate PUCCH resources and the Unicast PUSCH overlap in time. In such cases, the actually selected PUCCH resource and the Unicast PUSCH do not need to overlap in time.

[0161] For example, as shown in Figure 14, the Unicast PUSCH (simply referred to as PDSCH in Figure 14) does not overlap in time with the actually selected PUCCH resource (Resource2), but it does overlap in time with other candidate PUCCH resources (Resource4 to Resource6). Therefore, UE200 determines that certain conditions are met.

[0162] In cases where certain conditions are met, the operation of UE200 may be as follows. For example, UE200 may perform a multiplexing method related to handling method 1 (option 2 described above). Alternatively, UE200 may use a multiplexing method related to handling method 5, which will be described later.

[0163] In Option 5-5, UE200 may perform the process of multiplexing the MBS PUCCH and Unicast PUSCH if it has successfully received / decoded the Group-common PDSCH and there is an opportunity to send a HARQ-ACK. In other words, even if it is not necessary to send NACK-only feedback, UE200 may determine that there is a temporal overlap between the MBS PUCCH and the Unicast PUSCH / PUCCH if certain conditions are met. Such processing may be applied to any of the above-described Options 5-1 to 5-4.

[0164] (5.5) Handling Method 5 As described above, handling method 5 is a method for bundling two or more NACK-only feedbacks (HARQ-ACK bits). When handling method 5 is applied, UE200 determines, based on specific conditions, whether or not the MBS PUCCH overlaps temporally with the Unicast PUSCH / PUCCH.

[0165] Whether handling method 5 applies may be predefined in the wireless communication network 10 and may be implicitly or explicitly specified by at least one of the RRC message, MAC CE message, and DCI. The specification may be interpreted as setting, updating, instructing, activating, deactivating, etc.

[0166] Firstly, the specific condition is to determine whether the bundled MBS PUCCH overlaps in time with the Unicast PUSCH / PUCCH, based on the MBS PUCCH after bundling two or more NACK-only feedbacks. In other words, the UE200 determines that the specific condition is met if the bundled MBS PUCCH overlaps in time with the Unicast PUSCH / PUCCH.

[0167] In cases where certain conditions are met, the operation of UE200 may be as shown below. For example, UE200 may perform a multiplexing method related to handling method 1 (option 2 described above).

[0168] Secondly, the specific condition is to determine whether at least one of the MBS PUCCHs before bundling two or more NACK-only feedbacks temporally overlaps with a Unicast PUSCH / PUCCH, based on the MBS PUCCHs before bundling. In other words, the UE200 determines that the specific condition is met if at least one of the MBS PUCCHs before bundling temporally overlaps with a Unicast PUSCH / PUCCH.

[0169] In cases where certain conditions are met, the operation of UE200 may be as shown below. For example, UE200 may perform a multiplexing method related to handling method 1 (option 2 described above).

[0170] In such cases, UE200 may perform the process of multiplexing the MBS PUCCH with the Unicast PUSCH if it has successfully received / decoded the Group-common PDSCH and has an opportunity to send a HARQ-ACK. In other words, even if it is not necessary to send NACK-only feedback, UE200 may determine that there is a temporal overlap between the MBS PUCCH and the Unicast PUSCH / PUCCH if certain conditions are met.

[0171] (6) Action and Effects In this embodiment, when the MBS PUCCH and Unicast PUSCH overlap in time, the UE200 determines how the MBS PUCCH processes the Unicast PUSCH according to the handling method for NACK-only feedback. With this configuration, the operation of the UE200 according to the handling method for NACK-only feedback is clarified, and a common understanding of the operation of the UE200 can be obtained between the gNB100 and the UE200. Therefore, the multiplexing of the MBS PUCCH and Unicast PUSCH can be operated appropriately.

[0172] In this embodiment, even if it is not necessary to send NACK-only feedback, UE200 may determine that a temporal overlap has occurred between the MBS PUCCH and the Unicast PUSCH / PUCCH if certain conditions are met. With this configuration, a common understanding of the operation of UE200 can be obtained between gNB100 and UE200 regardless of the decoding result of the Group-common PDSCH. Therefore, the multiplexing of MBS PUCCH and Unicast PUSCH can be operated appropriately.

[0173] (7) Other embodiments Although the present invention has been described above in accordance with the embodiments, it will be obvious to those skilled in the art that the present invention is not limited to these descriptions and that various modifications and improvements are possible.

[0174] Although not specifically mentioned in the disclosure above, a drop may also mean that, if there are two channels, dropping one of them will cause the other channel to transmit.

[0175] Although not specifically mentioned in the disclosure above, each of the above options may be predefined in the wireless communication network 10 and may be implicitly or explicitly specified by at least one of the RRC message, MAC CE message, and DCI. The specification may be interpreted as setting, updating, instructing, activating, deactivating, etc.

[0176] In the disclosure described above, Unicast PUSCH was primarily used as an example of a second uplink channel that temporally overlaps with MBS PUCCH. However, the disclosure is not limited to this. The second uplink channel may also be a Unicast PUCCH. Furthermore, temporal overlap of multiple channels may mean overlapping within a given time unit, for example, that at least one symbol is the same, or that they are scheduled within the same time unit (e.g., slot).

[0177] Although not specifically mentioned in the disclosure above, in MBS, PDSCH(unicast) and PDSCH(multicast) may be time-division multiplexed. PDSCH(unicast) may also be referred to as TDMed PDSCH(unicast), and PDSCH(multicast) may also be referred to as TDMed PDSCH(multicast). In MBS, frequency division multiplexing of TDMed PDSCH(unicast) and DMed PDSCH(multicast) may be supported, and frequency division multiplexing of TDMed PDSCH(multicast) may also be supported.

[0178] The block diagrams (Figures 4 and 5) used in the description of the embodiments above show functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired or wireless connections). A functional block may also be realized by combining the above one device or the above multiple devices with software.

[0179] Functions include, but are not limited to, judgment, decision, judgment, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, assumption, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission is called a transmitting unit or transmitter. In any case, as mentioned above, the method of implementation is not particularly limited.

[0180] Furthermore, the gNB100 and UE200 (the device) described above may function as a computer that processes the wireless communication method of this disclosure. Figure 15 shows an example of the hardware configuration of the device. As shown in Figure 15, the device may be configured as a computer device including a processor 1001, memory 1002, storage 1003, communication device 1004, input device 1005, output device 1006, and bus 1007.

[0181] In the following explanation, the term "device" can be replaced with "circuit," "device," "unit," etc. The hardware configuration of the device may include one or more of the devices shown in the diagram, or it may be configured to omit some of the devices.

[0182] Each functional block of the device (see Figure 4) is implemented by any hardware element of the computer device, or a combination of such hardware elements.

[0183] Furthermore, each function in the device is realized by loading predetermined software (programs) onto hardware such as the processor 1001 and memory 1002, which allows the processor 1001 to perform calculations, control communication by the communication device 1004, and control at least one of data reading and writing in the memory 1002 and storage 1003.

[0184] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may consist of a central processing unit (CPU) that includes interfaces with peripheral devices, control units, arithmetic units, registers, and so on.

[0185] Furthermore, the processor 1001 reads programs (program code), software modules, data, etc., from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. Moreover, the above-mentioned various processes may be executed by one processor 1001, or by two or more processors 1001 simultaneously or sequentially. The processor 1001 may be implemented by one or more chips. The program may also be transmitted from a network via a telecommunications line.

[0186] Memory 1002 is a computer-readable recording medium and may consist of at least one of the following: Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), Random Access Memory (RAM), etc. Memory 1002 may also be called a register, cache, main memory, etc. Memory 1002 can store a program (program code), software modules, etc., that can execute a method according to one embodiment of this disclosure.

[0187] Storage 1003 is a computer-readable recording medium and may consist of at least one of the following: an optical disc such as a Compact Disc ROM (CD-ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disc, a digital multipurpose disc, a Blu-ray® disc), a smart card, flash memory (e.g., a card, a stick, a key drive), a floppy® disk, a magnetic strip, etc. Storage 1003 may also be called an auxiliary storage device. The recording medium described above may also be, for example, a database, server, or other suitable medium including at least one of memory 1002 and storage 1003.

[0188] The communication device 1004 is hardware (transceiver / receiver device) for communicating between computers via at least one of a wired network and a wireless network, and is also called a network device, network controller, network card, communication module, etc.

[0189] The communication device 1004 may be configured to include, for example, a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc., in order to implement at least one of frequency division duplex (FDD) and time division duplex (TDD).

[0190] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, LED lamp, etc.). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel).

[0191] Furthermore, each device, such as the processor 1001 and the memory 1002, is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or different buses may be configured for each device.

[0192] Furthermore, the device may include hardware such as a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a programmable logic device (PLD), and a field-programmable gate array (FPGA), and some or all of the functional blocks may be implemented by such hardware. For example, processor 1001 may be implemented using at least one of these hardware components.

[0193] Furthermore, notification of information is not limited to the embodiments / models described herein and may be carried out by other means. For example, notification of information may be carried out by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), upper layer signaling (e.g., RRC signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB))), other signals, or combinations thereof. RRC signaling may also be called RRC messages, and may be, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc.

[0194] Each aspect / embodiment described herein may be applied to at least one of the following: Long Term Evolution (LTE), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), Future Radio Access (FRA), New Radio (NR), W-CDMA®, GSM®, CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi®), IEEE 802.16 (WiMAX®), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth®, and other appropriate systems, as well as next-generation systems extended based thereon. Furthermore, multiple systems may be applied in combination (for example, a combination of at least one of LTE and LTE-A with 5G).

[0195] The processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described herein may be reordered, provided they are consistent with each other. For example, the methods described herein present various step elements in an exemplary order and are not limited to that specific order.

[0196] The specific operations described in this disclosure as being performed by a base station may, in some cases, be performed by its upper node. In a network consisting of one or more network nodes having a base station, it is clear that various operations performed for communication with a terminal can be performed by the base station and at least one other network node (for example, an MME or S-GW, but not limited to these). Although the above example illustrates a case where there is one other network node besides the base station, it may also be a combination of multiple other network nodes (for example, an MME and an S-GW).

[0197] Information and signals (such as data) can be output from a higher layer (or lower layer) to a lower layer (or higher layer). Input and output may occur via multiple network nodes.

[0198] Input and output information may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information may be overwritten, updated, or appended to. Output information may be deleted. Input information may be sent to other devices.

[0199] The determination may be made by a value represented by 1 bit (0 or 1), by a boolean value (true or false), or by a numerical comparison (for example, a comparison with a predetermined value).

[0200] Each aspect / embodiment described herein may be used individually, in combination, or switched between as needed during implementation. Furthermore, notification of specific information (e.g., notification that "X is") is not limited to explicit notification, but may also be implicit (e.g., by not providing such notification).

[0201] Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, and so on, whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name.

[0202] Furthermore, software, instructions, information, etc., may be transmitted and received via a transmission medium. For example, if software is transmitted from a website, server, or other remote source using at least one of wired technology (such as coaxial cable, fiber optic cable, twisted pair, or Digital Subscriber Line (DSL)) and wireless technology (such as infrared or microwave), then at least one of these wired and wireless technologies is included in the definition of a transmission medium.

[0203] The information, signals, etc. described in this disclosure may be represented using any of the various different technologies. For example, the data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0204] In addition, terms used in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of the channel and symbol may be a signal (signaling). Also, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, cell, frequency carrier, etc.

[0205] The terms “system” and “network” as used in this disclosure are interchangeable.

[0206] Furthermore, the information, parameters, etc., described in this disclosure may be expressed using absolute values, relative values ​​from a given value, or other corresponding information. For example, wireless resources may be indicated by an index.

[0207] The names used for the parameters described above are not restrictive in any way. Furthermore, the formulas and other expressions using these parameters may differ from those expressly disclosed in this disclosure. Since various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, the various names assigned to these various channels and information elements are not restrictive in any way.

[0208] In this disclosure, terms such as "Base Station (BS)," "wireless base station," "fixed station," "NodeB," "eNodeB (eNB)," "gNodeB (gNB)," "access point," "transmission point," "reception point," "transmission / reception point," "cell," "sector," "cell group," "carrier," and "component carrier" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0209] A base station can house one or more (e.g., three) cells (also called sectors). When a base station houses multiple cells, the entire coverage area of ​​the base station can be divided into multiple smaller areas, each of which can also be provided with communication services by a base station subsystem (e.g., a small indoor base station (Remote Radio Head: RRH)).

[0210] The terms "cell" or "sector" refer to a portion or all of the coverage area of ​​at least one of the base stations and base station subsystems that provide communication services in this coverage.

[0211] In this disclosure, terms such as "Mobile Station (MS)," "user terminal," "User Equipment (UE)," and "terminal" may be used interchangeably.

[0212] A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or several other appropriate terms.

[0213] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile body, the mobile body itself, etc. The mobile body may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does not necessarily move during communication operation. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

[0214] Furthermore, the term "base station" in this disclosure may be interpreted as "mobile station" (user terminal, hereinafter the same). For example, each aspect / embodiment of this disclosure may be applied to a configuration in which communication between a base station and a mobile station is replaced with communication between multiple mobile stations (which may be called, for example, Device-to-Device (D2D), Vehicle-to-Everything (V2X), etc.). In this case, the mobile station may have the functions that a base station has. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, uplink channel, downlink channel, etc. may be interpreted as side channel.

[0215] Similarly, the term "mobile station" in this disclosure may be interpreted as "base station." In this case, the base station may be configured to have the functions that a mobile station has.

[0216] A wireless frame may consist of one or more frames in the time domain. Each of these frames in the time domain may be called a subframe.

[0217] A subframe may further consist of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0218] Numerology may be communication parameters applied to at least one of the transmission and reception of a signal or channel. Numerology may include, for example, at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, specific filtering processes performed by the transceiver in the frequency domain, and specific windowing processes performed by the transceiver in the time domain.

[0219] A slot may consist of one or more symbols in the time domain (such as Orthogonal Frequency Division Multiplexing (OFDM) symbols or Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols). A slot may also be a time unit based on neurology.

[0220] A slot may include multiple minislots. Each minislot may consist of one or more symbols in the time domain. Minislots may also be called subslots. Minislots may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (or PUSCH) mapping type B.

[0221] Wireless frames, subframes, slots, minislots, and symbols all represent units of time when transmitting a signal. Different names may be used for each of these terms.

[0222] For example, one subframe may be called a transmission time interval (TTI), multiple consecutive subframes may be called a TTI, or one slot or one minislot may be called a TTI. In other words, at least one of a subframe and a TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (e.g., 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc., instead of a subframe.

[0223] Here, TTI refers to, for example, the smallest unit of time for scheduling in wireless communication. For example, in an LTE system, the base station schedules each user terminal to allocate wireless resources (such as the frequency bandwidth and transmission power available to each user terminal) in TTI units. However, the definition of TTI is not limited to this.

[0224] TTI may be a transmission time unit for channel-encoded data packets (transport blocks), code blocks, code words, etc., or it may be a processing unit for scheduling, link adaptation, etc. Given a TTI, the actual time interval (e.g., number of symbols) to which the transport block, code block, code word, etc. are mapped may be shorter than the given TTI.

[0225] Furthermore, if one slot or one mini-slot is referred to as TTI, then one or more TTIs (i.e., one or more slots or one or more mini-slots) may constitute the minimum time unit of scheduling. In addition, the number of slots (number of mini-slots) that constitute the minimum time unit of scheduling may be controlled.

[0226] A TTI with a time length of 1ms may also be called a normal TTI, long TTI, normal subframe, long subframe, slot, etc. A TTI shorter than a normal TTI may also be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, mini slot, sub slot, slot, etc.

[0227] Furthermore, long TTIs (e.g., normal TTIs, subframes, etc.) may be interpreted as TTIs with a time length exceeding 1 ms, and short TTIs (e.g., shortened TTIs, etc.) may be interpreted as TTIs with a TTI length less than that of a long TTI but 1 ms or more.

[0228] A resource block (RB) is a resource allocation unit in the time domain and frequency domain, and in the frequency domain, it may contain one or more consecutive subcarriers. The number of subcarriers in an RB may be the same regardless of the neurology, for example, 12. The number of subcarriers in an RB may be determined based on the neurology.

[0229] Furthermore, the time domain of RB may contain one or more symbols and may be the length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc., may each consist of one or more resource blocks.

[0230] One or more RBs may also be called Physical RBs (PRBs), Sub-Carrier Groups (SCGs), Resource Element Groups (REGs), PRB pairs, RB pairs, etc.

[0231] Furthermore, a resource block may consist of one or more resource elements (REs). For example, one RE may be a radio resource area comprising one subcarrier and one symbol.

[0232] A Bandwidth Part (BWP), also known as a partial bandwidth, may represent a subset of consecutive common resource blocks (RBs) for a given neurology on a given carrier. Here, the common RBs may be identified by an index of the RBs relative to the carrier's common reference point. PRBs may be defined and numbered within a BWP.

[0233] A BWP may include BWPs for UL (UL BWP) and BWPs for DL ​​(DL BWP). One or more BWPs may be configured within a single carrier for a UE.

[0234] At least one of the configured BWPs may be active, and the UE does not need to assume that it will send or receive a given signal / channel outside of the active BWP. In this disclosure, terms such as "cell" and "carrier" may be read as "BWP".

[0235] The structures described above, such as wireless frames, subframes, slots, minislots, and symbols, are merely illustrative. For example, the number of subframes included in a wireless frame, the number of slots per subframe or wireless frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, and the number of symbols, symbol length, and cyclic prefix (CP) length within a TTI can be varied in various ways.

[0236] The terms “connected,” “coupled,” or any variation thereof, mean any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are “connected” or “coupled” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be reinterpreted as “access.” As used in this disclosure, two elements may be considered to be “connected” or “coupled” with each other using at least one of one or more wires, cables, and printed electrical connections, and, in some non-limiting and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, and optical (both visible and invisible) domain.

[0237] The reference signal can also be abbreviated as Reference Signal (RS), and may be called a pilot depending on the applicable standard.

[0238] In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on."

[0239] In the configuration of each of the above devices, "means" may be replaced with "part," "circuit," "device," etc.

[0240] Any reference to elements using designations such as “First,” “Second,” etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, references to the First and Second elements do not imply that only two elements may be employed therein, or that the First element must precede the Second element in any way.

[0241] Where the terms “include,” “including,” and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to mean exclusive OR.

[0242] In this disclosure, if articles are added through translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural.

[0243] As used in this disclosure, the terms “determining” and “determining” may encompass a wide variety of actions. “Determining” may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiry (e.g., searching in a table, database, or other data structure), and ascertaining. “Determining” may also include, for example, receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, and accessing (e.g., accessing data in memory). Furthermore, "judgment" and "decision" can include considering something as having been "judged" or "decided" after resolving, selecting, choosing, establishing, comparing, etc. In other words, "judgment" and "decision" can include considering something as having been "judged" or "decided" after some action. Also, "judgment (decision)" can be reinterpreted as "assuming," "expecting," or "considering."

[0244] In this disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "combine" may be interpreted similarly to "different."

[0245] Figure 16 shows an example of the configuration of vehicle 2001. As shown in Figure 16, vehicle 2001 comprises a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021 to 2029, an information service unit 2012, and a communication module 2013.

[0246] The drive unit 2002 is composed of, for example, an engine, a motor, or a hybrid of an engine and a motor.

[0247] The steering unit 2003 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel performed by the user.

[0248] The electronic control unit 2010 consists of a microprocessor 2031, memory (ROM, RAM) 2032, and communication ports (IO ports) 2033. Signals from various sensors 2021 to 2027 installed in the vehicle are input to the electronic control unit 2010. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

[0249] Signals from various sensors 2021-2028 include current signals from the current sensor 2021 that senses motor current, front and rear wheel rotation speed signals obtained by the rotation speed sensor 2022, front and rear wheel air pressure signals obtained by the air pressure sensor 2023, vehicle speed signals obtained by the vehicle speed sensor 2024, acceleration signals obtained by the acceleration sensor 2025, accelerator pedal depression signals obtained by the accelerator pedal sensor 2029, brake pedal depression signals obtained by the brake pedal sensor 2026, shift lever operation signals obtained by the shift lever sensor 2027, and detection signals obtained by the object detection sensor 2028 for detecting obstacles, vehicles, pedestrians, etc.

[0250] The Information Services Unit 2012 consists of various devices for providing various types of information, such as driving information, traffic information, and entertainment information, including a car navigation system, audio system, speakers, television, and radio, and one or more ECUs that control these devices. The Information Services Unit 2012 uses information acquired from external devices via a communication module 2013, etc., to provide various multimedia information and multimedia services to the occupants of Vehicle 1.

[0251] The driver assistance system unit 2030 consists of various devices that provide functions to prevent accidents or reduce the driver's workload, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System)), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. The driver assistance system unit 2030 also sends and receives various information via the communication module 2013 to realize driver assistance functions or autonomous driving functions.

[0252] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 1 via its communication port. For example, the communication module 2013 sends and receives data via its communication port 2033 between the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, axle 2009, the microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021 to 2028 provided in the vehicle 2001.

[0253] The communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with external devices. For example, it can send and receive various types of information to and from external devices via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station or a mobile station.

[0254] The communication module 2013 transmits current signals from current sensors input to the electronic control unit 2010 to an external device via wireless communication. The communication module 2013 also transmits, via wireless communication, other signals input to the electronic control unit 2010, including front and rear wheel rotation speed signals obtained by the rotation speed sensor 2022, front and rear wheel air pressure signals obtained by the air pressure sensor 2023, vehicle speed signals obtained by the vehicle speed sensor 2024, acceleration signals obtained by the acceleration sensor 2025, accelerator pedal depression signals obtained by the accelerator pedal sensor 2029, brake pedal depression signals obtained by the brake pedal sensor 2026, shift lever operation signals obtained by the shift lever sensor 2027, and detection signals obtained by the object detection sensor 2028 for detecting obstacles, vehicles, pedestrians, etc.

[0255] The communication module 2013 receives various information (traffic information, signal information, distance information, etc.) transmitted from external devices and displays it on the information service unit 2012 installed in the vehicle. The communication module 2013 also stores the various information received from external devices in memory 2032, which is available to the microprocessor 2031. Based on the information stored in memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, axles 2009, sensors 2021-2028, etc., installed in the vehicle 2001.

[0256] Although the present disclosure has been described in detail above, it will be clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the intent and scope of the present disclosure as defined by the claims. Therefore, the descriptions in the present disclosure are illustrative and not intended to be restrictive in any way. [Explanation of symbols]

[0257] 10 Wireless communication systems 20 NG-RAN 100 gNB 110 Receiving unit 120 Transmitter 130 Control Unit 200 UE 210 Wireless signal transmission and reception unit 220 Amplifier section 230 Modulation / Demodulation Section 240 Control signal / reference signal processing unit 250 Encoding / Decoding Unit 260 Data transmission / reception unit 270 Control Unit 1001 Processor 1002 memory 1003 Storage 1004 Communication device 1005 Input device 1006 Output device 1007 Bus 2001 Vehicle 2002 Drive Unit 2003 Steering Department 2004 Accelerator pedal 2005 Brake pedal 2006 Shift Lever 2007 Left and right front wheels 2008 Left and right rear wheels 2009 Axle 2010 Electronic Control Unit 2012 Information Services Department 2013 Communication Module 2021 Current Sensor 2022 Rotation Speed Sensor 2023 Air Pressure Sensor 2024 Vehicle Speed Sensor 2025 Acceleration Sensor 2026 Brake Pedal Sensor 2027 Shift Lever Sensor 2028 Object Detection Sensor 2029 Accelerator Pedal Sensor 2030 Driving Assistance System Unit 2031 Microprocessor 2032 Memory (ROM, RAM) 2033 Communication Port

Claims

1. A transmission unit that transmits feedback on the data in data distribution to multiple terminals, A control unit that controls the feedback, Equipped with, The feedback is provided by a first feedback method that sends a negative response without sending an affirmative response, or a second feedback method that sends both the affirmative response and the negative response. When the control unit applies a method for associating the information of the first feedback method with a specific resource of the first uplink channel, if the specific resource overlaps in time with a second uplink channel that is different from the first uplink channel, the control unit feeds back the information of the first feedback method using the second feedback method. The control unit determines that, when the specific resource temporally overlaps with the second uplink channel which is different from the first uplink channel, there is no need to transmit feedback to which the first feedback method is applied, and that there is a temporal overlap between the information of the first feedback method and the second uplink channel which is different from the first uplink channel, in the terminal.

2. The terminal according to claim 1, wherein the control unit applies the method upon receiving a designation from signaling of a higher layer.

3. A transmission step that transmits feedback on the data in data distribution to multiple terminals, The system includes a control step for controlling the feedback, The feedback is provided by a first feedback method that sends a negative response without sending an affirmative response, or a second feedback method that sends both the affirmative response and the negative response. When applying the method of associating the information of the first feedback method with a specific resource of the first uplink channel, if the specific resource overlaps in time with a second uplink channel different from the first uplink channel, the information of the first feedback method is fed back using the second feedback method. A wireless communication method for a terminal, which determines that there is a temporal overlap between the information of the first feedback method and the second uplink channel, which is different from the first uplink channel, even when it is not necessary to transmit feedback to which the first feedback method is applied when the specified resource temporally overlaps with the second uplink channel, which is different from the first uplink channel.

4. In a communication system consisting of a base station and multiple terminals, The aforementioned base station is It is equipped with a transmission unit that transmits data for data distribution to multiple terminals, The aforementioned terminal is A transmission unit that transmits feedback for the aforementioned data, The system includes a control unit that controls the feedback, The feedback is provided by a first feedback method that sends a negative response without sending an affirmative response, or a second feedback method that sends both the affirmative response and the negative response. When the control unit applies a method for associating the information of the first feedback method with a specific resource of the first uplink channel, if the specific resource overlaps in time with a second uplink channel that is different from the first uplink channel, the control unit feeds back the information of the first feedback method using the second feedback method. The control unit determines that, when the specific resource temporally overlaps with the second uplink channel which is different from the first uplink channel, there is no need to transmit feedback using the first feedback method, even if there is no need to transmit feedback using the first feedback method. Communication system.

Images