WO2023079713A1 - 端末、無線通信システム及び無線通信方法 - Google Patents
端末、無線通信システム及び無線通信方法 Download PDFInfo
- Publication number
- WO2023079713A1 WO2023079713A1 PCT/JP2021/040892 JP2021040892W WO2023079713A1 WO 2023079713 A1 WO2023079713 A1 WO 2023079713A1 JP 2021040892 W JP2021040892 W JP 2021040892W WO 2023079713 A1 WO2023079713 A1 WO 2023079713A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- pusch
- downlink data
- pdsch
- data channels
- scheduled
- Prior art date
Links
- 238000004891 communication Methods 0.000 title claims description 78
- 238000000034 method Methods 0.000 title claims description 29
- 230000005540 biological transmission Effects 0.000 description 32
- 238000012545 processing Methods 0.000 description 16
- 230000008569 process Effects 0.000 description 14
- 238000010586 diagram Methods 0.000 description 13
- 230000006870 function Effects 0.000 description 12
- 230000011664 signaling Effects 0.000 description 8
- 230000009471 action Effects 0.000 description 6
- 230000006399 behavior Effects 0.000 description 6
- 238000001514 detection method Methods 0.000 description 6
- 238000013468 resource allocation Methods 0.000 description 6
- 230000001133 acceleration Effects 0.000 description 5
- 125000004122 cyclic group Chemical group 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 4
- 238000012986 modification Methods 0.000 description 4
- 230000004048 modification Effects 0.000 description 4
- 238000013473 artificial intelligence Methods 0.000 description 3
- 238000013507 mapping Methods 0.000 description 3
- 238000010295 mobile communication Methods 0.000 description 3
- 230000001960 triggered effect Effects 0.000 description 3
- 230000002776 aggregation Effects 0.000 description 2
- 238000004220 aggregation Methods 0.000 description 2
- 239000000969 carrier Substances 0.000 description 2
- 230000008878 coupling Effects 0.000 description 2
- 238000010168 coupling process Methods 0.000 description 2
- 238000005859 coupling reaction Methods 0.000 description 2
- 230000009977 dual effect Effects 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 238000005259 measurement Methods 0.000 description 2
- 230000008054 signal transmission Effects 0.000 description 2
- 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
- 101150071746 Pbsn gene Proteins 0.000 description 1
- 230000006978 adaptation Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 239000003795 chemical substances by application Substances 0.000 description 1
- 238000012937 correction Methods 0.000 description 1
- 238000005562 fading Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 238000001914 filtration Methods 0.000 description 1
- 238000011010 flushing procedure Methods 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 239000006249 magnetic particle Substances 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 230000005855 radiation Effects 0.000 description 1
- 230000011218 segmentation Effects 0.000 description 1
- 238000013519 translation Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/04—Error control
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/04—Wireless resource allocation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/12—Wireless traffic scheduling
Definitions
- the present disclosure relates to terminals, wireless communication systems, and wireless communication methods that support multi-PDSCH/PUSCH scheduling.
- the 3rd Generation Partnership Project (3GPP) has specified the 5th generation mobile communication system (also called 5G, New Radio (NR) or Next Generation (NG)), and the next generation specification called Beyond 5G, 5G Evolution or 6G We are also proceeding with 5G, 5G Evolution or 6G We are also proceeding with 5G, 5G Evolution or 6G We are also proceeding with 5G, 5G Evolution or 6G We are also proceeding with 5G, 5G Evolution or 6G We are also proceeding with 5G, 5G Evolution or 6G
- 3GPP Release-17 supports frequency bands above 52.6 GHz and up to 71 GHz. Scheduling of a plurality of PDSCH (Physical Downlink Shared Channel)/PUSCH (Physical Uplink Shared Channel) (multi-PDSCH/PUSCH scheduling) is possible (Non-Patent Document 1).
- multi-PDSCH scheduling allows collisions (overlapping radio resource allocations) with semi-static uplink (UL) symbols (for Time Division Duplex (TDD) ). Also, multi-PUSCH scheduling allows collisions with semi-static downlink (DL) symbols.
- the terminal User Equipment, UE
- the terminal continues to receive the data channel normally even if the collision occurs. There is a need to.
- the following disclosure is made in view of such a situation, and even if collision between PDSCH/PUSCH and UL/DL symbols is allowed, a terminal that can continue to receive the data channel normally , to provide a wireless communication system and a wireless communication method.
- One aspect of the present disclosure is a receiving unit (data transmitting/receiving unit 260) that receives a plurality of downlink data channels scheduled by a single downlink control information, and any downlink data channel collides with an uplink symbol.
- the terminal (UE 200) includes a control unit (control unit 270) that assumes that the downlink data channel canceled due to the collision is excluded from specific scheduling targets.
- One aspect of the present disclosure is a receiving unit that receives a plurality of downlink data channels scheduled by single downlink control information, and based on the scheduled downlink data channel or the valid downlink data channel, code block and a control unit that determines whether or not there is information about a group.
- One aspect of the present disclosure is a receiving unit that receives a plurality of downlink data channels scheduled by single downlink control information, and an automatic retransmission request for the downlink data channel based on the number of valid downlink data channels. and a controller for determining which codebook to include the feedback of.
- One aspect of the present disclosure is a receiving unit that receives a plurality of downlink data channels scheduled by a single downlink control information, and if any of the downlink data channels collide with an uplink symbol, cancel due to the collision a control unit that assumes reception of the downlink data channel by semi-static scheduling.
- One aspect of the present disclosure is a transmitting unit (data transmitting/receiving unit 260) that transmits a plurality of uplink data channels scheduled by a single downlink control information, and any of the uplink data channels collided with a downlink symbol.
- the terminal (UE 200) includes a control unit (control unit 270) that assumes that the uplink data channel canceled due to the collision is excluded from specific scheduling targets.
- One aspect of the present disclosure is a transmitting unit that transmits a plurality of uplink data channels scheduled by single downlink control information, and based on the scheduled uplink data channel or the valid uplink data channel, a channel state and a control unit that determines reporting of information.
- One aspect of the present disclosure is a transmitting unit that transmits a plurality of uplink data channels scheduled by a single downlink control information, and based on the scheduled uplink data channel or the valid uplink data channel, a code block and a control unit that determines whether or not there is information about a group.
- One aspect of the present disclosure is a transmission unit that transmits a plurality of uplink data channels scheduled by a single downlink control information, and if any of the uplink data channels collide with a downlink symbol, cancel due to the collision a control unit that stops transmission of the uplink data channel according to the set permission that has been set.
- FIG. 1 is an overall schematic configuration diagram of a radio communication system 10.
- FIG. 2 is a diagram showing frequency bands used in the wireless communication system 10.
- FIG. 3 is a diagram showing a configuration example of radio frames, subframes and slots used in the radio communication system 10.
- FIG. 4 is a functional block configuration diagram of gNB100 and UE200.
- FIG. 5 is a diagram showing a configuration example of multi-PDSCH/PUSCH scheduling.
- FIG. 6 is a diagram showing a sequence example regarding scheduling of data channels.
- FIG. 7 is a diagram showing an example of a TDRA table.
- FIG. 8 is a diagram showing an example of the hardware configuration of gNB100 and UE200.
- FIG. 9 is a diagram showing a configuration example of the vehicle 2001. As shown in FIG.
- FIG. 1 is an overall schematic configuration diagram of a radio communication system 10 according to the present embodiment.
- the radio communication system 10 is a radio communication system according to 5G New Radio (NR), and includes a Next Generation-Radio Access Network 20 (hereinafter, NG-RAN 20, and a terminal 200 (hereinafter, UE 200, User Equipment, UE).
- NG-RAN 20 Next Generation-Radio Access Network
- UE 200 User Equipment
- the radio communication system 10 may be a radio communication system according to a scheme called Beyond 5G, 5G Evolution, or 6G.
- NG-RAN 20 includes a radio base station 100 (hereinafter gNB 100).
- gNB 100 radio base station 100
- the specific configuration of the radio communication system 10 including the number of gNBs and UEs is not limited to the example shown in FIG.
- NG-RAN 20 actually includes multiple NG-RAN Nodes, specifically gNBs (or ng-eNBs), and is connected to a 5G-compliant core network (5GC, not shown). Note that NG-RAN 20 and 5GC may simply be referred to as a "network”.
- gNBs or ng-eNBs
- 5GC 5G-compliant core network
- the gNB100 is a 5G-compliant radio base station that performs 5G-compliant radio communication with the UE200.
- the gNB100 and UE200 control the radio signals transmitted from multiple antenna elements to generate antenna beams with higher directivity (hereafter, beam BM), Massive MIMO (Multiple-Input Multiple-Output), multiple It is possible to support carrier aggregation (CA), which uses component carriers (CC) in a bundle, and dual connectivity (DC), which simultaneously communicates between a UE and two NG-RAN Nodes.
- beam BM directivity
- Massive MIMO Multiple-Input Multiple-Output
- CA carrier aggregation
- CC component carriers
- DC dual connectivity
- the gNB 100 can transmit multiple beams BM with different transmission directions (simply called directions, radiation directions, coverage, etc.) in a space- and time-division manner. Note that the gNB 100 may transmit multiple beams BM at the same time.
- the wireless communication system 10 may support multiple frequency ranges (FR).
- FIG. 2 shows frequency bands used in wireless communication system 10 .
- FR1 410MHz to 7.125GHz
- FR2 24.25 GHz to 52.6 GHz
- a Sub-Carrier Spacing (SCS) of 15, 30 or 60 kHz may be used and a bandwidth (BW) of 5-100 MHz may be used.
- FR2 is higher frequency than FR1 and may use a subcarrier spacing (SCS) of 60 or 120 kHz (240 kHz may be included) and a bandwidth (BW) of 50-400 MHz.
- SCS subcarrier Spacing
- BW bandwidth
- SCS may be interpreted as numerology.
- numerology is defined in 3GPP TS38.300 and corresponds to one subcarrier spacing in the frequency domain.
- the wireless communication system 10 also supports higher frequency bands than the FR2 frequency band. Specifically, the wireless communication system 10 supports frequency bands exceeding 52.6 GHz and up to 71 GHz. Such high frequency bands may be conveniently referred to as "FR2x".
- Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM)/Discrete Fourier Transform-Spread (DFT- S-OFDM) may be applied.
- CP-OFDM Cyclic Prefix-Orthogonal Frequency Division Multiplexing
- DFT- S-OFDM Discrete Fourier Transform-Spread
- FIG. 3 shows a configuration example of radio frames, subframes and slots used in the radio communication system 10. As shown in FIG. Table 1 also shows the relationship between SCS and symbol period.
- the symbol period may also be referred to as symbol length, time direction, time domain, or the like.
- the frequency direction may also be referred to as frequency domain, resource block, subcarrier, BWP (Bandwidth part), and the like.
- the number of symbols constituting one slot does not necessarily have to be 14 symbols (for example, 28 or 56 symbols). Also, the number of slots per subframe may vary depending on the SCS.
- an SSB (SS/PBCH Block) composed of a synchronization signal (SS: Synchronization Signal) and a physical downlink channel (PBCH: Physical Broadcast CHannel) may be used.
- SS Synchronization Signal
- PBCH Physical Broadcast CHannel
- the SSB is periodically transmitted from the network mainly for the UE 200 to detect the cell ID and reception timing at the start of communication.
- SSB is also used for reception quality measurement of each cell.
- As the SSB transmission period (periodicity), 5, 10, 20, 40, 80, 160 milliseconds, etc. may be defined. Note that the initial access UE 200 may assume a transmission cycle of 20 milliseconds.
- the network can notify the actually transmitted SSB index indication (ssb-PositionsInBurst) to UE 200 through system information (SIB1) or radio resource control layer (RRC) signaling.
- SIB1 system information
- RRC radio resource control layer
- PSS Primary SS
- SSS Secondary SS
- PSS is a known signal that UE 200 attempts to detect first in the cell search procedure.
- SSS is a known signal that is sent to detect physical cell IDs in cell search procedures.
- the PBCH After detecting the SS/PBCH Block, the PBCH contains the System Frame Number (SFN) and an index to identify the symbol positions of multiple SS/PBCH Blocks within a half-frame (5 ms). It includes information necessary for UE200 to establish frame synchronization with the NR cell formed by gNB100.
- SFN System Frame Number
- the PBCH can also contain system parameters required to receive system information (SIB). Furthermore, the SSB also includes a broadcast channel demodulation reference signal (DMRS for PBCH). DMRS for PBCH is a known signal sent to measure radio channel conditions for PBCH demodulation.
- SIB system information
- DMRS for PBCH is a known signal sent to measure radio channel conditions for PBCH demodulation.
- the UE 200 determines that there is CORESET for Type0-PDCCH CSS based on the received master information block (MIB), the CORESET (CORESET 0) or Remaining Minimum System Information (RMSI) CORESET is called. determine a number of consecutive resource blocks (RBs) and symbols for UE 200 sets PDCCH (Physical Downlink Control Channel), specifically Type 0 PDCCH monitoring opportunity (MO) for system information block (SIB) decoding, based on the determined RBs and symbols.
- PDCCH Physical Downlink Control Channel
- MO Type 0 PDCCH monitoring opportunity
- SIB system information block
- CORESET 0 is a special CORESET that is different from normal CORESET. Such a specific CORESET may be interpreted as a CORESET transmitting PDCCH for SIB1 scheduling. CORESET 0 cannot be specified by RRC as it is used before RRC signaling is sent.
- RMSI may be interpreted to mean System Information Block 1 (SIB1).
- SIB1 may consist of system information that a device (UE 200) needs to know before accessing the system.
- SIB1 may always be broadcast periodically throughout the cell. SIB1 can provide information needed by UE 200 to perform initial random access (RA).
- RA initial random access
- SIB1 is provided by regular scheduled PDSCH (Physical Downlink Shared Channel) transmissions with a periodicity of 160 ms.
- the PBCH/MIB may provide information about the numerology used for SIB1 transmission and the search spaces and corresponding CORESETs used for scheduling SIB1.
- UE 200 may monitor the scheduling of SIB1 indicated by a special System Information RNTI (SI-RNTI).
- SI-RNTI System Information RNTI
- the wireless communication system 10 may support Time Domain Resource Allocation (TDRA).
- TDRA may be interpreted as resource allocation in the time domain of PUSCH (Physical Uplink Shared Channel) defined in 3GPP TS38.214.
- the PUSCH TDRA may be interpreted as defined by a radio resource control layer (RRC) information element (IE), specifically PDSCH-Config or PDSCH-ConfigCommon.
- RRC radio resource control layer
- TDRA may be interpreted as resource allocation in the time domain of PUSCH specified by Downlink Control Information (DCI).
- DCI Downlink Control Information
- one (single) DCI is used to schedule a plurality of data channels, specifically a plurality of PDSCH (Physical Downlink Shared Channel)/PUSCH (Physical Uplink Shared Channel) scheduling (multi- PDSCH/PUSCH scheduling) may be supported.
- PDSCH Physical Downlink Shared Channel
- PUSCH Physical Uplink Shared Channel
- FIG. 4 is a functional block configuration diagram of gNB100 and UE200.
- the UE 200 includes a radio signal transmission/reception unit 210, an amplifier unit 220, a modem unit 230, a control signal/reference signal processing unit 240, an encoding/decoding unit 250, a data transmission/reception unit 260, and a control unit 270. .
- FIG. 4 shows only main functional blocks related to the description of the embodiment, and that the UE 200 (gNB 100) has other functional blocks (for example, power supply section, etc.). Also, FIG. 4 shows the functional block configuration of the UE 200, and please refer to FIG. 8 for the hardware configuration.
- the radio signal transmitting/receiving unit 210 transmits/receives radio signals according to NR.
- the radio signal transmitting/receiving unit 210 controls radio (RF) signals transmitted from multiple antenna elements to generate beams with higher directivity. It can support aggregation (CA), dual connectivity (DC) in which communication is performed simultaneously between the UE and two NG-RAN Nodes, and the like.
- CA aggregation
- DC dual connectivity
- the amplifier section 220 is configured by a PA (Power Amplifier)/LNA (Low Noise Amplifier) and the like. Amplifier section 220 amplifies the signal output from modem section 230 to a predetermined power level. In addition, amplifier section 220 amplifies the RF signal output from radio signal transmission/reception section 210 .
- PA Power Amplifier
- LNA Low Noise Amplifier
- the modulation/demodulation unit 230 executes data modulation/demodulation, transmission power setting, resource block allocation, etc. for each predetermined communication destination (gNB 100, etc.).
- the modem unit 230 may apply Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM)/Discrete Fourier Transform-Spread (DFT-S-OFDM). Also, DFT-S-OFDM may be used not only for uplink (UL) but also for downlink (DL).
- the control signal/reference signal processing unit 240 executes processing related to various control signals transmitted and received by the UE 200 and processing related to various reference signals transmitted and received by the UE 200.
- control signal/reference signal processing unit 240 receives various control signals transmitted from the gNB 100 via a predetermined control channel, for example, radio resource control layer (RRC) control signals. Also, the control signal/reference signal processing unit 240 transmits various control signals to the gNB 100 via a predetermined control channel.
- RRC radio resource control layer
- the control signal/reference signal processing unit 240 executes processing using reference signals (RS) such as Demodulation Reference Signal (DMRS) and Phase Tracking Reference Signal (PTRS).
- RS reference signals
- DMRS Demodulation Reference Signal
- PTRS Phase Tracking Reference Signal
- a DMRS is a known reference signal (pilot signal) between a terminal-specific base station and a terminal for estimating the fading channel used for data demodulation.
- PTRS is a terminal-specific reference signal for estimating phase noise, which is a problem in high frequency bands.
- reference signals may include Channel State Information-Reference Signal (CSI-RS), Sounding Reference Signal (SRS), and Positioning Reference Signal (PRS) for position information.
- CSI-RS Channel State Information-Reference Signal
- SRS Sounding Reference Signal
- PRS Positioning Reference Signal
- control channels include PDCCH (Physical Downlink Control Channel), PUCCH (Physical Uplink Control Channel), RACH (Random Access Channel, Downlink Control Information (DCI) including Random Access Radio Network Temporary Identifier (RA-RNTI)), and Physical Broadcast Channel (PBCH) etc. may be included.
- PDCCH Physical Downlink Control Channel
- PUCCH Physical Uplink Control Channel
- RACH Random Access Channel
- DCI Downlink Control Information
- RA-RNTI Random Access Radio Network Temporary Identifier
- PBCH Physical Broadcast Channel
- data channels include PDSCH (Physical Downlink Shared Channel) and PUSCH (Physical Uplink Shared Channel).
- Data may refer to data transmitted over a data channel.
- control signal/reference signal processing unit 240 may transmit capability information of the UE 200 regarding scheduling of data channels to the network.
- control signal/reference signal processing unit 240 can transmit UE Capability Information regarding PDSCH and PUSCH scheduling to the gNB 100. Details of UE Capability Information will be described later.
- the encoding/decoding unit 250 performs data segmentation/concatenation, channel coding/decoding, etc. for each predetermined communication destination (gNB 100 or other gNB).
- the encoding/decoding unit 250 divides the data output from the data transmission/reception unit 260 into pieces of a predetermined size, and performs channel coding on the divided data. Also, encoding/decoding section 250 decodes the data output from modem section 230 and concatenates the decoded data.
- the data transmission/reception unit 260 executes transmission/reception of Protocol Data Unit (PDU) and Service Data Unit (SDU). Specifically, the data transmitting/receiving unit 260 performs PDU/SDU in multiple layers (medium access control layer (MAC), radio link control layer (RLC), packet data convergence protocol layer (PDCP), etc.). Assemble/disassemble etc. The data transmission/reception unit 260 also performs data error correction and retransmission control based on hybrid ARQ (Hybrid automatic repeat request).
- hybrid ARQ Hybrid automatic repeat request
- the data transmitting/receiving unit 260 can receive multiple downlink data channels (PDSCH) scheduled by one (single) downlink control information (DCI). Also, the data transmitter/receiver 260 can transmit multiple uplink data channels (uplink data channels) scheduled by a single downlink control information (DCI). In this embodiment, the data transmission/reception unit 260 may configure a reception unit for downlink data channels and a transmission unit for transmitting uplink data channels.
- PDSCH downlink data channels
- DCI downlink control information
- uplink data channels uplink data channels scheduled by a single downlink control information (DCI).
- the data transmission/reception unit 260 may configure a reception unit for downlink data channels and a transmission unit for transmitting uplink data channels.
- the control unit 270 controls each functional block that configures the UE200.
- the control unit 270 can execute control regarding multi-PDSCH/PUSCH scheduling.
- Control section 270 may assume that if any PDSCH among multiple PDSCHs by multi-PDSCH scheduling collides with an UL symbol, the PDSCH canceled due to the collision is excluded from specific scheduling targets.
- a UL symbol may be interpreted as a symbol that is semi-statically assigned in a slot.
- collisions with such semi-static UL symbols specifically overlapping resources in the time direction, may be allowed. That is, in multi-PDSCH scheduling, collisions between PDSCH and semi-static UL symbols can occur in Time Division Duplex (TDD).
- TDD Time Division Duplex
- specific scheduling may mean Out-of-order scheduling (OoO scheduling).
- OoO scheduling UE 200 may operate as follows.
- the UE 200 is scheduled to start receiving the PDCCH starting with symbol j and ending with symbol i, and the first PDSCH starting with symbol j.
- UE 200 does not expect to be scheduled to receive a PDSCH that begins before the end of the first PDSCH with a PDCCH that ends after symbol i.
- the UE 200 For any two HARQ process IDs in a given scheduled cell, if the UE 200 is scheduled to start the first PUSCH transmission with a PDCCH starting at symbol j and ending at symbol i, the UE 200: We do not expect a PDCCH that ends later than symbol i to be scheduled to send a PUSCH that starts before the end of the first PUSCH.
- control unit 270 may determine the presence or absence of information on code block groups (CBGs) based on scheduled PDSCHs or valid PDSCHs.
- CBGs code block groups
- the control unit 270 determines DCI based on a scheduled PDSCH or a valid PDSCH.
- the presence or absence of CBGTI (transmission information) and/or CBGFI (flushing out information) fields may be determined.
- a valid PDSCH may be interpreted as a PDSCH that does not collide with a semi-static UL symbol.
- control unit 270 may determine a codebook that includes PDSCH automatic repeat request (HARQ) feedback based on the number of valid PDSCHs.
- HARQ PDSCH automatic repeat request
- the control unit 270 uses a valid PDSCH in type 2 HARQ-ACK (Acknowledgment) feedback.
- HARQ-ACK may be included in either sub-codebook (first sub-codebook or second sub-codebook) based on the number of .
- control unit 270 may include HARQ-ACK in the second sub-codebook regardless of the number of valid or invalid PDSCHs.
- the first sub-codebook may mean a sub-codebook for DCI that schedules only one PDSCH (that is, indicates that the TDRA table contains only one SLIV). Note that types 1 and 2 are based on different codebook decision algorithms, and in type 2, the HARQ-ACK codebook may be dynamically set.
- control unit 270 may assume reception of the PDSCH due to semi-static scheduling canceled due to the collision.
- control unit 270 may assume reception of an SPS (Semi-Persistent Scheduling) PDSCH that overlaps with the PDSCH that was canceled due to collision (that is, uses the same radio resource).
- SPS Semi-Persistent Scheduling
- control unit 270 assumes that if any PUSCH among a plurality of PUSCHs by multi-PUSCH scheduling collides with a DL symbol, the PUSCH canceled due to the collision is excluded from specific scheduling (OoO scheduling). you can
- a DL symbol may be interpreted as a symbol that is semi-statically allocated in a slot.
- Multi-PUSCH scheduling may allow collisions with such semi-static DL symbols, SSB symbols and/or CORESET 0 symbols, specifically overlapping resources in the time direction.
- collision between multi-PUSCH scheduling and semi-static UL symbols can occur in Time Division Duplex (TDD).
- TDD Time Division Duplex
- the control unit 270 may decide to report channel state information (CSI) based on scheduled PUSCHs or valid PUSCHs. Specifically, the control unit 270, in the case of A-CSI (Aperiodic-CSI) reporting triggered by the UL grant DCI set based on the TDRA table including SLIV (Start and Length Indicator Value) of a number, scheduling A CSI report may be reported based on the requested PUSCH or the valid PUSCH.
- A-CSI Aperiodic-CSI
- SLIV Start and Length Indicator Value
- a valid PUSCH may be interpreted as a PUSCH that does not collide with a semi-static UL symbol, SSB and/or a symbol set to CORESET 0.
- control unit 270 may determine the presence or absence of information on code block groups (CBGs) based on scheduled PUSCHs or valid PUSCHs.
- CBGs code block groups
- the control unit 270 sets the CBGTI and/or CBGFI fields of the DCI based on the scheduled PUSCH or valid PUSCH.
- the presence or absence (presence) may be determined.
- the control unit 270 may be able to transmit a Configured Grant (CG) PUSCH that overlaps with the canceled PUSCH. Also, the control unit 270 may enable transmission of a CG PUSCH having the same HARQ process ID as the canceled PUSCH.
- CG Configured Grant
- control unit 270 may stop transmission of PUSCH by CG canceled by the collision.
- control unit 270 may apply the operations described in Chapters 11 and 11.1 (Release 15, 16) of 3GPP TS 38.213 for PUSCH that do not use DCI to CG PUSCH. That is, if the CG PUSCH overlaps with the DL symbol, the CG PUSCH may not be transmitted.
- control unit 270 may not transmit a CG PUSCH that overlaps with the canceled PUSCH and/or a CG PUSCH that has the same HARQ process ID.
- the gNB 100 (data transmitting/receiving unit 260) is a transmitting unit that transmits multiple downlink data channels (PDSCH) scheduled by a single downlink control information (DCI) according to multi-PDSCH/PUSCH scheduling, and multiple A receiver for receiving an uplink data channel (PUSCH) may be provided.
- PDSCH downlink data channels
- DCI downlink control information
- FIG. 5 is a configuration example of multi-PDSCH/PUSCH scheduling. indicates As shown in FIG. 5, in multi-PDSCH/PUSCH scheduling, it is possible to schedule multiple PDSCH/PUSCH using one (single) DCI.
- the slot format includes semi-static symbols (UL or DL symbols, which may also include guard (G) symbols).
- ⁇ (Problem 3): If the number of PUSCHs is used to determine the presence of the CBGTI field, it is not clear whether it should be based on the number of PUSCHs scheduled or the number of valid PUSCHs. Also, if the number of PDSCHs is used to determine the presence of the CBGTI/CBGFI field, it is not clear whether it should be based on the number of PDSCHs scheduled or the number of valid PDSCHs.
- ⁇ (Problem 4) PDSCH cancellation due to collision with quasi-static UL symbols is not considered. For example, if DCI schedules multiple PDSCHs and there is only one valid PDSCH, it is not clear whether HARQ-ACK feedback should be included in the first sub-codebook or the second sub-codebook.
- FIG. 6 shows a sequence example regarding scheduling of data channels.
- the UE 200 may send UE Capability Information to the network, specifically the gNB 100.
- UE Capability Information related to this operation example will be described later.
- the gNB100 can perform settings by RRC based on the capabilities of the UE200. Moreover, gNB100 may transmit DCI to UE200. As described above, in multi-PDSCH/PUSCH scheduling, multiple PDSCH/PUSCH may be scheduled by a single DCI.
- the gNB 100 may transmit multiple PDSCHs to the UE 200 according to DCI scheduling.
- UE200 may transmit HARQ feedback (ACK or NACK) for reception of PDSCH to gNB100.
- HARQ-ACK feedback types 1, 2 may be supported.
- the UE 200 may transmit multiple PUSCHs to the gNB 100 according to multi-PUSCH scheduling.
- Operation example 1 This operation example corresponds to Problem 1 and relates to OoO scheduling.
- a PDSCH by multi-PDSCH scheduling is canceled due to collision with a semi-static UL symbol, one of the following operations is applied to PDSCHs included in multiple PDSCHs scheduled by multi-PDSCH scheduling. may be
- the behavior of the UE 200 it may be permissible for the PDSCH scheduled and canceled by the previous DCI to end after the start of the PDSCH scheduled by the subsequent DCI.
- the UE starts receiving the first PDSCH with a PDCCH starting with symbol j and ending with symbol i. If the first PDSCH does not overlap any semi-static UL symbols, then the UE terminates later than symbol I, if the second PDSCH does not overlap any semi-static UL symbols.
- the UE For any two HARQ process IDs in a given scheduled cell, if the UE is scheduled to start receiving a first PDSCH starting in symbol j by a PDCCH ending in symbol i, where the first PDSCH doesn't overlap with any semi-static UL symbol, the UE is not expected to be scheduled to receive a second PDSCH starting earlier than the end of the first PDSCH with a PDCCH that ends later than symbol I, where the second PDSCH doesn't overlap with any semi-static UL symbol.).
- the start of PDSCH scheduled by later DCI should be later than the end of PDSCH scheduled by earlier DCI.
- any of the following actions may be applied.
- the behavior of the UE 200 it may be permissible for the PUSCH scheduled and canceled by the previous DCI to finish later than the start of the PUSCH scheduled by the later DCI.
- the UE starts receiving the first PUSCH with PDCCH starting with symbol j and ending with symbol i. If the first PUSCH does not overlap any semi-static UL symbol, the SSB symbol and the CORESET 0 symbol, the UE shall send symbol I, the second PUSCH any semi-static UL symbol, Do not expect to be scheduled to receive a second PUSCH that starts earlier than the end of the first PUSCH with a PDCCH that ends later than if neither the SSB symbol nor the CORESET 0 symbol overlaps (For any two HARQ process IDs in a given scheduled cell, if the UE is scheduled to start a first PUSCH transmission starting in symbol j by a PDCCH ending in symbol i, where the first PUSCH doesn't overlap with any with semi-static DL symbol, and/or symbol configured for SSB or CORESET#0, the UE is not expected to be scheduled to transmit
- the start of any PUSCH scheduled by later DCI should be later than the end of any PUSCH scheduled by earlier DCI.
- FIG. 7 shows an example of a TDRA table.
- any of the following actions may be applied.
- UE200 may report A-CSI report in the Mth scheduled PUSCH.
- UE 200 may report A-CSI report in the (M-1)th scheduled PUSCH.
- the PUSCH used for A-CSI report may be canceled due to collisions with semi-static DL symbols, SSB symbols, and/or symbols set to CORESET 0.
- ⁇ (Alt 2) The last scheduled PUSCH is used for A-CSI report.
- UE 200 performs A-CSI in the N-th valid PUSCH. You may report report.
- UE 200 may report A-CSI report in the (N-1)th valid PUSCH.
- a valid PUSCH may be interpreted as a PUSCH that does not collide with semi-static UL symbols, SSB and/or symbols set to CORESET 0.
- the PUSCH used for A-CSI report may be canceled due to a collision with a DL symbol, SSB, or a symbol set to CORESET 0.
- Operation example 3 This operation example corresponds to problem 3 and relates to CBG-based transmission.
- a DLgrant DCI set according to a TDRA table containing multiple SLIVs in at least one row such as the TDRA table of FIG. 7, any of the following actions may be applied.
- ⁇ (Option 1-1): The presence of the CBGTI/CBGFI field is determined based on the scheduled PDSCH.
- the number of PDSCHs scheduled by DCI is one, it may be assumed that the CBGTI/CBGFI fields are present. If the number of PDSCHs scheduled by DCI is greater than 1, it may be assumed that the CBGTI/CBGFI fields are not present.
- ⁇ (Option 1-2): The presence of the CBGTI/CBGFI field is determined based on the valid PDSCH.
- the number of PDSCHs scheduled by DCI is one, it may be assumed that the CBGTI/CBGFI fields are present. If the number of PDSCHs scheduled by DCI is greater than 1, the following may occur.
- any of the following operations may be applied.
- the number of PUSCHs scheduled by DCI is 1, it may be assumed that the CBGTI field is present. If the number of PUSCHs scheduled by DCI is greater than 1, it may be assumed that the CBGTI field is not present.
- Operation example 4 This operation example corresponds to problem 4 and relates to type 2 HARQ-ACK feedback.
- a DL grant DCI configured according to a TDRA table that includes multiple SLIVs in at least one row, such as the TDRA table in FIG. 7, and that schedules multiple PDSCHs, any of the following operations may be applied.
- HARQ-ACK information may be included in the first or second sub-codebook based on the number of PDSCHs available.
- DCI HARQ-ACK information may be included in the first subcodebook. If there are multiple valid PDSCHs among multiple scheduled PDSCHs, the DCI HARQ-ACK information may be included in the second subcodebook.
- the first sub-codebook may mean a sub-codebook for DCI that schedules only one PDSCH (that is, a TDRA row contains only one SLIV). .
- Operation example 5 This operation example corresponds to problem 5 and relates to the handling of SPS/DG PDSCH collisions.
- SPS PDSCH rescheduling
- any of the following operations may be applied to the canceled PDSCH resource.
- DCI can schedule another dynamic PDSCH for the remaining valid symbols of the canceled PDSCH.
- Operation example 6 This operation example corresponds to problem 6, and relates to handling at the time of CG/DG PUSCH collision.
- the timeline specified in 3GPP Release-16 it may be overwritten by CG (re-scheduling of PUSCH).
- any of the following operations may be applied.
- ⁇ (Option 1-1) It may be assumed that a CG PUSCH that overlaps with the canceled PUSCH can be transmitted.
- any of the following actions may be applied to DG/CG HARQ process collisions.
- a CG PUSCH having the same HARQ process ID as the canceled PUSCH may not be transmitted.
- any of the following operations may be applied to the canceled PUSCH resource.
- DCI can schedule another dynamic PUSCH for the remaining valid symbols of the canceled PUSCH.
- UE capabilities At least one of the following may be included as the capability (UE capability) of the UE 200 regarding multi-PDSCH/PUSCH scheduling.
- PDSCH/PUSCH has been described as an example in the above embodiments, similar operations may be applied to multiple data channels scheduled by a single DCI.
- configure, activate, update, indicate, enable, specify, and select may be read interchangeably. good.
- link, associate, correspond, and map may be read interchangeably to allocate, assign, monitor. , map, may also be read interchangeably.
- each functional block may be implemented using one device physically or logically coupled, or directly or indirectly using two or more physically or logically separate devices (e.g. , wired, wireless, etc.) and may be implemented using these multiple devices.
- a functional block may be implemented by combining software in the one device or the plurality of devices.
- Functions include judging, determining, determining, calculating, calculating, processing, deriving, investigating, searching, checking, receiving, transmitting, outputting, accessing, resolving, selecting, choosing, establishing, comparing, assuming, expecting, assuming, Broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, assigning, etc. can't
- a functional block (component) that performs transmission is called a transmitting unit or transmitter.
- the implementation method is not particularly limited.
- FIG. 8 is a diagram showing an example of the hardware configuration of the device. As shown in FIG. 8, the device may be configured as a computing device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, and the like.
- the term "apparatus” can be read as a circuit, device, unit, or the like.
- the hardware configuration of the device may be configured to include one or more of each device shown in the figure, or may be configured without some of the devices.
- Each functional block of the device (see FIG. 4) is realized by any hardware element of the computer device or a combination of the hardware elements.
- each function of the device is implemented by causing the processor 1001 to perform calculations, controlling communication by the communication device 1004, and controlling the It is realized by controlling at least one of data reading and writing in 1002 and storage 1003 .
- a processor 1001 operates an operating system and controls the entire computer.
- the processor 1001 may be configured by a central processing unit (CPU) including interfaces with peripheral devices, a control unit, an arithmetic unit, registers, and the like.
- CPU central processing unit
- the processor 1001 reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 to the memory 1002, and executes various processes according to them.
- programs program codes
- software modules software modules
- data etc.
- the various processes described above may be executed by one processor 1001, or may be executed by two or more processors 1001 simultaneously or sequentially.
- Processor 1001 may be implemented by one or more chips. Note that the program may be transmitted from a network via an electric communication line.
- the memory 1002 is a computer-readable recording medium, and is composed of at least one of Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), Random Access Memory (RAM), etc. may be
- ROM Read Only Memory
- EPROM Erasable Programmable ROM
- EEPROM Electrically Erasable Programmable ROM
- RAM Random Access Memory
- the memory 1002 may also be called a register, cache, main memory (main storage device), or the like.
- the memory 1002 can store programs (program code), software modules, etc. capable of executing a method according to an embodiment of the present disclosure.
- the storage 1003 is a computer-readable recording medium, for example, an optical disc such as a Compact Disc ROM (CD-ROM), a hard disk drive, a flexible disc, a magneto-optical disc (for example, a compact disc, a digital versatile disc, a Blu-ray disk), smart card, flash memory (eg, card, stick, key drive), floppy disk, magnetic strip, and/or the like.
- Storage 1003 may also be referred to as an auxiliary storage device.
- the recording medium described above may be, for example, a database, server, or other suitable medium including at least one of memory 1002 and storage 1003 .
- the communication device 1004 is hardware (transmitting/receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also called a network device, a network controller, a network card, a communication module, or the like.
- the communication device 1004 includes a high-frequency switch, duplexer, filter, frequency synthesizer, etc., for realizing at least one of frequency division duplex (FDD) and time division duplex (TDD).
- FDD frequency division duplex
- TDD time division duplex
- the input device 1005 is an input device (for example, keyboard, mouse, microphone, switch, button, sensor, etc.) that receives input from the outside.
- the output device 1006 is an output device (eg, display, speaker, LED lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated (for example, a touch panel).
- each device such as the processor 1001 and the memory 1002 is connected by a bus 1007 for communicating information.
- the bus 1007 may be configured using a single bus, or may be configured using different buses between devices.
- the device includes hardware such as a microprocessor, digital signal processor (DSP), application specific integrated circuit (ASIC), programmable logic device (PLD), field programmable gate array (FPGA), etc.
- DSP digital signal processor
- ASIC application specific integrated circuit
- PLD programmable logic device
- FPGA field programmable gate array
- notification of information is not limited to the aspects/embodiments described in the present disclosure, and may be performed using other methods.
- the notification of information may include physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI), higher layer signaling (e.g., RRC signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB), other signals, or combinations thereof, and RRC signaling may also be referred to as RRC messages, e.g., RRC Connection Setup ) message, RRC Connection Reconfiguration message, or the like.
- DCI Downlink Control Information
- UCI Uplink Control Information
- RRC signaling e.g., RRC signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB), other signals, or combinations thereof
- RRC signaling may also be referred to as RRC messages, e.g., RRC Connection Setup ) message, R
- LTE Long Term Evolution
- LTE-A LTE-Advanced
- SUPER 3G IMT-Advanced
- 4G 4th generation mobile communication system
- 5G 5th generation mobile communication system
- Future Radio Access FAA
- New Radio NR
- W-CDMA registered trademark
- GSM registered trademark
- CDMA2000 Code Division Multiple Access 2000
- UMB Ultra Mobile Broadband
- IEEE 802.11 Wi-Fi (registered trademark)
- IEEE 802.16 WiMAX®
- IEEE 802.20 Ultra-WideBand (UWB), Bluetooth®, other suitable systems, and/or next-generation systems enhanced therefrom.
- a plurality of systems may be applied in combination (for example, a combination of at least one of LTE and LTE-A and 5G).
- a specific operation that is performed by a base station in the present disclosure may be performed by its upper node in some cases.
- various operations performed for communication with a terminal may be performed by the base station and other network nodes other than the base station (e.g. MME or S-GW, etc., but not limited to).
- MME or S-GW network nodes
- the case where there is one network node other than the base station is exemplified above, it may be a combination of a plurality of other network nodes (for example, MME and S-GW).
- Information, signals can be output from a higher layer (or a lower layer) to a lower layer (or a higher layer). It may be input and output via multiple network nodes.
- Input/output information may be stored in a specific location (for example, memory) or managed using a management table. Input and output information may be overwritten, updated, or appended. The output information may be deleted. The entered information may be transmitted to other devices.
- the determination may be made by a value represented by one bit (0 or 1), by a true/false value (Boolean: true or false), or by numerical comparison (for example, a predetermined value).
- notification of predetermined information is not limited to being performed explicitly, but may be performed implicitly (for example, not notifying the predetermined information). good too.
- Software whether referred to as software, firmware, middleware, microcode, hardware description language or otherwise, includes instructions, instruction sets, code, code segments, program code, programs, subprograms, and software modules. , applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, and the like.
- software, instructions, information, etc. may be transmitted and received via a transmission medium.
- the Software uses wired technology (coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL), etc.) and/or wireless technology (infrared, microwave, etc.) to access websites, Wired and/or wireless technologies are included within the definition of transmission medium when sent from a server or other remote source.
- wired technology coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL), etc.
- wireless technology infrared, microwave, etc.
- data, instructions, commands, information, signals, bits, symbols, chips, etc. may refer to voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any of these. may be represented by a combination of
- the channel and/or symbols may be signaling.
- a signal may also be a message.
- a component carrier may also be called a carrier frequency, a cell, a frequency carrier, or the like.
- system and “network” used in this disclosure are used interchangeably.
- information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values from a predetermined value, or may be expressed using other corresponding information.
- radio resources may be indexed.
- base station BS
- radio base station fixed station
- NodeB NodeB
- eNodeB eNodeB
- gNodeB gNodeB
- a base station may also be referred to by terms such as macrocell, small cell, femtocell, picocell, and the like.
- a base station can accommodate one or more (eg, three) cells (also called sectors). When a base station accommodates multiple cells, the overall coverage area of the base station can be partitioned into multiple smaller areas, each smaller area corresponding to a base station subsystem (e.g., a small indoor base station (Remote Radio)). Head: RRH) can also provide communication services.
- a base station subsystem e.g., a small indoor base station (Remote Radio)
- Head: RRH can also provide communication services.
- cell refers to part or all of the coverage area of at least one of a base station and base station subsystem that provides communication services in this coverage.
- MS Mobile Station
- UE User Equipment
- a mobile station is defined by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless It may also be called a terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable term.
- At least one of the base station and mobile station may be called a transmitting device, a receiving device, a communication device, or the like.
- At least one of the base station and the mobile station may be a device mounted on a mobile object, the mobile object itself, or the like.
- the mobile body may be a vehicle (e.g., car, airplane, etc.), an unmanned mobile body (e.g., drone, self-driving car, etc.), or a robot (manned or unmanned ).
- at least one of the base station and the mobile station includes devices that do not necessarily move during communication operations.
- at least one of the base station and mobile station may be an Internet of Things (IoT) device such as a sensor.
- IoT Internet of Things
- the base station in the present disclosure may be read as a mobile station (user terminal, hereinafter the same).
- communication between a base station and a mobile station is replaced with communication between multiple mobile stations (for example, Device-to-Device (D2D), Vehicle-to-Everything (V2X), etc.)
- the mobile station may have the functions that the base station has.
- words such as "up” and “down” may be replaced with words corresponding to inter-terminal communication (for example, "side”).
- uplink channels, downlink channels, etc. may be read as side channels.
- a radio frame may consist of one or more frames in the time domain. Each frame or frames in the time domain may be referred to as a subframe. A subframe may also consist of one or more slots in the time domain. A subframe may be a fixed time length (eg, 1 ms) independent of numerology.
- a numerology may be a communication parameter that applies to the transmission and/or reception of a signal or channel. Numerology, for example, subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame structure, transmission and reception specific filtering operations performed by the receiver in the frequency domain, specific windowing operations performed by the transceiver in the time domain, and/or the like.
- SCS subcarrier spacing
- TTI transmission time interval
- number of symbols per TTI radio frame structure
- transmission and reception specific filtering operations performed by the receiver in the frequency domain specific windowing operations performed by the transceiver in the time domain, and/or the like.
- a slot may consist of one or more symbols (Orthogonal Frequency Division Multiplexing (OFDM) symbols, Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols, etc.) in the time domain.
- OFDM Orthogonal Frequency Division Multiplexing
- SC-FDMA Single Carrier Frequency Division Multiple Access
- a slot may be a unit of time based on numerology.
- a slot may contain multiple mini-slots. Each minislot may consist of one or more symbols in the time domain. A minislot may also be referred to as a subslot. A minislot may consist of fewer symbols than a slot.
- a PDSCH (or PUSCH) that is transmitted in time units larger than a minislot may be referred to as PDSCH (or PUSCH) mapping type A.
- PDSCH (or PUSCH) transmitted using minislots may be referred to as PDSCH (or PUSCH) mapping type B.
- Radio frames, subframes, slots, minislots and symbols all represent time units when transmitting signals. Radio frames, subframes, slots, minislots and symbols may be referred to by other corresponding designations.
- one subframe may be called a transmission time interval (TTI)
- TTI transmission time interval
- multiple consecutive subframes may be called a TTI
- one slot or one minislot may be called a TTI. That is, at least one of the subframe and TTI may be a subframe (1ms) in existing LTE, may be a period shorter than 1ms (eg, 1-13 symbols), or a period longer than 1ms may be Note that the unit representing the TTI may be called a slot, minislot, or the like instead of a subframe.
- TTI refers to, for example, the minimum scheduling time unit in wireless communication.
- a base station performs scheduling to allocate radio resources (frequency bandwidth, transmission power, etc. that can be used by each user terminal) to each user terminal on a TTI basis.
- radio resources frequency bandwidth, transmission power, etc. that can be used by each user terminal
- the TTI may be a transmission time unit for channel-encoded data packets (transport blocks), code blocks, codewords, etc., or may be a processing unit for scheduling, link adaptation, etc. Note that when a TTI is given, the time interval (for example, the number of symbols) in which transport blocks, code blocks, codewords, etc. are actually mapped may be shorter than the TTI.
- one slot or one minislot is called a TTI
- one or more TTIs may be the minimum scheduling time unit.
- the number of slots (the number of mini-slots) constituting the minimum time unit of the scheduling may be controlled.
- a TTI with a time length of 1 ms may be called a normal TTI (TTI in LTE Rel.8-12), normal TTI, long TTI, normal subframe, normal subframe, long subframe, slot, etc.
- TTI that is shorter than a regular TTI may also be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a minislot, a subslot, a slot, and so on.
- long TTI for example, normal TTI, subframe, etc.
- short TTI for example, shortened TTI, etc.
- a TTI having a TTI length greater than or equal to this value may be read as a replacement.
- a resource block is a resource allocation unit in the time domain and frequency domain, and may include one or more consecutive subcarriers in the frequency domain.
- the number of subcarriers included in an RB may be the same regardless of neurology, and may be 12, for example.
- the number of subcarriers included in an RB may be determined based on neumerology.
- the time domain of an RB may include one or more symbols and may be 1 slot, 1 minislot, 1 subframe, or 1 TTI long.
- One TTI, one subframe, etc. may each consist of one or more resource blocks.
- One or more RBs are physical resource blocks (Physical RB: PRB), sub-carrier groups (SCG), resource element groups (REG), PRB pairs, RB pairs, etc. may be called.
- PRB Physical resource blocks
- SCG sub-carrier groups
- REG resource element groups
- PRB pairs RB pairs, etc.
- a resource block may be composed of one or more resource elements (Resource Element: RE).
- RE resource elements
- 1 RE may be a radio resource region of 1 subcarrier and 1 symbol.
- a Bandwidth Part (which may also be called a Bandwidth Part) represents a subset of contiguous common resource blocks (RBs) for a neumerology in a carrier. good.
- the common RB may be identified by an RB index based on the common reference point of the carrier.
- PRBs may be defined in a BWP and numbered within that BWP.
- BWP may include BWP for UL (UL BWP) and BWP for DL (DL BWP).
- BWP may include BWP for UL (UL BWP) and BWP for DL (DL BWP).
- One or more BWPs may be configured in one carrier for a UE.
- At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal/channel outside the active BWP.
- BWP bitmap
- radio frames, subframes, slots, minislots and symbols described above are only examples.
- the number of subframes included in a radio frame the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of Configurations such as the number of subcarriers and the number of symbols in a TTI, symbol length, cyclic prefix (CP) length, etc.
- CP cyclic prefix
- connection means any direct or indirect connection or coupling between two or more elements, It can include the presence of one or more intermediate elements between two elements being “connected” or “coupled.” Couplings or connections between elements may be physical, logical, or a combination thereof. For example, “connection” may be read as "access”.
- two elements are defined using at least one of one or more wires, cables and printed electrical connections and, as some non-limiting and non-exhaustive examples, in the radio frequency domain. , electromagnetic energy having wavelengths in the microwave and light (both visible and invisible) regions, and the like.
- the reference signal can also be abbreviated as Reference Signal (RS), and may also be called Pilot depending on the applicable standard.
- RS Reference Signal
- any reference to elements using the "first,” “second,” etc. designations used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, references to first and second elements do not imply that only two elements may be employed therein or that the first element must precede the second element in any way.
- determining and “determining” used in this disclosure may encompass a wide variety of actions.
- “Judgement” and “determination” are, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (eg, lookup in a table, database, or other data structure), ascertaining as “judged” or “determined”, and the like.
- "judgment” and “determination” are used for receiving (e.g., receiving information), transmitting (e.g., transmitting information), input, output, access (accessing) (for example, accessing data in memory) may include deeming that a "judgment” or “decision” has been made.
- judgment and “decision” are considered to be “judgment” and “decision” by resolving, selecting, choosing, establishing, comparing, etc. can contain.
- judgment and “decision” may include considering that some action is “judgment” and “decision”.
- judgment (decision) may be read as “assuming”, “expecting”, “considering”, or the like.
- a and B are different may mean “A and B are different from each other.”
- the term may also mean that "A and B are different from C”.
- Terms such as “separate,” “coupled,” etc. may also be interpreted in the same manner as “different.”
- FIG. 9 shows a configuration example of a vehicle 2001.
- a vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, axles 2009, an electronic control unit 2010, It has various sensors 2021 to 2029, an information service unit 2012 and a communication module 2013.
- the driving unit 2002 is composed of, for example, an engine, a motor, or a hybrid of the engine and the motor.
- the steering unit 2003 includes at least a steering wheel (also called steering wheel), and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel operated by the user.
- the electronic control unit 2010 is composed of a microprocessor 2031 , a memory (ROM, RAM) 2032 and a communication port (IO port) 2033 . Signals from various sensors 2021 to 2027 provided in the vehicle are input to the electronic control unit 2010 .
- the electronic control unit 2010 may be called an ECU (Electronic Control Unit).
- the signals from various sensors 2021 to 2028 include the current signal from the current sensor 2021 that senses the current of the motor, the rotation speed signal of the front and rear wheels obtained by the rotation speed sensor 2022, and the front wheel obtained by the air pressure sensor 2023. and rear wheel air pressure signal, vehicle speed signal obtained by vehicle speed sensor 2024, acceleration signal obtained by acceleration sensor 2025, accelerator pedal depression amount signal obtained by accelerator pedal sensor 2029, brake pedal sensor 2026 obtained by There are a brake pedal depression amount signal, a shift lever operation signal acquired by the shift lever sensor 2027, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. acquired by the object detection sensor 2028, and the like.
- the information service unit 2012 includes various devices such as car navigation systems, audio systems, speakers, televisions, and radios for providing various information such as driving information, traffic information, and entertainment information, and one or more devices for controlling these devices. It consists of an ECU and The information service unit 2012 uses information acquired from an external device via the communication module 2013 and the like to provide passengers of the vehicle 1 with various multimedia information and multimedia services.
- Driving support system unit 2030 includes millimeter wave radar, LiDAR (Light Detection and Ranging), camera, positioning locator (e.g. GNSS), map information (e.g. high-definition (HD) map, autonomous vehicle (AV) map, etc. ), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chips, and AI processors to prevent accidents and reduce the driver's driving load. and one or more ECUs that control these devices.
- the driving support system unit 2030 transmits and receives various information via the communication module 2013, and realizes a driving support function or an automatic driving function.
- the communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 1 via communication ports.
- the communication module 2013 communicates with the vehicle 2001 through a communication port 2033 a driving unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, Data is sent and received between axle 2009, microprocessor 2031 and memory (ROM, RAM) 2032 in electronic control unit 2010, and sensors 2021-2028.
- the communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with an external device. For example, it transmits and receives various information to and from an external device via wireless communication.
- Communication module 2013 may be internal or external to electronic control 2010 .
- the external device may be, for example, a base station, a mobile station, or the like.
- the communication module 2013 transmits the current signal from the current sensor input to the electronic control unit 2010 to the external device via wireless communication.
- the communication module 2013 receives, from the electronic control unit 2010, the rotation speed signals of the front and rear wheels obtained by the rotation speed sensor 2022, the air pressure signals of the front and rear wheels obtained by the air pressure sensor 2023, and the vehicle speed sensor. 2024, the acceleration signal obtained by the acceleration sensor 2025, the accelerator pedal depression amount signal obtained by the accelerator pedal sensor 2029, the brake pedal depression amount signal obtained by the brake pedal sensor 2026, and the shift lever.
- a shift lever operation signal obtained by the sensor 2027 and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by the object detection sensor 2028 are also transmitted to an external device via wireless communication.
- the communication module 2013 receives various information (traffic information, signal information, inter-vehicle information, etc.) transmitted from external devices and displays it on the information service unit 2012 provided in the vehicle. Communication module 2013 also stores various information received from external devices in memory 2032 available to microprocessor 2031 . Based on the information stored in the memory 2032, the microprocessor 2031 controls the driving unit 2002, the steering unit 2003, the accelerator pedal 2004, the brake pedal 2005, the shift lever 2006, the left and right front wheels 2007, and the left and right rear wheels provided in the vehicle 2001. 2008, axle 2009, sensors 2021-2028, etc. may be controlled.
- various information traffic information, signal information, inter-vehicle information, etc.
- Radio communication system 20 NG-RAN 100 gNB 200UE 210 radio signal transmitter/receiver 220 amplifier 230 modem 240 control signal/reference signal processor 250 encoder/decoder 260 data transmitter/receiver 270 controller 1001 processor 1002 memory 1003 storage 1004 communication device 1005 input device 1006 output device 1007 bus 2001 Vehicle 2002 Drive unit 2003 Steering unit 2004 Accelerator pedal 2005 Brake pedal 2006 Shift lever 2007 Left and right front wheels 2008 Left and right rear wheels 2009 Axle 2010 Electronic control unit 2012 Information service unit 2013 Communication module 2021 Current sensor 2022 Revolution sensor 2023 Air pressure sensor 20 24 vehicle speed Sensor 2025 Acceleration sensor 2026 Brake pedal sensor 2027 Shift lever sensor 2028 Object detection sensor 2029 Accelerator pedal sensor 2030 Driving support system 2031 Microprocessor 2032 Memory (ROM, RAM) 2033 communication port
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
図1は、本実施形態に係る無線通信システム10の全体概略構成図である。無線通信システム10は、5G New Radio(NR)に従った無線通信システムであり、Next Generation-Radio Access Network 20(以下、NG-RAN20、及び端末200(以下、UE200, User Equipment, UE)を含む。なお、無線通信システム10は、Beyond 5G、5G Evolution或いは6Gと呼ばれる方式に従った無線通信システムでもよい。
・FR2:24.25 GHz~52.6 GHz
FR1では、15, 30または60kHzのSub-Carrier Spacing(SCS)が用いられ、5~100MHzの帯域幅(BW)が用いられてもよい。FR2は、FR1よりも高周波数であり、60または120kHz(240kHzが含まれてもよい)のサブキャリア間隔(SCS)が用いられ、50~400MHzの帯域幅(BW)が用いられてもよい。
次に、無線通信システム10の機能ブロック構成について説明する。具体的には、UE200の機能ブロック構成について説明する。図4は、gNB100及びUE200の機能ブロック構成図である。
次に、無線通信システム10の動作について説明する。具体的には、multi-PDSCH/PUSCH schedulingに関する動作、特に、TDDにおいて、PDSCH/PUSCHが、半静的なUL/DLシンボルなどと衝突(重複した無線リソースの割り当て)した場合における動作について説明する。
3GPP Release-17では、multi-PDSCH/PUSCH schedulingがサポートされてよく、以下の衝突が許容されてよい。
・multi-PUSCH schedulingでは、準静的DLシンボル、SSBシンボル、CORESET 0シンボルとの衝突
図5は、multi-PDSCH/PUSCH schedulingの構成例を示す。図5に示すように、multi-PDSCH/PUSCH schedulingでは、1つ(単一)のDCIによって、複数のPDSCH/PUSCHをスケジューリングすることが可能である。一方、スロットのフォーマットには、半静的なシンボル(ULまたはDLシンボル、他にガード(G)シンボルが含まれてもよい)が含まれる。
次に、上述した課題1~6に対応する動作例1~6について説明する。まず、データチャネル(PDSCH/PUSCH)のスケジューリングに関するシーケンス例について説明する。
本動作例は、課題1と対応し、OoO schedulingに関する。multi-PDSCH schedulingによるPDSCHが準静的なULシンボルとの衝突のためにキャンセルされる場合、multi-PDSCH schedulingによってスケジューリングされた複数のPDSCHに含まれるPDSCHについては、次の何れかの動作が適用されてよい。
本動作例は、課題2と対応し、A-CSI reportingに関する。図7は、TDRAテーブルの例を示す。
本動作例は、課題3と対応し、CBGベースの送信に関する。図7のTDRAテーブルのように、少なくとも1つの行に複数のSLIVを含むTDRAテーブルに従って設定されたDLgrant DCIに関しては、次の何れかの動作が適用されてよい。
本動作例は、課題4と対応し、type 2 HARQ-ACKフィードバックに関する。図7のTDRAテーブルのように、少なくとも1つの行に複数のSLIVを含むTDRAテーブルに従って設定され、複数のPDSCHをスケジュールするDL grant DCIについては、次の何れかの動作が適用されてよい。
本動作例は、課題5と対応し、SPS/DG PDSCHの衝突時の取扱いに関する。単一のDCIによってスケジュールされた複数のPDSCHに含まれるPDSCHであって、当該PDSCHが半静的なULシンボルとの衝突のためにキャンセルされる。この場合、3GPP Release-16において規定されているタイムラインを満たせば、SPSによって上書きされてよい(PDSCHの再スケジューリング)。具体的には、次の何れかの動作が適用されてよい。
本動作例は、課題6と対応し、CG/DG PUSCHの衝突時の取扱いに関する。単一のDCIによってスケジュールされた複数のPUSCHに含まれるPUSCHであって、当該PUSCHが、半静的なDLシンボル、SSBシンボル及び/またはCORESET 0に設定されたシンボルとの衝突のためにPUSCHがキャンセルされる。この場合、3GPP Release-16において規定されているタイムラインを満たせば、CGによって上書きされてよい(PUSCHの再スケジューリング)。具体的には、次の何れかの動作が適用されてよい。
上述した動作例に関して、次のような変更例がさらに適用されてよい。具体的には、何れの動作例(オプション)を適用するかについては、次の何れかに基づいて決定されてよい。
・UE200からのUE capabilityの報告
・3GPPの仕様
・上位レイヤパラメータの設定と、報告されたUE capabilityとの組み合わせ
また、動作例は、次のような条件に限定されてもよい。
・アンライセンス周波数帯
・特定のSCS
・上記の任意の組み合わせ
multi-PDSCH/PUSCH schedulingに関するUE200の能力(UE capability)としては、少なくとも次の何れかが含まれてよい。
・キャンセルされたPUSCHを考慮したOoO schedulingのサポート可否
・キャンセルされたPUSCHを考慮したA-CSI reportのサポート可否
・キャンセルされたPDSCHを考慮したCBGベースのスケジューリングのサポート可否
・キャンセルされたPUSCHを考慮したCBGベースのスケジューリングのサポート可否
・キャンセルされたPDSCHを考慮したtype 2 HARQ-ACK CB生成のサポート可否
・キャンセルされたPDSCHを考慮したSPS PDSCHの上書きのサポート可否
・キャンセルされたPDSCHのリソースを別のdynamic grant PDSCHに割り当てることのサポート可否
・キャンセルされたPUSCHを考慮したCG PDSCHの上書きのサポート可否
・キャンセルされたPUSCHのリソースを別dynamic grant PUSCHに割り当てることのサポート可否
上述した実施形態によれば、以下の作用効果が得られる。具体的には、上述したgNB100及びUE200によれば、multi-PDSCH/PUSCH schedulingが適用され、PDSCH/PUSCHと、UL/DLシンボルとの衝突が許容される場合でも、動作例1~6に従った動作を実行できるため、PDSCH/PUSCHの受信を正常に継続できる。
以上、実施形態について説明したが、当該実施形態の記載に限定されるものではなく、種々の変形及び改良が可能であることは、当業者には自明である。
無線フレームは時間領域において1つまたは複数のフレームによって構成されてもよい。時間領域において1つまたは複数の各フレームはサブフレームと呼ばれてもよい。サブフレームはさらに時間領域において1つまたは複数のスロットによって構成されてもよい。サブフレームは、ニューメロロジー(numerology)に依存しない固定の時間長(例えば、1ms)であってもよい。
操舵部2003は、少なくともステアリングホイール(ハンドルとも呼ぶ)を含み、ユーザによって操作されるステアリングホイールの操作に基づいて前輪及び後輪の少なくとも一方を操舵するように構成される。
電子制御部2010は、マイクロプロセッサ2031、メモリ(ROM、RAM)2032、通信ポート(IOポート)2033で構成される。電子制御部2010には、車両に備えられた各種センサ2021~2027からの信号が入力される。電子制御部2010は、ECU(Electronic Control Unit)と呼んでもよい。
20 NG-RAN
100 gNB
200 UE
210 無線信号送受信部
220 アンプ部
230 変復調部
240 制御信号・参照信号処理部
250 符号化/復号部
260 データ送受信部
270 制御部
1001 プロセッサ
1002 メモリ
1003 ストレージ
1004 通信装置
1005 入力装置
1006 出力装置
1007 バス
2001 車両
2002 駆動部
2003 操舵部
2004 アクセルペダル
2005 ブレーキペダル
2006 シフトレバー
2007 左右の前輪
2008 左右の後輪
2009 車軸
2010 電子制御部
2012 情報サービス部
2013 通信モジュール
2021 電流センサ
2022 回転数センサ
2023 空気圧センサ
2024 車速センサ
2025 加速度センサ
2026 ブレーキペダルセンサ
2027 シフトレバーセンサ
2028 物体検出センサ
2029 アクセルペダルセンサ
2030 運転支援システム部
2031 マイクロプロセッサ
2032 メモリ(ROM, RAM)
2033 通信ポート
Claims (6)
- 単一の下りリンク制御情報によってスケジューリングされる複数の下りデータチャネルを受信する受信部と、
何れかの前記下りデータチャネルが上りリンクシンボルと衝突した場合、前記衝突によってキャンセルされた前記下りデータチャネルが、特定スケジューリングの対象から除かれると想定する制御部と
を備える端末。 - 単一の下りリンク制御情報によってスケジューリングされる複数の下りデータチャネルを受信する受信部と、
スケジューリングされた前記下りデータチャネルまたは有効な前記下りデータチャネルに基づいて、コードブロックグループに関する情報の有無を決定する制御部と
を備える端末。 - 単一の下りリンク制御情報によってスケジューリングされる複数の下りデータチャネルを受信する受信部と、
有効な前記下りデータチャネルの数に基づいて、前記下りデータチャネルの自動再送要求のフィードバックを含めるコードブックを決定する制御部と
を備える端末。 - 単一の下りリンク制御情報によってスケジューリングされる複数の下りデータチャネルを受信する受信部と、
何れかの前記下りデータチャネルが上りリンクシンボルと衝突した場合、前記衝突によってキャンセルされた半静的なスケジューリングによる前記下りデータチャネルの受信を想定する制御部と
を備える端末。 - 無線基地局と端末とを含む無線通信システムであって、
前記無線基地局は、単一の下りリンク制御情報によってスケジューリングされる複数の下りデータチャネルを送信する送信部を備え、
前記端末は、
前記下りデータチャネルを受信する受信部と、
何れかの前記下りデータチャネルが上りリンクシンボルと衝突した場合、前記衝突によってキャンセルされた前記下りデータチャネルが、特定スケジューリングの対象から除かれると想定する制御部と
を備える無線通信システム。 - 無線基地局が、単一の下りリンク制御情報によってスケジューリングされる複数の下りデータチャネルを送信するステップと、
端末が、前記下りデータチャネルを受信するステップと、
前記端末が、何れかの前記下りデータチャネルが上りリンクシンボルと衝突した場合、前記衝突によってキャンセルされた前記下りデータチャネルが、特定スケジューリングの対象から除かれると想定するステップと
を含む無線通信方法。
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/JP2021/040892 WO2023079713A1 (ja) | 2021-11-05 | 2021-11-05 | 端末、無線通信システム及び無線通信方法 |
JP2023557566A JPWO2023079713A1 (ja) | 2021-11-05 | 2021-11-05 | |
CN202180102606.4A CN117981438A (zh) | 2021-11-05 | 2021-11-05 | 终端、无线通信系统以及无线通信方法 |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/JP2021/040892 WO2023079713A1 (ja) | 2021-11-05 | 2021-11-05 | 端末、無線通信システム及び無線通信方法 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2023079713A1 true WO2023079713A1 (ja) | 2023-05-11 |
Family
ID=86240883
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2021/040892 WO2023079713A1 (ja) | 2021-11-05 | 2021-11-05 | 端末、無線通信システム及び無線通信方法 |
Country Status (3)
Country | Link |
---|---|
JP (1) | JPWO2023079713A1 (ja) |
CN (1) | CN117981438A (ja) |
WO (1) | WO2023079713A1 (ja) |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20200296701A1 (en) * | 2019-03-15 | 2020-09-17 | Samsung Electronics Co., Ltd. | Method and device for priority-based control and data information transmission in wireless communication system |
-
2021
- 2021-11-05 WO PCT/JP2021/040892 patent/WO2023079713A1/ja active Application Filing
- 2021-11-05 JP JP2023557566A patent/JPWO2023079713A1/ja active Pending
- 2021-11-05 CN CN202180102606.4A patent/CN117981438A/zh active Pending
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20200296701A1 (en) * | 2019-03-15 | 2020-09-17 | Samsung Electronics Co., Ltd. | Method and device for priority-based control and data information transmission in wireless communication system |
Non-Patent Citations (2)
Title |
---|
3GPP: "Final Report of 3GPP TSG RAN WG1 #104bis-e v 1.0.0", R1-2104151, 3GPP TSG RAN WG1 MEETING #105-E, April 2021 (2021-04-01) |
MEDIATEK INC.: "Multi-PDSCH scheduling design for 52.6-71 GHz NR operation", 3GPP TSG RAN WG1 #106B-E R1-2109562, 2 October 2021 (2021-10-02), XP052058507 * |
Also Published As
Publication number | Publication date |
---|---|
CN117981438A (zh) | 2024-05-03 |
JPWO2023079713A1 (ja) | 2023-05-11 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2023162085A1 (ja) | 通信装置及び無線通信方法 | |
WO2023079713A1 (ja) | 端末、無線通信システム及び無線通信方法 | |
WO2023079715A1 (ja) | 端末、無線通信システム及び無線通信方法 | |
WO2024171440A1 (ja) | 端末及び無線基地局 | |
WO2023163030A1 (ja) | 端末及び無線通信方法 | |
WO2024166215A1 (ja) | 端末、無線基地局及び無線通信方法 | |
WO2023063397A1 (ja) | 端末、無線通信システム及び無線通信方法 | |
WO2023135637A1 (ja) | 端末、基地局、無線通信システム及び無線通信方法 | |
WO2024166221A1 (ja) | 端末及び無線通信方法 | |
WO2024166368A1 (ja) | 端末、基地局、無線通信システム及び無線通信方法 | |
WO2024100901A1 (ja) | 基地局 | |
WO2024100735A1 (ja) | 端末、基地局、無線通信システム及び無線通信方法 | |
WO2023067750A1 (ja) | 端末、基地局、無線通信システム及び無線通信方法 | |
WO2023195128A1 (ja) | 端末、基地局、無線通信システム及び無線通信方法 | |
WO2023079596A1 (ja) | 端末及び無線通信方法 | |
WO2023210009A1 (ja) | 端末、基地局、無線通信システム及び無線通信方法 | |
WO2023135645A1 (ja) | 端末、基地局、無線通信システム及び無線通信方法 | |
WO2023135646A1 (ja) | 端末、基地局、無線通信システム及び無線通信方法 | |
WO2023152836A1 (ja) | 端末及び無線通信方法 | |
WO2024034122A1 (ja) | 端末、基地局、無線通信システム及び無線通信方法 | |
WO2023053271A1 (ja) | 端末及び無線通信方法 | |
WO2023067778A1 (ja) | 端末、基地局、無線通信システム及び無線通信方法 | |
WO2023079619A1 (ja) | 端末及び無線通信方法 | |
WO2024024100A1 (ja) | 端末、基地局、無線通信システム及び無線通信方法 | |
WO2024029078A1 (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: 21963307 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 202180102606.4 Country of ref document: CN |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2023557566 Country of ref document: JP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2021963307 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref document number: 2021963307 Country of ref document: EP Effective date: 20240605 |