Terminal and wireless communication method

The terminal's advanced control unit and receiver configuration address the challenge of reliable retransmission in multicast/broadcast services by managing HARQ processes and identification information for scrambling channels, enhancing the reliability and efficiency of data transmission.

JP2025069346AInactive Publication Date: 2025-04-30NTT DOCOMO INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
JP2025016700
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2025-02-04
Publication Date
2025-04-30
Estimated Expiration
Not applicable · inactive patent

AI Technical Summary

Technical Problem

In multicast/broadcast services, there are challenges in ensuring reliable retransmission of data to specific or unspecified multiple terminals, particularly due to differences in HARQ process numbers and identification information for scrambling channels.

Method used

A terminal equipped with a receiver for downlink data channels common to terminal groups and a control unit that manages HARQ processes and identification information for reliable retransmission, ensuring that specific identification information is used for scrambling channels during retransmissions.

Benefits of technology

The solution enables more reliable retransmission of data in simultaneous data transmission services, improving the overall reliability and efficiency of multicast/broadcast communications.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2025069346000001_ABST
    Figure 2025069346000001_ABST
Patent Text Reader

Abstract

To provide a terminal and a wireless communication method for more reliably receiving re-transmitted data in a simultaneous data transmission service to a plurality of specified or unspecified terminals.SOLUTION: In a wireless communication system, a terminal UE receives a downlink data channel (PDSCH) that is common to a terminal group in data distribution to a plurality of terminals, and assumes that a process number of an automatic repeat request (HARQ) in the PDSCH is different from a process number of the HARQ in a terminal-specific PDSCH.SELECTED DRAWING: Figure 5
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

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

[0002] The 3rd Generation Partnership Project (3GPP) has developed specifications for the 5th generation mobile communication system (5G, also known as New Radio (NR) or Next Generation (NG)), and is also developing specifications for the next generation, known as Beyond 5G, 5G Evolution, or 6G.

[0003] 3GPP Release 17 targets simultaneous data transmission (also called distribution) services (provisional name: MBS: Multicast and Broadcast Services) in NR to multiple specific or unspecified terminals (User Equipment, UE) (Non-Patent Document 1).

[0004] In the MBS, for example, studies are being conducted on scheduling of UE groups that are the subject of services, and improving reliability (for example, feedback of hybrid automatic repeat request (HARQ) to radio base stations (gNBs)). [Prior art documents] [Non-patent literature]

[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 the Invention

[0006] In MBS, data (transport block (TB)) transmitted to multiple UEs can be retransmitted to a specific UE, that is, by unicast.

[0007] In this case, due to multiple ways of handling the HARQ (Automatic Repeat Request) process and retransmission, the UE may not receive the retransmitted data correctly.

[0008] Therefore, the following disclosure has been made in consideration of the above circumstances, and aims to provide a terminal and a wireless communication method that can more reliably receive retransmitted data in a simultaneous data transmission service to multiple specific or unspecified terminals.

[0009] One aspect of the present disclosure is a terminal (UE200) that includes a receiving unit (radio signal transmitting / receiving unit 210) that receives a downlink data channel that is common to a terminal group in data distribution to multiple terminals, and a control unit (control unit 270) that assumes that the process number of an automatic repeat request in the downlink data channel is different from the process number of an automatic repeat request in a downlink channel specific to the terminal.

[0010] One aspect of the present disclosure is a terminal (UE200) that includes a receiver (radio signal transceiver 210) that receives a downlink data channel common to a terminal group in data distribution to multiple terminals, and a control unit (control unit 270) that assumes that, when the downlink data channel is retransmitted to a specific terminal, specific identification information for retransmission is used for scrambling the downlink control channel and the terminal-specific downlink channel.

[0011] One aspect of the present disclosure is a terminal (UE200) that includes a receiver (radio signal transceiver 210) that receives a downlink data channel common to a terminal group in data distribution to multiple terminals, and a control unit (control unit 270) that assumes that a block transmitted via the downlink data channel is retransmitted to either the multiple terminals or a specific terminal only.

[0012] One aspect of the present disclosure is a terminal (UE200) that includes a receiver (radio signal transceiver 210) that receives a downlink data channel that is common to a terminal group in data distribution to multiple terminals, and a control unit (control unit 270) that assumes that a block transmitted via the downlink data channel may be retransmitted to both the multiple terminals and a specific terminal.

[0013] One aspect of the present disclosure is a wireless communication method for distributing data to multiple terminals, the method including the steps of receiving a downlink data channel common to a terminal group, and assuming that a process number of an automatic repeat request in the downlink data channel is different from a process number of an automatic repeat request in a downlink channel specific to the terminal.

[0014] One aspect of the present disclosure is a wireless communication method for distributing data to multiple terminals, the method including: receiving a downlink data channel common to a terminal group; and assuming that, when the downlink data channel is retransmitted to a specific terminal, specific identification information for retransmission is used for scrambling a downlink control channel and a terminal-specific downlink channel. [Brief description of the drawings]

[0015] [Figure 1] FIG. 1 is a diagram showing an overall schematic configuration of a wireless communication system 10. As shown in FIG. [Diagram 2] FIG. 2 is a diagram showing an example of the configuration of a radio frame, a subframe, and a slot used in the radio communication system 10. As shown in FIG. [Diagram 3] FIG. 3 is a diagram showing an example of the configuration of the PTM transmission method 1 and the PTM transmission method 2. As shown in FIG. [Figure 4] Figure 4 is a functional block configuration diagram of gNB100 and UE200. [Diagram 5] FIG. 5 is a diagram showing an example of a sequence of PDSCH and HARQ feedback according to the first operation example. [Figure 6]FIG. 6 is a diagram showing an example of a sequence of PDCCH, PDSCH and HARQ feedback according to the second operation example. [Figure 7] FIG. 7 is a diagram showing an example of a sequence of PDSCH and HARQ feedback according to the third operation example. [Figure 8] FIG. 8 is a diagram showing an example of the hardware configuration of gNB100 and UE200. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0016] Hereinafter, an embodiment will be described with reference to the drawings. Note that the same or similar reference numerals are used to designate the same functions or configurations, and the description thereof will be omitted as appropriate.

