Terminals and wireless communication methods

Abstract

To provide a terminal and a radio communication method with which it is possible to efficiently and reliably execute an operation along with a preset scheduling in a simultaneous data transmission service to a plurality of specified or unspecified terminals.SOLUTION: In a data distribution intended for a plurality of terminals, the terminals receive a downlink data channel that is common to terminal groups. It is assumed that the terminal groups of the terminals are divided in a plurality of subgroups, and a preset scheduling of the downlink data channel is applied in units of the subgroups.SELECTED DRAWING: Figure 6

Description

[Technical Field]

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

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

[0003] In 3GPP Release 17, the targeted subject is a simultaneous data transmission (also referred to as distribution) service (referred to as MBS: Multicast and Broadcast Services (provisional name)) to a plurality of specific or unspecific terminals (User Equipment, UE) in NR (Non-Patent Document 1).

[0004] In MBS, for example, studies are being promoted on scheduling of UE groups targeted by the service, and improvement of reliability (for example, feedback of HARQ (Hybrid Automatic repeat request) to a radio base station (gNB)). [Prior Art Documents] [Non-Patent Documents]

[0005] [Non-Patent Document 1] "New Work Item on NR support of Multicast and Broadcast Services", RP-193248, 3GPP TSG RAN Meeting #86, 3GPP, December 2019 [Summary of Invention]

[0006] In MBS, UEs need to efficiently and reliably perform actions related to the activation / deactivation of the semi-permanent scheduling (SPS) of the downlink data channel common to the UE group, specifically the PDSCH (Physical Downlink Shared Channel).

[0007] Furthermore, confirmation of the activation / deactivation of the scheduling must also be reliably performed.

[0008] Therefore, the following disclosure is made in light of these circumstances and aims to provide a terminal and wireless communication method that can efficiently and reliably perform operations associated with semi-fixed scheduling in a simultaneous data transmission service to multiple specific or unspecified terminals.

[0009] One aspect of the present disclosure is a terminal (UE200) comprising a receiving unit (wireless signal transmitting / receiving unit 210) that receives a downlink data channel common to a group of terminals in data distribution to multiple terminals, and a control unit (control unit 270) that assumes the terminal group is divided into a plurality of subgroups, and that the activation or deactivation of the semi-fixed scheduling of the downlink data channel is applied on a subgroup basis.

[0010] One aspect of this disclosure is a terminal (UE200) that, in data distribution to multiple terminals, includes a receiving unit (wireless signal transmitting / receiving unit 210) that receives a downlink data channel common to a group of terminals, and a control unit (control unit 270) that assumes that feedback of automatic retransmission requests in the downlink data channel is transmitted in different time domains for each terminal.

[0011] One aspect of the present disclosure is a terminal (UE200) that, in data distribution to multiple terminals, includes a receiving unit (wireless signal transmitting / receiving unit 210) that receives a downlink data channel common to a group of terminals, and a control unit (control unit 270) that applies both acknowledgment and negation as feedback for automatic retransmission requests in response to the activation or deactivation of the semi-fixed scheduling of the downlink data channel.

[0012] One aspect of the present disclosure is a terminal (UE200) that, in data distribution to multiple terminals, includes a receiving unit (wireless signal transmitting / receiving unit 210) that receives a downlink data channel common to a group of terminals, and a control unit (control unit 270) that controls the activation or deactivation of the semi-fixed scheduling of the downlink data channel based on a signaling common to the group of terminals or a signaling specific to the terminal.

[0013] One aspect of the present disclosure is a wireless communication method for data distribution to multiple terminals, comprising the steps of: receiving a downlink data channel common to a group of terminals; and assuming that the group of terminals is divided into a plurality of subgroups, and that the activation or deactivation of a semi-fixed scheduling of the downlink data channel is applied on a subgroup basis.

[0014] One aspect of the present disclosure is a wireless communication method for data distribution to multiple terminals, which includes the steps of receiving a downlink data channel common to a group of terminals, and assuming that feedback of an automatic retransmission request in the downlink data channel is transmitted in a different time domain for each terminal. [Brief explanation of the drawing]

[0015] [Figure 1] Figure 1 is a schematic diagram of the overall configuration of the wireless communication system 10. [Figure 2] Figure 2 shows an example of the configuration of wireless frames, subframes, and slots used in the wireless communication system 10. [Figure 3] FIG. 3 is a diagram illustrating a configuration example of PTM transmission scheme 1 and PTM transmission scheme 2. [Figure 4] FIG. 4 is a functional block configuration diagram of the gNB 100 and the UE 200. [Figure 5] FIG. 5 is a diagram illustrating a sequence example of PDCCH, PDSCH and HARQ feedback provided with an SPS scheme in MBS. [Figure 6] FIG. 6 is a diagram illustrating a configuration example of terminal groups and subgroups according to Operation Example 1. [Figure 7] FIG. 7 is a diagram illustrating an instruction example of HARQ feedback according to Operation Example 2. [Figure 8] FIG. 8 is a diagram illustrating a sequence example of PDCCH, PDSCH and HARQ feedback according to Operation Example 3. [Figure 9] FIG. 9 is a diagram illustrating an example of the hardware configuration of the gNB 100 and the UE 200. DESCRIPTION OF EMBODIMENTS

