Reduced capability / complexity nr bandwidth portion configuration

Abstract

A configuration allows a UE to receive a BWP configuration that supports RC NR. The UE sends information indicating UE capabilities of the UE to a network. The UE receives, based on the UE capability, information indicating a second BWP associated with the first BWP, the second BWP having a frequency range equal to or less than the first BWP. The UE receives at least one of control information or data based on the indicated first BWP and second BWP.

Description

[0001] This application is a divisional application of the invention patent application entitled "Reduced Capability / Complexity NR Bandwidth Partial Configuration" with an international application date of June 27, 2020 and application number 202080051793.3 (international application number PCT / US2020 / 040015).

[0002] CROSS-REFERENCE TO RELATED APPLICATIONS

[0003] This application claims the benefit of U.S. Provisional Application No. 62 / 878,723, filed on July 25, 2019, entitled “NR-Light BWP Configuration,” and U.S. Patent Application No. 16 / 914,077, filed on June 26, 2020, entitled “Reduced capacity / complexity NR bandwidth part configuration,” both of which are expressly incorporated herein by reference in their entirety. Technical Field

[0004] The present disclosure relates generally to communication systems and, more particularly, to reduced capability / complexity new radio (NR) bandwidth part (BWP) configurations. Background Art

[0005] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcast. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0006] These multiple access technologies have been adopted in various telecommunication standards to provide common protocols that enable different wireless devices to communicate at city, country, region, and even global levels. An example telecommunication standard is 5G New Radio (NR). 5G NR is a part of the continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)) and other requirements. 5GNR includes services associated with enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low latency communication (URLLC). Some aspects of 5G NR can be based on 4G Long Term Evolution (LTE) standards. There is a need for further improvements to 5G NR technology. These improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the invention

[0007] A brief summary of one or more aspects is given below to provide a basic understanding of such aspects. This summary is not an exhaustive overview of all conceived aspects, and is neither intended to identify the key or critical elements of all aspects nor to define the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description that will be presented later.

[0008] Reduced Capability / Complexity (RC) NR may support UE devices such as wearables, smart watches, industrial sensors, and video / surveillance cameras. Such RC NR UE devices may require greater power savings than other non-RC NR UE devices, and / or may have more limited capabilities than non-RC NR devices. As such, improved designs are needed to facilitate improved communications and performance by RC NR devices.

[0009] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be an apparatus at a UE. The apparatus may be a processor and / or a modem at the UE or the UE itself. The apparatus sends information indicating the UE capabilities of the UE to a network. The apparatus receives information indicating a second BWP associated with a first bandwidth part (BWP) based on the UE capabilities, the second BWP may have a frequency range equal to or less than the first BWP. The apparatus receives at least one of control information or data based on the indicated first BWP and the second BWP. A non-RC NR UE device may utilize the first BWP when receiving data and / or control information from a base station. An RC NR UE device may utilize a portion of the first BWP and the second BWP when receiving data and / or control information from a base station. The RC NR UE may receive at least one of control information or data based on the indicated first BWP and the second BWP. An RC NR UE may have more limited capabilities than a non-RC NR UE and may therefore require a second BWP of potentially smaller bandwidth to receive control information and / or data, or may require the power savings provided by utilizing the second BWP rather than the first BWP when receiving control information and / or data.

[0010] To achieve the foregoing and related ends, the one or more aspects include the features fully described below and particularly pointed out in the claims. The following description and drawings set forth in detail certain illustrative features of the one or more aspects. However, these features are merely indicative of several of the various ways in which the principles of the various aspects may be employed, and this description is intended to cover all such aspects and their equivalents. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] Figure 1 is a diagram illustrating an example of a wireless communication system and an access network.

[0012] Figure 2A , 2B , 2C, and 2D are diagrams illustrating examples of a first 5G NR frame, a DL channel within a 5G NR subframe, a second 5G NR frame, and a UL channel within a 5G NR subframe, respectively.

[0013] Figure 3 is a diagram illustrating an example of a base station and a user equipment (UE) in an access network.

[0014] Figure 4 is a diagram illustrating a first exemplary configuration for a plurality of BWPs.

[0015] Figure 5 is a diagram illustrating a second exemplary configuration for a plurality of BWPs.

[0016] Figure 6is a diagram illustrating a third exemplary configuration for a plurality of BWPs.

[0017] Figure 7 is a diagram illustrating an exemplary system information block (SIB) 1 (SIB1).

[0018] Figure 8 is a diagram illustrating a fourth exemplary configuration for a plurality of BWPs.

[0019] Fig. 9 is a call flow diagram of signaling between a UE and a base station according to certain aspects of the present disclosure.

[0020] Fig.10 is a flow chart of a wireless communication method.

[0021] Fig.11 is a diagram illustrating an example of a hardware implementation for an example device. DETAILED DESCRIPTION

[0022] The detailed description set forth below in conjunction with the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. This detailed description includes specific details to provide a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form in order to avoid diluting such concepts.

[0023] Several aspects of telecommunication systems will now be presented with reference to various apparatus and methods. These apparatus and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0024] As an example, an element, or any part of an element, or any combination of elements may be implemented as a "processing system" including one or more processors. Examples of processors include: microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gating logic, discrete hardware circuits, and other suitable hardware configured to perform various functionalities described throughout this disclosure. One or more processors in a processing system may execute software. Software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether it is described in software, firmware, middleware, microcode, hardware description languages, or other terms.

[0025] Accordingly, in one or more example embodiments, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, each function may be stored or encoded on a computer-readable medium as one or more instructions or codes. Computer-readable media include computer storage media. Storage media may be any available medium that can be accessed by a computer. As an example and not limitation, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, a combination of computer-readable media of the above types, or any other medium that can be used to store computer-accessible instructions or data structure forms of computer executable code.

[0026] Figure 1 1 is a diagram illustrating an example of a wireless communication system and access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN)) includes a base station 102, a UE 104, an evolved packet core (EPC) 160, and another core network 190 (e.g., a 5G core (5GC)). The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). A macro cell includes a base station. A small cell includes a femto cell, a pico cell, and a micro cell.

[0027] The base station 102 configured for 4G LTE (collectively referred to as the Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with the EPC 160 via a first backhaul link 132 (e.g., an S1 interface). The base station 102 configured for 5G NR (collectively referred to as the Next Generation RAN (NG-RAN)) can interface with the core network 190 via a second backhaul link 184. Among other functions, the base station 102 can also perform one or more of the following functions: delivery of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracking, RAN information management (RIM), paging, positioning, and delivery of alert messages. The base stations 102 may communicate with each other directly or indirectly (eg, through the EPC 160 or the core network 190) over a third backhaul link 134 (eg, an X2 interface). The first backhaul link 132, the second backhaul link 184, and the third backhaul link 134 may be wired or wireless.

[0028] Base stations 102 may communicate wirelessly with UE 104. Each base station 102 may provide communication coverage for a corresponding geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, a small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of one or more macro base stations 102. A network including both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved B node (eNB) (HeNB), which may provide services to a restricted group referred to as a closed subscriber group (CSG). A communication link 120 between a base station 102 and a UE 104 may include an uplink (UL) (also referred to as a reverse link) transmission from the UE 104 to the base station 102 and / or a downlink (DL) (also referred to as a forward link) transmission from the base station 102 to the UE 104. The communication link 120 may use multiple input multiple output (MIMO) antenna technology, including spatial multiplexing, beamforming and / or transmit diversity. These communication links may be through one or more carriers. The base station 102 / UE 104 may use spectrum of up to Y MHz (e.g., 5, 10, 15, 20, 100, 400 MHz, etc.) bandwidth for each carrier allocated in the carrier aggregation for a total of up to Yx MHz (x component carriers) for transmission in each direction. The carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL). The component carriers may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carrier may be referred to as a secondary cell (SCell).

[0029] Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL WWAN spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). The D2D communication may be through a variety of wireless D2D communication systems, such as, for example, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

[0030] The wireless communication system may further include a Wi-Fi access point (AP) 150 communicating with a Wi-Fi station (STA) 152 in the 5 GHz unlicensed spectrum via a communication link 154. When communicating in the unlicensed spectrum, the STA 152 / AP 150 may perform a clear channel assessment (CCA) prior to communication to determine whether the channel is available.