[0017] (1) Overall configuration of wireless communication system (1.1) System configuration example 1 is a schematic diagram of an overall configuration 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] The wireless communication system 10 may be a wireless communication system conforming to a standard called Beyond 5G, 5G Evolution, or 6G.

[0019] The 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.

[0020] The 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). The NG-RAN 20 and the 5GC may be simply referred to as a "network."

[0021] The gNB 100 is a radio base station conforming to NR, and performs radio communication conforming to NR with the UE 200. The gNB 100 and the UE 200 can support Massive MIMO, which generates a more directional beam BM by controlling radio signals transmitted from multiple antenna elements, Carrier Aggregation (CA), which uses a bundle of multiple component carriers (CCs), and Dual Connectivity (DC), which simultaneously communicates between the UE and each of multiple NG-RAN Nodes.

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

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

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

[0025] Also, 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] FIG. 2 shows an example of the configuration of radio frames, subframes, and slots used in the radio communication system 10. In FIG.

[0027] As shown in Figure 2, one slot is composed of 14 symbols, and the larger (wider) the SCS, the shorter the symbol period (and slot period). The number of symbols constituting one slot does not necessarily have to be 14 symbols (e.g., 28, 56 symbols). The number of slots per subframe may differ depending on the SCS. Furthermore, the SCS may be wider than 240 kHz (e.g., 480 kHz, 960 kHz as shown in Figure 2).

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

[0029] (1.2) Provision of MBS In the wireless communication system 10, Multicast and Broadcast Services (MBS) may be provided.

[0030] For example, in a stadium or a hall, a large number of UEs 200 are located within a certain geographical area, and a large number of UEs 200 may simultaneously receive the same data. In such a case, it is effective to use MBS instead of unicast.

[0031] Note that unicast may be interpreted as one-to-one communication with the network, with a specific UE 200 being designated (identification information unique to the UE 200 may be designated).

[0032] Multicast may be interpreted as one-to-many (specific many) communication with a network by specifying a specific number of UEs 200 (identification information for multicast may be specified). Note that the number of UEs 200 receiving the received multicast data may ultimately be one.

[0033] Broadcasting may be interpreted as one-to-one communication with the network for all UEs 200. Data to be multicast / broadcast may be identical copied content, but some content such as the header may be different. Data to be multicast / broadcast may be transmitted (distributed) simultaneously, but strict simultaneity is not necessarily required, and propagation delay and / or processing delay within the RAN node may be included.

[0034] The target UE 200 may have a radio resource control layer (RRC) state of an idle state (RRC idle), a connected state (RRC connected), or another state (e.g., an inactive state). The inactive state may be interpreted as a state in which some RRC settings are maintained.

[0035] In MBS, the following three types of methods are assumed for scheduling of multicast / broadcast PDSCH (Physical Downlink Shared Channel), specifically, scheduling of MBS packets (which may be read as data). Note that RRC connected UE may be read as RRC idle UE or RRC inactive UE.

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

[0037] The CRC (Cyclic Redundancy Checksum) of the PDCCH and the PDSCH are scrambled by a group-common RNTI (which may also be called the Radio Network Temporary Identifier, G-RNTI).

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

[0039] The PDCCH CRC is scrambled by the UE-specific RNTI.

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

[0041] ·PTP transmission method: For RRC connected UEs, schedule UE-specific PDSCH using UE-specific PDCCH.

[0042] The CRC of the PDCCH and the PDSCH are scrambled by a UE-specific RNTI, which may mean that the MBS packet is transmitted by unicast.

[0043] Fig. 3 shows configuration examples of PTM transmission method 1 and PTM transmission method 2. Note that the UE-specific PDCCH / PDSCH can be identified by the target UE, but does not need to be identified by other UEs in the same MBS group. The group-common PDCCH / PDSCH is transmitted in the same time / frequency resource and can be identified by all UEs in the same MBS group. The names of PTM transmission methods 1 and 2 are tentative names, and may be called by other names as long as the above-mentioned operations are performed.

[0044] Note that in point-to-point (PTP) distribution, the RAN node may distribute individual copies of the MBS data packets over the air to individual UEs, whereas in point-to-multipoint (PTM) distribution, the RAN node may distribute a single copy of the MBS data packets over the air to a set of UEs.

[0045] Also, in order to improve the reliability of MBS, the following two feedback methods are envisaged for HARQ (Hybrid Automatic repeat request) feedback, specifically, HARQ feedback for multicast / broadcast PDSCH.

[0046] Option 1: Both ACK and NACK feedback (ACK / NACK feedback) · UE that successfully receives and decodes PDSCH sends ACK · UEs that fail to receive and decode PDSCH send NACK PUCCH (Physical Uplink Control Channel) resource setting: PUCCH-Config can be set for multicast PUCCH resources: shared / orthogonal between UEs, depending on network configuration HARQ-ACK CB (codebook): Supports type-1 and type-2 (CB decision algorithm (specified in 3GPP TS38.213)) Multiplexing: Unicast or Multicast available Option 2: NACK-only feedback · UE that successfully receives and decodes PDSCH does not send ACK (does not send a response) · UEs that fail to receive and decode PDSCH send NACK For a given UE, PUCCH resource configuration can be configured separately via unicast or groupcast (multicast) In addition, ACK may be called a positive acknowledgement, and NACK may be called a negative acknowledgement. HARQ may be called an automatic repeat request.

