WO2022224942A1 - Terminal, station de base et procédé de communication - Google Patents

Terminal, station de base et procédé de communication Download PDF

Info

Publication number
WO2022224942A1
WO2022224942A1 PCT/JP2022/018099 JP2022018099W WO2022224942A1 WO 2022224942 A1 WO2022224942 A1 WO 2022224942A1 JP 2022018099 W JP2022018099 W JP 2022018099W WO 2022224942 A1 WO2022224942 A1 WO 2022224942A1
Authority
WO
WIPO (PCT)
Prior art keywords
bwp
terminal
communication
initial
ulbwp
Prior art date
Application number
PCT/JP2022/018099
Other languages
English (en)
Japanese (ja)
Inventor
大輝 前本
治彦 曽我部
秀明 ▲高▼橋
Original Assignee
株式会社デンソー
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 株式会社デンソー filed Critical 株式会社デンソー
Publication of WO2022224942A1 publication Critical patent/WO2022224942A1/fr

Links

Images

Classifications

    • 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, base stations, and communication methods.
  • Non-Patent Document 1 In the Third Generation Partnership Project (3GPP), an international standardization organization, Long Term Evolution (LTE), which is the 3.9th generation Radio Access Technology (RAT), and LTE-Advanced, which is the 4th generation RAT As a successor, Release 15 of New Radio (NR), which is a fifth generation (5G) RAT, has been specified (for example, Non-Patent Document 1).
  • LTE Long Term Evolution
  • RAT Radio Access Technology
  • NR New Radio
  • 3GPP has started to study functions assuming a new terminal for IoT (Internet of things) that performs radio access using NR.
  • the new terminal is called a RedCap terminal, and is based on the premise that it communicates in a relatively narrow bandwidth such as 20 MHz or 50 MHz, instead of using all of the wide band supported by NR.
  • radio resources for transmitting synchronization signals and broadcast information called SSBs (Synchronization Signal Blocks) are set in some frequencies in the downlink, and the terminal 10 determines the reception quality of the cell. etc. are measured by measuring SSB.
  • NR defines a mechanism called BWP (BandWidth Part) that enables all or part of the bandwidth of the entire cell to be allocated to terminals.
  • BWP BandWidth Part
  • the SSB is also called an SS/PBCH block (Synchronization Signal/Physical Broadcast Channel Block).
  • the BWP set in the RedCap terminal is a band including SSB, but the BWP set in the RedCap terminal is concentrated in the band including SSB. Then, the band will be congested. Therefore, it is being considered to operate a RedCap terminal with a plurality of BWPs.
  • the initial BWP does not have terminal-specific settings, the current NR specifications only define a BWP switching method using an RRC message, which poses a problem of large signaling overhead.
  • One object of the present disclosure is to provide a terminal, a base station, and a wireless communication method that can reduce signaling overhead when switching between BWPs.
  • a terminal is a receiving unit that receives, from a base station, an RRC message that does not include terminal-specific control channel resource settings for an initial BWP and that is set for a specific terminal and includes communication BWP settings. and a control unit that switches between the initial BWP and the communication BWP as an active BWP based on a physical downlink control channel signal specifying either the initial BWP or the communication BWP. .
  • a terminal it is possible to provide a terminal, a base station, and a wireless communication method that can reduce signaling overhead when switching between BWPs.
  • FIG. 1 is a diagram showing an example of an outline of a wireless communication system according to this embodiment.
  • FIG. 2 is a diagram showing an example of BWP settings.
  • FIG. 3 is a diagram for explaining the BWP switching process.
  • FIG. 4 is a diagram for explaining information elements of SIB1 used to set the initial BWP.
  • FIG. 5 is a diagram for explaining information elements related to BWP settings in an RRC message.
  • FIG. 6 is a diagram for explaining two options regarding the BWP setting method.
  • FIG. 7 is a sequence diagram for explaining the operation of BWP switching.
  • FIG. 8 is a diagram for explaining an example of a problem in this embodiment.
  • FIG. 9 is a sequence diagram for explaining an example of the BWP switching process when the initial BWP and communication BWP are set.
  • FIG. 10 is a flow chart showing an example of a processing procedure when transmitting a scheduling request.
  • FIG. 11 is a flow chart showing an example of a processing procedure when executing a random access procedure.
  • FIG. 12 is a diagram showing an example of an RRC message for setting a BWP for communication.
  • FIG. 13 shows an example of specification change of TS38.321.
  • FIG. 14 is a sequence showing an example of BWP switching processing when the initial BWP is not set for each terminal.
  • FIG. 15 is a diagram showing a definition example of a BWP indicator.
  • FIG. 16 is a diagram illustrating an example of the hardware configuration of each device within the wireless communication system.
  • FIG. 17 is a diagram illustrating an example of a functional configuration of a terminal;
  • FIG. 18 is a diagram illustrating an example of a functional configuration of a base station;
  • FIG. 1 is a diagram showing an example of an outline of a wireless communication system according to this embodiment.
  • the wireless communication system 1 may include a terminal 10, a base station 20, and a core network 30.
  • the numbers of terminals 10 and base stations 20 shown in FIG. 1 are merely examples, and are not limited to the numbers shown.
  • RAT radio access technology
  • 6th generation or later RAT can be used.
  • the terminal 10 is, for example, a given terminal or device such as a smartphone, a personal computer, an in-vehicle terminal, an in-vehicle device, a stationary device, a telematics control unit (TCU), or the like.
  • Terminal 10 may also be called a User Equipment (UE), a Mobile Station (MS), a User Terminal, a Radio apparatus, a subscriber terminal, an access terminal, and so on.
  • the terminal 10 may be mobile or stationary.
  • the terminal 10 is configured to be able to communicate using, for example, NR as the RAT.
  • the base station 20 forms one or more cells C and communicates with the terminal 10 using the cell C.
  • Cell C may be interchangeably referred to as serving cell, carrier, component carrier (CC), and the like.
  • the base station 20 may configure one primary cell and one or more secondary cells for the terminal 10 for communication (also called carrier aggregation). That is, one or more cells C include at least primary cells and may include secondary cells.
  • Base station 20 includes gNodeB (gNB), en-gNB, Next Generation-Radio Access Network (NG-RAN) node, low-power node, Central Unit (CU), Distributed Unit (DU), gNB -DU, Remote Radio Head (RRH), Integrated Access and Backhaul/Backhauling (IAB) node, etc.
  • the base station 20 is not limited to one node, and may be composed of a plurality of nodes (for example, a combination of a lower node such as DU and an upper node such as CU).
  • the core network 30 is, for example, an NR-compatible core network (5G Core Network: 5GC), but is not limited to this.
  • a device on the core network 30 (hereinafter also referred to as “core network device”) performs mobility management such as paging and location registration of the terminal 10 .
  • a core network device may be connected to the base station 20 via a predetermined interface (eg, S1 or NG interface).
  • the core network device includes, for example, an Access and Mobility Management Function (AMF) that manages C-plane information (e.g., information related to access and mobility management), and a User that controls transmission of U-plane information (e.g., user data).
  • AMF Access and Mobility Management Function
  • UPF Plane Function
  • the terminal 10 receives downlink (DL) signals from the base station 20 and/or transmits uplink (UL) signals.
  • Terminal 10 may be configured with one or more carriers. Each carrier has a bandwidth of, for example, 5 MHz to 400 MHz.
  • One carrier may be configured with one or more bandwidth parts (BWP).
  • BWP bandwidth parts
  • a BWP has the bandwidth of at least a portion of a carrier. That is, one or more BWPs may be configured in each of one or more cells C configured in the terminal 10 . For example, up to four BWPs (each of DLBWP and ULBWP, which will be described later) may be configured in one cell C for the terminal 10 .
  • CORESET is a time domain and frequency domain resource for a downlink control channel (eg, Physical Downlink Control Channel (PDCCH)).
  • a CORESET consists of a predetermined number of symbols (eg, 1 to 3 symbols) and a predetermined number of resource blocks (RBs) (eg, 6n (n ⁇ 1) RBs).
  • RBs resource blocks
  • the downlink control channel is not limited to the PDCCH, and any name can be used as long as it is a channel used for transmitting downlink control information (Downlink Control Channel: DCI).
  • one or more formats may be defined for DCI transmission.
  • a format defined for transmission of DCI is called a DCI format.
  • PDSCH physical downlink shared channel
  • PUSCH physical uplink shared channel
  • PDSCH and PUSCH are physical channels used to transmit user data and/or control information of layers higher than the physical layer (for example, Medium Access Control Element (MAC CE), Radio Resource Control (RRC) messages, etc.) If so, the name is irrelevant. Names of other channels do not matter as long as they have similar functions.
  • the terminal 10 controls reception on the PDSCH based on the downlink assignment. Also, the terminal 10 controls transmission on PUSCH based on the uplink grant.
  • a downlink shared channel (DL-SCH) and an uplink shared channel (UL-SCH) may be defined as transport channels.
  • downlink user data also referred to as DL-SCH data
  • uplink user data also referred to as UL-SCH data
  • the DL-SCH may be mapped to the PDSCH and the UL-SCH may be mapped to the PUSCH.
  • the terminal 10 detects a synchronization signal (for example, Primary Synchronization Signal (PSS) and/or Secondary Synchronization Signal (PSS)) from the base station 20, and the time and Get frequency synchronization.
  • a synchronization signal for example, Primary Synchronization Signal (PSS) and/or Secondary Synchronization Signal (PSS)
  • PSS Primary Synchronization Signal
  • PSS Secondary Synchronization Signal
  • Blocks containing synchronization signals, broadcast channels (e.g., Physical Broadcast Channel (PBCH)) and broadcast channel demodulation reference signals (DMRS) are synchronized signal blocks (Synchronization Signal and PBCH Block: SSB ), SS/PBCH block, and the like.
  • the SSB is provided at predetermined intervals.
  • NR does not transmit cell-specific reference signals. Therefore, according to the SMTC (SSB-based measurement timing configuration) specified by the base station 20, the terminal 10 uses SSB transmitted in a predetermined cycle, RSRP (Reference Signal Received Power), RSRQ (Reference Signal Received Quality) and/or SINR (Signal to Noise and Interference Ratio) or the like is measured.
  • RSRP, RSRQ and SINR measured using SS are also called SS-RSRP, SS-RSRQ and SS-SINR, respectively.
  • Terminal 10 reports the result of measuring SSB to base station 20 .
  • the BWP is the bandwidth used by the terminal 10 to transmit and receive signals to and from the base station 20, and is defined as a subset of contiguous resource blocks.
  • FIG. 2 is a diagram showing an example of BWP settings. As shown in FIG. 2, BWP can be set to different frequency locations and bandwidths for each terminal 10 . Also, BWP can be configured separately for downlink and uplink. In this embodiment, "BWP" includes downlink BWP and/or uplink BWP. Further, in the following description, the downlink BWP and the uplink BWP are referred to as “DLBWP (Downlink BWP)” and “ULBWP (Uplink BWP)”, respectively. , one BWP may be activated among the plurality of BWPs, and the terminal 10 transmits and receives (communicates) radio signals within the band of the activated one BWP.
  • the terminal 10 transmits on the uplink shared channel (UL-SCH) and transmits a random access preamble on the RACH (Random Access Channel) in the BWP (however, the PRACH opportunity ( PRACH occasions) are configured), PDCCH monitoring, transmission on PUCCH (if PUCCH resources are configured), SRS (Sounding Reference Signal) transmission (if SRS is configured) and/or Reception is performed on the downlink shared channel (DL-SCH).
  • the terminal 10 may report CSI (Channel State Information) for the BWP.
  • the PRACH opportunity may be a resource (for example, time and/or frequency resource) on which terminal 10 can transmit a random access preamble.
  • the maximum bandwidth of BWPs and the maximum number of BWPs that can be set depend on the capabilities of the terminal 10 .
  • that the terminal 10 performs uplink and downlink communication may include at least one operation of the terminal 10 performing uplink and downlink communication in or with respect to the activated BWP. That is, BWPs (also referred to as “communication BWPs”) used by the terminal 10 for uplink and downlink communications may include BWPs (activated BWPs) on which at least one of the operations is performed by the terminal 10 .
  • the BWP that is mainly used when the terminal 10 makes an initial access to the cell is called an initial BWP.
  • the frequency position, bandwidth, subcarrier spacing and/or cyclic prefix of the initial BWP are notified to the terminal 10 by system information (SIB1 (System Information Block 1)). That is, the base station 20 broadcasts information on the initial BWP (frequency position, bandwidth, subcarrier spacing and/or cyclic prefix) in SIB1, and the terminal 10, based on the information on the initial BWP, the initial A BWP may be specified.
  • the initial BWP may be given to the terminal 10 by information included in a Master Information Block (MIB). That is, the initial BWP is set for all terminals accessing the cell.
  • MIB Master Information Block
  • a BWP is uniquely identified by a BWP-ID, and the BWP-ID of the initial BWP is "0".
  • the base station 20 adds (sets) a BWP to a frequency position and bandwidth other than the initial BWP, it sets the BWP-ID of the BWP as consecutive IDs in order from 1.
  • BWP#n means a BWP whose BWP-ID is n.
  • BWP#0 is synonymous with the initial BWP (ie, BWP#0 may be the BWP-ID defined for the initial BWP).
  • FIG. 3 is a diagram for explaining the BWP switching process.
  • BWP switching means activating an inactive BWP and deactivating an active BWP in a serving cell at the same time. In other words, it means switching the active BWP.
  • three BWPs, BWP#0 to BWP#2 are set in the terminal 10, and it is shown how the active BWP is switched over time.
  • BWP#1 is active between times t1 and t2
  • BWP#2 is active between times t3 and t4
  • BWP#0 is active at other times.
  • BWP switching is triggered by any of the following: when an instruction is received from the base station 20, when the timer expires, or when random access (RA) is performed.
  • the timer is also called bwp-InactivityTimer.
  • the case of receiving an instruction from the base station 20 specifically means the case of receiving from the base station 20 an RRC message or a PDCCH (that is, DCI) including information designating a BWP to be activated.
  • FIG. 4 is a diagram for explaining information elements of SIB1 used to set the initial BWP. Note that FIG. 4 shows information elements necessary for explaining this embodiment, and SIB1 includes information elements not shown in FIG.
  • DownlinkConfigCommonSIB includes "BWP-DownlinkCommon" and "BWP-UplinkCommon" for cell-specific settings for initial DLBWP and initial ULBWP.
  • BWP-DownlinkCommon set the initial DLBWP frequency position, bandwidth, subcarrier spacing, cyclic prefix, etc., and set the cell-specific parameters related to PDCCH and PDSCH in the initial DLBWP.
  • "PDCCH-ConfigCommon” and "PDSCH-ConfigCommon” are included.
  • PDCCH-ConfigCommon includes settings for CORESET#0 (controlResourceSetZero), settings for search space #0 (SearchSpaceZero), and the like.
  • BWP-UplinkCommon includes "BWP" for setting the frequency position, bandwidth, subcarrier spacing, cyclic prefix, etc. of the initial ULBWP, and "RACH- ConfigCommon", and "PUCCH-ConfigCommon” and "PUSCH-ConfigCommon” for setting cell-specific parameters for PUCCH and PUSCH in the initial ULBWP.
  • FIG. 5 is a diagram for explaining information elements related to BWP settings in an RRC message. Note that FIG. 5 shows information elements necessary for explaining this embodiment, and the RRC message also includes information elements not shown in FIG. In FIG. 5, an RRC reconfiguration message (RRCReconfiguration) will be described as an example, but some of the information elements shown in FIG. 5 can also be included in other RRC messages (eg, RRC setup (RRC Setup)).
  • RRC setup RRC Setup
  • the RRC reconfiguration message is used to change UE-specific RRC connection settings for individual terminals 10.
  • the RRC reconfiguration message includes "ServingCellConfigCommon" for configuring cell-specific parameters in the serving cell and "ServingCellConfig” for configuring terminal-specific parameters in the serving cell.
  • “ServingCellConfigCommon” includes "BWP-DownlinkCommon” and "BWP-UplinkCommon” for cell-specific settings for initial DLBWP and initial ULBWP, similar to SIB1 shown in FIG.
  • “ServingCellConfig” includes “BWP-DownlinkDedicated” for terminal-specific settings set for the initial DLBWP and “BWP-UplinkDedicated” for terminal-specific settings set for the initial ULBWP.
  • “BWP-DownlinkDedicated” includes "PDCCH-Config” for setting terminal-specific PDCCH parameters such as CORESET and search space, and "PDSCH-Config” for setting terminal-specific PDSCH parameters.
  • ⁇ BWP-UplinkDedicated'' is a ⁇ PUCCH-Config'' that configures terminal-specific PUCCH parameters such as PUCCH resources used to transmit UCI (Uplink Control Information) such as scheduling requests (SR).
  • PUSCH-Config for setting terminal-specific PUSCH parameters.
  • a configuration such as a PUCCH resource used to transmit a scheduling request is also referred to as a scheduling request configuration (SR configuration).
  • the scheduling request configuration may include PUCCH resources, period, offset values, etc. used to transmit the scheduling request.
  • the terminal 10 may transmit the scheduling request based on the scheduling request settings.
  • “ServingCellConfig” also includes "BWP-Downlink” and “BWP-Uplink” used when adding BWPs (eg, BWP#1, BWP#2, etc.) in addition to the initial BWP.
  • BWP-Downlink for each DLBWP to be set, BWP-ID, BWP frequency position, bandwidth, subcarrier interval and cyclic prefix, etc., cell-specific parameters related to PDCCH and PDSCH " "BWP-DownlinkCommon” and "BWP-DownlinkDedicated” for setting terminal-specific PDCCH/PDSCH parameters such as CORESET and search space.
  • BWP-Uplink for each ULBWP to be set, BWP-ID, BWP frequency position, bandwidth, subcarrier spacing and cyclic prefix, etc., and cell-specific parameters related to PUCCH and PUSCH are set.
  • BWP-UplinkCommon and "BWP-UplinkDedicated” for setting terminal-specific PDCCH/PDSCH parameters such as CORESET and search space.
  • FIG. 6 is a diagram for explaining two options regarding the BWP setting method.
  • Option 1 (Option#1) does not perform settings other than cell-specific settings notified in SIB1 for BWP#0, and sets terminal-specific settings such as terminal-specific PUCCH parameters to BWP#1 to BWP#4. How to set.
  • "ServingCellConfig” is provided with "BWP-DownlinkDedicated” for performing terminal-specific resource settings for the initial BWP. If you set it using “BWP-Downlink” and “BWP-Uplink” in "downlinkBWP-ToAddModList" without using
  • one or more BWPs are configured for one serving cell, and the maximum number of BWPs (DLBWP and ULBWP, respectively) configured for one serving cell is It is specified to be four. Also, for example, option 1 specifies that the terminal 10 does not consider BWP#0 as the BWP set in the RRC message. Therefore, in Option 1, the base station 20 can configure four BWPs, BWP#1 to BWP#4, for the terminal 10 using RRC messages.
  • the terminal 10 can only perform limited processing.
  • DCI format 1_0 can be used, but DCI format 1_0 does not support BWP switching. Therefore, when switching the BWP of the terminal 10 from BWP#0 to another BWP, it is necessary to switch the BWP using an RRC message.
  • option 2 is a method of performing terminal-specific settings such as terminal-specific PUCCH parameters for BWP#0 in addition to cell-specific settings notified by SIB1.
  • terminal-specific settings such as terminal-specific PUCCH parameters for BWP#0 in addition to cell-specific settings notified by SIB1.
  • "ServingCellConfig” provides "BWP-DownlinkDedicated” for terminal-specific resource settings for the initial BWP, but the terminal-specific resource settings are set to "BWP-DownlinkDedicated". If you use it and set it, it will be in the option 2 state.
  • the specifications stipulate that the terminal 10 regards BWP#0 as the BWP set in the RRC message. Therefore, in Option 2, the base station 20 can configure BWPs BWP#0 to BWP#3 for the terminal 10 using an RRC message.
  • FIG. 7 is a sequence diagram for explaining the operation of BWP switching. Four switching patterns of BWP switching by random access, BWP switching by RRC message, BWP switching by PDCCH, and BWP switching by timer expiration will be specifically described with reference to FIG.
  • step S100 the terminal 10 detects that an event triggering a random access procedure has occurred.
  • step S101 the terminal 10 switches the initial ULBWP to active if no PRACH opportunity is configured in the current active ULBWP. Furthermore, if the serving cell performing the random access procedure is a special cell, switch the initial DLBWP to active. If a PRACH opportunity is set for the current active ULBWP, the terminal 10 does not switch the ULBWP.
  • step S102 the terminal 10 performs a random access (RA) procedure with the base station 20 in active ULBWP and active DLBWP.
  • RA random access
  • step S110 the terminal 10 receives from the base station 20 an RRC reconfiguration message including 'firstActiveDownlinkBWP-id' and/or 'firstActiveUplinkBWP-id'.
  • step S111 the terminal 10 switches active the BWP having the BWP-ID designated by 'firstActiveDownlinkBWP-id' and/or 'firstActiveUplinkBWP-id'.
  • step S120 the terminal 10 receives DCI for downlink or uplink resource allocation on the PDCCH.
  • step S121 when a BWP indicator (also called a Bandwidth part indicator) exists in the DCI, the terminal 10 switches the BWP of the BWP-ID specified by the BWP indicator to active.
  • step S122 the terminal 10 starts counting a timer (also called bwp-InactivityTimer).
  • the length of the timer is set in the terminal 10 by "ServingCellConfig". According to the Release 16 3GPP specifications, it can be set between 2ms (milliseconds) and a maximum of 2560ms. Note that when the terminal 10 receives a DCI for allocating downlink or uplink resources before the timer expires, the terminal 10 restarts the timer count regardless of whether the DCI includes a BWP indicator. )do.
  • DCIs that support BWP switching are DCI format 0_1, DCI format 0_2, DCI format 1_1, and DCI format 1_2.
  • DCI format 0_0 and DCI format 1_0 cannot contain a BWP indicator.
  • the bit length (also referred to as the number of bits) of the BWP indicator is determined to be 0, 1, or 2 bits based on the number of BWPs other than BWP #0 set in terminal 10 .
  • bit length of the BWP indicator included in the downlink assignment may be determined based on the number of DLBWPs set in the terminal 10 .
  • bit length of the BWP indicator included in the uplink grant may be determined based on the number of ULBWPs configured in the terminal 10 .
  • step S130 the terminal 10 determines whether the timer has expired. When the timer expires (S130-YES), switch the initial DLBWP to active. If resource allocation is performed by DCI before the timer expires, the timer count is restarted. no resource allocation). For example, if data transmission/reception is not performed during the period set by the timer, and if the default DLBWP-ID (DefaultDownlinkBWP-Id) is set in "ServingCellConfig", the terminal 10 replaces the initial DLBWP with Then, the DLBWP specified by the default DLBWP-ID is switched to active (S131). If the timer has not expired (S130-NO), the terminal 10 does not switch the BWP.
  • S130-YES switch the initial DLBWP to active. If resource allocation is performed by DCI before the timer expires, the timer count is restarted. no resource allocation). For example, if data transmission/reception is not performed during the period set by the timer,
  • ⁇ RedCap terminal> Release 17 of NR has lower performance and price than terminals for high speed, large capacity (enhanced Mobile Broadband: eMBB), ultra-reliable and low latency communications (URLLC) introduced in release 15 or 16 It is being considered to support functions for terminals assuming Obi.
  • the terminal is also called a reduced capability (RedCap) terminal, device, etc., and is used for, for example, an industrial wireless sensor, a surveillance camera (video serveilance), a wearable device, and the like. good too.
  • RedCap terminals are assumed to have higher performance than terminals for low power wide area communication (Low Power Wide Area: LPWA), and the carriers used by RedCap terminals are, for example, 20MHz, 50MHz or 100MHz bandwidth. There may be.
  • LPWA includes, for example, Category 1, Long Term Evolution for Machine-type-communication (LTE-M) and Narrow Band IoT (NB-IoT) that operate on LTE RAT.
  • LTE-M Long Term Evolution for Machine-type-communication
  • NB-IoT Narrow Band IoT
  • the maximum bandwidth of Category 1 is 20 MHz
  • the maximum bandwidth of LTE-M is 1.4 MHz (6 RB)
  • the maximum bandwidth of NB-IoT is 180 kHz (1 RB).
  • RedCap terminals may be used as middle-range terminals between those for eMBB, URLLC, and those for LPWA.
  • FIG. 8 is a diagram for explaining an example of the problem in this embodiment.
  • the maximum UE bandwidth supported by RedCap terminals is narrow (e.g., 20 MHz for Frequency Range 1 (e.g., frequency bands below 6 GHz) and 20 MHz for Frequency Range 2 (e.g., higher than 6 GHz). 100 MHz) for the frequency band), but if RedCap terminals are concentrated in a BWP containing SSB, the BWP will be congested. Therefore, it is being considered to distribute RedCap terminals over the entire carrier bandwidth for communication.
  • the BWP is switched using the RRC message.
  • the signaling overhead is large when performing BWP switching (second problem).
  • the present embodiment introduces a mechanism for suppressing the number of times the base station 20 issues a BWP switching instruction to the terminal 10 .
  • one BWP (communication BWP) may be set for the terminal 10 as a BWP other than the initial BWP and used by the terminal 10 for uplink and downlink communications.
  • BWP switching by PDCCH can be used from the base station 20 to the terminal 10 even if the initial BWP is not set for each terminal (in the case of option 1).
  • FIG. 9 is a sequence diagram for explaining an example of the BWP switching process when the initial BWP and communication BWP are set.
  • the terminal 10 is a RedCap terminal, but the present embodiment is not limited to this. It is also assumed that the terminal 10 is capable of executing the processing procedures described so far (for example, the BWP switching processing described with reference to FIG. 7).
  • the communication BWP does not include a band in which SSB is set, but it can also be applied when SSB is included. That is, the communication BWP may be a BWP including SSB resources. Also, the communication BWP may be a BWP that does not include SSB resources.
  • the terminal 10 notifies the base station 20 of terminal capability information (UE Capability).
  • the terminal 10 includes information indicating that it is a RedCap terminal in the terminal capability information and transmits it to the base station 20 . It is assumed that the terminal 10 acquires the setting of the initial BWP by receiving the SIB1 at the time of initial access.
  • the base station 20 refers to the terminal capability information to recognize that the terminal 10 is a RedCap terminal, and transmits an RRC message including information for setting a communication BWP to the terminal 10 .
  • the RRC message may be, for example, an RRC reconfiguration message.
  • step S210 data to be transmitted on the UL-SCH occurs in the terminal 10 in step S210. Also assume that the active BWPs are the initial ULBWP and the initial DLBWP.
  • step S211 when the terminal 10 transmits a scheduling request (for example, when in the RRC connected state), if terminal-specific PUCCH parameters are not set for the initial BWP, the process proceeds to step S211. Also, when transmitting a scheduling request, the terminal 10 proceeds to the processing procedure of step S220 if terminal-specific PUCCH parameters are set for the initial BWP.
  • requesting uplink resource allocation may include requesting UL-SCH resources for the initial transmission, i.e. scheduling The request may be used to request UL-SCH resources for initial transmission, and when terminal 10 performs a random access procedure (eg, when in RRC idle or RRC inactive state). If the PRACH opportunity is set in the communication BWP, the procedure proceeds to step S230, and in this case, if the terminal 10 does not set the PRACH opportunity in the communication BWP, the processing procedure of step S240 is performed. proceed to
  • step S211 the terminal 10 switches the active ULBWP from the initial ULBWP to the communication ULBWP.
  • the terminal 10 transmits a scheduling request to the base station 20 using the terminal-specific PUCCH resource for transmitting the scheduling request set in the ULBWP for communication.
  • step S213 the terminal 10 switches the active DLBWP from the initial DLBWP to the communication DLBWP, and monitors the PDCCH with the communication DLBWP.
  • the terminal 10 proceeds to the processing procedure of step S250.
  • step S212 the terminal 10 may switch the initial ULBWP and the initial DLBWP to the communication ULBWP and the communication DLBWP, respectively. That is, the terminal 10 may simultaneously switch the initial ULBWP and the initial DLBWP to the communication ULBWP and the communication DLBWP in step S212.
  • step S220 the terminal 10 transmits a scheduling request to the base station 20 using the terminal-specific PUCCH resource for transmitting scheduling requests set in the initial BWP.
  • step S221 the terminal 10 switches the active DLBWP from the initial DLBWP to the communication DLBWP, and monitors the PDCCH with the communication DLBWP.
  • the terminal 10 proceeds to the processing procedure of step S250.
  • step S221 the terminal 10 monitors the PDCCH with the initial DLBWP, and is instructed to activate the communication DLBWP with the PDCCH including the BWP indicator. You may switch to DLBWP for
  • step S230 the terminal 10 switches the active ULBWP and active DLBWP from the initial ULBWP and initial DLBWP to the communication ULBWP and communication DLBWP, respectively, when the PRACH opportunity is set in the communication ULBWP. That is, the terminal 10 may set the communication ULBWP and the communication DLBWP as the active ULBWP and active DLBWP.
  • step S231 the terminal 10 transmits a random access preamble to the base station 20 at the PRACH opportunity of the activated ULBWP for communication. After completing the random access procedure, the terminal 10 requests the base station 20 to allocate uplink resources. For example, the terminal 10 transmits a scheduling request in ULBWP for communication.
  • the terminal 10 of the base station 20 proceeds to the processing procedure of step S250.
  • the terminal 10 transmits a random access preamble to the base station 20 at the PRACH opportunity of the activated initial ULBWP, and performs a random access procedure with the base station 20. After completing the random access procedure, the terminal 10 requests the base station 20 to allocate uplink resources.
  • the terminal 10 switches the active ULBWP and active DLBWP from the initial ULBWP and initial DLBWP to the communication ULBWP and communication DLBWP, respectively. That is, the terminal 10 may set the communication ULBWP and the communication DLBWP as the active ULBWP and active DLBWP.
  • the terminal 10 may transmit a scheduling request in the initial ULBWP in step S240. Also, the terminal 10 may transmit a scheduling request in the ULBWP for communication in step S241.
  • step S250 the base station 20 transmits the DCI (uplink grant) used for PUSCH scheduling on the PDCCH of the communication DLBWP.
  • step S251 when the terminal 10 is instructed to activate the communication ULBWP by the BWP indicator of the DCI received in step S250, the terminal 10 switches the communication ULBWP to active.
  • the processing procedure of step S251 may be executed when individual PUCCH settings are made in the initial BWP (that is, in steps S220 and S221).
  • the ULBWP switching in the procedure of step S251 may be performed when the terminal 10 monitors the PDCCH in the initial DLBWP.
  • the terminal 10 monitors the PDCCH with the initial DLBWP, and is instructed to activate the communication ULBWP with the PDCCH including the BWP indicator. may be switched from the initial ULBWP to the communication ULBWP. Further, the terminal 10 may actively switch the communication ULBWP by itself instead of switching the ULBWP according to an instruction from the base station 20 after the processing procedure of step S221. Since the base station 20 no longer needs to include the BWP indicator in the DCI, it is possible to reduce signaling overhead.
  • step S252 the terminal 10 starts counting a timer when DCI used for PUSCH scheduling is received on the PDCCH (corresponding to the processing procedure of step S122 in FIG. 7).
  • step S253 the terminal 10 transmits data on the UL-SCH on the scheduled PUSCH.
  • the terminal 10 receives the DCI used for scheduling of the PUSCH or PDSCH on the PDCCH before the timer expires, the terminal 10 restarts the timer count.
  • step S260 when the timer related to the active BWP expires, the terminal 10 switches the active BWP from the communication BWP to the initial BWP (corresponding to steps S130 and S131 in FIG. 7). That is, the terminal 10 may set the initial BWP as the active BWP.
  • step S261 the terminal 10 uses the SSB present in the initial BWP based on the measurement configuration (Measurement Config) set by the base station 20 using the RRC message or the like in step S201, for example. (SS-RSRP, SS-RSRQ, etc.) are measured.
  • the processing procedure of steps S211 to S213 can also be applied to Option 2 shown in FIG. That is, the terminal 10 may execute the processing procedure of steps S211 to S213 even when terminal-specific PUCCH parameters are set in the initial ULBWP. Also, the processing procedure of steps S230 to S241 is not limited to the case of transmitting UL-SCH data, but can be applied to the general case of activating the random access procedure.
  • FIG. 10 is a flow chart showing an example of a processing procedure when transmitting a scheduling request.
  • the terminal 10 has both the DLBWP for communication and the ULBWP for communication set, and when transmitting a scheduling request, the terminal 10 executes the processing procedure shown below.
  • the terminal 10 determines whether or not the communication ULBWP is active. If the communication ULBWP is active, the process proceeds to step S301, and if the initial ULBWP is active, the process proceeds to step S302. At step S301, the terminal 10 triggers and transmits a scheduling request on the active ULBWP (that is, the communication ULBWP).
  • step S302 the terminal 10 determines whether terminal-specific PUCCH parameters for transmitting scheduling requests are set in the initial ULBWP. If the terminal-specific PUCCH parameter for transmitting the scheduling request is set, the process proceeds to step S303, and if the terminal-specific PUCCH parameter for transmitting the scheduling request is not set, the process proceeds to step S304. move on.
  • step S303 the terminal 10 triggers and sends a scheduling request on the active ULBWP (ie the initial ULBWP).
  • step S304 the terminal 10 actively switches between the communication ULBWP and the communication DLBWP.
  • step S305 the terminal 10 triggers and transmits a scheduling request on the active ULBWP (that is, the communication ULBWP).
  • step S306 the terminal 10 determines whether the DLBWP for communication is active. If the DLBWP for communication is active, the process ends, and if the initial DLBWP is active (that is, including the case where the DLBWP for communication is not active), the procedure proceeds to step S307. In step S307, the terminal 10 switches the communication DLBWP to active. The terminal 10 may perform communication on the activated DLBWP for communication and/or the activated ULBWP for communication.
  • the terminal 10 transmits the scheduling request in the initial ULBWP if the PUCCH resource (scheduling request setting may be set) for transmitting the scheduling request is set in the initial ULBWP. You may send. Also, when the scheduling request is triggered, if the PUCCH resource (which may be a scheduling request setting) for transmitting the scheduling request is not set to the initial ULBWP, the terminal 10 sets the ULBWP to the communication ULBWP. and send the scheduling request in the active ULBWP (ie, the communication ULBWP).
  • the PUCCH resource which may be a scheduling request setting
  • the terminal 10 activates the ULBWP as the communication ULBWP if the PUCCH resource (which may be the scheduling request setting) for transmitting the scheduling request is set in the communication ULBWP. It may switch as a ULBWP and send scheduling requests in the active ULBWP (ie, the communication ULBWP). That is, the terminal 10 may switch the ULBWP to the communication ULBWP as the active ULBWP when the scheduling request is triggered.
  • the terminal 10 may switch the communication DLBWP to the active DLBWP. That is, the terminal 10 may simultaneously switch between the communication ULBWP and the communication DLBWP as the active ULBWP and the active DLBWP, respectively.
  • the terminal 10 may itself switch the active ULBWP from the initial BWP to the communication ULBWP after the processing procedure of step S303. This makes it possible to omit, for example, the processing procedure of step S251 in FIG. 9 and reduce signaling overhead.
  • FIG. 11 is a flow chart showing an example of the processing procedure when executing the random access procedure.
  • the terminal 10 determines whether or not the PRACH opportunity is set in the communication ULBWP. When the PRACH opportunity is set in the communication ULBWP, the process proceeds to step S401, and when the PRACH opportunity is not set in the communication ULBWP, the process proceeds to step S405.
  • step S401 the terminal 10 determines whether the ULBWP for communication and the DLBWP for communication are active. If both the communication ULBWP and the communication DLBWP are active, the process proceeds to step S402, and if at least one of the communication ULBWP and the communication DLBWP is not active, the process proceeds to step S403.
  • step S402 the terminal 10 performs a random access procedure on the communication ULBWP and the communication DLBWP.
  • step S403 the terminal 10 switches the inactive BWP out of the communication ULBWP and the communication DLBWP to active.
  • step S404 after both the communication ULBWP and the communication DLBWP are switched active, the terminal 10 executes the random access procedure on the communication ULBWP and the communication DLBWP.
  • step S405 the terminal 10 performs a random access procedure with the initial ULBWP and the initial DLBWP.
  • step S406 the terminal 10 performs the random access procedure in the initial ULBWP and the initial DLBWP, and then actively switches between the communication ULBWP and the communication DLBWP.
  • a communication BWP may be called, for example, a communityBWP.
  • the base station 20 may set the communication BWP to the terminal 10 by including information indicating the BWP-ID of the communication BWP in the RRC message transmitted in the procedure of step S201 in FIG. .
  • the information may be called, for example, communicateUplinkBWP-id and communicateDownlinkBWP-id. That is, the base station 20 transmits an RRC message containing information for setting the BWP-ID, and the terminal 10 regards the BWP corresponding to the BWP-ID set using the information as the communication BWP.
  • the base station 20 transmits an RRC message including information for setting a BWP-ID corresponding to the DLBWP (for example, also referred to as communicateDownlinkBWP-id), and the terminal 10 transmits the BWP-ID corresponding to the DLBWP.
  • a DLBWP corresponding to a BWP-ID set using information for setting a DLBWP for communication may be regarded as a DLBWP for communication.
  • the terminal 10 performs RRC (re)configuration (for example, when performing RRC (re)configuration based on reception of an RRC message containing information for setting the BWP-ID corresponding to the DLBWP) , may activate the DLBWP for that BWP-ID.
  • the base station 20 transmits an RRC message including information for setting a BWP-ID corresponding to the ULBWP (for example, also referred to as communicateUplinkBWP-id), and the terminal 10 transmits the BWP-ID corresponding to the ULBWP.
  • the ULBWP corresponding to the BWP-ID set using the information for setting the ULBWP may be regarded as the communication ULBWP.
  • the terminal 10 performs RRC (re)configuration (for example, RRC (re)configuration based on reception of an RRC message containing information for setting the BWP-ID corresponding to the ULBWP). , may activate the ULBWP for that BWP-ID.
  • a value other than "0" (that is, a value other than the BWP-ID corresponding to the initial DLBWP and/or the initial ULBWP) is set as the BWP-ID corresponding to each of the communication DLBWP and/or the communication ULBWP.
  • FIG. 12 is a diagram showing an example of information elements included in the RRC message used to set the BWP for communication.
  • "communicateUplinkBWP-id” and “communicateDownlinkBWP-id” indicating the BWP-ID of the communication BWP may be defined in the "ServingCellConfig" of the RRC reconfiguration message.
  • the base station 20 determines that the terminal 10 is a RedCap terminal based on the UE Capability of the terminal 10, the information about one or more DLBWPs (for example, BWP- ID, frequency position, bandwidth, subcarrier spacing and/or cyclic prefix), and by specifying the BWP-ID of the DLBWP to be set as the DLBWP for communication using "communicateDownlinkBWP-id", 1 One communication DLBWP is set in the terminal 10 .
  • DLBWPs for example, BWP- ID, frequency position, bandwidth, subcarrier spacing and/or cyclic prefix
  • the base station 20 in the "BWP-Uplink" of the RRC message, information on one or more ULBWP (for example, BWP-ID, frequency position, bandwidth, subcarrier spacing and / or cyclic prefix)
  • One communication ULBWP is set in the terminal 10 by specifying the BWP-ID of the ULBWP to be set as the communication ULBWP using "communicateUplinkBWP-id".
  • the base station 20 sets a plurality of BWPs (for example, BWP #1 to #3) in the terminal 10, and sets a BWP-ID corresponding to the communication BWP, thereby It is possible to change the BWP arbitrarily. For example, it is possible to change the communication BWP from BWP#1 to BWP#3.
  • the value of the BWP-ID corresponding to each communication DLBWP and/or communication ULBWP may be a value defined in advance.
  • the BWP-ID value corresponding to the communication DLBWP may be "1".
  • the value of the BWP-ID corresponding to the communication ULBWP may be "1".
  • the value of the BWP-ID corresponding to each communication DLBWP and/or communication ULBWP is defined in advance by specifications or the like, and may be a known value between the base station 20 and the terminal 10.
  • the base station 20 sets information on one or more DLBWPs (eg, BWP-ID, frequency position, bandwidth, subcarrier spacing and/or cyclic prefix), and the terminal 10 sets "1 ( That is, a DLBWP with a BWP-ID set with a predefined value) may be regarded as a communication DLBWP.
  • the base station 20 sets information (for example, BWP-ID, frequency position, bandwidth, subcarrier spacing and/or cyclic prefix) about one or more ULBWPs, and the terminal 10 sets "1 ( That is, a ULBWP with a BWP-ID set with a predefined value) may be regarded as a communication DLBWP. In this way, by enabling designation of the communication BWP, it becomes possible to flexibly set the BWP in the RedCap terminal.
  • information for example, BWP-ID, frequency position, bandwidth, subcarrier spacing and/or cyclic prefix
  • firstActiveDownlinkBWP-id may be used to indicate the BWP-ID of the communication DLBWP
  • firstActiveUplinkBWP-id may be used to indicate the BWP-ID of the communication ULBWP.
  • the base station 20 determines that the terminal 10 is a RedCap terminal based on the UE Capability of the terminal 10, it uses the "BWP-Downlink" of the RRC message to transmit information about one or more DLBWPs.
  • One communication DLBWP is set in the terminal 10 by specifying the BWP-ID of the DLBWP to be set as the communication DLBWP using "firstActiveDownlinkBWP-id".
  • the base station 20 uses "BWP-Uplink" of the RRC message to set information about one or more ULBWPs, and uses "firstActiveUplinkBWP-id" to set the BWP-ID of the ULBWP to be set as a ULBWP for communication. , one communication ULBWP is set in the terminal 10 .
  • the terminal 10 determines whether or not it is a RedCap terminal in the processing procedure of step S201 in FIG.
  • the BWP corresponding to the BWP-ID specified by "ID” may be regarded as the communication BWP. This makes it possible to set a BWP for communication in the RedCap terminal using "firstActiveDownlinkBWP-id" and/or "firstActiveUplinkBWP-id" included in the RRC message.
  • one or more BWPs are set for one serving cell for RedCap terminals, and the maximum number of BWPs (DLBWP and ULBWP, respectively) set for one serving cell is specified to be 1.
  • the maximum number of BWPs (DLBWPs and ULBWPs, respectively) set for RedCap terminals may be the number of BWPs (DLBWPs and ULBWPs, respectively) other than the initial DLBWP and the initial ULBWP.
  • the base station 20 determines that the terminal 10 is a RedCap terminal based on the UE Capability of the terminal 10, it sets only the information about DLBWP#1 in "BWP-Downlink” of the RRC message, and sets "communicateDownlinkBWP-id ” or “firstActiveDownlinkBWP-id” to 1, the DLBWP for communication may be set in the terminal 10 .
  • the base station 20 sets only information related to ULBWP#1 in "BWP-Uplink” of the RRC message, and sets “communicateUplinkBWP-id” or “firstActiveUplinkBWP-id” to 1, thereby may be set in the terminal 10.
  • the number of BWPs set by the RRC message is limited to one, so it is possible to reduce the amount of data in the RRC message.
  • the base station 20 includes information for specifying the communication BWP (also referred to as "generic parameter") together with information for setting the BWP-ID of the communication BWP in the RRC message, and transmits the terminal. 10 may determine the communication BWP based on the information for setting the BWP-ID and the information for specifying the communication BWP.
  • the information for identifying the communication BWP may include information for setting the frequency position and/or bandwidth of the communication BWP.
  • the information for specifying the communication BWP may include information for setting the subcarrier interval of the communication BWP.
  • the information for specifying the communication BWP may include information for setting the cyclic prefix used in the communication BWP.
  • the terminal 10 executes RRC (re)configuration (for example, RRC (re)configuration based on reception of an RRC message containing information for setting the BWP-ID and information for specifying the communication BWP. Execution of setting), the BWP for communication may be activated.
  • the base station 20 transmits information for setting a plurality of frequency positions (that is, a plurality of positions in the frequency domain) of the communication BWP in an RRC message, and furthermore, the plurality of frequency positions Information (for example, BWP indicator) for indicating the frequency position of one of them may be included in the DCI format (downlink assignment and/or uplink grant) and transmitted.
  • RRC (re)configuration for example, RRC (re)configuration based on reception of an RRC message containing information for setting the BWP-ID and information for specifying the communication BWP. Execution of setting
  • the BWP for communication may be activated.
  • the base station 20 transmits information for setting a plurality of frequency positions
  • terminal 10 may determine a communication BWP based on information for setting the plurality of frequency positions and information for indicating one frequency position among the plurality of frequency positions. good. Information for designating one frequency position out of the plurality of frequency positions will be described in detail in the definition of the BWP designator below.
  • the base station 20 may set the communication BWP bandwidth set for the terminal 10 so as not to exceed the maximum terminal bandwidth of the terminal 10 . Also, the base station 20 may set the bandwidth of the communication BWP set for the terminal 10 so as not to exceed the bandwidth of the initial BWP set using the information included in the SIB1. Also, the terminal 10 may use the maximum terminal bandwidth in the terminal 10 as the bandwidth of the communication BWP. For example, it may be specified that the information for setting the bandwidth of the BWP for communication is not transmitted by the base station 20 and the bandwidth of the BWP for communication is the same as the maximum terminal bandwidth of the terminal 10 .
  • the base station 20 sets the communication BWP bandwidth, subcarrier interval and/or cyclic prefix to be set for the terminal 10 using the information included in SIB1, the initial BWP bandwidth, subcarrier It may be set equal to the interval and/or cyclic prefix.
  • the terminal 10 uses the information included in SIB1 as the communication BWP bandwidth, subcarrier spacing and/or cyclic prefix, the initial BWP bandwidth, subcarrier spacing and/or cyclic prefix set using the information included in SIB1 may be used.
  • information for setting the communication BWP bandwidth, subcarrier spacing and/or cyclic prefix is not transmitted by the base station 20, and the communication BWP bandwidth, subcarrier spacing and/or cyclic prefix is not set.
  • Each may be defined to be the same as the initial BWP's bandwidth, subcarrier spacing and/or cyclic prefix, respectively.
  • the bandwidths, subcarrier intervals and/or cyclic prefixes set (or defined) for each of the multiple BWPs set for the terminal 10 may be the same.
  • the bandwidth, subcarrier spacing and/or cyclic prefix configured for DLBWP and ULBWP may be different. That is, the terminal 10 may perform the BWP switching process for a plurality of DLBWPs for which the same bandwidth, subcarrier spacing and/or cyclic prefix are set. Also, the terminal 10 may perform a BWP switching process for a plurality of ULBWPs for which the same bandwidth, subcarrier spacing and/or cyclic prefix are set.
  • the setting of the initial BWP may follow Option 1 or Option 2 shown in FIG.
  • Fig. 13 shows an example of a specification change of TS38.321.
  • the example of FIG. 13 corresponds to the process of transmitting scheduling requests using active BWPs configured with PUCCH resources for transmitting scheduling requests in FIG.
  • the terminal 10 switches the active BWP by itself, for example, when transmitting a scheduling request. This reduces the chances of requiring an instruction from the base station 20 when switching between the initial BWP and the communication BWP, thereby reducing signaling overhead. Further, when the PRACH opportunity is set in the communication BWP, the terminal 10 switches the BWP by itself and executes the random access procedure in the communication BWP. As a result, in addition to reducing signaling overhead, it is possible to prevent random access processing from concentrating on SSBs within the initial BWP.
  • FIG. 14 is a sequence showing an example of BWP switching processing when the initial BWP is not set for each terminal.
  • the terminal 10 is a RedCap terminal, but the present embodiment is not limited to this. It is also assumed that the terminal 10 is capable of executing the processing procedures described so far (for example, the BWP switching processing described with reference to FIG. 7).
  • step S500 the terminal 10 notifies the base station 20 of terminal capability information (UE Capability).
  • the terminal 10 includes information indicating that it is a RedCap terminal in the terminal capability information and transmits the information to the base station 20 . It is assumed that the terminal 10 sets the initial BWP by referring to the SIB1 at the time of initial access.
  • step S501 the base station 20 refers to the terminal capability information to recognize that the terminal 10 is a RedCap terminal, and transmits an RRC message for setting the communication BWP to the terminal 10.
  • the RRC message may be, for example, an RRC reconfiguration message.
  • the base station 20 uses "BWP-Downlink” and "BWP-Uplink” in "downlinkBWP-ToAddModList” to perform DLBWP and ULBWP without using "BWP-DownlinkDedicated” in "ServingCellConfig" of the RRC message.
  • an individual resource for the terminal 10 is set (that is, BWP setting according to Option 1 in FIG. 6).
  • step S510 when switching the BWP of the terminal 10, the base station 20 transmits DCI including a BWP indicator designating the BWP to be switched to the terminal 10 on the PDCCH.
  • the base station 20 may transmit DCI of DCI format 1_0 including the BWP indicator to the terminal 10 .
  • the 3GPP specification may be modified to add a BWP indicator to DCI format 1_0.
  • the base station 20 may transmit DCI of DCI format 0_0 including the BWP indicator to the terminal 10 .
  • the 3GPP specification may be modified to add a BWP indicator to DCI format 0_0.
  • the base station 20 may transmit DCI of DCI format 1_1 or DCI format 1_2 including the BWP indicator to the terminal 10 .
  • the 3GPP specification may be modified to allow DCI transmission of DCI format 1_1 or DCI format 1_2 even if there is only cell-specific resource configuration in the initial BWP. .
  • the 3GPP specifications may define new DCI formats for RedCap terminals that include BWP indicators (eg, DCI format 0_3, DCI format 1_3).
  • BWP indicators eg, DCI format 0_3, DCI format 1_3
  • base station 20 may transmit DCI in a new DCI format including a BWP indicator to terminal 10 .
  • step S511 the terminal 10 switches the BWP specified by the BWP indicator to active.
  • step S512 the terminal 10 starts counting a timer upon receiving the PDCCH. Also, when the terminal 10 receives the PDCCH before the timer expires, the terminal 10 restarts the timer count.
  • step S521 the terminal 10 switches the initial BWP or the default BWP to active when the timer expires.
  • the processing procedure of step S240 corresponds to the processing procedure of steps S130 and S131 in FIG.
  • FIG. 15 is a diagram showing a definition example of a BWP indicator.
  • the name of the BWP indicator in this embodiment is merely an example, and any name may be used as long as it is information that defines the following operations.
  • the terminal 10 is instructed by the BWP indicator.
  • the active BWP may be set to the selected BWP.
  • FIG. 15A shows that if the value of the BWP indicator is set to 0, initial DLBWP and/or initial ULBWP are indicated.
  • the DLBWP i.e., including the communication DLBWP described above
  • the ULBWP i.e., including the communication ULBWP described above
  • the definition shown in A of FIG. 15 is that the base station 20 uses one DLBWP (that is, DLBWP#1) and one ULBWP (that is, ULBWP#) in "BWP-Downlink” and “BWP-Uplink” in "ServingCellConfig". 1) is set in the terminal 10.
  • DLBWP that is, DLBWP#1
  • ULBWP# that is, ULBWP#
  • the base station 20 sets "communicateUplinkBWP-id” and "communicateDownlinkBWP-id” indicating the BWP-ID of the communication BWP in "ServingCellConfig", so that the terminal 10 has one It is also possible to apply when a BWP for communication is set. That is, in this case, when the value of the BWP indicator included in the DCI format is set to 1, it indicates that BWP for communication is specified.
  • FIG. 15B shows that when the value of the BWP indicator is set to 0, initial DLBWP and/or initial ULBWP are indicated. Also, when the value of the BWP indicator is set to 1, it indicates that DLBWP#1 and/or ULBWP#1 are indicated.
  • the definition shown in FIG. 15B can be applied when the base station 20 sets one or more DLBWP and ULBWP to the terminal 10 in "BWP-Downlink” and "BWP-Uplink” in "ServingCellConfig". can.
  • FIG. 15C shows that when the value of the BWP indicator is set to 0, initial DLBWP and/or initial ULBWP are indicated. Also, when the value of the BWP indicator is set to 1, it indicates that the BWP set using 'firstActiveDownlinkBWP-id' and 'firstActiveUplinkBWP-id' is specified.
  • the BWP indicator may be used to indicate the BWP-ID and/or the frequency position (position in the frequency domain) of the BWP.
  • the BWP indicator may be used to indicate one frequency position among multiple frequency positions of the configured BWP.
  • the base station 20 may include information for setting a plurality of frequency positions of the communication BWP in the RRC message and transmit the RRC message.
  • the base station 20 includes information (for example, BWP indicator) for indicating one frequency position among the plurality of frequency positions in the DCI format (downlink assignment and/or uplink grant). You may send.
  • the base station 20 designates a first frequency position DLBWP-P1, a second frequency position DLBWP-P2, and a third frequency position DLBWP-P3 as a plurality of frequency positions for one DLBWP (DLBWP for communication). May be set. Also, the base station 20 transmits information (for example, BWP indicator) for indicating one frequency position out of the plurality of frequency positions (DLBWP-P1, DLBWP-P2, and DLBWP-P3) to the DCI (downlink). link assignment and/or uplink grant).
  • information for example, BWP indicator
  • DLBWP-P1 when 2-bit information is set in the DCI, "01" may indicate DLBWP-P1, "10” may indicate DLBWP-P2, and "11” may indicate DLBWP-P3.
  • the initial DLBWP when 2-bit information is set in the DCI, the initial DLBWP may be indicated by '00'. That is, information included in the downlink assignment and/or the uplink grant may be used to determine the frequency position of one DLBWP (DLBWP for communication).
  • the base station 20 designates a first frequency position ULBWP-P1, a second frequency position ULBWP-P2, and a third frequency position ULBWP-P3 as a plurality of frequency positions for one ULBWP (ULBWP for communication). May be set. Also, the base station 20 transmits information (for example, BWP indicator) for indicating one frequency position among the plurality of frequency positions (ULBWP-P1, ULBWP-P2, and ULBWP-P3) to DCI (downlink). link assignment and/or uplink grant).
  • information for example, BWP indicator
  • '01' may indicate ULBWP-P1
  • '10' may indicate ULBWP-P2
  • '11' may indicate ULBWP-P3.
  • the initial ULBWP may be indicated by '00'. That is, information included in the downlink assignment and/or the uplink grant may be used to determine the frequency position of one ULBWP (communication ULBWP).
  • the base station 20 sets a plurality of frequency positions for one DLBWP (DLBWP for communication) and a plurality of frequency positions for one ULBWP (ULBWP for communication), DCI (downlink assignment and/or Information (eg, BWP indicator) included in the uplink grant) may be used to indicate one frequency location for DLBWP and one frequency location for ULBWP. That is, the frequency position of one DLBWP (DLBWP for communication) and the frequency position of one ULBWP (DLBWP for communication) may be switched at the same time.
  • DLBWP-P1 may correspond to ULBWP-P1 (eg, may be defined or configured as a pair).
  • DLBWP-P2 may correspond to ULBWP-P2
  • DLBWP-P3 may correspond to ULBWP-P3.
  • the frequency position of the one DLBWP corresponds to the frequency position of the one ULBWP.
  • 2-bit information is set in DCI
  • '01' indicates DLBWP-P1 and ULBWP-P1
  • '10' indicates DLBWP-P2 and ULBWP-P2
  • '11' indicates DLBWP.
  • -P3 and ULBWP-P3 may be indicated.
  • the terminal 10 may simultaneously switch between the DLBWP frequency position and the ULBWP frequency position with the same index based on the value set in the information.
  • '00' may indicate the initial DLBWP and the initial ULBWP. That is, the information included in the downlink assignment and/or the uplink grant is used to determine the frequency position of one DLBWP (DLBWP for communication) and the frequency position of one ULBWP (ULBWP for communication).
  • bit length (also referred to as the number of bits) of information used to indicate the BWP-ID and/or the BWP frequency position (for example, BWP indicator) is and/or the number of frequency positions set for one ULBWP (DLBWP for communication).
  • bit length of the information included in the downlink assignment may be determined based on the number of frequency positions set for one DLBWP (DLBWP for communication).
  • bit length of the information included in the uplink grant may be determined based on the number of frequency positions set for one ULBWP (DLBWP for communication).
  • bit length of the information included in the downlink assignment and / or uplink grant is the number of frequency positions set for one DLBWP (DLBWP for communication) and one ULBWP (DLBWP for communication ) may be determined based on the larger number of the number of frequency positions set for ).
  • the terminal 10 may switch between both DLBWP and ULBWP.
  • the terminal 10 may switch between both DLBWP and ULBWP.
  • the terminal 10 may switch DLBWP. Also, when the DCI for allocating uplink resources includes the BWP indicator shown in FIG. 15, the terminal 10 may switch between ULBWPs. Also, one DCI may include both a BWP indicator that specifies DLBWP and a BWP indicator that specifies ULBWP. Also, the base station 20 may set information indicating whether or not the BWP indicator is included in the DCI in the terminal 10 in an RRC message or SIB.
  • DCI format 0_0, DCI format 0_1, DCI format 0_2, DCI format 1_0, DCI format 1_1, DCI format 1_2 and new DCI formats for RedCap terminals have a 1-bit BWP indicator.
  • the definition shown in FIG. 15 may be applied.
  • the terminal 10 may recognize that the BWP indicator has 1 bit when a BWP other than the initial BWP is set in the terminal 10 .
  • the BWP indicator may be fixed to 1 bit.
  • BWP switching by PDCCH can be used even when terminal-specific settings are not made in the initial BWP. This enables switching of BWP without using an RRC message, thereby reducing signaling overhead.
  • FIG. 16 is a diagram illustrating an example of the hardware configuration of each device within the wireless communication system.
  • Each device in the wireless communication system 1 eg, terminal 10, base station 20, core network 30, etc.
  • the processor 11 is, for example, a CPU (Central Processing Unit) and controls each device within the wireless communication system 1 .
  • the processor 11 may read and execute the program from the storage device 12 to execute various processes described in this embodiment.
  • Each device within the wireless communication system 1 may be configured with one or more processors 11 .
  • Each device may also be called a computer.
  • the storage device 12 is composed of storage such as memory, HDD (Hard Disk Drive) and/or SSD (Solid State Drive).
  • the storage device 12 may store various types of information necessary for execution of processing by the processor 11 (for example, programs executed by the processor 11, etc.).
  • the communication device 13 is a device that communicates via a wired and/or wireless network, and may include, for example, network cards, communication modules, chips, antennas, and the like. Further, the communication device 13 may include an amplifier, an RF (Radio Frequency) device that performs processing related to radio signals, and a BB (BaseBand) device that performs baseband signal processing.
  • RF Radio Frequency
  • BB BaseBand
  • the RF device for example, performs D/A conversion, modulation, frequency conversion, power amplification, etc. on the digital baseband signal received from the BB device to generate a radio signal to be transmitted from the antenna. Further, the RF device generates a digital baseband signal by performing frequency conversion, demodulation, A/D conversion, etc. on the radio signal received from the antenna, and transmits the digital baseband signal to the BB device.
  • the BB device performs a process of converting a digital baseband signal into a packet and a process of converting the packet into a digital baseband signal.
  • the input/output device 14 includes input devices such as keyboards, touch panels, mice and/or microphones, and output devices such as displays and/or speakers.
  • Each device in the wireless communication system 1 may omit part of the hardware shown in FIG. 12, or may include hardware not shown in FIG. Also, the hardware shown in FIG. 12 may be configured by one or a plurality of chips.
  • FIG. 17 is a diagram showing an example of the functional configuration of the terminal 10.
  • Terminal 10 includes receiver 101 , transmitter 102 , and controller 103 . All or part of the functions realized by the receiving unit 101 and the transmitting unit 102 can be realized using the communication device 13 . All or part of the functions realized by the receiving unit 101 and the transmitting unit 102 and the control unit 103 can be realized by the processor 11 executing a program stored in the storage device 12 . Also, the program can be stored in a storage medium.
  • the storage medium storing the program may be a non-transitory computer readable medium.
  • the non-temporary storage medium is not particularly limited, but may be a storage medium such as a USB memory or CD-ROM, for example.
  • the RedCap terminal is an example of a specific terminal.
  • PUCCH is an example of an uplink control channel.
  • PUCCH parameters and/or PDCCH parameters are an example of control channel resource configuration.
  • PDCCH is an example of a physical downlink control channel.
  • DCI is an example of a physical downlink control channel signal.
  • UE Capability is an example of terminal capability.
  • CommunicateDownlinkBWP-id or firstActiveDownlinkBWP-id is an example of communication DLBWP setting.
  • CommunicateUplinkBWP-id or firstActiveUplinkBWP-id is an example of communication ULBWP setting.
  • the receiving unit 101 receives the downstream signal. Also, the receiving section 101 may receive information and/or data transmitted via a downlink signal. Here, “receiving” may include, for example, performing processing related to reception such as at least one of receiving, demapping, demodulating, decoding, monitoring, and measuring radio signals.
  • the receiving unit 101 receives an RRC message including communication DLBWP (Downlink BandWidth Part) and communication ULBWP (Uplink BandWidth Part) settings set for a specific terminal from the base station 20. Further, receiving section 101 receives from base station 20 an RRC message that does not include terminal-specific control channel resource settings for initial BWP and that includes communication BWP settings that are set for specific terminals.
  • the RRC message may be, for example, an RRC reconfiguration message, an RRC resume message (RRCResume), an RRC setup message, or the like.
  • the transmission unit 102 transmits an upstream signal. Also, the transmitting section 102 may transmit information and/or data transmitted via an uplink signal. Here, “transmitting” may include performing processing related to transmission, such as at least one of encoding, modulation, mapping, and transmission of radio signals. Also, the transmission unit 102 transmits a scheduling request to the base station 20 in the active ULBWP. More specifically, when a scheduling request is triggered by the control unit 103, the transmitting unit 102 transmits the scheduling request by radio signal. Further, after the active ULBWP is switched to the communication ULBWP, the transmission unit 102 transmits a scheduling request to the base station 20 using the terminal-specific uplink control channel resource set in the communication ULBWP. can be
  • transmitting section 102 sets the terminal-specific uplink control channel resource set in the initial ULBWP. may be used to transmit the scheduling request to the base station 20 .
  • the transmission unit 102 may execute the random access procedure in the communication ULBWP and the communication DLBWP.
  • the control unit 103 performs a process of setting the BWP notified by the SIB and RRC message to the terminal 10, a process of activating the set BWP, and a process of switching the activated BWP. Further, when the control unit 103 detects a request to the base station 20 for resource allocation (uplink scheduling) for transmitting uplink data, it triggers the transmission unit 102 to transmit a scheduling request.
  • resource allocation uplink scheduling
  • the control unit 103 when the control unit 103 requests the base station 20 to allocate resources for transmitting uplink data, if terminal-specific uplink control channel resources are not set in the active ULBWP, the active ULBWP to ULBWP for communication. Further, when the active ULBWP is the initial ULBWP and no terminal-specific uplink control channel resource is set in the initial ULBWP, the control unit 103 switches the active ULBWP to the communication ULBWP. good too. In addition to switching the active ULBWP to the communication ULBWP, the control unit 103 may switch the active DLBWP to the communication DLBWP.
  • control unit 103 may switch the active ULBWP to the communication ULBWP after the scheduling request is transmitted. For example, the control unit 103 may switch the active ULBWP to the communication ULBWP after the scheduling request is transmitted (or triggered) in the initial ULBWP.
  • control unit 103 may switch the active DLBWP to the communication DLBWP after the scheduling request is transmitted (or after the scheduling request transmission is triggered). Further, after the transmission unit 102 transmits the scheduling request in the active ULBWP (or after triggering the transmission of the scheduling request in the active ULBWP), the control unit 103 determines that the active DLBWP is not the communication DLBWP. If not, the DLBWP for communication may be switched to active.
  • control unit 103 switches between the initial BWP and the communication BWP as the active BWP based on the physical downlink control channel signal that specifies either the initial BWP or the communication BWP. Further, the control unit 103 may switch between the initial ULBWP and the initial DLBWP as an active BWP based on the signal of the physical downlink control channel that specifies the initial BWP. The initial ULBWP may be switched as the active BWP based on the signal of the physical downlink control channel specifying the . Also, the control unit 103 may switch the initial DLBWP to an active BWP based on a physical downlink control channel signal specifying the initial DLBWP.
  • control unit 103 may switch the active BWP from the initial BWP to the communication BWP when triggering the random access procedure and when the PRACH opportunity is set in the communication ULBWP.
  • FIG. 18 is a diagram showing an example of the functional configuration of the base station 20.
  • Base station 20 includes receiver 201 , transmitter 202 , and controller 203 . All or part of the functions realized by the receiving unit 201 and the transmitting unit 202 can be realized using the communication device 13 . All or part of the functions realized by the receiving unit 201 and the transmitting unit 202 and the control unit 103 can be realized by the processor 11 executing a program stored in the storage device 12 . Also, the program can be stored in a storage medium.
  • the storage medium storing the program may be a computer-readable non-temporary storage medium.
  • the non-temporary storage medium is not particularly limited, but may be a storage medium such as a USB memory or CD-ROM, for example.
  • the receiving unit 201 receives an upstream signal. Also, the receiving section 201 may receive information and/or data transmitted via the uplink signal. Also, the receiving unit 101 receives information indicating the terminal capability of the terminal 10 from the terminal 10 . Further, when receiving section 101 does not configure the terminal-specific uplink control channel resource for terminal 10 in the initial ULBWP, the terminal 10 transmits using the terminal-specific uplink control channel resource configured in the communication ULBWP. When a scheduling request is received and a terminal-specific uplink control channel resource is set in the initial ULBWP, the scheduling request transmitted by the terminal-specific uplink control channel resource set in the initial ULBWP is received from the terminal 10. can be
  • the transmission unit 202 transmits a downlink signal. Also, the transmitting section 202 may transmit information and/or data transmitted via the downlink signal. Further, when the terminal 10 is indicated by the information indicating the terminal capability of the terminal 10 that the terminal 10 is a specific terminal, the transmitting section 202 transmits to the terminal 10 an RRC message including settings of the DLBWP for communication and the ULBWP for communication.
  • the RRC message may be, for example, an RRC reconfiguration message, an RRC restart message, an RRC setup message, or the like.
  • the transmitting section 202 does not include the setting of individual control channel resources for the initial BWP and sets for the specific terminal.
  • An RRC message containing the setting of the communication BWP to be set may be transmitted to the terminal 10 .
  • the transmitting section 102 may transmit a physical downlink control channel signal designating either the initial BWP or the communication BWP to the terminal.
  • the control unit 203 allocates uplink resources and downlink resources to the terminal 10, and the like. For example, when receiving a scheduling request from the terminal 10 , the control section 203 allocates resources for transmitting uplink data to the terminal 10 (uplink scheduling).
  • terminal-specific PUCCH parameters may be replaced with terminal-specific PUCCH resources.
  • the terms signal, information, signaling and message may be used interchangeably.
  • Various signals, information, and parameters in the above embodiments may be transmitted in any layer. That is, the various signals, information, and parameters are replaced with signals, information, and parameters of any layer such as higher layers (eg, NAS layer, RRC layer, MAC layer, etc.), lower layers (eg, physical layer), etc. good too. Further, the notification of the predetermined information is not limited to being performed explicitly, but may be performed implicitly (for example, by not notifying the information or using other information).
  • a slot may be named any unit of time having a predetermined number of symbols.
  • RB may be any name as long as it is a frequency unit having a predetermined number of subcarriers.
  • RRC messages may be referred to as RRC signaling.
  • the use of the terminal 10 in the above embodiment is not limited to those illustrated, as long as it has similar functions, any use (for example, eMBB, URLLC, Device-to- Device (D2D), Vehicle-to-Everything (V2X), etc.).