[0016] Hereinafter, embodiments will be described with reference to the drawings. Note that identical or similar reference numerals are given to identical functions and configurations, and descriptions thereof will be omitted as appropriate.

[0017] (1) Overall schematic configuration of a wireless communication system (1.1) System configuration example FIG. 1 is an overall schematic configuration diagram of a wireless communication system 10 according to the present embodiment. The wireless communication system 10 is a wireless communication system conforming to 5G New Radio (NR), and includes a Next Generation-Radio Access Network 20 (hereinafter, NG-RAN 20) and a plurality of terminals 200 (User Equipment 200, hereinafter, UE 200).

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

[0019] NG-RAN 20 includes a radio base station 100 (hereinafter, gNB 100). Note that the specific configuration of the radio communication system 10 including the number of gNBs and UEs is not limited to the example shown in FIG. 1.

[0020] NG-RAN 20 actually includes a plurality of NG-RAN Nodes, specifically, gNBs (or ng-eNBs), and is connected to a 5G-compliant core network (5GC, not shown). Note that NG-RAN 20 and 5GC may be simply referred to as a "network".

[0021] gNB 100 is an NR-compliant radio base station, and performs NR-compliant radio communication with UE 200. gNB 100 and UE 200 can support Massive MIMO, which generates beams BM with higher directivity by controlling radio signals transmitted from a plurality of antenna elements, Carrier Aggregation (CA) which uses a plurality of component carriers (CCs) in an aggregated manner, and Dual Connectivity (DC) which performs simultaneous communication between a UE and each of a plurality of NG-RAN Nodes, etc.

[0022] The radio communication system 10 supports FR1 and FR2. The frequency bands of each Frequency Range (FR) are as follows.

[0023] • 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 is used, and a bandwidth (BW) of 5 to 100 MHz may be used. FR2 is a higher frequency band than FR1, an SCS of 60 or 120 kHz (which may include 240 kHz) is used, and a bandwidth (BW) of 50 to 400 MHz may be used.

[0024] Furthermore, the wireless communication system 10 may also support higher frequency bands than the FR2 frequency band. Specifically, the wireless communication system 10 may support frequency bands exceeding 52.6 GHz and up to 114.25 GHz. In addition, the wireless communication system 10 may support frequency bands between FR1 and FR2.

[0025] Alternatively, 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. Furthermore, DFT-S-OFDM may be applied not only to the uplink (UL) but also to the downlink (DL).

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

[0027] As shown in Figure 2, one slot consists of 14 symbols, and the larger (wider) the SCS, the shorter the symbol duration (and slot duration). Note that the number of symbols constituting one slot does not necessarily have to be 14 (for example, 28 or 56 symbols). Also, the number of slots per subframe may differ depending on the SCS. Furthermore, the SCS may be wider than 240 kHz (for example, 480 kHz or 960 kHz, as shown in Figure 2).

[0028] The time direction (t) shown in Figure 2 may also be called the time domain, symbol period, or symbol time. The frequency direction may also be called the frequency domain, resource block, resource block group, subcarrier, BWP (Bandwidth part), subchannel, common frequency resource, etc.

[0029] (1.2) Provided by MBS The wireless communication system 10 may provide multicast and broadcast services (MBS).

[0030] 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.

[0031] 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.

[0032] 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.

[0033] 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.

[0034] 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.

[0035] In MBS, three methods are envisioned for scheduling multicast / broadcast PDSCH (Physical Downlink Shared Channel), 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.

[0036] ·PTM transmission method 1: • For the MBS group of the RRC-connected UE, a group-common PDSCH (Physical Downlink Control Channel) is scheduled using the group-common PDCCH.

[0037] • The CRC and PDSCH of PDCCH are scrambled using the group-common RNTI (Radio Network Temporary Identifier).

[0038] ·PTM transmission method 2: • For the MBS group of an RRC-connected UE, a group-common PDSCH is scheduled using a terminal-specific PDCCH.

[0039] • CRCs in PDCCH are scrambled using UE-specific RNTIs.

[0040] PDSCH is scrambled by group-common RNTI.

[0041] ·PTP transmission method: • For RRC-connected UEs, schedule UE-specific PDSCHs using UE-specific PDCCHs.

[0042] The CRC and PDSCH of PDCCH are scrambled by a UE-specific RNTI. This means that MBS packets are transmitted via unicast.

