WO2023080160A1 - 通信装置、基地局及び通信方法 - Google Patents

通信装置、基地局及び通信方法 Download PDF

Info

Publication number
WO2023080160A1
WO2023080160A1 PCT/JP2022/040998 JP2022040998W WO2023080160A1 WO 2023080160 A1 WO2023080160 A1 WO 2023080160A1 JP 2022040998 W JP2022040998 W JP 2022040998W WO 2023080160 A1 WO2023080160 A1 WO 2023080160A1
Authority
WO
WIPO (PCT)
Prior art keywords
bwp
initial
bandwidth portion
base station
redcap
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/JP2022/040998
Other languages
English (en)
French (fr)
Japanese (ja)
Inventor
大輝 前本
秀明 ▲高▼橋
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Denso Corp
Toyota Motor Corp
Original Assignee
Denso Corp
Toyota Motor Corp
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 Denso Corp, Toyota Motor Corp filed Critical Denso Corp
Priority to EP22889980.3A priority Critical patent/EP4429388A4/en
Priority to JP2023558052A priority patent/JP7680559B2/ja
Priority to CN202280071292.0A priority patent/CN118160400A/zh
Publication of WO2023080160A1 publication Critical patent/WO2023080160A1/ja
Priority to US18/649,784 priority patent/US20240283620A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signalling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signalling for the administration of the divided path, e.g. signalling of configuration information
    • H04L5/0094—Indication of how sub-channels of the path are allocated
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H04W48/12—Access restriction or access information delivery, e.g. discovery data delivery using downlink control channel
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H04W68/02—Arrangements for increasing efficiency of notification or paging channel
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0453—Resources in frequency domain, e.g. a carrier in FDMA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access