[0047] Enabling / Disabling of Option 1 or Option 2 may be applied as follows:

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

[0049] ·SPS group-common PDSCH adopted Multiple SPS group-common PDSCHs can be configured as UE capabilities. -HARQ feedback for SPS group-common PDSCH possible - Activation / deactivation possible via at least group-common PDCCH Note that deactivation may be replaced with other synonymous terms such as release. For example, activation may be replaced with start, initiation, trigger, etc., and deactivation may be replaced with end, stop, etc.

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

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

[0052] Also, for the physical layer, there may be scheduling categories of time domain scheduling and frequency domain scheduling.

[0053] Furthermore, multicast, groupcast, broadcast, and MBS may be interchangeable. A multicast PDSCH and a PDSCH scrambled by a group-common RNTI may be interchangeable.

[0054] Furthermore, the terms data and packet may be used interchangeably and may be interpreted as synonymous with terms such as signal, data unit, etc. Additionally, the terms send, receive, transmit, and distribute may be used interchangeably.

[0055] (2) Functional block configuration of wireless communication system Next, a functional block configuration of the wireless communication system 10 will be described. Specifically, the functional block configurations of the gNB 100 and the UE 200 will be described.

[0056] Fig. 4 is a functional block diagram of the gNB 100 and the UE 200. The following describes the UE 200. As shown in Fig. 4, the UE 200 includes a radio signal transmitting / receiving 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 transmitting / receiving unit 260, and a control unit 270.

[0057] Note that Fig. 4 shows only main functional blocks related to the description of the embodiment, and the UE 200 has other functional blocks (e.g., a power supply unit, etc.). Fig. 4 shows the functional block configuration of the UE 200 (gNB 100), and for the hardware configuration, please refer to Fig. 8.

[0058] The radio signal transmission / reception unit 210 transmits and receives radio signals conforming to NR. The radio signal transmission / reception unit 210 supports Massive MIMO, CA that uses a bundle of multiple CCs, and DC that simultaneously communicates between a UE and each of two NG-RAN nodes.

[0059] Moreover, the radio signal transmitting / receiving unit 210 supports MBS and can receive a downlink channel that is common to a terminal group (group common) in data distribution to a plurality of UEs 200. In this embodiment, the radio signal transmitting / receiving unit 210 may constitute a receiving unit.

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

[0061] The amplifier unit 220 is configured by a PA (Power Amplifier) / LNA (Low Noise Amplifier) ​​etc. The amplifier unit 220 amplifies the signal output from the modem unit 230 to a predetermined power level. The amplifier unit 220 also amplifies the RF signal output from the wireless signal transmitting / receiving unit 210.

[0062] The modem unit 230 performs data modulation / demodulation, transmission power setting, resource block allocation, and the like for each predetermined communication destination (such as the gNB 100). The modem 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 processor 240 executes processing related to various control signals transmitted and received by the UE 200, and processing related to various reference signals transmitted and received by the UE 200.

[0064] Specifically, the control signal / reference signal processor 240 receives various control signals, for example, radio resource control layer (RRC) control signals, transmitted from the gNB 100 via a predetermined control channel. In addition, the control signal / reference signal processor 240 transmits various control signals to the gNB 100 via a predetermined control channel.

[0065] The control signal / reference signal processor 240 executes processing using reference signals (RS) such as a Demodulation Reference Signal (DMRS) and a Phase Tracking Reference Signal (PTRS).

[0066] DMRS is a known reference signal (pilot signal) between a base station and a terminal for estimating a fading channel used for data demodulation. PTRS is a terminal-specific reference signal for estimating phase noise, which is an issue in high frequency bands.

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

[0068] The channels include a control channel and a data channel. The control channels may include a PDCCH, a Physical Uplink Control Channel (PUCCH), a Random Access Channel (RACH, Downlink Control Information (DCI) including a Random Access Radio Network Temporary Identifier (RA-RNTI)), a Physical Broadcast Channel (PBCH), and the like.

[0069] Moreover, the data channel includes a PDSCH, a PUSCH (Physical Uplink Shared Channel), etc. Data may mean data transmitted via a data channel.

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

[0071] Specifically, the encoding / decoding unit 250 divides the data output from the data transmitting / receiving unit 260 into pieces of a predetermined size, performs channel coding on the divided data, and decodes the data output from the modem unit 230 and concatenates the decoded data.

[0072] The data transmission / reception unit 260 transmits and receives Protocol Data Units (PDUs) and Service Data Units (SDUs). Specifically, the data transmission / reception unit 260 performs assembly / disassembly of PDUs / SDUs in multiple layers (such as a Medium Access Control layer (MAC), a Radio Link Control layer (RLC), and a Packet Data Convergence Protocol layer (PDCP)). In addition, the data transmission / reception unit 260 performs data error correction and retransmission control based on a hybrid automatic repeat request (Hybrid ARQ).

[0073] The control unit 270 controls each functional block constituting the UE 200. In particular, in this embodiment, the control unit 270 executes control related to scheduling of a downlink channel for MBS and HARQ feedback of the channel.

