WO2022215299A1 - 基地局、端末、及び、通信方法 - Google Patents
基地局、端末、及び、通信方法 Download PDFInfo
- Publication number
- WO2022215299A1 WO2022215299A1 PCT/JP2021/047271 JP2021047271W WO2022215299A1 WO 2022215299 A1 WO2022215299 A1 WO 2022215299A1 JP 2021047271 W JP2021047271 W JP 2021047271W WO 2022215299 A1 WO2022215299 A1 WO 2022215299A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- data
- harq
- dai
- feedback
- information
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 290
- 238000004891 communication Methods 0.000 title claims description 56
- 230000008569 process Effects 0.000 claims abstract description 218
- 230000005540 biological transmission Effects 0.000 claims abstract description 92
- 230000001186 cumulative effect Effects 0.000 claims description 4
- 230000006870 function Effects 0.000 description 44
- 238000012545 processing Methods 0.000 description 33
- 238000010586 diagram Methods 0.000 description 29
- 238000007726 management method Methods 0.000 description 13
- 238000005516 engineering process Methods 0.000 description 12
- 230000011664 signaling Effects 0.000 description 10
- 239000000872 buffer Substances 0.000 description 9
- 238000012937 correction Methods 0.000 description 7
- 238000006243 chemical reaction Methods 0.000 description 6
- 238000013507 mapping Methods 0.000 description 6
- 238000012544 monitoring process Methods 0.000 description 5
- 230000008901 benefit Effects 0.000 description 3
- 230000001413 cellular effect Effects 0.000 description 3
- 230000006872 improvement Effects 0.000 description 3
- 238000013468 resource allocation Methods 0.000 description 3
- 238000000926 separation method Methods 0.000 description 3
- 241001633942 Dais Species 0.000 description 2
- 230000004913 activation Effects 0.000 description 2
- 230000002776 aggregation Effects 0.000 description 2
- 238000004220 aggregation Methods 0.000 description 2
- 230000003321 amplification Effects 0.000 description 2
- 230000003139 buffering effect Effects 0.000 description 2
- 125000004122 cyclic group Chemical group 0.000 description 2
- 230000009849 deactivation Effects 0.000 description 2
- 238000009826 distribution Methods 0.000 description 2
- 230000010354 integration Effects 0.000 description 2
- 238000005259 measurement Methods 0.000 description 2
- 238000003199 nucleic acid amplification method Methods 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 230000007704 transition Effects 0.000 description 2
- 241000854291 Dianthus carthusianorum Species 0.000 description 1
- 230000006978 adaptation Effects 0.000 description 1
- 230000003190 augmentative effect Effects 0.000 description 1
- 238000013475 authorization Methods 0.000 description 1
- 230000015572 biosynthetic process Effects 0.000 description 1
- 239000000969 carrier Substances 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000006835 compression Effects 0.000 description 1
- 238000007906 compression Methods 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 238000013523 data management Methods 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000005059 dormancy Effects 0.000 description 1
- 239000003814 drug Substances 0.000 description 1
- 230000009977 dual effect Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005538 encapsulation Methods 0.000 description 1
- 238000001914 filtration Methods 0.000 description 1
- 230000036541 health Effects 0.000 description 1
- 238000009776 industrial production Methods 0.000 description 1
- 238000007689 inspection Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000010363 phase shift Effects 0.000 description 1
- 230000001172 regenerating effect Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 238000000638 solvent extraction Methods 0.000 description 1
- 230000003595 spectral effect Effects 0.000 description 1
- 239000013589 supplement Substances 0.000 description 1
- 238000001356 surgical procedure Methods 0.000 description 1
- 238000003786 synthesis reaction Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 239000013598 vector Substances 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/08—Arrangements for detecting or preventing errors in the information received by repeating transmission, e.g. Verdan system
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/14—Arrangements for detecting or preventing errors in the information received by using return channel in which the signals are sent back to the transmitter to be checked ; echo systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/04—Error control
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
- H04W84/04—Large scale networks; Deep hierarchical networks
- H04W84/06—Airborne or Satellite Networks
Definitions
- the present disclosure relates to base stations, terminals, and communication methods.
- NR new radio access technology
- Non-limiting embodiments of the present disclosure contribute to providing base stations, terminals, and communication methods that can improve the efficiency of retransmission control.
- a base station includes a control circuit that determines information to be set in a signal that notifies the number of data allocations in the retransmission process, based on settings related to feedback for the retransmission process; and a transmission circuit for transmitting the
- efficiency of retransmission control can be improved.
- FIG. 1 Diagram showing an example of Downlink Assignment Index (DAI) and Hybrid automatic repeat request - Acknowledgment (HARQ-ACK) codebook Block diagram showing a configuration example of part of a base station Block diagram showing a configuration example of part of a terminal Block diagram showing an example of the configuration of a base station Block diagram showing an example of the configuration of a terminal Sequence diagram showing an operation example of a base station and a terminal Diagram showing an example of DAI and HARQ-ACK codebook related to setting method 1 Diagram showing an example of DAI and HARQ-ACK codebook related to setting method 2 Diagram showing an example of DAI and HARQ-ACK codebook related to setting method 3 Diagram showing an example of DAI and HARQ-ACK codebook related to setting method 4 A diagram showing an example of a case with blind retransmission and a case without blind retransmission Diagram showing an example of setting an extended New Data Indicator (NDI) Diagram showing a setting example of the retransmission notification bit in the DAI field Diagram of an exemplary architecture of
- Hybrid automatic repeat request In Long Term Evolution (LTE) or 5G NR, for example, Hybrid automatic repeat request (HARQ) is applied to retransmission control during data transmission.
- LTE Long Term Evolution
- 5G NR 5th Generation NR
- HARQ Hybrid automatic repeat request
- the transmitting side performs channel coding (FEC: Forward Error Correction) such as turbo coding or Low Density Parity Check (LDPC) coding on data before transmitting the data.
- FEC Forward Error Correction
- LDPC Low Density Parity Check
- the receiving side saves the received data (for example, a soft decision value) in a buffer (in other words, it is also called buffering, storing, or holding).
- the buffers are also called HARQ soft buffers or simply soft buffers, for example.
- the receiving side synthesizes (soft synthesizes) received data (e.g., resent data or data related to a resend request) and previously received data (in other words, stored data), and outputs the synthesized data. to decrypt.
- received data e.g., resent data or data related to a resend request
- previously received data in other words, stored data
- the receiving side can decode data using data with improved reception quality (for example, SNR: Signal to Noise Ratio).
- the transmitting side can improve the coding gain by transmitting parity bits different from the previous transmission (for example, a different Redundancy version (RV)).
- RV Redundancy version
- continuous data transmission is possible by using multiple processes (for example, also called HARQ process or retransmission process) in consideration of propagation path delay or processing delay on the transmitting side and receiving side. is.
- the receiving side divides the received data, for example, by process ID (also referred to as "PID" or "HARQ process ID”), which is identification information that identifies a process (or data), and stores it in a buffer. do.
- a base station for example, also called eNB or gNB
- eNB also called eNB or gNB
- NDI New Data Indicator
- RV New Data Indicator
- a terminal performs reception processing (eg, soft combining processing) of data (eg, Physical Downlink Shared Channel (PDSCH)) based on information about HARQ notified from the base station.
- reception processing eg, soft combining processing
- data eg, Physical Downlink Shared Channel (PDSCH)
- HARQ-ACK HARQ-Acknowledgment
- HARQ-ACK may be sent using, for example, an uplink control channel (eg, Physical Uplink Control Channel (PUCCH)) or an uplink data channel (eg, Physical Uplink Shared Channel (PUSCH)).
- PUCCH Physical Uplink Control Channel
- PUSCH Physical Uplink Shared Channel
- the base station may specify, for example, a slot in which the terminal transmits HARQ-ACK in downlink control information (for example, Downlink Control Information (DCI)) that allocates PDSCH.
- DCI Downlink Control Information
- uplink slots are set to part of the time resources (in other words, limited), so HARQ-ACKs for each of a plurality of PDSCHs are identical. may be collectively transmitted in uplink slots.
- FDD Frequency Division Duplex
- CA Carrier Aggregation
- CC Component Carrier
- PDSCHs transmitted in a cell are sent together in one CC in one slot.
- the terminal may transmit, for example, a bit string of HARQ-ACK bits containing multiple HARQ-ACKs (hereinafter referred to as "HARQ-ACK codebook") on PUCCH or PUSCH.
- HARQ-ACK codebook a bit string of HARQ-ACK bits containing multiple HARQ-ACKs
- the number of HARQ-ACK bits transmitted in a given slot may vary, for example, depending on the number of PDSCH allocations.
- NR Rel.15 or Rel.16 (hereafter also referred to as NR Rel.15/16), for example, "Type 1 HARQ-ACK codebook" in which the HARQ-ACK codebook size is semi-statically determined, and , a "Type 2 HARQ-ACK codebook” is defined in which the HARQ-ACK codebook size is determined dynamically (see, for example, section 9 of Non-Patent Document 2).
- the HARQ-ACK codebook size is reduced to the PDSCH allocation. set to a fixed size regardless of
- the HARQ-ACK codebook contains HARQ-ACK bits corresponding to slots or CCs with PDSCH allocation.
- HARQ-ACK bits corresponding to slots or CCs with no PDSCH allocation are not included in the HARQ-ACK codebook. For example, based on whether or not DCI including information on PDSCH allocation is received in each slot or CC, the terminal determines whether or not there is a HARQ-ACK bit for the PDSCH received in that slot and CC.
- the terminal when the terminal fails to receive DCI (for example, decoding error or false detection), it makes an error in determining whether there is a HARQ-ACK bit, and recognizes HARQ (for example, HARQ-ACK codebook size).
- DCI for example, decoding error or false detection
- HARQ for example, HARQ-ACK codebook size
- DAI Downlink Assignment Index
- DAI may notify the terminal of information on the number of PDSCH allocations.
- the terminal can specify the correct HARQ-ACK codebook size even if it misses receiving DCI, for example.
- identity may be read interchangeably with other terms such as “discrimination”, “identification”, “recognition”, “determination”, and “estimation”.
- DAI includes "Counter-DAI (C-DAI)” that counts slots and CCs with PDSCH allocation up to the slot and CC to which the DAI is notified, and total PDSCH allocation up to the slot. "Total-DAI (T-DAI)” indicating the number is included.
- C-DAI Counter-DAI
- T-DAI Total-DAI
- C-DAI is, for example, the current CC and slot (or Serving cell and PDCCH monitoring occasion) up to PDSCH reception (or PDSCH allocation) slot and CC pairs (or Serving cell and PDCCH monitoring occasion pairs).
- T-DAI is, for example, a pair of slots and CCs (or a pair of serving cell and PDCCH monitoring occurrence) where there is PDSCH reception (or PDSCH allocation) up to the current slot (or PDCCH monitoring occurrence). You may indicate the total number.
- C-DAI may be incremented each time PDSCH is allocated in DCI in each slot and CC.
- T-DAI may indicate the total number of PDSCH allocations up to (including) the slot in which the DAI is notified.
- Each of C-DAI and T-DAI may, for example, be represented by two bits.
- C-DAI and T-DAI may be capable of counting four or more numbers even when represented by two bits.
- FIG. 1 is a diagram showing an example of DAI (for example, C-DAI and T-DAI) included in DCI that allocates PDSCH and HARQ-ACK codebook transmitted by a terminal.
- DAI for example, C-DAI and T-DAI
- the terminal for example, in each slot (slot1 and slot2 in FIG. 1) and each CC (CC1 to CC4 in FIG. 1) DCI including DAI (C-DAI, T-DAI) may receive
- terminals are assigned PDSCHs in CC1 and CC3 of slot1
- PDSCHs are assigned in CC1, CC2 and CC4 of slot2.
- the terminal receives DAI including C-DAI indicating the count value of the number of PDSCH assignments and T-DAI indicating the total number of PDSCH assignments up to the relevant slot in slots and CCs with PDSCH assignments. you can
- the terminal can identify that a DCI reception error has occurred in CC1 of slot2 based on DAI (4, 5) received in CC2 of slot2, for example. Accordingly, terminal 200 can feed back a HARQ-ACK codebook including HARQ-ACK bits for five PDSCHs allocated by base station 100, as shown in FIG. 1, for example. In this way, the DAI can prevent the terminal 200 from erroneously recognizing the HARQ-ACK codebook size.
- NTN Non-Terrestrial Network
- LTE and NR Rel.15/16 are specified as radio access technologies for terrestrial networks.
- NR is being considered for extension to non-terrestrial networks (NTN) such as communication using satellites or high-altitude pseudo-satellites (HAPS) (for example, Non-Patent Document 1) .
- NPN non-terrestrial networks
- HAPS high-altitude pseudo-satellites
- the satellite coverage area eg, one or more cells
- the round trip time RTT: Round Trip Time
- the altitude of the satellite for example, up to about 36000 km
- the angle viewed from the terminal that is, the positional relationship between the satellite and the terminal.
- Non-Patent Document 1 states that the maximum round-trip time (RTT) of radio wave propagation between a base station and a terminal is about 540 ms.
- retransmission control is based on individual HARQ-ACK feedback for HARQ processes. Therefore, in NTN with large RTT compared to terrestrial networks, a large number of HARQ processes can be used for continuous data transmission. Also, for example, NTN considers disabling HARQ-ACK feedback for each HARQ process individually (see Non-Patent Document 1, for example).
- HARQ-ACK is transmitted from the terminal, and the base station may schedule based on HARQ-ACK.
- HARQ-ACK is not transmitted from the terminal, and the base station does not wait for reception of HARQ-ACK. You may schedule the following data in
- the HARQ-ACK bit for the PDSCH of the feedback-disabled HARQ process is not included in the HARQ-ACK codebook.
- the content of the information signaled (or indicated) in the DAI field included in the DCI that schedules (eg, allocates) feedback-disabled HARQ processes has not been fully considered.
- DAIs e.g., C-DAI and T-DAI
- information to be set in DAI may be determined (or controlled) based on HARQ feedback settings (eg, enabled or disabled).
- a communication system includes base station 100 and terminal 200 .
- FIG. 2 is a block diagram showing a configuration example of part of the base station 100.
- a control unit for example, corresponding to a control circuit
- controls data in the retransmission process for example, HARQ process
- settings for example, whether to enable or disable
- Determine the information to be set in the signal for example, DAI
- a transmission unit for example, corresponding to a transmission circuit
- transmits, for example, information determined in the signal for example, DAI).
- FIG. 3 is a block diagram showing a configuration example of part of the terminal 200.
- a receiving unit eg, corresponding to a receiving circuit
- Receive in a signal eg, DAI
- a control unit e.g., corresponding to a control circuit controls reception of data based on the information.
- FIG. 4 is a block diagram showing an example of the configuration of base station 100 according to this embodiment.
- Base station 100 includes, for example, retransmission control section 101, encoding/modulation section 102, radio transmission section 103, antenna 104, radio reception section 105, demodulation/decoding section 106, and HARQ-ACK determination section 107. And prepare.
- At least one of the retransmission control section 101, the encoding/modulation section 102, the demodulation/decoding section 106, and the HARQ-ACK determination section 107 shown in FIG. 4 may be included in the control section shown in FIG. 2, for example. 4 may be included in the transmitter shown in FIG. 2, for example.
- the retransmission control section 101 controls retransmission of transmission data (for example, PDSCH).
- transmission data for example, PDSCH
- retransmission control section 101 for transmission data, HARQ process ID, NDI, RV, information indicating HARQ-ACK transmission timing (for example, PDSCH-to-HARQ_feedback timing indicator), and DAI (C-DAI, T- DAI) may be generated.
- Retransmission control section 101 outputs the generated information on retransmission control to encoding/modulation section 102 .
- HARQ-ACK feedback settings for example, whether feedback is enabled or disabled
- HARQ process IDs may be associated in advance.
- Information related to association between feedback configuration and HARQ process ID may be notified (or configured) to terminal 200 by, for example, higher layer signaling or downlink control information.
- the base station 100 may implicitly notify the terminal 200 of either feedback enablement or disablement by, for example, reporting the HARQ process ID. Note that notification of the feedback configuration is not limited to the example described above, and base station 100 may explicitly notify terminal 200 of information regarding the feedback configuration.
- retransmission control section 101 may determine information to be set in the DAI field corresponding to the HARQ process, for example, based on the HARQ-ACK feedback setting for each HARQ process. An example of how to set the DAI field will be described later.
- retransmission control section 101 determines retransmission of transmission data (or transmission of new data), and encodes the presence or absence of retransmission of transmission data. • You may instruct the modulating section 102 .
- Encoding/modulation unit 102 for example, the input transmission data (e.g., transport block) turbo code, error correction encoding such as LDPC code or polar code, and Quarter Phase Shift Keying (QPSK) or Quadrature Amplitude Modulation (QAM), and outputs the modulated signal to radio transmission section 103 .
- the input transmission data e.g., transport block
- turbo code e.g., error correction encoding
- error correction encoding such as LDPC code or polar code
- QPSK Quarter Phase Shift Keying
- QAM Quadrature Amplitude Modulation
- the encoding/modulation section 102 may store transmission data in a buffer, for example.
- the encoding/modulation section 102 may perform the same processing as described above on transmission data (for example, retransmission data) stored in the buffer.
- the encoding/modulation unit 102 may delete the corresponding transmission data stored in the buffer.
- the encoding/modulating section 102 encodes and modulates downlink control information (for example, DCI), and outputs the modulated signal to the radio transmitting section 103 .
- DCI includes, for example, time and frequency resource allocation information, information on coding and modulation schemes (e.g., Modulation and Coding Scheme (MCS) information) data allocation information, and HARQ process input from retransmission control unit 101
- MCS Modulation and Coding Scheme
- MCS Modulation and Coding Scheme
- HARQ process input from retransmission control unit 101 Information related to retransmission control such as ID, NDI, RV, PDSCH-to-HARQ_feedback timing indicator or DAI (C-DAI, T-DAI) may be included.
- transmission data may correspond to PDSCH
- data allocation information may correspond to DCI or PDCCH.
- Radio transmission section 103 for example, performs transmission processing such as D/A conversion, up-conversion, and amplification on the signal input from encoding/modulation section 102, and transmits the radio signal after transmission processing from antenna 104. Send.
- Radio receiving section 105 for example, down-converts and A/Ds data signals (eg, PUSCH) and control signals (eg, HARQ-ACK information) from terminal 200 received via antenna 104. Reception processing such as conversion is performed, and the signal after reception processing is output to demodulation/decoding section 106 .
- data signals eg, PUSCH
- control signals eg, HARQ-ACK information
- Demodulation/decoding section 106 performs channel estimation, demodulation processing, and decoding processing on the received signal input from radio reception section 105, for example. For example, when the received signal is data, demodulation/decoding section 106 outputs the received data, and when the received signal is HARQ-ACK information, outputs HARQ-ACK information to HARQ-ACK determination section 107. do.
- HARQ-ACK decision section 107 for example, based on the HARQ-ACK information (for example, HARQ-ACK codebook) input from demodulation/decoding section 106, the error for each transmitted transmission data (for example, transport block) (for example, ACK or NACK).
- the HARQ-ACK information for example, HARQ-ACK codebook
- the error for each transmitted transmission data for example, transport block
- HARQ-ACK determination section 107 may instruct retransmission control section 101 to retransmit data.
- HARQ-ACK determination section 107 may instruct retransmission control section 101 not to retransmit data.
- base station 100 When Type 2 HARQ-ACK codebook is set for terminal 200, base station 100, for example, receives HARQ-ACK of a feedback-enabled HARQ process, and receives HARQ-ACK of a feedback-disabled HARQ process. -Don't receive ACK.
- HARQ-ACK determination section 107 may determine whether or not there is an error in HARQ-ACK of a feedback-enabled HARQ process.
- which type of HARQ-ACK codebook is applied to each HARQ process may be notified (or set) in advance to the terminal 200 .
- FIG. 5 is a block diagram showing an example of the configuration of terminal 200 according to the present embodiment.
- Terminal 200 includes, for example, antenna 201 , radio reception section 202 , demodulation/decoding section 203 , HARQ-ACK generation section 204 , encoding/modulation section 205 , and radio transmission section 206 .
- At least one of the demodulator/decoder 203, the HARQ-ACK generator 204, and the encoder/modulator 205 shown in FIG. 5 may be included in the controller shown in FIG. 3, for example. 5 may be included in the receiver shown in FIG. 3, for example.
- Radio receiving section 202 for example, down-converts and A/Ds data signals (eg, PDSCH) and control signals (eg, PDCCH or DCI) from base station 100 received via antenna 201. It performs reception processing such as conversion, and outputs the signal after reception processing to demodulation/decoding section 203 .
- data signals eg, PDSCH
- control signals eg, PDCCH or DCI
- the demodulation/decoding section 203 performs channel estimation, demodulation processing, and decoding processing on the received signal input from the radio reception section 202, for example. For example, when the received signal is data, the demodulator/decoder 203 may perform processing based on data allocation information (for example, modulation scheme and coding rate) included in the control signal. Also, the demodulation/decoding section 203 may determine whether the received data is first transmission data (or new data) or retransmission data, for example, based on the NDI included in the control signal. For example, in the case of initial transmission data, demodulation/decoding section 203 may perform error correction decoding and perform Cyclic Redundancy Check (CRC) determination.
- CRC Cyclic Redundancy Check
- the demodulation/decoding section 203 may perform error correction decoding after combining the data stored in the buffer and the received data, and perform CRC determination.
- Demodulation/decoding section 203 outputs the CRC determination result to HARQ-ACK generation section 204, for example.
- HARQ-ACK generating section 204 generates HARQ-ACK information (for example, HARQ-ACK codebook) based on, for example, the CRC determination result input from demodulating/decoding section 203, and outputs it to encoding/modulating section 205. do.
- HARQ-ACK information for example, HARQ-ACK codebook
- the HARQ-ACK generation unit 204 generates HARQ-ACK information (eg, ACK or NACK) based on the CRC determination result, for example, for feedback-enabled HARQ process data. For example, HARQ-ACK generating section 204 generates ACK when CRC OK (eg, no error), and generates NACK when CRC NG (eg, error exists). Also, for example, when the terminal 200 receives a plurality of transport blocks or code blocks, the HARQ-ACK generation unit 204 generates HARQ-ACK for each of the plurality of transport blocks or code blocks, and generates a plurality of HARQ- A HARQ-ACK code block consisting of ACKs may be generated.
- HARQ-ACK information eg, ACK or NACK
- the HARQ-ACK generation unit 204 for example, for slots and CCs without data allocation, or for data of HARQ processes with feedback disabled, CRC decoding result NACK may be inserted into the HARQ-ACK codebook regardless of
- the HARQ-ACK generation unit 204 when the Type 2 HARQ-ACK codebook is set, the HARQ-ACK generation unit 204 generates HARQ-ACKs for slots and CCs without data allocation, or for data of HARQ processes with feedback disabled, for example, HARQ- It does not have to be included in the ACK codebook.
- the HARQ-ACK generator 204 may include, for example, slots and CCs with data allocation, or HARQ-ACKs for data of feedback-enabled HARQ processes in the HARQ-ACK codebook.
- the coding/modulation section 205 performs, for example, error correction coding and modulation processing on input transmission data (eg, transport block), and outputs the modulated signal to the radio transmission section 206 . Also, the coding/modulation unit 205 performs error correction coding and modulation processing on the HARQ-ACK information input from the HARQ-ACK generation unit 204, for example, and transmits the modulated signal to the radio transmission unit 206. Output.
- Radio transmission section 206 for example, performs transmission processing such as D/A conversion, up-conversion, and amplification on the signal input from encoding/modulation section 205, and transmits the radio signal after transmission processing from antenna 201. Send.
- terminal 200 may transmit HARQ-ACK information at timing based on the PDSCH-to-HARQ_feedback timing indicator included in the control signal from base station 100, for example. Also, terminal 200 sets the HARQ-ACK codebook size, for example, based on the DAI (C-DAI, T-DAI) included in the DCI received last among the DCIs that allocate the PDSCH of the HARQ-ACK transmission timing. You can
- FIG. 6 is a sequence diagram showing an operation example of base station 100 and terminal 200 in this embodiment.
- the base station 100 sets DAI (eg, C-DAI and T-DAI) based on, for example, allocation of downlink data (eg, PDSCH) for the terminal 200 (S101).
- DAI eg, C-DAI and T-DAI
- Base station 100 sets information to be set in the DAI field in the HARQ process, for example, based on the setting (for example, one of feedback enablement and feedback disablement) regarding feedback of each HARQ process corresponding to PDSCH allocation. You can decide.
- DAI eg, C-DAI and T-DAI
- the base station 100 transmits DCI including DAI to the terminal 200 (S102).
- Terminal 200 receives DCI including DAI from base station 100 .
- the base station 100 transmits downlink data to the terminal 200 (S103).
- Terminal 200 may receive downlink data, for example, based on data allocation information included in DCI.
- the terminal 200 may perform reception processing such as error correction decoding and CRC determination on the received downlink data (S104). For example, the terminal 200 uses the DAI (eg, at least one of C-DAI and T-DAI) corresponding to the feedback-disabled HARQ process, based on the downlink data (eg, data corresponding to the HARQ process) receive processing (e.g., determination of HARQ-ACK codebook size).
- DAI eg, at least one of C-DAI and T-DAI
- receive processing e.g., determination of HARQ-ACK codebook size
- the terminal 200 may generate HARQ-ACK information, for example, based on the result of downlink data reception processing (eg, CRC determination result) (S105). For example, terminal 200 may generate a HARQ-ACK codebook including HARQ-ACKs for downlink data corresponding to feedback-enabled HARQ processes. In other words, the terminal 200 does not have to include HARQ-ACK information for downlink data corresponding to feedback-disabled HARQ processes in the HARQ-ACK codebook.
- HARQ-ACK information for example, based on the result of downlink data reception processing (eg, CRC determination result) (S105).
- terminal 200 may generate a HARQ-ACK codebook including HARQ-ACKs for downlink data corresponding to feedback-enabled HARQ processes.
- the terminal 200 does not have to include HARQ-ACK information for downlink data corresponding to feedback-disabled HARQ processes in the HARQ-ACK codebook.
- the terminal 200 transmits the generated HARQ-ACK information (eg, HARQ-ACK codebook) to the base station 100 (S106).
- HARQ-ACK information eg, HARQ-ACK codebook
- the base station 100 performs retransmission control based on the HARQ-ACK information transmitted from the terminal 200 (S107).
- DAI for example, an example of information to be set in the DAI field
- Setting method 1 to setting method 4 will be described below as examples.
- ⁇ Setting method 1> In setting method 1, the C-DAI field in the DCI that allocates a feedback-enabled HARQ process, for example, as specified in NR Rel. A C-DAI value indicating the count value of slots and CCs (or the count value of the number of allocated data) may be included. Also, in setting method 1, the T-DAI field in the DCI that allocates feedback-enabled HARQ processes, for example, as specified in NR Rel. A T-DAI value that indicates the number of data allocations may be included.
- each of the C-DAI field and the T-DAI field in the DCI that allocates feedback-disabled HARQ processes for example, similarly to the feedback-enabled HARQ process, the C-DAI value and A T-DAI value may be included.
- the C-DAI value and T-DAI value in this case may each be a value that does not count (in other words, does not include) data allocation in feedback-disabled HARQ processes.
- the base station 100 may transfer information (eg, C-DAI value and T-DAI value) about the number of data allocations in feedback-enabled HARQ processes to signals for feedback-disabled HARQ processes (eg, C -DAI field and T-DAI field).
- C-DAI field and T-DAI field in the DCI that allocates a feedback-disabled HARQ process contain the C-DAI field in the feedback-enabled HARQ process immediately before the allocation of the feedback-disabled HARQ process.
- a DAI value and a T-DAI value may be set.
- FIG. 7 is a diagram showing an example of the DAI field and HARQ-ACK codebook according to setting method 1.
- CC1 and CC3 of slot1 and CC1 and CC4 of slot2 transmit and receive DCI that allocates feedback-enabled HARQ processes, and CC2 of slot2 allocates feedback-disabled HARQ processes. DCI is sent and received.
- the base station 100 assigns a count value (or cumulative number) and a T-DAI value indicating the total number of data allocations for each slot may be set.
- the base station 100 does not have to count data allocation for feedback-disabled HARQ processes, for example, in setting the DCI C-DAI value for allocating feedback-enabled HARQ processes. Also, the base station 100 may not count data allocation for feedback-disabled HARQ processes, for example, in setting the T-DAI value of DCI for allocating feedback-enabled HARQ processes. In other words, base station 100 counts data allocations in setting C-DAI and T-DAI values in feedback-enabled HARQ processes, excluding data allocations in feedback-disabled HARQ processes. you can
- the T-DAI value is set to 2
- the allocation of feedback-disabled HARQ processes in CC2 of slot2 is counted.
- T-DAI value 4
- the C-DAI value is not counted (in other words, incremented) without counting the assignments of feedback-disabled HARQ processes in CC2 of slot2.
- the base station 100 for example, in the C-DAI field and the T-DAI field of DCI that allocates a feedback-disabled HARQ process, does not count the allocation of the HARQ process and does not count the HARQ process that is feedback-enabled. May be set to the same value as the C-DAI and T-DAI values of the process.
- the C-DAI value and T-DAI value in CC2 of slot2 are the same values as the C-DAI value and T-DAI value in CC1 of slot2, which is the previous allocation (3, 4) may be set to
- the terminal 200 does not have to include the HARQ-ACK of the feedback-disabled HARQ process in the HARQ-codebook.
- the terminal 200 for example, based on the information of the C-DAI field and the T-DAI field of DAI included in the DCI that allocates the feedback-disabled HARQ process, HARQ- You may specify the size of the HARQ-codebook including the ACK.
- terminal 200 fails to receive DCI in CC1 of slot2
- the terminal 200 for example, based on DAI (3, 4) of the feedback-disabled HARQ process received in CC2 of slot2, CC1 of slot2 to which data in the feedback-enabled HARQ process is assigned.
- DAI (3, 4) of the feedback-disabled HARQ process received in CC2 of slot2
- CC1 of slot2 to which data in the feedback-enabled HARQ process is assigned it can be identified that a DCI reception error has occurred.
- terminal 200 can identify that there is a feedback-enabled HARQ process assignment in CC1 of slot2 based on DAI (3, 4) received in CC2 of slot2. Therefore, as shown in FIG. 7, the terminal 200 can specify the size of the HARQ-ACK codebook including 4 feedback-enabled HARQ-ACK bits.
- terminal 200 assigns feedback-disabled HARQ processes even when there is a DCI reception error (or reception error) that allocates feedback-enabled HARQ processes.
- the HARQ-codebook size can be specified. Therefore, it is possible to reduce the probability of disagreement in recognition of the HARQ-codebook size between base station 100 and terminal 200 .
- the same DCI size can be set between the DCI that allocates feedback-disabled HARQ processes and the DCI that allocates feedback-enabled HARQ processes. It is possible to suppress an increase in the number of times of blind decoding at the time of reception.
- the C-DAI and T-DAI fields of the DCI that allocate feedback-disabled HARQ processes may be reserved.
- the base station 100 for example, in the C-DAI field and the T-DAI field of the DAI for feedback-disabled HARQ process, C-DAI value and T-DAI value (for example, information about the number of PDSCH allocation ) need not be set.
- base station 100 sets the DAI value (for example, information about the number of PDSCH allocations) and Different information may be set.
- DAI value for example, information about the number of PDSCH allocations
- Different information may be set.
- FIG. 8 is a diagram showing an example of the DAI field and HARQ-ACK codebook according to setting method 2.
- the base station 100 uses feedback-disabled HARQ processes as in setting method 1. You don't have to count allocations of data for processes.
- base station 100 allocates a feedback-disabled HARQ process, for example, in DCI (for example, DCI in CC2 of slot2), where C-DAI field and T-DAI field included in DAI , the DAI value (for example, the C-DAI value and the T-DAI value) need not be set (or notified).
- DCI for example, DCI in CC2 of slot2 in FIG. 8
- a specified value for example, all 0
- the terminal 200 may, for example, ignore the value of the DAI field included in the DCI that allocates HARQ processes with feedback disabled. In other words, terminal 200 may perform HARQ-ACK-related processing (eg, specify HARQ-ACK codebook size) based on, for example, the value of the DAI field included in the DCI that allocates feedback-enabled HARQ processes. .
- HARQ-ACK-related processing eg, specify HARQ-ACK codebook size
- terminal 200 sets the values to be set in the C-DAI field and T-DAI field (for example, reserved fields) included in the DCI that allocates feedback-disabled HARQ processes, as described later, It may be used for purposes other than the use related to notification of the number of downlink data allocations.
- the DAI field for feedback-disabled HARQ processes for example, a field in which no DAI value is set
- at least a part of the C-DAI field and the T-DAI field has a specified value (for example, the base Known information) may be set (or inserted) between the station 100 and the terminal 200 .
- Terminal 200 may use the specified value as a virtual CRC, for example.
- the virtual CRC can reduce the occurrence of erroneous CRC determination in terminal 200 .
- base station 100 can, for example, suppress an increase in DCI size and notify terminal 200 of parameters related to data transmission.
- the same DCI size can be set between the DCI that allocates feedback-disabled HARQ processes and the DCI that allocates feedback-enabled HARQ processes. It is possible to suppress an increase in the number of times of blind decoding at the time of reception.
- the C-DAI field of the DCI that allocates feedback-disabled HARQ processes is reserved, and the T-DAI field contains a T-DAI value that indicates the total number of data allocations up to the slot in which the DAI is notified. may be included.
- the base station 100 may not set the C-DAI value in some fields (eg, the C-DAI field) of the DAI for feedback-disabled HARQ processes, for example, and may not set the C-DAI value in other fields (eg, , T-DAI field) may be set to the T-DAI value for feedback-enabled HARQ processes.
- the base station 100 may set information different from the C-DAI value in the C-DAI field (for example, the field in which the DAI value is not set) for the feedback-disabled HARQ process.
- information different from the C-DAI value in the C-DAI field for example, the field in which the DAI value is not set
- An example of how to use the C-DAI field of DCI for allocating feedback-disabled HARQ processes will be described later.
- FIG. 9 is a diagram showing an example of the DAI field and HARQ-ACK codebook according to setting method 3.
- base station 100 sets a C-DAI value in the C-DAI field included in DCI that allocates feedback-disabled HARQ processes (for example, DCI in CC2 of slot2). (or notice).
- the C-DAI field may be set with a specified value (for example, all 0), or information for a different purpose than information on the number of data allocations is set.
- the base station 100 determines that feedback is enabled in the T-DAI field included in DCI that allocates feedback-disabled HARQ processes (eg, DCI in CC2 of slot2). may set the T-DAI value in the HARQ process.
- the T-DAI value may be set to the same value as the T-DAI value of CC1 of slot2, which is allocated immediately before.
- the terminal 200 may, for example, ignore the value of the C-DAI field included in the DCI that allocates HARQ processes with feedback disabled. In other words, the terminal 200, for example, based on the value of the DAI field included in the DCI that allocates feedback-enabled HARQ processes and the value of the T-DAI field included in the DCI that allocates feedback-disabled HARQ processes, processing for HARQ-ACK (eg, specifying the HARQ-ACK codebook size).
- terminal 200 assigns a value set in a C-DAI field (for example, a reserved field) included in DCI that allocates feedback-disabled HARQ processes, as described later, to downlink data allocation. You may use it for other uses different from the use regarding the notification of a number.
- a C-DAI field for example, a reserved field
- At least a part of the C-DAI field (for example, a field in which the DAI value is not set) for the feedback-disabled HARQ process has a specified value (for example, between base station 100 and terminal 200 known information) may be set (or inserted).
- Terminal 200 may use the specified value as a virtual CRC, for example.
- the virtual CRC can reduce the occurrence of erroneous CRC determination in terminal 200 .
- the feedback-disabled HARQ process may be set for data transmission in .
- base station 100 can, for example, suppress an increase in DCI size and notify terminal 200 of parameters related to data transmission.
- a prescribed number of bits for example, 2 bits in NR Rel.15/16
- Parameters related to data transmission can be notified regardless of the setting of the number of CCs.
- terminal 200 for example, based on information (for example, T-DAI value) set in the T-DAI field of DCI that allocates feedback-invalidated HARQ processes, HARQ-codebook size can be determined. For this reason, for example, even if a reception error (or a reception error) of DCI that allocates a feedback-enabled HARQ process occurs, the terminal 200 does not change the T-DAI field of DCI that allocates a feedback-disabled HARQ process. Based on the value, it is possible to determine the HARQ-ACK codebook size. Therefore, it is possible to reduce the probability of disagreement in recognition of the HARQ-ACK codebook size between base station 100 and terminal 200 .
- information for example, T-DAI value
- the T-DAI value indicates the total number of data allocations up to the slot in which the T-DAI value is notified (for example, a value that can correspond to the HARQ-ACK codebook size).
- DAI Compared to DAI, it is effective in identifying the HARQ-ACK codebook size. For example, in the example of FIG. 9, even if terminal 200 misses DCI reception in at least one of CC1 and CC4 of slot2, terminal 200 receives DAI (-, 4) in CC2 of slot2, Since we can determine that the total number of data allocations up to slot2 is 4, we can determine the size of the HARQ-ACK codebook containing 4 feedback-enabled HARQ-ACKs.
- the same DCI size can be set between the DCI that allocates feedback-disabled HARQ processes and the DCI that allocates feedback-enabled HARQ processes. It is possible to suppress an increase in the number of times of blind decoding at the time of reception.
- the C-DAI field of the DCI that allocates feedback-disabled HARQ processes has a C-DAI value that indicates the number of data allocations (for example, cumulative number) up to the slot and CC to which the DAI is notified. included, the T-DAI field may be reserved.
- the base station 100 may not set the T-DAI value in some fields (eg, the T-DAI field) of the DAI for feedback-disabled HARQ processes, and may not set the T-DAI value in other fields (eg, , C-DAI field) may be set to the C-DAI value for feedback-enabled HARQ processes.
- the base station 100 may set information different from the T-DAI value in the T-DAI field (for example, the field in which the DAI value is not set) for the feedback-disabled HARQ process.
- information different from the T-DAI value in the T-DAI field for example, the field in which the DAI value is not set
- An example of how to use the T-DAI field of DCI for allocating feedback-disabled HARQ processes will be described later.
- FIG. 10 is a diagram showing an example of the DAI field and HARQ-ACK codebook according to setting method 4.
- the base station 100 sets the T-DAI value in the T-DAI field included in the DCI that allocates feedback-disabled HARQ processes (for example, the DCI in CC2 of slot2). (or notice).
- the T-DAI field may be set with a specified value (for example, all 0), or information for a different application than information on the number of data allocations is set.
- the base station 100 determines that feedback is enabled in the C-DAI field included in DCI that allocates feedback-disabled HARQ processes (eg, DCI in CC2 of slot2). may set the C-DAI value in the HARQ process.
- the C-DAI value may be set to the same value as the C-DAI value of CC1 of slot2, which is allocated immediately before.
- the terminal 200 may, for example, ignore the value of the T-DAI field included in the DCI that allocates feedback-disabled HARQ processes. In other words, the terminal 200, for example, based on the value of the DAI field included in the DCI that allocates feedback-enabled HARQ processes and the value of the C-DAI field included in the DCI that allocates feedback-disabled HARQ processes, processing for HARQ-ACK (eg, specifying the HARQ-ACK codebook size).
- terminal 200 assigns a value set in a T-DAI field (for example, a reserved field) included in DCI that allocates a feedback-disabled HARQ process to a value set in downlink data allocation, as will be described later. You may use it for other uses different from the use regarding the notification of a number.
- a T-DAI field for example, a reserved field
- a specified value for example, between base station 100 and terminal 200 known information
- Terminal 200 may use the specified value as a virtual CRC, for example.
- the virtual CRC can reduce the occurrence of erroneous CRC determination in terminal 200 .
- the feedback-disabled HARQ process may be set for data transmission in .
- base station 100 can, for example, suppress an increase in DCI size and notify terminal 200 of parameters related to data transmission.
- terminal 200 for example, based on information (for example, C-DAI value) set in the C-DAI field of DCI that allocates feedback-invalidated HARQ processes, HARQ-codebook size can be determined. For this reason, for example, even if a DCI reception error (or a reception error) that allocates a feedback-enabled HARQ process occurs, the terminal 200 can set the C-DAI field of DCI that allocates a feedback-disabled HARQ process. Based on the value, it is possible to determine the HARQ-ACK codebook size. Therefore, it is possible to reduce the probability of disagreement in recognition of the HARQ-ACK codebook size between base station 100 and terminal 200 .
- information for example, C-DAI value
- terminal 200 even if terminal 200 fails to receive DCI in CC1 of slot2, terminal 200 receives data up to CC2 of slot2 based on DAI (3, -) received in CC2 of slot2. Since we can identify that the number of allocations is 3, we may be able to identify the size of the HARQ-ACK codebook.
- the same DCI size can be set between the DCI that allocates feedback-disabled HARQ processes and the DCI that allocates feedback-enabled HARQ processes. It is possible to suppress an increase in the number of times of blind decoding at the time of reception.
- setting method 2 setting method 3, and setting method 4, in at least a part of the C-DAI field and the T-DAI field (for example, a field in which no DAI value is set), An example in which information used for purposes other than notification of information is set will be described.
- data transmission in a feedback-disabled HARQ process does not provide HARQ retransmission and combining gains, so more robust transmission parameters compared to data transmission in a feedback-enabled HARQ process, or Transmissions based on transmission parameters that achieve lower error rates (eg, Block Error Rate (BLER)) are expected.
- BLER Block Error Rate
- a field reserved in the DAI may be set with, for example, a parameter relating to the number of repetitions (or repetition number) in data transmission of feedback-disabled HARQ processes.
- terminal 200 may use the repetition number notified (or set) by "pdsch-AggregationFactor” or "repetitionNumber” of higher layer parameters (eg, RRC parameters). .
- the terminal 200 uses the repetition number notified (or set) in the DAI field (for example, at least one of the C-DAI field and the T-DAI field).
- the repetition number notified by the DAI field for example, any one of multiple candidates for the repetition number separately set in terminal 200 by the RRC parameter may be notified, and is set in terminal 200 by the RRC parameter. Multiple candidates and different repetition numbers may be used.
- the repetition number notified by the DAI field may be set higher than the repetition number set for feedback-enabled HARQ processes. This allows lower BLER to be achieved in transmissions by feedback-disabled HARQ processes without HARQ retransmissions.
- a field reserved in the DAI may be set, for example, with a parameter relating to the MCS level used for data transmission of feedback-disabled HARQ processes.
- MCS index table multiple MCS tables (eg, MCS index table) are defined, as described in section 5.1.3 of Non-Patent Document 3, for example.
- MCS levels for example, modulation order
- Table 2 that defines MCS levels up to 256QAM
- Table 3 is defined, which defines up to the MCS level with a coding rate lower than that of Table 1.
- a parameter indicating any one of Tables 1 to 3 may be set in the field reserved in DAI.
- the terminal 200 uses the MCS based on the MCS table notified (or set) in the DAI field (for example, at least one of the C-DAI field and the T-DAI field).
- a level eg, modulation scheme and coding rate
- parameters related to MCS levels different from the MCS levels defined in Tables 1 to 3, for example, may be set in the fields reserved in DAI.
- a field reserved in DAI includes an encoding rate (or spectral efficiency ) may be set for the MCS level.
- a field reserved in DAI includes a ratio (for example, 1/2, 1/4, 1/8, or 1/16) may be set. Note that the number of bits of the value indicating the ratio to the coding rate is not limited to 2 bits.
- an example of a method of achieving lower BLER in transmission by a feedback-disabled HARQ process is a method in which the base station 100 transmits the same data (for example, PDSCH) multiple times by blind retransmission.
- base station 100 transmits retransmission data to terminal 200 without receiving HARQ-ACK from terminal 200 .
- terminal 200 may determine whether transmission data is initial transmission (or new transmission) or retransmission, for example, based on the bits of NDI included in DCI for data allocation.
- FIG. 11 is a diagram showing an example of a case with blind retransmission (FIG. 11(a)) and a case without blind retransmission (FIG. 11(b)).
- the first data eg, new Data
- the terminal 200 may be notified of the NDI.
- the terminal 200 determines that the retransmitted data and the previously received data are retransmitted data. and may be combined for decoding.
- the second and third data eg, new data
- the previously notified NDI value is toggled. (or incremented) and notified to the terminal 200 .
- the NDI is 1 bit
- the second data for example, new data
- the NDI is different from the NDI when the first data is transmitted (FIG. 11(b) In 1)
- the terminal 200 is notified.
- a value different from the NDI when transmitting the second data that is, the same value as the NDI when transmitting the first data (Fig. 11(b) Then 0) is notified to the terminal 200 .
- parameters for blind retransmissions in HARQ processes with feedback disabled may be set in the fields reserved in DAI.
- a field reserved in DAI may be set with a parameter indicating whether or not data to be allocated is retransmission data (for example, an extended DAI or a retransmission notification bit, which will be described later).
- the NDI field may be extended using a reserved field of DAI. For example, add 1 bit of the reserved field of DAI (e.g., at least one of the C-DAI field and the T-DAI field) to NDI, and add 1 bit of the NDI field for a total of 2 bits.
- the NDI may be notified to terminal 200 .
- FIG. 12 is a diagram showing an example of a case without blind retransmission in method 3 of use.
- a 2-bit extended NDI (for example, 0 (bit string: 00), 1 (bit string: 01), 2 (bit string: 10) and 3 (bit string: 11) (not shown)) may be notified to the terminal 200 .
- the second and third data for example, PDSCH
- the previously reported NDI value is toggled (or incremented) and reported to the terminal 200.
- the extended NDI is 2 bits
- the NDI eg, 0 (bit string: 00)
- a different value (2 (bit string: 10) in FIG. 12) may be notified to terminal 200 .
- FIG. 12 shows that since the extended NDI is 2 bits, when transmitting the second data (eg, new data), the NDI (eg, 0 (bit string: 00)) at the time of transmitting the first data and A different value (2 (bit string: 10) in FIG. 12) may be notified to terminal 200 . Also, as shown in FIG.
- the NDI for example, 0 (bit string: 00) and 1 (bit string: : 01)) (2 (bit string: 10) in FIG. 12) may be notified to the terminal 200 .
- terminal 200 determines that the first data and the third data are different data, and receives the new data without combining. In this way, extended NDI can suppress the occurrence of erroneous synthesis at terminal 200 .
- the number of bits in the DAI field included in the extended NDI is not limited to 1 bit, and may be 2 bits or more.
- 2 bits of either one of C-DAI and T-DAI may be added to the NDI to notify terminal 200 of an extended NDI of a total of 3 bits including 1 bit of the NDI field.
- a total of 4 bits of C-DAI and T-DAI may be added to the NDI, and an extended NDI of 5 bits in total including 1 bit of the NDI field may be notified to terminal 200 .
- a parameter indicating whether or not the transmission data is to be retransmitted may be notified in the reserved field of DAI, apart from NDI.
- FIG. 13 is a diagram showing an example in which one bit of the fields reserved in DAI is used as a retransmission notification bit.
- FIG. 13(a) shows a case with blind retransmission
- FIG. 11(b) shows a case without blind retransmission.
- terminal 200 may erroneously determine that the third data is retransmission data of the first data based on the value of NDI. Even in this case, terminal 200 can correctly determine that the third data is new data based on the retransmission notification bit of DAI (0 in FIG. 13(b)). In this way, the occurrence of erroneous combining in terminal 200 can be suppressed by the retransmission notification bit of DAI.
- Blind retransmission is sometimes called HARQ retransmission without feedback.
- the fields reserved in the DAI may be set, for example, with parameters relating to the transmission power level used for data transmission by feedback-disabled HARQ processes.
- a parameter regarding the power level of data (eg, PDSCH) may be set, or a parameter regarding the power difference between the reference signal and the data may be set.
- a transmission power control command may be set in a field reserved in DAI.
- the base station 100 can increase the power of the data or reference signal during transmission of the feedback-disabled HARQ process, for example, so that transmission at a lower BLER is possible. Become.
- parameters regarding the pattern of reference signals or whether or not to add them may be set. This allows more reference signals to be transmitted when transmitting feedback-disabled HARQ processes, thus allowing transmission at a lower BLER.
- parameters related to at least two methods (in other words, uses) out of usage methods 1 to 4 of the DAI field described above may be notified in a reserved field.
- 2 bits may indicate the repetition count, and the other 2 bits may indicate the NDI bit (for example, extended NDI bit).
- some bits of the C-DAI field or the T-DAI field are used to notify the DAI value or non-DAI value information such as usage methods 1 to 4, The remaining bits may be reserved.
- base station 100 uses DAI (for example, C- DAI field and T-DAI field) to be set.
- terminal 200 receives information set based on settings related to feedback to the HARQ process in DAI that notifies the number of data allocations in the HARQ process, and controls data reception based on the received information. .
- DAI for example, C- DAI field and T-DAI field
- the terminal 200 receives the DAI value of the feedback-enabled HARQ process in the DAI field in the DCI that allocates the data of the feedback-disabled HARQ process, thereby performing HARQ-ACK in the feedback-enabled HARQ process. Since the possibility of identifying the codebook size (or the specific success rate) can be increased, the efficiency of retransmission control by HARQ can be improved.
- the terminal 200 receives transmission parameters for feedback-disabled HARQ process data in the DAI field in the DCI that allocates feedback-disabled HARQ process data. For example, by receiving transmission parameters that can reduce BLER, terminal 200 can reduce the reception error rate of data in feedback-disabled HARQ processes, thereby improving the efficiency of retransmission control by HARQ.
- DAIs for example, C-DAI and T-DAI
- transmission of downlink data (eg, PDSCH) from base station 100 to terminal 200 has been described, but one embodiment of the present disclosure is not limited to this. It may be applied to uplink data (for example, PUSCH) to station 100 or data in links between terminals 200 (for example, sidelink). Also, in the above-described embodiments, retransmission of data (for example, PDSCH) has been described, but retransmission targets are not limited to data (or data channels), and may be other signals or channels.
- the HARQ-ACK bits included in the HARQ-ACK codebook are not limited to HARQ-ACK bits for PDSCH reception, and may be HARQ-ACK bits for other signals.
- the HARQ-ACK codebook may include HARQ-ACK bits for DCI indicating Semi-Persistent Scheduling (SPS) release (also called SPS PDSCH release) or Scell dormancy.
- SPS Semi-Persistent Scheduling
- both the C-DAI field and the T-DAI field may be notified of the C-DAI value and the T-DAI value including the HARQ-ACK bit.
- both the C-DAI field and the T-DAI field are notified to the terminal 200.
- the present invention is not limited to this. Either one may be notified to the terminal 200 and the other may not be notified to the terminal 200 .
- information in the C-DAI field is notified to terminal 200, and information in the T-DAI field is notified to terminal 200. It doesn't have to be.
- the C-DAI field in the DCI that allocates the feedback-disabled HARQ process is assigned data in the feedback-disabled HARQ process. Uncounted C-DAI values may be included.
- the above-described setting methods 1 to 4 may be used in combination by setting the parameters of the base station or cell. For example, when one CC (or one cell) is configured, configuration method 4 is used, and when multiple CCs (or multiple cells) are configured, configuration method 3 is used. good. In this case, when one CC (or one cell) is configured, the C-DAI value is notified to the terminal 200 in the C-DAI field in the DCI that allocates the feedback-disabled HARQ process, and T- Information in the DAI field may not be notified.
- the C-DAI field in the DCI that allocates feedback-disabled HARQ processes is reserved, or the usage methods 1 to 4 Information different from the C-DAI value may be notified to terminal 200 as in the above, and the T-DAI value may be notified to terminal 200 in the T-DAI field.
- terminal 200 considering the possibility that terminal 200 does not transmit HARQ-ACK when operating in an unlicensed band (for example, also referred to as NR-Unlicensed (NR-U)), terminal 200 ⁇ Type 3 HARQ-ACK codebook'' is specified to transmit all together.
- an embodiment of the present disclosure may be applied when using the Type3 HARQ-ACK codebook.
- an embodiment of the present disclosure is not limited to the Type3 HARQ-ACK codebook, and may be applied when using other HARQ-ACK codebooks, for example, when notifying information about the HARQ-ACK codebook size by DAI. .
- the DAI field which is a field for notifying parameters related to the number of data allocations.
- Fields are not limited to this.
- the field used for notifying information to the terminal 200 in one embodiment of the present disclosure is HARQ process ID, NDI, RV, PDSCH-to-HARQ_feedback timing indicator, etc.
- a field used for notification of information to the terminal 200 in one embodiment of the present disclosure may be defined as a reserved field in a certain release (eg, Release 17), or It may be used for purposes other than reporting information about the number of data allocations in subsequent releases.
- DCI formats 1_0, 1_1, and 1_2 are DCI formats used for downlink scheduling (data allocation), and an embodiment of the present disclosure is applied to all of these DCI formats. Alternatively, one embodiment of the present disclosure may be applied to at least one. Also, the notification information in the DAI field may be changed individually for each DCI format.
- activation or deactivation of HARQ feedback may be set individually for the terminal or individually for the cell. may be set.
- DAI field itself may be deleted and defined as a separate reserved field.
- another field name may be defined.
- an embodiment of the present disclosure can be applied regardless of the type of satellite such as GEO, Medium Earth Orbit satellite (MEO), LEO, or Highly Elliptical Orbit satellite (HEO).
- An embodiment of the present disclosure may also be applied to non-terrestrial communications such as HAPS or drone base stations, for example.
- the NTN environment for example, satellite communication environment
- the present disclosure is not limited to this.
- the present disclosure may be applied to other communication environments (eg, LTE and/or NR terrestrial cellular environments).
- one embodiment of the present disclosure may be applied to terrestrial communication in an environment where the cell size is large and the propagation delay between the base station 100 and the terminal 200 is long (for example, above a threshold).
- it may be applied to communication other than NTN to which HARQ or HARQ feedback invalidation is applied.
- the form of satellite communication may be a configuration in which the functions of the base station are present on the satellite (for example, "regenerative satellite"), and the functions of the base station are present on the ground and the base station
- a configuration in which a satellite relays communication between the terminal and the terminal may also be used.
- the downlink and uplink may be the link between the terminal and the satellite, or the link via the satellite, in one embodiment of the present disclosure.
- the various parameters in the above embodiment are examples, and other numerical values may be used.
- the number of slots and the number of CCs for which the number of data allocations is notified by DAI is not limited to 2 slots and 4 CCs, and may be other numbers.
- the HARQ-ACK codebook size is not limited to the examples shown in FIGS. 7 to 10, and may be other sizes.
- the number of bits in at least one of the C-DAI field and the T-DAI field included in DAI is not limited to 2 bits, and may be another number of bits.
- at least one of the position (eg, CC2 of slot2) and the number (eg, 1) of feedback-disabled HARQ processes may be other values.
- HARQ-ACK may be called, for example, ACK/NACK or HARQ-feedback.
- a base station may be called a gNodeB or a gNB.
- a terminal may also be referred to as a UE.
- a slot may be replaced with a time slot, minislot, frame, subframe, or the like.
- (supplement) Information indicating whether or not the terminal 200 supports the functions, operations, or processes shown in the above embodiments is transmitted from the terminal 200 to the base station 100, for example, as capability information or a capability parameter of the terminal 200. (or notified).
- the capability information may include an information element (IE) individually indicating whether or not the terminal 200 supports at least one of the functions, operations, or processes shown in the above embodiments.
- the capability information may include an information element indicating whether or not the terminal 200 supports a combination of two or more of the functions, operations or processes shown in the above embodiments.
- base station 100 may determine (or determine or assume) functions, operations, or processes supported (or not supported) by terminal 200 as the source of capability information. The base station 100 may perform operation, processing, or control according to the determination result based on the capability information. For example, based on the capability information received from terminal 200, base station 100 assigns at least one of downlink resources such as PDCCH or PDSCH and uplink resources such as PUCCH or PUSCH (for example, in the DAI field scheduling) may be controlled.
- downlink resources such as PDCCH or PDSCH
- uplink resources such as PUCCH or PUSCH
- terminal 200 not supporting part of the functions, operations, or processes shown in the above-described embodiments can be interpreted as limiting such functions, operations, or processes in terminal 200.
- base station 100 may be notified of information or requests regarding such restrictions.
- Information about the capabilities or limitations of terminal 200 may be defined, for example, in a standard, or may be implicitly associated with information known in base station 100 or information transmitted to base station 100 . may be notified.
- a downlink control signal (or downlink control information) related to an embodiment of the present disclosure may be, for example, a signal (or information) transmitted in the Physical Downlink Control Channel (PDCCH) of the physical layer, It may be a signal (or information) transmitted in a medium access control element (MAC CE) or radio resource control (RRC) of a higher layer. Also, the signal (or information) is not limited to being notified by a downlink control signal, and may be defined in advance in specifications (or standards), or may be set in advance in base stations and terminals.
- PDCCH Physical Downlink Control Channel
- MAC CE medium access control element
- RRC radio resource control
- the uplink control signal (or uplink control information) related to an embodiment of the present disclosure may be, for example, a signal (or information) transmitted in PUCCH of the physical layer, MAC CE or It may be a signal (or information) transmitted in RRC. Also, the signal (or information) is not limited to being notified by an uplink control signal, and may be defined in advance in specifications (or standards), or may be set in advance in base stations and terminals. Also, the uplink control signal may be replaced with, for example, uplink control information (UCI), 1st stage sidelink control information (SCI), or 2nd stage SCI.
- UCI uplink control information
- SCI 1st stage sidelink control information
- 2nd stage SCI 2nd stage SCI.
- a base station includes a Transmission Reception Point (TRP), a cluster head, an access point, a Remote Radio Head (RRH), an eNodeB (eNB), a gNodeB (gNB), a Base Station (BS), a Base Transceiver Station (BTS), base unit, gateway, etc.
- TRP Transmission Reception Point
- RRH Remote Radio Head
- eNB eNodeB
- gNB gNodeB
- BS Base Station
- BTS Base Transceiver Station
- base unit gateway, etc.
- a terminal may play the role of a base station.
- a relay device that relays communication between the upper node and the terminal may be used. It may also be a roadside device.
- An embodiment of the present disclosure may be applied to any of uplink, downlink, and sidelink, for example.
- an embodiment of the present disclosure can be used for uplink Physical Uplink Shared Channel (PUSCH), Physical Uplink Control Channel (PUCCH), Physical Random Access Channel (PRACH), downlink Physical Downlink Shared Channel (PDSCH), PDCCH, Physical It may be applied to the Broadcast Channel (PBCH), or the sidelink Physical Sidelink Shared Channel (PSSCH), Physical Sidelink Control Channel (PSCCH), and Physical Sidelink Broadcast Channel (PSBCH).
- PUSCH Physical Uplink Shared Channel
- PUCCH Physical Uplink Control Channel
- PRACH Physical Random Access Channel
- PDSCH Physical Downlink Shared Channel
- PDCCH Physical It may be applied to the Broadcast Channel (PBCH), or the sidelink Physical Sidelink Shared Channel (PSSCH), Physical Sidelink Control Channel (PSCCH), and Physical Sidelink Broadcast Channel (PSBCH).
- PBCH Broadcast Channel
- PSSCH Physical Sidelink Shared Channel
- PSCCH Physical Sidelink
- PDCCH, PDSCH, PUSCH, and PUCCH are examples of a downlink control channel, downlink data channel, uplink data channel, and uplink control channel, respectively.
- PSCCH and PSSCH are examples of sidelink control channels and sidelink data channels.
- PBCH and PSBCH are broadcast channels, and PRACH is an example of a random access channel.
- An embodiment of the present disclosure may be applied to either data channels or control channels, for example.
- the channels in one embodiment of the present disclosure may be replaced with any of the data channels PDSCH, PUSCH, and PSSCH, or the control channels PDCCH, PUCCH, PBCH, PSCCH, and PSBCH.
- the reference signal is, for example, a signal known to both the base station and the mobile station, and is sometimes called Reference Signal (RS) or pilot signal.
- the reference signal can be Demodulation Reference Signal (DMRS), Channel State Information - Reference Signal (CSI-RS), Tracking Reference Signal (TRS), Phase Tracking Reference Signal (PTRS), Cell-specific Reference Signal (CRS), or Sounding Any reference signal (SRS) may be used.
- DMRS Demodulation Reference Signal
- CSI-RS Channel State Information - Reference Signal
- TRS Tracking Reference Signal
- PTRS Phase Tracking Reference Signal
- CRS Cell-specific Reference Signal
- SRS Sounding Any reference signal
- the unit of time resources is not limited to one or a combination of slots and symbols, such as frames, superframes, subframes, slots, time slot subslots, minislots or symbols, Orthogonal Time resource units such as frequency division multiplexing (OFDM) symbols and single carrier-frequency division multiplexing (SC-FDMA) symbols may be used, or other time resource units may be used.
- Orthogonal Time resource units such as frequency division multiplexing (OFDM) symbols and single carrier-frequency division multiplexing (SC-FDMA) symbols may be used, or other time resource units may be used.
- the number of symbols included in one slot is not limited to the number of symbols exemplified in the above embodiment, and may be another number of symbols.
- An embodiment of the present disclosure may be applied to both licensed bands and unlicensed bands.
- An embodiment of the present disclosure is applied to any of communication between base stations and terminals (Uu link communication), communication between terminals (Sidelink communication), and vehicle to everything (V2X) communication. good too.
- the channel in one embodiment of the present disclosure may be replaced with any of PSCCH, PSSCH, Physical Sidelink Feedback Channel (PSFCH), PSBCH, PDCCH, PUCCH, PDSCH, PUSCH, or PBCH.
- an embodiment of the present disclosure may be applied to any of a terrestrial network, a non-terrestrial network (NTN: Non-Terrestrial Network) using satellites or high altitude pseudo satellites (HAPS: High Altitude Pseudo Satellite) .
- NTN Non-Terrestrial Network
- HAPS High Altitude pseudo satellites
- an embodiment of the present disclosure may be applied to a terrestrial network such as a network with a large cell size, an ultra-wideband transmission network, or the like, in which the transmission delay is large compared to the symbol length or slot length.
- an antenna port refers to a logical antenna (antenna group) composed of one or more physical antennas.
- an antenna port does not always refer to one physical antenna, but may refer to an array antenna or the like composed of a plurality of antennas.
- the number of physical antennas that constitute an antenna port is not defined, but may be defined as the minimum unit in which a terminal station can transmit a reference signal.
- an antenna port may be defined as the minimum unit for multiplying weights of precoding vectors.
- 5G fifth generation cellular technology
- NR new radio access technologies
- the system architecture as a whole is assumed to be NG-RAN (Next Generation-Radio Access Network) with gNB.
- the gNB provides UE-side termination of NG radio access user plane (SDAP/PDCP/RLC/MAC/PHY) and control plane (RRC) protocols.
- SDAP/PDCP/RLC/MAC/PHY NG radio access user plane
- RRC control plane
- the gNB also connects to the Next Generation Core (NGC) via the Next Generation (NG) interface, and more specifically, the Access and Mobility Management Function (AMF) via the NG-C interface (e.g., a specific core entity that performs AMF) , and is also connected to a UPF (User Plane Function) (eg, a specific core entity that performs UPF) by an NG-U interface.
- NNC Next Generation Core
- AMF Access and Mobility Management Function
- UPF User Plane Function
- the NG-RAN architecture is shown in Figure 14 (see, eg, 3GPP TS 38.300 v15.6.0, section 4).
- the NR user plane protocol stack (see e.g. 3GPP TS 38.300, section 4.4.1) consists of a network-side terminated PDCP (Packet Data Convergence Protocol (see TS 38.300 section 6.4)) sublayer at the gNB, It includes the RLC (Radio Link Control (see TS 38.300 clause 6.3)) sublayer and the MAC (Medium Access Control (see TS 38.300 clause 6.2)) sublayer. Also, a new Access Stratum (AS) sublayer (Service Data Adaptation Protocol (SDAP)) has been introduced on top of PDCP (see, for example, 3GPP TS 38.300, Section 6.5).
- PDCP Packet Data Convergence Protocol
- RLC Radio Link Control
- MAC Medium Access Control
- SDAP Service Data Adaptation Protocol
- a control plane protocol stack is defined for NR (see, eg, TS 38.300, section 4.4.2).
- An overview of layer 2 functions is given in clause 6 of TS 38.300.
- the functions of the PDCP sublayer, RLC sublayer and MAC sublayer are listed in TS 38.300 clauses 6.4, 6.3 and 6.2 respectively.
- the functions of the RRC layer are listed in clause 7 of TS 38.300.
- the Medium-Access-Control layer handles logical channel multiplexing and scheduling and scheduling-related functions, including handling various neurology.
- the physical layer is responsible for encoding, PHY HARQ processing, modulation, multi-antenna processing, and mapping of signals to appropriate physical time-frequency resources.
- the physical layer also handles the mapping of transport channels to physical channels.
- the physical layer provides services to the MAC layer in the form of transport channels.
- a physical channel corresponds to a set of time-frequency resources used for transmission of a particular transport channel, and each transport channel is mapped to a corresponding physical channel.
- physical channels include PRACH (Physical Random Access Channel), PUSCH (Physical Uplink Shared Channel), and PUCCH (Physical Uplink Control Channel) as uplink physical channels, and PDSCH (Physical Downlink Shared Channel) as downlink physical channels.
- PDCCH Physical Downlink Control Channel
- PBCH Physical Broadcast Channel
- NR use cases/deployment scenarios include enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), massive machine type communication (mMTC) with diverse requirements in terms of data rate, latency and coverage can be included.
- eMBB is expected to support peak data rates (20 Gbps in the downlink and 10 Gbps in the uplink) and user-experienced data rates on the order of three times the data rates provided by IMT-Advanced.
- URLLC more stringent requirements are imposed for ultra-low latency (0.5 ms each for UL and DL for user plane latency) and high reliability (1-10-5 within 1 ms).
- mMTC preferably has high connection density (1,000,000 devices/km 2 in urban environments), wide coverage in hostile environments, and extremely long battery life (15 years) for low cost devices. can be requested.
- the OFDM numerology (e.g., subcarrier spacing, OFDM symbol length, cyclic prefix (CP) length, number of symbols per scheduling interval) suitable for one use case may be used for other use cases. May not be valid.
- low-latency services preferably require shorter symbol lengths (and thus larger subcarrier spacings) and/or fewer symbols per scheduling interval (also called TTI) than mMTC services.
- TTI time-to-live
- Subcarrier spacing may optionally be optimized to maintain similar CP overhead.
- the value of subcarrier spacing supported by NR may be one or more.
- resource element may be used to mean the smallest resource unit consisting of one subcarrier for the length of one OFDM/SC-FDMA symbol.
- resource grids of subcarriers and OFDM symbols are defined for uplink and downlink, respectively.
- Each element of the resource grid is called a resource element and is identified based on a frequency index in the frequency domain and a symbol position in the time domain (see 3GPP TS 38.211 v15.6.0).
- FIG. 15 shows functional separation between NG-RAN and 5GC.
- Logical nodes in NG-RAN are gNBs or ng-eNBs.
- 5GC has logical nodes AMF, UPF and SMF.
- gNBs and ng-eNBs host the following main functions: - Radio Bearer Control, Radio Admission Control, Connection Mobility Control, dynamic allocation of resources to UEs in both uplink and downlink (scheduling), etc. Functions of Radio Resource Management; - IP header compression, encryption and integrity protection of data; - AMF selection on UE attach when routing to an AMF cannot be determined from information provided by the UE; - routing of user plane data towards UPF; - routing of control plane information towards AMF; - setting up and tearing down connections; - scheduling and sending paging messages; - scheduling and transmission of system broadcast information (originating from AMF or Operation, Admission, Maintenance (OAM)); - configuration of measurements and measurement reports for mobility and scheduling; - transport level packet marking in the uplink; - session management; - support for network slicing; - QoS flow management and mapping to data radio bearers; - Support for UEs in RRC_INACTIVE state; - the ability to deliver NAS messages; - sharing
- the Access and Mobility Management Function hosts the following main functions: - Ability to terminate Non-Access Stratum (NAS) signaling; - security of NAS signaling; - Access Stratum (AS) security controls; - Core Network (CN) inter-node signaling for mobility across 3GPP access networks; - Reachability to UEs in idle mode (including control and execution of paging retransmissions); - management of the registration area; - support for intra-system and inter-system mobility; - access authentication; - access authorization, including checking roaming rights; - mobility management control (subscription and policy); - support for network slicing; - Selection of the Session Management Function (SMF).
- NAS Non-Access Stratum
- AS Access Stratum
- CN Core Network
- the User Plane Function hosts the following main functions: - Anchor points for intra-RAT mobility/inter-RAT mobility (if applicable); - External PDU (Protocol Data Unit) session points for interconnection with data networks; - packet routing and forwarding; – Policy rule enforcement for packet inspection and user plane parts; - reporting of traffic usage; - an uplink classifier to support routing of traffic flows to the data network; - Branching Points to support multi-homed PDU sessions; - QoS processing for the user plane (e.g. packet filtering, gating, UL/DL rate enforcement; - verification of uplink traffic (mapping of SDF to QoS flows); - Downlink packet buffering and downlink data notification trigger function.
- Anchor points for intra-RAT mobility/inter-RAT mobility if applicable
- External PDU Protocol Data Unit
- – Policy rule enforcement for packet inspection and user plane parts for interconnection with data networks
- - reporting of traffic usage - an uplink classifier to support routing of traffic flows to the data network
- Session Management Function hosts the following main functions: - session management; - allocation and management of IP addresses for UEs; - UPF selection and control; - the ability to configure traffic steering in the User Plane Function (UPF) to route traffic to the proper destination; - policy enforcement and QoS in the control part; - Notification of downlink data.
- UPF User Plane Function
- Figure 16 shows some interactions between UE, gNB and AMF (5GC entity) when UE transitions from RRC_IDLE to RRC_CONNECTED for NAS part (see TS 38.300 v15.6.0).
- RRC is a higher layer signaling (protocol) used for UE and gNB configuration.
- the AMF prepares the UE context data (which includes, for example, the PDU session context, security keys, UE Radio Capabilities, UE Security Capabilities, etc.) and the initial context Send to gNB with INITIAL CONTEXT SETUP REQUEST.
- the gNB then activates AS security together with the UE. This is done by the gNB sending a SecurityModeCommand message to the UE and the UE responding to the gNB with a SecurityModeComplete message.
- the gNB sends an RRCReconfiguration message to the UE, and the gNB receives the RRCReconfigurationComplete from the UE to reconfigure for setting up Signaling Radio Bearer 2 (SRB2) and Data Radio Bearer (DRB) .
- SRB2 Signaling Radio Bearer 2
- DRB Data Radio Bearer
- the step for RRCReconfiguration is omitted as SRB2 and DRB are not set up.
- the gNB notifies the AMF that the setup procedure is complete with an INITIAL CONTEXT SETUP RESPONSE.
- the present disclosure provides control circuitry for operationally establishing a Next Generation (NG) connection with a gNodeB and an operationally NG connection so that signaling radio bearers between the gNodeB and User Equipment (UE) are set up.
- a 5th Generation Core (5GC) entity eg, AMF, SMF, etc.
- AMF Next Generation
- SMF User Equipment
- the gNodeB sends Radio Resource Control (RRC) signaling including a Resource Allocation Configuration Information Element (IE) to the UE via the signaling radio bearer.
- RRC Radio Resource Control
- IE Resource Allocation Configuration Information Element
- the UE then performs uplink transmission or downlink reception based on the resource allocation configuration.
- Figure 17 shows some of the use cases for 5G NR.
- the 3rd generation partnership project new radio (3GPP NR) considers three use cases envisioned by IMT-2020 to support a wide variety of services and applications.
- the first stage of specifications for high-capacity, high-speed communications (eMBB: enhanced mobile-broadband) has been completed.
- Current and future work includes expanding eMBB support, as well as ultra-reliable and low-latency communications (URLLC) and Massively Connected Machine Type Communications (mMTC). Standardization for massive machine-type communications is included
- Figure 17 shows some examples of envisioned usage scenarios for IMT beyond 2020 (see eg ITU-RM.2083 Figure 2).
- URLLC use cases have strict performance requirements such as throughput, latency (delay), and availability.
- URLLLC use cases are envisioned as one of the elemental technologies to realize these future applications such as wireless control of industrial production processes or manufacturing processes, telemedicine surgery, automation of power transmission and distribution in smart grids, and traffic safety. ing.
- URLLLC ultra-reliability is supported by identifying technologies that meet the requirements set by TR 38.913.
- an important requirement includes a target user plane latency of 0.5 ms for UL (uplink) and 0.5 ms for DL (downlink).
- the general URLLC requirement for one-time packet transmission is a block error rate (BLER) of 1E-5 for a packet size of 32 bytes with a user plane latency of 1 ms.
- BLER block error rate
- NRURLC the technical enhancements targeted by NRURLC aim to improve latency and improve reliability.
- Technical enhancements for latency improvement include configurable numerology, non-slot-based scheduling with flexible mapping, grant-free (configured grant) uplink, slot-level repetition in data channels, and downlink pre-emption.
- Preemption means that a transmission with already allocated resources is stopped and the already allocated resources are used for other transmissions with lower latency/higher priority requirements requested later. Transmissions that have already been authorized are therefore superseded by later transmissions. Preemption is applicable regardless of the concrete service type. For example, a transmission of service type A (URLLC) may be replaced by a transmission of service type B (eg eMBB).
- Technology enhancements for increased reliability include a dedicated CQI/MCS table for a target BLER of 1E-5.
- mMTC massive machine type communication
- NR URLLC NR URLLC
- the stringent requirements are: high reliability (reliability up to 10-6 level), high availability, packet size up to 256 bytes, time synchronization up to several microseconds (depending on the use case, the value 1 ⁇ s or a few ⁇ s depending on the frequency range and latency as low as 0.5 ms to 1 ms (eg, 0.5 ms latency in the targeted user plane).
- NRURLC NR Ultra User Downlink Control Channel
- enhancements for compact DCI PDCCH repetition, and increased PDCCH monitoring.
- enhancement of UCI Uplink Control Information
- enhancement of enhanced HARQ Hybrid Automatic Repeat Request
- minislot refers to a Transmission Time Interval (TTI) containing fewer symbols than a slot (a slot comprises 14 symbols).
- TTI Transmission Time Interval
- the 5G QoS (Quality of Service) model is based on QoS flows, and includes QoS flows that require a guaranteed flow bit rate (GBR: Guaranteed Bit Rate QoS flows), and guaranteed flow bit rates. support any QoS flows that do not exist (non-GBR QoS flows). Therefore, at the NAS level, a QoS flow is the finest granularity of QoS partitioning in a PDU session.
- a QoS flow is identified within a PDU session by a QoS Flow ID (QFI) carried in an encapsulation header over the NG-U interface.
- QFI QoS Flow ID
- 5GC For each UE, 5GC establishes one or more PDU sessions. For each UE, in line with the PDU session, NG-RAN establishes at least one Data Radio Bearers (DRB), eg as shown above with reference to FIG. Also, additional DRBs for QoS flows for that PDU session can be configured later (up to NG-RAN when to configure). NG-RAN maps packets belonging to different PDU sessions to different DRBs. NAS level packet filters in UE and 5GC associate UL and DL packets with QoS flows, while AS level mapping rules in UE and NG-RAN associate UL and DL QoS flows with DRB.
- DRB Data Radio Bearers
- FIG. 18 shows the non-roaming reference architecture of 5G NR (see TS 23.501 v16.1.0, section 4.23).
- An Application Function eg, an external application server hosting 5G services, illustrated in FIG. 17
- AF Application Function
- NEF Network Exposure Function
- PCF Policy Control Function
- Application Functions that are not authorized by the operator to directly access the Network Function communicate with the associated Network Function using the open framework to the outside world via the NEF.
- Figure 18 shows further functional units of the 5G architecture: Network Slice Selection Function (NSSF), Network Repository Function (NRF), Unified Data Management (UDM), Authentication Server Function (AUSF), Access and Mobility Management Function (AMF) , Session Management Function (SMF), and Data Network (DN, eg, service by operator, Internet access, or service by third party). All or part of the core network functions and application services may be deployed and operated in a cloud computing environment.
- NSF Network Slice Selection Function
- NRF Network Repository Function
- UDM Unified Data Management
- AUSF Authentication Server Function
- AMF Access and Mobility Management Function
- SMSF Session Management Function
- DN Data Network
- QoS requirements for at least one of URLLC, eMMB and mMTC services are set during operation to establish a PDU session including radio bearers between a gNodeB and a UE according to the QoS requirements.
- the functions of the 5GC e.g., NEF, AMF, SMF, PCF, UPF, etc.
- a control circuit that, in operation, serves using the established PDU session;
- An application server eg AF of 5G architecture
- Each functional block used in the description of the above embodiments is partially or wholly realized as an LSI, which is an integrated circuit, and each process described in the above embodiments is partially or wholly implemented as It may be controlled by one LSI or a combination of LSIs.
- An LSI may be composed of individual chips, or may be composed of one chip so as to include some or all of the functional blocks.
- the LSI may have data inputs and outputs.
- LSIs are also called ICs, system LSIs, super LSIs, and ultra LSIs depending on the degree of integration.
- the method of circuit integration is not limited to LSI, and may be realized with a dedicated circuit, a general-purpose processor, or a dedicated processor. Further, an FPGA (Field Programmable Gate Array) that can be programmed after the LSI is manufactured, or a reconfigurable processor that can reconfigure the connections and settings of the circuit cells inside the LSI may be used.
- FPGA Field Programmable Gate Array
- reconfigurable processor that can reconfigure the connections and settings of the circuit cells inside the LSI may be used.
- the present disclosure may be implemented as digital or analog processing.
- a communication device may include a radio transceiver and processing/control circuitry.
- a wireless transceiver may include a receiver section and a transmitter section, or functions thereof.
- a wireless transceiver (transmitter, receiver) may include an RF (Radio Frequency) module and one or more antennas.
- RF modules may include amplifiers, RF modulators/demodulators, or the like.
- Non-limiting examples of communication devices include telephones (mobile phones, smart phones, etc.), tablets, personal computers (PCs) (laptops, desktops, notebooks, etc.), cameras (digital still/video cameras, etc.).
- digital players digital audio/video players, etc.
- wearable devices wearable cameras, smartwatches, tracking devices, etc.
- game consoles digital book readers
- telehealth and telemedicine (remote health care/medicine prescription) devices vehicles or mobile vehicles with communication capabilities (automobiles, planes, ships, etc.), and combinations of the various devices described above.
- Communication equipment is not limited to portable or movable equipment, but any type of equipment, device or system that is non-portable or fixed, e.g. smart home devices (household appliances, lighting equipment, smart meters or measuring instruments, control panels, etc.), vending machines, and any other "Things" that can exist on the IoT (Internet of Things) network.
- smart home devices household appliances, lighting equipment, smart meters or measuring instruments, control panels, etc.
- vending machines and any other "Things” that can exist on the IoT (Internet of Things) network.
- Communication includes data communication by cellular system, wireless LAN system, communication satellite system, etc., as well as data communication by a combination of these.
- Communication apparatus also includes devices such as controllers and sensors that are connected or coupled to communication devices that perform the communication functions described in this disclosure. Examples include controllers and sensors that generate control and data signals used by communication devices to perform the communication functions of the communication device.
- Communication equipment also includes infrastructure equipment, such as base stations, access points, and any other equipment, device, or system that communicates with or controls the various equipment, not limited to those listed above. .
- a base station includes a control circuit that determines information to be set in a signal that notifies the number of data allocations in the retransmission process, based on settings related to feedback for the retransmission process; and a transmission circuit for transmitting the
- control circuit transmits the information about the allocation number in a first retransmission process with the feedback enabled to the signal for a second retransmission process with the feedback disabled. set to
- control circuit does not count the allocation of the data for the second retransmission process in setting the information on the number of allocations.
- control circuit does not set information about the allocation number of the data in at least some fields of the signal for the feedback-disabled retransmission process.
- control circuit sets information about the allocation number for the feedback-enabled retransmission process in the signal for the feedback-disabled retransmission process. Set it to a different field than the one you don't want.
- the fields in which the information is not set are a first field indicating the cumulative number of allocations of the data per component carrier and per slot, and the total number of allocations of the data per slot. at least one of the second fields shown.
- control circuit sets information different from the information regarding the number of data allocations in the field in which the information regarding the number of data allocations is not set.
- control circuit sets known information between the base station and the terminal in fields in which the information on the number of data allocations is not set.
- a parameter regarding transmission of the data in a retransmission process in which the feedback is disabled is set.
- the parameters include the number of repetition times of transmission of the data, a parameter related to coding and modulation of the data, a parameter indicating whether the data is retransmission data, and transmission power of the data. is at least one of the parameters for
- a terminal includes a receiving circuit that receives information set based on settings related to feedback for a retransmission process in a signal that notifies the number of data allocations in the retransmission process, and based on the information: , and a control circuit for controlling the reception of the data.
- the base station determines information to be set in a signal that notifies the number of data allocations in the retransmission process, based on settings related to feedback for the retransmission process, and in the signal, the Send information.
- a terminal receives information set based on settings related to feedback for a retransmission process in a signal notifying the number of data allocations in the retransmission process, and based on the information, to control the reception of the data.
- One aspect of the present disclosure is useful for wireless communication systems.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Physics & Mathematics (AREA)
- Astronomy & Astrophysics (AREA)
- General Physics & Mathematics (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
Long Term Evolution(LTE)又は5G NRでは、例えば、データ送信の際の再送制御にHybrid automatic repeat request(HARQ)が適用される。
LTE及びNR Rel.15/16は、地上ネットワーク向けの無線アクセス技術として仕様化されている。一方で、NRは、衛星または高高度疑似衛星(HAPS:High-altitude platform station)を用いた通信等の地上以外のネットワーク(NTN)への拡張が検討されている(例えば、非特許文献1)。
本開示の一実施の形態に係る通信システムは、基地局100及び端末200を備える。
図4は、本実施の形態に係る基地局100の構成の一例を示すブロック図である。基地局100は、例えば、再送制御部101と、符号化・変調部102と、無線送信部103と、アンテナ104と、無線受信部105と、復調・復号部106と、HARQ-ACK判定部107と、を備える。
次に、端末200の構成例を説明する。
次に、基地局100及び端末200の動作例について説明する。
設定方法1では、フィードバック有効化されたHARQプロセスを割り当てるDCIにおけるC-DAIフィールドには、例えば、NR Rel.15/16の規定のように、当該DAIが通知されるスロット及びCCまでのデータ割り当てが有るスロット及びCCのカウント値(又は、データの割り当て数のカウント値)を示すC-DAI値が含まれてよい。また、設定方法1では、フィードバック有効化されたHARQプロセスを割り当てるDCIにおけるT-DAIフィールドには、例えば、NR Rel.15/16の規定のように、当該DAIが通知されるスロットまでのトータルのデータ割り当て数を示すT-DAI値が含まれてよい。
設定方法2では、フィードバック無効化されたHARQプロセスを割り当てるDCIのC-DAIフィールド及びT-DAIフィールドは、リザーブ(reserved)されてよい。換言すると、基地局100は、例えば、フィードバック無効化されたHARQプロセスについてのDAIのC-DAIフィールド及びT-DAIフィールドにおいて、C-DAI値及びT-DAI値(例えば、PDSCHの割り当て数に関する情報)を設定しなくてよい。
設定方法3では、フィードバック無効化されたHARQプロセスを割り当てるDCIのC-DAIフィールドはリザーブされ、T-DAIフィールドには、当該DAIが通知されるスロットまでのデータ割り当て総数を示すT-DAI値が含まれてよい。換言すると、基地局100は、例えば、フィードバック無効化されたHARQプロセスについてのDAIの一部のフィールド(例えば、C-DAIフィールド)においてC-DAI値を設定しなくてよく、他のフィールド(例えば、T-DAIフィールド)に、フィードバック有効化されたHARQプロセスについてのT-DAI値を設定してよい。
設定方法4では、フィードバック無効化されたHARQプロセスを割り当てるDCIのC-DAIフィールドには、当該DAIが通知されるスロット及びCCまでのデータ割り当て数(例えば、累積数)を示すC-DAI値が含まれ、T-DAIフィールドはリザーブされてよい。換言すると、基地局100は、例えば、フィードバック無効化されたHARQプロセスについてのDAIの一部のフィールド(例えば、T-DAIフィールド)においてT-DAI値を設定しなくてよく、他のフィールド(例えば、C-DAIフィールド)に、フィードバック有効化されたHARQプロセスについてのC-DAI値を設定してよい。
使用方法1では、DAIにおいてリザーブされるフィールドには、例えば、フィードバック無効化されたHARQプロセスのデータ送信における繰り返し送信数(又は、レピティション数)に関するパラメータが設定されてよい。
使用方法2では、DAIにおいてリザーブされるフィールドには、例えば、フィードバック無効化されたHARQプロセスのデータ送信に用いるMCSレベルに関するパラメータが設定されてよい。
例えば、フィードバック無効化されたHARQプロセスによる送信において、より低いBLERを実現する方法の例として、基地局100がブラインド再送によって同一データ(例えば、PDSCH)を複数回送信する方法が挙げられる。ブラインド再送では、例えば、基地局100は、端末200からのHARQ-ACKを受信せずに、端末200に再送データを送信する。ここで、端末200は、例えば、データ割り当てのためのDCIに含まれるNDIのビットに基づいて、送信データが初回送信(又は、新規送信)であるか、再送であるかを判断してよい。
使用方法4では、DAIにおいてリザーブされるフィールドには、例えば、フィードバック無効化されたHARQプロセスによるデータ送信に用いる送信電力レベルに関するパラメータが設定されてよい。
上述した実施の形態に示した機能、動作又は処理を端末200がサポートするか否かを示す情報が、例えば、端末200の能力(capability)情報あるいは能力パラメータとして、端末200から基地局100へ送信(あるいは通知)されてもよい。
本開示において、本開示の一実施例に関連する下り制御信号(又は、下り制御情報)は、例えば、物理層のPhysical Downlink Control Channel(PDCCH)において送信される信号(又は、情報)でもよく、上位レイヤのMedium Access Control Control Element(MAC CE)又はRadio Resource Control(RRC)において送信される信号(又は、情報)でもよい。また、信号(又は、情報)は、下り制御信号によって通知される場合に限定されず、仕様(又は、規格)において予め規定されてもよく、基地局及び端末に予め設定されてもよい。
本開示の一実施例において、基地局は、Transmission Reception Point(TRP)、クラスタヘッド、アクセスポイント、Remote Radio Head(RRH)、eNodeB (eNB)、gNodeB(gNB)、Base Station(BS)、Base Transceiver Station(BTS)、親機、ゲートウェイなどでもよい。また、サイドリンク通信では、基地局の役割を端末が担ってもよい。また、基地局の代わりに、上位ノードと端末の通信を中継する中継装置であってもよい。また、路側器であってもよい。
本開示の一実施例は、例えば、上りリンク、下りリンク、及び、サイドリンクの何れに適用してもよい。例えば、本開示の一実施例を上りリンクのPhysical Uplink Shared Channel(PUSCH)、Physical Uplink Control Channel(PUCCH)、Physical Random Access Channel(PRACH)、下りリンクのPhysical Downlink Shared Channel(PDSCH)、PDCCH、Physical Broadcast Channel(PBCH)、又は、サイドリンクのPhysical Sidelink Shared Channel(PSSCH)、Physical Sidelink Control Channel(PSCCH)、Physical Sidelink Broadcast Channel(PSBCH)に適用してもよい。
本開示の一実施例は、例えば、データチャネル及び制御チャネルの何れに適用してもよい。例えば、本開示の一実施例におけるチャネルをデータチャネルのPDSCH、PUSCH、PSSCH、又は、制御チャネルのPDCCH、PUCCH、PBCH、PSCCH、PSBCHの何れかに置き換えてもよい。
本開示の一実施例において、参照信号は、例えば、基地局及び移動局の双方で既知の信号であり、Reference Signal(RS)又はパイロット信号と呼ばれることもある。参照信号は、Demodulation Reference Signal(DMRS)、Channel State Information - Reference Signal(CSI-RS)、Tracking Reference Signal(TRS)、Phase Tracking Reference Signal(PTRS)、Cell-specific Reference Signal(CRS)、又は、Sounding Reference Signal(SRS)の何れでもよい。
本開示の一実施例において、時間リソースの単位は、スロット及びシンボルの1つ又は組み合わせに限らず、例えば、フレーム、スーパーフレーム、サブフレーム、スロット、タイムスロットサブスロット、ミニスロット又は、シンボル、Orthogonal Frequency Division Multiplexing(OFDM)シンボル、Single Carrier - Frequency Division Multiplexing(SC-FDMA)シンボルといった時間リソース単位でもよく、他の時間リソース単位でもよい。また、1スロットに含まれるシンボル数は、上述した実施の形態において例示したシンボル数に限定されず、他のシンボル数でもよい。
本開示の一実施例は、ライセンスバンド、アンライセンスバンドのいずれに適用してもよい。
本開示の一実施例は、基地局と端末との間の通信(Uuリンク通信)、端末と端末との間の通信(Sidelink通信)、Vehicle to Everything(V2X)の通信のいずれに適用してもよい。例えば、本開示の一実施例におけるチャネルをPSCCH、PSSCH、Physical Sidelink Feedback Channel(PSFCH)、PSBCH、PDCCH、PUCCH、PDSCH、PUSCH、又は、PBCHの何れかに置き換えてもよい。
本開示の一実施例において、アンテナポートは、1本又は複数の物理アンテナから構成される論理的なアンテナ(アンテナグループ)を指す。例えば、アンテナポートは必ずしも1本の物理アンテナを指すとは限らず、複数のアンテナから構成されるアレイアンテナ等を指すことがある。例えば、アンテナポートが何本の物理アンテナから構成されるかは規定されず、端末局が基準信号(Reference signal)を送信できる最小単位として規定されてよい。また、アンテナポートはプリコーディングベクトル(Precoding vector)の重み付けを乗算する最小単位として規定されることもある。
3GPPは、100GHzまでの周波数範囲で動作する新無線アクセス技術(NR)の開発を含む第5世代携帯電話技術(単に「5G」ともいう)の次のリリースに向けて作業を続けている。5G規格の初版は2017年の終わりに完成しており、これにより、5G NRの規格に準拠した端末(例えば、スマートフォン)の試作および商用展開に移ることが可能である。
図15は、NG-RANと5GCとの間の機能分離を示す。NG-RANの論理ノードは、gNBまたはng-eNBである。5GCは、論理ノードAMF、UPF、およびSMFを有する。
- 無線ベアラ制御(Radio Bearer Control)、無線アドミッション制御(Radio Admission Control)、接続モビリティ制御(Connection Mobility Control)、上りリンクおよび下りリンクの両方におけるリソースのUEへの動的割当(スケジューリング)等の無線リソース管理(Radio Resource Management)の機能;
- データのIPヘッダ圧縮、暗号化、および完全性保護;
- UEが提供する情報からAMFへのルーティングを決定することができない場合のUEのアタッチ時のAMFの選択;
- UPFに向けたユーザプレーンデータのルーティング;
- AMFに向けた制御プレーン情報のルーティング;
- 接続のセットアップおよび解除;
- ページングメッセージのスケジューリングおよび送信;
- システム報知情報(AMFまたは運用管理保守機能(OAM:Operation, Admission, Maintenance)が発信源)のスケジューリングおよび送信;
- モビリティおよびスケジューリングのための測定および測定報告の設定;
- 上りリンクにおけるトランスポートレベルのパケットマーキング;
- セッション管理;
- ネットワークスライシングのサポート;
- QoSフローの管理およびデータ無線ベアラに対するマッピング;
- RRC_INACTIVE状態のUEのサポート;
- NASメッセージの配信機能;
- 無線アクセスネットワークの共有;
- デュアルコネクティビティ;
- NRとE-UTRAとの緊密な連携。
- Non-Access Stratum(NAS)シグナリングを終端させる機能;
- NASシグナリングのセキュリティ;
- Access Stratum(AS)のセキュリティ制御;
- 3GPPのアクセスネットワーク間でのモビリティのためのコアネットワーク(CN:Core Network)ノード間シグナリング;
- アイドルモードのUEへの到達可能性(ページングの再送信の制御および実行を含む);
- 登録エリアの管理;
- システム内モビリティおよびシステム間モビリティのサポート;
- アクセス認証;
- ローミング権限のチェックを含むアクセス承認;
- モビリティ管理制御(加入およびポリシー);
- ネットワークスライシングのサポート;
- Session Management Function(SMF)の選択。
- intra-RATモビリティ/inter-RATモビリティ(適用可能な場合)のためのアンカーポイント;
- データネットワークとの相互接続のための外部PDU(Protocol Data Unit)セッションポイント;
- パケットのルーティングおよび転送;
- パケット検査およびユーザプレーン部分のポリシールールの強制(Policy rule enforcement);
- トラフィック使用量の報告;
- データネットワークへのトラフィックフローのルーティングをサポートするための上りリンククラス分類(uplink classifier);
- マルチホームPDUセッション(multi-homed PDU session)をサポートするための分岐点(Branching Point);
- ユーザプレーンに対するQoS処理(例えば、パケットフィルタリング、ゲーティング(gating)、UL/DLレート制御(UL/DL rate enforcement);
- 上りリンクトラフィックの検証(SDFのQoSフローに対するマッピング);
- 下りリンクパケットのバッファリングおよび下りリンクデータ通知のトリガ機能。
- セッション管理;
- UEに対するIPアドレスの割当および管理;
- UPFの選択および制御;
- 適切な宛先にトラフィックをルーティングするためのUser Plane Function(UPF)におけるトラフィックステアリング(traffic steering)の設定機能;
- 制御部分のポリシーの強制およびQoS;
- 下りリンクデータの通知。
図16は、NAS部分の、UEがRRC_IDLEからRRC_CONNECTEDに移行する際のUE、gNB、およびAMF(5GCエンティティ)の間のやり取りのいくつかを示す(TS 38.300 v15.6.0参照)。
図17は、5G NRのためのユースケースのいくつかを示す。3rd generation partnership project new radio(3GPP NR)では、多種多様なサービスおよびアプリケーションをサポートすることがIMT-2020によって構想されていた3つのユースケースが検討されている。大容量・高速通信(eMBB:enhanced mobile-broadband)のための第一段階の仕様の策定が終了している。現在および将来の作業には、eMBBのサポートを拡充していくことに加えて、高信頼・超低遅延通信(URLLC:ultra-reliable and low-latency communications)および多数同時接続マシンタイプ通信(mMTC:massive machine-type communicationsのための標準化が含まれる。図17は、2020年以降のIMTの構想上の利用シナリオのいくつかの例を示す(例えばITU-R M.2083 図2参照)。
5GのQoS(Quality of Service)モデルは、QoSフローに基づいており、保証されたフロービットレートが求められるQoSフロー(GBR:Guaranteed Bit Rate QoSフロー)、および、保証されたフロービットレートが求められないQoSフロー(非GBR QoSフロー)をいずれもサポートする。したがって、NASレベルでは、QoSフローは、PDUセッションにおける最も微細な粒度のQoSの区分である。QoSフローは、NG-Uインタフェースを介してカプセル化ヘッダ(encapsulation header)において搬送されるQoSフローID(QFI:QoS Flow ID)によってPDUセッション内で特定される。
101 再送制御部
102,205 符号化・変調部
103,206 無線送信部
104,201 アンテナ
105,202 無線受信部
106,203 復調・復号部
107 HARQ-ACK判定部
200 端末
204 HARQ-ACK生成部
Claims (13)
- 再送プロセスに対するフィードバックに関する設定に基づいて、前記再送プロセスにおけるデータの割り当て数を通知する信号に設定する情報を決定する制御回路と、
前記信号において前記情報を送信する送信回路と、
を具備する基地局。 - 前記制御回路は、前記フィードバックが有効化された第1の再送プロセスにおける前記割り当て数に関する前記情報を、前記フィードバックが無効化された第2の再送プロセスについての前記信号に設定する、
請求項1に記載の基地局。 - 前記制御回路は、前記割り当て数に関する情報の設定において、前記第2の再送プロセスについての前記データの割り当てをカウントしない、
請求項2に記載の基地局。 - 前記制御回路は、前記フィードバックが無効化された再送プロセスについての前記信号の少なくとも一部のフィールドにおいて、前記データの割り当て数に関する情報を設定しない、
請求項1に記載の基地局。 - 前記制御回路は、前記フィードバックが有効化された再送プロセスについての前記割り当て数に関する情報を、前記フィードバックが無効化された再送プロセスについての前記信号において、前記情報を設定しないフィールドと異なるフィールドに設定する、
請求項4に記載の基地局。 - 前記情報を設定しないフィールドは、コンポーネントキャリア毎かつスロット毎の前記データの割り当ての累積数を示す第1のフィールド、及び、スロット毎の前記データの割り当て数の総数を示す第2のフィールドの少なくとも一つである、
請求項4に記載の基地局。 - 前記制御回路は、前記データの割り当て数に関する情報を設定しないフィールドにおいて、前記データの割り当て数に関する情報と異なる情報を設定する、
請求項4に記載の基地局。 - 前記制御回路は、前記データの割り当て数に関する情報を設定しないフィールドにおいて、前記基地局と端末との間において既知の情報を設定する、
請求項7に記載の基地局。 - 前記制御回路は、前記データの割り当て数に関する情報を設定しないフィールドにおいて、前記フィードバックが無効化された再送プロセスにおける前記データの送信に関するパラメータを設定する、
請求項7に記載の基地局。 - 前記パラメータは、前記データの繰り返し送信回数、前記データの符号化及び変調に関するパラメータ、前記データが再送データであるか否かを示すパラメータ、及び、前記データの送信電力に関するパラメータの少なくとも一つである、
請求項9に記載の基地局。 - 再送プロセスに対するフィードバックに関する設定に基づいて設定された情報を、当該再送プロセスにおけるデータの割り当て数を通知する信号において受信する受信回路と、
前記情報に基づいて、前記データの受信を制御する制御回路と、
を具備する端末。 - 基地局は、
再送プロセスに対するフィードバックに関する設定に基づいて、前記再送プロセスにおけるデータの割り当て数を通知する信号に設定する情報を決定し、
前記信号において前記情報を送信する、
通信方法。 - 端末は、
再送プロセスに対するフィードバックに関する設定に基づいて設定された情報を、当該再送プロセスにおけるデータの割り当て数を通知する信号において受信し、
前記情報に基づいて、前記データの受信を制御する、
通信方法。
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202180096105.XA CN117083908A (zh) | 2021-04-06 | 2021-12-21 | 基站、终端及通信方法 |
US18/553,709 US20240187136A1 (en) | 2021-04-06 | 2021-12-21 | Base station, terminal, and communication method |
JP2023512816A JPWO2022215299A1 (ja) | 2021-04-06 | 2021-12-21 |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2021064668 | 2021-04-06 | ||
JP2021-064668 | 2021-04-06 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2022215299A1 true WO2022215299A1 (ja) | 2022-10-13 |
Family
ID=83545823
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2021/047271 WO2022215299A1 (ja) | 2021-04-06 | 2021-12-21 | 基地局、端末、及び、通信方法 |
Country Status (4)
Country | Link |
---|---|
US (1) | US20240187136A1 (ja) |
JP (1) | JPWO2022215299A1 (ja) |
CN (1) | CN117083908A (ja) |
WO (1) | WO2022215299A1 (ja) |
-
2021
- 2021-12-21 CN CN202180096105.XA patent/CN117083908A/zh active Pending
- 2021-12-21 US US18/553,709 patent/US20240187136A1/en active Pending
- 2021-12-21 JP JP2023512816A patent/JPWO2022215299A1/ja active Pending
- 2021-12-21 WO PCT/JP2021/047271 patent/WO2022215299A1/ja active Application Filing
Non-Patent Citations (3)
Title |
---|
APPLE: "Discussion on HARQ Enhancements for NTN", 3GPP DRAFT; R1-2101385, vol. RAN WG1, 18 January 2021 (2021-01-18), pages 1 - 7, XP051971552 * |
CATT: "HARQ operation enhancement for NTN", 3GPP DRAFT; R1-2100383, vol. RAN WG1, 19 January 2021 (2021-01-19), pages 1 - 7, XP051970986 * |
ERICSSON: "On HARQ enhancements for NTN", 3GPP DRAFT; R1-2100928, vol. RAN WG1, 19 January 2021 (2021-01-19), pages 1 - 13, XP051971267 * |
Also Published As
Publication number | Publication date |
---|---|
US20240187136A1 (en) | 2024-06-06 |
CN117083908A (zh) | 2023-11-17 |
JPWO2022215299A1 (ja) | 2022-10-13 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2021161639A1 (ja) | 受信装置、送信装置、受信方法及び送信方法 | |
US20220256557A1 (en) | Communication apparatuses and communication methods for dci for v2x communication apparatuses | |
WO2022137659A1 (ja) | 端末及び通信方法 | |
WO2021215098A1 (ja) | 端末及び通信方法 | |
CN115428558A (zh) | 移动台、基站、接收方法及发送方法 | |
WO2021131307A1 (ja) | 通信装置及び通信方法 | |
WO2022215299A1 (ja) | 基地局、端末、及び、通信方法 | |
WO2023013522A1 (ja) | 基地局、端末、及び、通信方法 | |
WO2023058264A1 (ja) | 通信装置及び通信方法 | |
WO2023100470A1 (ja) | 基地局、端末及び通信方法 | |
WO2022239289A1 (ja) | 通信装置、及び、通信方法 | |
WO2022030069A1 (ja) | 端末、基地局及び通信方法 | |
WO2023013191A1 (ja) | 通信装置、及び、通信方法 | |
WO2023013217A1 (ja) | 基地局、端末及び通信方法 | |
WO2022195952A1 (ja) | 端末、基地局及び通信方法 | |
WO2022085254A1 (ja) | 通信装置及び通信方法 | |
WO2023013204A1 (ja) | 端末、基地局、及び、通信方法 | |
WO2023139852A1 (ja) | 端末、基地局、及び、通信方法 | |
WO2023119756A1 (ja) | 通信装置及び通信方法 | |
WO2023203938A1 (ja) | 端末、基地局、通信方法及び集積回路 | |
WO2023181557A1 (ja) | 端末、基地局及び通信方法 | |
WO2023181556A1 (ja) | 端末、基地局及び通信方法 | |
WO2023100471A1 (ja) | 基地局、端末及び通信方法 | |
WO2022209097A1 (ja) | 通信装置および通信方法 | |
WO2024034198A1 (ja) | 端末、基地局及び通信方法 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 21936097 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 202180096105.X Country of ref document: CN |
|
WWE | Wipo information: entry into national phase |
Ref document number: 18553709 Country of ref document: US |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2023512816 Country of ref document: JP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 21936097 Country of ref document: EP Kind code of ref document: A1 |