[0031] The small cell 102' may operate in a licensed and / or unlicensed spectrum. When operating in an unlicensed spectrum, the small cell 102' may employ NR and use the same 5 GHz unlicensed spectrum as used by the Wi-Fi AP 150. The small cell 102' employing NR in the unlicensed spectrum may boost the coverage of the access network and / or increase the capacity of the access network.

[0032] Whether a small cell 102' or a large cell (e.g., a macro base station), the base station 102 may include and / or be referred to as an eNB, a gB node (gNB), or another type of base station. Some base stations (such as gNB 180) may operate in traditional sub-6 GHz spectrum, millimeter wave (mmW) frequencies, and / or near mmW frequencies to communicate with UE 104. When the gNB 180 operates in mmW or near mmW frequencies, the gNB 180 may be referred to as a mmW base station. Extremely high frequency (EHF) is part of the RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength between 1 mm and 10 mm. The radio waves in this band may be referred to as millimeter waves. Near mmW can extend down to 3 GHz frequencies with a wavelength of 100 mm. The super high frequency (SHF) band extends between 3 GHz and 30 GHz, which is also referred to as centimeter waves. The frequency range bands include frequency range 1 (FR1), which includes frequency bands below 7.225 GHz, and frequency range 2 (FR2), which includes frequency bands above 24.250 GHz. Communications using mmW / near mmW radio frequency (RF) bands (e.g., 3 GHz–300 GHz) have extremely high path loss and short range. The base station / UE may operate within one or more frequency range bands. The mmW base station 180 may utilize beamforming 182 with the UE 104 to compensate for the extremely high path loss and short range. The base station 180 and the UE 104 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays to facilitate beamforming.

[0033] Base station 180 may transmit beamformed signals to UE 104 in one or more transmit directions 182'. UE 104 may receive beamformed signals from base station 180 in one or more receive directions 182". UE 104 may also transmit beamformed signals to base station 180 in one or more transmit directions. Base station 180 may receive beamformed signals from UE 104 in one or more receive directions. Base station 180 / UE 104 may perform beam training to determine the best receive direction and transmit direction for each of base station 180 / UE 104. The transmit direction and receive direction of base station 180 may be the same or may be different. The transmit direction and receive direction of UE 104 may be the same or may be different.

[0034] The EPC 160 may include a mobility management entity (MME) 162, other MMEs 164, a serving gateway 166, a multimedia broadcast multicast service (MBMS) gateway 168, a broadcast multicast service center (BM-SC) 170, and a packet data network (PDN) gateway 172. The MME 162 may be in communication with a home subscriber server (HSS) 174. The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. In general, the MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are delivered through the serving gateway 166, which itself is connected to the PDN gateway 172. The PDN gateway 172 provides UE IP address allocation and other functions. The PDN gateway 172 and the BM-SC 170 are connected to IP services 176. The IP services 176 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a PS streaming service, and / or other IP services. The BM-SC 170 may provide functionality for MBMS user service provisioning and delivery. The BM-SC 170 may serve as an entry point for content provider MBMS transmissions, may be used to authorize and initiate MBMS bearer services within a public land mobile network (PLMN), and may be used to schedule MBMS transmissions. The MBMS gateway 168 may be used to distribute MBMS traffic to base stations 102 belonging to a multicast broadcast single frequency network (MBSFN) area that broadcasts a specific service, and may be responsible for session management (start / stop) and for collecting eMBMS-related charging information.

[0035] The core network 190 may include an access and mobility management function (AMF) 192, other AMFs 193, a session management function (SMF) 194, and a user plane function (UPF) 195. The AMF 192 may be in communication with a unified data management (UDM) 196. The AMF 192 is a control node that handles signaling between the UE 104 and the core network 190. In general, the AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are delivered through the UPF 195. The UPF 195 provides UE IP address allocation and other functions. The UPF 195 is connected to an IP service 197. The IP service 197 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a packet switching (PS) streaming (PSS) service, and / or other IP services.

[0036] A base station may include and / or be referred to as a gNB, a Node B, an eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmission reception point (TRP), or some other suitable term. The base station 102 provides an access point to the EPC 160 or the core network 190 for the UE 104. Examples of UE 104 include a cellular phone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., an MP3 player), a camera, a game console, a tablet device, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a health care device, an implant, a sensor / actuator, a display, or any other similar functional device. Some UEs 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, ovens, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.

[0037] Refer again Figure 1In certain aspects, the UE 104 may be configured to receive a BWP configuration supporting RCNR based on the capabilities of the UE 104. For example, the UE 104 may include a UE capability component 198 configured to send information indicating the UE capabilities of the UE 104 to the network via the base station 102 / 180. The UE 104 may be configured to send information indicating the UE capabilities of the UE (such as UE maximum BW size, number of rx antennas, tx power, etc.) to the network. In addition, the UE 104 may be configured to receive information indicating a second BWP associated with a first BWP based on the UE capabilities, wherein the frequency range of the second BWP is equal to or less than the first BWP. The BW size of the second BWP may be equal to or less than the size of the UE maximum BW. In addition, the UE 104 may receive at least one of control information or data based on the indicated first BWP and the second BWP.

[0038] Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar areas such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0039] Figure 2A 200 is a diagram illustrating an example of a first subframe within a 5G / NR frame structure. Figure 2B is a diagram 230 illustrating an example of DL channels within a 5G NR subframe. Figure 2C 250 is a diagram illustrating an example of a second subframe within a 5G NR frame structure. Figure 2D 280 is a diagram illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure can be frequency division duplex (FDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to DL or UL; or can be time division duplex (TDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to both DL and UL. Figure 2A , 2CIn the example provided, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (mostly DL) and subframe 3 is configured with slot format 34 (mostly UL), where D is DL, U is UL, and F is for flexible use between DL / UL. Although subframes 3 and 4 are shown as having slot formats 34 and 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are full DL and full UL, respectively. Other slot formats 2-61 include a mixture of DL, UL, and flexible symbols. The UE is configured with a slot format (dynamically configured by DL control information (DCI) or semi-statically / statically configured by radio resource control (RRC) signaling) through the received slot format indicator (SFI). Note that the following description also applies to the 5G NR frame structure for TDD.

[0040] Other wireless communication technologies may have different frame structures and / or different channels. A frame (10ms) may be divided into 10 equally sized subframes (1ms). Each subframe may include one or more time slots. A subframe may also include mini-slots, which may include 7, 4, or 2 symbols. Each time slot may include 7 or 14 symbols, depending on the time slot configuration. For time slot configuration 0, each time slot may include 14 symbols, and for time slot configuration 1, each time slot may include 7 symbols. The symbols on the DL may be cyclic prefix (CP) OFDM (CP-OFDM) symbols. The symbols on the UL may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (also known as single carrier frequency division multiple access (SC-FDMA) symbols) (for power-limited scenarios; limited to single stream transmission). The number of time slots within a subframe is based on the time slot configuration and parameter design. For slot configuration 0, different parameter designs μ0 to 4 allow 1, 2, 4, 8, 16, and 32 slots per subframe, respectively. For slot configuration 1, different parameter designs 0 to 2 allow 2, 4, and 8 slots per subframe, respectively. Accordingly, for slot configuration 0 and parameter design μ, there are 14 symbols per slot and 2 per subframe. μ time slots. The subcarrier spacing and symbol length / duration vary depending on parameter design. The subcarrier spacing can be equal to 2 μ *15kHz, where μ is parameter design 0 to 4. Thus, parameter design μ=0 has a subcarrier spacing of 15kHz, while parameter design μ=4 has a subcarrier spacing of 240kHz. The symbol length / duration is inversely related to the subcarrier spacing. Figures 2A-2DAn example of a slot configuration 0 with 14 symbols per slot and a parameter design μ=2 and 4 slots per subframe is provided. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within a frame set, there may be one or more different bandwidth parts (BWPs) that are frequency division multiplexed (see Figure 2B ). Each BWP may have a specific parameter design.

[0041] A resource grid may be used to represent the frame structure. Each slot includes a resource block (RB) (also called a physical RB (PRB)) extending over 12 consecutive subcarriers. The resource grid is divided into a number of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0042] like Figure 2A As explained in the illustration, some REs carry reference (pilot) signals (RS) for UEs. RSs may include demodulation RSs (DM-RSs) for channel estimation at the UE (indicated as R for a particular configuration). x , where 100x is the port number, but other DM-RS configurations are possible) and a channel state information reference signal (CSI-RS). RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and a phase tracking RS (PT-RS).