[0074] The control unit 270 executes control corresponding to the scheduling of a downlink channel common to a terminal group in the MBS, that is, data delivery to a plurality of UEs 200. Specifically, the control unit 270 can execute control corresponding to the scheduling of a group-common PDCCH and a group-common PDSCH.

[0075] In addition, the control unit 270 may assume that the HARQ process number (HARQ process ID) in the downlink data channel, specifically, the PDSCH related to the MBS (which may include the group-common PDSCH and the SPS group-common PDSCH) is different from the HARQ process number in the downlink channel (PDSCH) specific to the UE 200.

[0076] The downlink channel (PDSCH) specific to UE 200 may be interpreted as a channel transmitted (which may include retransmission) by unicast (PTP) to a specific UE 200 (or data (transport block (TB)) transmitted via the corresponding downlink channel).

[0077] The HARQ process number (HPN) may be interpreted as a number capable of identifying a plurality of HARQ processes that may be executed in parallel, and may be, for example, 0 to 3. The control unit 270 may assume that the HPN of a PDSCH related to multicast / broadcast such as a group-common PDSCH is different from the HPN of a PDSCH transmitted by unicast, that is, the same number is not assigned.

[0078] The HPN for the group-common PDSCH (TB associated with the group-common PDSCH) may be set by a parameter of a higher layer. The HPN for the group-common PDSCH may be fixed, or, once control unit 270 recognizes the HPN for the group-common PDSCH, it may assume that the HPN is used for the group-common PDSCH.

[0079] Furthermore, when control unit 270 receives a unicast channel (TB) associated with an HPN recognized as for a group-common PDSCH, control unit 270 may assume that the TB is a retransmission related to the group-common PDSCH.

[0080] The control unit 270 may assume that when a PDSCH for an MBS is retransmitted to a specific UE 200, i.e., retransmitted by PTP, a specific identification information for retransmission (RNTI) is used for scrambling downlink channels such as a PDCCH (downlink control channel) and a PDSCH specific to the UE 200.

[0081] Specifically, when a group-common PDSCH transmitted by PTM1 is retransmitted by PTP, the control unit 270 may assume that the RNTI for scrambling the CRC of the PDCCH (which may include DCI) and the RNTI for scrambling the PDSCH are predetermined RNTIs reserved for retransmission.

[0082] The control unit 270 may assume that a block (which may be read as data) transmitted via a downlink data channel such as a group-common PDSCH, specifically a transport block (TB), is retransmitted to either a plurality of UEs 200 or a specific UE 200. Specifically, the control unit 270 may assume that the TB is retransmitted by only one of PTM1 or PTP.

[0083] In addition, whether the retransmission is performed by PTM1 or PTP may be notified to UE 200 by higher layer signaling. In addition, whether the retransmission is performed by PTM1 or PTP may be set for each HPN, and the retransmission by PTM1 or PTP may be set in association with a logical channel.

[0084] Alternatively, the control unit 270 may assume that a TB transmitted via a downlink data channel such as a group-common PDSCH may be retransmitted to both a plurality of UEs 200 and a specific UE 200 .

[0085] Specifically, the control unit 270 may assume that the group-common PDSCH may be retransmitted simultaneously by PTM1 and PTP.

[0086] A specific operation example regarding retransmission of TB transmitted via group-common PDSCH by PTM1 and PTP will be described later.

[0087] In addition, gNB100 can perform control regarding the scheduling, retransmission, and HARQ of the above-mentioned downlink channels.

[0088] (3) Operation of wireless communication system Next, a description will be given of the operation of the wireless communication system 10. Specifically, a description will be given of the operation related to the scheduling of the downlink channel for the MBS and the HARQ feedback of the channel.

[0089] For MBS, the scheduling of HARQ retransmission may be as shown in Table 1, but is not limited thereto.

[0090] [Table 1]

[0091] As shown in Table 1, if the initial transmission (Initial TX) of a TB is PTM-1 and the HARQ feedback is ACK and NACK (ACK / NACK), retransmission for HARQ of the TB may be performed by PTM-1 or PTP (or both).

[0092] On the other hand, if the initial transmission (Initial TX) of a certain TB is PTM-1 and the HARQ feedback is NACK-only, retransmission regarding the HARQ of the TB may be performed by PTM-1.

[0093] In this way, a transport block (TB) transmitted via group-common PDSCH by PTM-1 can be retransmitted by PTP, but for example, how to handle the HARQ process in this case may be an issue. Furthermore, how the UE 200 recognizes that it is a retransmission of a TB transmitted by PTM-1 may also be an issue.

[0094] In addition, it is also necessary to consider whether or not to allow simultaneous execution of PTM-1 retransmission and PTP retransmission of a TB transmitted by PTM-1. For example, if PTM-1 retransmission is performed for many UEs in the simultaneous execution, PDCCH and / or PDSCH resources can be saved. At the same time, if PTP retransmission is performed for a specific (e.g., one) UE (such as a UE located at a cell edge), an appropriate beam and MCS (Modulation and Coding Scheme) can be used. However, when a UE receives both the PTM-1 retransmission and the PTP retransmission for a certain TB, it is necessary to clarify which one to process, which one to provide HARQ feedback to, etc.

[0095] In the following, an example of an operation regarding retransmission of a TB transmitted via a group-common PDSCH that can solve such a problem will be described.

[0096] (3.1) Example 1 In this example operation, the TB transmitted by PTM-1 may be retransmitted by PTP. In this example operation, the HARQ process number (HPN, which may also be called HARQ process ID) for the group-common PDSCH transmitted by PTM-1 may have to be a different value from other unicast transmissions.