Definitions

  • the present disclosure relates to a communication device, base station and communication method used in a mobile communication system.
  • a portion of the total bandwidth of a cell and at least the initial bandwidth portion used for initial access is set in communication devices.
  • 3rd Generation Partnership Project 3rd Generation Partnership Project
  • a method for setting the initial bandwidth portion a method is defined in which the initial bandwidth portion is not set by dedicated signaling but is set by common signaling (see Non-Patent Document 1).
  • the initial bandwidth portion set by common signaling is set in the communication device as a bandwidth portion with a bandwidth portion number of 0 (specifically, BWP#0).
  • BWP#0 is not considered a bandwidth portion configured by Radio Resource Control (RRC).
  • RRC Radio Resource Control
  • the bandwidth parts (BWP#1 to BWP#4) with a bandwidth part number of 1 and higher are bandwidth parts set by dedicated signaling and bandwidth parts set by RRC.
  • RedCap UE a communication device having reduced communication capacity compared to a general communication device (hereinafter appropriately referred to as a general communication device) has been added to the 5G system.
  • Redcap UE is a communication device with middle-range performance and price for IoT (Internet of Things).
  • IoT Internet of Things
  • the initial bandwidth portion for redcap UE that is, the initial bandwidth portion narrower than the initial bandwidth portion for general communication devices (hereinafter , where appropriate called a separate initial bandwidth portion) to be set independently of the initial bandwidth portion for general communication devices (see Non-Patent Document 2).
  • a communication device is a communication device having reduced communication capacity compared to other communication devices.
  • the communication device designates a predetermined bandwidth portion number other than the bandwidth portion number for which the initial bandwidth portion used by the other communication device is set, and sets a separate initial bandwidth portion different from the initial bandwidth portion. and a control unit for executing a random access procedure using the separate initial bandwidth part.
  • a base station is a base station that communicates with a communication device having reduced communication capacity compared to other communication devices.
  • the base station designates a predetermined bandwidth portion number other than the bandwidth portion number for which the initial bandwidth portion used for the other communication device is set, and sets a separate initial bandwidth portion different from the initial bandwidth portion. and a control unit for executing a random access procedure with the communication device using the separate initial bandwidth part.
  • a communication method is a communication method performed by a communication device having reduced communication capacity compared to other communication devices.
  • a separate initial bandwidth portion different from the initial bandwidth portion is specified by specifying a predetermined bandwidth portion number other than the bandwidth portion number for which the initial bandwidth portion used for the other communication device is set. and performing a random access procedure using the separate initial bandwidth portion from the base station in a system information block.
  • FIG. 1 is a diagram showing the configuration of a mobile communication system according to an embodiment.
  • FIG. 2 is a diagram illustrating a configuration example of a protocol stack according to the embodiment;
  • FIG. 3 is a diagram for explaining a method of setting an initial BWP to a UE.
  • FIG. 4 is a diagram showing the configuration of the UE according to the embodiment.
  • FIG. 5 is a diagram showing the configuration of a base station according to the embodiment.
  • FIG. 6 is a sequence diagram for explaining an operation example of the mobile communication system according to the embodiment.
  • FIG. 7 is a diagram (part 1) for explaining the frequency domain according to the first operation example of the mobile communication system according to the embodiment.
  • FIG. 8 is a diagram (part 2) for explaining the frequency domain according to the first operation example of the mobile communication system according to the embodiment.
  • FIG. 9 is a diagram for explaining a method of setting an initial BWP to a UE in the mobile communication system according to the embodiment.
  • FIG. 10 is a diagram (part 1) for explaining information elements of the mobile communication system according to the embodiment.
  • FIG. 11 is a diagram (part 2) for explaining information elements of the mobile communication system according to the embodiment.
  • FIG. 12 is a diagram (part 3) for explaining information elements of the mobile communication system according to the embodiment.
  • FIG. 13 is a diagram for explaining the frequency domain according to the second operation example of the mobile communication system according to the embodiment.
  • FIG. 14 is a diagram for explaining the frequency domain according to the third operation example of the mobile communication system according to the embodiment.
  • FIG. 15 is a diagram for explaining the frequency domain according to the fourth operation example of the mobile communication system according to the embodiment.
  • FIG. 16 is a diagram for explaining the frequency domain according to the fifth operation example of the mobile communication system according to the embodiment.
  • FIG. 17 is a diagram for explaining the frequency domain according to the sixth operation example of the mobile communication system according to the embodiment.
  • FIG. 18 is a diagram (part 1) for explaining information elements of a mobile communication system according to another embodiment.
  • FIG. 19 is a diagram (part 2) for explaining information elements of a mobile communication system according to another embodiment.
  • redcap UE can perform initial access in the initial bandwidth portion used for general communication devices, common signaling sets the bandwidth portion with a bandwidth portion number of 0 (BWP#0) to the redcap UE.
  • BWP#0 bandwidth portion number of 0
  • a separate initial bandwidth portion is set for redcap UEs as a bandwidth portion set by RRC (ie, a predetermined bandwidth portion with a bandwidth portion number of 1 or higher).
  • the bandwidth portion set by RRC is set by dedicated signaling, so redcap UEs can use a separate initial bandwidth portion after initial access. Therefore, there is a problem that redcap UEs cannot use a separate initial bandwidth portion for performing random access procedures during initial access. Accordingly, the present disclosure provides a communication device capable of using a separate initial bandwidth portion during initial access when the initial bandwidth portion is set as a bandwidth portion with a bandwidth portion number of 0 by common signaling,
  • One object is to provide a base station and a communication method.
  • the mobile communication system 1 is, for example, a system conforming to 3GPP Technical Specifications (TS).
  • TS 3GPP Technical Specifications
  • a mobile communication system based on the 3GPP standard 5th Generation System (5G system), that is, NR (New Radio) will be described as an example.
  • the mobile communication system 1 has a network 10 and user equipment (UE) 100 communicating with the network 10 .
  • the network 10 includes an NG-RAN (Next Generation Radio Access Network) 20, which is a 5G radio access network, and a 5GC (5G Core Network) 30, which is a 5G core network.
  • NG-RAN Next Generation Radio Access Network
  • 5G Core Network 5G Core Network
  • the UE 100 is an example of a communication device.
  • the UE 100 may be a mobile wireless communication device.
  • UE 100 may be a communication device that communicates via base station 200 .
  • UE 100 may be a device used by a user.
  • the UE 100 may be a user equipment defined by 3GPP technical specifications.
  • the UE 100 is, for example, a portable device such as a mobile phone terminal such as a smart phone, a tablet terminal, a notebook PC, a communication module, or a communication card.
  • the UE 100 may be a vehicle (eg, car, train, etc.) or a device provided therein.
  • the UE 100 may be a transport body other than a vehicle (for example, a ship, an airplane, etc.) or a device provided thereon.
  • the UE 100 may be a sensor or a device attached thereto.
  • the UE 100 includes a mobile station, a mobile terminal, a mobile device, a mobile unit, a subscriber station, a subscriber terminal, a subscriber device, a subscriber unit, a wireless station, a wireless terminal, a wireless device, a wireless unit, a remote station, and a remote terminal. , remote device, or remote unit.
  • a general UE general user equipment: general UE
  • a red cap UE red Two types of UEs are assumed: cap UE 100B.
  • the general UE 100A has advanced communication capabilities such as high-speed, large-capacity (enhanced mobile broadband: eMBB) and ultra-reliable and low-latency communications (URLLC), which are features of NR. Therefore, the general UE 100A has higher communication capability than the redcap UE 100B.
  • General UE 100A may be referred to as a non-RedCap UE.
  • the general UE 100A may be an existing UE, that is, a UE before Release 16 (so-called legacy UE).
  • the redcap UE 100B is a UE with reduced equipment cost and complexity compared to the general UE 100A.
  • the red cap UE 100B is a UE 100 having middle-range performance and price for IoT, and for example, compared to the general UE 100A, the maximum bandwidth used for wireless communication is set narrower, or the number of receivers is smaller. do. Note that the receiver is sometimes called a reception branch.
  • the redcap UE 100B is sometimes referred to as a reduced capability NR device.
  • it is also described as a general UE or a redcap UE, but the general UE or the redcap UE in this embodiment is a UE. That is, the general UE in this embodiment may be replaced with a UE. Also, the redcap UE in this embodiment may be replaced with a UE.
  • the redcap UE 100B conforms to the LPWA (Low Power Wide Area) standard, such as LTE Cat. (Long Term Evolution UE Category) 1/1bis, LTE Cat. M1 (LTE-M), LTE Cat. It may be possible to communicate at a communication speed equal to or higher than the communication speed specified by NB1 (NB-IoT).
  • the redcap UE 100B may be able to communicate in a bandwidth equal to or greater than the bandwidth defined by the LPWA standard. Redcap UEs 100B may have limited bandwidth for communication compared to Rel-15 or Rel-16 UEs.
  • the maximum bandwidth supported by the redcap UE 100B (also referred to as UE maximum bandwidth) may be 20 MHz.
  • the maximum bandwidth supported by the redcap UE 100B may be 100 MHz.
  • a redcap UE 100B may have only one receiver for receiving radio signals.
  • the redcap UE 100B may be, for example, a wearable device, a sensor device, or the like.
  • NG-RAN 20 includes multiple base stations 200 .
  • Each base station 200 manages at least one cell.
  • a cell constitutes the minimum unit of a communication area.
  • One cell belongs to one frequency (carrier frequency).
  • the term “cell” may represent a radio communication resource and may also represent a communication target of UE 100 .
  • Each base station 200 can perform radio communication with the UE 100 residing in its own cell.
  • the base station 200 communicates with the UE 100 using the RAN protocol stack. Details of the protocol stack will be described later.
  • Base stations 200 are also connected to other base stations 200 (which may be referred to as adjacent base stations) via Xn interfaces.
  • Base station 200 communicates with neighboring base stations via the Xn interface.
  • the base station 200 also provides NR user plane and control plane protocol termination towards the UE 100 and is connected to the 5GC 30 via the NG interface.
  • gNodeB gNodeB
  • the 5GC 30 includes a core network device 300.
  • the core network device 300 includes, for example, AMF (Access and Mobility Management Function) and/or UPF (User Plane Function).
  • AMF Access and Mobility Management Function
  • UPF User Plane Function
  • AMF performs mobility management of UE100.
  • UPF provides functions specialized for U-plane processing.
  • the AMF and UPF are connected with the base station 200 via the NG interface.
  • the protocol of the radio section between the UE 100 and the base station 200 includes a physical (PHY) layer, a MAC (Medium Access Control) layer, an RLC (Radio Link Control) layer, a PDCP (Packet Data Convergence Protocol) layer, It has an RRC (Radio Resource Control) layer.
  • PHY physical
  • MAC Medium Access Control
  • RLC Radio Link Control
  • PDCP Packet Data Convergence Protocol
  • RRC Radio Resource Control
  • the PHY layer performs encoding/decoding, modulation/demodulation, antenna mapping/demapping, and resource mapping/demapping. Data and control information are transmitted between the PHY layer of the UE 100 and the PHY layer of the base station 200 via physical channels.
  • the MAC layer performs data priority control, retransmission processing by hybrid ARQ (HARQ: Hybrid Automatic Repeat reQuest), random access procedures, and the like. Data and control information are transmitted between the MAC layer of the UE 100 and the MAC layer of the base station 200 via transport channels.
  • the MAC layer of base station 200 includes a scheduler. The scheduler determines uplink and downlink transport formats (transport block size, modulation and coding scheme (MCS)) and allocation resources to the UE 100 .
  • MCS modulation and coding scheme
  • the RLC layer uses the functions of the MAC layer and PHY layer to transmit data to the RLC layer on the receiving side. Data and control information are transmitted between the RLC layer of the UE 100 and the RLC layer of the base station 200 via logical channels.
  • the PDCP layer performs header compression/decompression and encryption/decryption.
  • An SDAP (Service Data Adaptation Protocol) layer may be provided as an upper layer of the PDCP layer.
  • the SDAP (Service Data Adaptation Protocol) layer performs mapping between an IP flow, which is the unit of QoS (Quality of Service) control performed by the core network, and a radio bearer, which is the unit of AS (Access Stratum) QoS control.
  • the RRC layer controls logical channels, transport channels and physical channels according to radio bearer establishment, re-establishment and release.
  • RRC signaling for various settings is transmitted between the RRC layer of UE 100 and the RRC layer of base station 200 .
  • UE 100 When there is an RRC connection between the RRC of UE 100 and the RRC of base station 200, UE 100 is in the RRC connected state. If there is no RRC connection between the RRC of the UE 100 and the RRC of the base station 200, the UE 100 is in RRC idle state. When the RRC connection between the RRC of UE 100 and the RRC of base station 200 is suspended, UE 100 is in RRC inactive state.
  • the NAS layer located above the RRC layer in the UE 100 performs session management and mobility management for the UE 100.
  • NAS signaling is transmitted between the NAS layer of UE 100 and the NAS layer of core network device 300 .
  • the UE 100 has an application layer and the like in addition to the radio interface protocol.
  • Radio frame configuration In 5G systems, downlink and uplink transmissions are organized within a radio frame of 10 ms duration.
  • a radio frame consists of 10 subframes.
  • one subframe may be 1 ms.
  • one subframe may consist of one or more slots.
  • the number of symbols forming one slot is 14 for normal CP (Cyclic Prefix) and 12 for extended CP.
  • the number of slots forming one subframe changes according to the set subcarrier interval.
  • the number of slots per subframe is 1 (i.e., 14 symbols), and if the subcarrier spacing is set to 30 kHz, the subframe If the number of slots per subframe is 2 (i.e. 28 symbols) and the subcarrier spacing is set to 60kHz, the number of slots per subframe is 4 (i.e. 56 symbols) and the subcarrier spacing is 120kHz. is set, the number of slots per subframe is 8 (ie, 128 symbols). Also, when 60 kHz is set as the subcarrier spacing for the extended CP, the number of slots per subframe is 4 (that is, 48 symbols).
  • the number of slots forming one subframe is determined based on the subcarrier spacing set by base station 200 . Also, based on the subcarrier spacing set by base station 200, the number of symbols forming one subframe is determined. That is, based on the subcarrier interval set by base station 200, the number of symbols forming a 1 ms subframe is determined, and the length of each symbol (length in the time direction) changes.
  • BWP bandwidth portion
  • the base station 200 configures one or more BWPs for the UE100.
  • the base station 200 can notify the UE 100 of the BWP used for communication with the base station 200 (that is, the active BWP) among one or more set BWPs.
  • the base station 200 can transmit to the UE 100 an identifier indicating the BWP to be activated when executing the setting, that is, the BWP that is first used in communication with the base station 200 .
  • an inactive BWP for controlling switching from an active BWP to a BWP that is not an active BWP (hereinafter referred to as an inactive BWP) and switching from an inactive BWP to an active BWP (so-called BWP switching), for example, a physical downlink control channel (e.g., downlink link assignment, uplink assignment), timer (ie bwp-InactivityTimer), RRC signaling, or MAC entity.
  • a physical downlink control channel e.g., downlink link assignment, uplink assignment
  • timer ie bwp-InactivityTimer
  • RRC signaling for controlling switching from an active BWP to a BWP that is not an active BWP
  • MAC entity for example, a physical downlink control channel (e.g., downlink link assignment, uplink assignment), timer (ie bwp-InactivityTimer), RRC signaling, or MAC entity.
  • communication in BWP means transmission on the uplink shared channel (UL-SCH: Uplink-Shared Channel) in the BWP, and random access channel (RACH: Random Access Channel) in the BWP.
  • UL-SCH Uplink-Shared Channel
  • RACH Random Access Channel
  • Transmission of the physical random access channel (PRACH: Physical RACH) opportunity is set), monitoring of the physical downlink control channel (PDCCH: Physical Downlink Control Channel) in the BWP, physical uplink control channel in the BWP ( PUCCH: Physical Uplink Control Channel) transmission (when PUCCH resource is configured), channel state information (CSI: Channel State Information) report for the BWP, and downlink shared channel (DL-SCH) in the BWP : Downlink-Shared Channel).
  • PUCCH Physical Downlink Control Channel
  • CSI Channel State Information
  • the UL-SCH is a transport channel and is mapped to a physical uplink shared channel (PUSCH: Physical Uplink Shared Channel).
  • PUSCH Physical Uplink Shared Channel
  • Data transmitted on the UL-SCH is also referred to as UL-SCH data.
  • UL-SCH is a transport channel and is mapped to a physical downlink shared channel (PDSCH: Physical Downlink Shared Channel).
  • PDSCH Physical Downlink Shared Channel
  • Data transmitted on the DL-SCH is also referred to as DL-SCH data.
  • DL-SCH data For example, it may correspond to DL-SCH data and downlink user data.
  • the PUCCH is used to transmit uplink control information.
  • the uplink control information includes HARQ-ACK (Hybrid Automatic Repeat Request), CSI, and/or SR (Scheduling Request).
  • HARQ-ACK includes positive acknowledgment or negative acknowledgment.
  • PUCCH is used to transmit HARQ-ACK for PDSCH (that is, DL-SCH (DL-SCH data, downlink user data)).
  • DL-SCH data and/or downlink user data are also referred to as downlink transport blocks.
  • the BWP includes an initial bandwidth portion (initial BWP) and a bandwidth portion dedicated to each UE 100 (dedicated BWP).
  • the initial BWP is used at least for initial access of the UE 100 .
  • the initial BWP is commonly used by multiple UEs 100 .
  • the initial BWP is set using parameters common to multiple UEs 100 (cell-specific parameters).
  • the initial BWP includes an initial BWP for downlink communication (hereinafter referred to as initial downlink BWP (Initial DL BWP)) and an initial BWP for uplink communication (hereinafter referred to as initial uplink BWP (Initial UL BWP)).
  • initial downlink BWP Initial DL BWP
  • initial uplink BWP Initial UL BWP
  • the value of the identifier (ie, bwp-id) indicating each of the initial downlink BWP and the initial uplink BWP may be 0.
  • the UE 100 can specify (set) the initial BWP (that is, the initial downlink BWP and the initial uplink BWP) by, for example, two methods.
  • the UE 100 identifies the initial BWP based on CORESET#0, which is set using information contained in the master information block (MIB) within the physical broadcast channel (PBCH).
  • the UE 100 identifies the initial BWP based on the location and bandwidth in the frequency domain that are set using information included in the system information block (SIB).
  • SIB system information block
  • UE 100 may apply the BWP identified by the first method to communication with base station 200, for example, until reception of message 4 (MSG4) in the random access procedure.
  • MSG4 message 4
  • message 4 in the random access procedure may include an RRC setup message, an RRC resume message and/or an RRC (re)establishment message.
  • a dedicated BWP is set exclusively for the UE 100.
  • the dedicated BWP includes a dedicated BWP for downlink communication (hereinafter referred to as a dedicated downlink BWP (UE dedicated DL BWP)) and a dedicated BWP for uplink communication (hereinafter referred to as a dedicated uplink BWP (UE dedicated UL BWP)).
  • a dedicated downlink BWP UE dedicated DL BWP
  • UE dedicated uplink BWP UE dedicated UL BWP
  • the value of the identifier indicating each of the dedicated downlink BWP and the dedicated uplink BWP may be other than 0.
  • a dedicated BWP is configured based on information included in the RRC message (eg, information for BWP downlink (ie, BWP-Downlink) and information for uplink BWP (ie, BWP-Uplink)).
  • information for BWP downlink (ie, BWP-Downlink) and information for uplink BWP (ie, BWP-Uplink) may be included.
  • information for dedicated downlink BWP and the information for dedicated uplink BWP for example, information indicating the position and bandwidth in the frequency domain (eg, locationAndBadwidth), information indicating subcarrier spacing (eg, subcarrierSpacing), and extension
  • At least one of information indicating a cyclic prefix (eg, cyclicPrefix) may be included.
  • the UE 100 can monitor the PDCCH using the set BWP.
  • PDCCH monitoring is DL BWP (e.g., activated DL BWP) in a serving cell (e.g., activated serving cell) in which PDCCH monitoring (monitoring) is configured according to the corresponding search space set, one or more may mean monitoring the set of PDCCH candidates in the control resource set (CORESET(s): Control Resource Set(s)).
  • PDCCH monitoring may include decoding each of the PDCCH candidates according to a monitored downlink control information (DCI) format.
  • DCI downlink control information
  • the UE 100 may monitor a DCI format to which a CRC (Cyclic Redundancy Check, also referred to as a CRC parity bit) scrambled by an RNTI (Radio Network Temporary Identifier) set by the base station 200 is added.
  • RNTI is SI-RNTI (System Information-RNTI), RA-RNTI (Random Access RNTI), TC-RNTI (Temporary C-RNTI), P-RNTI (Paging RNTI), and/or C-RNTI (Cell-RNTI) may be included.
  • a set of PDCCH candidates monitored by the UE 100 may be defined as a PDCCH search space set.
  • the search space set includes a common search space set (CSS set(s): Common Search Space set(s)) and/or a UE-specific search space set (USS set(s): UE Specific Search Space set(s)). It's okay. Therefore, the base station 200 configures the CORESET and/or search space set to the UE 100, and the UE 100 may monitor the PDCCH in the configured CORESET and/or search space set.
  • the UE 100 uses Type 0-PDCCH CSS set (Type 1-PDCCH CSS set), Type 1-PDCCH CSS set (Type 2-PDCCH CSS set), Type 2-PDCCH CSS set (Type 3-PDCCH CSS set), and USS PDCCH candidates may be monitored in at least one search space set of the set (USS set).
  • Type 1-PDCCH CSS set Type 1-PDCCH CSS set
  • Type 2-PDCCH CSS set Type 2-PDCCH CSS set
  • USS PDCCH candidates may be monitored in at least one search space set of the set (USS set).
  • Type 0 - PDCCH CSS set is PDCCH for DCI format with added CRC scrambled by pdcch-ConfigSIB1 in Master Information Block (MIB), by searchSpaceSIB1 in PDCCH-ConfigCommon, or by SI-RNTI - Set in UE 100 by searchSpaceZero in ConfigCommon.
  • Type 1-PDCCH CSS set is set in UE 100 by ra-SearchSpace in PDCCH-ConfigCommon for DCI format with CRC scrambled by RA-RNTI or TC-RNTI.
  • Type 2-PDCCH CSS set is set in UE 100 by pagingSearchSpace in PDCCH-ConfigCommon for DCI format with added CRC scrambled by P-RNTI.
  • the USS set is set in the UE 100 by the SearchSpace in the PDCCH-Config whose searchSpaceType for the DCI format to which the CRC scrambled by the C-RNTI is attached is ue-Specific.
  • Execution of SI (system information) transmission/reception may include setting the corresponding CORESET and/or search space set (eg, type 1-PDCCH CSS set) in the UE 100. Also, when performing SI transmission/reception, PDCCH (it may be a DCI format with a CRC scrambled by SI-RNTI) is monitored in the corresponding CORESET and/or search space set (type 1-PDCCH CSS set). may include
  • Execution of the random access (RA) procedure may include the corresponding CORESET and/or search space set (eg, type 1-PDCCH CSS set) being configured in the UE 100. Also, the execution of the RA procedure may be DCI format with CRC scrambled by PDCCH (RA-RNTI and/or TC-RNTI in the corresponding CORESET and/or search space set (type 1-PDCCH CSS set) ) is monitored.
  • RA-RNTI and/or TC-RNTI in the corresponding CORESET and/or search space set (type 1-PDCCH CSS set)
  • Execution of paging may include setting the corresponding CORESET and/or search space set (eg, type 2-PDCCH CSS set) in the UE 100.
  • the execution of paging confirms that the PDCCH (which may be a DCI format with a CRC scrambled by P-RNTI) is monitored in the corresponding CORESET and/or search space set (type 2-PDCCH CSS set). may contain.
  • the initial BWP set by common signaling is set in the UE 100 as a BWP with a BWP number of 0 (specifically, BWP#0).
  • BWP#0 the initial BWP (BWP#0) is set by BWP-DownlinkCommon and BWP-UplinkCommon in ServingCellConfigCommon, but not by BWP-DownlinkDedicated or BWP-UplinkDedicated in ServingCellConfig.
  • BWP#0 is not considered a BWP configured by Radio Resource Control (RRC).
  • RRC Radio Resource Control
  • BWPs with a BWP number of 1 or later are BWPs (dedicated BWPs) set by dedicated signaling and are BWPs set by RRC.
  • the initial BWP for the red cap UE 100B that is, the initial BWP with a narrower bandwidth than the initial BWP for the general UE 100A (hereinafter referred to as a separate initial BWP as appropriate) ) is set independently of the initial BWP for general UE 100A.
  • the redcap UE 100B can perform initial access in the initial BWP used by the general UE 100A, by common signaling, after setting the BWP (BWP#0) with a BWP number of 0 to the redcap UE, RRC It is assumed that a separate initial BWP is set in the redcap UE 100B as a BWP set by (that is, a predetermined BWP with a BWP number of 1 or later).
  • the BWP set by RRC is set by dedicated signaling, so the redcap UE 100B can use a separate initial BWP after initial access. Therefore, there is a problem that the redcap UE 100B cannot use the separate initial BWP to perform random access procedures during initial access.
  • the initial BWP is set as a BWP with a BWP number of 0 by common signaling, operations for enabling the use of a separate initial BWP during initial access will be described.
  • UE 100 includes communication unit 120 and control unit 140 .
  • the communication unit 120 performs wireless communication with the base station 200 by transmitting and receiving wireless signals to and from the base station 200 .
  • the communication unit 120 has at least one reception unit 121 and at least one transmission unit 122 .
  • the receiving section 121 and the transmitting section 122 may be configured including an antenna and an RF circuit.
  • the antenna converts a signal into radio waves and radiates the radio waves into space. Also, the antenna receives radio waves in space and converts the radio waves into signals.
  • the RF circuitry performs analog processing of signals transmitted and received through the antenna.
  • the RF circuitry may include high frequency filters, amplifiers, modulators, low pass filters, and the like.
  • the receiving unit 121 may be called a receiver (RX: Receiver).
  • the transmitter 122 may be referred to as a transmitter (TX).
  • TX transmitter
  • the number of receivers included in the communication unit 120 may be two to four.
  • the UE 100 is the redcap UE 100B, the number of receivers included in the communication unit 120 may be one or two.
  • the control unit 140 performs various controls in the UE 100.
  • the control unit 140 controls communication with the base station 200 via the communication unit 120 .
  • the operation of the UE 100 which will be described later, may be an operation under the control of the control unit 140.
  • the control unit 140 may include at least one processor capable of executing a program and a memory that stores the program.
  • the processor may execute a program to operate the controller 140 .
  • Control unit 140 may include a digital signal processor that performs digital processing of signals transmitted and received through the antenna and RF circuitry.
  • the digital processing includes processing of the protocol stack of the RAN. Note that the memory stores programs executed by the processor, parameters related to the programs, and data related to the programs.
  • the memory is ROM (Read Only Memory), EPROM (Erasable Programmable Read Only Memory), EEPROM (Electrically Erasable Programmable Read Only Memory), RAM (Random Access Mem ory) and flash memory. All or part of the memory may be included within the processor.
  • the receiving unit 121 sets the initial BWP used in the general UE 100A to a predetermined BWP number other than the BWP number
  • Common setting information for specifying a number and setting a separate initial BWP different from the initial BWP is received from the base station 200 in SIB.
  • the control unit 140 performs a random access procedure using separate initial BWP.
  • BWP#0 used for the general UE 100A is set by the common signaling to the redcap UE 100B
  • the redcap UE 100B has a predetermined BWP based on the common setting information received in the system information block.
  • a separate initial BWP can be set as the BWP of the number.
  • the redcap UE 100B can use separate initial BWP during initial access.
  • the operation of the functional unit (specifically, at least one of the communication unit 120 and the control unit 140) included in the UE 100 may be described as the operation of the UE 100.
  • the base station 200 has a radio communication section 220 , a network communication section 230 and a control section 240 .
  • the wireless communication unit 220 communicates with the UE 100 via the antenna.
  • the radio communication unit 220 has a receiving unit 221 and a transmitting unit 222 .
  • the receiving section 221 converts a radio signal received by the antenna into a received signal that is a baseband signal, performs signal processing on the received signal, and outputs the received signal to the control section 240 .
  • the transmission unit 222 performs signal processing on a transmission signal, which is a baseband signal output from the control unit 240, converts the signal into a radio signal, and transmits the radio signal from an antenna.
  • the network communication unit 230 transmits and receives signals to and from the network.
  • the network communication unit 230 receives signals from adjacent base stations connected via an Xn interface, which is an interface between base stations, and transmits signals to the adjacent base stations. Also, the network communication unit 230 receives a signal from the core network device 300 connected via the NG interface, for example, and transmits the signal to the core network device 300 .
  • the control unit 240 performs various controls in the base station 200.
  • the control unit 240 controls communication with the UE 100 via the radio communication unit 220, for example.
  • the control unit 240 controls communication with nodes (for example, adjacent base stations, the core network device 300) via the network communication unit 230, for example. Operations of the base station 200 described later may be operations under the control of the control unit 240 .
  • the control unit 240 may include at least one processor capable of executing programs and a memory that stores the programs.
  • the processor may execute a program to operate the controller 240 .
  • Control unit 240 may include a digital signal processor that performs digital processing of signals transmitted and received through the antenna and RF circuitry.
  • the digital processing includes processing of the protocol stack of the RAN.
  • the memory stores programs executed by the processor, parameters related to the programs, and data related to the programs. All or part of the memory may be included within the processor.
  • the base station 200 configured in this manner communicates with the UE 100 (red cap UE 100B) having reduced communication capability compared to the general UE 100A.
  • the transmitting unit 222 designates a predetermined BWP number other than the BWP number in which the initial BWP used for the general UE 100A is set, and sends common setting information for setting a separate initial BWP different from the initial BWP to the SIB.
  • Send with The control unit 240 performs a random access procedure with the redcap UE 100B using separate initial BWP.
  • the redcap UE 100B has a predetermined BWP based on the common setting information received in the system information block.
  • a separate initial BWP can be set as the BWP of the number.
  • the redcap UE 100B can use separate initial BWP during initial access.
  • the operation of the functional units (specifically, at least one of the wireless communication unit 220 (receiving unit 221 and/or transmitting unit 222), the network communication unit 230, and the control unit 240) included in the base station 200 is , may be described as operations of the base station 200 .
  • the redcap UE 100B may be in RRC idle state or RRC inactive state between the redcap UE 100B and the base station 200 (cell).
  • Step S101 The base station 200 (transmitting unit 222) transmits synchronization signals and physical broadcast channel blocks (hereinafter referred to as SSBs).
  • the redcap UE 100B (receiving unit 121) receives the SSB from the base station 200.
  • FIG. 1 The base station 200 (transmitting unit 222) transmits synchronization signals and physical broadcast channel blocks (hereinafter referred to as SSBs).
  • the redcap UE 100B receives the SSB from the base station 200.
  • the SSB consists of 4 OFDM (Orthogonal Frequency Division Multiplexing) symbols in the time domain, and consists of 240 consecutive subcarriers in the frequency domain.
  • the SSB is composed of a primary synchronization signal (hereinafter referred to as PSS), a secondary synchronization signal (hereinafter referred to as SSS), and a physical broadcast channel (PBCH).
  • PSS primary synchronization signal
  • SSS secondary synchronization signal
  • PBCH physical broadcast channel
  • Each of PSS and SSS occupies 1 OFDM symbol and 127 subcarriers.
  • the PBCH spans 3 OFDM symbols and 240 subcarriers.
  • the location of the resource element to which the SSB is mapped is specified in the specification.
  • the PBCH transmits the master information block (MIB).
  • the MIB contains a common control resource set (CORESET), a common search space and an information element (pdcch-ConfigSIB1) that determines the required PDCCH.
  • pdcch-ConfigSIB1 contains an information element (controlResourceSetZero) used to set CORESET#0 of the initial BWP.
  • controlResourceSetZero is indicated by an integer value from 0 to 15.
  • the base station 200 transmits multiple SSBs on different frequencies.
  • a plurality of SSBs are in the initial BWP (SIB1-Configured initial DL BWP for general UE 100A) used for general UE 100A set by system information block type 1 (SIB1) and red cap UE 100B set by SIB1.
  • SIB1-Configured initial DL BWP for RedCap UE100B located in the initial BWP for RedCap
  • SSB (Pattern 1) is located within the initial BWP (MIB-Configured initial DL BWP) set based on MIB1
  • SSB (Pattern 2/3) is set based on MIB1. outside the initial BWP.
  • the redcap UE 100B (control unit 140) can receive (that is, detect) the SSB transmitted from the base station 200 and synchronize time and/or frequency.
  • the redcap UE 100B acquires the MIB by receiving the SSB.
  • the redcap UE 100B sets the initial BWP based on CORESET#0 set based on the MIB.
  • the initial BWP (initial downstream BWP) set based on CORESET#0 may be referred to as "MIB Configured Initial DL BWP" or "Initial DL BWP derived by MIB”.
  • the initial BWP may be referred to as the MIB initial BWP.
  • the redcap UE 100B (control unit 140), for example, identifies the type 0-PDCCH CSS set (eg, bandwidth (24, 48, or 96 RB)) based on the setting value indicated by controlResourceSetZero in the MIB. As a result, the type 0-PDCCH CSS set is set in the redcap UE 100B (control unit 140).
  • the redcap UE 100B (control unit 140) monitors the system information block (specifically, SIB1) in the type 0-PDCCH CSS set using the MIB initial BWP.
  • Step S102 The base station 200 (transmitting section 222) transmits SIB1.
  • the redcap UE 100B (receiving unit 121) receives SIB1 from the base station 200.
  • SIB1 is transmitted in "SIBs" in FIG. Therefore, SIB1 is located within the MIB initial BWP.
  • SIBs not only SIB1 but also other SIBs may be transmitted.
  • SIB1 includes first common setting information (for example, a parameter indicating frequency location and/or bandwidth (locationAndBadwidth)) for setting the initial BWP used for general UE 100A (initial BWP for general UE 100A).
  • SIB1 includes an information element (ServingCellConfigCommonSIB) used to configure cell-specific parameters of the UE cell (serving cell).
  • ServingCellConfigCommonSIB contains, as the first common configuration information, an information element (BWP-DownlinkCommon) used to set common parameters for downlink BWP and an information element (BWP-UplinkCommon) used to set common parameters for uplink BWP. include.
  • the UE 100 sets the initial BWP based on BWP-DownlinkCommon and BWP-UplinkCommon in ServingCellConfigCommonSIB.
  • the initial BWP is the initial BWP for the general UE 100A and is set as a BWP with a BWP number of 0 (BWP#0).
  • BWP#0 is the initial BWP for general UE 100A, but redcap UE 100B may be available. That is, the initial BWP for the general UE 100A may be an initial BWP that can be shared by the general UE 100A and the redcap UE 100B.
  • an initial BWP for general UE 100A is set as a BWP with a BWP number of 0 (BWP#0) by common signaling.
  • SIB1 includes second common setting information for setting a separate initial BWP different from the initial BWP used for general UE 100A.
  • SIB1 includes an information element (ServingCellConfigCommonSIB) used to configure cell-specific parameters of the UE cell (serving cell).
  • ServingCellConfigCommonSIB includes an information element (DownlinkConfigCommonSIB) that provides common downlink parameters for cells.
  • DownlinkConfigCommonSIB includes second common setting information specifying a predetermined BWP number other than BWP number 0 (specifically, BWP number 1) and setting a separate initial BWP different from the initial BWP for general UE 100A.
  • DownlinkConfigCommonSIB includes an information element (downlinkBWP-One-r17: BWP-DownlinkCommon) indicating the configuration of downlink BWP#1 for the primary cell (PCell) as the second common configuration information.
  • the downlink BWP-One-r17 field When the downlink BWP-One-r17 field is set, the downlink BWP#1 may not include the entire CORESET#0 in the frequency domain. In this operation example, the downstream BWP#1 includes the entire CORESET#0 in the frequency domain.
  • the downlinkBWP-One-r17 field is a method for setting the initial BWP to the redcap UE 100B, in which the initial BWP is not set by dedicated signaling but is set by common signaling (so-called BWP setting option described in Appendix B.2. May optionally be present when supporting access from redcap UEs according to 1). Otherwise, the field may not exist.
  • ServingCellConfigCommonSIB includes information elements (uplinkConfigCommon-r17, supplementaryUplinkConfig-r17) for setting separate initial uplink BWP as second common setting information.
  • UplinkConfigCommon-r17 indicates the setting of separate initial BWP for normal uplink
  • supplementaryUplinkConfig-r17 indicates the setting of separate initial BWP for additional uplink.
  • Each of uplinkConfigCommon-r17 and supplementaryUplinkConfig-r17 indicates a separate initial uplink BWP configuration by an information element (UplinkConfigCommonSIB-r17) that provides common uplink parameters for the cell.
  • UplinkConfigCommonSIB-r17 an information element that provides common uplink parameters for the cell.
  • UplinkConfigCommon-r17 includes an information element (frequencyInfoUL-r17) indicating an absolute uplink frequency configuration and a subcarrier-specific virtual carrier, and an information element (initialUplinkBWP-r17) indicating an initial uplink BWP setting for the serving cell. ), a time alignment timer (timeAlignmentTimerCommon-r17), and an information element (uplinkBWP-One-r17) indicating the setting of uplink BWP#1 for the primary cell. If the uplinkBWP-One-r17 field is set, uplink BWP#1 may include PRACH opportunity, PUCCH, PUSCH, and SRS.
  • the fields of uplinkBWP-One-r17 are similar to those described above in Appendix B.1. 2. may optionally be present if supporting access from redcap UEs with BWP configuration option 1 as described in . Otherwise, the field may not exist.
  • the base station 200 transmits the second common setting information for setting the separate initial BWP (BWP#1) in SIB1.
  • the redcap UE 100B sets the initial BWP based on downlink BWP-One-r17 and uplink BWP-One-r17 in ServingCellConfigCommonSIB. As shown in FIG. 9, the initial BWP is set as a BWP with a BWP number of 1 (BWP#1).
  • the redcap UE 100B uses BWP #1 based on this setting when in the RRC idle state or RRC inactive state.
  • Step S103 The base station 200 and the redcap UE 100B may perform paging.
  • Base station 200 transmits PDCCH (DCI format (paging DCI) with CRC scrambled by P-RNTI) in the corresponding CORESET and/or search space set (type 2-PDCCH CSS set). Send.
  • the base station 200 may transmit the paging DCI using the separate initial BWP or using the MIB initial BWP.
  • the paging DCI is transmitted in the area located in the separate initial BWP and the MIB initial BWP (specifically, the area indicated by "Paging").
  • the paging DCI may contain scheduling information indicating scheduling of the PDSCH to transmit the paging message.
  • the base station 200 (transmitter 222) may transmit the paging message according to the scheduling indicated by the scheduling information.
  • the redcap UE 100B may monitor paging as execution of paging using separate initial BWP (BWP#1).
  • the redcap UE 100B may monitor the PDCCH (paging DCI) in the type 2-PDCCH CSS set in the separate initial BWP (BWP#1).
  • the redcap UE 100B may receive the paging message based on the scheduling information included in the paging DCI.
  • the redcap UE 100B (control unit 140) determines whether the paging message includes its own unique identifier. When the paging message includes its own identifier, the redcap UE 100B (control unit 140) may assume that there is a call, and may perform an operation to transition to the RRC connected state, for example.
  • the explanation will proceed assuming that a random access (RA) procedure is executed between the red cap UE 100B and the base station 200.
  • RA random access
  • the redcap UE 100B and the base station 200 perform a random access procedure using separate initial BWP.
  • Step S111 The redcap UE 100B (transmitting unit 122) transmits message 1 (hereinafter, MSG1) to the base station 200 using separate initial BWP.
  • MSG1 message 1
  • the base station 200 (receiving unit 221) receives MSG1 from the redcap UE 100B.
  • MSG1 message 1
  • PRACH physical random access channel
  • PRACH is transmitted in a separate initial BWP (SIB1-Configured initial UL BWP for RedCap UE100B).
  • the communication system is a time division duplex (TDD) system
  • the center frequency of the separate initial upstream BWP is the same as the center frequency of the separate initial downstream BWP.
  • the communication scheme is a frequency division duplex (FDD) scheme
  • the separate initial uplink BWP may be arranged at one end of the initial uplink BWP for general UE 100A in the frequency direction. Thereby, in the frequency direction, the initial uplink BWP for the general UE 100A is not separated by separate initial uplink BWPs. As a result, a wide resource area can be secured as the initial uplink BWP for the general UE 100A, and time-frequency resources can be effectively utilized.
  • the redcap UE 100B may determine whether the separate initial BWP frequency band includes the MIB initial BWP frequency band.
  • the redcap UE 100B (transmitting unit 122) may perform the random access procedure using the separate initial BWP or the MIB initial BWP when the separate initial BWP frequency band includes the MIB initial BWP frequency band. That is, the redcap UE 100B (transmitting unit 122) may transmit MSG1 using separate initial BWP or MIB initial BWP.
  • the redcap UE 100B (transmitting unit 122) may perform the random access procedure using the separate initial BWP if the frequency band of the separate initial BWP does not negate the frequency band of the MIB initial BWP. That is, the redcap UE 100B (transmitting unit 122) may transmit MSG1 using a separate initial BWP without using the MIB initial BWP.
  • Step S112 The base station 200 (transmitting unit 222) transmits message 2 (hereinafter referred to as MSG2) to the redcap UE 100B.
  • MSG2 is a random access (RA) response.
  • the redcap UE 100B (receiving unit 121) receives MSG2 from the base station 200.
  • FIG. 7 MSG2 is located in the area located in the separate initial BWP and the MIB initial BWP (specifically, the area indicated by "RA").
  • MSG2 includes, for example, preamble information indicating the RA preamble received from the redcap UE 100B, an uplink grant (UL grant) indicating the time-frequency resource used by the UE 100 to transmit message 3, and the like.
  • Time-frequency resources may be located at frequencies within a separate initial BWP.
  • the redcap UE 100B (control unit 140) that has received the RA response executes the process of step S113 when the RA preamble transmitted by itself matches the RA preamble indicated by the preamble information received from the base station 200 in step S102. do.
  • Step S113 The redcap UE 100B (transmitting unit 122) transmits message 3 (hereinafter referred to as MSG3) to the base station 200.
  • MSG3 message 3
  • the redcap UE 100B (transmitting unit 122) transmits MSG3 to the base station 200 in the time-frequency resource allocated by the uplink grant.
  • the base station 200 (receiving unit 221) receives MSG3 from the redcap UE 100B.
  • Step S114 The base station 200 (transmitting unit 222) transmits message 4 (hereinafter referred to as MSG4) to the redcap UE 100B.
  • Base station 200 transmits MSG4 using separate initial BWP.
  • the redcap UE 100B receives MSG4 from the base station 200 using separate initial BWP.
  • MSG4 may contain any RRC message, either an RRC setup message, an RRC resume message, or an RRC (re)establishment message.
  • the RRC message may include an information element (ServingCellConfig) used to configure (add or change) the serving cell to the UE 100.
  • ServingCellConfig includes an information element (downlink BWP-One-r17) indicating dedicated (UE-specific) settings for downlink BWP#1 and information indicating dedicated (UE-specific) settings for uplink BWP#1.
  • Downlink BWP-One-r17 and uplink BWP-One-r17 specify a predetermined BWP number (specifically, BWP number 1) other than BWP number 0, and use a dedicated BWP (BWP#1 ) may be dedicated setting information for setting Therefore, the base station 200 (transmitter 222) can transmit dedicated configuration information through dedicated signaling during the random access procedure.
  • the redcap UE 100B (receiving unit 121) can receive dedicated configuration information through dedicated signaling during the random access procedure.
  • the redcap UE 100B sets a dedicated BWP based on downlink BWP-One-r17 and uplink BWP-One-r17 in ServingCellConfig. As shown in FIG. 9, the dedicated BWP is set as a BWP with a BWP number of 1 (BWP#1). The redcap UE 100B (control unit 140) uses BWP#1 based on this setting when in the RRC connected state.
  • the redcap UE 100B transitions from the RRC idle state or RRC inactive state to the RRC connected state by a random access procedure. Thereafter, the redcap UE 100B (control unit 140) in the RRC connected state communicates with the base station 200 using dedicated BWP.
  • the base station 200 designates a predetermined BWP number other than the BWP number (that is, 0) in which the initial BWP used for the general UE 100A is set, and sets a separate initial BWP.
  • the second common setting information is transmitted in SIB1.
  • the redcap UE 100B receives the second common setting information from the base station 200 in SIB1.
  • the base station 200 (control unit 240) and the redcap UE 100B (control unit 140) use separate initial BWP to perform a random access procedure.
  • the redcap UE 100B can use separate initial BWP during initial access.
  • the red cap UE 100B designates a predetermined BWP number during the random access procedure, and transmits dedicated setting information for setting a dedicated BWP used in the RRC connected state from the base station 200 by dedicated signaling. may receive. This allows the redcap UE 100B (receiving unit 121) to use the separate initial BWP immediately after completing the random access procedure, that is, after receiving MSG4.
  • the redcap UE 100B may monitor paging using a separate initial BWP. This allows the redcap UE 100B to use the separate initial BWP even before executing the random access procedure.
  • the redcap UE 100B may perform the random access procedure using the separate initial BWP, and the frequency of the separate initial BWP If the band includes the frequency band of the MIB initial BWP, the random access procedure may be performed using separate initial BWP or MIB initial BWP.
  • the red cap UE 100B does not execute the random access procedure using the MIB initial BWP for the general UE 100A, It is possible to suppress the occurrence of interference with the general UE 100A.
  • the separate initial BWP is arranged at one end of the initial BWP for the general UE 100A in the frequency direction.
  • the separate initial downlink BWP is arranged at one end of the initial downlink BWP for the general UE 100A in the frequency direction.
  • the separate initial uplink BWP is arranged at one end of the initial uplink BWP for the general UE 100A in the frequency direction.
  • the communication system is the FDD system, the operation is the same as in the first operation example.
  • SSB is transmitted (hereinafter referred to as SSB area), CORESET#0, SIB is transmitted (hereinafter referred to as SIB area), an area (hereinafter referred to as paging area) in which paging (paging DCI) is transmitted, and an area (hereinafter referred to as RA area) in which RA response (MSG2) is transmitted are arranged there is Therefore
  • the UE 100 is configured for SSB, CORESET#0, SIB, and random access procedure so that separate initial BWP is used.
  • Cells in the separate initial BWP are considered redcap UE 100B specific cells.
  • the red cap UE 100B uses the separate initial BWP, for example, a random access procedure By executing, it is possible to suppress the occurrence of interference with the general UE 100A.
  • the redcap UE 100B (control unit 140) does not receive the common setting information for setting the separate initial BWP, the MIB initial BWP, which is the initial BWP set based on the MIB, is used to execute the random access procedure.
  • the MIB initial BWP is the MIB initial BWP for the redcap UE 100B
  • the redcap UE 100B executes the random access procedure using the MIB initial BWP, and the general UE 100A and interference can be suppressed.
  • redcap UE 100B (control unit 140) executes the random access procedure using the MIB initial BWP when the setting based on the common setting information is not completed even when the common setting information is received.
  • the red cap UE 100B (control unit 140) is when the common setting information for setting the separate initial BWP is not received, and the initial BWP for the general UE 100A set by SIB1 (that is, BWP #0) If the bandwidth exceeds the maximum bandwidth supported by the redcap UE 100B (which may be referred to as the UE maximum bandwidth), the MIB initial BWP may be used to perform the random access procedure.
  • the redcap UE 100B control unit 140
  • the bandwidth of the initial BWP for the general UE 100A does not exceed the maximum bandwidth supported by the redcap UE 100B.
  • the random access procedure may be performed using the initial BWP for general UE 100A.
  • the network 10 uses 24, 48, and 96 PRBs can be set, and the bandwidth of the initial BWP set by SIB1 is not limited to 24, 48, and 96 PRBs. Therefore, for example, if the bandwidth of the initial BWP set by SIB1 for the general UE 100A is wider than the bandwidth of the MIB initial BWP, by performing a random access procedure using the initial BWP for the general UE 100A , the occurrence of interference can be suppressed as compared with the case of using the MIB initial BWP.
  • the redcap UE 100B may monitor paging using a separate initial BWP. This allows the redcap UE 100B to use the separate initial BWP even before executing the random access procedure.
  • the red cap UE 100B (control unit 140), as in the third operation example described later, the initial BWP for the general UE 100A (specifically, the MIB initial BWP for the general UE 100A) to monitor the paging Compared to the above, it is possible to omit retuning between the MIB initial BWP for general UE 100A and the separate initial BWP for each paging, so the processing time associated with retuning is unnecessary, and retuning processing is performed. Power consumption caused by the load can be reduced.
  • Redcap UE 100B uses the initial BWP for general UE 100A (specifically, MIB initial BWP for general UE 100A) to acquire SIB1 and other SIBs, SIB1 and other SIBs to receive
  • the redcap UE 100B may use the initial BWP for the general UE 100A only when receiving the SIB, and when receiving other information (for example, SSB, paging DCI, etc.), the redcap UE 100B An initial BWP may be used.
  • the redcap UE 100B may use the initial BWP for the general UE 100A only when communication processing using the initial BWP for the redcap UE 100B cannot be executed, and the communication processing using the initial BWP for the redcap UE 100B is executed. If possible, the initial BWP for the redcap UE 100B may be used.
  • the redcap UE 100B uses the initial BWP for the general UE 100A to monitor paging in order to perform paging.
  • a fifth operation example will be described with reference to FIG. 16, mainly focusing on differences from the above-described operation example.
  • a CORESET, a paging area and an RA area are arranged in a separate initial BWP (SIB1-Configured initial DL BWP for RedCap UE100B).
  • the SSB area, CORESET#0, and SIB area are not arranged in the separate initial BWP.
  • the redcap UE 100B may use the separate initial BWP to monitor the set of PDCCH candidates in CORESET, monitor paging, and perform random access procedures.
  • the redcap UE 100B may use the MIB initial BWP for the general UE 100A when performing other processing (for example, receiving SSB, receiving SIB, etc.). Therefore, the redcap UE 100B may use the initial BWP for the general UE 100A only when communication processing using the initial BWP for the redcap UE 100B cannot be executed, and the communication processing using the initial BWP for the redcap UE 100B is executed. If possible, the initial BWP for the redcap UE 100B may be used.
  • the base station 200 when the initial BWP (specifically, downlink BWP #1) for the redcap UE 100B does not include the entire CORESET #0 in the frequency domain, the base station 200 (control unit 140) , in the DownlinkConfigCommonSIB, the field of the information element (downlinkBWP-One-r17) indicating the configuration of the downlink BWP#1 may be set, that is, the DownlinkConfigCommonSIB may include the downlinkBWP-One-r17.
  • the redcap UE 100B (control unit 140) may determine that the initial BWP for the redcap UE 100B does not include the entire CORESET#0 in the frequency domain. In this case, the redcap UE 100B (control unit 140) may use the MIB initial BWP for the general UE 100A to perform, for example, SSB reception, SIB reception, and the like.
  • the redcap UE 100B may use separate initial BWP to monitor the set of PDCCH candidates in CORESET and perform random access procedures.
  • the redcap UE 100B may use the MIB initial BWP for the general UE 100A when performing other processes (for example, reception of SSB, monitoring of paging, reception of SIB, etc.).
  • the base station 200 designates a predetermined BWP number other than BWP number 0 (for example, BWP number 1), and the RRC connected state in the target cell to be RRC-connected after handover. may be transmitted to the redcap UE 100B in the RRC connected state.
  • the RRC message may include an information element (ServingCellConfigCommon) used to configure cell-specific parameters of the serving cell (target cell) of the UE 100. As shown in FIGS.
  • ServingCellConfigCommon includes an information element (downlinkBWP-One-r17) indicating a dedicated (UE common) setting for downlink BWP#1 and a dedicated (UE common) setting for uplink BWP#1. and an information element (uplinkBWP-One-r17) indicating Therefore, the base station 200 (transmitting unit 222) can transmit the dedicated configuration information through dedicated signaling before the handover procedure from the source cell (serving cell) to which the redcap UE 100B is RRC-connected to the target cell is completed.
  • the redcap UE 100B (receiving unit 121) can communicate with the target cell using the BWP having a predetermined BWP number using the dedicated setting information during or after the handover procedure.
  • BWP number 1 was specified as a predetermined BWP number other than BWP number 0, but this is not the only option. Any from BWP number 2 to the maximum number of settings supported by the redcap UE 100B (up to 4 in existing 3GPP technical specifications) may be specified.
  • the SSB area, CORESET#0, SIB area, paging area, and RA area are included in the separate initial BWP for Redcap UE100B set by SIB1 (SIB1-Configured initial DL BWP for RedCap UE100B). If it is arranged (in the case of the second operation example), the base station 200 (transmitting unit 222) designates BWP number 0 without designating a predetermined BWP number other than BWP number 0, and performs separate initialization.
  • An SIB (for example, SIB1) including common setting information for setting the BWP may be transmitted to the redcap UE 100B.
  • Common configuration information may be, for example, BWP-DownlinkCommon and BWP-UplinkCommon in ServingCellConfigCommon.
  • the redcap UE 100B may set a separate initial BWP as BWP#0 based on the common setting information. In this case, the redcap UE 100B does not need to set the initial BWP for the general UE 100A based on the first common setting information as BWP#0 even if the SIB contains the first common setting information.
  • the base station 200 (control unit 240) can set the BWP to the redcap UE 100B by the operation described in the existing 3GPP technical specifications.
  • Base station 200 (transmitting unit 222) arranges at least one of the SSB area, CORESET#0, SIB area, paging area, and RA area in the separate initial BWP for redcap UE 100B set by SIB1. If not, the SIB including the first common setting information and the second common setting information may be transmitted as in the above-described embodiment.
  • the mobile communication system 1 based on NR has been described as an example.
  • the mobile communication system 1 may be a TS-compliant system of either LTE or another generation system (eg, 6th generation) of the 3GPP standard.
  • Base station 200 may be an eNB that provides E-UTRA user plane and control plane protocol termination towards UE 100 in LTE.
  • the mobile communication system 1 may be a system conforming to a TS of a standard other than the 3GPP standard.
  • the base station 200 may be an IAB (Integrated Access and Backhaul) donor or an IAB node.
  • IAB Integrated Access and Backhaul
  • the mobile communication system 1 based on NR has been described as an example.
  • the mobile communication system 1 is not limited to this example.
  • the mobile communication system 1 may be a TS-compliant system of either LTE or another generation system (eg, 6th generation) of the 3GPP standard.
  • Base station 200 may be an eNB that provides E-UTRA user plane and control plane protocol termination towards UE 100 in LTE.
  • the mobile communication system 1 may be a system conforming to a TS of a standard other than the 3GPP standard.
  • each operation flow described above is not limited to being implemented independently, but can be implemented by combining two or more operation flows. For example, some steps of one operation flow may be added to another operation flow, or some steps of one operation flow may be replaced with some steps of another operation flow.
  • a program that causes a computer to execute each process performed by the UE 100 or the base station 200 may be provided.
  • the program may be recorded on a computer readable medium.
  • a computer readable medium allows the installation of the program on the computer.
  • the computer-readable medium on which the program is recorded may be a non-transitory recording medium.
  • the non-transitory recording medium is not particularly limited, but may be, for example, a recording medium such as CD-ROM (Compact Disk Read Only Memory) or DVD-ROM (Digital Versatile Disc Read Only Memory). good.
  • circuits that execute each process performed by the UE 100 or the base station 200 may be integrated, and at least a part of the UE 100 or the base station 200 may be configured as a semiconductor integrated circuit (chipset, SoC (System On Chip)).
  • “transmit” may mean performing at least one layer of processing in the protocol stack used for transmission, or physically transmitting the signal wirelessly or by wire. It may mean sending to Alternatively, “transmitting” may mean a combination of performing the at least one layer of processing and physically transmitting the signal wirelessly or by wire.
  • “receive” may mean performing processing of at least one layer in the protocol stack used for reception, or physically receiving a signal wirelessly or by wire. may mean that Alternatively, “receiving” may mean a combination of performing the at least one layer of processing and physically receiving the signal wirelessly or by wire.
  • “obtain/acquire” may mean obtaining information among stored information, and may mean obtaining information among information received from other nodes.
  • references to "based on” and “depending on/in response to” are used unless otherwise specified. does not mean The phrase “based on” means both “based only on” and “based at least in part on.” Similarly, the phrase “depending on” means both “only depending on” and “at least partially depending on.” Similarly, “include” and “comprise” are not meant to include only the recited items, and may include only the recited items or in addition to the recited items. Means that it may contain further items. Similarly, in the present disclosure, “or” does not mean exclusive OR, but means logical OR. Furthermore, any references to elements using the "first,” “second,” etc.
  • the receiving unit (121) specifies the predetermined bandwidth part number during the random access procedure, and sets dedicated setting information for setting the dedicated bandwidth part used in the radio resource control (RRC) connected state. 1.
  • the control unit (140) When the frequency band of the separate initial bandwidth part does not include the frequency band of the MIB initial bandwidth part, which is the initial bandwidth part set based on the master information block, the random perform the access procedure, If the frequency band of the separate initial bandwidth portion includes the frequency band of the MIB initial bandwidth portion, performing the random access procedure using the separate initial bandwidth portion or the MIB initial bandwidth portion. 4.
  • the communication device (100, 100B) according to any one of 3.
  • control unit (140) performs the random access procedure using the MIB initial bandwidth portion, which is the initial bandwidth portion set based on the master information block. 5.
  • a communication device (100, 100B) according to any one of 1 to 4.
  • a base station (200) that communicates with communication devices (100, 100B) having reduced communication capacity compared to other communication devices (100, 100A), A separate initial bandwidth portion different from the initial bandwidth portion by designating a predetermined bandwidth portion number other than the bandwidth portion number for which the initial bandwidth portion used for the other communication device (100, 100A) is set a transmission unit (222) for transmitting common setting information for setting the in a system information block;
  • a base station (200) comprising a control unit (240) that performs a random access procedure with the communication device (100, 100B) using the separate initial bandwidth portion.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)
PCT/JP2022/040998 2021-11-02 2022-11-02 通信装置、基地局及び通信方法 Ceased WO2023080160A1 (ja)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP22889980.3A EP4429388A4 (en) 2021-11-02 2022-11-02 COMMUNICATION DEVICE, BASE STATION AND COMMUNICATION METHOD
JP2023558052A JP7680559B2 (ja) 2021-11-02 2022-11-02 通信装置、基地局及び通信方法
CN202280071292.0A CN118160400A (zh) 2021-11-02 2022-11-02 通信设备、基站以及通信方法
US18/649,784 US20240283620A1 (en) 2021-11-02 2024-04-29 Communication apparatus, base station, and communication method

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2021179781 2021-11-02
JP2021-179781 2021-11-02

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/649,784 Continuation US20240283620A1 (en) 2021-11-02 2024-04-29 Communication apparatus, base station, and communication method

Publications (1)

Publication Number Publication Date
WO2023080160A1 true WO2023080160A1 (ja) 2023-05-11

Family

ID=86241159

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2022/040998 Ceased WO2023080160A1 (ja) 2021-11-02 2022-11-02 通信装置、基地局及び通信方法

Country Status (5)

Country Link
US (1) US20240283620A1 (https=)
EP (1) EP4429388A4 (https=)
JP (1) JP7680559B2 (https=)
CN (1) CN118160400A (https=)
WO (1) WO2023080160A1 (https=)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2026043186A1 (ko) * 2024-08-21 2026-02-26 삼성전자 주식회사 멀티 캐리어로 구성되는 무선 통신 시스템에서 단말의 초기 접속 방법 및 장치

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2021179781A (ja) 2020-05-13 2021-11-18 株式会社日立製作所 文抽出装置及び文抽出方法

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021146998A1 (zh) * 2020-01-22 2021-07-29 华为技术有限公司 一种确定初始带宽部分bwp的方法、装置及存储介质
US20230209542A1 (en) * 2020-03-23 2023-06-29 FG Innovation Company Limited Method of initial access in wireless communications and related device

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2021179781A (ja) 2020-05-13 2021-11-18 株式会社日立製作所 文抽出装置及び文抽出方法

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
MODERATOR (ERICSSON): "FL summary #7 on reduced maximum UE bandwidth for RedCap", 3GPP TSG RAN WG1 #106-E. 27 AUGUST 2021, R1-2108632, 28 August 2021 (2021-08-28), XP052043050 *
See also references of EP4429388A4
ZTE CORPORATION, SANECHIPS: "Identification and Access Restriction for RedCap", 3GPP TSG RAN WG2 #113-E. 05 FEBRUARY 2021, R2-2100572, 15 January 2021 (2021-01-15), XP051973706 *
ZTE, SANECHIPS: "UE features discussion for RedCap", 3GPP TSG RAN WG1 #106B-E. 19 OCTOBER 202, 2 October 2021 (2021-10-02), XP052058292 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2026043186A1 (ko) * 2024-08-21 2026-02-26 삼성전자 주식회사 멀티 캐리어로 구성되는 무선 통신 시스템에서 단말의 초기 접속 방법 및 장치

Also Published As

Publication number Publication date
JPWO2023080160A1 (https=) 2023-05-11
CN118160400A (zh) 2024-06-07
EP4429388A4 (en) 2025-01-29
EP4429388A1 (en) 2024-09-11
JP7680559B2 (ja) 2025-05-20
US20240283620A1 (en) 2024-08-22

Similar Documents

Publication Publication Date Title
JP7783347B2 (ja) Ｔｄｄワイヤレス通信システムのためのダウンリンク及びアップリンクサブフレーム割当の動的シグナリング
US9642161B2 (en) Cross-scheduling for random access response
EP4128953B1 (en) Terminal apparatus, base station apparatus, and communication method
JP7043746B2 (ja) 通信装置、通信方法及びコンピュータプログラム
KR20190114871A (ko) 상향링크 데이터 채널 전송 전력 제어 방법 및 장치
CN107409394A (zh) 辅小区上的物理上行链路控制信道的系统及方法
EP4161159A1 (en) Enhancements for reduced capability new radio devices
KR20190098708A (ko) 상향링크 데이터를 전송하는 방법 및 장치
KR102493165B1 (ko) 상향링크 데이터 채널 전송 전력 제어 방법 및 장치
WO2021025174A1 (en) User equipment, base station apparatus, and method
WO2023013610A1 (ja) 通信装置、基地局装置及び通信方法
US20240283620A1 (en) Communication apparatus, base station, and communication method
US20240284367A1 (en) Communication apparatus, base station, and communication method
WO2023013547A1 (ja) 通信装置、基地局及び通信方法
JP7757435B2 (ja) 通信装置及び通信方法
JP7757436B2 (ja) 通信装置及び通信方法
US20240284366A1 (en) Communication apparatus, base station, and communication method
US20260032518A1 (en) In-device coexistence indication for multiple bandwidth parts in wireless communication system
WO2023013548A1 (ja) 通信装置及び通信制御方法
WO2025074988A1 (ja) 通信装置、基地局及び通信方法
WO2023080038A1 (ja) 通信装置、基地局、及び通信方法
WO2025074989A1 (ja) 通信装置、基地局及び通信方法
WO2023080036A1 (ja) 通信装置、基地局、及び通信方法
WO2023238686A1 (ja) 通信装置、基地局、及び通信方法
WO2023238689A1 (ja) 通信装置、基地局、及び通信方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22889980

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2023558052

Country of ref document: JP

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 202280071292.0

Country of ref document: CN

WWE Wipo information: entry into national phase

Ref document number: 2022889980

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2022889980

Country of ref document: EP

Effective date: 20240603