[0043] Figure 2BAn example of various DL channels within a subframe of a frame is illustrated. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs), each CCE including 9 RE groups (REGs), each REG including 4 consecutive REs in an OFDM symbol. The PDCCH within a BWP may be referred to as a control resource set (CORESET). Additional BWPs may be located at higher and / or lower frequencies across the channel bandwidth. The primary synchronization signal (PSS) may be within symbol 2 of a particular subframe of a frame. The PSS is used by the UE 104 to determine subframe / symbol timing and physical layer identity. The secondary synchronization signal (SSS) may be within symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE may determine the physical cell identifier (PCI). Based on the PCI, the UE may determine the location of the aforementioned DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also referred to as an SS block (SSB)). The MIB provides the number of RBs in the system bandwidth, and the system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted over the PBCH (such as the system information block (SIB)), and paging messages.

[0044] As in Figure 2C As explained in , some REs carry DM-RSs for channel estimation at the base station (indicated as R for one specific configuration, but other DM-RS configurations are possible). The UE may transmit DM-RSs for the physical uplink control channel (PUCCH) and DM-RSs for the physical uplink shared channel (PUSCH). The PUSCH DM-RS may be transmitted in the first or first two symbols of the PUSCH. The PUCCH DM-RS may be transmitted in different configurations depending on whether a short PUCCH or a long PUCCH is transmitted and on the specific PUCCH format used. The UE may transmit a sounding reference signal (SRS). The SRS may be transmitted in the last symbol of the subframe. The SRS may have a comb structure, and the UE may transmit the SRS on one of the comb teeth. The SRS may be used by the base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

[0045] Figure 2DExamples of various UL channels within a subframe of an illustration frame. The PUCCH may be located at a location as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicator (CQI), precoding matrix indicator (PMI), rank indicator (RI), and hybrid automatic repeat request (HARQ) ACK / NACK feedback. The PUSCH carries data and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0046] Figure 3 3 is a block diagram of a base station 310 in communication with a UE 350 in an access network. In the DL, IP packets from the EPC 160 may be provided to a controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a media access control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration of UE measurement reports; PDCP layer functionality associated with header compression / decompression, security (ciphering, cipher decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with delivery of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0047] The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include error detection on the transport channel, forward error correction (FEC) encoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 handles the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to produce multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine coding and modulation schemes and for spatial processing. The channel estimates may be derived from a reference signal and / or channel condition feedback transmitted by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX may modulate an RF carrier with a corresponding spatial stream for transmission.

[0048] At the UE 350, each receiver 354RX receives a signal through its corresponding antenna 352. Each receiver 354RX recovers the information modulated onto the RF carrier and provides the information to a receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for the UE 350. If there are multiple spatial streams destined for the UE 350, they can be combined into a single OFDM symbol stream by the RX processor 356. The RX processor 356 then transforms the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, as well as the reference signal, are recovered and demodulated by determining the signal constellation point most likely transmitted by the base station 310. These soft decisions can be based on the channel estimates calculated by the channel estimator 358. These soft decisions are then decoded and deinterleaved to recover the data and control signals originally transmitted on the physical channel by the base station 310. These data and control signals are then provided to the controller / processor 359 which implements layer 3 and layer 2 functionality.

[0049] The controller / processor 359 may be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer readable medium. In the UL, the controller / processor 359 provides demultiplexing between transport channels and logical channels, packet reassembly, cipher interpretation, header decompression, and control signal processing to recover IP packets from the EPC 160. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0050] Similar to the functionality described in conjunction with DL transmissions performed by the base station 310, the controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression, and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with delivery of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing MAC SDUs onto TBs, demultiplexing MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0051] Channel estimates derived by a channel estimator 358 from a reference signal or feedback transmitted by the base station 310 may be used by a TX processor 368 to select the appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via separate transmitters 354TX. Each transmitter 354TX may modulate an RF carrier with a corresponding spatial stream for transmission.

[0052] UL transmissions are processed at the base station 310 in a manner similar to that described in conjunction with the receiver functionality at the UE 350. Each receiver 318RX receives a signal through its respective antenna 320. Each receiver 318RX recovers information modulated onto an RF carrier and provides the information to a RX processor 370.

[0053] The controller / processor 375 may be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport channels and logical channels, packet reassembly, cipher decoding, header decompression, control signal processing to recover IP packets from the UE 350. The IP packets from the controller / processor 375 may be provided to the EPC 160. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0054] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform operations related to Figure 1 The 198 combined aspects.

[0055] NR can support UEs configured with eMBB and URLLC. RC NR can support UE devices such as wearable devices, smart watches, industrial sensors, and video / surveillance cameras. Compared with high-end eMBB and URLLC devices, RC NR UEs can have reduced device complexity. In addition, RC NR UEs can be configured to have a compact form factor and to support all frequency ranges (FR) 1 / FR2 bands for FDD and TDD. In some instances, RC NR UEs can be used as industrial wireless sensors with 99.99% communication service availability and end-to-end latency of less than 100ms (e.g., 5-10ms for security-related sensors). RC NR UEs can have a reference bit rate of less than 2Mbps with heavy uplink traffic. RC NR UEs can be stationary or mobile and can have a battery life of at least several years. RC NR UEs can also be used in video surveillance settings and can have a video bit rate of 2-4Mbps and a latency of 500ms or less. In some instances, an RC NR UE may provide high-end video with a video bit rate of 2-4Mbps. Some RC NR UEs (e.g., wearable devices) may have a downlink bit rate of about 10Mbps or more and an uplink bit rate of about 5Mbps or more. As discussed above, an RC NR UE may have more limited capabilities than a non-RC NR UE, and may therefore require limited bandwidth to receive control information and / or data, or may require power savings provided by utilizing limited bandwidth when receiving control information and / or data. Challenges in the design of RC NR UEs include potentially limited frequency bands on which the UE can operate and low complexity requirements. For example, an RC NR UE may only support a bandwidth of 5MHz, 10MHz, or 20MHz, rather than a 100MHz bandwidth for a non-RC NR UE. The bandwidth supported by the RC NR UE may be at least the bandwidth of a synchronization signal block (SSB), and thus the RC NR UE may receive the same SSB as the SSB received by the non-RC NR UE. Challenges in RC NR UE design may further include lower transmit maximum power (e.g., 20dBm or 14dBm instead of 23dBm), fewer receive antennas (e.g., one or two receive antennas instead of four receive antennas), greater power saving / battery life requirements (e.g., 1-5 years), more flexible mobility, and coexistence with eMBB, URLLC, LTE narrowband (NB) IoT / MTC.