[0097] Fig. 5 shows an example of a sequence of PDSCH and HARQ feedback according to operation example 1. As shown in Fig. 5, the HPN (e.g., y) associated with the group-common PDSCH transmitted by PTM-1 may be a value different from the HPN (e.g., x) associated with the PDSCH of other unicast transmissions.

[0098] In this operation example, which HPN is for the TB related to the group-common PDSCH may be configured by a higher layer (eg, RRC) NO parameter.

[0099] The UE 200 may assume that the HPN associated with the group-common PDSCH once received applies only to the TB transmitted via the group-common PDSCH.

[0100] In addition, when UE 200 receives unicast data (which may be a TB) associated with an HPN related to the group-common PDSCH (e.g., when it receives a DL assignment scrambled by the C-RNTI), it may assume that the data is a retransmission of a TB via the group-common PDSCH.

[0101] (3.2) Example 2 In this operation example, the TB transmitted by PTM-1 may be retransmitted by PTP. In this operation example, when the group-common PDSCH (TB) transmitted by PTM-1 is retransmitted by PTP, the RNTI for scrambling the CRC of the PDCCH (which may be read as DCI) and the RNTI for scrambling the PDSCH may be a predetermined RNTI that is distinguished from other RNTIs.

[0102] Fig. 6 shows an example of the sequence of the PDCCH, PDSCH and HARQ feedback according to the operation example 2. As shown in Fig. 6, the RNTI used for scrambling the CRC of the PDCCH / DCI and the RNTI used for scrambling the retransmitted PDSCH (group-common PDSCH) may be a predetermined RNTI (e.g., x) that is distinguished from other RNTIs.

[0103] The RNTI may be dedicated for retransmission by PTP. Alternatively, it may be another RNTI generated based on the C (Cell)-RNTI, or another RNTI generated based on the G-RNTI. The other RNTI may be a value reversibly derived from the C-RNTI / G-RNTI, such as a value calculated by multiplying the value of the C-RNTI / G-RNTI by a coefficient.

[0104] (3.3) Example 3 In this operation example, a TB transmitted by PTM-1 is not retransmitted by both PTM-1 and PTP simultaneously.

[0105] 7 shows an example of a sequence of PDSCH and HARQ feedback according to operation example 3. In this operation example, for a TB transmitted via a certain group-common PDSCH, UE 200 may assume that the TB is retransmitted by only either PTM-1 or PTP. That is, UE 200 may not assume that the TB is retransmitted by both PTM-1 and PTP at the same time.

[0106] In addition, whether the retransmission is performed using PTM1 or PTP may be set by a higher layer (for example, RRC). For example, whether the retransmission is performed using PTM1 or PTP may be notified to UE 200 by signaling of the RRC layer. More specifically, whether the retransmission is performed using PTM1 or PTP may be notified by system information (SIB: System Information Block), and a common setting may be applied to all UEs in a cell.

[0107] In addition, whether retransmission is performed by PTM1 or PTP may be set for each HARQ process number (HPN), or retransmission by PTM1 or PTP may be set in association with a logical channel (LCH).

[0108] In addition, PDCCH / PDSCH reception and HARQ feedback transmission may be considered as one set, and UE 200 may assume that no transmission is performed via another PDCCH / PDSCH of the same TB (using PTM-1 or PTP) between the start and end of the one set.

[0109] In this case, the PDCCH / PDSCH included in the set may be limited to be transmitted by either PTM-1 or PTP. That is, the UE 200 may assume that after receiving the PDCCH / PDSCH by PTM-1, the UE 200 will not receive the same TB by PTP until HARQ feedback. On the other hand, the UE 200 may assume that after receiving the PDCCH / PDSCH by PTP, the UE 200 will not receive the same TB by PTM-1 until HARQ feedback.

[0110] Furthermore, UE 200 may assume that PDCCH reception related to only retransmission by either PTM-1 or PTP is performed in a PDCCH monitoring occasion (MO) / search space / control resource set (CORESET).

[0111] (3.4) Example 4 In this operation example, a TB transmitted by PTM-1 may be retransmitted by both PTM-1 and PTP at the same time. In this operation example, for a TB transmitted via a certain group-common PDSCH, the UE 200 may assume that the TB may be retransmitted by both PTM-1 and PTP.

[0112] For retransmission of a TB transmitted via a certain group-common PDSCH, the first PDCCH / PDSCH reception and the HARQ feedback transmission are considered as one set, and UE 200 may assume that transmission (second PDCCH / PDSCH reception) of the same TB via another PDCCH / PDSCH (using PTM-1 or PTP) may occur between the start and end of the one set.

[0113] In this case, for example, the first PDCCH / PDSCH reception may be limited to be transmitted by either PTM-1 or PTP, i.e., the UE 200 may assume that after receiving the PDCCH / PDSCH by PTM-1, it may receive the same TB by PTP until HARQ feedback, but may not assume the opposite (receiving the same TB by PTM-1 after receiving by PTP).

[0114] Alternatively, UE200 may assume that after receiving the PDCCH / PDSCH via PTP, it may receive the same TB via PTM-1 until HARQ feedback, but it need not assume the reverse (receiving the same TB via PTP after receiving it via PTM-1).

[0115] Furthermore, the UE 200 may assume that PDCCH reception related to retransmission by both PTM-1 and PTP is performed in a certain PDCCH monitoring occasion (MO) / search space / CORESET.

[0116] In both retransmissions by PTM-1 and PTP, at least some of the same (i.e., overlapping) radio resources, specifically time resources or frequency resources, may be used.