Landscapes

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

Abstract

L'invention concerne un terminal comprenant : une unité de réception qui reçoit d'une station de base, un message RRC qui ne comprend pas de configurations de ressources de canal de contrôle spécifiques au terminal pour une BWP initiale et comprend une configuration d'une BWP de communication qui est définie pour un terminal spécifique ; et une unité de commande qui commute entre la BWP initiale et la BWP de communication en tant que BWP active, sur la base d'un signal de canal physique de contrôle en liaison descendante spécifiant soit la BWP initiale, soit la BWP de communication.
PCT/JP2022/018099 2021-04-23 2022-04-19 Terminal, station de base et procédé de communication WO2022224942A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2021-073579 2021-04-23
JP2021073579A JP2022167642A (ja) 2021-04-23 2021-04-23 端末、基地局及び通信方法

Publications (1)

Publication Number Publication Date
WO2022224942A1 true WO2022224942A1 (fr) 2022-10-27

Family

ID=83723307

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2022/018099 WO2022224942A1 (fr) 2021-04-23 2022-04-19 Terminal, station de base et procédé de communication

Country Status (2)

Country Link
JP (1) JP2022167642A (fr)
WO (1) WO2022224942A1 (fr)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020142683A1 (fr) * 2019-01-04 2020-07-09 Cirik Ali Cagatay Procédure d'accès aléatoire en deux étapes dans des bandes sans licence

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020142683A1 (fr) * 2019-01-04 2020-07-09 Cirik Ali Cagatay Procédure d'accès aléatoire en deux étapes dans des bandes sans licence

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "Reduced maximum UE bandwidth for RedCap", 3GPP TSG RAN WG1 #104B-E ; R1-2102722, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), SOPHIA-ANTIPOLIS CEDEX ; FRANCE, 7 April 2021 (2021-04-07), e-Meeting; 20210412 - 20210420, XP052177715 *
HUAWEI, HISILICON: "Potential solutions for UE complexity reduction", 3GPP TSG RAN WG1 #104-E; R1-2100230, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), SOPHIA-ANTIPOLIS CEDEX ; FRANCE, 19 January 2021 (2021-01-19), E-meeting; 20210125 - 20210205, XP051970862 *