[0056] Figure 44 is a diagram illustrating a first exemplary configuration for multiple BWPs. A system information (e.g., SIB1) initial BWP (BWP#0) 402 may be indicated in the MIB. SSB 404 may be within the initial BWP 402. CORESET#0 406 BW may be equal to the BW of BWP#0 402. PDSCH 408 carrying system information (e.g., SIB1) may be scheduled within BWP#0 402. Both CORESET 406 and PDSCH 408 may be quasi-co-located (QCLized) with SSB 404. NonSIB1-initial BWP 414 (e.g., initial BWP for additional system information other than SIB1) may be indicated in system information (408). The system information may indicate whether the additional system information to be transmitted (referred to as other system information (OSI)) is a broadcast or non-broadcast (e.g., dedicated) OSI. The CORESET 410 configured in the non-SIB1 initial BWP 414 is used for the UE to monitor the PDCCH 410 within the PDSCH 412 for OSI. The PDSCH 412 carrying the OSI may be scheduled within the non-SIB1 initial BWP 414. The CORESET 410 and the PDSCH 412 may be configured with a different transmission configuration indicator (TCI) state than the SSB 402. With respect to the BWP for an RRC connected UE (e.g., the UE is in the RRC connected state), one or more BWPs may be configured via unicast RRC signaling.

[0057] Refer again Figure 4 , the UE may receive an indication of an initial BWP 402 (at Figure 4 The UE may receive an SSB 404 within the initial BWP 402. The SSB 404 may indicate a control resource set (CORESET) 406 (in Figure 4The CORESET 406 may include a search space for a PDCCH. Within the CORESET 406, the UE may receive a PDCCH including a DCI. The DCI may include scheduling information (modulation and coding scheme (MCS), RB allocation, etc.) for receiving a PDSCH 408 including system information (e.g., SIB1). The SSB 404 may be time division multiplexed (TDM) / frequency division multiplexed (FDM) with the CORESET 406 / PDSCH 408. The CORESET 406 and the PDSCH 408 may be QCLed (e.g., having substantially the same channel excluding phase) with the SSB 404. The system information may provide information indicating the location of the CORESET 410 and whether the UE may obtain a broadcast or non-broadcast OSI through the CORESET 410. The UE may monitor the PDCCH within the CORESET 410 for receiving the OSI. Within the CORESET 410, the UE may receive a PDCCH including a DCI. The DCI may include scheduling information for receiving a PDSCH 412 including an OSI, such as system information included in SIB x, where x>1 (e.g., non-SIB1 SIBs including SIB2, SIB3, SIB4, etc.). The UE may receive the CORESET 410 and the PDSCH 412 within a non-SIB1 initial BWP 414, which may be 100 MHz, for example. The non-SIB1 initial BWP 414 indicated by SIB1 may be larger than the initial BWP 402. If not configured in SIB1, the non-SIB1 initial BWP 414 defaults to the same as the initial BWP 402.

[0058] As about Figure 4 As discussed, RC NR design may present challenges in adapting the framework. These challenges include limited frequency band and low complexity of RC NR UEs, coverage compensation is required for RC NR UEs due to limited frequency band and limited number of receive antennas; and high PDCCH capacity to support a large number of RC NR UEs. RC NR UEs can access legacy NR 5G networks, but with reduced flexibility of existing features. For future NR 5G networks, new designs / signaling may be introduced. Such designs may improve coverage by combining new signals and part of the legacy signals for system information. In addition, such designs may allow transmission of new signals with backward compatibility and improve spectrum efficiency with minimal impact on legacy UEs (e.g., reception of OSI).

[0059] Figure 55 is a diagram illustrating a second exemplary configuration for multiple BWPs. An RC NR initial BWP (BWP#0′) 514 may be defined for system information (e.g., SIB1) using predefined resources based on the SSB ID of the SSB 504 within the initial BWP (BWP#0) 502. One RC NR initial BWP 514 may be configured according to the SSB 504 within the initial BWP 502. The CORESET#0′ 510 bandwidth may be the same as the BWP#0′ 514. Both the CORESET#0 in the BWP#0 502 and the CORESET#0′ in the BWP#0′ 514 are QCLed with the SSB 504. The PDSCH 512 carrying additional system information may be scheduled by the PDCCH in the CORESET#0′ 510 within the RC NR initial BWP 514. The RC NR UE may monitor a portion of the TDMed CORESET#0' 510 / SIB1 512 and CORESET#0 506' / SIB1 508' for combination. The distribution pattern of the legacy CORESET#0 506 / SIB1 508 may not be restricted, for example, the PDSCH carrying SIB1 in BWP#0 may be distributed in BWP#0, where only a subset of BWP#0 is in the same frequency range as BWP#0'. BWP#0' and BWP#0 may be TDM (e.g., in FR1 / FR2) or FDM (e.g., in FR1) using a predefined mapping relationship. Different RC NR initial BWPs 514 for different SSBs may also be TDM (e.g., in FR1 / FR2) or FDM (e.g., in FR1). Under some predefined conditions (e.g., only when the BW of BWP#0 502>BW of BWP#0'514, the number of receive antennas is less than 4, and / or the PBCH-based signal to interference plus noise ratio (SINR) is less than X dB), the RC NR UE may need to blindly detect the RC NR initial BWP (BWP#0') 514 for SIB1 detection, assuming a predefined resource mapping relationship (e.g., RB / time slot position) relative to BWP#0.

[0060] Refer again Figure 5 , the UE may receive an indication of an initial BWP 502 (at Figure 5 The UE may receive the SSB 504 in the initial BWP 502. The SSB 504 may also be in the light initial BWP 514. The SSB 504 may indicate the location and size of the CORESET 506 (in the Figure 5506). Within CORESET 506, the UE receives at least a portion of PDCCH 506' including DCI. The DCI includes scheduling information for receiving PDSCH 508 including system information (e.g., SIB1). Although the UE receives only a portion of PDCCH 506', the UE may be able to obtain the DCI due to the low coding rate / redundant bits. Based on the DCI, the UE receives a portion of PDSCH 508'. The UE then decodes PDSCH 508' to obtain system information (e.g., SIB1). Although the UE receives only a portion of PDSCH 508', the UE may be able to obtain system information (e.g., SIB1) within the PDSCH due to the low coding rate (e.g., 1 / 3) / redundant bits. Both portions of PDCCH 506' and PDSCH 508' are within the light initial BWP 514, which is the range of available bandwidth available to the UE (which is an RC NR UE). Based on the location of BWP#0, the UE may determine, infer, or use blind detection to receive CORESET 510 (at Figure 5 In the CORESET 510, the UE receives a PDCCH including a DCI. The DCI includes scheduling information for receiving a PDSCH 512 including system information (e.g., SIB1). Based on the DCI, the UE receives a PDSCH 512 including system information (e.g., SIB1). The system information of the PDSCHs 508', 512 may be the same. Both the CORESET 510 (including the PDCCH) and the PDSCH 512 are within a light initial BWP (BWP#0') 514. In one configuration, the CORESET 510 and the PDSCH 512 have the same bandwidth as the light initial BWP 514. In one configuration, the light initial BWP 514 spans a frequency range that is less than or equal to the initial BWP 502. In another configuration, as Figure 5 As shown in FIG. 5 , the light initial BWP 514 spans a smaller frequency range than the initial BWP 502 .

[0061] In one configuration, the CORESET 510 and PDSCH 512 may span more symbols / duration than the CORESET 506 and PDSCH 508. Specifically, since the PDSCH 512 may contain the same system information as the PDSCH 508, the PDSCH 512 may span more symbols / duration than the PDSCH 508 to account for a smaller bandwidth, assuming that the PDSCH 512 has a smaller bandwidth than the PDSCH 508. Additionally, if the CORESET 510 contains the same or nearly the same DCI information as the DCI in the CORESET 506 (e.g., shares at least some common information), the CORESET 510 may span more symbols than the CORESET 506 to account for a smaller bandwidth, assuming that the CORESET 510 has a smaller bandwidth than the CORESET 506.

[0062] After receiving the system information (e.g., SIB1) in each of PDSCH 508' and PDSCH 512, the UE can decode each of the PDSCHs to obtain two corresponding system information, which, as described above, can include the same system information. The UE can then combine the decoded system information to obtain a single system information (e.g., log-likelihood ratio (LLR) combination). In such a configuration, the UE can better successfully detect the system information (e.g., SIB1) with less waiting time.

[0063] As described above, the UE may combine system information. The UE may also combine the DCI or portions of the first DCI with the second DCI to obtain a DCI. In such a configuration, the UE may be configured to recover system information (e.g., SIB1) within the PDSCH in the CORESET and the DCI within the PDCCH. With respect to combining at the UE for channel estimation, in addition to utilizing the QCL properties of the associated SSBs, the UE may be able to assume a DMRS association between CORESET#0 506' / PDSCH 508' in BWP#0 502 and CORESET#0'510 / PDSCH 512 in BWP#0'514 (e.g., if the DMRS within BWP#0 and the DMRS within BWP#0' are transmitted from the same antenna port using the same transmission scheme). The DMRS association allows the UE to combine the DMRS for channel estimation (e.g., coherent combining). For example, the UE may combine the DMRS in CORESET 506' with the DMRS in CORESET 510 when estimating the channel before decoding the DCI in CORESETS 506', 510. For example, the UE may combine the DMRS in PDSCH 508' with the DMRS in PDSCH 512 when estimating the channel before decoding the system information (e.g., SIB1) in PDSCH 508', 512. For system information (e.g., SIB1), the UE may combine the PDSCH carrying system information in BWP#0 502 and BWP#0'514. For PDCCH, in a first configuration, PDCCH combining is enabled. If the DCI bits (or at least some common fields) in the PDCCH of CORESET#0 506' and CORESET#0'510 are the same, PDCCH combining may be enabled. Only common DCI bits may be combined. This may restrict the same resource allocation for PDSCH in BWP#0 502 and BWP#0' 514. If the DCI bits in CORESET#0 506' and CORESET#0' 510 are independent, PDCCH combining may be disabled.

[0064] Figure 6600 is a diagram illustrating a third exemplary configuration for multiple BWPs. The RC NR BWP 612 of the OSI 610 for the RC NR UE may be defined using a configuration indicated by the system information (e.g., SIB1) 602 (e.g., see 508', 512). More than one RC NR non-SIB1 initial BWP 612 (N in number) may be configured for the OSI 610 for the RC NR UE. For example, if concurrent in time, there may be up to 20 5MHz RC NR non-SIB1 initial BWPs 612 in the 100MHz non-SIB1 initial BWP 614 without overlapping in frequency. In one example, one RC NR BWP 612 may be used for the broadcast OSI monitored by all RC NR UEs, while the remaining N-1 RC NR BWPs 612 may be used for non-broadcast SIBs (on demand). The RC NR BWP for broadcasting OSI can set the BW size to the minimum supported BW size for all RC NR UEs. System information (e.g., SIB1) 602 can indicate the mapping relationship between the RC NR non-SIB1 initial BWP 612 and each type of system information. For example, the UE can receive system information (e.g., SIB2) through one of the N-1 RC NR BWPs and receive system information (e.g., SIB3) through another of the N-1 RC NR BWPs. This can be applied in a similar manner to RC NR paging configured using one or more BWPs. The UE can select one of multiple BWPs for load balancing for the RC NR UE based on a predefined mapping relationship (e.g., UE ID). The RC NR BWP 612 for OSI 610 can have different bandwidth sizes and can be within or outside the old non-SIB1 initial BWP 614. For example, the BWP can be larger to receive SIBs for RC NR UEs supporting larger BWs. After receiving a request from the RC NR UE, the light BWP for on-demand SIB may be scheduled / selected by RAR (Random Access Response).

[0065] Refer again Figure 6, the UE receives system information (e.g., SIB1) 602 (see also 508', 512 and related discussions). Based on the information in the system information, the RC NR UE determines the location of the CORESET 606. The non-RC NR UE may determine the location of the CORESET 604 and then obtain the PDSCH 608 including the OSI. The RC NR UE may decode the PDCCH within the CORESET 606 to obtain the DCI, and receive the PDSCH 610 based on the DCI and decode the PDSCH 610 to obtain the OSI. The CORESET 606 and the PDSCH 610 are within the light non-SIB1 initial BWP 612.

[0066] The RC NR CORESET 606 for OSI 610 may be configured in an associated RC NR non-SIB1 initial BWP 612 (except for frequency hopping (FH)). The PDSCH 610 may be scheduled within the same BW as the RC NR CORESET 606. With respect to the RC NR CORESET 606 for the RC NR BWP 612 and the legacy CORESET 604 for the legacy BWP 614, if such PDCCH search spaces of the CORESETs 606 and 604 overlap in TDM / FDM, the IDs configured for system information, RA and paging shall be different for legacy UEs and RC NR UEs. In the case of TDM in FR1 / FR2 or FDM in FR1, the TCI states of the RC NR CORESET 606 and the legacy CORESET 604 may be different if configured separately (the default is the same if there is no additional TCI state configuration for the RC NR CORESET). The UE may perform OSI combining for coverage extension. If the TDMed PDSCH carries the same content of the OSI (e.g., for a broadcast OSI), the UE may be able to combine the OSI for coverage extension. For example, the UE may combine the OSI in the PDSCH 610 with the OSI subsequently received in the PDSCH. In one configuration, if the PDSCH 608 is not concurrent in time with the PDSCH 610, the UE may obtain a portion of the PDSCH 608 based on its light non-SIB1 initial BSP 612 and also obtain the PDSCH 610, and then combine the PDSCH 610 and the portion of the PDSCH 608 to obtain the OSI. In addition, the UE may also perform DMRS combining for enhanced channel estimation, assuming a DMRS association between the light non-SIB1 initial BWP and the non-SIB1 initial BWP. In some aspects, the light non-SIB1 initial BWP may be implicitly configured by using a CORESET configuration for the RC NR UE. The PDSCH scheduled by PDCCH in a CORESET for RC NR UE is confined within the same BW of the CORESET.

[0067] Figure 7 7 is a diagram illustrating exemplary system information (eg, SIB1). The system information may include additional system information in dashed boxes, where information 702 provides separate scheduling information for RC NR broadcast or non-broadcast OSI, and information 704 provides a list of RC NR non-SIB1 initial BWPs for RC NR.

[0068] Figure 8800 is a diagram illustrating a fourth exemplary configuration for multiple BWPs. Such a configuration may be applied to a UE in an RRC connected state. RC NR BWPs 802, 804 for unicast data may be configured as RC NR UEs for RRC connectivity. In one configuration, N RC NR BWPs may be configured for an RRC RC NR UE. For example, if each RC NR BWP is 5MHz and such BWPs do not overlap (e.g., are not concurrent in time or frequency) within a 100MHz legacy BWP 806 and FDM, then N may be up to 20. In one configuration, the UE may receive an explicit indication of the RC NR BWP to be used by unicast RRC signaling. The RC NR BWP may be a UE-specific BWP based on the UE capability to support the BW size. For example, a first UE with a lower or reduced UE capability may be assigned a light BWP1 802, while a second UE with a higher or improved UE capability may be assigned a light BWP2 804. Alternatively, the UE may receive an implicit indication of the RC NR BWP to be used by using its CORESET configuration. The RC NR CORESET may be configured to be no larger than the BW based on UE capabilities. The PDSCH may be scheduled within the bandwidth of the RC NR CORESET.

[0069] RC NR uplink BWP may also be configured. For RRC Idle UEs, in addition to the conventional uplink and downlink common configurations for non-RC NR, the system information (e.g., SIB1) for RC NR uplink BWP may further include an uplink common configuration specific to RC NR.

[0070] For RRC connected UEs, the configuration may be indicated by unicast RRC signaling. In one configuration, the UE may receive an explicit indication of the RC NR UL BWP by unicast RRC signaling. The RC NR BWP may be a UE-specific BWP based on the UE capability to support the UL BW size. In one configuration, in case of TDD, the UE may receive an implicit indication of the RC NR UL BWP by using its DL CORESET configuration. The RC NR CORESET may be configured to be no larger than the BW based on the UE capability. PUSCH / PUCCH may be scheduled within the bandwidth of the RC NR DL CORESET.

[0071] Fig. 9 is a call flow diagram 900 of signaling between a UE and a base station in accordance with certain aspects of the present disclosure. Fig. 9The diagram 900 includes a UE 902 and a base station 904. The base station 904 can be configured to provide a cellular cell. The UE 902 can be configured to communicate with the base station 904. For example, in Figure 1 In the context of , base station 904 may correspond to base station 102 / 180, and accordingly, a cellular cell may include a geographic coverage area 110 in which communication coverage is provided and / or a small cellular cell 102' having a coverage area 110'. In addition, UE 902 may correspond to at least UE 104. In another example, in Figure 3 In the context of , base station 904 may correspond to base station 310, and UE 902 may correspond to UE 350. Optional aspects are illustrated with dashed lines.

[0072] As illustrated at 906, UE 902 may send information indicating UE capabilities. The UE may send information indicating UE capabilities to the network. The information may indicate that the UE capabilities are types of UEs with RC. The UE may send information indicating UE capabilities to the network via a base station.

[0073] As illustrated at 908, the base station may send information indicating a second BWP associated with the first BWP. The UE 902 may receive information indicating a second BWP associated with the first BWP. The UE 902 may receive information indicating the second BWP based on the UE capabilities. The second BWP may have a frequency range equal to or less than the first BWP.

[0074] As illustrated at 910, the base station may send at least one of control information or data. The UE 902 may receive at least one of the control information or data. The UE 902 may receive at least one of the control information or the data based on the indicated first BWP and the second BWP. In some aspects, to receive at least one of the control information or the data based on the indicated first BWP and the second BWP, the UE 902 may receive DCI in a PDCCH within a CORESET. The CORESET may be within the second BWP. The UE 902 may also receive data in a PDSCH within the second BWP based on the received DCI.

[0075] In some aspects, for example at 912, the base station 904 may send a subset of the first SIB in the PDSCH. The UE 902 may receive the subset of the first SIB in the PDSCH. The first SIB may be in the first BWP. The subset of the first SIB may be in the second BWP.

[0076] In some aspects, for example, at 914, the base station 904 may send a second SIB in the PDSCH within the second BWP. The UE 902 may receive the second SIB in the PDSCH within the second BWP. In some aspects, to receive the second SIB, the UE may perform blind detection to identify the second SIB by assuming a location of the second BWP based on a location of the first BWP.

[0077] In some aspects, for example, at 916, the UE 902 may obtain system information. The UE 902 may obtain the system information by decoding at least one of the subset of the first SIB and the second SIB. In some aspects, the UE 902 may decode the subset of the first SIB and the second SIB. The UE may combine at least a portion of the decoded subset of the first SIB with the second SIB. In some aspects, the system information may be associated with a SIB (e.g., SIB1). The system information may be associated with many different SIBs, and the present disclosure is not limited to the system information being associated with SIB1.

[0078] In some aspects, the UE may combine the DMRS within a portion of the first BWP that may include the subset of the first SIB with the DMRS within the second BWP that includes the second SIB. In some aspects, the UE may perform channel estimation based on the combined DMRS. Decoding of the subset of the first SIB and the second SIB may be based on the channel estimate.

[0079] In some aspects, the UE may receive a first DCI in a PDCCH within a subset of a first CORESET. The first CORESET may be within the first BWP. The subset of the first CORESET may be within the second BWP. The subset of the first SIB may be received based on the received first DCI. In some aspects, the UE may receive a second DCI in the PDCCH within the second CORESET. The second CORESET may be within the second BWP. The second SIB may be received based on the received second DCI. In some aspects, the UE may decode the first DCI and the second DCI. The UE may combine at least a portion of the decoded first DCI with the decoded second DCI to obtain a combined DCI. The second SIB may include system information that is the same as the system information of the first SIB.

[0080] In some aspects, for example at 918, the base station 904 may send information indicating a plurality of CORESETs. The UE 902 may receive information indicating a plurality of CORESETs. A first CORESET of the plurality of CORESETs may be within a first BWP. A second CORESET of the plurality of CORESETs may be within a second BWP. In some aspects, the first CORESET may overlap with the second CORESET in at least one of time or frequency, wherein a non-overlapping search space of the PDCCH or an overlapping search space of the PDCCH has a different identifier (ID) for the SIB. In some aspects, the first CORESET does not overlap with the second CORESET. Overlapping search spaces may include search spaces that occur concurrently in time or frequency. Non-overlapping search spaces do not occur concurrently in time or frequency so that the search spaces are separated by time or frequency.

[0081] In some aspects, the base station 904 may send the DCI in the PDCCH, for example at 920. The UE 902 may receive the DCI in the PDCCH. The UE 902 may receive the DCI in the PDCCH in the second CORESET.

[0082] In some aspects, for example at 922, the base station 904 may send first additional system information. The UE 902 may receive the first additional system information. The UE may receive the first additional system information in the PDSCH within the second BWP. The UE may receive the first additional system information based on the received DCI. In some aspects, the first additional system information may be associated with one or more SIBs x, where x>1. In some aspects, the UE may receive the second additional system information in the PDSCH within the second BWP. The UE may receive the second additional system information based on the received DCI. In some aspects, the UE may combine the first additional system information and the second additional system information to obtain a set of additional system information. The configuration of the second BWP for the second additional system information is different from the configuration of the second BWP for the first additional system information.

[0083] Fig.10 1000 is a flow chart of a wireless communication method. The method may be performed by a UE (e.g., UE 104, 902; equipment 1102; cellular baseband processor 1104, which may include memory 360 and may be the entire UE 350 or a component of UE 350 (such as TX processor 368, RX processor 356 and / or controller processor 359)). One or more of the illustrated operations may be omitted, transposed, or performed simultaneously. Optional aspects are illustrated with dashed lines. The method may allow the UE to receive a BWP configuration that supports RC NR.

[0084] At 1002, the UE may send information indicating UE capabilities. For example, 1002 may be performed by a UE capabilities component 1140 of the equipment 1102. The UE may send information indicating UE capabilities to a network. The information may indicate that the UE capabilities are types of UEs with RC. The UE may send information indicating UE capabilities to the network via a base station.

[0085] At 1004, the UE may receive information indicating a second BWP associated with the first BWP. For example, 1004 may be performed by a receiving component 1130 of the equipment 1102. The UE may receive information indicating the second BWP based on the UE capabilities. The second BWP may have a frequency range equal to or less than the first BWP.

[0086] At 1006, the UE may receive at least one of control information or data. For example, 1006 may be performed by a receiving component 1130 of the equipment 1102. The UE may receive at least one of the control information or the data based on the indicated first BWP and the second BWP. In some aspects, to receive at least one of the control information or the data based on the indicated first BWP and the second BWP, the UE may receive a DCI in a PDCCH within a CORESET. The CORESET may be within the second BWP. The UE may also receive data in a PDSCH within the second BWP based on the received DCI.

[0087] In some aspects, the UE may receive a subset of the first SIB within the PDSCH, for example at 1008. For example, 1008 may be performed by a receiving component 1130 of the apparatus 1102. The first SIB may be within the first BWP. The subset of the first SIB may be within the second BWP.

[0088] In some aspects, the UE may receive a second SIB in the PDSCH within the second BWP, for example at 1010. For example, 1010 may be performed by a receiving component 1130 of the equipment 1102. In some aspects, to receive the second SIB, the UE may perform blind detection to identify the second SIB by assuming a location of the second BWP based on a location of the first BWP.

[0089] In some aspects, the UE may obtain system information, for example, at 1012. For example, 1012 may be performed by the SI component 1142 of the equipment 1102. The UE may obtain the system information by decoding at least one of the subset of the first SIB and the second SIB.

[0090] In some aspects, the UE may decode a subset of the first SIB and the second SIB. The UE may combine at least a portion of the decoded subset of the first SIB with the second SIB. In some aspects, the system information may be associated with SIB 1 (e.g., SIB1). The system information may be associated with many different SIBs, and the present disclosure is not limited to the system information being associated with SIB1.

[0091] In some aspects, the UE may combine the DMRS within a portion of the first BWP that may include the subset of the first SIB with the DMRS within the second BWP that includes the second SIB. In some aspects, the UE may perform channel estimation based on the combined DMRS. Decoding of the subset of the first SIB and the second SIB may be based on the channel estimate.

[0092] In some aspects, the UE may receive a first DCI in a PDCCH within a subset of a first CORESET. The first CORESET may be within the first BWP. The subset of the first CORESET may be within the second BWP. The subset of the first SIB may be received based on the received first DCI. In some aspects, the UE may receive a second DCI in a PDCCH in a second CORESET. The second CORESET may be within the second BWP. The second SIB may be received based on the received second DCI. In some aspects, the UE may decode the first DCI and the second DCI. The UE may combine at least a portion of the decoded first DCI with the decoded second DCI to obtain a combined DCI. The second SIB may include system information that is the same as the system information of the first SIB.

[0093] In some aspects, for example, at 1014, the UE may receive information indicating a plurality of CORESETs. For example, 1014 may be performed by a receiving component 1130 of the equipment 1102. A first CORESET of the plurality of CORESETs may be within a first BWP. A second CORESET of the plurality of CORESETs may be within a second BWP. In some aspects, the first CORESET may overlap with the second CORESET in at least one of time or frequency, wherein a non-overlapping search space of the PDCCH or an overlapping search space of the PDCCH has a different identifier (ID) for the SIB. In some aspects, the first CORESET does not overlap with the second CORESET.

[0094] In some aspects, the UE may receive the DCI in the PDCCH, for example, at 1016. For example, 1016 may be performed by the receiving component 1130 of the apparatus 1102. The UE may receive the DCI in the PDCCH in the second CORESET.

[0095] In some aspects, for example, at 1018, the UE may receive first additional system information. For example, 1018 may be performed by a receiving component 1130 of the equipment 1102. The UE may receive the first additional system information within the PDSCH within the second BWP. The UE may receive the first additional system information based on the received DCI. In some aspects, the first additional system information may be associated with one or more SIBs x, where x>1. In some aspects, the UE may receive the second additional system information within the PDSCH within the second BWP. The UE may receive the second additional system information based on the received DCI. In some aspects, the UE may combine the first additional system information and the second additional system information to obtain a set of additional system information. The configuration of the second BWP for the second additional system information is different from the configuration of the second BWP for the first additional system information.

[0096] Fig.111 is a diagram 1100 illustrating an example of a hardware implementation of an apparatus 1102. The apparatus 1102 is a UE and includes a cellular baseband processor 1104 (also referred to as a modem) coupled to a cellular RF transceiver 1122 and one or more subscriber identity modules (SIM) cards 1120, an application processor 1106 coupled to a secure digital (SD) card 1108 and a screen 1110, a Bluetooth module 1112, a wireless local area network (WLAN) module 1114, a global positioning system (GPS) module 1116, and a power supply 1118. The cellular baseband processor 1104 communicates with the UE 104 and / or the BS 102 / 180 through the cellular RF transceiver 1122. The cellular baseband processor 1104 may include a computer-readable medium / memory. The computer-readable medium / memory may be non-transitory. The cellular baseband processor 1104 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory. The software, when executed by the cellular baseband processor 1104, causes the cellular baseband processor 1104 to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the cellular baseband processor 1104 when executing the software. The cellular baseband processor 1104 further includes a receiving component 1130, a communication manager 1132, and a transmission component 1134. The communication manager 1132 includes one or more of the illustrated components. The components within the communication manager 1132 may be stored in a computer-readable medium / memory and / or configured as hardware within the cellular baseband processor 1104. The cellular baseband processor 1104 may be a component of the UE 350 and may include a memory 360 and / or at least one of the following: a TX processor 368, an RX processor 356, and a controller / processor 359. In one configuration, the equipment 1102 may be a modem chip and include only the baseband processor 1104, and in another configuration, the equipment 1102 may be the entire UE (e.g., see Figure 3 350) and includes the aforementioned additional modules of equipment 1102.

[0097] The communication manager 1132 includes a UE capability component 1140, which is configured to send information indicating UE capabilities, such as in conjunction with Fig.10 1002 as described. The communication manager 1132 further includes an SI component 1142, which is configured to obtain system information, for example, as combined Fig.10 The receiving component 1130 may be configured to receive information indicating a second BWP associated with a first BWP, for example, as described in conjunction with Fig.10 The receiving component 1130 may be configured to receive at least one of control information or data, for example, as described in conjunction with Fig.10The receiving component 1130 may be configured to receive a subset of the first SIB within the PDSCH, for example, as described in conjunction with Fig.10 The receiving component 1130 may be configured to receive the second SIB in the PDSCH within the second BWP, for example, as described in conjunction with Fig.10 The receiving component 1130 may be configured to receive information indicating a plurality of CORESETs, for example, as described in conjunction with Fig.10 1014 as described. The receiving component 1130 can be configured to receive the DCI in the PDCCH, for example, as combined with Fig.10 The receiving component 1130 may be configured to receive the first additional system information, for example, as described in conjunction with Fig.10 1018 described.

[0098] The equipment may include performing Fig.10 The additional components of each box of the algorithm in the preceding flowchart. Thus, Fig.10 Each block in the aforementioned flow chart of can be performed by a component and the equipment may include one or more of those components. These components can be one or more hardware components specially configured to perform the process / algorithm, implemented by a processor configured to perform the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0099] In one configuration, the equipment 1102, and in particular the cellular baseband processor 1104, includes: means for sending information indicating UE capabilities of the UE to the network. The equipment includes: means for receiving information indicating a second BWP associated with a first BWP based on the UE capabilities. The second BWP has a frequency range equal to or less than the first BWP. The equipment includes: means for receiving at least one of control information or data based on the indicated first BWP and second BWP. The equipment may further include: means for receiving a subset of a first SIB within a PDSCH, the first SIB being within the first BWP. The subset of the first SIB is within the second BWP. The equipment may further include: means for receiving a second SIB in the PDSCH within the second BWP. The equipment may further include: means for obtaining system information in the subset of the first SIB and the second SIB by decoding the subset of the first SIB and the second SIB and combining the decoded subset of the first SIB and the decoded second SIB. The apparatus may further include: means for combining DMRS within a portion of the subset of the first SIB in the first BWP with DMRS within the second BWP including the second SIB. The apparatus may further include: means for performing channel estimation based on the combined DMRS. The apparatus may further include: means for receiving a first DCI in a PDCCH within a subset of a first CORESET. The first CORESET is within the first BWP. The subset of the first CORESET is within the second BWP. The subset of the first SIB is received based on the received first DCI. The apparatus may further include: means for receiving a second DCI in the PDCCH within the second CORESET. The second CORESET is within the second BWP, and the second SIB is received based on the received second DCI. The apparatus may further include: means for decoding the first DCI and the second DCI. The apparatus may further include: means for combining at least a portion of the decoded first DCI with the decoded second DCI to obtain a combined DCI. The apparatus may further include: means for receiving information indicating a plurality of CORESETs, a first CORESET of the plurality of CORESETs being within the first BWP, and a second CORESET of the plurality of CORESETs being within the second BWP. The apparatus may further include: means for receiving DCI in a PDCCH within the second CORESET. The apparatus may further include: means for receiving first additional system information within a PDSCH within the second BWP based on the received DCI. The apparatus may further include: means for receiving second additional system information within the PDSCH within the second BWP based on the received DCI.The equipment may further include: a device for combining the first additional system information and the second additional system information to obtain a set of additional system information. The equipment may further include: a device for receiving DCI in the PDCCH within the CORESET. The CORESET is located within the second BWP. The equipment may further include: a device for receiving data in the PDSCH within the second BWP based on the received DCI. The aforementioned means may be one or more of the aforementioned components in the equipment 1102 configured to perform the functions described by the aforementioned means. As described above, the equipment 1102 may include a TX processor 368, an RX processor 356, and a controller / processor 359. As such, in one configuration, the aforementioned means may be a TX processor 368, an RX processor 356, and a controller / processor 359 configured to perform the functions described by the aforementioned means.

[0100] It should be understood that the specific order or hierarchy of each box in the disclosed process / flowchart is an illustration of an example approach. It should be understood that the specific order or hierarchy of each box in these process / flowcharts can be rearranged based on design preferences. In addition, some boxes can be combined or omitted. The attached method claims present the elements of various boxes in an exemplary order and are not meant to be limited to the specific order or hierarchy presented.

[0101] The following examples are merely illustrative and may be combined with aspects of other embodiments or teachings described herein without limitation.

[0102] Example 1 is a wireless communication method of a UE, comprising: sending information indicating UE capabilities of the UE to a network; receiving information indicating a second BWP associated with a first BWP based on the UE capabilities, the second BWP having a frequency range equal to or smaller than the first BWP; and receiving at least one of control information or data based on the indicated first BWP and second BWP.

[0103] In Example 2, the method of Example 1 further includes: receiving a subset of a first SIB within the PDSCH, the first SIB being within the first BWP, and the subset of the first SIB being within the second BWP; receiving a second SIB in the PDSCH within the second BWP; and obtaining system information by decoding at least one of the subset of the first SIB and the second SIB.

[0104] In Example 3, the method of Example 1 or 2 further includes: decoding the subset of the first SIB and the second SIB; and combining at least a portion of the decoded subset of the first SIB with the second SIB.

[0105] In Example 4, the method of any one of Examples 1-3 further includes: receiving the second SIB includes: performing blind detection to identify the second SIB by assuming a position of the second BWP based on a position of the first BWP.

[0106] In Example 5, the method of any one of Examples 1-4 further includes: combining a demodulation reference signal (DMRS) within a portion of the first BWP including a subset of the first SIB with a DMRS within the second BWP including the second SIB; and performing channel estimation based on the combined DMRS, wherein decoding the subset of the first SIB and the second SIB is based on the channel estimation.

[0107] In Example 6, the method of any one of Examples 1-5 further includes: receiving first downlink control information (DCI) in a physical downlink control channel (PDCCH) within a subset of a first control resource set (CORESET), the first CORESET being within the first BWP, the subset of the first CORESET being within the second BWP, the subset of the first SIB being received based on the received first DCI; and receiving a second DCI in the PDCCH within the second CORESET, the second CORESET being within the second BWP, the second SIB being received based on the received second DCI.

[0108] In Example 7, the method of any one of Examples 1-6 further includes: decoding the first DCI and the second DCI; and combining at least a portion of the decoded first DCI with the decoded second DCI to obtain a combined DCI.

[0109] In Example 8, the method of any one of Examples 1-7 further includes: the second SIB includes the same system information as the first SIB.

[0110] In Example 9, the method of any one of Examples 1-8 further includes: receiving information indicating multiple CORESETs, a first CORESET of the multiple CORESETs is located within the first BWP, and a second CORESET of the multiple CORESETs is located within the second BWP; receiving DCI in the PDCCH within the second CORESET; and receiving first additional system information in the PDSCH within the second BWP based on the received DCI.

[0111] In Example 10, the method of any one of Examples 1-9 further includes: the first additional system information is associated with one or more SIBs x, where x>1.

[0112] In Example 11, the method of any one of Examples 1-10 further includes: the first CORESET overlaps with the second CORESET in at least one of time or frequency, wherein the non-overlapping search space of the PDCCH or the overlapping search space of the PDCCH has different IDs of the SIB.

[0113] In Example 12, the method of any one of Examples 1-11 further includes: the first CORESET and the second CORESET do not overlap.

[0114] In Example 13, the method of any one of Examples 1-12 further includes: receiving second additional system information in the PDSCH in the second BWP based on the received DCI; and combining the first additional system information and the second additional system information to obtain a set of additional system information.

[0115] In Example 14, the method of any one of Examples 1-13 further includes: configuration of the second BWP for the second additional system information is different from configuration of the second BWP for the first additional system information.

[0116] In Example 15, the method of any one of Examples 1-14 further includes: receiving at least one of the control information or the data based on the indicated first BWP and second BWP; receiving DCI in the PDCCH within a CORESET, the CORESET being located within the second BWP; and receiving data in the PDSCH within the second BWP based on the received DCI.

[0117] Example 16 is a device comprising one or more processors and one or more memories in electronic communication with the one or more processors, the one or more memories storing instructions executable by the one or more processors to cause a system or equipment to implement a method as in any of Examples 1-15.

[0118] Example 17 is a system or apparatus comprising means for implementing a method as in any one of Examples 1-15 or implementing an apparatus as in any one of Examples 1-15.

[0119] Example 18 is a non-transitory computer-readable medium storing instructions executable by one or more processors that cause the one or more processors to implement a method as in any of Examples 1-15.

[0120] The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be easily understood by those skilled in the art, and the universal principles defined in this article can be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown in this article, but should be granted the full scope consistent with the claims in language, wherein the singular reference of the elements is not intended to represent "there is and only one", but "one or more", unless otherwise stated. Terms such as "if", "when..." and "when..." should be interpreted as meaning "under the condition", rather than implying a direct time relationship or reaction. That is, these phrases (e.g., "when...") do not imply an immediate action in response to the occurrence of an action or during the occurrence of an action, but only imply that an action will occur when the condition is met, and no specific or immediate time constraints are required for the action to occur. The wording "exemplary" is used herein to mean "used as an example, instance or explanation". Any aspect described as "exemplary" herein need not be interpreted as being superior to or superior to other aspects. Unless otherwise stated, the term "some / some" refers to one or more. Combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, and may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, wherein any such combination may include one or more members of A, B, or C. All structural and functional equivalents to the elements of the various aspects described throughout the disclosure that are currently or later known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be covered by the claims. Furthermore, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly recited in the claims. The terms "module," "mechanism," "element," "device," etc. may not be a substitute for the term "means." Thus, no claim element should be construed as a means-plus-function unless the element is explicitly recited using the phrase "means for..."

Claims

1. An apparatus for wireless communication at a user equipment UE, comprising: Memory; as well as at least one processor coupled to the memory and, based at least in part on information stored in the memory, configured to: Receiving a first system information block SIB; identifying a second bandwidth part (BWP) for UEs with reduced capabilities based on the first SIB and UE capabilities, the second BWP being different from the first BWP for other UEs; as well as A second SIB is received within the second BWP.

2. The apparatus of claim 1, further comprising: A transceiver is coupled to the at least one processor. The apparatus according to claim 1 , wherein the second SIB indicates other system information (OSI).

4. The apparatus of claim 3, wherein the first BWP and the second BWP are initial downlink BWPs used to receive the OSI. The apparatus of claim 1 , wherein the second BWP has a smaller bandwidth than the first BWP. The apparatus of claim 1 , wherein the first SIB includes configurations for both the first BWP and the second BWP.

7. The apparatus of claim 6, wherein the configuration comprises a common downlink configuration for a serving cell.

8. The apparatus of claim 1 , wherein the at least one processor configured to receive the second SIB comprises: The at least one processor is configured to: identifying a control resource set CORESET in the second BWP based on the first SIB; decoding a control channel within the CORESET; and A data channel carrying the second SIB is received within the second BWP based on the control channel.

9. The apparatus of claim 1, wherein the at least one processor is further configured to: A third BWP for the reduced-capability UE is identified based on the first SIB and the UE capabilities, wherein the third BWP is an uplink BWP.

10. A method for wireless communication at a user equipment UE, comprising: Receiving a first system information block SIB; identifying a second bandwidth part (BWP) for UEs with reduced capabilities based on the first SIB and UE capabilities, the second BWP being different from the first BWP for other UEs; as well as A second SIB is received within the second BWP. 11 . The method of claim 10 , wherein the second SIB indicates other system information (OSI), wherein the first BWP and the second BWP are initial downlink BWPs used to receive the OSI.

12. The method of claim 10, wherein the second BWP has a smaller bandwidth than the first BWP.

13. The method of claim 10, wherein the first SIB includes configurations for both the first BWP and the second BWP, wherein the configurations include a common downlink configuration for a serving cell.

14. The method of claim 10, wherein receiving the second SIB further comprises: identifying a control resource set CORESET in the second BWP based on the first SIB; Decoding a control channel within the CORESET; as well as A data channel carrying the second SIB is received within the second BWP based on the control channel.

15. The method of claim 10, further comprising: A third BWP for the reduced-capability UE is identified based on the first SIB and the UE capabilities, wherein the third BWP is an uplink BWP.

16. An apparatus for wireless communication at a network entity, comprising: Memory; as well as at least one processor coupled to the memory and, based at least in part on information stored in the memory, configured to: outputting a first system information block SIB; and A second SIB is output within a second bandwidth part BWP for reduced capability user equipment UEs, wherein the second BWP is different from a first BWP for other UEs and is indicated by the first SIB.

17. The apparatus of claim 16, further comprising: A transceiver is coupled to the at least one processor. The apparatus of claim 16 , wherein the second SIB indicates other system information (OSI).

19. The apparatus of claim 18, wherein the first BWP and the second BWP are initial downlink BWPs used to output the OSI.

20. The apparatus of claim 16, wherein the second BWP has a smaller bandwidth than the first BWP.

21. The apparatus of claim 16, wherein the first SIB includes configurations for both the first BWP and the second BWP.

22. The apparatus of claim 21, wherein the configuration comprises a common downlink configuration for a serving cell.

23. The apparatus of claim 16, wherein the at least one processor being configured to output the second SIB comprises: The at least one processor is configured to: A data channel carrying the second SIB is output within the second BWP based on a control channel, wherein a control resource set CORESET is within the second BWP, wherein the control channel is within the CORESET.

24. The apparatus of claim 16, wherein the at least one processor is further configured to: A third BWP for the reduced-capability UE is configured based on the first SIB and the UE capabilities, wherein the third BWP is an uplink BWP.

25. A method for wireless communication at a network entity, comprising: Transmitting a first system information block SIB; as well as A second SIB is transmitted within a second bandwidth part BWP for reduced capability user equipment UEs, wherein the second BWP is different from a first BWP for other UEs and is indicated by the first SIB.

26. The method of claim 25, wherein the second SIB indicates other system information (OSI), wherein the first BWP and the second BWP are initial downlink BWPs used to output the OSI.

27. The method of claim 25, wherein the second BWP has a smaller bandwidth than the first BWP.

28. The method of claim 25, wherein the first SIB includes configurations for both the first BWP and the second BWP, wherein the configurations include a common downlink configuration for a serving cell.

29. The method of claim 25, wherein transmitting the second SIB further comprises: A data channel carrying the second SIB is transmitted within the second BWP based on a control channel, wherein a control resource set CORESET is within the second BWP, wherein the control channel is within the CORESET.

30. The method of claim 25, further comprising: A third BWP for the reduced-capability UE is configured based on the first SIB and the UE capabilities, wherein the third BWP is an uplink BWP.

Images