[0117] In the above-mentioned retransmission by both PTM-1 and PTP, when the UE 200 receives the PDCCH related to the retransmission by PTM-1 and the PDCCH related to the retransmission by PTP, the UE 200 may execute a predetermined process related to reception and / or decoding. Specifically, the following process may be executed.

[0118] - Execute reception / decoding process only for retransmission by PTM-1 -Only retransmission by PTP is performed, and reception / decoding process is performed - Receive / decode only the PDCCH / PDSCH that is received first - Receive / decode retransmissions by both PTM-1 and PTP In this case, UE 200 may combine and decode the signals retransmitted by both PTM-1 and PTP.

[0119] In addition, in the above-mentioned retransmission by both PTM-1 and PTP, when the UE 200 receives the PDCCH related to the retransmission by PTM-1 and the PDCCH related to the retransmission by PTP, the UE 200 may execute a predetermined process related to the HARQ feedback. Specifically, the following process may be executed.

[0120] For HARQ processes related to retransmissions that were not received / decoded, feedback is provided as a predefined response (e.g., NACK). No feedback is performed for HARQ processes related to retransmissions that were not received / decoded When receiving / decoding retransmissions by both PTM-1 and PTP, feedback is provided for each retransmission. In this case, the information to be fed back may be the same or different.

[0121] When the time domains (e.g., slots) in which feedback for retransmission by PTM-1 and PTP is performed are the same, or when at least a portion of the resources for feedback overlap, the contents of the feedback may be multiplexed.

[0122] (3.5) Example of changes The above-described operation examples 1 to 4 may be combined and applied in a composite manner as long as no contradiction occurs. Furthermore, as described above, a term indicating a time domain such as a slot may be replaced with a term indicating another time domain such as a subslot.

[0123] The above-described operational example relates to an MBS targeted for simultaneous transmission (distribution) to multiple UEs, however, the UEs targeted by the MBS do not necessarily always have to be multiple, and as long as operation in accordance with the MBS is performed, such as using a group-common PDSCH, multiple specific or unspecified UEs may include cases where there is essentially one UE, and do not have to be multiple UEs.

[0124] (4) Actions and Effects According to the above-described embodiment, the following advantageous effects can be obtained. Specifically, according to the UE 200 according to the operation examples 1 to 4, data (TB) transmitted and retransmitted by PTM-1 and / or PTP can be reliably received, and appropriate HARQ feedback can be executed. In other words, according to the UE 200, in a simultaneous data transmission service (MBS) to a specified or unspecified plurality of UEs 200, retransmitted data can be more reliably received.

[0125] In this embodiment, the UE 200 may assume that the HPN of the PDSCH for the MBS is different from the HPN in the downlink channel (PDSCH) specific to the UE 200. Therefore, the UE 200 can easily and reliably recognize that the TB is retransmitted via the PDSCH for the MBS based on the HPN.

[0126] In this embodiment, when the group-common PDSCH transmitted by PTM1 is retransmitted by PTP, the UE 200 may assume that the RNTI for scrambling the CRC of the PDCCH (which may include DCI) and the RNTI for scrambling the PDSCH are predetermined RNTIs reserved for retransmission. Therefore, the UE 200 can easily and reliably recognize the retransmitted TB.

[0127] In this embodiment, the UE 200 may assume that a TB transmitted via a downlink data channel such as a group-common PDSCH is retransmitted to either a plurality of UEs 200 or a specific UE 200. Alternatively, the UE 200 may assume that a TB transmitted via a downlink data channel such as a group-common PDSCH is retransmitted to both a plurality of UEs 200 and a specific UE 200. This allows the UE 200 to easily and reliably recognize the retransmitted TB.

[0128] (5) Other embodiments Although the embodiment has been described above, it will be apparent to those skilled in the art that the present invention is not limited to the description of the embodiment and that various modifications and improvements are possible.

[0129] For example, in the above-described embodiment, the names PDCCH and PDSCH are used as downlink channels, but the downlink control channel or the downlink data channel (which may be a shared channel) may be called by another name.

[0130] Also, in the above description, configure, activate, update, indicate, enable, specify, and select may be interchanged. Similarly, link, associate, correspond, and map may be interchanged, and allocate, assign, monitor, and map may be interchanged.

[0131] Furthermore, specific, dedicated, UE-specific, and UE-dedicated may be read as interchangeable terms. Similarly, common, shared, group-common, UE-common, and UE-shared may be read as interchangeable terms.

[0132] Moreover, the block configuration diagram (FIG. 4) used in the description of the above-mentioned embodiment shows functional blocks. 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 by using one device that is physically or logically combined, or may be realized by using two or more devices that are physically or logically separated and directly or indirectly connected (for example, by using wires, wirelessly, etc.). The functional block may be realized by combining the one device or the multiple devices with software.

[0133] Functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs the function of transmission is called a transmitting unit or a transmitter. As described above, there is no particular limitation on the method of realization of any of these.

[0134] Furthermore, the above-mentioned gNB 100 and UE 200 may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 8 is a diagram showing an example of a hardware configuration of the device. As shown in Fig. 8, the device may be configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, and a bus 1007.

[0135] In the following description, the term "apparatus" may be interpreted as a circuit, a device, a unit, etc. The hardware configuration of the apparatus may be configured to include one or more of the apparatuses shown in the drawings, or may be configured to exclude some of the apparatuses.

[0136] Each functional block of the device (see FIG. 4) is realized by any hardware element of the computer device, or a combination of the hardware elements.

[0137] In addition, each function in the device is realized by loading a specific software (program) onto hardware such as the processor 1001, memory 1002, etc., so that the processor 1001 performs calculations, controls communication by the communication device 1004, and controls at least one of reading and writing of data in the memory 1002 and storage 1003.