[0043] Figure 3 shows example configurations for PTM transmission methods 1 and 2. Note that UE-specific PDCCH / PDSCH can be identified by the target UE, but do not need to be identifiable by other UEs within the same MBS group. Group-common PDCCH / PDSCH are transmitted using the same time / frequency resources and are identifiable 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.

[0044] 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.

[0045] 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.

[0046] 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 via unicast or 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.

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

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

[0049] • 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 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."

[0050] 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).

[0051] 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.

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

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

[0054] 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.

[0055] (2) Functional block configuration of the wireless communication system Next, the functional block configuration of the wireless communication system 10 will be described. Specifically, the functional block configurations of gNB100 and UE200 will be described.

[0056] Figure 4 is a functional block diagram of the gNB100 and UE200. The UE200 will be described below. 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.

[0057] Note that Figure 4 only shows the main functional blocks relevant to the description of the embodiment, and the UE200 has other functional blocks (e.g., a power supply unit). Also, Figure 4 shows the functional block configuration of the UE200 (gNB100), but please refer to Figure 9 for the hardware configuration.

[0058] 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.

[0059] Furthermore, the wireless signal transceiver 210 is compatible with MBS and can receive downlink channels that are common to the terminal group (group common) when distributing data to multiple UE200s. In this embodiment, the wireless signal transceiver 210 may constitute a receiving unit.

[0060] The wireless signal transceiver 210 can receive a common downlink data channel (PDSCH) for the terminal group, specifically a group-common PDSCH (which may include an SPS group-common PDSCH). The wireless signal transceiver 210 can also receive a common downlink control channel for the terminal group, specifically a group-common PDCCH.

[0061] 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.

[0062] The modulation / demodulation unit 230 performs data modulation / demodulation, transmit power setting, and resource block allocation for each predetermined communication destination (such as gNB100). 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).

[0063] 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.

[0064] 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.

[0065] 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).

[0066] 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.

[0067] 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.

[0068] Furthermore, channels include control channels and data channels. Control channels may include PDCCH, 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.

[0069] Data channels also include PDSCH and PUSCH (Physical Uplink Shared Channel). "Data" can refer to data transmitted through a data channel.

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

[0071] 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.

[0072] 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 Hybrid ARQ (Hybrid automatic repeat request).

[0073] The control unit 270 controls each functional block that constitutes the UE200. In particular, in this embodiment, the control unit 270 performs scheduling of downlink channels related to the MBS and control related to HARQ feedback for those channels.

[0074] The control unit 270 performs control corresponding to the scheduling of the downlink data channel, which is common to the terminal group, in MBS, that is, in data distribution to multiple UE200s. Specifically, the control unit 270 can perform control corresponding to the scheduling of group-common PDCCH and group-common PDSCH.

[0075] The control unit 270 may assume that, with respect to the SPS group-common PDSCH, the terminal group is divided into multiple subgroups, and that the SPS for the downlink data channel (PDSCH) for that terminal group, i.e., the activation / deactivation of semi-fixed scheduling, is applied to each subgroup.

[0076] The control unit 270 may assume that feedback for automatic retransmission requests (HARQs) in the downlink data channel, specifically feedback for automatic retransmission requests (HARQs) in response to the activation or deactivation of the semi-fixed scheduling of the downlink data channel, is transmitted in different time domains for each UE200.

[0077] Specifically, the control unit 270 may assume that the slots used for HARQ feedback for activation / deactivation of the SPS group-common PDSCH (see Figure 2) are different for each UE200. Note that the slots may be changed to other units in the time domain, such as subslots, subframes, or symbols.

[0078] The control unit 270 may apply both acknowledgment (ACK) and negation (NACK) as feedback for automatic retransmission requests (HARQ) in response to the activation or deactivation of semi-fixed scheduling (SPS) of the downlink data channel (PDSCH).

[0079] Specifically, the control unit 270 may use both ACK and NACK for HARQ feedback only for the activation / deactivation of the SPS group-common PDSCH. On the other hand, for HARQ feedback to an SPS group-common PDSCH without a PDCCH, the control unit 270 may use NACK only.

[0080] Alternatively, the control unit 270 may always use both ACK and NACK for the HARQ feedback for the activation / deactivation of the SPS group-common PDSCH and the SPS group-common PDSCH.

[0081] Furthermore, the control unit 270 may set the HARQ feedback for the activation / deactivation of the SPS group-common PDSCH to NACK-only.

[0082] The control unit 270 may perform activation / deactivation of the SPS group-common PDSCH at a layer higher than the physical (PHY) layer. For example, the control unit 270 may perform activation / deactivation at the MAC or RRC layer.

