WO2023013191A1 - 通信装置、及び、通信方法 - Google Patents
通信装置、及び、通信方法 Download PDFInfo
- Publication number
- WO2023013191A1 WO2023013191A1 PCT/JP2022/019551 JP2022019551W WO2023013191A1 WO 2023013191 A1 WO2023013191 A1 WO 2023013191A1 JP 2022019551 W JP2022019551 W JP 2022019551W WO 2023013191 A1 WO2023013191 A1 WO 2023013191A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- slot
- section
- signal
- transmission
- resource
- Prior art date
Links
- 238000004891 communication Methods 0.000 title claims abstract description 85
- 238000000034 method Methods 0.000 title claims description 90
- 230000005540 biological transmission Effects 0.000 claims abstract description 186
- 238000012545 processing Methods 0.000 description 73
- 230000006870 function Effects 0.000 description 42
- 238000010586 diagram Methods 0.000 description 33
- 238000013468 resource allocation Methods 0.000 description 19
- 238000007562 laser obscuration time method Methods 0.000 description 17
- 230000008569 process Effects 0.000 description 14
- 238000007726 management method Methods 0.000 description 13
- 238000001514 detection method Methods 0.000 description 12
- 238000005516 engineering process Methods 0.000 description 12
- 238000013507 mapping Methods 0.000 description 9
- 230000011664 signaling Effects 0.000 description 9
- 230000006866 deterioration Effects 0.000 description 7
- 238000000605 extraction Methods 0.000 description 7
- 230000008901 benefit Effects 0.000 description 6
- 238000006243 chemical reaction Methods 0.000 description 6
- 238000012986 modification Methods 0.000 description 6
- 230000004048 modification Effects 0.000 description 6
- 238000004364 calculation method Methods 0.000 description 4
- 230000001934 delay Effects 0.000 description 4
- 230000007274 generation of a signal involved in cell-cell signaling Effects 0.000 description 4
- 230000006872 improvement Effects 0.000 description 4
- 101150071746 Pbsn gene Proteins 0.000 description 3
- 238000012937 correction Methods 0.000 description 3
- 238000010295 mobile communication Methods 0.000 description 3
- 238000000926 separation method Methods 0.000 description 3
- 230000001413 cellular effect Effects 0.000 description 2
- 125000004122 cyclic group Chemical group 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 238000009826 distribution Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 239000000284 extract Substances 0.000 description 2
- 239000000945 filler Substances 0.000 description 2
- 230000010354 integration Effects 0.000 description 2
- 238000005259 measurement 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
- 101000741965 Homo sapiens Inactive tyrosine-protein kinase PRAG1 Proteins 0.000 description 1
- 102100038659 Inactive tyrosine-protein kinase PRAG1 Human genes 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
- 230000003139 buffering effect Effects 0.000 description 1
- 230000010267 cellular communication 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
- 239000003814 drug Substances 0.000 description 1
- 230000009977 dual effect Effects 0.000 description 1
- 238000005538 encapsulation Methods 0.000 description 1
- 238000001914 filtration Methods 0.000 description 1
- 238000007667 floating 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
- 238000012544 monitoring process Methods 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000008054 signal transmission Effects 0.000 description 1
- 238000000638 solvent extraction Methods 0.000 description 1
- 239000013589 supplement Substances 0.000 description 1
- 238000001356 surgical procedure Methods 0.000 description 1
- 230000009897 systematic effect Effects 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
- H04L27/00—Modulated-carrier systems
- H04L27/26—Systems using multi-frequency codes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/04—Wireless resource allocation
Definitions
- the present disclosure relates to communication devices and communication methods.
- 5th Generation mobile communication systems consist of large capacity and ultra-high speed (eMBB: enhanced Mobile Broadband), massive Machine Type Communication (mMTC), and ultra-reliable and low It has the characteristics of delay (URLLC: Ultra Reliable and Low Latency Communication), and these characteristics can be used to flexibly provide wireless communication according to a wide variety of needs.
- eMBB enhanced Mobile Broadband
- mMTC massive Machine Type Communication
- URLLC Ultra Reliable and Low Latency Communication
- the 3rd Generation Partnership Project (3GPP) an international standardization body, is working on the specification of New Radio (NR) as one of the 5G radio interfaces.
- NR New Radio
- 3GPP TS38.104 V15.14.0 “NR Base Station (BS) radio transmission and reception (Release 15),” June 2021.
- 3GPP TS38.211 V16.6.0 “NR Physical channels and modulation (Release 16),” June 2021.
- 3GPP TS38.212 V16.6.0 “NR Multiplexing and channel coding (Release 16),” June 2021.
- 3GPP TS38.213 V16.6.0 “NR Physical layer procedures for control (Release 16),” June 2021.
- 3GPP TS38.214 V16.6.0 “NR Physical layer procedures for data (Release 16),” June 2021.
- 3GPP TS38.331 V16.5.0 “NR Radio Resource Control (RRC) protocol specification (Release 16)”, June 2021.
- RRC Radio Resource Control
- a non-limiting embodiment of the present disclosure contributes to providing a communication device and a communication method that can improve communication efficiency in uplink.
- a communication device sets the reading position of the encoded data of the signal in a first interval, among a plurality of intervals in time domain resources allocated to transmission of the signal, before the first interval. and a transmission circuit for transmitting the signal based on the readout position.
- communication efficiency in uplink can be improved.
- NR for example, in addition to the frequency band below 6 GHz, which is mainly used for cellular communication, such as the 700 MHz to 3.5 GHz band (for example, also called Frequency Range 1 (FR1)), 28 GHz or 39 GHz that can secure a wide band
- FR1 Frequency Range 1
- FR2 millimeter wave band
- a higher frequency band such as the 3.5 GHz band may be used compared to the frequency band used in Long Term Evolution (LTE) or 3G (3rd Generation mobile communication systems).
- Radio Access Technology Radio Access Technology
- a terminal for example, also called User Equipment (UE)
- UE User Equipment
- a downlink control channel for example, PDCCH: Physical Downlink Control Channel
- PDCCH Physical Downlink Control Channel
- gNB base station
- DCI Downlink Control Information
- RRC Radio Resource Control
- the terminal transmits an uplink data channel (eg PUSCH: Physical Uplink Shared Channel) according to resource allocation (eg Grant or UL grant) from the base station.
- Resource allocation information included in at least one of DCI and RRC may include, for example, information on time domain resources for transmitting PUSCH.
- information on time domain resources includes information on timing (eg, slot offset) from the slot in which the terminal receives PDCCH to transmitting PUSCH (eg, K2), the position of the first symbol of PUSCH in the slot, or, Information regarding the number of symbols to transmit PUSCH may be included.
- NR uplink transmission supports a method of transmitting the same information multiple times (also called repetition).
- Release 15 (for example, expressed as “Rel.15") defines a slot-based repetition called “PUSCH repetition Type A”
- Release 16 (for example, expressed as “Rel. 16") defines "PUSCH Repetition called “repetition Type B”, which allows transmission of a plurality of PUSCHs within one slot, is stipulated.
- PUSCH repetition Type B can achieve lower delay than PUSCH repetition Type A.
- PUSCH repetition Type A for example, the same time resource allocation is applied over multiple consecutive slots.
- the base station notifies the terminal of time resource allocation in slots and the number of repetition slots.
- the number of repeated slots may be, for example, a value counted based on consecutive slots.
- the base station may, for example, notify the terminal of the time domain resource and the number of repetitions for the first (initial) PUSCH transmission.
- time domain resource allocation for the second and subsequent PUSCH transmissions for example, consecutive symbols and the same number of symbols as in the previous PUSCH transmission may be allocated.
- the number of repetition slots to be notified is a value counted based on consecutive slots, so the number of slots for actually transmitting PUSCH is less than the number of repetition slots to be notified.
- the number of repetition slots to be notified is a value counted based on consecutive slots, so the number of slots for actually transmitting PUSCH is less than the number of repetition slots to be notified.
- data size or transport block size is defined as slot Determined based on the unit resource amount, or the resource amount assigned to the initial PUSCH transmission in Repetition (for example, the resource amount assigned to the first slot PUSCH transmission in Repetition) (see, for example, Non-Patent Document 6) .
- the resource amount may be represented by, for example, the number of symbols or the number of resource elements (REs).
- TBS may be described as TB size.
- TBS calculated from the amount of resources allocated for the first PUSCH transmission in slot units or Repetition is multiplied by a scaling factor greater than 1.
- a method for determining TBS is being considered.
- a PUSCH transmission that transmits the TBs of the TBS determined by this method in multiple slots is also called "TB processing over multi-slot PUSCH (TBoMS)" or "TBoMS transmission”.
- TBoMS for example, similar to PUSCH repetition Type A, allocating the same time resource over multiple slots is being considered. Also, a parameter for determining the number of slots used for TBoMS is being considered to be included in an RRC information element (IE: Information Element) that sets information on time domain resources for transmitting PUSCH, for example.
- IE Information Element
- an RRC information element that sets information about time domain resources for transmitting PUSCH may be "PUSCH-TimeDomainResourceAllocation IE" (see Non-Patent Document 8).
- PUSCH-TimeDomainResourceAllocation for example, information on the timing from the slot in which PDCCH is received until PUSCH is transmitted (for example, slot offset), PUSCH head symbol position in slot, number of symbols for transmitting PUSCH, or TBoMS slot Numerical parameters may be included. For example, candidates for combinations of these parameters (for example, called “TDRA list” or "TDRA table”) may be set.
- the terminal may select one parameter combination for PUSCH transmission actually used by the terminal from among a plurality of parameter combination candidates, for example, using several bits of DCI or RRC that allocate the corresponding PUSCH.
- TDD Time Division Duplex
- TBoMS Time Division Duplex
- time domain resources for example, slots
- a section (group) composed of one or a plurality of consecutive slots is sometimes called "TOT: Transmission Occasion for TBoMS" (for example , see Non-Patent Document 8).
- the time domain resources allocated for TBoMS may be configured by one or multiple TOTs.
- FIG. 1 is a diagram showing an example of time domain resources allocated to TBoMS when the number of slots allocated to TBoMS is 4 slots and the number of consecutive slots constituting TOT is 2 slots.
- the time domain resource allocated for TBoMS consists of two TOTs (4 slots in total).
- Circular Buffer is used for retransmission control.
- Circular Buffer is a memory that stores encoder output (e.g., encoded data including systematic bits and parity bits, or encoded bits), and Circular Buffer specifies the number of bits of encoder output according to the amount of allocated resources. Read from the read start position (RV: Redundancy Version). The operation of reading coded bits from the specified RV in the Circular Buffer according to the allocated resource amount is also called "Rate matching".
- Rel.15/16 for example, four RV positions are defined within the Circular Buffer.
- the RV position specified in the Circular Buffer is a fixed position regardless of the allocated resource amount.
- the following three methods (Option 1, Option 2, and Option 3) are available as methods of mapping the coded bits for the TB generated by the method described above to multiple slots.
- Option 1 is a method of setting time domain resources (for example, also referred to as “TBoMS resources”) allocated to TBoMS in units of rate matching.
- TBoMS resources time domain resources allocated to TBoMS in units of rate matching.
- Option 1 reads the number of coded bits according to the resource amount of the slots used for TBoMS transmission (for example, multiple slots or one or more TOTs) from the specified RV position, This is a method of mapping read coded bits to TBoMS resources over multiple slots.
- a single RV position is used for reading coded bits.
- Fig. 2 is a diagram showing an example of TBoMS using Option 1 Rate matching.
- the TBoMS resource includes two TOTs each composed of two slots (for example, four slots in total).
- a number of coded bits corresponding to the amount of TBoMS resources are sequentially read from a single RV position, so there is a possibility of transmitting all coded bits stored in the Circular Buffer in TBoMS resources. Since it is high, there is an advantage that sufficient coding gain can be obtained and excellent decoding performance can be obtained.
- Option 1 for example, if the unit of Rate matching is the time resource allocated to TBoMS, in the calculation of the number of bits according to the allocated resource amount and the bit interleaving process, multiple Slots are considered. In this way, in Option 1, the rate matching process can be started based on the resource amounts of multiple slots, so the processing delay in the terminal tends to increase. For example, when TBoMS is transmitted using non-consecutive slots as shown in FIG. 2, the effects of processing delays in terminals can become more pronounced.
- the terminal may multiplex the UCI into the TBoMS and transmit.
- the terminal for example, considers the UCI multiplexed in the trailing slot assigned to TBoMS and starts the rate matching process, so the processing delay tends to increase.
- the processing delay in the terminal tends to increase.
- a slot in which collision processing is possible (referred to as a reference slot, for example) is set as the first slot allocated to TBoMS, which may limit the terminal processing timeline.
- Option 2 is a method of setting the slot to the rate matching unit.
- Option 2 reads the number of coded bits corresponding to the amount of resources allocated for PUSCH transmission of each slot used for TBoMS transmission from the specified RV position, and reads the read coded bits in the slot It is a method of mapping to resources individually.
- the RV positions used for reading coded bits may be different.
- slots may have their RV positions set (eg, changed) individually.
- Fig. 3 is a diagram showing an example of TBoMS using Option 2 Rate matching.
- the TBoMS resource includes two TOTs each composed of two slots (for example, four slots in total).
- Option 2 is effective, for example, from the viewpoint of supporting non-consecutive slots or facilitating handling of collision processing, and can suppress an increase in processing delay in terminals.
- collision processing can be performed on a slot-by-slot basis, and a slot in which collision processing can be performed (for example, a reference slot) can be set to a slot in which collisions can occur. No line limit.
- Option 2 for example, when reading coded bits from existing 4 RV positions such as Rel. Hateful. For example, the higher the coding rate, the fewer coded bits are read, and the more likely it is that not all coded bits are transmitted in TBoMS. Therefore, in Option 2, it is difficult to obtain a coding gain, and the decoding performance tends to deteriorate.
- Option 3 is a method of setting TOT as the unit of rate matching.
- Option 3 is a method in which the number of coded bits corresponding to the amount of TOT resources in TBoMS is read from the specified RV position, and the read coded bits are individually mapped to resources in the TOT.
- the RV positions used for reading coded bits may be different.
- the TOT may be individually set (eg, changed) to the RV position.
- Fig. 4 is a diagram showing an example of TBoMS using Option 3 Rate matching.
- the TBoMS resource includes two TOTs each composed of two slots (for example, four slots in total).
- Option 3 for example, compared to Option 1, the rate matching unit is shorter, so the impact of processing delays on the terminal can be reduced.
- Option 3 for example, compared to Option 2, it is possible to suppress deterioration in decoding performance due to not transmitting more (eg, all) coded bits.
- Option 3 for example, as shown in Fig. 4, if the TOT consists of multiple slots, as with Option 3, multiple slots are taken into account in handling collisions, so compared to Option 2, Therefore, the processing delay is likely to increase, and the terminal processing timeline may be restricted.
- RV positions e.g. RV0, RV1, RV2 and RV3
- RV positions in the Circular Buffer are fixed positions regardless of the amount of allocated resources.
- Non-Patent Document 9 As a method of maintaining slot-based processing in Option 2 and suppressing deterioration in decoding performance, there is a method of setting the RV position variably (see, for example, Non-Patent Document 9 and Non-Patent Document 10. ).
- FIG. 5 is a diagram showing an example of a rate matching method that applies a variable RV position (for example, also called “continuous RV” or “floating RV") to Option 2.
- a variable RV position for example, also called “continuous RV” or “floating RV”
- the terminal reads, for example, the number of coded bits corresponding to the amount of resources allocated for PUSCH transmission in each slot from the variable RV position, The read coded bits may be individually mapped to resources within the slot.
- the terminal may hold the number of encoded bits read in each slot, and based on the held number of encoded bits, determine the RV position when reading the encoded bits in the next slot.
- the RV position for example, the read start bit position on the Circular Buffer
- s n in the n-th slot forming the TOT may be given by the following equation (1).
- ln -1 indicates the last bit position on the Circular Buffer of the coded bits read in the (n-1)th slot. That is, the RV position s n of the nth slot may be set to the bit position next to the last bit position on the nCircular Buffer of the coded bits read in the (n ⁇ 1)th slot.
- Option 2 which applies variable RV positions, for example, even when rate matching is performed on a slot-by-slot basis, it becomes easier for the terminal to transmit continuous bit strings on the Circular Buffer, suppressing the deterioration in decoding performance described in Option 2. can.
- the rate matching unit can be a slot, so like Option 2, slot-based processing can be maintained, and the processing delay is reduced compared to Option 1 or Option 3. , and simplification of collision processing can be realized.
- Option 2 applying a fixed RV position
- the terminal since the RV position is fixed, the terminal, if information on the amount of resources allocated for PUSCH transmission of the slot to which Rate matching is applied is obtained, the slot Rate matching processing can be started regardless of the number of coded bits read in the previous slot.
- Option 2 with a fixed RV position in each of multiple slots assigned to TBoMS, it is possible to start rate matching processing without waiting for the rate matching processing of the previous slot.
- the RV position when reading coded bits (the read start bit position on the Circular Buffer) in multiple slots assigned to TBoMS is the same as the rate matching of the previous slot.
- the terminal specifies the number of coded bits read in the slot before the slot to which Rate matching is applied, and then starts Rate matching processing for that slot. In other words, the rate matching process for the slot is not started before the number of coded bits read in the slot prior to the slot to which rate matching is applied is specified.
- Option 2 which applies variable RV positions, tends to increase processing delays at terminals compared to Option 2, which applies fixed RV positions.
- the TBoMS time domain resource collides with the transmission resource for the PUCCH that transmits UCI, and the UCI is multiplexed with the PUSCH resource, the TBoMS time domain resource collides with the resource indicated by the UL CI and the PUSCH is dropped, or the time domain resource of the TBoMS collides with the allocation of the high priority uplink transmission and the PUSCH is dropped.
- the RV position when reading coded bits in a certain slot is the UCI in the slot before the slot in question.
- the downlink data channel e.g., PDSCH: Physical Downlink Shared Channel
- the DCI that transmits the UL CI or also the DCI that allocates high priority uplink transmissions.
- the decoding performance may be significantly reduced, or in the base station, processing such as blind decoding considering DCI erroneous detection in the terminal is also possible. In this case, the decoding process of the base station may be complicated.
- deterioration in decoding performance may be suppressed by applying a variable RV position to rate matching processing in units of slots in TBoMS.
- the variable RV position in each slot of TBoMS (the read start bit position on the Circular Buffer) is a resource that does not depend on the rate matching processing result in the slot before the slot ( For example, it may be determined based on the number of coded bits calculated from a reference resource (referred to as "reference resource usage").
- a communication system includes base station 100 and terminal 200 .
- FIG. 6 is a block diagram showing a configuration example of part of the base station 100 (corresponding to a communication device, for example) according to an embodiment of the present disclosure.
- the control unit 101 (for example, corresponding to a control circuit) is assigned to transmit a signal (for example, PUSCH) within a time domain resource (for example, a TBoMS resource or a resource in the TOT).
- the readout position (eg, RV position) of the coded data of the signal in the first section among the plurality of sections (eg, slots) of the first section, and the readout result of the coded data in the second section before the first section eg, It is determined based on the amount of resources (for example, reference resources) that does not depend on rate matching results).
- a receiving unit 108 (corresponding to a receiving circuit, for example) receives a signal based on the readout position.
- FIG. 7 is a block diagram showing a configuration example of part of the terminal 200 (corresponding to a communication device, for example) according to an embodiment of the present disclosure.
- control section 205 e.g., corresponding to a control circuit
- a transmission unit 209 (corresponding to, for example, a transmission circuit) transmits a signal based on the reading position.
- FIG. 8 is a block diagram showing a configuration example of base station 100 according to Embodiment 1.
- base station 100 includes control section 101, upper control signal generation section 102, downlink control information generation section 103, coding section 104, modulation section 105, signal allocation section 106, transmission section 107 , a receiving unit 108 , an extracting unit 109 , a demodulating unit 110 and a decoding unit 111 .
- the control unit 101 determines information on reception of a downlink data signal (eg, PDSCH) and information on transmission of an uplink data signal (eg, PUSCH) for the terminal 200, and transmits the determined information as a higher control signal. Output to the generation unit 102 .
- Information on reception of downlink data signals and information on transmission of uplink data signals include, for example, information on time domain resource allocation (e.g., information on TDRA tables), or information on TBoMS (e.g., information on the number of transmission slots ) may be included.
- control unit 101 for example, downlink data signal, higher control signal, or information on the downlink signal for transmitting the downlink control information (e.g., coding and modulation scheme (MCS: Modulation and Coding Scheme) and radio resource allocation), and outputs the determined information to coding section 104, modulation section 105 and signal allocation section . Also, the control section 101 outputs, for example, information on downlink signals (for example, data signals or higher control signals) to the downlink control information generating section 103 .
- MCS Modulation and Coding Scheme
- control section 101 determines information (eg, MCS and radio resource allocation) regarding transmission of uplink data signals (eg, PUSCH) in terminal 200, for example.
- the control unit 101 outputs, for example, information about the determined uplink data signal to the downlink control information generation unit 103, the extraction unit 109, the demodulation unit 110 and the decoding unit 111. Further, the control unit 101 determines at least one of the TBS in the TBoMS and the RV positions of a plurality of slots included in the TBoMS, for example, based on a method described later, and outputs the determined information to the decoding unit 111. you can
- higher layer control signal generation section 102 generates a higher layer control signal bit string based on information input from control section 101 and outputs the higher layer control signal bit string to encoding section 104 .
- Downlink control information generation section 103 generates a downlink control information (for example, DCI) bit string based on information input from control section 101, for example, and outputs the generated DCI bit string to encoding section 104. Note that the control information may be transmitted to multiple terminals.
- DCI downlink control information
- the encoding unit 104 For example, based on information input from the control unit 101, the encoding unit 104 generates downlink data (eg, DL data signal), a bit string input from the higher control signal generation unit 102, or downlink control information.
- the DCI bit string input from section 103 is encoded.
- Encoding section 104 outputs the encoded bit string to modulation section 105 .
- Modulation section 105 modulates a coded bit string input from coding section 104 based on information input from control section 101, for example, and outputs a modulated signal (for example, a symbol string) to signal allocation section 106. Output to
- Signal allocation section 106 for example, based on the information indicating the radio resource input from control section 101, the symbol sequence input from modulation section 105 (for example, including a downlink data signal or control signal) to the radio resource. map.
- the signal allocation section 106 outputs the downlink signal to which the signal is mapped to the transmission section 107 .
- the transmission section 107 performs transmission waveform generation processing such as orthogonal frequency division multiplexing (OFDM) on the signal input from the signal allocation section 106, for example.
- OFDM orthogonal frequency division multiplexing
- the transmitting unit 107 performs inverse fast Fourier transform (IFFT) processing on the signal, and adds CP to the signal after IFFT. Append.
- IFFT inverse fast Fourier transform
- transmitting section 107 performs RF processing such as D/A conversion or up-conversion on the signal, and transmits the radio signal to terminal 200 via an antenna.
- the receiving section 108 performs RF processing such as down-conversion or A/D conversion on the uplink signal from the terminal 200 received via the antenna.
- receiving section 108 performs Fast Fourier Transform (FFT) processing on the received signal, and outputs the obtained frequency domain signal to extraction section 109 .
- FFT Fast Fourier Transform
- Extracting section 109 for example, based on the information input from control section 101, from the received signal input from receiving section 108, extracts the radio resource portion in which the uplink data signal (for example, PUSCH) is transmitted, The extracted radio resource portion is output to demodulation section 110 .
- the uplink data signal for example, PUSCH
- the demodulation section 110 demodulates the uplink data signal (for example, PUSCH) input from the extraction section 109 based on information input from the control section 101, for example.
- Demodulation section 110 outputs the demodulation result to decoding section 111, for example.
- Decoding section 111 for example, based on the information input from control section 101 and the demodulation result input from demodulation section 110, performs error correction decoding of the uplink data signal (eg, PUSCH), and after decoding Obtain a received bit sequence (eg, UL data signal).
- uplink data signal eg, PUSCH
- a received bit sequence eg, UL data signal
- FIG. 9 is a block diagram showing a configuration example of terminal 200 according to an embodiment of the present disclosure.
- terminal 200 includes receiving section 201, extraction section 202, demodulation section 203, decoding section 204, control section 205, encoding section 206, modulation section 207, and signal allocation section 208. , and a transmission unit 209 .
- the receiving unit 201 receives a downlink signal (for example, a downlink data signal or downlink control information) from the base station 100 via an antenna, and down-converts or A/D converts the received radio signal. RF processing is performed to obtain a received signal (baseband signal). Further, when receiving an OFDM signal, the receiving section 201 performs FFT processing on the received signal, and transforms the received signal into the frequency domain. Receiving section 201 outputs a received signal to extracting section 202 .
- a downlink signal for example, a downlink data signal or downlink control information
- RF processing is performed to obtain a received signal (baseband signal).
- the receiving section 201 performs FFT processing on the received signal, and transforms the received signal into the frequency domain.
- Receiving section 201 outputs a received signal to extracting section 202 .
- Extracting section 202 for example, based on the information about the radio resource of the downlink control information, which is input from control section 205, from the received signal input from receiving section 201, the radio resource portion that can contain the downlink control information is extracted and output to demodulation section 203 . Also, extraction section 202 extracts a radio resource portion containing downlink data based on information about the radio resource of the data signal input from control section 205 , and outputs the radio resource portion to demodulation section 203 .
- Demodulation section 203 demodulates the signal (for example, PDCCH or PDSCH) input from extraction section 202 based on information input from control section 205 , and outputs the demodulation result to decoding section 204 .
- the signal for example, PDCCH or PDSCH
- Decoding section 204 performs error correction decoding of PDCCH or PDSCH using the demodulation result input from demodulation section 203 based on information input from control section 205, for example. A layer control signal or downlink control information is obtained. Decoding section 204 outputs an upper layer control signal and downlink control information to control section 205, and outputs downlink reception data. Also, the decoding unit 204 may generate a response signal (for example, ACK/NACK) based on the decoding result of the downlink received data.
- ACK/NACK response signal
- the control section 205 determines radio resources for at least one of PDSCH reception and PUSCH transmission, for example, based on signals input from the decoding section 204 (for example, higher layer control signals or downlink control information). Control section 205 outputs the determined information to extraction section 202, demodulation section 203, coding section 206, modulation section 207, and signal allocation section 208, for example.
- control unit 205 determines at least one of the TBS in the TBoMS and the RV positions of a plurality of slots included in the TBoMS according to the method described later, and transmits the determined information to the encoding unit 206, the modulation unit 207 and signal allocation section 208 .
- the encoding unit 206 performs error correction encoding on the uplink data signal based on information input from the control unit 205, for example. Encoding section 206 outputs the encoded bit string to modulation section 207 .
- Modulation section 207 modulates the coded bit string input from coding section 206 based on information input from control section 205, for example, and outputs the modulated signal (symbol string) to signal allocation section 208. .
- the signal allocation section 208 maps the signal input from the modulation section 207 to radio resources based on information input from the control section 205, for example.
- the signal allocation section 208 outputs, for example, the uplink signal to which the signal is mapped to the transmission section 209 .
- the transmission section 209 performs transmission signal waveform generation such as OFDM on the signal input from the signal allocation section 208 . Further, for example, in the case of OFDM transmission using CP, the transmission unit 209 performs IFFT processing on the signal and adds CP to the signal after IFFT. Alternatively, when the transmission unit 209 generates a single carrier waveform, for example, a Discrete Fourier Transform (DFT) unit may be added after the modulation unit 207 or before the signal allocation unit 208 (not shown). . Also, the transmission section 209 performs RF processing such as D/A conversion and up-conversion on the transmission signal, for example, and transmits the radio signal to the base station 100 via the antenna.
- DFT Discrete Fourier Transform
- FIG. 10 is a flow chart showing an example of operations related to TBoMS transmission in the terminal 200.
- FIG. 10 is a flow chart showing an example of operations related to TBoMS transmission in the terminal 200.
- terminal 200 receives an instruction regarding PUSCH transmission by TBoMS (for example, resource allocation information regarding TBoMS transmission) from base station 100 .
- TBoMS for example, resource allocation information regarding TBoMS transmission
- Terminal 200 determines resources or resource amounts (hereinafter also referred to as “reference resources”) used to determine RV positions (read start bit positions in Circular Buffer) in each of a plurality of slots included in TBoMS.
- reference resources resources or resource amounts (hereinafter also referred to as “reference resources”) used to determine RV positions (read start bit positions in Circular Buffer) in each of a plurality of slots included in TBoMS.
- the reference resource may be, for example, a resource amount that does not depend on the rate matching result (read result) of encoded data in slots preceding the slot in which rate matching is performed.
- the reference resource may be a resource that is determined without considering factors that may vary between slots.
- the reference resource may be a resource amount that does not depend on whether UCI is multiplexed.
- the reference resource is, for example, a dynamic SFI, UL CI, or a resource amount that does not depend on whether the PUSCH transmission is dropped due to allocation of high priority uplink transmission. good.
- the reference resource may be the resource amount (for example, the number of REs) allocated for PUSCH transmission in the first slot in the TOT.
- the resource amount of reference resources (for example, referred to as “reference resource amount”) N RE may be calculated based on the following formula (2) or formula (3).
- the upper limit of the number of REs in a slot is set to 156, for example. Note that the upper limit of the number of REs in a slot is not limited to 156, and may be another value.
- n PRB is the number of resource blocks (for example, PRB: Physical Resource Block) allocated for TBoMS transmission.
- N' RE may be calculated based on, for example, the following equation (4).
- the number of OFDM symbols allocated for PUSCH transmission in the first slot in the TOT may be notified to terminal 200 by information on the symbol length of time domain resource allocation (TDRA).
- TDRA time domain resource allocation
- Terminal 200 determines (eg, calculates) the number of encoding bits corresponding to the reference resource (hereinafter, also referred to as “the number of reference encoding bits”).
- the reference encoding bit number N ref corresponding to the reference resource is calculated based on the following formula (5) using the reference resource amount N RE calculated by formula (2) or formula (3), for example. good.
- Terminal 200 for example, based on the number of reference encoding bits and the slot index (eg, "n") of each slot included in TBoMS (or TOT), the RV position (eg, variable RV position ).
- Terminal 200 sets the RV position (read start bit position on Circular Buffer) in the first slot in TOT to the existing RV positions (for example, RV0, RV1, RV2, RV3) specified in Rel.15/16. Either) may be set.
- RV0, RV1, RV2, RV3 specified in Rel.15/16. Either
- terminal 200 may, for example, determine the RV position in a slot subsequent to the beginning within the TOT based on the reference encoding bit number N ref and the slot index n of the slot within the TOT.
- the RV position s n in the n-th slot (eg, slot index n) that constitutes the TOT may be given by Equation (6) below.
- N RVx is the RV position (for example, the bit position defined by RV0, RV1, RV2 or RV3) used in the leading slot in TOT.
- terminal 200 determines the RV position of each slot based on the reference encoding bit number N ref corresponding to the reference resource and the index of the slot. In other words, terminal 200 determines the RV position of each slot without depending on the rate matching results in the slots preceding the current slot.
- Terminal 200 performs rate matching in each slot based on the determined RV position. For example, terminal 200 sets the number of reference encoding bits corresponding to reference resources (for example, the number of bits according to the amount of resources allocated for PUSCH transmission in the first slot in TOT) to the RV position determined for each slot. (Variable RV position) and the read coded bits may be mapped to the PUSCH resources of each slot.
- reference resources for example, the number of bits according to the amount of resources allocated for PUSCH transmission in the first slot in TOT
- Terminal 200 transmits PUSCH by TBoMS, for example.
- terminal 200 sets the RV position of each slot in TOT (for example, the read start bit position in Circular Buffer) to the rate matching result of the slot before the slot. Determine uniquely without dependencies.
- FIG. 11 is a diagram showing an example of TBoMS using rate matching according to this embodiment.
- the number of slots included in TBoMS is 4 slots, and the number of TOTs is 1 (for example, the number of slots is 4).
- the terminal 200 replaces the RV position (read start bit position on the Circular Buffer) s0 in the first slot in the TOT with the existing RV position ( In FIG. 11, it may be set to RV0).
- terminal 200 may set, for example, resources allocated to PUSCH in the first slot in TOT as reference resources.
- the reference resource may be, for example, a resource amount that does not depend on the presence or absence of UCI multiplexing, as described above.
- the last bit position on the Circular Buffer of the read coded bits in the first slot when there is UCI multiplexing in the first slot may differ.
- the terminal 200 uses the PUSCH allocated resource in the leading slot in the TOT, and based on the reference resource that does not depend on UCI multiplexing, the RV in the slot after the leading slot. Determine position. Therefore, as shown in FIGS. 11(a) and 11(b), even if the last bit position (in other words, rate matching result) on the circular buffer of the read-encoded bits in the first slot is different, the terminal 200 RV positions s 1 , s 2 , and s 3 in slots after the leading slot are uniquely determined regardless of the presence or absence of UCI multiplexing.
- terminal 200 can start rate matching processing for each slot without waiting for the result of rate matching processing for the previous slot, for example.
- the last bit position ln -1 on the Circular Buffer of the read-encoded bits in the previous slot depends on the presence or absence of UCI multiplexing within the PUSCH resource. can vary.
- the RV position determination method based on Equation (6) the RV position of each slot is determined based on reference resources independent of UCI multiplexing, without being affected by the presence or absence of UCI multiplexing. Therefore, in the present embodiment, for example, the RV position of each slot does not depend on DCI that allocates PDSCHs corresponding to multiplexed UCIs. Therefore, terminal 200 is capable of robust PUSCH transmission against erroneous detection of DCI.
- terminal 200 may determine whether to actually transmit PUSCH for each slot according to the PUSCH dropping rule, for example, in uplink slots that can be used for TBoMS.
- the terminal 200 may count a slot determined not to actually transmit PUSCH (drop PUSCH transmission) as a slot constituting TOT.
- the slot index n in the TOT may be assigned to each of the slots forming the TOT regardless of whether PUSCH transmission is dropped.
- the terminal 200 may use the non-PUSCH in the slot where the collision occurs.
- a decision may be made to transmit (eg, drop PUSCH transmissions).
- terminal 200 may count slots in which PUSCH is not transmitted (slots in which PUSCH transmission is dropped) as slots constituting TOT.
- FIG. 12 is a diagram showing an example of TBoMS using rate matching according to this embodiment.
- the number of slots included in TBoMS is 4 slots, and the number of TOTs is 1 (for example, the number of slots is 4).
- n 0 for 4 slots in TOT including the 3rd slot.
- a slot index of ⁇ 3 may be set. In other words, the terminal 200 counts the third slot in which the PUSCH transmission is dropped as a slot constituting the TOT.
- Terminal 200 uses the above-described method to determine the RV position (the read start bit position on the Circular Buffer) in each of the first slot in the TOT and the n-th slot (for example, n is an integer equal to or greater than 1) that constitutes the TOT. decide.
- base station 100 determines and determines the RV position of each slot in TBoMS of terminal 200. Based on the RV position, reception processing of the signal transmitted by TBoMS from the terminal 200 may be performed.
- reference resources for example, allocated resources for the first slot in TOT
- base station 100 and terminal 200 for example, among the slots in the time domain resources allocated to TBoMS, the RV position in a certain slot, the rate matching result in the slot before the slot make decisions based on reference resources that do not depend on .
- variable RV positions can be applied to rate matching processing on a slot-by-slot basis in TBoMS, so decoding performance can be improved in the same manner as Option 2 described above.
- an increase in processing delay in terminal 200 can be suppressed by rate matching processing in units of slots.
- the RV position of each slot (the read start bit position on the Circular Buffer) is used for dynamic SFI notification (dynamic SFI), UL CI, or assignment of high-priority uplink transmission. Not affected by presence or absence. Therefore, in this embodiment, the RV position of each slot does not depend on dynamic SFI indication (dynamic SFI), UL CI, or DCI corresponding to high priority uplink transmission allocation. Therefore, the RV position determination method according to the present embodiment is robust against erroneous detection of DCI.
- the RV position is set regardless of the presence or absence of erroneous DCI detection, discrepancies in the RV position when reading encoded bits from the Circular Buffer between the base station 100 and the terminal 200 are less likely to occur. Therefore, for example, base station 100 does not need to perform decoding processing in consideration of erroneous detection of DCI in terminal 200 . Therefore, according to the present embodiment, it is possible to suppress the complexity of decoding processing in base station 100 .
- Embodiment 2 The configurations of the base station and terminal according to this embodiment may be the same as the configurations of base station 100 and terminal 200 according to Embodiment 1, respectively.
- terminal 200 determines whether or not to actually transmit the PUSCH of each slot in an uplink slot that can be used for TBoMS according to the PUSCH dropping rule, as in Embodiment 1. you can
- terminal 200 does not count a slot determined not to transmit PUSCH (drop PUSCH transmission) as a slot constituting TOT.
- the slot index n in the TOT may be attached to each of the slots that constitute the TOT, which is different from the slot in which PUSCH transmission is dropped, for example, the slot in which PUSCH transmission is performed.
- FIG. 13 is a diagram showing an example of TBoMS using rate matching according to this embodiment.
- the number of slots included in TBoMS is 4 slots, and the number of TOTs is 1 (for example, the number of slots is 4).
- n A slot index from 0 to 2 may be set. In other words, terminal 200 does not count the third slot in which the PUSCH transmission is dropped as a slot constituting the TOT.
- Terminal 200 sets the variable RV position (read start bit position on Circular Buffer) in each slot of TBoMS based on the reference encoding bit number N ref corresponding to the reference resource and the slot index n in the TOT.
- the slot index n is the index of the slot in which the PUSCH is actually transmitted, excluding the slots in which the PUSCH transmission is dropped, among the slots in the TOT.
- the reference resource may be, for example, a resource amount that does not depend on the rate matching result (read result) of encoded data in the slot preceding the slot in which rate matching is performed, as in Embodiment 1.
- the reference resource may be a resource amount that does not depend on whether or not UCI is multiplexed.
- the reference resource is, for example, a dynamic SFI, UL CI, or a resource amount that does not depend on whether the PUSCH transmission is dropped due to allocation of high priority uplink transmission. good.
- the reference resource may be the resource amount (the number of REs) allocated for PUSCH transmission in the first slot in the TOT.
- the reference encoding bit number N ref calculated based on the reference resource may be determined according to Equation (5).
- Terminal 200 for example, in the n-th slot in the TOT, the number of encoded bits corresponding to the amount of resources allocated for PUSCH transmission in the slot, the number of reference encoded bits N ref and the slot index in the TOT Read from the RV position s n given based on n, and map the read coded bits to PUSCH resources in the nth slot.
- the RV position s n at the nth PUSCH transmission (eg, slot index n) in the TOT may be given by equation (7) below.
- N RVx is the RV position (for example, the bit position defined by RV0, RV1, RV2, or RV3) used in the leading PUSCH transmission within TOT.
- terminal 200 may set, for example, resources allocated to PUSCH in the first PUSCH transmission in TOT as reference resources.
- the reference resource may be, for example, a resource amount that does not depend on UCI multiplexing, as in the first embodiment.
- the variable RV position in TBoMS, can be applied to rate matching processing on a slot-by-slot basis. It is possible to suppress an increase in processing delay in Further, in the present embodiment, the RV position of each slot is not affected by the presence or absence of dynamic SFI notification (dynamic SFI), UL CI, or allocation of high-priority uplink transmission, and supports these. Since it does not depend on DCI, the method for determining the RV position is robust against false detection of DCI, as in the first embodiment.
- dynamic SFI dynamic SFI notification
- UL CI UL CI
- allocation of high-priority uplink transmission and supports these. Since it does not depend on DCI, the method for determining the RV position is robust against false detection of DCI, as in the first embodiment.
- the RV position is set regardless of the presence or absence of erroneous detection of DCI, discrepancies in the RV position when reading encoded bits from the Circular Buffer between the base station 100 and the terminal 200 are unlikely to occur.
- base station 100 does not need to perform decoding processing in consideration of erroneous detection of DCI in terminal 200, so that complication of decoding processing in base station 100 can be suppressed.
- terminal 200 uses the number of reference encoding bits corresponding to the amount of reference resources, and a slot in a slot different from the slot in which PUSCH transmission is dropped among a plurality of slots in TOT (or TBoMS). Determine the RV position based on the index.
- the coded bits stored in the Circular Buffer are continuously transmitted in multiple slots in which PUSCH in TOT is transmitted. Since the data can be read out at the same time, it is possible to prevent deterioration of the decoding performance.
- FIG. 12 is a diagram showing an example in which PUSCH transmission in the third slot is dropped in Embodiment 1
- FIG. 13 is an example in which PUSCH transmission in the third slot is dropped in Embodiment 2.
- terminal 200 does not transmit the coded bits read from RV position s2 because the PUSCH transmission in the third slot is dropped.
- the terminal 200 transmits the coded bits read from the RV position s 2 in the PUSCH transmission of the 4th slot. .
- the coded bits stored in the Circular Buffer are evenly transmitted by TBoMS transmission, so deterioration of decoding performance can be prevented.
- the configurations of the base station and terminal according to this embodiment may be the same as the configurations of base station 100 and terminal 200 according to Embodiment 1, respectively.
- At least one of the PUSCH resources (e.g., symbols) in the assigned slot can be used for PUSCH transmission even if at least one symbol is not available for PUSCH transmission.
- a transmission method that enables transmission of PUSCH in the relevant slot when a certain number of symbols is included is being studied.
- At least one symbol is a symbol that cannot be used for PUSCH transmission, and a slot containing a certain number of symbols that can be used for PUSCH transmission is called "Special slot”. call.
- the part indicated by "U” represents PUSCH resources (symbols) in which PUSCH is actually transmitted.
- the part indicated by "D” represents the resource for transmitting the downlink signal
- the part indicated by "F” is the resource capable of transmitting both the downlink signal and the uplink signal ( flexible symbols).
- normal slots slots that are not Special slots will be referred to as "normal slots" for convenience.
- a normal slot may be a slot whose symbols constitute symbols that can be used for PUSCH transmission, such as slots #0, #2 and #3 shown in FIG.
- the terminal 200 transmits the PUSCH using the uplink symbols included in the Special slot, it is possible to improve the utilization efficiency of the uplink resources and improve the coverage performance of the PUSCH.
- the reference resource determination method for example, calculation method
- the reference resource determination method is changed depending on whether the leading slot in the TOT is a Special slot or not.
- the reference resource is, for example, the resource amount (eg, the number of REs) allocated for PUSCH transmission in the first slot in the TOT, multiplied by a scaling factor greater than 1 (eg, represented as "K"). good.
- the resources allocated for PUSCH transmission in the first slot in the TOT, which are used for calculating reference resources may be resources that do not consider UCI multiplexing.
- the reference resource amount N RE may be calculated by the method shown in Equation (8) below.
- N RE,0 indicates the resource amount (for example, the number of REs) allocated for PUSCH transmission in the first slot in the TOT given by Equation (2) or Equation (3).
- scaling factor K may be multiplied by the number of encoding bits (the number of reference encoding bits) N ref calculated based on the reference resource instead of the reference resource amount N RE,0 .
- the reference slot for calculating the reference resource amount is the leading slot in the TOT regardless of whether the leading slot of the TOT is a Special slot.
- the first normal slot in the TOT may be used as the reference slot for calculating the reference resource amount.
- the slot that serves as the basis for calculating the reference resource amount may be the leading slot.
- the slot that serves as a reference for calculating the reference resource amount may be a normal slot different from the head slot in the TOT (for example, the first normal slot).
- the terminal 200 can calculate the reference resource amount based on the normal slot, regardless of the setting of the Special slot in the TOT. Therefore, according to method 2, for example, unlike method 1, it is not necessary to adjust the scaling factor according to whether the leading slot in the TOT is a special slot, and the processing of terminal 200 can be simplified.
- ⁇ Method 3> For example, in TBoMS, as one of the methods of notifying information on time domain resource allocation, information on the number of symbols for transmitting the first symbol position of PUSCH and PUSCH in a slot (for example, SLIV: Start symbol and allocation length indicator value). There is also a method of sending multiple notifications to the terminal 200 .
- Methods of notifying multiple SLIVs include, for example, a method of individually notifying SLIVs for each slot in TBoMS, or a method of notifying different SLIVs for normal slots and special slots.
- the slots that serve as the basis for calculating the reference resource amount are multiple SLIVs.
- the largest value of symbol length (L) may be set to the notified slot.
- the terminal 200 may set the resource of the slot in which the SLIV corresponding to the normal slot is reported as the reference resource.
- terminal 200 determines the RV position of the n-th slot in TOT (the read start bit position on the Circular Buffer) based on equation (6) as in the first embodiment. Alternatively, it may be determined based on the equation (7) as in the second embodiment.
- the parameters used to determine the RV position of each slot are the number of reference encoding bits corresponding to the reference resource and the , and slot index, there is an advantage that the processing of terminal 200 can be simplified.
- setting of slot index n may be the same as in Embodiment 1 or may be the same as in Embodiment 2.
- the configurations of the base station and terminal according to this embodiment may be the same as the configurations of base station 100 and terminal 200 according to Embodiment 1, respectively.
- PUSCH resources in slots allocated to TBoMS may be allowed to differ in each slot in TOT. .
- terminal 200 may calculate reference resources based on, for example, the number of PUSCH symbols that serve as a reference (for example, expressed as “L ref ”).
- the terminal 200 sets the variable RV position (the read start bit position on the Circular Buffer) in each slot of TBoMS to the number of reference encoding bits N ref corresponding to the reference resource, the slot index n in the TOT, and It may be determined based on the ratio between the number of symbols used for actual PUSCH transmission in each slot and the number of reference PUSCH symbols (for example, expressed as “ ⁇ ”).
- setting of slot index n may be the same as in Embodiment 1 or may be the same as in Embodiment 2.
- the reference resource may be a resource amount that does not depend on the rate matching result (read result) of the encoded data in the slot preceding the slot in which rate matching is performed.
- the reference resource may be a resource amount that does not depend on whether or not UCI is multiplexed.
- the reference resource is, for example, a dynamic SFI, UL CI, or a resource amount that does not depend on whether the PUSCH transmission is dropped due to allocation of high priority uplink transmission. good.
- the reference resource amount N RE may be calculated based on Equation (9) or Equation (10) below.
- the upper limit of the number of REs in a slot is set to 156, for example. Note that the upper limit of the number of REs in a slot is not limited to 156, and may be another value.
- n PRB is the number of resource blocks (eg, number of PRBs) allocated for TBoMS transmission.
- N' RE may be calculated based on, for example, the following equation (11).
- the reference encoding bit number N ref corresponding to the reference resource is calculated based on the following equation (12) using the reference resource amount N RE calculated by equation (9) or equation (10), for example. may be
- the ratio ⁇ between the number of symbols used for actual PUSCH transmission in each slot and the number of reference PUSCH symbols is the ratio between the actual number of PUSCH symbols L n in the n-th slot and the number L REF of PUSCH symbols serving as a reference. It may be given by the ratio Ln / Lref .
- L REF 14
- the terminal 200 converts the coded bits according to the amount of resources allocated for PUSCH transmission in this slot to the number of reference coded bits N ref corresponding to the reference resource, the slot index in the TOT. n and the RV position s n given by the ratio ⁇ and maps the read coded bits to PUSCH resources in the n-th slot.
- RV position s n in the n-th slot that constitutes the TOT may be given by Equation (13) below.
- N RVx is the RV position (for example, the bit position defined by RV0, RV1, RV2 or RV3) used in the leading slot in TOT.
- terminal 200 sets the RV position in each of a plurality of slots in the TOT based on the ratio ⁇ between the number of symbols used for PUSCH transmission in each slot and the number of reference PUSCH symbols. decide.
- the ratio ⁇ the number of reference encoding bits N ref corresponding to the reference resource is the amount of resources allocated for PUSCH transmission in each slot (in other words, the ratio between the number of reference PUSCH symbols and the number of PUSCH symbols in each slot ), it is possible to improve the accuracy of rate matching in each slot and improve the decoding performance.
- the configurations of the base station and terminal according to this embodiment may be the same as the configurations of base station 100 and terminal 200 according to Embodiment 1, respectively.
- this embodiment will explain a case where the PUSCH resources in the slots allocated to TBoMS are allowed to be different for each slot in TOT, as shown in FIG.
- Embodiments 1 to 4 the method of setting reference resources for multiple slots within the TOT and determining the RV positions of each of multiple slots within the TOT based on the reference resources has been described.
- the terminal 200 sets the variable RV position (the read start bit position on the Circular Buffer) in the n-th slot of TBoMS to the number of reference encoding bits calculated based on the reference resource of the slot (for example, "N RE, n ”) and the slot index n in the TOT.
- setting of slot index n may be the same as in Embodiment 1 or may be the same as in Embodiment 2.
- the reference resource in the n-th slot in the TOT may be the resource amount (eg, the number of REs) allocated for PUSCH transmission without considering UCI multiplexing in the n-th slot.
- the reference resource amount N RE,n in the n-th slot in the TOT may be calculated based on Equation (14) or Equation (15) below.
- the upper limit of the number of REs in a slot is set to 156, for example. Note that the upper limit of the number of REs in a slot is not limited to 156, and may be another value.
- n PRB is the number of resource blocks (eg, number of PRBs) allocated for TBoMS transmission.
- N' RE may be calculated, for example, based on equation (16) below.
- the reference encoding bit number N ref (n) corresponding to the reference resource is, for example, the reference resource amount N RE,n calculated by Equation (14) or Equation (15). may be calculated based on the following equation (17).
- the terminal 200 converts the coded bits corresponding to the amount of resources allocated for PUSCH transmission in this slot to the number of reference coded bits N ref (n ), and from the RV position s n given by the slot index n in the TOT, and map the read coded bits to PUSCH resources in the nth slot.
- RV position s n in the n-th slot that constitutes the TOT may be given by Equation (18) below.
- N RVx is the RV position (eg, bit position defined by RV0, RV1, RV2 or RV3) used in the leading slot in TOT.
- terminal 200 individually configures reference resources in a plurality of slots within TOT.
- terminal 200 assigns coded bits to resources in slots according to the amount of resources allocated for PUSCH transmission in each slot (in other words, the amount of resources allocated to PUSCH transmission in each slot). Since it can be mapped, it is possible to improve the accuracy of rate matching in each slot and improve the decoding performance.
- reference resources are configured individually for each slot.
- the reference resources or the number of reference encoding bits
- the reference resources are varied between slots according to the difference in DMRS configuration between slots. Since it is also possible, compared to Embodiment 4 (method using the ratio of the number of reference PUSCH symbols and the actual number of PUSCH symbols in each slot), the accuracy of rate matching can be further improved.
- the parameters used when determining the RV position of each slot are the number of reference encoding bits corresponding to the reference resource of each slot independent of UCI multiplexing, the slot index and , there is an advantage that the processing of the terminal 200 can be simplified.
- the configurations of the base station and terminal according to this embodiment may be the same as the configurations of base station 100 and terminal 200 according to Embodiment 1, respectively.
- the time domain resources allocated to TBoMS can be composed of multiple TOTs.
- the RV position of the head slot of each TOT is determined by any of the following methods. may be determined.
- Method 1 the RV position (read start bit position on the Circular Buffer) in the first slot in the TOT is the specified RV position (for example, the read start bit position on the Circular Buffer specified by RV0, RV1, RV2 or RV3). ) is fine.
- terminal 200 may determine the RV position to be applied to PUSCH transmitted in the first slot of each TOT of TBoMS based on the RV field included in DCI. For example, when TBoMS transmission is scheduled using a DCI format that includes a 2-bit RV field, the RV applied to the leading slot of the m-th TOT may be set as shown in FIG.
- terminal 200 sets the RV positions in the leading slot to RV2, RV3, RV1, and RV0 in order from the leading TOT in TBoMS. good. RV may be similarly set for other values of the RV field shown in FIG. Note that the RV positions applied to the leading slots of each of a plurality of TOTs are not limited to the example shown in FIG.
- the RV position of the first slot in each of the multiple TOTs in the TBoMS is set to the prescribed RV position, so the processing of terminal 200 can be simplified. Also, for example, as shown in FIG. 16, the RV positions of the leading slots in each of a plurality of TOTs are evenly set to prescribed RV positions in the circular buffer, and all coded bits stored in the circular buffer can be transmitted easily, and the decoding performance can be improved.
- the RV position (read start bit position on the Circular Buffer) in the leading slot in the TOT may be set variably.
- the RV position of the first slot in the TOT may be determined based on reference resources (for example, the number of reference encoding bits).
- equation (19) is an example when the number of slots included in each TOT is the same.
- the RV position s m,0 in the leading slot of the m-th TOT can be given by the following equation (20). good.
- the RV position of the first slot in each of multiple TOTs in TBoMS is variably set according to the amount of resources (for example, reference resources) in each TOT, so it is stored in the circular buffer. Since the coded bits can be read continuously, the decoding performance can be improved.
- TBS may be calculated by the following method.
- the TBS may be determined by multiplying the TBS calculated from the amount of resources (for example, the number of symbols or the number of REs) allocated for PUSCH transmission in the first slot in the TOT by a scaling factor greater than one.
- the resource amount (the number of REs) N REs allocated for PUSCH transmission in the first slot may be calculated based on the following equation (21).
- the upper limit of the number of REs in a slot is set to 156, for example. Note that the upper limit of the number of REs in a slot is not limited to 156, and may be another value.
- n PRB is the number of resource blocks (eg, PRBs) allocated for PUSCH transmission.
- N' RE may be calculated based on, for example, the following equation (22).
- the number of OFDM symbols allocated for PUSCH transmission in the leading slot may be notified to terminal 200 by information on the symbol length of time domain resource allocation (TDRA).
- TDRA time domain resource allocation
- the TB size N info may be calculated, for example, based on the following formula (23) using the resource amount N RE allocated to PUSCH transmission in the first slot calculated by formula (21).
- Terminal 200 uses the value used to calculate TBS in PUSCH transmission, for example, in calculating the number of reference encoding bits (N ref ) corresponding to the amount of reference resources when determining the RV position of each slot in TOT.
- N ref the number of reference encoding bits
- the amount of processing or memory usage in the terminal 200 can be reduced by using the value used for calculating the TBS for calculating the reference resource.
- the reference resource is not limited to being set based on the resources in the first slot in the TOT or the first normal slot in the TOT, and any It may be set based on the resource of any slot.
- Option 2 Rent matching per slot
- Option 3 Rent matching in TOT units
- slot-based processing and slot-specific or common parameters in each of the above-described embodiments may be read as TOT-based processing and TOT-specific or common parameters.
- TOT may be the unit of one TBoMS transmission (Single TBoMS). Also, TBoMS repetition transmission (Repetition) that transmits a plurality of TBoMS transmission units may be applied. In this case, for example, the TOT in the above-described embodiment may be read as the unit of one TBoMS transmission (Single TBoMS).
- the number of reference encoding bits may be the number of bits excluding Filler bits of the LDPC code.
- the RV position s n in the n-th slot constituting the TOT may be given by the following equation (24). .
- the calculation of the RV position may be given by a modulo operation modulo the Circular Buffer size or the Circular Buffer length Ncb .
- the RV position s n in the n-th slot forming the TOT may be given by Equation (25) below.
- PUSCH resources that can be used for PUSCH transmission are not limited to uplink symbols (U), and may include flexible symbols (F).
- TBoMS transmission was described as an example of PUSCH transmission using multiple slots, but PUSCH transmission using multiple slots is not limited to TBoMS transmission, and other transmissions. can be a method. Also, transmission using multiple slots is not limited to PUSCH transmission, and may be transmission of other channels or signals.
- the communication device that transmits data is not limited to the terminal 200, and may be the base station 100.
- the communication device that receives data is not limited to the base station 100 and may be the terminal 200 .
- each embodiment or each modification may be applied not only to uplink transmission but also to downlink transmission or sidelink transmission.
- inventions, variations, and methods of each embodiment in one non-limiting example of the present disclosure may be switchable and differentiated for different communication methods (types) or channel/signal types. good too.
- the name of the information element used in the non-limiting embodiment of the present disclosure or the name of the parameter set in the information element is an example, and other names may be used.
- the number of slots constituting a TBoMS, the number of slots constituting a TOT, the number of TOTs included in the TBoMS, the number of symbols in a slot, the slot type in the TOT (for example, "D", "U” or "F") settings, and the specified number of RV positions are only examples, and other values may be used.
- (supplement) Information indicating whether the terminal 200 supports the functions, operations, or processes shown in each embodiment and each modification described above is, for example, capability information or a capability parameter of the terminal 200, from the terminal 200 It may be transmitted (or notified) to base station 100 .
- 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 each embodiment and each modification described above.
- the capability information may include an information element indicating whether the terminal 200 supports a combination of two or more of the functions, operations, or processes shown in each embodiment and each modification described above.
- 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.
- base station 100 may control TBoMS transmission based on capability information received from terminal 200 .
- terminal 200 not supporting part of the functions, operations, or processes shown in each of the above-described embodiments and modifications means that such functions, operations, or processes are restricted in terminal 200. It may be read as For example, 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.
- the downlink control signal (information) related to the present disclosure may be a signal (information) transmitted by PDCCH of the physical layer, a signal (information) transmitted by MAC CE (Control Element) or RRC of the higher layer ) can be used. Also, the downlink control signal may be a signal (information) defined in advance.
- the uplink control signal (information) related to the present disclosure may be a signal (information) transmitted by PUCCH of the physical layer, or may be a signal (information) transmitted by MAC CE or RRC of the higher layer. Also, the uplink control signal may be a signal (information) defined in advance. Also, the uplink control signal may be replaced with UCI (uplink control information), 1st stage SCI (sidelink control information), and 2nd stage SCI.
- the base station includes TRP (Transmission Reception Point), cluster head, access point, RRH (Remote Radio Head), eNodeB (eNB), gNodeB (gNB), BS (Base Station), BTS (Base Transceiver Station) , parent device, gateway, or the like.
- TRP Transmission Reception Point
- eNB eNodeB
- gNodeB gNB
- BTS Base Transceiver Station
- parent device gateway, or the like.
- a terminal may serve as a base station.
- a base station may be a relay device that relays communication between an upper node and a terminal.
- the base station may be a roadside device.
- the present disclosure may be applied to any of uplink, downlink, and sidelink.
- the present disclosure to uplink PUSCH, PUCCH, PRACH, downlink PDSCH, PDCCH, PBCH, sidelink PSSCH (Physical Sidelink Shared Channel), PSCCH (Physical Sidelink Control Channel), PSBCH (Physical Sidelink Broadcast Channel) may apply.
- PDCCH, PDSCH, PUSCH, and PUCCH are examples of downlink control channels, downlink data channels, uplink data channels, and uplink control channels.
- 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.
- the present disclosure may apply to both data channels and control channels.
- the channels of the present disclosure may be replaced with data channels PDSCH, PUSCH, and PSSCH, and control channels PDCCH, PUCCH, PBCH, PSCCH, and PSBCH.
- the reference signal is a signal known to both the base station and the terminal, and is also called RS (Reference Signal) or pilot signal.
- Reference signals are DMRS, CSI-RS (Channel State Information - Reference Signal), TRS (Tracking Reference Signal), PTRS (Phase Tracking Reference Signal), CRS (Cell-specific Reference Signal), SRS (Sounding Reference Signal). or
- the unit of time resources is not limited to one or a combination of slots and symbols, for example, frames, superframes, subframes, slots, time slots, subslots, minislots or symbols, OFDM Division Multiplexing) symbols, SC-FDMA (Single Carrier-Frequency Division Multiple Access) symbols, or other time resource units.
- 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.
- the present disclosure may be applied to both licensed bands and unlicensed bands.
- the present disclosure may be applied to any of communication between base stations and terminals (Uu link communication), communication between terminals (Sidelink communication), and V2X (Vehicle to Everything) communication.
- the channels of the present disclosure may be replaced with PSCCH, PSSCH, PSFCH (Physical Sidelink Feedback Channel), PSBCH, PDCCH, PUCCH, PDSCH, PUSCH, and PBCH.
- the present disclosure may be applied to both terrestrial networks and non-terrestrial networks (NTN: Non-Terrestrial Network) using satellites and advanced pseudolites (HAPS).
- NTN Non-Terrestrial Network
- HAPS advanced pseudolites
- the present disclosure may also be applied to terrestrial networks with large transmission delays compared to symbol lengths and slot lengths, such as networks with large cell sizes and ultra-wideband transmission networks.
- An antenna port refers to a logical antenna (antenna group) composed of one or more physical antennas.
- the 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.
- how many physical antennas constitute an antenna port is not specified, but is specified as the minimum unit in which a terminal 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
- UPF User Plane Function
- the NR user plane protocol stack (e.g., 3GPP TS 38.300, see 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. 18 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 19 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 20 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 20 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. 21 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. 20
- Policy Control Function Policy Control Function (PCF) reference).
- Application Functions that are considered operator-trusted, based on their deployment by the operator, can interact directly with the associated Network 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 21 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 communication device sets the reading position of the encoded data of the signal in a first interval, among a plurality of intervals in time domain resources allocated to transmission of the signal, before the first interval. and a transmission circuit for transmitting the signal based on the readout position.
- the resource amount is a resource amount that does not depend on the presence or absence of multiplexing of uplink control information.
- the resource amount is a resource amount independent of whether transmission of the signal is dropped.
- control circuit determines the readout position based on the number of encoding bits corresponding to the resource amount and the index of the first section in the plurality of sections.
- control circuit includes a coding bit number corresponding to the resource amount and an index of the first interval in an interval different from an interval in which transmission of the signal is dropped among the plurality of intervals. and determines the readout position.
- control circuit varies the resource amount determination method depending on whether the leading section of the time domain resource is a special slot or not.
- control circuit determines the read position in each of the plurality of sections based on a ratio between the number of symbols used for transmitting the signal in the section and a reference value for the number of symbols. decide.
- control circuit individually sets the resource amounts for the plurality of intervals.
- the time-domain resource includes at least one group consisting of one or a plurality of consecutive intervals, and the readout position in the first interval in the group is a specified position be.
- the time-domain resource includes at least one group consisting of one or a plurality of consecutive intervals, and the readout position in the first interval in the group is equal to the amount of resources. determined based on
- control circuit uses the value used to calculate the transport block size of the signal in calculating the resource amount.
- a communication device sets the reading position of the encoded data of the signal in the first section among a plurality of sections in the time domain resource allocated to the transmission of the signal to A control circuit that determines based on a resource amount that does not depend on the readout result of the encoded data in the second interval, and a transmission circuit that receives the signal based on the readout position.
- the communication device sets the reading position of the coded data of the signal in the first section among a plurality of sections within the time domain resource allocated to the transmission of the signal to the The determination is made based on the amount of resources that does not depend on the result of reading the encoded data in the second section before the first section, and the signal is transmitted based on the reading position.
- the communication device sets the reading position of the encoded data of the signal in the first section among a plurality of sections in the time domain resource allocated for transmission of the signal to the first The signal is received based on the reading position, determined based on the amount of resources that does not depend on the reading result of the encoded data in the second section preceding the section.
- An embodiment of the present disclosure is useful for wireless communication systems.
Abstract
Description
NRでは、例えば、再送制御にCircular Bufferが用いられる。Circular Bufferは、符号器出力(例えば、システマチックビット及びパリティビットを含む符号化データ又は符号化ビット)を格納したメモリであり、割当リソース量に応じたビット数の符号器出力をCircular Bufferにおいて規定の読み出し開始位置(RV: Redundancy Version)から読み出す。割り当てリソース量に応じてCircular Bufferにおける規定のRVから符号化ビットを読み出す動作は「Rate matching」とも呼ばれる。
Option 1は、TBoMSに割り当てられる時間領域リソース(例えば、「TBoMSリソース」とも呼ぶ)を、Rate matchingの単位に設定する方法である。
Option 2は、スロットを、Rate matchingの単位に設定する方法である。
Option 3は、TOTを、Rate matchingの単位に設定する方法である。
[通信システムの概要]
本開示の各実施の形態に係る通信システムは、基地局100及び端末200を備える。
図8は、実施の形態1に係る基地局100の構成例を示すブロック図である。図8において、基地局100は、制御部101と、上位制御信号生成部102と、下りリンク制御情報生成部103と、符号化部104と、変調部105と、信号割当部106と、送信部107と、受信部108と、抽出部109と、復調部110と、復号部111と、を有する。
図9は、本開示の一実施例に係る端末200の構成例を示すブロック図である。例えば、図9において、端末200は、受信部201と、抽出部202と、復調部203と、復号部204と、制御部205と、符号化部206と、変調部207と、信号割当部208と、送信部209と、を有する。
以上の構成を有する基地局100及び端末200における動作例について説明する。
図10において、端末200は、TBoMSによるPUSCH送信に関する指示(例えば、TBoMS送信に関するリソース割当情報)を基地局100から受信する。
端末200は、例えば、TBoMSに含まれる複数のスロットのそれぞれにおけるRV位置(Circular Bufferにおける読み出し開始ビット位置)の決定に用いるリソース又はリソース量(以下、「参照リソース」とも呼ぶ)を決定する。
端末200は、例えば、参照リソースに対応する符号化ビット数(以下、「参照符号化ビット数」とも呼ぶ)を決定(例えば、算出)する。
端末200は、例えば、参照符号化ビット数と、TBoMS(又は、TOT)に含まれる各スロットのスロットインデックス(例えば、「n」)とに基づいて、各スロットにおけるRV位置(例えば、可変RV位置)を決定する。
端末200は、決定したRV位置に基づいて、各スロットにおいてRate matchingを行う。例えば、端末200は、参照リソースに対応する参照符号化ビット数(例えば、TOT内の先頭スロットのPUSCH送信に割り当てられるリソース量に応じたビット数)を、各スロットに対して決定されたRV位置(可変RV位置)から読み出し、読み出した符号化ビットを、各スロットのPUSCHリソースにマッピングしてよい。
端末200は、例えば、TBoMSによってPUSCHを送信する。
本実施の形態に係る基地局及び端末の構成は、実施の形態1に係る基地局100及び端末200の構成と同様でよい。
本実施の形態に係る基地局及び端末の構成は、実施の形態1に係る基地局100及び端末200の構成と同様でよい。
方法1では、参照リソースは、例えば、TOT内の先頭スロットのPUSCH送信に割り当てられるリソース量(例えば、RE数)に、1より大きいスケーリング係数(例えば、「K」と表す)を乗算した値でよい。なお、参照リソースの算出に使用される、TOT内の先頭スロットのPUSCH送信に割り当てられるリソースは、UCI多重を考慮しないリソースでよい。
方法1では、例えば、参照リソース量を算出する基準となるスロットは、TOTの先頭スロットがSpecial slotであるか否かに依らずTOT内の先頭スロットである。方法2では、例えば、参照リソース量を算出する基準となるスロットは、TOT内の最初の通常スロットでよい。
例えば、TBoMSでは、時間領域リソース割り当てに関する情報の通知方法の一つとして、スロット内のPUSCHの先頭シンボル位置及びPUSCHを送信するシンボル数に関する情報(例えば、SLIV:Start symbol and allocation Length Indicator Value)を端末200へ複数通知する方法もある。
本実施の形態に係る基地局及び端末の構成は、実施の形態1に係る基地局100及び端末200の構成と同様でよい。
から読み出し、読み出した符号化ビットを第nスロット内のPUSCHリソースにマッピングする。
本実施の形態に係る基地局及び端末の構成は、実施の形態1に係る基地局100及び端末200の構成と同様でよい。
本実施の形態に係る基地局及び端末の構成は、実施の形態1に係る基地局100及び端末200の構成と同様でよい。
方法1では、TOT内の先頭スロットにおけるRV位置(Circular Buffer上の読み出し開始ビット位置)は、規定のRV位置(例えば、RV0、RV1、RV2又はRV3によって規定されるCircular Buffer上の読み出し開始ビット位置)でよい。
方法2では、TOT内の先頭スロットにおけるRV位置(Circular Buffer上の読み出し開始ビット位置)は、可変に設定されてよい。例えば、TOT内の先頭スロットのRV位置は、参照リソース(例えば、参照符号化ビット数)に基づいて決定されてよい。
TBoMSでは、例えば、以下の方法によりTBSが算出されてもよい。
上述した各実施の形態及び各変形例に示した機能、動作又は処理を端末200がサポートするか否かを示す情報が、例えば、端末200の能力(capability)情報あるいは能力パラメータとして、端末200から基地局100へ送信(あるいは通知)されてもよい。
本開示において、本開示に関連する下り制御信号(情報)は、物理層のPDCCHで送信される信号(情報)でもよく、上位レイヤのMAC CE(Control Element)又はRRCで送信される信号(情報)でもよい。また、下り制御信号は、予め規定されている信号(情報)としてもよい。
本開示において、基地局は、TRP(Transmission Reception Point)、クラスタヘッド、アクセスポイント、RRH(Remote Radio Head)、eNodeB (eNB)、gNodeB(gNB)、BS(Base Station)、BTS(Base Transceiver Station)、親機、ゲートウェイ等でもよい。また、サイドリンク通信においては、端末が、基地局の役割を担ってもよい。基地局は、上位ノードと端末の通信を中継する中継装置であってもよい。また、基地局は、路側器であってもよい。
本開示は、上りリンク、下りリンク、サイドリンクのいずれに適用してもよい。例えば、本開示を上りリンクのPUSCH、PUCCH、PRACH、下りリンクのPDSCH、PDCCH、PBCH、サイドリンクのPSSCH(Physical Sidelink Shared Channel)、PSCCH(Physical Sidelink Control Channel)、PSBCH(Physical Sidelink Broadcast Channel)に適用してもよい。
本開示は、データチャネル及び制御チャネルのいずれに適用してもよい。例えば、本開示のチャネルをデータチャネルのPDSCH、PUSCH、PSSCH、制御チャネルのPDCCH、PUCCH、PBCH、PSCCH、PSBCHに置き換えてもよい。
本開示において、参照信号は、基地局及び端末の双方で既知の信号であり、RS (Reference Signal)又はパイロット信号と呼ばれることもある。参照信号は、DMRS、CSI-RS(Channel State Information - Reference Signal)、TRS(Tracking Reference Signal)、PTRS(Phase Tracking Reference Signal)、CRS(Cell-specific Reference Signal), SRS(Sounding Reference Signal)のいずれかであってもよい。
本開示において、時間リソースの単位は、スロット及びシンボルの1つ又は組み合わせに限らず、例えば、フレーム、スーパーフレーム、サブフレーム、スロット、タイムスロット、サブスロット、ミニスロット又は、シンボル、OFDM(Orthogonal Frequency Division Multiplexing)シンボル、SC-FDMA(Single Carrier - Frequency Division Multiple Access)シンボルといった時間リソース単位でもよく、他の時間リソース単位でもよい。また、1スロットに含まれるシンボル数は、上述した実施の形態において例示したシンボル数に限定されず、他のシンボル数でもよい。
本開示は、ライセンスバンド、アンライセンスバンドのいずれに適用してもよい。
本開示は、基地局と端末との間の通信(Uuリンク通信)、端末と端末との間の通信(Sidelink通信)、V2X(Vehicle to Everything)の通信のいずれに適用してもよい。例えば、本開示のチャネルをPSCCH、PSSCH、PSFCH(Physical Sidelink Feedback Channel)、PSBCH、PDCCH、PUCCH、PDSCH、PUSCH、PBCHに置き換えてもよい。
アンテナポートは、1本または複数の物理アンテナから構成される論理的なアンテナ(アンテナグループ)を指す。すなわち、アンテナポートは必ずしも1本の物理アンテナを指すとは限らず、複数のアンテナから構成されるアレイアンテナ等を指すことがある。例えば、アンテナポートが何本の物理アンテナから構成されるかは規定されず、端末が参照信号(Reference signal)を送信できる最小単位として規定される。また、アンテナポートはプリコーディングベクトル(Precoding vector)の重み付けを乗算する最小単位として規定されることもある。
3GPPは、100GHzまでの周波数範囲で動作する新無線アクセス技術(NR)の開発を含む第5世代携帯電話技術(単に「5G」ともいう)の次のリリースに向けて作業を続けている。5G規格の初版は2017年の終わりに完成しており、これにより、5G NRの規格に準拠した端末(例えば、スマートフォン)の試作および商用展開に移ることが可能である。
図18は、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;
- 下りリンクデータの通知。
図19は、NAS部分の、UEがRRC_IDLEからRRC_CONNECTEDに移行する際のUE、gNB、およびAMF(5GCエンティティ)の間のやり取りのいくつかを示す(TS 38.300 v15.6.0参照)。
図20は、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のための標準化が含まれる。図20は、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、205 制御部
102 上位制御信号生成部
103 下りリンク制御情報生成部
104、206 符号化部
105、207 変調部
106、208 信号割当部
107、209 送信部
108、201 受信部
109、202 抽出部
110、203 復調部
111、204 復号部
200 端末
Claims (14)
- 信号の送信に割り当てられる時間領域リソース内の複数の区間のうち、第1区間における前記信号の符号化データの読み出し位置を、前記第1区間より前の第2区間における前記符号化データの読み出し結果に依存しないリソース量に基づいて決定する制御回路と、
前記読み出し位置に基づいて、前記信号を送信する送信回路と、
を具備する通信装置。 - 前記リソース量は、上り制御情報の多重の有無に依存しないリソース量である、
請求項1に記載の通信装置。 - 前記リソース量は、前記信号の送信がドロップされたか否かに依存しないリソース量である、
請求項1に記載の通信装置。 - 前記制御回路は、前記リソース量に対応する符号化ビット数と、前記複数の区間における前記第1区間のインデックスとに基づいて、前記読み出し位置を決定する、
請求項1に記載の通信装置。 - 前記制御回路は、前記リソース量に対応する符号化ビット数と、前記複数の区間のうち前記信号の送信がドロップされる区間と異なる区間における前記第1区間のインデックスとに基づいて、前記読み出し位置を決定する、
請求項1に記載の通信装置。 - 前記制御回路は、前記時間領域リソースの先頭の区間が、スペシャルスロットであるか否かに応じて、前記リソース量の決定方法を異ならせる、
請求項1に記載の通信装置。 - 前記制御回路は、前記複数の区間のそれぞれにおける前記読み出し位置を、当該区間において前記信号の送信に使用するシンボル数と、シンボル数に関する基準値との比率に基づいて決定する、
請求項1に記載の通信装置。 - 前記制御回路は、前記リソース量を、前記複数の区間に個別に設定する、
請求項1に記載の通信装置。 - 前記時間領域リソースは、1つ又は連続する複数の区間によって構成されるグループを少なくとも一つ含み、
前記グループ内の先頭の区間における前記読み出し位置は、規定の位置である、
請求項1に記載の通信装置。 - 前記時間領域リソースは、1つ又は連続する複数の区間によって構成されるグループを少なくとも一つ含み、
前記グループ内の先頭の区間における前記読み出し位置は、前記リソース量に基づいて決定される、
請求項1に記載の通信装置。 - 前記制御回路は、前記リソース量の算出において、前記信号のトランスポートブロックサイズの算出に用いた値を使用する、
請求項1に記載の通信装置。 - 信号の送信に割り当てられる時間領域リソース内の複数の区間のうち第1区間における前記信号の符号化データの読み出し位置を、前記第1区間より前の第2区間における前記符号化データの読み出し結果に依存しないリソース量に基づいて決定する制御回路と、
前記読み出し位置に基づいて、前記信号を受信する送信回路と、
を具備する通信装置。 - 通信装置は、
信号の送信に割り当てられる時間領域リソース内の複数の区間のうち、第1区間における前記信号の符号化データの読み出し位置を、前記第1区間より前の第2区間における前記符号化データの読み出し結果に依存しないリソース量に基づいて決定し、
前記読み出し位置に基づいて、前記信号を送信する、
通信方法。 - 通信装置は、
信号の送信に割り当てられる時間領域リソース内の複数の区間のうち第1区間における前記信号の符号化データの読み出し位置を、前記第1区間より前の第2区間における前記符号化データの読み出し結果に依存しないリソース量に基づいて決定し、
前記読み出し位置に基づいて、前記信号を受信する、
通信方法。
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202280050022.1A CN117678207A (zh) | 2021-08-02 | 2022-05-06 | 通信装置及通信方法 |
KR1020247001052A KR20240042599A (ko) | 2021-08-02 | 2022-05-06 | 통신 장치, 및, 통신 방법 |
JP2023539651A JPWO2023013191A5 (ja) | 2022-05-06 | 通信装置、通信方法及び集積回路 |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2021126687 | 2021-08-02 | ||
JP2021-126687 | 2021-08-02 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2023013191A1 true WO2023013191A1 (ja) | 2023-02-09 |
Family
ID=85155718
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2022/019551 WO2023013191A1 (ja) | 2021-08-02 | 2022-05-06 | 通信装置、及び、通信方法 |
Country Status (4)
Country | Link |
---|---|
KR (1) | KR20240042599A (ja) |
CN (1) | CN117678207A (ja) |
TW (1) | TW202329730A (ja) |
WO (1) | WO2023013191A1 (ja) |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2010528554A (ja) * | 2007-05-29 | 2010-08-19 | サムスン エレクトロニクス カンパニー リミテッド | 移動通信システムにおけるシンボルをリソースにマッピングする装置及び方法 |
JP2021126687A (ja) | 2020-02-14 | 2021-09-02 | 三菱電機株式会社 | 実装基板の製造装置および実装基板の製造方法 |
-
2022
- 2022-05-06 WO PCT/JP2022/019551 patent/WO2023013191A1/ja active Application Filing
- 2022-05-06 KR KR1020247001052A patent/KR20240042599A/ko unknown
- 2022-05-06 CN CN202280050022.1A patent/CN117678207A/zh active Pending
- 2022-06-17 TW TW111122672A patent/TW202329730A/zh unknown
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2010528554A (ja) * | 2007-05-29 | 2010-08-19 | サムスン エレクトロニクス カンパニー リミテッド | 移動通信システムにおけるシンボルをリソースにマッピングする装置及び方法 |
JP2021126687A (ja) | 2020-02-14 | 2021-09-02 | 三菱電機株式会社 | 実装基板の製造装置および実装基板の製造方法 |
Non-Patent Citations (12)
Title |
---|
"Discussion on TB processing over multi-slot PUSCH", 3GPP TSG RAN WG1 #105-E, R1-2104242, May 2021 (2021-05-01) |
"Final FL summary of TB processing over multi-slot PUSCH (AI 8.8.1.2", 3GPP TSG RAN WG1 #105-E, R1-2106251, May 2021 (2021-05-01) |
"New WID on NR coverage enhancements", 3GPP TSG RAN MEETING #90E, RP-202928, December 2020 (2020-12-01) |
"NR Base Station (BS) radio transmission and reception (Release 15", 3GPP TS38.104 V15.14.0, June 2021 (2021-06-01) |
"NR Multiplexing and channel coding (Release 16", 3GPP TS38.212 V16.6.0, June 2021 (2021-06-01) |
"NR Physical channels and modulation (Release 16", 3GPP TS38.211 V16.6.0, June 2021 (2021-06-01) |
"NR Physical layer procedures for control (Release 16", 3GPP TS38.213 V16.6.0, June 2021 (2021-06-01) |
"NR Physical layer procedures for data (Release 16", 3GPP TS38.214 V16.6.0, June 2021 (2021-06-01) |
"NR Radio Resource Control (RRC) protocol specification (Release 16", 3GPP TS38.331 V16.5.0, June 2021 (2021-06-01) |
"TB processing over multi-slot PUSCH", 3GPP TSG RAN WG1 #104-BIS-E, R1-2104686, May 2021 (2021-05-01) |
MODERATOR (NOKIA, NOKIA SHANGHAI BELL): "Final FL summary of TB processing over multi-slot PUSCH (AI 8.8.1.2)", 3GPP DRAFT; R1-2106251, vol. RAN WG1, 27 May 2021 (2021-05-27), pages 1 - 100, XP052015770 * |
SHARP: "TB processing over multi-slot PUSCH", 3GPP DRAFT; R1-2103480, vol. RAN WG1, 7 April 2021 (2021-04-07), pages 1 - 6, XP052178201 * |
Also Published As
Publication number | Publication date |
---|---|
TW202329730A (zh) | 2023-07-16 |
JPWO2023013191A1 (ja) | 2023-02-09 |
KR20240042599A (ko) | 2024-04-02 |
CN117678207A (zh) | 2024-03-08 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2021161861A1 (ja) | 端末及び通信方法 | |
US20220256557A1 (en) | Communication apparatuses and communication methods for dci for v2x communication apparatuses | |
CN115428558A (zh) | 移动台、基站、接收方法及发送方法 | |
WO2022014272A1 (ja) | 端末、基地局及び通信方法 | |
WO2023013191A1 (ja) | 通信装置、及び、通信方法 | |
JP2023514076A (ja) | 予約されたリソースを利用する通信装置および通信方法 | |
WO2022239289A1 (ja) | 通信装置、及び、通信方法 | |
WO2022195952A1 (ja) | 端末、基地局及び通信方法 | |
WO2023203938A1 (ja) | 端末、基地局、通信方法及び集積回路 | |
WO2023013192A1 (ja) | 端末、基地局及び通信方法 | |
WO2023119756A1 (ja) | 通信装置及び通信方法 | |
WO2023181557A1 (ja) | 端末、基地局及び通信方法 | |
WO2023013217A1 (ja) | 基地局、端末及び通信方法 | |
WO2022208989A1 (ja) | 通信装置、及び、通信方法 | |
WO2023181556A1 (ja) | 端末、基地局及び通信方法 | |
WO2023181579A1 (ja) | 端末、基地局及び通信方法 | |
WO2023100470A1 (ja) | 基地局、端末及び通信方法 | |
WO2023013204A1 (ja) | 端末、基地局、及び、通信方法 | |
WO2022215390A1 (ja) | 端末、基地局及び通信方法 | |
WO2023188913A1 (ja) | 基地局、端末及び通信方法 | |
WO2024029157A1 (ja) | 端末、基地局、及び、通信方法 | |
WO2023188912A1 (ja) | 基地局、端末及び通信方法 | |
WO2023139852A1 (ja) | 端末、基地局、及び、通信方法 | |
WO2024024259A1 (ja) | 端末、基地局、及び、通信方法 | |
WO2023100471A1 (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: 22852620 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: MX/A/2024/000292 Country of ref document: MX |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2023539651 Country of ref document: JP |
|
REG | Reference to national code |
Ref country code: BR Ref legal event code: B01A Ref document number: 112024000464 Country of ref document: BR |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2022852620 Country of ref document: EP Effective date: 20240304 |
|
ENP | Entry into the national phase |
Ref document number: 112024000464 Country of ref document: BR Kind code of ref document: A2 Effective date: 20240109 |