[0138] The processor 1001 controls the entire computer by running, for example, an operating system, and may be configured by a central processing unit (CPU) including an interface with peripheral devices, a control unit, an arithmetic unit, a register, and the like.

[0139] Furthermore, the processor 1001 reads out programs (program codes), 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 according to these. As the programs, programs that cause a computer to execute at least a part of the operations described in the above-mentioned embodiments are used. Furthermore, the above-mentioned various processes may be executed by one processor 1001, or may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may be transmitted from a network via a telecommunications line.

[0140] The memory 1002 is a computer-readable recording medium, and may be configured by at least one of, for example, a Read Only Memory (ROM), an Erasable Programmable ROM (EPROM), an Electrically Erasable Programmable ROM (EEPROM), a Random Access Memory (RAM), etc. The memory 1002 may also be called a register, a cache, a main memory (primary storage device), etc. The memory 1002 can store a program (program code), a software module, etc., capable of executing a method according to an embodiment of the present disclosure.

[0141] Storage 1003 is a computer-readable recording medium, and may be composed of at least one of, for example, an optical disk such as a Compact Disc ROM (CD-ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray (registered trademark) disk), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy (registered trademark) disk, a magnetic strip, and the like. Storage 1003 may be referred to as an auxiliary storage device. The above-mentioned recording medium may be, for example, a database, a server, or other suitable medium including at least one of memory 1002 and storage 1003.

[0142] The communication device 1004 is hardware (transmission / reception device) for performing communication between computers via at least one of a wired network and a wireless network, and is also called, for example, a network device, a network controller, a network card, or a communication module.

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

[0144] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that accepts input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, an LED lamp, etc.) that performs output to the outside. The input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).

[0145] In addition, 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 may be configured using different buses between each device.

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

[0147] Furthermore, the notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., RRC signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB)), other signals, or a combination of these. Furthermore, the RRC signaling may be called an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.

[0148] Each aspect / embodiment described in the present disclosure may be applied to at least one of a system using 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 (registered trademark), GSM (registered trademark), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), other suitable systems, and next-generation systems extended based on these. In addition, a combination of multiple systems (e.g., a combination of at least one of LTE and LTE-A and 5G, etc.) may be applied.

[0149] The order of the steps, sequences, flow charts, etc. of each aspect / embodiment described in this disclosure may be changed unless inconsistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

[0150] In the present disclosure, a specific operation performed by a base station may be performed by its upper node in some cases. 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 may be performed by at least one of the base station and other network nodes other than the base station (e.g., MME or S-GW, etc., but are not limited to these). Although the above example illustrates a case in which there is one other network node other than the base station, it may also be a combination of multiple other network nodes (e.g., MME and S-GW).

[0151] Information, signals (information, etc.) may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer), and may be input and output via multiple network nodes.

[0152] The input / output information may be stored in a specific location (e.g., memory) or may be managed using a management table. The input / output information may be overwritten, updated, or appended. The output information may be deleted. The input information may be transmitted to another device.

[0153] The determination may be based on a value represented by a single bit (0 or 1), a Boolean (true or false) value, or a numerical comparison (e.g., comparison with a predetermined value).

[0154] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched according to execution. In addition, notification of specific information (e.g., notification that "X is the case") is not limited to being done explicitly, but may be done implicitly (e.g., not notifying the specific information).

[0155] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0156] Additionally, software, instructions, information, etc. may be transmitted or received over a transmission medium. For example, if the software is transmitted from a website, server, or other remote source using wired and / or wireless technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave, etc.), then these wired and / or wireless technologies are included within the definition of transmission media.

[0157] The information, signals, etc. described in this disclosure may be represented using any of a variety of 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 voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

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

[0159] As used in this disclosure, the terms "system" and "network" are used interchangeably.

[0160] In addition, the information, parameters, etc. described in the present disclosure may be represented using absolute values, may be represented using relative values ​​from a predetermined value, or may be represented using other corresponding information. For example, a radio resource may be indicated by an index.

[0161] The names used for the above-mentioned parameters are not limiting in any way. Furthermore, the formulas using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not limiting in any way.

[0162] In this disclosure, terms such as "base station (BS)", "radio base station", "fixed station", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", "access point", "transmission point", "reception point", "transmission / reception point", "cell", "sector", "cell group", "carrier", "component carrier", etc. may be used interchangeably. A base station may also be referred to by terms such as a macro cell, a small cell, a femto cell, a pico cell, etc.

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

[0164] The term "cell" or "sector" refers to part or all of the coverage area of ​​a base station and / or a base station subsystem that provides communication services within that coverage.

[0165] In this disclosure, the terms "Mobile Station (MS)", "user terminal", "User Equipment (UE)", "terminal", etc. may be used interchangeably.

[0166] 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 suitable terminology.

[0167] 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 moving body, the moving body itself, etc. The moving body may be a vehicle (e.g., a car, an airplane, etc.), an unmanned moving 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 include 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.

[0168] Furthermore, a base station in the present disclosure may be read as a mobile station (user terminal, the same applies below). For example, each aspect / embodiment of the present 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) or Vehicle-to-Everything (V2X)). In this case, the mobile station may be configured to have the functions of a base station. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, an uplink channel, a downlink channel, etc. may be read as a side channel (or side link).

[0169] Similarly, a mobile station in the present disclosure may be interpreted as a base station, in which case the base station may have the functions of a mobile station. A radio frame may be composed of one or more frames in the time domain. Each of the one or more frames in the time domain may be called a subframe. A subframe may further be composed 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.