[0083] Furthermore, the control unit 270 may perform confirmation of the activation / deactivation of the SPS group-common PDSCH at a layer higher than the physical (PHY) layer. For example, the control unit 270 may perform confirmation at the MAC layer.

[0084] The control unit 270 may control the activation or deactivation of semi-fixed scheduling (SPS) for downlink data channels based on group common signaling or UE-specific signaling.

[0085] Specifically, the control unit 270 may assume that the activation / deactivation of the SPS group-common PDSCH is performed by both group common signaling and UE-specific signaling. Alternatively, the control unit 270 may assume that the activation / deactivation is performed by at least one of group common signaling and UE-specific signaling.

[0086] Furthermore, the gNB100 can perform the downlink channel scheduling and HARQ-related control described above.

[0087] (3) Operation of the wireless communication system Next, the operation of the wireless communication system 10 will be described. Specifically, the operation of downlink channel scheduling and HARQ feedback for the MBS will be described.

[0088] In MBS, scheduling of group-common PDSCHs is possible using group-common PDCCHs (see Figure 3), but as mentioned above, SPS activation / deactivation may be applied to group-common PDSCHs (such group-common PDSCHs may be conveniently called SPS group-common PDSCHs).

[0089] In such cases, it is necessary to consider methods for confirming activation / deactivation.

[0090] Figure 5 shows example sequences of PDCCH, PDSCH, and HARQ feedback that provided the SPS scheme in MBS.

[0091] In 3GPP Release-15 (Unicast SPS), HARQ feedback can have the meaning of confirmation, but applying such a scheme to MBS and ensuring that ACK / NACK is always fed back is only feasible if a large amount of PUCCH resources are available.

[0092] On the other hand, if only NACK feedback is used, the gNB cannot determine which UE (Underground User) is responsible for the misdetection. Therefore, how to send HARQ ACK / NACK can become a challenge.

[0093] The following describes an example of efficient operation of group-common PDSCH regarding SPS, taking these challenges into consideration.

[0094] (3.1) Example of operation 1 In this example, the terminal group (UE group) that serves as the destination for the SPS group-common PDSCH is divided into multiple subgroups. SPS activation / deactivation may be performed on a per-subgroup basis.

[0095] Figure 6 shows an example configuration of terminal groups and subgroups related to Operation Example 1. As shown in Figure 6, a terminal group (UE Group of SPS group-common PDSCH) may be divided into multiple subgroups. The number of subgroups and the number of UEs included in each subgroup are not particularly limited. As shown in Figure 6, SPS activation / deactivation (release) may be performed on a subgroup basis. UE200 may assume such SPS activation / deactivation for each subgroup.

[0096] The SPS group-common PDSCH on which activation / deactivation (release) is performed may be the SPS group-common PDSCH for the terminal group (i.e., the terminal group before it is divided into subgroups), or it may be the Group-common PDCCH / PDSCH related to the G-RNTI.

[0097] Subgroups may be defined in association with a specific G (Group)-RNTI. A G-RNTI is an RNTI associated with a terminal group and may be called by a different name. Alternatively, an RNTI generated based on a specific G-RNTI (for example, which may be called a sub-G-RNTI) may be used, but the name is not limited to this. A G-RNTI may be any RNTI relating to a Group-common PDCCH / PDSCH (the same applies hereafter).

[0098] G-RNTI may be used for MBS group-common PDCCH CRC scrambling and / or PDSCH data scrambling. G-RNTI may be configured by control information from a higher layer (e.g., RRC).

[0099] HARQ feedback for activation / deactivation of SPS at the subgroup level may use ACK / NACK feedback. In this case, a dedicated PUCCH resource may be set up for activation / deactivation at the subgroup level.

[0100] SPS activation at the subgroup level does not necessarily require PDSCH reception. In this case, the HARQ feedback slot may be determined based on the timing of subgroup-level activation reception.

[0101] According to this example, activation / deactivation is performed in smaller subgroup units rather than terminal groups, thus reducing the amount of PUCCH resources used at one time. This allows for more reliable and easier detection of activation / deactivation failures. On the other hand, sending group-common PDSCH messages in larger terminal group units reduces the number of PDSCH transmissions compared to performing them in subgroup units.

[0102] (3.2) Example of operation 2 In this example, the slot that provides HARQ feedback for the activation / deactivation of the SPS group-common PDSCH may differ for each UE.

[0103] Specifically, in the PDCCH used for activation / deactivation of the SPS group-common PDSCH, a separate slot offset (i.e., a time-domain offset from the PDSCH (or PDCCH) to the PUCCH) may be notified for each UE.

[0104] More specifically, in the DCI format related to the activation / deactivation of the SPS group-common PDSCH, fields related to HARQ feedback may be specified or set.

[0105] The DCI containing the field may be scrambled by G-RNTI or by RNTI generated based on G-RNTI. The field may also be a PDSCH-to-HARQ_feedback timing indicator field (as defined in 3GPP TS38.213) or a HARQ feedback timing indicator field.

