WO2022195885A1 - 端末、無線通信システム及び無線通信方法 - Google Patents
端末、無線通信システム及び無線通信方法 Download PDFInfo
- Publication number
- WO2022195885A1 WO2022195885A1 PCT/JP2021/011517 JP2021011517W WO2022195885A1 WO 2022195885 A1 WO2022195885 A1 WO 2022195885A1 JP 2021011517 W JP2021011517 W JP 2021011517W WO 2022195885 A1 WO2022195885 A1 WO 2022195885A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- pdsch
- qcl
- mbs
- common
- downlink data
- Prior art date
Links
- 238000004891 communication Methods 0.000 title claims description 60
- 238000000034 method Methods 0.000 title description 30
- 230000005540 biological transmission Effects 0.000 claims description 39
- 238000012545 processing Methods 0.000 description 19
- 238000010586 diagram Methods 0.000 description 18
- 238000012544 monitoring process Methods 0.000 description 15
- 230000006870 function Effects 0.000 description 10
- 230000011664 signaling Effects 0.000 description 8
- 101000741965 Homo sapiens Inactive tyrosine-protein kinase PRAG1 Proteins 0.000 description 7
- 102100038659 Inactive tyrosine-protein kinase PRAG1 Human genes 0.000 description 7
- 230000004048 modification Effects 0.000 description 5
- 238000012986 modification Methods 0.000 description 5
- 230000004913 activation Effects 0.000 description 4
- 125000004122 cyclic group Chemical group 0.000 description 4
- 230000009849 deactivation Effects 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 238000013507 mapping Methods 0.000 description 3
- 238000010295 mobile communication Methods 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 230000008054 signal transmission Effects 0.000 description 3
- 230000008878 coupling Effects 0.000 description 2
- 238000010168 coupling process Methods 0.000 description 2
- 238000005859 coupling reaction Methods 0.000 description 2
- 230000001934 delay Effects 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 230000007774 longterm Effects 0.000 description 2
- 238000005259 measurement Methods 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 238000012384 transportation and delivery Methods 0.000 description 2
- 101150071746 Pbsn gene Proteins 0.000 description 1
- LELQZCNRZHLYFG-ZDVGBALWSA-N [(4e,7e)-trideca-4,7-dienyl] acetate Chemical compound CCCCC\C=C\C\C=C\CCCOC(C)=O LELQZCNRZHLYFG-ZDVGBALWSA-N 0.000 description 1
- 230000006978 adaptation Effects 0.000 description 1
- 230000002776 aggregation Effects 0.000 description 1
- 238000004220 aggregation Methods 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 239000000872 buffer Substances 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 239000000969 carrier Substances 0.000 description 1
- 239000003795 chemical substances by application Substances 0.000 description 1
- 238000012937 correction Methods 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 230000009977 dual effect Effects 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
- 230000006872 improvement Effects 0.000 description 1
- 239000006249 magnetic particle Substances 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000000737 periodic effect Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 238000013468 resource allocation Methods 0.000 description 1
- 230000004044 response 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
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
-
- 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 terminals, wireless communication systems, and wireless communication methods that support multicast/broadcast services.
- 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
- Non-Patent Document 1 simultaneous data transmission (also called distribution) services (MBS: Multicast and Broadcast Services) (tentative name) to multiple specified or unspecified terminals (User Equipment, UE) in NR. is targeted (Non-Patent Document 1).
- MMS Multicast and Broadcast Services
- the time from reception of downlink control information (DCI) to downlink data channel (PDSCH: Physical Downlink Shared Channel) is defined for Quasi-Colocation (QCL). If it is shorter than the specified time (timeDurationForQCL), it is specified to receive the PDSCH using the QCL of the latest monitoring slot minimum control resource set (CORESET: control resource sets) ID (Non-Patent Document 2 ).
- the QCL of the minimum CORESET ID for the latest monitoring slot differs for each UE, and may be a unicast CORESET. Therefore, even if the operation described above is applied to MBS as it is, it is not possible to determine an appropriate QCL for multicast PDSCH (which may be called group-common PDSCH).
- the following disclosure has been made in view of this situation, and provides a terminal, a wireless communication system, and a wireless communication system that can assume appropriate pseudo collocations in simultaneous data transmission services to a plurality of specified or unspecified terminals.
- the purpose is to provide a communication method.
- a receiving unit radio signal transmitting/receiving unit 210) that receives a downlink data channel common to a terminal group, and a pseudo collocation of the downlink data channel are
- a terminal UE 200
- control unit control unit 270
- One aspect of the present disclosure is a radio communication system including a radio base station and a terminal, wherein the radio base station transmits a downlink data channel common to a terminal group in data distribution for a plurality of terminals. and the terminal assumes that a receiver for receiving the downlink data channel and the pseudo-colocation of the downlink data channel are in a specific state common to the plurality of terminals when a specific condition is satisfied. and a control unit.
- FIG. 1 is an overall schematic configuration diagram of a radio communication system 10.
- FIG. 2 is a diagram showing a configuration example of radio frames, subframes and slots used in the radio communication system 10.
- FIG. 3 is a diagram showing a setting example of the TCI state field of DCI format 1_1/1_2.
- FIG. 4 is a diagram showing an example (part 1) of the relationship between DCI format 1_0, timeDurationForQCL, and PDSCH.
- FIG. 5 is a diagram showing a configuration example of PTM transmission method 1 and PTM transmission method 2.
- FIG. FIG. 6 is a functional block configuration diagram of gNB100 and UE200.
- FIG. 7 is a diagram showing a sequence example of PDCCH, PDSCH and HARQ feedback in MBS.
- FIG. 8 is a diagram showing an example (part 2) of the relationship between DCI format 1_0, timeDurationForQCL, and PDSCH.
- FIG. 9 is a diagram showing a relationship example of group-common PDCCH, timeDurationForQCL and group-common PDSCH.
- FIG. 10 is a diagram showing an example of relationships among CFR, group-common PDCCH, group-common PDSCH, and unicast PDCCH/PDSCH.
- FIG. 11 is a diagram illustrating an example of minimum DCI codepoints according to operation example 2; FIG.
- FIG. 12 is a diagram showing an example of relationships among CFR, group-common PDCCH, group-common PDSCH, and unicast PDCCH/PDSCH according to the modification.
- FIG. 13 is a diagram showing an example of the hardware configuration of gNB100 and UE200.
- FIG. 1 is an overall schematic configuration diagram of a radio communication system 10 according to the present embodiment.
- the wireless communication system 10 is (1) Overall Schematic Configuration of Radio Communication System (1.1) System Configuration Example
- 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 plurality of terminals 200 (User Equipment 200, hereinafter, UE 200). include.
- NR Next Generation-Radio Access Network 20
- UE 200 User Equipment 200
- the wireless communication system 10 may be a wireless communication system according to a system 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 an NR-compliant radio base station and performs NR-compliant radio communication with the UE200.
- the gNB100 and UE200 use Massive MIMO, which generates beams with higher directivity by controlling radio signals transmitted from multiple antenna elements, and Carrier Aggregation (CA), which bundles multiple component carriers (CC). , and dual connectivity (DC) in which communication is performed simultaneously between the UE and each of a plurality of NG-RAN Nodes.
- Massive MIMO which generates beams with higher directivity by controlling radio signals transmitted from multiple antenna elements
- CA Carrier Aggregation
- CC component carriers
- DC dual connectivity
- the wireless communication system 10 supports FR1 and FR2.
- the frequency bands of each FR are as follows.
- FR1 410MHz to 7.125GHz
- FR2 24.25 GHz to 52.6 GHz
- SCS Sub-Carrier Spacing
- BW bandwidth
- FR2 is a higher frequency than FR1 and may use an SCS of 60 or 120 kHz (240 kHz may be included) and a bandwidth (BW) of 50-400 MHz.
- the wireless communication system 10 may also support a higher frequency band than the FR2 frequency band. Specifically, the wireless communication system 10 may support frequency bands above 52.6 GHz and up to 114.25 GHz. Also, the radio communication system 10 may support a frequency band between FR1 and FR2.
- Cyclic Prefix-Orthogonal Frequency Division Multiplexing CP-OFDM
- DFT-S-OFDM Discrete Fourier Transform-Spread
- SCS Sub-Carrier Spacing
- DFT-S-OFDM may be applied not only to the uplink (UL) but also to the downlink (DL).
- FIG. 2 shows a configuration example of radio frames, subframes and slots used in the radio communication system 10.
- one slot consists of 14 symbols, and the larger (wider) the SCS, the shorter the symbol period (and slot period). Note that the number of symbols forming 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. Additionally, the SCS may be wider than 240kHz (eg, 480kHz, 960kHz, as shown in Figure 2).
- time direction (t) shown in FIG. 2 may be called the time domain, symbol period, symbol time, or the like.
- the frequency direction may also be referred to as frequency domain, resource block, resource block group, subcarrier, BWP (Bandwidth part), subchannel, common frequency resource, and the like.
- QCL/TCI states Quasi-Colocation (QCL) is defined as, for example, two antennas if the characteristics of the channel in which the symbols on one antenna port are carried can be inferred from the channel in which the symbols on the other antenna port are carried. It is assumed that the ports are in the same pseudo location.
- QCL should not be assumed between SSBs (Synchronization Signal/Physical Broadcast Channel blocks) with the same SSB index, and between other SSBs (that is, different SSB indexes). Note that QCL may be called quasi-collocation.
- TCI Transmission Configuration Indication
- TCI state may mean that it is explicitly set by the control element (MAC CE) of the radio resource control layer (RRC) or medium access control layer (MAC).
- QCL relationships may include both cases where the TCI state is explicitly set and cases where the TCI state is not set.
- QCL/TCI state/Bohm may be read interchangeably.
- PDCCH Physical Downlink Control Channel
- SSB Physical Downlink Control Channel
- channel estimation information for detecting SSB is also useful for detecting PDCCH.
- the channel state may be defined by the following parameters.
- the QCL type may be defined using such parameters. Specifically, the QCL type is defined as follows in section 5.1.5 of 3GPP TS38.214.
- ⁇ QCL-Type A ⁇ Doppler shift, Doppler spread, average delay
- delay spread ⁇ ⁇ QCL-Type B ⁇ Doppler shift
- Doppler spread ⁇ ⁇ QCL-Type C ⁇ Doppler shift
- average delay ⁇ ⁇ QCL-Type D ⁇ Spatial Rx parameter ⁇ Type A is always set as the TCI state of DMRS of PDCCH/PDSCH, and in addition, Type D may be set (especially in the case of FR2).
- Type A RS (CSI (Channel State Information)-RS) is used for long-term channel information measurement, and may be used for DMRS channel estimation, for example. Even if DMRS is measured, only instantaneous measured values can be obtained, so Doppler information cannot be obtained.
- UE200 acquires QCL-Type A (Doppler shift, Doppler spread, average delay, delay spread) information by measuring periodic RS set as QCL Type A RS (for example, TRS (Tracking Reference Signal)). and receive PDSCH/PDCCH using this information.
- QCL-Type A Doppler shift, Doppler spread, average delay, delay spread
- Type D RS is used for notifying the base station side transmission spatial domain filter (in short, analog beam).
- UE 200 selects an appropriate UE-side reception spatial domain filter by measuring an RS (for example, TRS) set in advance as Type D RS, and when receiving PDCCH/PDSCH, selects the reception spatial domain filter to receive PDCCH/PDSCH.
- RS for example, TRS
- the PDCCH TCI state may be notified by RRC and/or MAC CE.
- a maximum of 8 PDSCH TCI states may be notified by RRC/MAC CE and indicated by a maximum of 3-bit TCI state field of DCI format 1_1/1_2 (present when tciPresentInDCI of RRC is set).
- the TCI state of PDSCH may be determined by a predetermined method.
- DCI format 1_1/1_2 and tciPresentInDCI is not set, there is no TCI state field, so the TCI state of PDSCH may be determined by a predetermined method.
- Fig. 3 shows a setting example of the TCI state field of DCI format 1_1/1_2.
- a 3-bit TCI state field may be allocated as shown in FIG.
- the value of the TCI state field may be associated with the TCI state for a given PDSCH.
- the TCI state of PDSCH may be determined by a predetermined method.
- a predetermined method may be called Default TCI state.
- DCI format 1_0 is particularly expected in multicast PDSCH (MBS PDSCH) scheduling.
- Fig. 4 shows an example (1) of the relationship between DCI format 1_0, timeDurationForQCL and PDSCH.
- PDSCH may be scheduled according to DCI format 1_0.
- the time from DCI to PDSCH is set longer than timeDurationForQCL.
- the PDSCH When the PDSCH is scheduled according to DCI format 1_0, it does not have the TCI state field as described above. In this case, the time from DCI to PDSCH may be set longer than timeDurationForQCL.
- the QCL of the PDCCH (DCI) that schedules the PDSCH may be assumed to be the QCL of the PDSCH.
- the wireless communication system 10 may provide Multicast and Broadcast Services (MBS).
- MBS Multicast and Broadcast Services
- unicast may be interpreted as one-to-one communication with a network by specifying one specific UE 200 (identification information unique to the UE 200 may be specified).
- Multicast may be interpreted as communication performed one-to-many (specified many) with the network by designating a plurality of specific UEs 200 (identification information for multicast may be designated). Note that the number of UEs 200 that receive received multicast data may eventually be one.
- Broadcast may be interpreted as one-to-unspecified communication with the network for all UE 200.
- the data to be multicast/broadcast may have the same copied content, but may have different content such as a header.
- multicast/broadcast data may be sent (delivered) at the same time, but does not necessarily require strict concurrency and may include propagation delays and/or processing delays within the RAN nodes, and the like.
- the radio resource control layer (RRC) state of the target UE 200 is either an idle state (RRC idle), a connected state (RRC connected), or another state (eg, inactive state). good too.
- the inactive state may be interpreted as a state in which some RRC settings are maintained.
- MBS multicast/broadcast PDSCH scheduling
- MBS packet which can be read as data
- RRC connected UE may be read as RRC idle UE and RRC inactive UE.
- PTM-1 Schedule a group-common PDSCH using a group-common PDCCH for the MBS group of the RRC connected UE.
- group-common RNTI Radio Network Temporary Identifier
- ⁇ PTM transmission method 2 (PTM-2): - A group-common PDSCH is scheduled using terminal specific (UE-specific) PDCCH with respect to the MBS group of RRC connected UE.
- ⁇ PDSCH is scrambled by group-common RNTI.
- ⁇ PTP transmission method - Schedule a UE-specific PDSCH using a UE-specific PDCCH for an RRC connected UE.
- - PDCCH CRC and PDSCH are scrambled by UE-specific RNTI. In other words, it may mean that MBS packets are transmitted by unicast.
- FIG. 5 shows a configuration example of PTM transmission method 1 and PTM transmission method 2.
- the UE-specific PDCCH/PDSCH can be identified by the target UE, but may not be identified by other UEs within the same MBS group.
- a group common PDCCH/PDSCH is transmitted on the same time/frequency resource and can be identified by all UEs within the same MBS group.
- the names of the PTM transmission methods 1 and 2 are tentative names, and may be called by other names as long as the above-described operations are performed.
- RAN nodes may deliver individual copies of MBS data packets to individual UEs over the air.
- PTM point-to-multipoint
- a RAN node may deliver a single copy of MBS data packets over the air to a set of UEs.
- HARQ Hybrid Automatic repeat request
- ACK/NACK feedback Both ACK/NACK feedback (ACK/NACK feedback) ⁇ UEs that successfully receive/decode PDSCH transmit ACK. ⁇ UEs that fail to receive/decode PDSCH transmit NACK.
- PUCCH-Config Physical Uplink Control Channel
- - PUCCH resource Shared/orthogonal between UEs depends on network settings - HARQ-ACK CB (codebook): type-1 and type-2 (CB decision algorithm (specified in 3GPP TS38.213)) ⁇ Multiplexing: Unicast or multicast can be applied ⁇ Option 2: NACK-only feedback ⁇ A UE that has successfully received and decoded PDSCH does not transmit an ACK (does not transmit a response). ⁇ A UE that fails to receive or decode PDSCH transmits NACK. ⁇ In a given UE, PUCCH resource settings can be set separately by unicast or groupcast (multicast). ACK is a positive acknowledgment. , NACK may be called a negative acknowledgment. HARQ may be referred to as automatic repeat request.
- ⁇ RRC and downlink control information (DCI: Downlink Control Information) • RRC only Also, the following content is assumed for SPS (Semi-persistent Scheduling) of multicast/broadcast PDSCH.
- DCI Downlink Control Information
- SPS is a scheduling used in contrast to dynamic scheduling, and may be called semi-fixed, semi-persistent or semi-persistent scheduling, or interpreted as Configured Scheduling (CS) good.
- CS Configured Scheduling
- Scheduling may be interpreted as the process of allocating resources for transmitting data.
- Dynamic scheduling may be interpreted as a mechanism where all PDSCHs are scheduled by DCI (eg DCI 1_0, DCI 1_1 or DCI 1_2).
- SPS may be interpreted as a mechanism by which PDSCH transmissions are scheduled by higher layer signaling such as RRC messages.
- scheduling categories of time domain scheduling and frequency domain scheduling there may be scheduling categories of time domain scheduling and frequency domain scheduling.
- Multicast PDSCH which may include group-common PDSCH and SPS group-common PDSCH
- PDSCH scrambled by group-common RNTI which may be called G-RNTI
- G-RNTI group-common RNTI
- data and packet may be read interchangeably, and may be interpreted as being synonymous with terms such as signal and data unit.
- transmission, reception, transmission and distribution may be read interchangeably.
- FIG. 6 is a functional block configuration diagram of gNB100 and UE200.
- the UE 200 will be described below.
- 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. 6 shows only main functional blocks related to the description of the embodiment, and that the UE 200 has other functional blocks (for example, power supply section, etc.).
- FIG. 4 shows the functional block configuration of the UE 200 (gNB 100), and please refer to FIG. 13 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 supports Massive MIMO, CA that bundles multiple CCs, and DC that simultaneously communicates between the UE and each of the two NG-RAN Nodes.
- the radio signal transmitting/receiving unit 210 supports MBS, and can receive a downlink channel that is common to a terminal group (group common) in data distribution for a plurality of UEs 200 .
- the radio signal transmitting/receiving unit 210 may constitute a receiving unit that receives downlink channels.
- the radio signal transmitting/receiving unit 210 can receive a downlink data channel (PDSCH) common to the terminal group, specifically, the group-common PDSCH (which may include the SPS group-common PDSCH). Also, the radio signal transmitting/receiving section 210 can receive a downlink control channel common to the terminal group, specifically, a group-common PDCCH.
- PDSCH downlink data channel
- group-common PDSCH which may include the SPS group-common PDSCH
- the radio signal transmitting/receiving section 210 can receive a downlink control channel common to the terminal group, specifically, a group-common PDCCH.
- 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), Positioning Reference Signal (PRS) for position information, and the like.
- CSI-RS Channel State Information-Reference Signal
- SRS Sounding Reference Signal
- PRS Positioning Reference Signal
- control channels include PDCCH, PUCCH (Physical Uplink Control Channel), RACH (Random Access Channel, Downlink Control Information (DCI) including Random Access Radio Network Temporary Identifier (RA-RNTI)), and Physical Broadcast Channel (PBCH) may be included.
- PDCCH 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 and PUSCH (Physical Uplink Shared Channel).
- Data may refer to data transmitted over a data channel.
- the control signal/reference signal processing unit 240 may receive control information of higher layers (for example, RRC) including QCL of PDSCH.
- the control signal/reference signal processing unit 240 may configure a receiving unit that receives control information of higher layers.
- 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 control unit 270 controls each functional block that configures the UE200.
- the control unit 270 executes control for downlink channel scheduling for MBS and HARQ feedback for this channel.
- the control unit 270 performs control corresponding to scheduling of downlink data channels that are common to a terminal group (group common) in MBS, that is, data distribution for a plurality of UEs 200 .
- control section 270 can perform control corresponding to scheduling of group-common PDCCH and group-common PDSCH.
- the control unit 270 may assume that the QCL of PDSCH (which may include group-common PDSCH and SPS group-common PDSCH) is in a specific state common to multiple UEs 200 when a specific condition is met.
- PDSCH which may include group-common PDSCH and SPS group-common PDSCH
- a specific condition may be, for example, any of the following.
- the scheduling offset between DCI (PDCCH) and PDSCH is less than (or less than) a predetermined time (for example, timeDurationForQCL).
- the MBS PDSCH QCL may be similarly applied, that is, a specific state common to a plurality of UEs 200 may be applied.
- ⁇ It is a specific DCI format or DCI.
- DCI format 1_0 without TCI state field or DCI format 1_1, 1_2 without tciPresentInDCI set.
- a specific state (which may be called a predetermined QCL) common to a plurality of UEs 200 may be the QCL of PDCCH monitoring symbols. That is, control section 270 may receive PDSCH based on the QCL of PDCCH.
- control section 270 may be based on the QCL of some received signal (channel), such as the QCL for unicast transmission or the QCL for multicast transmission, and on which QCL the PDSCH is received is set by an upper layer.
- control unit 270 may assume that the QCL of PDSCH is in the same state as the QCL of the control resource set (CORESET). That is, the predetermined QCL may be the QCL of CORESET.
- the CORESET may be any CORESET associated with the MBS within the serving cell's active BWP.
- control unit 270 may assume that the QCL of the PDSCH is in the same state as the QCL of the PDSCH other than the current PDSCH. Specifically, the control unit 270 may assume that the QCL of the MBS PDSCH is the same as the QCL of another PDSCH related to the MBS. For example, among the QCLs of the MBS PDSCH, the QCL may be the minimum or maximum DCI codepoint (TCI codepoint may be used), or the minimum or maximum TCI state QCL.
- TCI codepoint may be used
- control section 270 may determine the state of the PDSCH QCL based on the control information of the upper layer. Specifically, the control unit 270 can determine the PDSCH QCL state based on the QCL information included in the control information of the higher layer (for example, RRC) received by the control signal/reference signal processing unit 240 . Note that the control information may be notified not only by RRC, but also by MAC CE, for example.
- the gNB 100 can execute control related to the above-described downlink channel scheduling and the like.
- radio signal transmitting/receiving section 210 of gNB 100 may transmit PDSCH, which is common to the terminal group, to multiple UEs 200 included in the terminal group in MBS.
- the radio signal transmitting/receiving unit 210 of the gNB 100 may constitute a transmitting unit.
- Fig. 7 shows a sequence example of PDCCH, PDSCH and HARQ feedback in MBS.
- PDCCH which may include DCI
- PDSCH may be transmitted by unicast or multicast (broadcast).
- the UE 200 may transmit HARQ feedback (ACK/NACK) for (the transport block (TB) received via) the channel.
- ACK/NACK HARQ feedback
- both unicast PDSCH and multicast PDSCH are transmitted after one PDCCH/DCI, but either unicast PDSCH or multicast PDSCH is transmitted after one PDCCH/DCI. may be sent. That is, one PDCCH/DCI may schedule either unicast PDSCH or multicast PDSCH.
- timeDurationForQCL is set as described above (see Fig. 4).
- the constraint of always providing a scheduling offset between DCI and PDSCH of 14 symbols or more is considered undesirable.
- Fig. 8 shows an example of the relationship between DCI format 1_0, timeDurationForQCL and PDSCH (Part 2).
- FIG. 8 shows an example in which the scheduling offset between DCI and PDSCH is shorter than timeDurationForQCL.
- UE 200 receives PDSCH using ⁇ QCL with the smallest CORESET ID in the latest monitoring slot''.
- the UE determines that the PDSCH DM-RS port of the serving cell has the lowest controlResourceSetId in the most recent slot in which one or more CORESETs in the active BWP of the serving cell are being monitored by the UE.
- the QCL parameters used for PDCCH pseudo-colocation of CORESET associated space it can be assumed that the UE may assume that the DM-RS ports of PDSCH of a serving cell are quasi co-located with the RS(s) with respect to the QCL parameter(s) used for PDCCH quasi co-location indication of the CORESET associated with a monitored search space with the lowest controlResourceSetId in the latest slot in which one or more CORESETs within the active BWP of the serving cell are monitored by the UE) (3GPP TS38.214 Section 5.1.5).
- QCL of the latest monitoring slot minimum CORESET ID may differ for each UE. There is also the possibility of CORESET for unicast transmissions. Therefore, even if such operation is applied to MBS PDSCH as it is, there is a high possibility that it will not be an appropriate QCL.
- DCI can schedule the PDSCH without symbol gaps.
- the UE After receiving the search space, the UE performs PDSCH BD and at the same time stores (buffers) the DL received signal. If the UE finds that there is a PDSCH schedule on a certain symbol after DCI detection, the UE demodulates and decodes the PDSCH using the stored DL signal.
- 3GPP Release-15 16 can only receive DL signals with one receive beam at a time. Therefore, when storing DL signals, it is necessary to receive them based on some QCL. Therefore, for example, 3GPP Release-15 stipulates that when DCI to PDSCH is scheduled for a period shorter than timeDurationForQCL, PDSCH is received using "QCL with the smallest CORESET ID in the latest monitoring slot.”
- Fig. 9 shows an example of the relationship between group-common PDCCH, timeDurationForQCL and group-common PDSCH.
- the "QCL of the latest monitoring slot minimum CORESET ID" differs for each UE, so the same PDSCH cannot be received with the same QCL. .
- FIG. 10 shows an example relationship between CFR, group-common PDCCH, group-common PDSCH and unicast PDCCH/PDSCH.
- CFR MBS specific BWP (Option 2A)
- unicast and multicast are separate BWPs, so even as the QCL of "the latest monitoring slot's minimum CORESET ID QCL" (within the active BWP of the serving cell), the MBS PDSCH QCL is There is no problem because it will be the QCL of PDCCH.
- FIG. 10 shows an example in which the CFR is different from the BWP for unicast, but it is also possible to have a mutually inclusive relationship.
- defining the MBS frequency region within the dedicated unicast BWP (Option 2B) is also under consideration.
- unicast and multicast are the same BWP, so if "QCL with the smallest CORESET ID in the latest monitoring slot" (within the active BWP of the serving cell), the MBS PDSCH QCL is the same as the unicast PDCCH QCL. There is a possibility that it will become a problem.
- the QCL of the group-common PDSCH is shared between UEs in the operation example below.
- the QCL of unicast PDCCH/PDSCH may differ between UEs.
- Default TCI state of group-common PDSCH (DCI to PDSCH is less than timeDurationForQCL) is defined.
- the QCL of (DMRS of) PDSCH associated with MBS may be a predetermined QCL under predetermined conditions.
- a predetermined condition may be any of the following.
- ⁇ DCI to PDSCH scheduling offset is a predetermined time (for example, less than (or less than) timeDurationForQCL).
- the MBS PDSCH QCL may be applied in the same way, not limited to (less than) the predetermined time.
- ⁇ Prescribed DCI format or DCI For example, a DCI format or DCI that does not have a TCI state field (eg DCI format 1_0 or DCI format 1_1/1_2 when tciPresentInDCI is not set).
- enableDefaultTCIStateForMulticast may be interpreted as an IE that enables the default TCI state for multicast.
- the PDSCH related to MBS may be interpreted as PDSCH-Config or PDSCH resource in which MBS is configured, or PDSCH scheduled in CORESET/Search-Space (SS) related to MBS. It may also be interpreted as PDSCH scheduled with DCI with CRC scrambled by G-RNTI.
- Predetermined QCL may be interpreted as a PDCCH monitoring symbol.
- the UE 200 may receive the PDSCH based on the PDCCH QCL.
- the given QCL may be interpreted as a symbol other than the PDCCH monitoring symbol.
- the UE 200 may store the received signal based on some predetermined QCL. Since the UE 200 can assume only one predetermined QCL at a time, whether to apply the predetermined QCL for unicast or the predetermined QCL for multicast may be switched by an upper layer.
- the UE 200 operates according to 3GPP Release-15, specifically, operates using the Type A RS or Type D RS described above, and assumes a predetermined QCL for unicast. It may store the received signal and receive the PDSCH.
- the UE 200 may operate according to one of the operation examples described later, store the received signal assuming a predetermined QCL for multicast, and receive the PDSCH (in accordance with 3GPP Release-17 may be interpreted as actions).
- enableDefaultTCIStateForMulticast is a tentative name as described above, and may be called by another name.
- the “predetermined QCL” may be the CORESET QCL.
- (the DMRS of) the PDSCH associated with the MBS may be received using a predetermined QCL.
- the predetermined QCL may be any of the following CORESET QCLs associated with the MBS (but within the active BWP of the serving cell).
- the same QCL as any one of the MBS CORESETs can be appropriately applied to the MBS PDSCH.
- the UE receives DM-RS in the PDSCH associated with the MBS frequency domain (CFR) of the serving cell.
- a port is in a PDCCH pseudo-colocation of CORESETs associated with the monitored search space with the lowest controlResourceSetId among the CORESETs associated with the MBS frequency domain (CFR) in the most recent monitoring slot in the active BWP of the serving cell.
- RS and pseudo-colocation If a UE is configured with enableDefaultTCIStateForMulticast and the UE is configured by higher layer parameter PDCCH-Config that associates with MBS frequency region (CFR), the UE may assume that the DM-RS ports of PDSCH associated with MBS frequency region (CFR) of a serving cell are quasi co-located with the RS(s) with respect to the QCL parameter(s) used for PDCCH quasi co-location indication of the CORESET associated with a monitored search space with the lowest controlResourceSetId among CORESETs associated with MBS frequency region (CFR) in the latest monitoring slot within the active BWP of the serving cell.).
- the “predetermined QCL” may be the PDSCH QCL.
- (the DMRS of) the PDSCH associated with the MBS may be received using a given QCL.
- the predetermined QCL may be any of the following QCLs of PDSCH related to MBS.
- FIG. 11 shows an example of a minimum DCI codepoint according to Operation Example 2.
- FIG. 11 the smallest DCI codepoint (QCL corresponding to TCI state "#28" in TCI state field "000") may be selected.
- a QCL appropriately set for MBS PDSCH can be applied to MBS PDSCH.
- the UE shall specify the DM-RS port of the PDSCH associated with the MBS frequency domain (CFR) of the serving cell.
- the UE may assume that the DM-RS ports of PDSCH associated with MBS frequency region (CFR) of a serving cell are quasi co-located with the RS(s) with respect to the QCL parameter(s) associated with the TCI states corresponding to the lowest codepoint among the TCI codepoints within PDSCH configured for MBS frequency region (CFR ) within the active BWP of the serving cell.).
- the “predetermined QCL” may be set by higher layers. As described above, (the DMRS of) the PDSCH associated with the MBS may be received using a given QCL.
- the predetermined QCL set by the upper layer may be the TCI state or QCL set by RRC or MAC CE.
- the TCI state/QCL used in the Default TCI state may be set in advance by the upper layer.
- the TCI state/QCL may also be called Unified TCI, Common TCI state/QCL, or the like. In particular, it may use the TCI state/QCL set in relation to the MBS.
- a QCL appropriately set for MBS can be applied to MBS PDSCH.
- the UE shall specify the DM-RS port of the PDSCH associated with the MBS frequency domain (CFR) of the serving cell.
- the UE may assume that the DM-RS ports of PDSCH associated with MBS frequency region (CFR) of a serving cell are quasi co-located with the RS (s) with respect to the QCL parameter(s) associated with the TCI states configured for MBS frequency region (CFR) within the active BWP of the serving cell.).
- Default TCI state of unicast PDSCH that is, if unicast DCI to unicast PDSCH ⁇ timeDurationForQCL, DCI without TCI state field (for example, DCI format 1_0 without TCI state field, or tciPresentInDCI is not set Unicast PDSCH QCL) scheduled by DCI format 1_1, 1_2, etc.) is not clear.
- gNB 100 and UE 200 may operate according to any of the following.
- the operation using the Type A RS or Type D RS described above, specifically, the Type A RS or Type D RS described in (1.2) QCL/TCI state Execute the measurement operation, and follow the operation example described above for the Default TCI state of the multicast PDSCH.
- the Default TCI state of the unicast PDSCH also follows this operation example in the same way as the Default TCI state of the multicast PDSCH (however, it may be limited to when enableDefaultTCIStateForMulticast is set).
- the UE 200 may receive multicast/unicast PDSCH with a predetermined QCL under predetermined conditions.
- the (draft) expression in the 3GPP specification mentioned above states that "the UE may assume that the DM-RS port of the PDSCH associated with the MBS frequency domain (CFR) of the serving cell" that the DM-RS ports of PDSCH associated with MBS frequency region (CFR)... but the part "associated with MBS frequency region (CFR)" may be deleted.
- FIG. 12 shows an example of the relationship between CFR, group-common PDCCH, group-common PDSCH, and unicast PDCCH/PDSCH according to the modified example.
- the Default TCI state for the MBS PDSCH may be applied.
- the Default TCI state for the MBS PDSCH may be applied to the PDSCH scheduled by the DCI.
- an appropriate pseudo collocation can be assumed in MBS, that is, simultaneous data transmission service to specified or unspecified multiple UEs.
- the names PDCCH and PDSCH are used as downlink channels, but other names may be used as long as they are downlink control channels or downlink data channels (or shared channels). .
- the MBS PDSCH has been described as an example, but at least one of the operation examples described above may be applied to other downlink channels such as the MBS PDCCH. Furthermore, the operation examples described above may be combined and applied in a complex manner unless there is a contradiction.
- configure, activate, update, indicate, enable, specify, and select may be read interchangeably.
- 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. 13 is a diagram showing an example of the hardware configuration of the device.
- the device may be configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, 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. 6) 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 (or sidelinks).
- 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 of a fixed length of time (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” can 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.”
- Radio communication system 20 NG-RAN 100 gNB 200UE 210 radio signal transmission/reception unit 220 amplifier unit 230 modulation/demodulation unit 240 control signal/reference signal processing unit 250 encoding/decoding unit 260 data transmission/reception unit 270 control unit 1001 processor 1002 memory 1003 storage 1004 communication device 1005 input device 1006 output device 1007 bus
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
図1は、本実施形態に係る無線通信システム10の全体概略構成図である。無線通信システム10は、
(1)無線通信システムの全体概略構成
(1.1)システム構成例
図1は、本実施形態に係る無線通信システム10の全体概略構成図である。無線通信システム10は、5G New Radio(NR)に従った無線通信システムであり、Next Generation-Radio Access Network 20(以下、NG-RAN20、及び複数の端末200(User Equipment 200、以下、UE200)を含む。
・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)が用いられてもよい。
擬似コロケーション(QCL:Quasi-Colocation)とは、例えば、一方のアンテナポート上のシンボルが搬送されるチャネルの特性が、他方のアンテナポート上のシンボルが搬送されるチャネルから推測できる場合、2つのアンテナポートは擬似的に同じ場所にあるとするものである。
・ドップラースプレッド
・平均遅延
・遅延スプレッド
・空間Rxパラメータ
また、このようなパラメータを用いてQCLタイプが規定されてもよい。具体的には、QCLタイプは、3GPP TS38.214の5.1.5章において、以下のように規定される。
・QCL-Type B: {Doppler shift, Doppler spread}
・QCL-Type C: {Doppler shift,average delay}
・QCL-Type D: {Spatial Rx parameter}
PDCCH/PDSCHのDMRSのTCI stateとしては、Type Aが必ず設定され,加えてType Dが設定されてよい(特にFR2の場合)。
無線通信システム10では、マルチキャスト/ブロードキャスト・サービス(MBS:Multicast and Broadcast Services)が提供されてよい。
・RRC connected UEのMBS groupに対して、グループ共通(group-common)PDCCHを用いてgroup-common PDSCHをスケジューリングする。
・RRC connected UEのMBS groupに対して、端末固有(UE-specific)PDCCHを用いてgroup-common PDSCHをスケジューリングする。
・RRC connected UEに対して、UE-specific PDCCHを用いてUE-specific PDSCHをスケジューリングする。
・PDSCH受信・復号に成功したUEは、ACKを送信する
・PDSCH受信・復号に失敗したUEは、NACKを送信する
・PUCCH(Physical Uplink Control Channel)リソース設定:マルチキャスト向けにPUCCH-Configを設定できる
・PUCCHリソース:UE間の共有/直交(shared/orthogonal)は、ネットワークの設定による
・HARQ-ACK CB (codebook):type-1及びtype-2(CB決定アルゴリズム(3GPP TS38.213において規定))をサポート
・多重化:ユニキャストまたはマルチキャストを適用可
・オプション2:NACKのみをフィードバック(NACK-only feedback)
・PDSCH受信・復号に成功したUEは、ACKを送信しない(応答を送信しない)
・PDSCH受信・復号に失敗したUEは、NACKを送信する
・所定のUEにおいて、PUCCHリソース設定は、ユニキャストまたはグループキャスト(マルチキャスト)によって別々に設定できる
なお、ACKは、positive acknowledgement(肯定応答)、NACKは、negative acknowledgement(否定応答)と呼ばれてもよい。HARQは、自動再送要求と呼ばれてもよい。
・RRCのみ
また、マルチキャスト/ブロードキャストPDSCHのSPS(Semi-persistent Scheduling)について、次のような内容が想定されている。
・UE能力(capability)として、複数のSPS group-common PDSCHが設定できる
・SPS group-common PDSCHに対するHARQフィードバックが可能
・少なくともgroup-common PDCCHによるアクティブ化/非アクティブ化(activation/deactivation)が可能
なお、非アクティブ化(deactivation)は、解放(release)などの他の同義の用語に読み替えられてもよい。例えば、アクティブ化は、起動、開始、トリガーなど、非アクティブ化は、さらに、終了、停止などに読み替えられてもよい。
次に、無線通信システム10の機能ブロック構成について説明する。具体的には、gNB100及びUE200の機能ブロック構成について説明する。
次に、無線通信システム10の動作について説明する。具体的には、MBSに関する下りチャネルのスケジューリング、特にQCLの想定に関する動作について説明する。
group-common PDSCHのDefault TCI state(DCI to PDSCH is less than timeDurationForQCL)が規定される。
本動作例では、MBS PDSCHに対して所定のQCLを適用させる条件が示される。MBSに関連するPDSCH(のDMRS)のQCLは、所定の条件において、所定のQCLとしてよい。
例えば、TCI state fieldを有さないDCI formatまたはDCI(例えば、DCI format 1_0、またはDCI format 1_1/1_2においてtciPresentInDCIが設定されない場合)が挙げられる。
例えば、UE200がRRCのIE(enableDefaultTCIStateForMulticast(仮称))によって設定されている場合が挙げられる。enableDefaultTCIStateForMulticastは、マルチキャスト用のデフォルトのTCI stateを有効にするIEと解釈されてよい。
本動作例では、「所定のQCL」は、CORESETのQCLとしてよい。上述したように、MBSに関連するPDSCH(のDMRS)は、所定のQCLを用いて受信されてよい。
・MBSに関連するCORESETの中において、最新monitoring slotの最小CORESET IDのQCL
本動作例によれば、MBS PDSCHには、適切にMBS CORESETの中から何れかのCORESETと同一のQCLを適用できる。
本動作例では、「所定のQCL」は、PDSCHのQCLとしてよい。上述したように、MBSに関連するPDSCH(のDMRS)は、所定のQCLを用いて受信されてよい。
・最小または最大のTCI state IDのQCL
図11は、動作例2に係る最小DCI codepointの例を示す。図11に示すように、最小のDCI codepoint(TCI state field "000"のTCI state "#28"と対応するQCL)が選択されてよい。
本動作例では、「所定のQCL」は、上位レイヤによって設定されてよい。上述したように、MBSに関連するPDSCH(のDMRS)は、所定のQCLを用いて受信されてよい。
上述した動作例において、以下のような変更がなされてもよい。例えば、動作例1~3に関する3GPPの仕様の表現(案)では、enableDefaultTCIStateForMulticastが設定されたら、MBSに関連するPDSCHをMBS向け所定QCLに基づいて受信すると記載されていた。
上述した実施形態によれば、以下の作用効果が得られる。具体的には、動作例0~3に係るgNB100及びUE200によれば、MBS、つまり、特定または不特定の複数のUEへの同時データ送信サービスにおいて、適切な擬似コロケーション(QCL)を想定できる。
以上、実施形態について説明したが、当該実施形態の記載に限定されるものではなく、種々の変形及び改良が可能であることは、当業者には自明である。
無線フレームは時間領域において1つまたは複数のフレームによって構成されてもよい。時間領域において1つまたは複数の各フレームはサブフレームと呼ばれてもよい。サブフレームはさらに時間領域において1つまたは複数のスロットによって構成されてもよい。サブフレームは、ニューメロロジー(numerology)に依存しない固定の時間長(例えば、1ms)であってもよい。
20 NG-RAN
100 gNB
200 UE
210 無線信号送受信部
220 アンプ部
230 変復調部
240 制御信号・参照信号処理部
250 符号化/復号部
260 データ送受信部
270 制御部
1001 プロセッサ
1002 メモリ
1003 ストレージ
1004 通信装置
1005 入力装置
1006 出力装置
1007 バス
Claims (6)
- 複数の端末向けのデータ配信において、端末グループに共通である下りデータチャネルを受信する受信部と、
前記下りデータチャネルの擬似コロケーションは、特定の条件を満たす場合、前記複数の端末において共通な特定の状態であると想定する制御部と
を備える端末。 - 前記制御部は、前記下りデータチャネルの擬似コロケーションは、制御リソースセットの擬似コロケーションと同じ状態であると想定する請求項1に記載の端末。
- 前記制御部は、前記下りデータチャネルの擬似コロケーションは、前記下りデータチャネルと別の下りデータチャネルの擬似コロケーションと同じ状態であると想定する請求項1に記載の端末。
- 前記受信部は、前記下りデータチャネルの擬似コロケーションを含む上位レイヤの制御情報を受信し、
前記制御部は、前記制御情報に基づいて、前記下りデータチャネルの擬似コロケーションの状態を決定する請求項1に記載の端末。 - 無線基地局と端末とを含む無線通信システムであって、
前記無線基地局は、複数の端末向けのデータ配信において、端末グループに共通である下りデータチャネルを送信する送信部を備え、
前記端末は、
前記下りデータチャネルを受信する受信部と、
前記下りデータチャネルの擬似コロケーションは、特定の条件を満たす場合、前記複数の端末において共通な特定の状態であると想定する制御部と
を備える無線通信システム。 - 複数の端末向けのデータ配信において、端末グループに共通である下りデータチャネルを受信するステップと、
前記下りデータチャネルの擬似コロケーションは、特定の条件を満たす場合、前記複数の端末において共通な特定の状態であると想定するステップと
を含む無線通信方法。
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US18/282,714 US20240163060A1 (en) | 2021-03-19 | 2021-03-19 | Terminal, radio communication system and radio communication method |
CN202180095732.1A CN117063562A (zh) | 2021-03-19 | 2021-03-19 | 终端、无线通信系统和无线通信方法 |
PCT/JP2021/011517 WO2022195885A1 (ja) | 2021-03-19 | 2021-03-19 | 端末、無線通信システム及び無線通信方法 |
JP2023506697A JPWO2022195885A1 (ja) | 2021-03-19 | 2021-03-19 |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/JP2021/011517 WO2022195885A1 (ja) | 2021-03-19 | 2021-03-19 | 端末、無線通信システム及び無線通信方法 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2022195885A1 true WO2022195885A1 (ja) | 2022-09-22 |
Family
ID=83322178
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2021/011517 WO2022195885A1 (ja) | 2021-03-19 | 2021-03-19 | 端末、無線通信システム及び無線通信方法 |
Country Status (4)
Country | Link |
---|---|
US (1) | US20240163060A1 (ja) |
JP (1) | JPWO2022195885A1 (ja) |
CN (1) | CN117063562A (ja) |
WO (1) | WO2022195885A1 (ja) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20230039425A1 (en) * | 2021-08-04 | 2023-02-09 | Qualcomm Incorporated | Techniques for configuring tci states for mbs transmissions |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2021009916A1 (ja) * | 2019-07-18 | 2021-01-21 | 株式会社Nttドコモ | 端末及び無線通信方法 |
WO2021024494A1 (ja) * | 2019-08-08 | 2021-02-11 | 株式会社Nttドコモ | 端末及び無線通信方法 |
-
2021
- 2021-03-19 CN CN202180095732.1A patent/CN117063562A/zh active Pending
- 2021-03-19 US US18/282,714 patent/US20240163060A1/en active Pending
- 2021-03-19 JP JP2023506697A patent/JPWO2022195885A1/ja active Pending
- 2021-03-19 WO PCT/JP2021/011517 patent/WO2022195885A1/ja active Application Filing
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2021009916A1 (ja) * | 2019-07-18 | 2021-01-21 | 株式会社Nttドコモ | 端末及び無線通信方法 |
WO2021024494A1 (ja) * | 2019-08-08 | 2021-02-11 | 株式会社Nttドコモ | 端末及び無線通信方法 |
Non-Patent Citations (3)
Title |
---|
MODERATOR (BBC): "Feature lead summary on RAN basic functions for broadcast/multicast for UEs in RRC_IDLE/ RRC_INACTIVE states", 3GPP DRAFT; R1-2101721, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20210125 - 20210205, 26 January 2021 (2021-01-26), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051975864 * |
NTT DOCOMO, INC.: "Discussion on group scheduling mechanism for RRC_CONNECTED UEs", 3GPP DRAFT; R1-2103594, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20210412 - 20210420, 6 April 2021 (2021-04-06), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051993442 * |
OPPO: "Enhancements on multi-TRP for PDCCH, PUCCH and PUSCH", 3GPP DRAFT; R1-2100119, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20210125 - 20210205, 19 January 2021 (2021-01-19), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051970818 * |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20230039425A1 (en) * | 2021-08-04 | 2023-02-09 | Qualcomm Incorporated | Techniques for configuring tci states for mbs transmissions |
US11937270B2 (en) * | 2021-08-04 | 2024-03-19 | Qualcomm Incorporated | Techniques for configuring TCI states for MBS transmissions |
Also Published As
Publication number | Publication date |
---|---|
US20240163060A1 (en) | 2024-05-16 |
CN117063562A (zh) | 2023-11-14 |
JPWO2022195885A1 (ja) | 2022-09-22 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2022195885A1 (ja) | 端末、無線通信システム及び無線通信方法 | |
WO2022190389A1 (ja) | 端末及び無線通信方法 | |
WO2022195713A1 (ja) | 端末及び無線通信方法 | |
WO2022234622A1 (ja) | 端末及び無線通信方法 | |
WO2023022135A1 (ja) | 端末及び無線通信方法 | |
WO2022239086A1 (ja) | 端末及び無線通信方法 | |
WO2022239084A1 (ja) | 端末及び無線通信方法 | |
WO2022269910A1 (ja) | 端末、無線通信システム及び無線通信方法 | |
WO2023012982A1 (ja) | 端末及び無線通信方法 | |
WO2022234670A1 (ja) | 端末及び無線通信方法 | |
WO2022239083A1 (ja) | 端末及び無線通信方法 | |
WO2022195711A1 (ja) | 端末及び無線通信方法 | |
WO2022195884A1 (ja) | 端末、無線通信システム及び無線通信方法 | |
WO2022195883A1 (ja) | 端末及び無線通信システム | |
WO2023021855A1 (ja) | 端末及び無線通信方法 | |
WO2022239085A1 (ja) | 端末及び無線通信方法 | |
WO2022269933A1 (ja) | 端末及び無線通信方法 | |
WO2023026941A1 (ja) | 端末、無線通信システム及び無線通信方法 | |
WO2023026968A1 (ja) | 端末、無線通信システム及び無線通信方法 | |
WO2022244497A1 (ja) | 端末、無線通信システム及び無線通信方法 | |
WO2022215272A1 (ja) | 端末、基地局、無線通信システム及び無線通信方法 | |
WO2022195787A1 (ja) | 端末、無線通信システム及び無線通信方法 | |
WO2022190377A1 (ja) | 端末、無線通信システム及び無線通信方法 | |
WO2022244097A1 (ja) | 端末及び無線通信方法 | |
WO2023026975A1 (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: 21931630 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2023506697 Country of ref document: JP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 202180095732.1 Country of ref document: CN |
|
WWE | Wipo information: entry into national phase |
Ref document number: 18282714 Country of ref document: US |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 21931630 Country of ref document: EP Kind code of ref document: A1 |