Also Published As

Publication number Publication date
JP2022167642A (ja) 2022-11-04

Similar Documents

Publication Publication Date Title
US11626952B2 (en) Signal configuration method and related device
US20200275308A1 (en) Method and apparatus for wireless communication
CN109587705B (zh) 通信方法、装置和系统
WO2021062612A1 (fr) Procédé et appareil de communication
US20160219574A1 (en) Method and Apparatus for Device to Device Communication
US11871376B2 (en) Paging operation with narrow bandwidth part frequency hopping
CN109792710A (zh) 一种信号传输方法、设备及系统
US9749987B2 (en) Mobile communication method and radio base station
CN112106423A (zh) 用于物理下行链路控制信道监测的方法、终端设备和基站
JP2024507648A (ja) ページングアーリーインジケーション技術
JP2023537283A (ja) 上りリンク信号の送受信方法及び装置
JP2023512807A (ja) 無線通信において、低減した能力のデバイスをサポートする方法及び装置
EP3142438B1 (fr) Procédé destiné à des communications entre dispositifs, station de base et équipement utilisateur
US20230403724A1 (en) Terminal, base station and wireless communication method
WO2020221313A1 (fr) Procédé et appareil de communication
JP2023501555A (ja) ユーザ装置、スケジューリングノード、ユーザ装置用の方法、およびスケジューリングノード用の方法
KR20220079545A (ko) 크로스슬롯 스케줄링 조정을 위한 디바이스 및 방법
JP7503656B2 (ja) リソース決定方法及び装置
WO2022022673A1 (fr) Procédé et dispositif de communication
WO2022224942A1 (fr) Terminal, station de base et procédé de communication
WO2022224941A1 (fr) Terminal, station de base et procédé de communication
JP2024519220A (ja) ユーザ機器、スケジューリングノード、ユーザ機器のための方法、スケジューリングノードのための方法および集積回路
CN111436085A (zh) 通信方法及装置
WO2023277026A1 (fr) Terminal et procédé de communication sans fil
WO2023277027A1 (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: 22791713

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

Country of ref document: EP

Kind code of ref document: A1