[0106] The number of such fields may be set by control information from a higher layer. Alternatively, a separate field may be defined or set for each UE, and the UE may determine the HARQ feedback slot based on the field associated with that UE. In this case, which of the multiple fields (e.g., which field) is used for timing indication of the UE's HARQ feedback may be set by a higher layer or determined according to a predetermined rule (for example, C (cell)-RNTI may be the field number obtained by modulo the number of such fields). Of the multiple fields, the values ​​of the fields not associated with the UE may be ignored (and not used to determine the timing of HARQ feedback).

[0107] Figure 7 shows an example of HARQ feedback instructions related to Operation Example 2. As shown in Figure 7, the DCI field may contain multiple HARQ feedback timing indicators. Here, we show an example in which a specific UE is instructed to determine the HARQ feedback timing according to the field of the second HARQ feedback timing indicator (#2).

[0108] The above behavior may be applied to multiple UEs instead of one UE per UE. For example, if subgroups of UEs are defined, a separate field may be specified or set for each subgroup, and the UE may determine the HARQ feedback slot based on the field associated with that UE. In this case as well, as described above, which (e.g., which) field is used for timing indication of the HARQ feedback for that UE may be set by a higher layer or determined according to a predetermined rule. Furthermore, the values ​​of fields among these multiple fields that are not associated with that UE may be ignored (see Figure 7).

[0109] Additionally, a time-domain offset (which may also be called a time offset) may be set for HARQ feedback for the activation / deactivation of the SPS group-common PDSCH. The time offset may be, but is not limited to, an offset of slots from the PDSCH (or PDCCH) to the PUCCH, and may be in units of subslots, subframes, frames, or symbols, as described above.

[0110] The slot offset included in the PDCCH related to the activation / deactivation of the SPS group-common PDSCH may not be used for the HARQ feedback. In other words, except for the activation / deactivation of the SPS group-common PDSCH, it may or may not be used for HARQ feedback transmission in response to SPS group-common PDSCH reception.

[0111] Furthermore, multiple slot offset values ​​may be set for each UE, and the fields included in the PDCCH related to activation / deactivation of the SPS group-common PDSCH may specify an identifier (index) associated with the slot offset. In other words, even with DCI format 1_0, a slot offset may be set for each UE and associated with an index, and the DCI may indicate that index.

[0112] Alternatively, the HARQ feedback timing may be determined by adding or subtracting a time offset (slot, subslot, subframe, frame, or symbol number) set by the upper layer to the slot (which may also be a subslot, subframe, frame, or symbol) number of the HARQ feedback timing indicated using at least one field related to HARQ feedback. If no time offset is set, the HARQ feedback timing may be determined as time offset=0.

[0113] This example may be applied not only to the activation / deactivation of SPS group-common PDSCHs, but also to HARQ feedback for any group-common PDCCH. For example, if only DCI format 1_0 is used in the MBS, at least one time offset for HARQ feedback may be set, for example, at a higher layer, and one of the indices associated with the set time offset may be indicated by the DCI. In this case, the flexibility of resource allocation for HARQ feedback for group-common PDCCHs is improved.

[0114] (3.3) Example of operation 3 In this example, HARQ feedback for activation / deactivation of an SPS group-common PDSCH is always ACK / NACK feedback, while HARQ feedback for an SPS group-common PDSCH without a PDCCH (i.e., an SPS group-common PDSCH that does not correspond to activation / deactivation) may be performed using NACK-only.

[0115] Figure 8 shows an example sequence of PDCCH, PDSCH, and HARQ feedback related to Operation Example 3. As shown on the left side of Figure 8, only for HARQ feedback for activation / deactivation of an SPS group-common PDSCH accompanied by a PDCCH, both ACK and NACK may be sent. On the other hand, as shown on the right side of Figure 8, for HARQ feedback to an SPS group-common PDSCH without a PDCCH, only NACK may be sent.

[0116] In other words, even in an SPS group-common PDSCH where NACK-only feedback is set or instructed, HARQ feedback for activation / deactivation may be performed by ACK / NACK feedback.

[0117] In this case, a dedicated PUCCH resource may be configured for ACK / NACK feedback for activation / deactivation.

[0118] Furthermore, if only a PUCCH resource / resource set related to NACK-only feedback is configured for HARQ feedback to group-common PDSCH, one of the following may be executed:

[0119] The UE may determine the PUCCH resources for ACK / NACK feedback based on the PUCCH resource / resource set related to NACK-only feedback, and perform ACK / NACK feedback for activation / deactivation.

[0120] For example, if PUCCH Format (PF) is 0 (short format), the PUCCH resource for NACK-based feedback may be used in the case of NACK, and the ACK resource may be derived by setting the CS index of the PUCCH resource for NACK-based feedback to +6.

[0121] If PF1 (long format) is used, the PUCCH resource for NACK-based feedback may transmit both ACK and NACK via PF1. In PF1, ACK / NACK may be modulated using BPSK (Binary Phase Shift Keying) or QPSK (Quadrature Phase Shift Keying) before transmission.

[0122] The UE may use the PUCCH resource / resource set for unicast PDSCHs to provide HARQ feedback for the activation / deactivation of SPS group-common PDSCHs.

[0123] Furthermore, in this example, HARQ feedback for the SPS group-common PDSCH and its activation / deactivation may be performed using both ACK and NACK feedback. In other words, NACK-only feedback is not required.

[0124] Specifically, for HARQ feedback to a group-common PDSCH, a PUCCH resource / resource set for ACK / NACK feedback and a PUCCH resource / resource set for NACK-only feedback may be configured. In this case, HARQ feedback for the SPS group-common PDSCH and its activation / deactivation may be sent using the PUCCH resource / resource set for ACK / NACK feedback.

[0125] Alternatively, if only a PUCCH resource / resource set related to NACK-only feedback is configured for HARQ feedback to group-common PDSCH, one of the following may occur:

[0126] Based on the PUCCH resource / resource set related to NACK-only feedback, the PUCCH resources related to ACK / NACK feedback may be determined, and ACK / NACK feedback may be performed.

[0127] For example, if PF0 is used, the PUCCH resource for NACK-based feedback may be used in the case of NACK, and the ACK resource may be derived by setting the CS index of the PUCCH resource for NACK-based feedback to +6. If PF1 is used, the PUCCH resource for NACK-based feedback may be used to transmit both ACK and NACK signals via PF1. In PF1, ACK and NACK signals may be transmitted with BPSK / QPSK modulation.

[0128] The UE may use the PUCCH resource / resource set for unicast PDSCH to provide HARQ feedback to the SPS group-common PDSCH.

[0129] (3.4) Example of operation 4 In this example, the activation / deactivation of the SPS group-common PDSCH may be performed at a layer higher than the physical (PHY) layer.

[0130] For example, the activation / deactivation may be performed by a MAC CE (Control Element). Specifically, the activation / deactivation may be notified by a MAC CE included in a group-common PDSCH. In this case, the group-common PDSCH may represent the initial SPS group-common PDSCH reception.

[0131] The Cyclic Redundancy Checksum (CRC) of the PDCCH corresponding to the group-common PDSCH that notifies activation / deactivation may be scrambled by G-RNTI or by RNTI for SPS group-common PDSCH.

[0132] For HARQ feedback regarding activation / deactivation, any of the methods described above may be applied.

[0133] Alternatively, the activation / deactivation of an SPS group-common PDSCH may be notified by a MAC CE included in the unicast PDSCH. In this case, the offset from the unicast PDSCH to the initial SPS group-common PDSCH receiving resource may be notified.

[0134] Alternatively, the activation / deactivation of the SPS group-common PDSCH may be notified by RRC signaling.

[0135] Specifically, the activation / deactivation of the SPS group-common PDSCH may be set by unicast signaling at the RRC layer, and such activation / deactivation may be notified. Confirmation may be performed by a completion report for the provision of RRC parameters.

[0136] Alternatively, the activation / deactivation of the SPS group-common PDSCH may be notified by System Information Box (SIB) containing multicast information.

[0137] (3.5) Example of operation 5 In this example, confirmation for the activation / deactivation of the SPS group-common PDSCH may be performed at a layer higher than the physical (PHY) layer.

[0138] For example, a confirmation MAC CE for an SPS group-common PDSCH may be defined, and this confirmation MAC CE may be transmitted in response to the activation / deactivation of the SPS group-common PDSCH.

[0139] Alternatively, a UE that receives an activation / deactivation of an SPS group-common PDSCH must send the MAC CE on the earliest PUSCH resource after the reception. In other words, if the MAC CE is not sent, the gNB may assume that the UE that did not send (or could not send) the SPS group-common PDSCH activation / deactivation has not been received. In this case, it may be specified that this only applies if NACK-only feedback is set or instructed.

[0140] (3.6) Example of operation 6 In this example, activation / deactivation of the SPS group-common PDSCH may be performed by both group-common signaling and UE-specific signaling.

[0141] Situations in which such signaling is applied include, for example, when a UE that was unable to perform activation / deactivation via group-common signaling receives activation / deactivation via UE-specific signaling, or when a new UE joins an SPS group-common PDSCH UE group that has already completed activation and started transmitting, and begins receiving that SPS group-common PDSCH.

[0142] In this example, the activation / deactivation of the SPS group-common PDSCH may be performed by the UE-specific PDCCH.

[0143] Specifically, if the CRC of a UE-specific PDCCH is scrambled by a predetermined RNTI, that PDCCH may be determined to be an activation / deactivation of an SPS group-common PDSCH.

[0144] Alternatively, if the DCI field value is the same as that of the activation / deactivation of the UE-specific SPS PDSCH, the UE-specific PDCCH may be determined to be the activation / deactivation of the SPS group-common PDSCH.

[0145] Alternatively, if a predetermined field of the DCI is at a predetermined value, the UE-specific PDCCH may be determined to be an activation / deactivation of the SPS group-common PDSCH. The predetermined field may be, for example, the PDSCH-to-HARQ_feedback timing indicator, the PUCCH resource indicator, or the ZP (Zero power) CSI-RS trigger.

[0146] Alternatively, a PDSCH resource specified in a UE-specific PDCCH may be recognized as an SPS group-common PDSCH.

[0147] (3.7) Example of operation 7 In this example, HARQ feedback for the activation / deactivation of the SPS group-common PDSCH may be performed using ACK-only feedback.

[0148] Specifically, in ACK-only feedback, the UE may behave as follows:

[0149] • If the UE successfully receives and decodes the PDSCH signal, it sends an ACK. If a UE fails to receive and decode PDSCH signals, it will not transmit anything. Additionally, a separate PUCCH resource / resource set for ACK-only feedback may be configured, or a PUCCH resource / resource set for ACK / NACK feedback or a PUCCH resource / resource set for NACK-only feedback may be used.

[0150] Furthermore, this example of operation may be applied not only to the activation / deactivation of SPS group-common PDSCHs, but also to group-common PDSCHs other than SPS group-common PDSCHs, specifically to HARQ feedback of group-common PDSCHs to which SPS is not applied.

[0151] (3.8) Example of changes The above examples 1-7 may be combined and applied in combination, as long as no contradictions arise. Also, as mentioned above, terms indicating time domains such as slots may be replaced with terms indicating other time domains, such as sub-slots.

[0152] Furthermore, the CRC of PDCCH / DCI related to the activation / deactivation of SPS group-common PDSCH may be scrambled by G-RNTI.

[0153] The above example of operation was related to MBS targeting simultaneous transmission (delivery) to multiple UEs, but the UEs targeted by MBS do not necessarily have to be multiple. If the operation is performed in accordance with MBS, such as by using group-common PDSCH, the specific or unspecified multiple UEs may be effectively one, and may not be multiple.

[0154] (4) Action and Effects According to the embodiments described above, the following effects can be obtained. Specifically, with the UE200 (and gNB100) according to operation examples 1 to 7, the activation / deactivation of the group-common PDSCH, more precisely the SPS group-common PDSCH, can be performed normally, meaning that the gNB100 (network) can detect DCI misdetection in the UE200. In addition, the gNB100 can appropriately control resources related to HARQ feedback (including the activation / deactivation of the SPS group-common PDSCH).

[0155] The gNB100 and UE200 can efficiently and reliably perform operations associated with semi-fixed scheduling (SPS) in simultaneous data transmission services (MBS) to specific or unspecified multiple UE200s.

[0156] In this embodiment, the UE200 can assume that, with respect to the SPS group-common PDSCH, a terminal group is divided into multiple subgroups, and the SPS of the downlink data channel (PDSCH) is applied on a subgroup basis. Therefore, failures in the activation / deactivation of the SPS group-common PDSCH can be detected more reliably and easily. In addition, by performing group-common PDSCH transmissions on a larger terminal group basis, the number of PDSCH transmissions can be reduced compared to when they are performed on a subgroup basis.

[0157] In this embodiment, it can be assumed that the HARQ feedback for the activation / deactivation of the SPS group-common PDSCH is transmitted in a different time domain (such as a slot) for each UE200. Therefore, reliable HARQ feedback can be provided for each UE200 while utilizing the SPS group-common PDSCH.

[0158] In this embodiment, UE200 may apply both affirmative (ACK) and negative (NACK) responses as HARQ feedback to the activation / deactivation of SPS group-common PDSCH. This allows for precise HARQ feedback for each UE200 while utilizing SPS group-common PDSCH.

[0159] In this embodiment, the UE200 may control the activation / deactivation of the SPS group-common PDSCH based on group common signaling or UE-specific signaling. This allows for more reliable control of the activation / deactivation of the SPS group-common PDSCH.

[0160] (5) Other embodiments Although embodiments have been described above, it will be obvious to those skilled in the art that the invention is not limited to those embodiments described and that various modifications and improvements are possible.

[0161] For example, in the embodiment described above, the names PDCCH and PDSCH were used for the downlink channels, but any downlink control channel or downlink data channel (which may also be a shared channel) may be called by a different name.

[0162] Furthermore, in the above description, configure, activate, update, indicate, enable, specify, and select may be interpreted interchangeably. Similarly, link, associate, correspond, and map may be interpreted interchangeably, as may allocate, assign, monitor, and map.

[0163] Furthermore, "specific," "dedicated," "UE specific," and "UE individual" may be interpreted interchangeably. Similarly, "common," "shared," "group-common," "UE common," and "UE shared" may be interpreted interchangeably.

[0164] Furthermore, the block diagram (Figure 4) used in the description of the embodiments above shows functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Moreover, 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.

[0165] 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.

[0166] Furthermore, the gNB100 and UE200 described above may function as computers that process the wireless communication method of this disclosure. Figure 9 shows an example of the hardware configuration of the device. As shown in Figure 9, 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.

[0167] 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.

[0168] 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.

[0169] 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.

[0170] 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.

[0171] 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 be transmitted from a network via a telecommunications line.

[0172] 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.

[0173] 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.

[0174] 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.

[0175] 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).

