WO2023286260A1 - Terminal et procédé de communication sans fil - Google Patents

Terminal et procédé de communication sans fil Download PDF

Info

Publication number
WO2023286260A1
WO2023286260A1 PCT/JP2021/026709 JP2021026709W WO2023286260A1 WO 2023286260 A1 WO2023286260 A1 WO 2023286260A1 JP 2021026709 W JP2021026709 W JP 2021026709W WO 2023286260 A1 WO2023286260 A1 WO 2023286260A1
Authority
WO
WIPO (PCT)
Prior art keywords
pucch
priority
scell
config
terminal
Prior art date
Application number
PCT/JP2021/026709
Other languages
English (en)
Japanese (ja)
Inventor
優元 ▲高▼橋
聡 永田
チーピン ピ
ジン ワン
ラン チン
Original Assignee
株式会社Nttドコモ
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 株式会社Nttドコモ filed Critical 株式会社Nttドコモ
Priority to PCT/JP2021/026709 priority Critical patent/WO2023286260A1/fr
Publication of WO2023286260A1 publication Critical patent/WO2023286260A1/fr

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W16/00Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/24Cell structures
    • H04W16/32Hierarchical cell structures
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/02Selection of wireless resources by user or terminal
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/04Wireless resource allocation

Definitions

  • the present disclosure relates to terminals and wireless communication methods.
  • LTE Long Term Evolution
  • UMTS Universal Mobile Telecommunication System
  • LTE-A Long Term Evolution-Advanced
  • FAA Future Radio Access
  • 5G 5th generation mobile communication system
  • 5G+ 5th generation mobile communication system
  • New-RAT Radio Access Technology
  • NR Radio
  • Non-Patent Document 1 For example, in NR, strengthening the function of feedback from terminals to base stations is under consideration in order to improve communication quality (for example, Non-Patent Document 1).
  • One aspect of the present disclosure provides a terminal and a radio communication method that can appropriately configure resources used for transmitting information fed back from the terminal to the base station.
  • a terminal determines priority of configuration information regarding one or more uplink control channels configured for each of a plurality of cells, and transmits control information according to the priority.
  • a control unit that sets resources, and a transmission unit that transmits the control information in the set resources.
  • a terminal determines priority of configuration information regarding one or more uplink control channels configured for each of a plurality of cells, and according to the priority
  • a resource for transmitting control information is set, and the control information is transmitted in the set resource.
  • FIG. 4 is a diagram showing an example of PUCCH carrier switching; 2 is a block diagram showing an example of the configuration of a base station according to one embodiment; FIG. 1 is a block diagram showing an example of a configuration of a terminal according to one embodiment; FIG. FIG. 10 is a diagram showing an example 1 of priority determination; 1 is a diagram showing an example of Alt.1 in Priority Determination Example 2.
  • FIG. 2 is a diagram showing an example of Alt.2 in Priority Determination Example 2.
  • FIG. FIG. 4 is a diagram showing an example of the relationship between priority and carrier switching;
  • FIG. 4 is a diagram showing an example of configuration of option 1 of PUCCH resource type in each cell; FIG.
  • FIG. 4 is a diagram showing an example of configuration of option 2 of PUCCH resource type in each cell; It is a figure which shows an example of PUCCH-Config. It is a figure which shows an example of PUCCH-CSI-Resource.
  • FIG. 10 is a diagram showing an example of priority mismatch regarding configuration of PUCCH resources in a PUCCH cell;
  • FIG. 10 is a diagram showing an example of UCI type mismatch with respect to PUCCH resource configuration in a PUCCH cell;
  • Figure 5 shows an example of Opt. 5 for priority or UCI type mismatch.
  • FIG. 3 is a diagram showing an example 1 of PUCCH report configuration;
  • FIG. 10 is a diagram showing example 2 of PUCCH report configuration; It is a figure which shows an example of the hardware configuration of the base station and terminal which concern on one Embodiment.
  • HARQ-ACK Hybrid Automatic Repeat request - Acknowledgment
  • PUCCH Physical Uplink Control Channel
  • PUCCH carrier switching is a technique applied when a base station communicates through multiple cells. Dual connectivity, which is an example of communication via multiple cells, and PUCCH carrier switching will be described below.
  • FIG. 1 is a diagram illustrating an example of dual connectivity (DC).
  • base station 10-1 may be a MasterNode (MN).
  • Base station 10-2 may be a secondary node (SN).
  • DC bundles carriers between different base stations.
  • the base station 10-1 communicates with the terminal 20 via a primary cell (Pcell) and a secondary cell (Scell).
  • Pcell primary cell
  • Scell secondary cell
  • terminal 20 has established an RRC connection with base station 10-1.
  • the uplink control information (eg, UCI) received by the Pcell of the base station 10-1 is transferred to the backhaul Notify the base station 10-2 via a link (for example, a wired or wireless link connecting the base station 10-1 and the base station 10-2) and reflect it in the scheduling of Scell under the base station 10-2.
  • a link for example, a wired or wireless link connecting the base station 10-1 and the base station 10-2
  • one carrier under the control of the base station 10-2 may be set as the Primary Scell (PScell), and PUCCH transmission may be supported by the PScell.
  • PScell Primary Scell
  • terminal 20 transmits UCI to base station 10-2 via PScell.
  • the terminal 20 sets Scell in addition to Pcell for the base station 10-1. Also, the terminal 20 sets Scell in addition to PScell for the base station 10-2.
  • the terminal 20 transmits the UCI of each carrier under the control of the base station 10-1 on the PUCCH of the Pcell. Also, the terminal 20 transmits the UCI of each carrier under the control of the base station 10-2 on PUCCH of the PScell.
  • the cell group (CG) under the base station 10-1 may be called MasterCell-Group (MCG).
  • a cell group under the base station 10-2 may be called a Secondary Cell-Group (SCG).
  • terminal 20 transmits PUCCH via Pcell, PScell, and/or PUCCH-Scell. In general, it is not assumed that the terminal 20 transmits PUCCH via Scells other than Pcell, PScell, and PUCCH-Scell.
  • PUCCH carrier switching is being studied as a method of reducing HARQ-ACK feedback latency in the Time Division Duplex (TDD) system.
  • FIG. 2 is a diagram showing an example of PUCCH carrier switching.
  • the base station 10 and the terminal 20 are communicating via cell 1 and cell 2.
  • cell 1 is Pcell and cell 2 is Scell.
  • the example of FIG. 2 also shows downlink (DL) slots and uplink (UL) slots in each cell.
  • the terminal 20 receives data (receives PDSCH) at the timing of S101.
  • the terminal 20 attempts to transmit HARQ-ACK for the data received in S101 at the timing of S102, but at the timing of S102, the cell1 slot is a downlink (DL) slot. Therefore, when the terminal 20 transmits HARQ-ACK in cell 1, HARQ-ACK transmission is suspended until the PUCCH transmission timing in the uplink (UL) slot (for example, the timing of S103 in FIG. 2). So the latency of HARQ-ACK transmission increases.
  • the PUCCH transmission timing in the uplink (UL) slot may be referred to as a PUCCH transmission opportunity.
  • the slot of cell 2 is the UL slot at the timing of S102.
  • the terminal 20 can transmit HARQ-ACK for the data received in S101 at the PUCCH transmission opportunity of cell 2 at the timing of S102, the latency of HARQ-ACK transmission can be reduced.
  • URLLC particularly requires low delay in the radio section. For this reason, 3GPP is considering PUCCH carrier switching in which the terminal 20 switches the carrier for PUCCH transmission as an extension of the URLLLC technology.
  • the "same timing" may be completely the same timing, or may be a time resource (for example, one or more symbols (a resource in time units shorter than a symbol) may be the same or overlap.
  • PUCCH carrier switching means that when terminal 20 attempts to transmit PUCCH at a specific transmission timing of Pcell (may be PScell or PUCCH-Scell), Pcell (may be PScell or PUCCH-Scell) Since the slot of the specific transmission timing of the DL slot is a DL slot, the terminal 20 selects a cell that transmits PUCCH from the Pcell (may be PScell or PUCCH-Scell) from the specific One of one or more Scells in which the slot with the same timing as the transmission timing is the UL slot (in the case of PScell, it is a Scell other than PScell, and in the case of PUCCH-Scell, PUCCH-Scell It may be to switch to Scell other than Scell).
  • the specific transmission timing unit is not limited to the slot.
  • the specific transmission timing may be timing in units of subframes or timing in units of symbols.
  • the first method is a method in which the base station 10 dynamically instructs the terminal 20 of a carrier for PUCCH transmission.
  • the second method is a method in which the base station 10 semi-statically sets the carrier for PUCCH transmission to the terminal 20 . It should be noted that, in the following embodiments, "transmitting PUCCH” and “transmitting PUCCH” may mean transmitting uplink control information via PUCCH.
  • the terminal 20 may notify the base station 10 of terminal capability information (UE capability) that defines information on the capability of the terminal regarding PUCCH transmission.
  • UE capability terminal capability information
  • information indicating whether or not the terminal 20 supports switching settings related to transmission of control information may be defined.
  • Switching settings for transmission of control information may be, for example, switching resources (for example, carriers) used for transmission of control information. Switching resources (for example, carriers) used for transmitting control information may be referred to as “PUCCH carrier switching”.
  • Information indicating whether or not the terminal 20 supports PUCCH carrier switching based on DCI associated with the PUCCH may be defined as the terminal capability information of the terminal 20 .
  • Information indicating whether or not the terminal 20 supports PUCCH carrier switching based on DCI that is not associated with PUCCH may be defined as the terminal capability information of the terminal 20 .
  • PUCCH resource configuration should be per UL BWP (Uplink Bandwidth Part) (eg, per candidate cell and the UL BWP of that candidate cell).
  • UL BWP Uplink Bandwidth Part
  • PUCCH configuration in a candidate PUCCH cell there is room for consideration, for example, in the following points.
  • PUCCH-Config which is information about PUCCH settings. • For periodic or semi-static PUCCH reporting. • How to handle possible problems caused by mismatching PUCCH resource configuration priorities or UCI types in PUCCH cells.
  • priority of PUCCH resource configuration or the UCI type may be an example of parameters associated with PUCCH resources.
  • a terminal and a wireless communication method are provided that can appropriately configure resources used for transmitting information fed back from the terminal to the base station.
  • the radio communication system includes base station 10 shown in FIG. 3 and terminal 20 shown in FIG.
  • the number of base stations 10 and the number of terminals 20 are not particularly limited.
  • the wireless communication system may be a wireless communication system according to New Radio (NR).
  • NR New Radio
  • the wireless communication system may be a wireless communication system according to a scheme called URLLC and/or IIoT.
  • the wireless communication system may be a wireless communication system that conforms to a system called 5G, Beyond 5G, 5G Evolution, or 6G.
  • the base station 10 may be called an NG-RAN Node, ng-eNB, eNodeB (eNB), or gNodeB (gNB).
  • the terminal 20 may be called User Equipment (UE).
  • the base station 10 may be regarded as a device included in the network to which the terminal 20 connects.
  • the radio communication system may include Next Generation-Radio Access Network (NG-RAN).
  • NG-RAN includes multiple NG-RAN Nodes, specifically gNBs (or ng-eNBs), and is connected to a 5G-compliant core network (5GC, not shown).
  • 5GC 5G-compliant core network
  • NG-RAN and 5GC may be simply referred to as "networks”.
  • the base station 10 performs wireless communication with the terminal 20.
  • the wireless communication performed complies with NR.
  • At least one of the base station 10 and the terminal 20 uses Massive MIMO (Multiple-Input Multiple-Output) to generate beams (BM) with higher directivity by controlling radio signals transmitted from a plurality of antenna elements. You can respond.
  • at least one of the base station 10 and the terminal 20 may support carrier aggregation (CA) that uses multiple component carriers (CC) in a bundle.
  • CA carrier aggregation
  • CC component carriers
  • at least one of the base station 10 and the terminal 20 may support dual connectivity (DC), etc., in which communication is performed between the terminal 20 and each of the plurality of base stations 10 .
  • a wireless communication system may support multiple frequency bands.
  • a wireless communication system supports Frequency Ranges (FR) 1 and FR2.
  • the frequency bands of each FR are, for example, as follows. ⁇ FR1: 410MHz to 7.125GHz ⁇ FR2: 24.25GHz to 52.6GHz
  • FR1 Sub-Carrier Spacing (SCS) of 15 kHz, 30 kHz or 60 kHz may be used, and a bandwidth (BW) of 5 MHz to 100 MHz may be used.
  • SCS Sub-Carrier Spacing
  • BW bandwidth
  • FR2 is, for example, a higher frequency than FR1.
  • FR2 may use an SCS of 60 kHz or 120 kHz and a bandwidth (BW) of 50 MHz to 400 MHz.
  • FR2 may include a 240 kHz SCS.
  • the wireless communication system in this embodiment may support a frequency band higher than the frequency band of FR2.
  • the wireless communication system in this embodiment can support frequency bands exceeding 52.6 GHz and up to 114.25 GHz.
  • Such high frequency bands may be referred to as "FR2x.”
  • Cyclic Prefix-Orthogonal Frequency Division Multiplexing CP-OFDM
  • DFT-S-OFDM Discrete Fourier Transform - Spread - Orthogonal Frequency Division Multiplexing
  • SCS Sub-Carrier Spacing
  • DFT-S-OFDM may be applied to both uplink and downlink, or may be applied to either one.
  • a time division duplex (TDD) slot configuration pattern may be set.
  • slots for transmitting downlink (DL) signals, slots for transmitting uplink (UL) signals, slots in which DL signals, UL signals and guard symbols are mixed, and signals to be transmitted are flexible
  • a pattern may be defined that indicates the order of two or more of the slots to be changed to .
  • channel estimation of PUSCH can be performed using a demodulation reference signal (DMRS) for each slot.
  • DMRS demodulation reference signal
  • Such channel estimation may be called joint channel estimation. Alternatively, it may be called by another name such as cross-slot channel estimation.
  • the terminal 20 may transmit the DMRS assigned to each of the multiple slots so that the base station 10 can perform joint channel estimation using DMRS.
  • an enhanced function may be added to the feedback function from the terminal 20 to the base station 10.
  • enhanced functionality of terminal feedback for HARQ-ACK may be added.
  • the configurations of the base station 10 and the terminal 20 will be explained.
  • the configurations of base station 10 and terminal 20 described below are examples of functions related to the present embodiment.
  • the base station 10 and terminal 20 may have functions not shown.
  • the functional division and/or the name of the functional unit are not limited as long as the function executes the operation according to the present embodiment.
  • FIG. 3 is a block diagram showing an example of the configuration of base station 10 according to this embodiment.
  • the base station 10 includes a transmitter 101, a receiver 102, and a controller 103, for example.
  • the base station 10 wirelessly communicates with the terminal 20 (see FIG. 4).
  • the transmission section 101 transmits a downlink (DL) signal to the terminal 20 .
  • the transmitter 101 transmits a DL signal under the control of the controller 103 .
  • a DL signal may include, for example, a downlink data signal and control information (eg, Downlink Control Information (DCI)).
  • DCI Downlink Control Information
  • the DL signal may include information (for example, UL grant) indicating scheduling regarding signal transmission of the terminal 20 .
  • the DL signal may include higher layer control information (for example, Radio Resource Control (RRC) control information).
  • RRC Radio Resource Control
  • the DL signal may include a reference signal.
  • Channels used for transmitting DL signals include, for example, data channels and control channels.
  • the data channel may include a PDSCH (Physical Downlink Shared Channel)
  • the control channel may include a PDCCH (Physical Downlink Control Channel).
  • the base station 10 transmits control information to the terminal 20 using the PDCCH, and transmits downlink data signals using the PDSCH.
  • reference signals included in DL signals include demodulation reference signals (DMRS), phase tracking reference signals (PTRS), channel state information-reference signals (CSI-RS), sounding reference signals (SRS ), and Positioning Reference Signal (PRS) for position information.
  • DMRS demodulation reference signals
  • PTRS phase tracking reference signals
  • CSI-RS channel state information-reference signals
  • SRS sounding reference signals
  • PRS Positioning Reference Signal
  • reference signals such as DMRS and PTRS are used for demodulation of downlink data signals and transmitted using PDSCH.
  • the receiving unit 102 receives an uplink (UL) signal transmitted from the terminal 20 .
  • the receiver 102 receives UL signals under the control of the controller 103 .
  • the control unit 103 controls the communication operation of the base station 10, including the transmission processing of the transmission unit 101 and the reception processing of the reception unit 102.
  • control unit 103 acquires information such as data and control information from the upper layer and outputs it to the transmission unit 101 .
  • Control section 103 also outputs the data received from receiving section 102, control information, and the like to an upper layer.
  • control unit 103 based on the signal received from the terminal 20 (e.g., data and control information, etc.) and / or data and control information obtained from the upper layer, resource (or channel) used for transmission and reception of the DL signal and/or allocates resources used for transmission and reception of UL signals. Information about the allocated resources may be included in control information to be transmitted to the terminal 20 .
  • the control unit 103 sets PUCCH resources as an example of allocation of resources used for transmission and reception of UL signals.
  • Information on PUCCH configuration may be notified to terminal 20 by RRC.
  • FIG. 4 is a block diagram showing an example of the configuration of terminal 20 according to this embodiment.
  • Terminal 20 includes, for example, receiver 201 , transmitter 202 , and controller 203 .
  • the terminal 20 communicates with the base station 10 by radio, for example.
  • the receiving unit 201 receives the DL signal transmitted from the base station 10. For example, the receiver 201 receives a DL signal under the control of the controller 203 .
  • the transmission unit 202 transmits the UL signal to the base station 10.
  • the transmitter 202 transmits UL signals under the control of the controller 203 .
  • the UL signal may include, for example, an uplink data signal and control information (eg, UCI).
  • control information eg, UCI
  • information about the processing capability of terminal 20 eg, UE capability
  • the UL signal may include a reference signal.
  • Channels used to transmit UL signals include, for example, data channels and control channels.
  • the data channel includes PUSCH (Physical Uplink Shared Channel)
  • the control channel includes PUCCH (Physical Uplink Control Channel).
  • the terminal 20 receives control information from the base station 10 using PUCCH, and transmits uplink data signals using PUSCH.
  • the reference signal included in the UL signal may include at least one of DMRS, PTRS, CSI-RS, SRS, and PRS, for example.
  • reference signals such as DMRS and PTRS are used for demodulation of uplink data signals and transmitted using an uplink channel (eg, PUSCH).
  • the control unit 203 controls communication operations of the terminal 20, including reception processing in the reception unit 201 and transmission processing in the transmission unit 202.
  • control unit 203 acquires information such as data and control information from the upper layer and outputs it to the transmission unit 202 . Also, the control unit 203 outputs, for example, the data and control information received from the receiving unit 201 to the upper layer.
  • control unit 203 controls transmission of information to be fed back to the base station 10 .
  • Information fed back to the base station 10 may include, for example, HARQ-ACK, channel state information (CSI), or scheduling request (SR). good.
  • Information to be fed back to the base station 10 may be included in the UCI.
  • UCI is transmitted on PUCCH resources.
  • the control unit 203 configures PUCCH resources based on configuration information received from the base station 10 (for example, configuration information and/or DCI notified by RRC). Control section 203 determines PUCCH resources to be used for transmitting information to be fed back to base station 10 . Under the control of control section 203 , transmission section 202 transmits information to be fed back to base station 10 on PUCCH resources determined by control section 203 .
  • the channels used for DL signal transmission and the channels used for UL signal transmission are not limited to the above examples.
  • the channel used for DL signal transmission and the channel used for UL signal transmission may include RACH (Random Access Channel) and PBCH (Physical Broadcast Channel).
  • RACH may be used, for example, to transmit Downlink Control Information (DCI) containing Random Access Radio Network Temporary Identifier (RA-RNTI).
  • DCI Downlink Control Information
  • RA-RNTI Random Access Radio Network Temporary Identifier
  • PUCCH-Config configuration information related to an uplink control channel (for example, PUCCH) is described as "PUCCH-Config".
  • PUCCH uplink control channel
  • PUCCH-Config configuration information related to an uplink control channel
  • the method of setting the priority of PUCCH-Config may be defined according to the number of PUCCH-Configs.
  • ⁇ Option 1 for setting the number of PUCCH-Config> For example, in option 1, the number of PUCCH-Config in PUCCH Scell is set to the same number as the number of PUCCH-Config in Pcell or PScell.
  • Pcell or PScell may be described as "Pcell/PScell.” Also, hereinafter, Pcell may be replaced with "PScell”.
  • two PUCCH-Configs are set for Pcell/PScell, two PUCCH-Configs are also set for Scell. Also, when one PUCCH-Config is set for Pcell/PScell, one PUCCH-Config is also set for Scell.
  • priority determination example 1 An example of PUCCH resource priority determination in PUCCH-Config when option 1 for setting the number of PUCCH-Configs is applied (hereinafter referred to as priority determination example 1) will be explained.
  • Example 1 of priority determination the same rule as Rel-16 is applied to the priority determination rule of PUCCH resources.
  • the PUCCH resource prioritization rule may be the rule described in section 9 of 3GPP TS 38.213 V16.6.0 (2021-06).
  • the priority of PUCCH resources may follow the HARQ-ACK codebook.
  • the first PUCCH-Config is for low priority (i.e., priority index 0) and the second PUCCH-Config is for high priority. for priority (i.e. priority index 1).
  • the configured PUCCH-Config is for low priority (that is, priority index 0).
  • FIG. 5 is a diagram showing an example 1 of priority determination.
  • FIG. 5 shows a Pcell and two Scells, Scell#1 and Scell#2. Then, in the example of FIG. 5, Option 1 for setting the number of PUCCH-Configs is applied, and two PUCCH-Configs are set for each cell.
  • PUCCH-Config#1 of each cell is for low priority (i.e. priority index 0) and PUCCH-Config#2 of each cell is for high priority (i.e. priority index 1). is for
  • a consistent PUCCH resource priority can be set in each of the possible PUCCH cells, so a simple setting can be performed. Also, since there is no need to indicate priority to PUCCH-Config of each cell, RRC signaling overhead can be reduced.
  • Subslot length of PUCCH-Config ⁇ Subslot length of PUCCH-Config>
  • the above-described priority determination example 1 may be applied, and the length of the sub-slot (sub-slot length) according to the priority may be set for the determined priority.
  • the subslot length any of the following "Alt 1" and "Alt 2" settings may be applied.
  • the set subslot lengths are the same.
  • the PUCCH-related settings for example, PUCCH-config
  • the PUCCH-related settings with the same priority may be controlled to set the same value as the sub-slot length.
  • the subslot length may be set based on information received from the base station (for example, subslotLengthForPUCCH-r16 of PUCCH-config). Also, a common value may be set based on a predetermined constraint.
  • the set subslot lengths may be the same or different.
  • the PUCCH-related settings for example, PUCCH-config
  • the PUCCH-related settings with the same priority are controlled to set the same value or different values as the sub-slot length. good too.
  • the subslot length is based on the information received from the base station (for example, subslotLengthForPUCCH-r16 of PUCCH-config)), even if it is set independently for each PUCCH setting (for example, PUCCH-Config) good.
  • the number of PUCCH-Configs in PUCCH Scell may be the same as or different from the number of PUCCH-Configs in Pcell/PScell.
  • the number of PUCCH-Configs in PUCCH Scell and the number of PUCCH-Configs in Pcell/PScell are set respectively.
  • a condition for limiting the number of PUCCH-Configs may be set.
  • the number of PUCCH-Configs that satisfy this limit is set. For example, when two PUCCH-Configs are configured for Pcell/PScell, one PUCCH-Config is configured for Scell.
  • the PUCCH-Config number limit described above is not set, the PUCCH-Config number is set regardless of this limit. For example, when one PUCCH-Config is set to Pcell/PScell, two PUCCH-Config may be set to Scell, one PUCCH-Config may be set, or PUCCH-Config may not be set.
  • the limitation on the number of PUCCH-Configs described above is an example, and the present disclosure is not limited to this.
  • the number of PUCCH-Config in Pcell/PScell may be restricted to be less than the number of PUCCH-Config in Scell, or the number of PUCCH-Config in Pcell/PScell must be A limit may be provided that is equal to the number of .
  • the restriction is set that the number of PUCCH-Configs in Pcell/PScell is the same as the number of PUCCH-Configs in Scell, it is similar to option 1 of setting the number of PUCCH-Configs described above. may be interpreted as
  • priority determination example 2 an example of PUCCH resource priority determination in PUCCH-Config when option 2 for setting the number of PUCCH-Configs is applied.
  • Alt. 1 A parameter indicating the priority of PUCCH resources in PUCCH-Config is introduced into PUCCH-Config.
  • the parameter indicating the priority of PUCCH resources may be called "PriorityIndexConfig", or may be called another name.
  • the parameter indicating the priority of PUCCH resources is an example of a higher layer parameter, and may indicate the priority of PUCCH-Config.
  • FIG. 6 is a diagram showing an example of Alt.1 in Example 2 of Priority Determination.
  • FIG. 6 shows a Pcell and two Scells, Scell#1 and Scell#2. Then, in the example of FIG. 6, in Pcell, PUCCH-Config#1 with a priority index set to 0 (priority index 0) and PUCCH-Config#1 with a priority index set to 1 (priority index 1) Config#2 is set. Also, in Scell#1, PUCCH-Config#1 with a priority index set to 1 (priority index 1) is set, and in Scell#2, a priority index is set to 0 (priority index 0). PUCCH-Config#2 is set.
  • a parameter indicating the priority of PUCCH resources introduced in PUCCH-Config may indicate the priority of each PUCCH-Config.
  • a parameter indicating the priority of PUCCH resources may or may not exist.
  • two PUCCH-Config are set in Pcell, so in this case, parameters indicating the priority of PUCCH resources may or may not exist.
  • the priority of PUCCH-Config is (always) low priority. Note that the case where one PUCCH-Config is set and two are not set may correspond to the case where "PUCCH-ConfigurationList" is not set.
  • PUCCH carrier switching is supported for high priority PUCCH even if one PUCCH-Config is configured and not two or more. . Therefore, in "Alt. 1", by introducing a parameter that indicates the priority of PUCCH-Config, even if one PUCCH-Config is set and not two or more Can be set to high priority. If PUCCH carrier switching is supported for high priority PUCCH, 'Alt. Can be set.
  • the priority of PUCCH-Config#1 of Scell#1 in the example of FIG. 6 is set to low priority (eg, priority index 0).
  • priority index 0 priority index 1
  • the first PUCCH-Config is configured with low priority (i.e., priority index 0) and the second PUCCH-Config with high priority. degree (i.e. priority index 1).
  • the second PUCCH-Config is set to low priority (i.e., priority index 0)
  • the first PUCCH- Config is set to high priority (i.e. priority index 1).
  • FIG. 7 is a diagram showing an example of Alt.2 in Priority Determination Example 2.
  • FIG. 7 shows a Pcell and two Scells, Scell#1 and Scell#2.
  • the first PUCCH-Config is set to low priority (i.e., priority index 0)
  • the second PUCCH-Config is set to high priority (ie priority index 1).
  • the PUCCH-Config priority may be based on the following options.
  • Option 1 Determined by the default priority (for example, priority index 0 or priority index 1).
  • the default priority of one PUCCH-Config in Pcell/PScell is priority index 0 (low priority), and the default priority of one PUCCH-Config in Scell is priority index 1 (high priority ).
  • the default priority may differ from cell to cell.
  • the priority index of PUCCH-Config#1 is set to 0 (priority index 0) according to the above option 1 rule. Also, in Scell#1, PUCCH-Config#1 is set to have a priority index of 1 (priority index 1) according to the rule of option 1 above.
  • Option 2 Any priority is selected.
  • the actual priority of PUCCH transmission in the PUCCH resource of PUCCH-Config is determined by one or both of the UCI priority and UCI type included in the PUCCH. For example, for a PUCCH resource of PUCCH-Config in a cell, if a high priority UCI is transmitted or switched, the PUCCH is high priority. Also, PUCCH is low priority if low priority UCI is transmitted or switched for PUCCH resources of PUCCH-Config in a cell.
  • Subslot length of PUCCH-Config> the above-described priority determination example 2 may be applied, and the length of the sub-slot (sub-slot length) according to the priority may be set for the determined priority. For example, for the subslot length, any of the following "Alt 1" and "Alt 2" settings may be applied.
  • Alt 2 When PUCCH-Configs with the same priority are set for different cells, the set subslot lengths may be the same or different.
  • FIG. 8 is a diagram showing an example of the relationship between priority and carrier switching.
  • FIG. 8 shows a Pcell and two Scells, Scell#1 and Scell#2.
  • two PUCCH-Configs are set for Pcell and Scell#2, and one PUCCH-Config is set for Scell#1.
  • PUCCH-Config#1 in Pcell is low priority (LP) and PUCCH-Config#2 is high priority (High Priority (HP)).
  • PUCCH-Config#1 in Scell#2 is Low Priority (LP) and PUCCH-Config#2 is High Priority (HP).
  • PUCCH-Config#1 in Scell#1 is High Priority (HP).
  • Scell#1 does not have a low priority PUCCH-Config set.
  • carrier switching is not supported for low priority PUCCH.
  • carrier switching to Scell#1 with no low-priority PUCCH-Config configured is not supported for low-priority PUCCH.
  • the priority of PUCCH-Configs may be determined according to the number of PUCCH-Configs.
  • the terminal 20 determines the priority of PUCCH-Config for each of a plurality of cells (eg, Pcell/PScell and Scell), and may set PUCCH resources for transmitting UCI according to the priority. .
  • the priority it is possible to set an appropriate priority in PUCCH-Config and appropriately set the resources used for transmitting information fed back from the terminal to the base station.
  • PUCCH resource configuration in different cells for corresponding priority there are various types of PUCCH resources.
  • the following describes PUCCH resource configuration related to PUCCH resource types. Two options are described below.
  • the PUCCH resource type set in Scell matches the corresponding priority PUCCH resource type set in Pcell/PScell.
  • the PUCCH resource type is one or more of dynamic HARQ-ACK, SPS HARQ-ACK, SR resource and CSI resource.
  • FIG. 9 is a diagram showing an example of configuration of option 1 of the PUCCH resource type in each cell.
  • FIG. 9 shows Pcell and Scell#1.
  • a low priority (Low Priority (LP)) PUCCH-Config and a high priority (High Priority (HP)) PUCCH-Config are set for each of Pcell and Scell#1. be.
  • the UCI types of the low-priority PUCCH-Config of Pcell and Scell#1 are "Dynamic HARQ-ACK resource(s)", “SPS HARQ-ACK resource(s)”, “SR resource( s)” and “CSI resource(s)”. Note that SPS is an abbreviation for semi-persistent scheduling.
  • the UCI types of high-priority PUCCH-Config for Pcell and Scell#1 are "Dynamic HARQ-ACK resource(s)", “SPS HARQ-ACK resource(s)", and "SR resource(s)”. be.
  • the UCI types of the low and high priority PUCCH-Configs of Pcell match the UCI types of the low and high priority PUCCH-Configs of Scell#1, respectively.
  • the PUCCH resource type configured in the Scell may or may not match the corresponding priority PUCCH resource type configured in the Pcell/PScell.
  • FIG. 10 is a diagram showing an example of configuration of option 2 of the PUCCH resource type in each cell.
  • FIG. 10 shows Pcell, Scell#1, and Scell#2.
  • PUCCH-Config with low priority Low Priority (LP)
  • PUCCH-Config with high priority High Priority (HP)
  • the UCI types of the low-priority PUCCH-Config of Pcell and Scell#2 are "Dynamic HARQ-ACK resource(s)", “SPS HARQ-ACK resource(s)”, “SR resource( s)” and “CSI resource(s)”. Note that SPS is an abbreviation for semi-persistent scheduling.
  • the UCI types of high-priority PUCCH-Config for Pcell and Scell#2 are "Dynamic HARQ-ACK resource(s)", “SPS HARQ-ACK resource(s)", and "SR resource(s)”. be. In the example of FIG.
  • the UCI types of the low-priority and high-priority PUCCH-Configs of Pcell match the UCI types of the low-priority and high-priority PUCCH-Configs of Scell#2, respectively.
  • the UCI types of the low-priority and high-priority PUCCH-Config of Pcell do not match the UCI types of the low-priority and high-priority PUCCH-Config of Scell#1, respectively.
  • any of the following may be implied. - Carrier switching is not supported for PUCCH of that particular UCI type and/or that priority. • Carrier switching to that Scell is not supported for PUCCH of that particular UCI type and/or that priority.
  • the UCI types "SPS HARQ-ACK resource(s)", “SR resource(s)” and “CSI resource(s)” are the low priority PUCCH-Config in Pcell and Scell#2. but not in the low-priority PUCCH-Config in Scell#1.
  • carrier switching is supported for low priority PUCCHs of UCI types "SPS HARQ-ACK resource(s)", “SR resource(s)” and “CSI resource(s)”.
  • the Scell for which the UCI types "SPS HARQ-ACK resource(s)", “SR resource(s)” and “CSI resource(s)” are not configured in the low-priority PUCCH-Config Carrier switch to #1 is not supported for low priority PUCCH with UCI types "SPS HARQ-ACK resource(s)", “SR resource(s)” and “CSI resource(s)” , may be implied.
  • Scell # Switching to 2 may be possible.
  • Implicit support for carrier switching allows, for example, to imply that PUCCH carrier switching is supported for a particular UCI type and/or priority without unnecessary configuration, reducing RRC signaling overhead. can be reduced.
  • FIG. 11 is a diagram showing an example of PUCCH-Config.
  • PUCCH-Config allows configuration of resources for dynamic HARQ-ACK, SPS HARQ-ACK, SR (and CSI resources for multiple CSI reports).
  • PUCCH-CSI-Resource Information (for example, parameters) included in information referred to as "PUCCH-CSI-Resource" may be used to configure the CSI PUCCH resource in the Scell.
  • FIG. 12 is a diagram showing an example of PUCCH-CSI-Resource.
  • 'ServingCellId' included in 'PUCCH-CSI-Resource' may be used to configure CSI PUCCH resources in Scell, and other parameters may be used to configure CSI PUCCH resources in Scell. , may be used.
  • CSI PUCCH resources may be regarded as PCell/PScell PUCCH resources by default.
  • the priority and/or UCI type of PUCCH resources configured in each cell are defined by the relationship between cells.
  • the priority and/or UCI type of PUCCH resources can be set appropriately, and the resources used for transmitting information fed back from the terminal to the base station can be set appropriately.
  • FIG. 13 is a diagram showing an example of priority discrepancies regarding the configuration of PUCCH resources in PUCCH cells.
  • FIG. 13 shows Pcell and Scell#1. Then, in the example of FIG. 13, a low priority (Low Priority (LP)) PUCCH-Config and a high priority (High Priority (HP)) PUCCH-Config are set for the Pcell. High Priority (HP) PUCCH-Config is set for Scell#1.
  • LP Low Priority
  • HP High Priority
  • FIG. 14 is a diagram showing an example of UCI type mismatch with respect to PUCCH resource configuration in a PUCCH cell.
  • FIG. 14 shows Pcell and Scell#1.
  • a low priority (Low Priority (LP)) PUCCH-Config and a high priority (High Priority (HP)) PUCCH-Config are set for each of Pcell and Scell#1.
  • the UCI types of the low-priority PUCCH-Config of Pcell are "PUCCH-ResourceSet", "sps-PUCCH-AN-List", "schedulingRequestResourceToAddModList” and "multi-CSI-PUCCH-ResourceList". be.
  • FIG. 14 shows Pcell and Scell#1.
  • LP Low Priority
  • HP High Priority
  • the UCI types of the high-priority PUCCH-Config of Pcell are "PUCCH-ResourceSet", “sps-PUCCH-AN-List” and "schedulingRequestResourceToAddModList”.
  • the UCI type of PUCCH-Config of low priority and high priority of Scell#1 is "PUCCH-ResourceSet”.
  • UCI types with the same priority in different cells are different from each other.
  • SPS HARQ-ACK resource in PUCCH-Config with priority index 1 of Scell#1 is An event that is not set may occur.
  • the SPS HARQ-ACK resource may be a resource whose UCI type is "sps-PUCCH-AN-List".
  • Opt.1 to Opt.6 operations may be taken.
  • Option 1 Treat as an error.
  • Opt. 2 Do not switch PUCCH for priority and/or UCI type PUCCH.
  • Option 3 PUCCH is transmitted in Pcell/PScell when UCI type or priority PUCCH resource is configured in Pcell/PScell.
  • Opt. 4 PUCCH is not transmitted in any cell.
  • Opt. 5 UE behavior depends on PUCCH transmission of the same UCI type with different priorities in PUCCH resources or Scells.
  • Opt. 6 UE behavior depends on PUCCH resources or resources for PUCCH transmissions of different UCI types with the same priority.
  • the PUCCH resource is configured in the Scell with the same UCI type as the PUCCH determined to be switched in the Scell, but the priority of the PUCCH resource is the priority of the PUCCH determined to be switched in the Scell A case where is different from is explained.
  • the operation may differ depending on each of the following two cases.
  • PUCCH is transmitted on PUCCH resources of the same UCI type with different priorities in the Scell in case 2, where PUCCH transmission with the same UCI type and different priorities is not actually performed in the Scell.
  • the PUCCH resource is set in the Scell with the same UCI type as the PUCCH determined to be switched in the Scell, but the priority of the PUCCH resource is the priority of the PUCCH determined to be switched in the Scell If it is not a different case, eg, neither Case 1 nor Case 2, then Opt. 1/2/3/4/6 operations are possible.
  • Fig. 15 is a diagram showing an example of Opt. 5 regarding priority or UCI type mismatch.
  • FIG. 15 shows Pcell and Scell#1.
  • a low priority (Low Priority (LP)) PUCCH-Config and a high priority (High Priority (HP)) PUCCH-Config are set for each of Pcell and Scell#1.
  • the UCI types of the low-priority PUCCH-Config of Pcell are "PUCCH-ResourceSet", "sps-PUCCH-AN-List", "schedulingRequestResourceToAddModList” and "multi-CSI-PUCCH-ResourceList". be.
  • FIG. 15 shows Pcell and Scell#1.
  • a low priority (Low Priority (LP)) PUCCH-Config and a high priority (High Priority (HP) PUCCH-Config are set for each of Pcell and Scell#1.
  • the UCI types of the low-priority PUCCH-Config of Pcell are "PU
  • the UCI types of the high-priority PUCCH-Config of Pcell are "PUCCH-ResourceSet", “sps-PUCCH-AN-List” and "schedulingRequestResourceToAddModList”.
  • the UCI type of the low-priority PUCCH-Config of Scell#1 is "PUCCH-ResourceSet”.
  • the UCI types of the high-priority PUCCH-Config of Scell#1 are "PUCCH-ResourceSet", “sps-PUCCH-AN-List” and "schedulingRequestResourceToAddModList".
  • the low priority UCI types of different cells are different from each other.
  • Alt1 Low-priority SPS HARQ-ACK may be multiplexed with high-priority SPS HARQ-ACK and sent in sps-PUCCH-AN-List of PUCCH-Config for high-priority of Scell#1. good.
  • Alt2 Actions such as Opt. 1/2/3/4/6 above may be performed.
  • UE behavior depends on PUCCH resources or resources of PUCCH transmissions of different UCI types with the same priority.
  • the operation may differ depending on each of the following two cases.
  • Case 1 In Case 1, when PUCCH resources of other specific UCI type(s) with the same priority are configured in the Scell, and PUCCH transmissions of other specific UCI types with the same priority actually occur in the Scell, Either of the following "Alt.1" and "Alt.2" may be applied.
  • Alt 1 UCIs with a specific UCI type are multiplexed and transmitted on PUCCH resources configured according to priority.
  • Alt2 Operation like Opt. 1/2/3/4/5 is possible.
  • the priority or UCI type PUCCH resources may be configured based on whichever is more likely. For example, PUCCH carrier switching may be performed based on PUCCH transmissions or PUCCH resources of the same UCI type if the priorities are different. Also, for example, PUCCH carrier switching may be performed based on PUCCH transmissions or PUCCH resources with the same priority when UCI types are different. Switching PUCCH carriers may be regarded as newly configuring PUCCH resources.
  • Periodic/semi-static PUCCH report configuration A Periodic/semi-static PUCCH report configuration is described below. For example, when UCI-type PUCCH resources (eg, SR resources and/or CSI resources) corresponding to one or more Scells are configured, either of the following two options may be applied.
  • UCI-type PUCCH resources eg, SR resources and/or CSI resources
  • periodic or semi-static PUCCH transmission (such as SR or CSI reporting) may be based on Pcell/PScell.
  • periodic or semi-static PUCCH transmissions (such as SR or CSI reports) may not be based on Scell.
  • PUCCH resources eg, SR resources, CIS resources, etc.
  • SR resources SR resources, CIS resources, etc.
  • CIS resources CIS resources, etc.
  • PUCCH resources eg, SR resources, CIS resources, etc.
  • it is used for semi-static PUCCH transmission switched from Pcell/PScell by carrier switching. Two examples are given below.
  • SR PUCCH is generated for SR resources in Pcell/PScell.
  • no SR PUCCH is generated for SR resources in Scell.
  • the PUCCH resource selected from the SR resource ("schedulingRequestResourceToAddModList") set in Scell is used for SR PUCCH transmission used for
  • Example 2 of Option 1 An example of a CSI report when the pucch-CSI-ResourceList of CSI-ReportConfig includes PUCCH resources for Pcell/PScell and Scell is given.
  • the Pcell/PScell CSI report is active or activated. In other words, Scell's CSI reporting is not active in this example. Then, when it is determined that the CSI PUCCH in Pcell/PScell is switched to Scell according to the semi-static PUCCH carrier pattern, the PUCCH resource selected from the CSI resources configured in Scell is used for CSI PUCCH transmission. be.
  • FIG. 16 is a diagram showing an example 1 of PUCCH report settings.
  • the horizontal axis of FIG. 16 is, for example, the time axis.
  • FIG. 16 shows an example of arrangement of SR resources for Pcell/PScell and Scell.
  • one section aligned in the time axis direction may be a "slot", a "sub-slot", or any other time section.
  • SR PUCCH is not generated (SR PUCCH is not transmitted) in the SR resource set in Scell.
  • SR resources configured in Scell are used when SR PUCCH in a certain cell (eg, Pcell/PScell) switches to Scell.
  • periodic or semi-static PUCCH transmission may be based on Pcell/PScell and Scell. Two examples are given below.
  • SR PUCCH is generated in Pcell/PScell and Scell. Then, when SR PUCCHs overlap between different cells, one SR PUCCH is transmitted in one cell. In this case, SR PUCCH may not be transmitted in other cells.
  • the cell used for SR PUCCH transmission is determined by the PUCCH carrier pattern.
  • SR PUCCH is transmitted in one of the SR PUCCH cells. Which cell it is transmitted on may be determined by, for example, the cell index, or the end/start symbol of the SR PUCCH, the length of the SR PUCCH. Note that the case where the SR PUCCH is not enabled may correspond to the case where the SR PUCCH is disabled. Also, the length of SR PUCCH may correspond to the symbol length for transmitting the PUCCH.
  • Example 2 of option 2 An example of a CSI report when pucch-CSI-ResourceList of CSI-ReportConfig includes PUCCH resources for Pcell/PScell and Scell is given.
  • CSI PUCCH is generated in Pcell/PScell and Scell. Then, when CSI PUCCHs overlap between different cells, either of the following "Alt.1" and “Alt.2" operations are performed.
  • Alt. 2 One CSI PUCCH out of multiple CSI PUCCHs may be transmitted, and the other CSI PUCCHs may be cancelled. Which CSI PUCCH to transmit may then be determined by, for example, CSI report prioritization defined in TS38.214. Alternatively, which CSI PUCCH to transmit may be determined based on the cell index of the CSI PUCCH and the end/start symbols of the CSI PUCCH. Alternatively, which CSI PUCCH to transmit may be determined based on the length of the CSI PUCCH.
  • FIG. 17 is a diagram showing example 2 of PUCCH report settings.
  • the horizontal axis in FIG. 17 is, for example, the time axis.
  • FIG. 17 shows an example of arrangement of SR resources for Pcell/PScell and Scell.
  • one section aligned in the time axis direction may be a "slot", a "sub-slot", or any other time section.
  • SR PUCCH may be generated (SR PUCCH may be transmitted) in SR resources configured in Scell. However, as shown in FIG. 17, one SR PUCCH is transmitted when multiple SR PUCCHs overlap between Pcell/PScell and Scell.
  • PUCCH resources used for PUCCH reporting multiple cells (for example, Pcell / PScell and Scell) based on the UCI type relationship between PUCCH Configure resources for reporting.
  • the terminal 20 configures resources used for PUCCH reporting based on the UCI type relationship between multiple cells (eg, Pcell/PScell and Scell). For example, in each of Pcell / PScell and Scell, when SR resources and / or CSI report resources are configured, Pcell / PScell SR resources and / or CSI report resources are used for PUCCH reporting, Scell The resource may be used for PUCCH carrier switching.
  • the SR resources and / or CSI report resources of each of Pcell / PScell and Scell are used for PUCCH reporting may With such resource configuration for PUCCH reporting, it is possible to appropriately configure resources for PUCCH reporting, and to appropriately configure resources used for transmitting information fed back from a terminal to a base station.
  • any one of multiple options is applied for one setting, and/or one of multiple options (Alt. 1, Alt. 2, etc. in the above description) is applied for one setting.
  • shown to be For example, which of multiple options applies and/or which of multiple options (in the above, Alt. 1, Alt. 2, etc.) applies is determined in the following manner: good.
  • Set by upper layer parameters - The UE reports as UE capability(ies). - Described in the specifications. • Determined based on higher layer parameter settings and reported UE capabilities. • Determined by a combination of two or more of the above determinations.
  • the upper layer parameters may be RRC parameters, MAC CE (Media Access Control Element), or a combination thereof.
  • the UE capability indicating the capability of the UE may include information indicating the following capabilities of the UE. Note that the information indicating the capabilities of the UE may correspond to information defining the capabilities of the UE. - Information defining whether the UE supports PUCCH carrier switching or not. - Information defining whether the UE supports the same and/or different number of PUCCH-Configs in Scell and Pcell/PScell.
  • each functional block may be implemented using one device that is physically or logically coupled, or directly or indirectly using two or more devices that are physically or logically separated (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.
  • a base station, a terminal, etc. may function as a computer that performs processing of the wireless communication method of the present disclosure.
  • FIG. 18 is a diagram illustrating an example of hardware configurations of a base station and a terminal according to an embodiment of the present disclosure;
  • the base station 10 and terminal 20 described above may be physically 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 base station 10 and terminal 20 may be configured to include one or more of each device shown in the figure, or may be configured without some devices.
  • Each function of the base station 10 and the terminal 20 is performed by the processor 1001 by loading predetermined software (program) onto hardware such as the processor 1001 and the memory 1002, and the processor 1001 performs calculations and controls communication by the communication device 1004. , and controlling at least one of reading and writing of data in the memory 1002 and the storage 1003 .
  • the processor 1001 for example, operates an operating system and controls the entire computer.
  • the processor 1001 may be configured by a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic device, registers, and the like.
  • CPU central processing unit
  • the control unit 103 and the control unit 203 described above may be implemented by the processor 1001 .
  • 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 program a program that causes a computer to execute at least part of the operations described in the above embodiments is used.
  • the control unit 103 of the base station 10 or the control unit 203 of the terminal 20 may be implemented by a control program stored in the memory 1002 and operating in the processor 1001, and other functional blocks may be implemented in the same way. good.
  • FIG. 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, for example, ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), etc. may be
  • ROM Read Only Memory
  • EPROM Erasable Programmable ROM
  • EEPROM Electrical 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 executable programs (program code), software modules, etc. for implementing a wireless communication 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 CD-ROM (Compact Disc 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 called an auxiliary storage device.
  • the storage 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, a duplexer, a filter, a frequency synthesizer, etc., in order to realize at least one of, for example, frequency division duplex (FDD) and time division duplex (TDD). may consist of For example, the transmitting unit 101, the receiving unit 102, the receiving unit 201, the transmitting unit 202, etc. described above may be realized by the communication device 1004.
  • 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 base station 10 and the terminal 20 include hardware such as microprocessors, digital signal processors (DSPs), ASICs (Application Specific Integrated Circuits), PLDs (Programmable Logic Devices), and FPGAs (Field Programmable Gate Arrays). , and part or all of each functional block may be implemented by the hardware.
  • processor 1001 may be implemented using at least one of these pieces of hardware.
  • notification of information includes physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), higher layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling, It may be implemented by broadcast information (MIB (Master Information Block), SIB (System Information Block)), other signals, or a combination thereof.
  • RRC signaling may also be called an RRC message, and may be, for example, an RRC connection setup message, an RRC connection reconfiguration message, or the like.
  • Each aspect/embodiment described in the present disclosure includes LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), FRA (Future Radio Access), NR (New Radio), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark) )), IEEE 802.16 (WiMAX®), IEEE 802.20, UWB (Ultra-WideBand), Bluetooth®, and other suitable systems and extended It may be applied to at least one of the next generation systems. Also, a plurality of systems may be applied in combination (for example, a combination of at least one of LTE and LTE-A and 5G, etc.).
  • Base station operation Certain operations that are described in this disclosure as being performed by a base station may also 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. (including but not limited to).
  • MME or S-GW network nodes other than the base station
  • 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).
  • (input/output direction) Information and the like can be output from the upper layer (or lower layer) to the lower layer (or higher layer). It may be input and output via multiple network nodes.
  • Input/output information and the like may be stored in a specific location (for example, memory), or may be managed using a management table. Input/output information and the like can be overwritten, updated, or appended. The output information and the like may be deleted. The entered information and the like may be transmitted to another device.
  • 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).
  • 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 at least one of wired technology (coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), etc.) and wireless technology (infrared, microwave, etc.) to website, 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.
  • Information, signal Information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies.
  • 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 As used in this disclosure, the terms “system” and “network” are used interchangeably.
  • radio resources may be indexed.
  • Base station wireless base station
  • base station radio base station
  • 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.
  • the overall coverage area of the base station can be partitioned into multiple smaller areas, each smaller area being associated with a base station subsystem (e.g., an indoor small base station (RRH: Communication services can also be provided by Remote Radio Head)).
  • RRH indoor small base station
  • the terms "cell” or “sector” refer to part or all of the coverage area of at least one of the base stations and base station subsystems that serve communication within such coverage.
  • terminal In this disclosure, terms such as “Mobile Station (MS),” “user terminal,” “User Equipment (UE),” “terminal,” etc. may be used interchangeably. .
  • 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 a base station and a mobile station may be called a transmitter, a receiver, a communication device, and 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 object may be a vehicle (e.g., car, airplane, etc.), an unmanned mobile object (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 the mobile station may be an IoT (Internet of Things) device such as a sensor.
  • IoT Internet of Things
  • the base station in the present disclosure may be read as a user terminal.
  • communication between a base station and a user terminal is replaced with communication between multiple user terminals (for example, D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.)
  • the terminal 20 may have the functions of the base station 10 described above.
  • 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 terminal in the present disclosure may be read as a base station.
  • the base station 10 may have the functions of the terminal 20 described above.
  • determining may encompass a wide variety of actions.
  • “Judgement”, “determining” 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.
  • 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 optical (both visible and invisible) regions, and the like.
  • the reference signal may be abbreviated as RS (Reference Signal), or may be referred to as Pilot according to the applicable standard.
  • 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 configuration, 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
  • radio frame configuration for example, 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 (OFDM (Orthogonal Frequency Division Multiplexing) symbol, SC-FDMA (Single Carrier Frequency Division Multiple Access) symbol, etc.) in the time domain.
  • 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.
  • PDSCH (or PUSCH) transmitted in time units larger than minislots 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
  • TTI Transmission Time Interval
  • TTI Transmission Time Interval
  • one slot or one minislot may be called a TTI.
  • TTI Transmission Time Interval
  • at least one of the subframe and TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (eg, 1-13 symbols), or a period longer than 1 ms may be Note that the unit representing the TTI may be called a slot, mini-slot, 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
  • a TTI may be a transmission time unit such as a channel-encoded data packet (transport block), code block, or codeword, or may be a processing unit such as scheduling and link adaptation. 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 or more TTIs may be the minimum scheduling time unit. Also, the number of slots (the number of mini-slots) constituting the minimum time unit of the scheduling may be controlled.
  • a TTI having 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, or the like.
  • a TTI that is shorter than a normal TTI may be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a minislot, a subslot, a slot, and the like.
  • the long TTI (e.g., normal TTI, subframe, etc.) may be replaced with a TTI having a time length exceeding 1 ms
  • the short TTI e.g., shortened TTI, etc.
  • a TTI having the above TTI length may be read instead.
  • a resource block is a resource allocation unit in the time domain and the frequency domain, and may include one or more consecutive subcarriers in the frequency domain.
  • the number of subcarriers included in the RB may be the same regardless of the neumerology, eg twelve.
  • 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 (PRBs), sub-carrier groups (SCGs), resource element groups (REGs), PRB pairs, RB pairs, etc. may be called.
  • PRBs physical resource blocks
  • SCGs sub-carrier groups
  • REGs resource element groups
  • PRB pairs RB pairs, etc. may be called.
  • a resource block may be composed of one or more resource elements (RE: Resource Element).
  • RE Resource Element
  • 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 certain numerology in a certain 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.
  • the BWP may include a BWP for UL (UL BWP) and a BWP for DL (DL BWP).
  • UL BWP UL BWP
  • DL BWP DL BWP
  • One or multiple BWPs may be configured for a UE within one carrier.
  • 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 contained in a radio frame the number of slots per subframe or radio frame, the number of minislots contained within a slot, the number of symbols and RBs contained in a slot or minislot, the number of Configurations such as the number of subcarriers, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc.
  • CP cyclic prefix
  • 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.”
  • 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.
  • One aspect of the present disclosure is useful for mobile communication systems.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Le présent terminal comprend : une unité de commande pour déterminer la priorité d'informations de réglage concernant un ou plusieurs canaux de commande de liaison montante qui sont respectivement définis sur une pluralité de cellules, et définir une ressource pour transmettre des informations de commande conformément à la priorité ; et une unité de transmission pour transmettre les informations de commande dans la ressource définie.
PCT/JP2021/026709 2021-07-15 2021-07-15 Terminal et procédé de communication sans fil WO2023286260A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/JP2021/026709 WO2023286260A1 (fr) 2021-07-15 2021-07-15 Terminal et procédé de communication sans fil

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2021/026709 WO2023286260A1 (fr) 2021-07-15 2021-07-15 Terminal et procédé de communication sans fil

Publications (1)

Publication Number Publication Date
WO2023286260A1 true WO2023286260A1 (fr) 2023-01-19

Family

ID=84918808

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2021/026709 WO2023286260A1 (fr) 2021-07-15 2021-07-15 Terminal et procédé de communication sans fil

Country Status (1)

Country Link
WO (1) WO2023286260A1 (fr)

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
MODERATOR (NOKIA): "Final moderator summary on HARQ-ACK feedback enhancements for NR Rel-17 URLLC/IIoT", 3GPP DRAFT; R1-2106249, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20210519 - 20210527, 28 May 2021 (2021-05-28), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP052017048 *
MODERATOR (OPPO): "Summary#1 of R17 intra-UE Multiplexing/Prioritization", 3GPP DRAFT; R1-2103857, 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, 12 April 2021 (2021-04-12), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051995168 *

Similar Documents

Publication Publication Date Title
WO2020066025A1 (fr) Terminal d'utilisateur et procédé de communication sans fil
WO2023007565A1 (fr) Terminal et procédé de communication sans fil
WO2023013005A1 (fr) Terminal et procédé de communication sans fil
WO2023012914A1 (fr) Terminal et procédé de communication radio
WO2023021710A1 (fr) Terminal et procédé de communication sans fil
WO2022239082A1 (fr) Terminal et procédé de communication sans fil
WO2023286260A1 (fr) Terminal et procédé de communication sans fil
WO2023286262A1 (fr) Terminal et procédé de communication sans fil
WO2023286261A1 (fr) Terminal et procédé de communication sans fil
WO2023281608A1 (fr) Terminal et procédé de communication radio
WO2023017571A1 (fr) Terminal et procédé de communication sans fil
WO2023281677A1 (fr) Terminal et procédé de communication sans fil
WO2023012955A1 (fr) Terminal et procédé de communication sans fil
WO2023037479A1 (fr) Terminal et procédé de communication sans fil
WO2023012956A1 (fr) Terminal et procédé de communication sans fil
WO2023053393A1 (fr) Terminal et procédé de communication sans fil
WO2023017621A1 (fr) Terminal et procédé de communication sans fil
WO2023286259A1 (fr) Terminal et procédé de communication sans fil
WO2023053433A1 (fr) Terminal et procédé de communication
WO2023053434A1 (fr) Terminal et procédé de communication
WO2023021862A1 (fr) Terminal et procédé de communication radio
WO2023007564A1 (fr) Terminal et procédé de communication radio
WO2022220040A1 (fr) Terminal et procédé de communication
WO2023007563A1 (fr) Terminal et procédé de communication sans fil
WO2023053232A1 (fr) Terminal et procédé de communication sans fil

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: 21950197

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21950197

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: JP