[0170] Numerology may be a communication parameter that applies to the transmission and / or reception of a signal or channel, and may indicate, for example, at least one of a SubCarrier Spacing (SCS), a bandwidth, a symbol length, a Cyclic Prefix length, a Transmission Time Interval (TTI), a number of symbols per TTI, a radio frame structure, a particular filtering operation that the transceiver performs in the frequency domain, a particular windowing operation that the transceiver performs in the time domain, etc.

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

[0172] A slot may include multiple minislots. Each minislot may be composed of one or more symbols in the time domain. A minislot may also be called a subslot. A minislot may be composed 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.

[0173] A radio frame, a subframe, a slot, a minislot, and a symbol each represent a time unit for transmitting a signal. The radio frame, the subframe, the slot, the minislot, and the symbol may each be referred to by a different name.

[0174] 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. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in the existing LTE, a period shorter than 1 ms (for example, 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.

[0175] Here, TTI refers to, for example, the minimum time unit for scheduling in wireless communication. For example, in an LTE system, a base station performs scheduling to allocate radio resources (such as frequency bandwidth and transmission power that can be used by each user terminal) to each user terminal in TTI units. Note that the definition of TTI is not limited to this.

[0176] The TTI may be a transmission time unit of a channel-coded data packet (transport block), a code block, a code word, etc., or may be a processing unit of scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) in which a transport block block, a code word, etc. are actually mapped may be shorter than the TTI.

[0177] In addition, when one slot or one minislot is called TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit of scheduling. Also, the number of slots (minislots) constituting the minimum time unit of scheduling may be controlled.

[0178] A TTI having a time length of 1 ms may be called a normal TTI (TTI in LTE Rel. 8-12), a normal TTI, a long TTI, a normal subframe, a normal subframe, a long subframe, a slot, etc. A TTI shorter than a normal TTI may be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a minislot, a subslot, a slot, etc.

[0179] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length exceeding 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and equal to or greater than 1 ms.

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

[0181] In addition, the time domain of the RB may include one or more symbols and may be one slot, one minislot, one subframe, or one TTI in length. Each of one TTI, one subframe, etc. may be composed of one or more resource blocks.

[0182] One or more RBs may be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, or the like.

[0183] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.

[0184] A Bandwidth Part (BWP), which may also be referred to as a fractional bandwidth, may represent a subset of contiguous common resource blocks (RBs) for a numerology on a carrier, where the common RBs may be identified by the index of the RBs relative to a common reference point of the carrier. PRBs may be defined in a BWP and numbered within the BWP.

[0185] The BWP may include a BWP for UL (UL BWP) and a BWP for DL ​​(DL BWP). One or more BWPs may be configured for a UE within one carrier.

[0186] At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal / channel outside the active BWP. Note that the terms "cell", "carrier", etc. in this disclosure may be replaced with "BWP".

[0187] The above-mentioned structures of radio frames, subframes, slots, minislots, symbols, etc. are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio 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, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc. may be changed in various ways.

[0188] The terms "connected," "coupled," or any variation thereof, refer to 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" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using at least one of one or more wires, cables, and printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

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

[0190] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

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

[0192] Any reference to an element using a designation such as "first," "second," etc., 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. Thus, a reference to a first and a second element does not imply that only two elements may be employed therein or that the first element must precede the second element in some way.

[0193] When the terms "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term "comprising." Further, as used in this disclosure, the term "or" is not intended to be an exclusive or.

[0194] In this disclosure, where articles have been added due to translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

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

[0196] In the present 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 "coupled" may also be interpreted in the same way as "different."

[0197] Although the present disclosure has been described in detail above, it is clear to those skilled in the art that the present disclosure is not limited to the embodiments described in the present disclosure. The present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure. [Explanation of symbols]

[0198] 10. Wireless communication systems 20 NG-RAN 100 gNB 200UE 210 Radio signal transmitter / receiver 220 Amplifier section 230 Modulation and demodulation section 240 Control signal / reference signal processing unit 250 Encoding / Decoding Unit 260 Data transmission and reception unit 270 Control Unit 1001 Processor 1002 Memory 1003 Storage 1004 Communication equipment 1005 Input Device 1006 Output device 1007 Bus

Claims

1. A receiving unit that receives data via a downlink data channel that applies common scheduling to a terminal group; A control unit that assumes that either one of a scheduling common to the terminal group and a scheduling specific to the terminal is applied to the retransmission of the data; A terminal comprising:

2. The terminal according to claim 1 , wherein the downlink data channel is dynamically or semi-permanently scheduled.

3. The terminal according to claim 1 , wherein the control unit applies feedback that transmits both a positive acknowledgement and a negative acknowledgement to the downlink data channel.

4. receiving data via a downlink data channel to which a common scheduling is applied to a group of terminals; A step of assuming that either one of a scheduling common to the terminal group and a scheduling specific to the terminal is applied to the retransmission of the data; A communication method for a terminal including:

5. A transmitter that transmits data via a downlink data channel that applies common scheduling to a terminal group; A control unit that applies either a scheduling common to the terminal group or a scheduling specific to the terminal to the retransmission of the data; A base station comprising:

6. A communication system including a base station and a plurality of terminals, The base station, A transmitter that transmits data via a downlink data channel that applies common scheduling to a terminal group; A control unit that applies, to the retransmission of the data, either one of a scheduling common to the terminal group and a scheduling specific to the terminal, The terminal includes: a receiving unit for receiving the data via the downlink data channel; A communication system comprising: a control unit that assumes that either one of scheduling common to the terminal group and scheduling specific to the terminal is applied to the retransmission of the data.