[0176] 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).

[0177] 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.

[0178] 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.

[0179] 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.

[0180] 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).

[0181] 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.

[0182] 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 the 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).

[0183] 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.

[0184] 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.

[0185] 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).

[0186] 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).

[0187] 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.

[0188] 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.

[0189] 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.

[0190] 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.

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

[0192] 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.

[0193] 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.

[0194] 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.

[0195] A base station can house one or more (e.g., three) cells (also called sectors). If 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)).

[0196] 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.

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

[0198] 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 some other appropriate term.

[0199] 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.

[0200] Furthermore, the term "base station" in this disclosure may be interpreted as "mobile station" (user terminal, hereinafter the same). For example, the various aspects / embodiments 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 (or side link).

[0201] 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. A wireless frame may consist of one or more frames in the time domain. Each of these one or more frames in the time domain may be called a subframe. 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.

[0202] 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.

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

[0204] 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 a PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called a PDSCH (or PUSCH) mapping type B.

[0205] 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.

[0206] For example, one subframe may be called a Transmit 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.

[0207] 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.

[0208] 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.

[0209] 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 this minimum time unit of scheduling may be controlled.

[0210] 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.

[0211] 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.

[0212] 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.

[0213] Furthermore, the time domain of the 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.

[0214] One or more RBs may also be called a Physical RB (PRB), Sub-Carrier Group (SCG), Resource Element Group (REG), PRB pair, RB pair, etc.

[0215] 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.

[0216] 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.

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

[0218] 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".

[0219] 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 the TTI can be varied in various ways.

[0220] 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.

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

[0222] 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."

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

[0224] 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.

[0225] 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.

[0226] 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.

[0227] 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."

[0228] 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."

[0229] 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]

[0230] 10 Wireless communication systems 20 NG-RAN 100 gNB 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

Claims

1. In data distribution to multiple terminals, a receiving unit receives a common downlink data channel for a semi-fixed schedule of terminal groups, A terminal comprising a control unit that provides feedback to a downlink control channel that activates the semi-fixed scheduling of the downlink data channel using a feedback method that applies both affirmative and negative responses, and provides feedback to a downlink data channel that does not have a downlink control channel using a feedback method that applies only negative responses.

2. In data distribution to multiple terminals, the steps include receiving a common downlink data channel for a semi-fixed scheduled group of terminals, A terminal communication method comprising the steps of providing feedback to a downlink control channel that activates the semi-fixed scheduling of the downlink data channel using a feedback method that applies both affirmative and negative responses, and providing feedback to a downlink data channel that does not have a downlink control channel using a feedback method that applies only negative responses.

3. In data distribution to multiple terminals, a transmission unit transmits a common downlink data channel to a semi-fixed schedule of terminal groups, A base station comprising a receiving unit that receives feedback from a terminal using a feedback method that applies both affirmative and negative responses to a downlink control channel that activates the semi-fixed scheduling of the downlink data channel, and receives feedback from the terminal using a feedback method that applies only negative responses to the downlink data channel that does not have a downlink control channel.

4. A communication system including a base station and multiple terminals, The aforementioned base station is In data distribution to multiple terminals, a transmission unit transmits a common downlink data channel to a semi-fixed schedule of terminal groups, The receiving unit includes a receiving unit that receives feedback from the terminal using a feedback method that applies both affirmative and negative responses to a downlink control channel that activates the semi-fixed scheduling of the downlink data channel, and a receiving unit that receives feedback from the terminal using a feedback method that applies only negative responses to a downlink data channel that does not have a downlink control channel. The aforementioned terminal is The downlink data channel receiving unit, A communication system comprising a control unit that performs feedback using a feedback method that applies both affirmative and negative responses to the downlink control channel, and performs feedback using a feedback method that applies only negative responses to the downlink data channel that does not have a downlink control channel.

Images