Selection of different initial bandwidth portions for user equipment with reduction capabilities

Abstract

The present disclosure provides a system, method, and apparatus, including a computer program encoded on a computer storage medium, for a reduced capability (RedCap) user equipment (UE) and supporting cell. The RedCap UE is configured with multiple bandwidth portions (BWPs). The maximum bandwidth of the RedCap UE is lower than the maximum bandwidth of multiple non-RedCap UEs. The UE receives a cell-defined synchronization signal block (CD-SSB) that defines a shared initial downlink BWP for multiple RedCap UEs and multiple non-RedCap UEs. The UE switches to separate initial downlink BWPs for the multiple RedCap UEs. The UE accesses a cell via the separate initial downlink BWPs. The UE receives configurations of active downlink BWPs for the multiple RedCap UEs. The UE determines whether to switch from the active downlink BWP to the shared initial BWP or the separate initial downlink BWP to obtain information such as updated system information, system measurements, and uplink configuration information.

Description

Technical Field

[0001] Cross - reference to Related Applications This application claims priority to U.S. Provisional Application No. 63 / 234,966, filed Aug. 19, 2021, and U.S. Patent Application No. 17 / 820,371, filed Aug. 17, 2022, both entitled "SELECTION OF DIFFERENT INITIAL BANDWIDTH PARTS FOR REDUCED CAPABILITY USER EQUIPMENT", which have been assigned to the assignee of this application and are hereby incorporated by reference in their entirety.

[0002] This disclosure relates to wireless communication including selection of different initial bandwidth parts for reduced - capability user equipment.

Background Art

[0003] Wireless communication systems are widely deployed to provide various remote communication services such as telephony, video, data, messaging, and broadcast. A typical wireless communication system can utilize multiple - access technologies that can support 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.

[0004] These multiple access technologies are being adopted in various telecommunications standards to provide a common protocol that enables various wireless devices to communicate at the city, national, regional, and global levels. An exemplary telecommunications standard is 5G New Radio (NR). 5G NR is part of the ongoing evolution of mobile broadband published 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. 5G NR includes services related to Enhanced Mobile Broadband (eMBB), Massive Machine-Type Communications (mMTC), and Ultra-High Reliability Low Latency Communications (URLLC). Some aspects of 5G NR may be based on the 4G Long-Term Evolution (LTE) standard. [Overview of the project]

[0005] The systems, methods, and devices of this disclosure each have several innovative aspects, and none of these aspects alone constitute the desirable characteristics disclosed herein.

[0006] One innovative aspect of the subject matter described herein may be implemented in a method for acquiring information in a RedCap User Equipment (RedCap UE). The method includes receiving a cell-defined synchronization signal block (CD-SSB) that defines a shared initial downlink bandwidth portion (BWP) for a plurality of RedCap UEs and a plurality of non-RedCap UEs. The method includes switching to separate initial downlink BWPs for the plurality of RedCap UEs. The method includes accessing the cell via the separate initial downlink BWP. The method includes receiving the configuration of the active downlink BWP for the plurality of RedCap UEs. The method includes determining whether to switch from the active downlink BWP to a shared initial BWP or a separate initial downlink BWP in order to acquire information.

[0007] In another innovative aspect, the Disclosure provides a method for initiating a random access procedure. The method includes receiving a cell-defined synchronization signal block (CD-SSB) at a reduced capability user device (RedCap UE) that defines a shared initial downlink bandwidth portion (BWP) for a plurality of RedCap UEs and a plurality of non-RedCap UEs. The method includes receiving a non-CD-SSB at a RedCap UE for separate initial downlink BWPs for the plurality of RedCap UEs. The method includes selecting one of the CD-SSB or the non-CD-SSB to transmit a random access message based on system information received on the shared initial BWP or the separate initial BWP.

[0008] In another innovative aspect, the Disclosure provides a method for configuring BWP-specific uplink parameters. The method includes receiving a cell-defined synchronization signal block (CD-SSB) that defines a shared initial downlink bandwidth portion (BWP) for a plurality of RedCap UEs and a plurality of non-RedCap UEs. The method includes switching to separate initial downlink BWPs for the plurality of RedCap UEs and initial uplink BWPs for the plurality of RedCap UEs. The method includes receiving BWP-specific uplink parameters for the initial uplink BWPs for the plurality of RedCap UEs or active uplink BWPs for the plurality of RedCap UEs, where the initial uplink BWPs for the plurality of RedCap UEs and active uplink BWPs for the plurality of RedCap UEs are configured at the edge of the carrier bandwidth.

[0009] The disclosure also provides an apparatus (e.g., a UE) including memory for storing computer executable instructions and at least one processor configured to execute computer executable instructions in order to perform at least one of the above methods; an apparatus including means for performing at least one of the above methods; and a non-temporary computer-readable medium for storing computer executable instructions for performing at least one of the above methods.

[0010] One innovative aspect of the subject matter described herein may be implemented in a manner that supports RedCap UEs (for example, by a base station). The method includes transmitting a cell-defined synchronization signal block (CD-SSB) that defines a shared initial downlink bandwidth portion (BWP) for a plurality of RedCap UEs and a plurality of non-RedCap UEs. The method includes transmitting non-CD-SSBs to separate initial downlink BWPs for the plurality of RedCap UEs. The method includes configuring an active downlink BWP for a RedCap UE that includes a paging search space. The method includes transmitting a paging physical downlink control channel (PDCCH) indicating that system information has been updated. The method includes transmitting the updated system information on a shared initial downlink BWP, a separate initial downlink BWP, or an active downlink BWP, as indicated by the paging PDCCH.

[0011] In another innovative aspect, the Disclosure provides a method for supporting RedCap UEs with BWP-specific uplink parameters. The method includes transmitting a cell-defined synchronization signal block (CD-SSB) that defines a shared initial downlink bandwidth portion (BWP) for a plurality of RedCap UEs and a plurality of non-RedCap UEs. The method includes transmitting non-CD-SSBs for separate initial downlink BWPs for the plurality of RedCap UEs and initial uplink BWPs for the plurality of RedCap UEs. The method includes transmitting BWP-specific uplink parameters for the initial uplink BWPs for the plurality of RedCap UEs or active uplink BWPs for the plurality of RedCap UEs, where the initial uplink BWPs for the plurality of RedCap UEs and the active uplink BWPs for the plurality of RedCap UEs are configured at the edge of the carrier bandwidth.

[0012] The disclosure also provides an apparatus (e.g., BS) including memory for storing computer executable instructions and at least one processor configured to execute computer executable instructions in order to perform at least one of the above methods; an apparatus including means for performing at least one of the above methods; and a non-temporary computer-readable medium for storing computer executable instructions for performing at least one of the above methods.

[0013] Details of one or more implementations of the subject matter described herein are shown in the accompanying drawings and the following description. Other features, embodiments, and advantages will become apparent from the description, drawings, and claims. Note that the relative dimensions in the following figures may not be drawn to scale. [Brief explanation of the drawing]

[0014] [Figure 1] This figure shows an example of a wireless communication system and access network. [Figure 2A] This is a diagram showing an example of the first frame. [Figure 2B] This figure shows an example of a DL channel within a subframe. [Figure 2C] This figure shows an example of the second frame. [Figure 2D] This figure shows an example of a subframe. [Figure 3] This diagram shows an example of a base station (BS) and user equipment (UE) within an access network. [Figure 4] This figure shows an example of a cell configuration that includes a separate initial bandwidth portion (BWP) and active BWP for Reduction Capability (RedCap) UE. [Figure 5] This figure shows another example of a cell configuration including active BWPs for multiple RedCap UEs. [Figure 6] This figure shows an example of a technique for obtaining updated system information in a configuration with multiple BWPs. [Figure 7] This message diagram shows example messages for managing multiple BWPs. [Figure 8] This is a conceptual data flow diagram illustrating the data flow between different means / components within an exemplary BS. [Figure 9] This is a conceptual data flow diagram illustrating the data flow between different means / components within an exemplary UE. [Figure 10] This is a flowchart illustrating one example of a method for obtaining information in a configuration where the UE has multiple BWPs. [Figure 11] This is a flowchart illustrating one example of a method for initiating a random access procedure in a configuration where the UE has multiple BWPs. [Figure 12] This is a flowchart illustrating an example of a method for configuring BWP-specific uplink parameters in a configuration where the UE has multiple BWPs. [Figure 13] This is a flowchart illustrating an exemplary method for BS to support RedCap UE with multiple BWPs. [Figure 14]A flowchart of an exemplary method for configuring BWP-specific uplink parameters in a configuration where a BS has a plurality of BWPs.

[0015] Like reference numerals and designations in the various drawings refer to like elements.

BRIEF DESCRIPTION OF THE DRAWINGS

[0016] The following description is directed to several implementations for the purpose of describing the inventive aspects of the present disclosure. However, one of ordinary skill in the art will readily recognize that the teachings herein can be applied in many different ways. Some of the examples in the present disclosure are based on wireless and wired local area network (LAN) communications according to the Institute of Electrical and Electronics Engineers (IEEE) 802.11 wireless standard, the IEEE 802.3 Ethernet standard, and the IEEE 1901 power line communication (PLC) standard. However, the described implementations can be implemented in any of the IEEE 802.11 standards, the Bluetooth® standard, code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), Global System for Mobile Communications (GSM) for mobile communications, GSM / general packet radio service (GPRS), enhanced data GSM environment (EDGE), terrestrial trunked radio (TETRA), wideband CDMA (W-CDMA), evolution data optimized (EV-DO), 1xEV-DO, EV-DO Rev A, EV-DO Rev B, high speed packet access (HSPA), high speed downlink packet access (HSDPA), high speed uplink packet access (HSUPA), evolved high speed packet access (HSPA+), long term evolution (LTE), AMPS, or any other known signals for transmitting and receiving in a wireless, cellular, or Internet of Things (IoT) network such as a system utilizing the technology of 3G technology, 4G technology, or 5G technology, or further implementations thereof, in any device, system, or network capable of communicating.

[0017] A user equipment (UE) can utilize a subset of the total cell bandwidth, called a bandwidth part (BWP). For example, in 5G NR Releases 15 and 16, the maximum BWP size is 100 MHz. In higher frequency ranges (e.g., FR 2), the size of the bandwidth part can increase. Such large bandwidths can be designed to meet the demand for premium smartphones that utilize enhanced mobile broadband (eMBB) and other use cases such as ultra-reliable low latency communication (URLLC) and vehicle-to-everything (V2X). In the case of reduced-capability or some devices called multiple RedCap devices, the maximum size of the BWP can be reduced to provide power savings and complexity reduction. That is, a first type of UE can be capable of using a BWP with a maximum BWP size, and a RedCap UE can be a second type of UE having a maximum BWP size lower than that of the first type of UE for a frequency range. Exemplary multiple RedCap devices can include wearables, industrial wireless sensor networks (IWSNs), surveillance cameras, and low-end smartphones. In some cases, the data rate for multiple RedCap devices can be achieved with a BWP size of less than 100 MHz. In an exemplary implementation, in FR1, the maximum device bandwidth of a non-RedCap device can be 100 MHz, and the maximum device bandwidth of a RedCap device can be 20 MHz. In FR2, the maximum device bandwidth of a non-RedCap device can be 200 MHz, and the maximum device bandwidth of a RedCap device can be 100 MHz. Other maximum device bandwidths may be applicable in other implementations.

[0018] Multiple RedCap devices can coexist with multiple non-RedCap devices on the same cell. However, the reduced bandwidth of multiple RedCap devices may be incompatible with some system configurations. For example, the physical uplink control channel (PUCCH) is typically allocated to the edge of the uplink BWP to enable continuous physical uplink shared channel (PUSCH) and random access channel (RACH) transmissions near the center of the uplink BWP. Broadcast signaling for initial access (e.g., channel raster and synchronization signal block (SSB)) is typically transmitted near the center of the downlink BWP. Therefore, a RedCap UE with a reduced BWP size may not be able to transmit over the PUCCH and receive the SSB. One proposal to accommodate multiple RedCap UEs is to provide separate initial BWPs for the multiple RedCap devices carrying the downlink signaling. These separate initial BWPs for multiple RedCap devices can be located near the edge of the carrier bandwidth so that the PUCCH resources overlap with the PUCCH resources for the multiple non-RedCap devices. Some proposals suggest that an active BWP may also be configured for multiple RedCap devices. While multiple BWPs can provide flexibility for multiple RedCap devices, they introduce additional signaling issues. Generally, a RedCap UE can monitor one BWP at a time, but signaling may occur on different BWPs. For example, paging for system information updates, system measurement, random access procedures, radio resource control (RRC) re-establishment, and uplink configuration can be affected by the presence of multiple BWPs.

[0019] In one embodiment, the disclosure provides signaling for the use of multiple BWPs for a RedCap UE. A RedCap UE may receive cell-defined SSBs (CD-SSBs) on a shared initial BWP applicable to both multiple RedCap UEs and multiple non-RedCap UEs. A CD-SSB refers to a set of SSBs located at SSB raster points. Thus, CD-SSBs can be discovered by the UE performing the initial access. A RedCap UE may receive non-CD SSBs on a separate initial BWP for multiple RedCap UEs. Non-CD-SSBs are not located at raster points. The UE only knows the location of the non-CD-SSBs after connecting to the network (e.g., the shared initial BWP). A RedCap UE may further be configured with an active BWP for multiple RedCap UEs. A RedCap UE can determine whether to switch from the active BWP to either the shared initial BWP or the separate initial BWP. For example, if the active BWP is configured with a paging search space, the RedCap UE can receive a paging physical downlink control channel (PDCCH) and determine whether to receive updated system information on a shared initial BWP, a separate initial BWP, or the active BWP. If the active BWP is not configured with a paging search space, the RedCap UE can periodically switch to a separate initial BWP to receive paging messages. Similarly, the configuration of the active BWP may indicate measurement resources (e.g., for Layer 3 measurements) on either the shared initial BWP, a separate initial BWP, or the active BWP, and measurement gaps on the active BWP. For example, the RedCap UE can measure both CD-SSB on the shared initial downlink BWP and non-CD-SSB on the separate initial downlink BWP. The default initial downlink BWP may be standardized for fallback during RRC re-establishment or RRC release with redirection, or the network may indicate when separate initial downlink BWPs for multiple RedCap UEs are available on adjacent cells.

[0020] For random access procedures, system information can specify whether the RedCap UE should use CD-SSB or non-CD-SSB to send the initial random access message. The RedCap UE may use CD-SSB for the initial transmission of the random access message and switch to non-CD-SSB if retransmission is required and there is time to measure non-CD-SSB before retransmission. More generally, uplink transmission parameters may be BWP-specific (for example, they may differ between the initial uplink BWP for multiple RedCap UEs and the active initial uplink BWP for multiple RedCap UEs). The RedCap UE may receive BWP-specific uplink parameters in the BWP configuration, BWP switching commands, or system information updates for multiple RedCap UEs.

[0021] Certain implementations of the subject matter described herein may be carried out to achieve one or more of the following potential benefits: Multiple RedCap devices may use a narrower bandwidth that can conserve power while coexisting on the same carrier bandwidth as multiple non-RedCap UEs. Multiple RedCap UEs may be configured with multiple BWPs and may switch BWPs to acquire information without interfering with the operation of multiple non-RedCap UEs.

[0022] Several embodiments of telecommunications systems are presented here with respect to various devices and methods. These devices and methods are described in the following detailed description and are shown 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.

[0023] For example, an element, any part of an element, or any combination of elements may be implemented as a “processing system” comprising 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 a chip (SoC), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionalities described throughout this disclosure. A processor may include, or be coupled to, an interface from which it can acquire or output signals. A processor may acquire signals through an interface and output signals through an interface. In some implementations, the interface may be a printed circuit board (PCB) transmission line. In some other implementations, the interface may include a wireless transmitter, a wireless transceiver, or a combination thereof. For example, the interface may include a radio frequency (RF) transceiver that can be implemented to receive or transmit signals, or both. One or more processors in the processing system may run software.Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc., regardless of whether they are called software, firmware, middleware, microcode, hardware description languages, or otherwise.

[0024] Therefore, in one or more exemplary implementations, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored on a computer-readable medium or encoded on a computer-readable medium as one or more instructions or codes. Computer-readable medium includes computer storage media, which may be called non-temporary computer-readable medium. Non-temporary computer-readable medium may exclude temporary signals. The storage medium may be any available medium accessible by a computer. Such computer-readable medium may include, but not limited to, random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of the computer-readable media of the types described above, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer.

[0025] Figure 1 shows an example of a wireless communication system and access network 100. The wireless communication system (also called a Wireless Wide Area Network (WWAN)) includes a base station 102, an UE 104, an Advanced Packet Core (EPC) 160, and another core network 190 (such as a 5G core (5GC)). The base station 102 may include macrocells (high-power cellular base stations) or small cells (low-power cellular base stations). Macrocells include base stations. Small cells include femtocells, picocells, and microcells. Small cells include femtocells, picocells, and microcells. The base station 102 may be configured in a Disaggregated RAN (D-RAN) or Open RAN (O-RAN) architecture, where functionality is divided among multiple units such as a central unit (CU), one or more distributed units (DUs), or radio units (RUs). Such an architecture may be configured to utilize a protocol stack that is logically divided among one or more units (such as one or more CUs and one or more DUs). In some embodiments, the CU may be implemented within an edge RAN node, and in some embodiments, one or more DUs may be co-located with the CU or geographically distributed across one or more RAN nodes. The DUs may be implemented to communicate with one or more RUs.

[0026] In some implementations, one or more of the UEs 104 may include a RedCap BWP component 140 that manages multiple BWPs for RedCap UEs. The RedCap BWP component 140 may include a shared initial BWP component 142 configured to receive CD-SSBs that define shared initial BWPs for multiple RedCap UEs and multiple non-RedCap UEs. The RedCap BWP component 140 may include a separate initial BWP component 144 configured to switch to separate initial downlink BWPs for multiple RedCap UEs. For example, the separate initial BWP component 144 may be configured to receive non-CD-SSBs for separate initial downlink BWPs for multiple RedCap UEs. The RedCap BWP component 140 can access cells via the separate initial downlink BWPs. The RedCap BWP component 140 may include an active BWP component 146 configured to receive configurations for active downlink BWPs for multiple RedCap UEs. The RedCap BWP component 140 may include a BWP switching component configured to determine whether to switch from an active downlink BWP to a shared initial BWP or a separate initial downlink BWP to obtain information. In some implementations, the RedCap BWP component 140 may include a random access component 910 configured to select either CD-SSB or non-CD-SSB to send random access messages based on system information received on the shared initial BWP or a separate initial BWP. In some implementations, the RedCap BWP component 140 may optionally include an uplink configuration component 920 (Figure 9) configured to receive BWP-specific uplink parameters for initial uplink BWPs for multiple RedCap UEs or active uplink BWPs for multiple RedCap UEs.Initial uplink BWPs for multiple RedCap UEs and active uplink BWPs for multiple RedCap UEs may be configured at the edge of the carrier bandwidth.

[0027] In some implementations, one or more of the base stations 102 may include a RedCap BWP control component 120 configured to manage multiple BWPs for multiple RedCap UEs. As shown in Figure 8, the RedCap BWP control component 120 may include a shared initial BWP component 810 configured to transmit CD-SSBs defining a shared initial BWP for multiple RedCap UEs and multiple non-RedCap UEs. The RedCap BWP control component 120 may include a separate initial BWP component 820 configured to transmit non-CD-SSBs for separate initial downlink BWPs for multiple RedCap UEs. The RedCap BWP control component 120 may include an active BWP component 830 configured to constitute an active downlink BWP for a RedCap UE that includes a paging search space. The RedCap BWP control component 120 may include a paging component 840 configured to transmit a paging PDCCH indicating that system information has been updated. The RedCap BWP control component 120 may include a system information update component 850 configured to transmit updated system information on a shared initial downlink BWP, a separate initial downlink BWP, or an active downlink BWP, as shown by the paging PDCCH. In some implementations, the RedCap BWP control component 120 may optionally include an uplink configuration component 860 configured to transmit BWP-specific uplink parameters to an initial uplink BWP for multiple RedCap UEs or an active uplink BWP for multiple RedCap UEs. The initial uplink BWPs for multiple RedCap UEs and the active uplink BWPs for multiple RedCap UEs may be configured at the edge of the carrier bandwidth.

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

[0029] Base station 102 can communicate wirelessly with UE 104. Each base station 102 may provide communication coverage to its respective geographical coverage area 110. There may be overlapping geographical 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 containing both small cells and macro cells is sometimes known as a heterogeneous network. A heterogeneous network may also include home-evolved node B (eNB) (HeNB) that can serve restricted groups called limited subscriber groups (CSGs). The communication link 112 between base station 102 and UE 104 may include UL (also called reverse link) transmission from UE 104 to base station 102, or DL ​​(also called forward link) transmission from base station 102 to UE 104. Communication link 112 may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, or transmit diversity. The communication link may pass through one or more carriers. Base station 102 / UE104 may use a spectrum with bandwidth up to Y MHz per carrier (e.g., 5, 10, 15, 20, 100, 400 MHz) allocated in carrier aggregation up to a total of Yx MHz (x component carriers) used for transmission in each direction. Carriers may or may not be adjacent to each other. Carrier allocation may be asymmetric with respect to DL and UL (such as more or fewer carriers being allocated to DL than to UL). Component carriers may include primary component carriers and one or more secondary component carriers. Primary component carriers may be called primary cells (PCells), and secondary component carriers may be called secondary cells (SCells).

[0030] Several UE104s may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use the DL / UL WWAN spectrum. The D2D communication link 158 may use one or more sidelink channels, such as the physical sidelink broadcast channel (PSBCH), physical sidelink discovery channel (PSDCH), physical sidelink shared channel (PSSCH), and physical sidelink control channel (PSCCH). D2D communication may be conducted through various wireless D2D communication systems, such as FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

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

[0032] Small cell 102' may operate in a licensed frequency spectrum or an unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, small cell 102' may employ NR and may use the same 5GHz unlicensed frequency spectrum used by Wi-Fi AP150. Small cell 102' employing NR in an unlicensed frequency spectrum may boost coverage to the access network or increase the capacity of the access network.

[0033] The base station 102 may include an eNB, g-node B (gNB), or other type of base station, whether it is a small cell 102' or a large cell (such as a macro base station). Some base stations, such as gNB180, may operate in one or more frequency bands within the electromagnetic spectrum.

[0034] The electromagnetic spectrum is often subdivided into various classes, bands, channels, etc., based on frequency / wavelength. In 5G NR, two initial operating bands are identified as frequency range designations FR1 (410 MHz–7.125 GHz) and FR2 (24.25 GHz–52.6 GHz). Frequencies between FR1 and FR2 are often referred to as intermediate band frequencies. Although a portion of FR1 is above 6 GHz, FR1 is often referred to (interchangeably) as the "sub-6 GHz" band in various documents and papers. A similar nomenclature issue sometimes arises with respect to FR2, which is often referred to (interchangeably) as the "millimeter wave" (mmW) band in documents and papers, even though it is different from the extremely high frequency (EHF) band (30 GHz–300 GHz) which is identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0035] With the above aspects in mind, unless otherwise specified, terms such as "sub-6GHz" may broadly refer to frequencies that may be below 6GHz, within FR1, or include intermediate band frequencies when used herein. Furthermore, unless otherwise specified, terms such as "millimeter wave" may broadly refer to frequencies that may include intermediate band frequencies, within FR2, or within the EHF band when used herein. Communications using the mmW radio frequency band have extremely high path loss and short distances. The mmW base station 180 may utilize beamforming 182 in conjunction with UE 104 to compensate for path loss and short distances.

[0036] EPC160 may include Mobility Management Entity (MME) 162, another MME 164, Serving Gateway 166, Multimedia Broadcast Multicast Service (MBMS) Gateway 168, Broadcast Multicast Mobility Management Entity (BM-SC) 170, and Packet Data Network (PDN) Gateway 172. MME 162 may communicate with Home Subscriber Server (HSS) 174. MME 162 is the control node that handles signaling between UE 104 and EPC160. Generally, MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are forwarded through Serving Gateway 166, which itself is connected to PDN Gateway 172. PDN Gateway 172 provides UEIP address allocation and other functions. PDN Gateway 172 and BM-SC 170 are connected to IP Service 176. IP service 176 may include the Internet, intranet, IP multimedia subsystem (IMS), PS streaming service, or other IP services. BM-SC170 may provide functionality for MBMS user service provisioning and distribution. BM-SC170 may act 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 collecting eMBMS-related billing information.

[0037] The core network 190 may include Access and Mobility Management Function (AMF) 192, other AMFs 193, Session Management Function (SMF) 194, and User Plane Function (UPF) 195. AMF 192 may communicate with Unified Data Management (UDM) 196. AMF 192 is a control node that handles signaling between UE 104 and the core network 190. Generally, AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are forwarded through UPF 195. UPF 195 provides IP address allocation for the UE and other functions. UPF 195 is connected to IP service 197. IP service 197 may include the Internet, intranet, IP multimedia subsystem (IMS), PS streaming service, or other IP services.

[0038] A base station may include, or be referred to as, a gNB, node B, eNB, access point, base transceiver station, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), transmit / receive point (TRP), or any other preferred term. Base station 102 provides UE104 with an access point to EPC160 or core network 190. Examples of UE104 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (such as MP3 players), cameras, game consoles, tablets, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similar functional devices. Some of UE104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, cardiac monitors, etc.). The UE104 may also be referred to as station, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or several other preferred terms.

[0039] While 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, including future 6G technologies.

[0040] Figure 2A is Figure 200, which shows an example of a first frame. Figure 2B is Figure 230, which shows an example of a DL channel within a subframe. Figure 2C is Figure 250, which shows an example of a second frame. Figure 2D is Figure 280, which shows an example of a subframe. The 5G NR frame structure may be FDD, where subframes within a set of subcarriers are dedicated to either DL or UL for a given set of subcarriers (carrier system bandwidth), or it may be TDD, where subframes within a set of subcarriers are dedicated to both DL and UL for a given set of subcarriers (carrier system bandwidth). A subset of the total cell bandwidth of a cell is called a Bandwidth Part (BWP), and bandwidth adaptation is achieved by configuring a UE using BWPs and informing the UE which of the configured BWPs is currently active. In one embodiment, a Narrow Bandwidth Part (NBWP) refers to a BWP having a bandwidth less than or equal to the maximum configurable bandwidth of a BWP. The bandwidth of an NBWP is smaller than the carrier system bandwidth. NBWPs may hop across the carrier system bandwidth. Hopping allows for the provision of frequency diversity gain without increasing the BWP size, or using a narrower active BWP.

[0041] In the example provided in Figures 2A and 2C, the 5G NR frame structure is assumed to be TDD, with subframe 4 constructed using slot format 28 (mostly containing DL), where D is DL, U is UL, and X is flexible for use between DL and UL, and subframe 3 constructed using slot format 34 (mostly containing UL). Although subframes 3 and 4 are shown in slot formats 34 and 28 respectively, any particular subframe may be constructed in any of the various available slot formats 0 to 61. Slot formats 0 and 1 are all DL and UL, respectively. The other slot formats 2 to 61 include a mixture of DL, UL, and flexible symbols. The UE is constructed in slot format (dynamically via DL Control Information (DCI) or quasi-statically / statically via 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 which is TDD.

[0042] Other wireless communication technologies may have different frame structures or different channels. A frame (e.g., 10 milliseconds (ms)) may be divided into 10 subframes (1 ms) of equal size. Each subframe may contain one or more time slots. A subframe may also contain minislots that may contain 7, 4, or 2 symbols. Each slot may contain 7 or 14 symbols depending on the slot configuration. In slot configuration 0, each slot may contain 14 symbols, and in slot configuration 1, each slot may contain 7 symbols. Symbols on 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 called single-carrier frequency-division multiple access (SC-FDMA) symbols) (for power-limited scenarios, limited to single-stream transmission). The number of slots in a subframe depends on the slot configuration and numerology. Slot configuration 0 allows 1, 2, 4, 8, 16, and 32 slots per subframe, respectively, for different numerologies μ0-5. Slot configuration 1 allows 2, 4, and 8 slots per subframe, respectively, for different numerologies 0-2. Therefore, for slot configuration 0 and numerology μ, there are 14 symbols / slot and 2 μ There are 2 slots / subframes. Subcarrier interval and symbol length / duration are functions of numerology. The subcarrier interval is 2 μ*The subcarrier interval may be equal to 15 kHz, where μ is numerology 0 to 5. Thus, numerology μ=0 has a subcarrier interval of 15 kHz, and numerology μ=5 has a subcarrier interval of 480 kHz. The symbol length / duration is inversely proportional to the subcarrier interval. Figures 2A to 2D provide examples of slot configuration 0, which has 14 symbols per slot, and numerology μ=2, which has 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier interval is 60 kHz, and the symbol duration is approximately 16.67 microseconds (μs).

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

[0044] As shown in Figure 2A, some of the REs carry a reference (pilot) signal (RS) to the UE. The RS is used for channel estimation at the UE, and for certain configurations, it is a demodulated RS (DM-RS) (where 100x is the port number). x Although shown as such, other DM-RS configurations are possible) and may include a channel state information reference signal (CSI-RS). RS may also include beam measurement RS (BRS), beam improvement RS (BRRS), and phase tracking RS (PT-RS).

[0045] Figure 2B shows an example of various DL channels within a frame subframe. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs), each CCE containing nine RE groups (REGs), and each REG containing four consecutive REs within the OFDM symbol. The primary synchronization signal (PSS) may be located within symbol 2 of a particular subframe of the frame. The PSS is used by UE104 to determine the subframe / symbol timing and physical layer identification information. The secondary synchronization signal (SSS) may be located within symbol 4 of a particular subframe of the frame. The SSS is used by the UE to determine the physical layer cell identification information group number and wireless frame timing. Based on the physical layer identification information and physical layer cell identification information group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS described above. A physical broadcast channel (PBCH) carrying a Master Information Block (MIB) may be logically grouped with PSS and SSS to form a Synchronization Signal (SS) / PBCH Block (SSB). The MIB provides the number of RBs and the System Frame Number (SFN) within the system bandwidth. A physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted through the PBCH, such as System Information Blocks (SIBs), and paging messages.

[0046] As shown in Figure 2C, some of the REs carry DM-RS for channel estimation at the base station (shown as R for one particular configuration, but other DM-RS configurations are possible). The UE may transmit DM-RS for the physical uplink control channel (PUCCH) and DM-RS for the physical uplink sharing channel (PUSCH). PUSCH DM-RS may be transmitted in the first one or two symbols of the PUSCH. PUCCH DM-RS may be transmitted in different configurations depending on whether a short or long PUCCH is transmitted and depending 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 a subframe. The SRS may have a comb structure, and the UE may transmit the SRS on one of the combs. The SRS may be used by the base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

[0047] Figure 2D shows examples of various UL channels within a frame subframe. In one configuration, the PUCCH may be located as shown. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and HARQ ACK / NACK feedback. The PUCCH carries data and may additionally be used to carry buffer status reports (BSR), power headroom reports (PHR), or UCI.

[0048] Figure 3 shows an example of base stations 310 and UE350 in an access network. In DL, IP packets from EPC160 can be provided to controller / processor 375. Controller / processor 375 implements Layer 3 and Layer 2 functions. Layer 3 includes the Radio Resource Control (RRC) layer, and Layer 2 includes the Service Data Adaptive Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Medium Access Control (MAC) layer. The controller / processor 375 provides RRC layer functions associated with system information (MIB, SIB, etc.), RRC connection control (RRC connection paging, RRC connection establishment, RRC connection correction, and RRC connection release, etc.), mobility between radio access technologies (RATs), and broadcasting of measurement configurations for UE measurement reporting; PDCP layer functions associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions associated with forwarding upper layer packet data units (PDUs), error correction by ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with mapping between logical channels and transport channels, multiplexing MAC SDUs onto transport blocks (TBs), demultiplexing MAC SDUs from TBs, scheduling information reporting, error correction by HARQ, priority processing, and logical channel prioritization.

[0049] The transmit (TX) processor 316 and the receive (RX) processor 370 implement Layer 1 functions 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) coding / 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 mapping to signal constellations based on various modulation schemes (such as binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), and M-quadrature amplitude modulation (M-QAM)). Encoded and modulated symbols may be divided into parallel streams. Each stream can be mapped to an OFDM subcarrier, multiplexed with a reference signal (such as a pilot) in the time domain or frequency domain, and synthesized together using an inverse fast Fourier transform (IFFT) to generate a physical channel that carries a time-domain OFDM symbol stream. The OFDM streams are spatially precoded to generate multiple spatial streams. Channel estimates from channel estimator 374 may be used to determine the coding and modulation scheme, as well as for spatial processing. Channel estimates may be derived from a reference signal or channel state feedback transmitted by UE350. Each spatial stream may be supplied to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX can modulate RF carriers on its respective spatial stream for transmission.

[0050] In UE350, each receiver 354RX receives signals via its respective antenna 352. Each receiver 354RX reconstructs the information modulated on the RF carrier and provides this information to the receiver (RX) processor 356. The TX processor 368 and RX processor 356 implement Layer 1 functions related to various signal processing functions. The RX processor 356 may perform spatial processing on the information to reconstruct any spatial stream destined for UE350. Multiple spatial streams, when destined for UE350, can be combined into a single OFDM symbol stream by the RX processor 356. The RX processor 356 uses a Fast Fourier Transform (FFT) to convert the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal contains a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, and the reference signal, are reconstructed and demodulated by determining the most likely signal constellation point transmitted by the base station 310. These soft decisions may be based on channel estimates calculated by the channel estimator 358. The soft decisions are decoded and deinterleaved to reconstruct the data and control signals initially transmitted by the base station 310 on the physical channel. The data and control signals are provided to the controller / processor 359, which implements Layer 3 and Layer 2 functions.

[0051] The controller / processor 359 may be associated with memory 360, which stores program code and data. Memory 360 is sometimes referred to as computer-readable media. In UL, the controller / processor 359 provides demultiplexing between transport and logical channels, packet reassembly, decoding, header decompression, and control signal processing to reconstruct IP packets from the EPC160. The controller / processor 359 is also responsible for error detection using the ACK or NACK protocol to support HARQ operation.

[0052] Similar to the functions described in relation to DL transmission by base station 310, the controller / processor 359 provides RRC layer functions associated with system information (MIB, SIB, etc.) acquisition, RRC connection, and measurement reporting; PDCP layer functions associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions associated with forwarding upper layer PDUs, error correction by ARQ, concatenation, segmentation, and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with mapping between logical channels and transport channels, multiplexing MAC SDUs onto TB, demultiplexing MAC SDUs from TB, scheduling information reporting, error correction by HARQ, priority processing, and logical channel prioritization.

[0053] The channel estimate derived by the channel estimator 358 from a reference signal or feedback transmitted by the base station 310 may be used by the TX processor 368 to select an appropriate coding and modulation scheme and to facilitate spatial processing. The spatial stream generated by the TX processor 368 can be provided to different antennas 352 via a separate transmitter 354TX. Each transmitter 354TX can modulate the RF carrier in its respective spatial stream for transmission.

[0054] UL transmission is processed at base station 310 in a manner similar to that described for receiver functions in UE350. Each receiver 318RX receives the signal via its respective antenna 320. Each receiver 318RX reconstructs the information modulated on the RF carrier and provides this information to RX processor 370.

[0055] The controller / processor 375 can be associated with memory 376, which stores program code and data. Memory 376 is sometimes referred to as computer-readable media. In UL, the controller / processor 375 performs demultiplexing between transport and logical channels, packet reassembly, decoding, header decompression, and control signal processing to reconstruct IP packets from the UE350. IP packets from the controller / processor 375 can be served to the EPC160. The controller / processor 375 is also responsible for error detection using the ACK or NACK protocol to support HARQ operation.

[0056] At least one of the TX processor 368, RX processor 356, and controller / processor 359 may be configured to execute an embodiment related to the RedCap BWP component 140 shown in Figure 1. For example, memory 360 may contain executable instructions that define the RedCap BWP component 140. The TX processor 368, RX processor 356, and / or controller / processor 359 may be configured to execute the RedCap BWP component 140.

[0057] At least one of the TX processor 316, RX processor 370, and controller / processor 375 may be configured to execute an embodiment relating to the RedCap BWP control component 120 shown in Figure 1. For example, memory 376 may contain executable instructions that define the RedCap BWP control component 120. The TX processor 316, RX processor 370, and / or controller / processor 375 may be configured to execute the RedCap BWP control component 120.

[0058] Figure 4 shows an example of a configuration 400 of multiple BWPs for a RedCap UE on a carrier bandwidth 410. The carrier bandwidth 410 may be, for example, the maximum system bandwidth. For example, in 5G NR FR1, the maximum system bandwidth may be 100 MHz. The cell may be configured with a shared initial UL BWP 420 and a shared initial DL BWP 430. The shared initial UL BWP 420 and the shared initial DL BWP 430 may be used by both multiple RedCap UEs and multiple non-RedCap UEs. A non-RedCap UE or baseline device may refer to a first type of UE capable of using BWPs of the maximum BWP size, and a RedCap UE may refer to a second type of UE having a lower maximum BWP size for a frequency range than the first type of UE. The descriptions of non-RedCap UEs and RedCap UEs here may be equally applicable to the first type of UE and the second type of UE.

[0059] The difference between a first type of UE (e.g., a non-RedCap UE) and a second type of UE (e.g., a RedCap UE) can result in different uses of the shared initial UL BWP 420 and shared initial DL BWP 430. In particular, multiple non-RedCap UEs may continue to use the shared initial UL BWP 420 and shared initial DL BWP 430 as their initial BWPs after cell acquisition. For example, the maximum BWP size for multiple non-RedCap UEs may be greater than or equal to the size of the shared initial UL BWP 420 and shared initial DL BWP 430. In contrast, the maximum BWP size for multiple RedCap UEs may be less than the size of the shared initial UL BWP 420 and / or the size of the shared initial DL BWP 430. For example, multiple RedCap UEs may not be able to communicate over a portion of the shared initial UL BWP 420 and / or the size of the shared initial DL BWP 430. For example, a shared initial UL BWP 420 may include a PUCCH resource 422 configured at the edge of the carrier bandwidth 410, and a shared initial DL BWP 430 may carry a CD-SSB 432 near the center of the carrier bandwidth 410. The CD-SSB 432 may be transmitted according to a channel raster so that the shared initial DL BWP 430 can be positioned during cell discovery. Thus, the CD-SSB 432 defines a cell. In one embodiment, multiple RedCap UEs may receive a portion of the initial DL BWP 430 carrying the CD-SSB 432 (e.g., an initial control resource set (CORESET)), but may not be able to transmit it over the PUCCH resource 422 of the shared initial UL BWP 420.

[0060] In one embodiment, the CD-SSB 432 contains or identifies system information for separate initial DL BWP 450 for multiple RedCap UEs. The separate initial DL BWP 450 may carry a non-CD-SSB 452. The non-CD-SSB 452 may carry some or all of the cell information and the information for the separate initial DL BWP 450. The non-CD-SSB 452 may contain information for separate UL BWP 440 for multiple RedCap UEs. The separate UL BWP 440 may be located at the edge of the carrier bandwidth 410 and may contain a PUCCH resource 442 that overlaps with the PUCCH resource 422 of the shared initial UL BWP 420. The RedCap UE 104 may connect to the cell via the separate initial DL BWP 450 and the separate initial UL BWP 440. For example, RedCap UE 104 may receive a non-CD-SSB 452 to acquire system information and perform measurements. RedCap UE 104 can perform random access procedures on a separate initial UL BWP 440. For example, a separate initial UL BWP 440 may include a Physical Random Access Channel (PRACH) occasion for sending an initial random access message. A separate initial DL BWP 450 may include a common search space for receiving subsequent random access messages.

[0061] When RedCap UE 104 accesses a cell, the network can configure RedCap UE 104 with an active UL BWP 460 for multiple RedCap UEs and an active DL BWP 470 for multiple RedCap UEs. The active DL BWP 470 may be outside of the shared initial DL BWP 430 and / or separate initial DL BWP 450. In one embodiment, the active DL BWP 470 may consist of signaling to facilitate the operation of the RedCap UEs. For example, the active DL BWP 470 may carry periodic reference signals such as a tracking reference signal (TRS), a channel status information reference signal (CSI-RS), and / or a positioning reference signal (PRS). The active DL BWP 470 may include a common search space (CSS) for paging and wake-up signals (WUS). If a paging search space is not configured, the active DL BWP 470 may include dedicated RRC signaling for system information updates. The active DL BWP 470 may include a Layer 3 in-frequency measurement gap for measuring adjacent cells and / or reference signals on other BWPs (e.g., a shared initial DL BWP 430 and / or separate initial DL BWP 450).

[0062] Figure 5 shows another example of a configuration 500 of multiple BWPs for a RedCap UE on a carrier bandwidth 510. Similar to configuration 400, configuration 500 may include a shared initial UL BWP 520 and a shared initial DL BWP 530 that can be used by both a first type of UE (e.g., multiple non-RedCap UEs) and a second type of UE (e.g., multiple RedCap UEs). The shared initial UL BWP 520 may include a PUCCH resource 522 located at the edge of the shared initial UL BWP 520. The shared initial DL BWP 530 may include a CORESET0 that carries a CD-SSB 532.

[0063] The RedCap UE 104 can access cells via a shared initial DL BWP 530. The network can configure the RedCap UE 104 with an active UL BWP 540 for multiple RedCap UEs and an active DL BWP 550 for multiple RedCap UEs. The active DL BWP 470 may be located outside the shared initial DL BWP 530. In one embodiment, the active DL BWP 470 may consist of signaling to facilitate the operation of the RedCap UE. For example, the active DL BWP 470 may carry periodic reference signals such as TRS, CSI-RS, and / or PRS. The active DL BWP 470 may include CSS for paging and wake-up signals (WUS). The active DL BWP 470 may include dedicated RRC signaling for system information updates. The active DL BWP 470 may include a Layer 3 in-frequency measurement gap for measuring adjacent cells and / or reference signals on other BWPs (e.g., shared initial DL BWP 530).

[0064] In one embodiment, a RedCap UE configured with active DL BWPs 460, 540 under configuration 400 or configuration 500 can obtain various information from the active DL BWPs 460, 540, shared DL BWPs 430, 530, and / or a separate initial DL BWP 450. For simplicity, further explanation will refer to configuration 400, but may also be applicable to configuration 500. Examples of information that a RedCap UE may obtain include paging messages, updated system information, measurements such as Layer 3 measurements and neighboring cell measurements, as well as neighboring cell system information during RRC re-establishment or release with redirection.

[0065] In connected mode, UE 104 can receive updated system information. When a cell updates system information, it can send a paging message to notify connected UEs to retrieve the updated system information. For multiple non-RedCap UEs, the UEs can receive paging information on the initial DL BWP's CSS, retrieve the Management Information Block (MIB) from CD-SSB 432, and then place the remaining Minimum System Information (RMSI) from the MIB. In configurations 400 and 500, the RedCap UE's active BWP may not overlap with the initial DL BWP or the CD-SSB's CSS.

[0066] Figure 6 shows a technique for obtaining updated system information for a RedCap UE 104 configured with active DL BWPs 470, 550 for multiple RedCap UEs. The active DL BWPs 470, 550 may be configured with a paging search space 610. The paging search space 610 may be part of the CSS. The paging search space 610 may be configured together with or separately from the WUS search space. UE 104 may monitor the paging search space 610 for the paging PDCCH 612. When RedCap UE 104 operates in half-duplex frequency-domain duplex (HD-FDD) on an active downlink BWP, receiving the paging search space may take precedence over uplink transmissions if paging occasions overlap with semi-static or dynamically configured uplink transmissions. If the paging PDCCH 612 indicates that system information has been updated, the UE can switch to either the shared initial DL BWP 430, 530 or a separate initial DL BWP 450 to receive the system information update, or remain within the active DL BWP 470, 550 and decode the broadcast / multicast PDSCH.

[0067] For example, in block 620, the paging PDCCH 612 may indicate to switch BWPs to receive system information updates. In block 622, the paging PDCCH notifies the RedCap UE to switch to a different DL BWP to receive system information updates. The UE may receive instructions on whether the initial downlink BWP for obtaining the updated system information is a shared initial BWP or a separate initial downlink BWP. For example, the instructions could be one of the following: the presence of system information in a separate initial downlink BWP, radio network transient identifier (RNTI) scrambling in the cyclic redundancy check (CRC) of the paging PDCCH 612, a BWP identifier in the paging PDCCH 612, the DMRS configuration of the paging PDCCH 612, or the paging occasion configuration of the paging PDCCH 612. Based on the instructions, UE 104 can switch to the initial shared DL BWP 430, 530 in block 622, or to a separate initial DL BWP 450 in block 624.

[0068] As another example, in block 630, the paging PDCCH 612 may indicate that RedCap UEs should receive system information updates without switching DL BWPs. The paging PDCCH 612 may schedule system information updates on active DL BWPs 470, 550. For example, the paging PDCCH may indicate PDSCHs on active downlink BWPs 470, 550 for multiple RedCap UEs via one of the following: scrambling of the paging PDCCH's CRC (RNT), a BWP identifier within the paging PDCCH, the paging PDCCH's DMRS configuration, or the paging occasion configuration of the paging PDCCH. In block 632, the system information updates are broadcast or multicast to multiple RedCap UEs on PDSCHs scheduled by the paging PDCCH using a group RNTI, which may be a function of a cell ID, BWP ID, or group common parameter.

[0069] Figure 7 is a message diagram 700 showing an exemplary message between base station 102 and UE 104 for obtaining information about having multiple BWPs for a RedCap UE. Base station 102 may broadcast CD-SSB 710 for shared initial DL BWPs 430 and 530. In some implementations, base station 102 may also broadcast non-CD-SSB 720 for a separate DL BWP 450.

[0070] UE 104 may send a random access message 730. For example, the random access message 730 could be a first random access message, such as Msg1 in a four-step random access procedure or MsgA in a two-step random access procedure. If the cell consists of both a shared initial DL BWP 430 and a separate initial DL BWP 450, UE 104 may choose between a CD-SSB 710 and a non-CD-SSB 720 to send the first random access message. In some implementations, system information indicated by the CD-SSB 710 and / or non-CD-SSB 720 may explicitly indicate which SSB should be used. In some implementations, rules may identify SSB preferences or rankings. For example, UE 104 may initially send a first random access message based on CD-SSB 710, and if the time between the initial transmission and the retransmission is greater than a threshold, it may send a retransmission of the first random access message based on non-CD-SSB 720 (therefore, allowing the UE to measure non-CD-SSB 720).

[0071] After the random access procedure, base station 102 may transmit an active RedCap BWP configuration 740 for active DL BWP 470, 550 and active UL BWP 460, 540. For example, the active RedCap BWP configuration 740 may be an RRC configuration. In some implementations, the active RedCap BWP configuration 740 may include a configuration for the paging search space 610. The RedCap UE 104 can switch to active DL BWP 470, 550 and active UL BWP 460, 540 for communication in connected mode.

[0072] In some implementations, the base station 102 may transmit BWP-specific uplink parameters 745. For example, the transmitted BWP-specific uplink parameters 745 may include BWP-specific power control parameters, frequency hopping flags, coverage extension parameters, and / or waveform configurations for UL channels (e.g., PRACH / PUSCH / PUCCH / SRS) for one or more UL BWPs (e.g., shared UL BWP 420, separate UL BWP 440, or active UL BWP 460). The BWP-specific uplink parameters 745 may be communicated as BWP configuration or reconfiguration information (e.g., in an active RedCap BWP configuration 740). The BWP-specific uplink parameters 745 may be communicated as BWP switching commands (e.g., on DCI or MAC-CE). The BWP-specific uplink parameters 745 may be communicated as system information updated specifically for multiple RedCap UEs (e.g., on separate DL BWP 450 or active DL BWP 470, 550).

[0073] Base station 102 may transmit a paging PDCCH 612. If the paging search space 610 is configured on active DL BWPs 470, 550, UE 104 may receive the paging PDCCH 612 without switching BWPs. As described above with respect to Figure 6, RedCap UE 104 may switch to shared DL BWPs 430, 530 or a separate initial DL BWP 550 to receive updated system information 750. Alternatively, as indicated by the paging PDCCH 612, RedCap UE 104 may remain on active DL BWPs 470, 550 to receive the PDSCH carrying the updated system information.

[0074] If the active DL BWPs 470 and 550 are not configured with the paging search space 610, the RedCap UE 104 may periodically switch to a separate initial DL BWP 550 to receive the paging PDCCH 612 and / or the updated system information 750. In the first option, the RedCap UE 104 may receive the paging PDCCH 612 on the separate initial DL BWP 550. If the paging PDCCH 612 indicates updated system information, the RedCap UE 104 may switch to the shared DL BWP 430 to receive the updated system information 750. In the second option, the updated system information 750 may be broadcast on the separate initial DL BWP 550, and the RedCap UE 104 may periodically receive the updated system information 750 to determine whether an update has occurred (for example, without receiving the paging PDCCH 612). In the third option, the RedCap UE 104 can receive the paging PDCCH 612 on a separate initial DL BWP 550 and receive the updated system information 750 on the separate initial DL BWP 550 based on the paging PDCCH 612.

[0075] Base station 102 can transmit a reference signal (RS) instruction 760. The RS instruction 760 can identify a measurement resource on one of the following: an active downlink BWP, a separate initial downlink BWP, or a shared initial downlink BWP. For example, the measurement resource may be for Layer 3 measurements such as reference signal received power (RSRP), reference signal received quality (RSRQ), signal-to-interference noise ratio (SINR), signal-to-noise ratio (SNR), or a combination thereof. The measurement resource may be one or more of SSB, CSI-RS, or PRS. Base station 102 can transmit a reference signal 770 indicated on the indicated measurement resource.

[0076] RS instruction 760 can be communicated through one or more combinations of system information, RRC signaling, MAC-CE, and DCI. If the measurement resource is on a separate initial downlink BWP or a shared initial downlink BWP, RS instruction 760 can configure a measurement gap on the active DL BWP 470, 550 to switch the BWP so that the RedCap UE 104 can perform the measurement. In some implementations, the measurement includes an adjacent cell measurement based on the adjacent cell's system information. The adjacent cell's system information may be provided in the active RedCap BWP configuration 740. Thus, the RedCap UE may be able to obtain the adjacent cell's system information even if complete system information is not transmitted in the adjacent cell's separate initial DL BWP 450.

[0077] In some implementations, base station 102 may transmit an adjacent cell instruction 780. The adjacent cell instruction 780 may indicate whether the adjacent cell is configured with separate DL BWPs 450 for multiple RedCap UEs that carry system information. The adjacent cell instruction 780 may indicate whether the separate DL BWPs 450 should be used for RRC re-establishment or RRC release with redirection. For example, the default configuration may use a shared initial downlink BWP 430 as a fallback BWP during RRC re-establishment or RRC release with redirection. If RedCap UE 104 receives an adjacent cell instruction 780, RedCap UE 104 may use the adjacent cell's separate DL BWP 450 as a fallback BWP.

[0078] In some implementations, the active RedCap BWP configuration 740 includes different measurement gaps for measuring CD-SSB 710 for a shared initial downlink BWP and non-CD-SSB 720 for a separate initial downlink BWP. The base station 102 may transmit an SSB Tx power instruction 790 for CD-SSB 710 and non-CD-SSB 720. The SSB Tx power instruction 790 may include an instruction for the absolute transmit power of CD-SSB 710 for the shared initial downlink BWPs 430 and 530, and the differential transmit power of non-CD-SSB 720 for the separate initial downlink BWP 450.

[0079] Figure 8 is a conceptual data flow diagram 800 showing data flow between different means / components in an exemplary base station 102, which may be an example of a base station 802 including a RedCap BWP control component 120. The RedCap BWP control component 120 may be implemented by memory 376 in Figure 3, and a TX processor 316, an RX processor 370, and / or a controller / processor 375. For example, memory 376 can store executable instructions that define the RedCap BWP control component 120, and the TX processor 316, an RX processor 370, and / or a controller / processor 375 can execute the instructions.

[0080] The base station 102 may include a receiver component 870, which may include, for example, a radio frequency (RF) receiver for receiving signals as described herein. The base station 102 may also include a transmitter component 872, which may include, for example, an RF transmitter for transmitting signals as described herein. In one embodiment, the receiver component 870 and the transmitter component 872 may be co-located in a transceiver, such as the one shown by TX / RX 318 in Figure 3.

[0081] As explained with respect to Figure 1, the RedCap BWP control component 120 may include a shared initial BWP component 810, a separate initial BWP component 820, an active BWP component 830, a paging component 840, and a system information update component 850. The RedCap BWP control component 120 may optionally include an uplink configuration component 860.

[0082] The receiver component 870 may receive UL signals, including UL communications, from UE 104. In some implementations, the receiver component 870 may optionally receive random access messages from UE 104 attempting to connect to base station 802. The receiver component 870 may provide identification information of UE 104 to the active BWP component 830.

[0083] The shared initial BWP component 810 may transmit a CD-SSB 710 via the transmitter component 872 that defines shared initial downlink BWPs 430, 530 for multiple RedCap UEs and multiple non-RedCap UEs. For example, the CD-SSB 710 may contain or identify system information. The shared initial BWP component 810 may update the system information and provide update instructions to the paging component 840.

[0084] A separate initial BWP component 820 may transmit a non-CD-SSB 720 to separate initial downlink BWPs for multiple RedCap UEs via the transmitter component 872. For example, the non-CD-SSB 710 may contain or identify unique system information for multiple RedCap UEs. In some implementations, the system information transmitted by the separate initial BWP component 820 on the separate initial downlink BWP 550 may include some or all of the system information transmitted by the shared initial BWP component 810. The separate initial BWP component 820 may update the system information and provide update instructions to the paging component 840.

[0085] The active BWP component 830 may receive random access messages and / or identification of the RedCap UE 104 from the receiver component 870. The active BWP component 830 may configure active DL BWP 470, 550 and active UL BWP 460, 540 for the RedCap UE 104. For example, the active BWP component 830 may transmit an RRC configuration message via the transmitter component 872, including the configuration of the active DL BWP 470, 550 and active UL BWP 460, 540.

[0086] The paging component 840 may receive instructions from the shared initial BWP component 810 and / or a separate initial BWP component 820 indicating that system information has been updated. The paging component 840 may transmit a paging PDCCH 612 indicating an update to the system information via the transmitter component 872. If the updated system information should be transmitted as a PDSCH on the active DL BWP 470, 550, the paging component 840 may schedule the PDSCH and include scheduling information within the paging PDCCH 612. The paging component 840 may provide the system information update component 850 with resources for the PDSCH.

[0087] The system information update component 850 may transmit updated system information on a shared initial downlink BWP, a separate initial downlink BWP, or an active downlink BWP, as indicated by the paging PDCCH 612. For example, the system information update component 850 may receive resources for a PDSCH from the paging component 840 and transmit updated system information 750 as a PDSCH on active DL BWPs 470 and 550.

[0088] The uplink configuration component 860 may transmit BWP-specific uplink parameters 745 to the initial uplink BWP 460 for multiple RedCap UEs, or active uplink BWPs 440, 540 for multiple RedCap UEs.

[0089] Figure 9 is a conceptual dataflow diagram 900 illustrating the data flow between different means / components in an exemplary UE 904, which may be an example of UE 104 and may include a RedCap BWP component 140. The RedCap BWP component 140 may be implemented by memory 360 and a TX processor 368, an RX processor 356, and / or a controller / processor 359. For example, memory 360 can store executable instructions that define the RedCap BWP component 140, and the TX processor 368, an RX processor 356, and / or a controller / processor 359 can execute the instructions.

[0090] UE 104 may include a receiver component 970, which may include, for example, an RF receiver for receiving the signals described herein. UE 104 may also include a transmitter component 972, which may include, for example, an RF transmitter for transmitting the signals described herein. In one embodiment, the receiver component 970 and the transmitter component 972 may be co-located within a transceiver such as the TX / RX 352 in Figure 3.

[0091] As explained with respect to Figure 1, the RedCap BWP component 140 may include a shared initial BWP component 142, a separate initial BWP component 144, an active BWP component 146, and a BWP switching component 148. In some implementations, the RedCap BWP component 140 may optionally include a random access component 910 and / or an uplink configuration component 920.

[0092] Receiver component 970 may receive DL signals described herein, such as CD-SSB 710, non-CD-SSB 720, active RedCap BWP configuration 740, BWP-specific uplink parameters 745, paging PDCCH 612, updated system information 750, RS indicator 760, RS 770, adjacent cell indicator 780, and SSB Tx power indicator 790. Receiver component 970 may provide CD-SSB 710 to a shared initial BWP component 142. Receiver component 970 may provide non-CD-SSB 720 to a separate initial BWP component 144. Receiver component 970 may provide active RedCap BWP configuration 740, updated system information 750, RS indicator 760, RS 770, adjacent cell indicator 780, and SSB Tx power indicator 790 to an active BWP component 146. The receiver component 970 may provide the BWP-specific uplink parameter 745 to the uplink configuration component 920. The receiver component 970 may provide the paging PDCCH 612 to the BWP switching component 148.

[0093] The shared initial BWP component 142 may receive CD-SSB 710 via the receiver component 970. The shared initial BWP component 142 may obtain system information based on CD-SSB 710. The system information may include the location of non-CD-SSB 720. The shared initial BWP component 142 may control the receiver component 970 to receive non-CD-SSB 720.

[0094] A separate initial BWP component 144 may receive non-CD-SSB 720 via receiver component 970. The separate initial BWP component 144 may receive system information for multiple RedCap UEs based on non-CD-SSB 720. For example, the separate initial BWP component 144 may determine RACH occasions on a separate initial uplink BWP 440. The separate initial BWP component 144 may provide RACH occasions to the random access component 910.

[0095] The random access component 910 may receive RACH occasions from a separate initial BWP component 144. In some implementations, the random access component 910 may receive CD-SSB 710 and non-CD-SSB 720 or their measurements. The random access component 910 may access cells via a separate initial downlink BWP 450 (for example, based on identified RACH occasions). For example, the random access component 910 may send random access messages on RACH occasions. The random access component 910 may select either CD-SSB 710 or non-CD-SSB 720 to send random access messages based on system information received on a shared initial BWP or a separate initial BWP.

[0096] The active BWP component 146 may receive the active RedCap BWP configuration 740 via the receiver component 970. The active RedCap BWP configuration 740 may be in response to a random access procedure (for example, a UE connecting to a cell). The active BWP component 146 may forward the signaling received on the active downlink BWP 470 to the BWP switching component 148.

[0097] The BWP switching component 148 can switch the UE 904 between BWPs, including a shared initial downlink BWP 430, a separate initial downlink BWP 450, and an active downlink BWP 470. For example, the BWP switching component 148 may select a BWP to receive various information. For example, depending on the configuration of the paging search space 610, the BWP switching component 148 may control the UE 904 to receive a paging PDCCH on the separate initial downlink BWP 450 or the active downlink BWP 470. If a paging PDCCH 612 is received, the BWP switching component 148 may control the UE 904 to receive updated system information 750 on the BWP indicated by the paging PDCCH.

[0098] Figure 10 is a flowchart of an exemplary method 1000 for a RedCap UE configured with multiple BWPs to acquire information. Method 1000 can be performed by a UE (which may include memory 360 and may be the entire UE 104, or components of UE 104 such as the RedCap BWP component 140, TX processor 368, RX processor 356, or controller / processor 359). Method 1000 can be performed by a RedCap BWP component 140 communicating with a RedCap BWP control component 120 of a base station 102. Optional blocks are shown with dashed lines.

[0099] In block 1010, method 1000 may include receiving a CD-SSB that defines a shared initial downlink BWP for multiple RedCap UEs and multiple non-RedCap UEs. In some implementations, for example, a UE 104, an RX processor 356, or a controller / processor 359 may run a RedCap BWP component 140 or a shared initial BWP component 142 to receive a CD-SSB 720 that defines a shared initial downlink BWP 430 for multiple RedCap UEs and multiple non-RedCap UEs. Thus, a UE 104, an RX processor 356, or a controller / processor 359 running a RedCap BWP component 140 or a shared initial BWP component 142 may provide means for receiving a CD-SSB that defines a shared initial downlink BWP for multiple RedCap UEs and multiple non-RedCap UEs.

[0100] In block 1020, method 1000 may include switching to separate initial downlink BWPs for multiple RedCap UEs. In some implementations, for example, UE 104, RX processor 356, or controller / processor 359 may run a RedCap BWP component 140 or a separate initial BWP component 144 to switch to a separate initial downlink BWP 450 for multiple RedCap UEs. Thus, UE 104, RX processor 356, or controller / processor 359 running a RedCap BWP component 140 or a separate initial BWP component 144 may provide a means to switch to a separate initial downlink BWP for multiple RedCap UEs.

[0101] In block 1030, method 1000 may include accessing a cell via a separate initial downlink BWP. In some implementations, for example, UE 104, TX processor 368, or controller / processor 359 may run a RedCap BWP component 140 or a random access component 910 to access a cell via a separate initial downlink BWP 450. Thus, UE 104, TX processor 368, or controller / processor 359 running a RedCap BWP component 140 or a random access component 910 may provide a means to access a cell via a separate initial downlink BWP.

[0102] In block 1040, method 1000 may include receiving configurations for active downlink BWPs for multiple RedCap UEs. In some implementations, for example, a UE 104, an RX processor 356, or a controller / processor 359 may run a RedCap BWP component 140 or an active BWP component 146 to receive configurations for active downlink BWPs 470 for multiple RedCap UEs. Thus, a UE 104, an RX processor 356, or a controller / processor 359 running a RedCap BWP component 140 or an active BWP component 146 may provide means for receiving configurations for active downlink BWPs for multiple RedCap UEs.

[0103] In block 1050, method 1000 may include determining whether to switch from an active downlink BWP to a shared initial BWP or a separate initial downlink BWP in order to obtain information. In some implementations, for example, UE 104, RX processor 356, or controller / processor 359 may run a RedCap BWP component 140 or a BWP switching component 148 to determine whether to switch from an active downlink BWP to a shared initial BWP or a separate initial downlink BWP in order to obtain information. Thus, UE 104, RX processor 356, TX processor 368, or controller / processor 359 running a RedCap BWP component 140 or a BWP switching component 148 may provide means for determining whether to switch from an active downlink BWP to a shared initial BWP or a separate initial downlink BWP in order to obtain information.

[0104] Figure 11 is a flowchart of an exemplary method 1100 for a RedCap UE configured with multiple BWPs to initiate random access. Method 1100 can be performed by a UE (which may include memory 360 and may be the entire UE 104, or components of UE 104 such as the RedCap BWP component 140, TX processor 368, RX processor 356, or controller / processor 359). Method 1100 can be performed by a RedCap BWP component 140 communicating with a RedCap BWP control component 120 of a base station 102. Optional blocks are shown with dashed lines.

[0105] In block 1110, method 1100 may include receiving a CD-SSB that defines a shared initial downlink BWP for multiple RedCap UEs and multiple non-RedCap UEs. In some implementations, for example, UE 104, RX processor 356, or controller / processor 359 may run a RedCap BWP component 140 or a shared initial BWP component 142 to receive a CD-SSB 720 that defines a shared initial downlink BWP 430 for multiple RedCap UEs and multiple non-RedCap UEs. Thus, UE 104, RX processor 356, or controller / processor 359 running a RedCap BWP component 140 or a shared initial BWP component 142 may provide means for receiving a CD-SSB that defines a shared initial downlink BWP for multiple RedCap UEs and multiple non-RedCap UEs.

[0106] In block 1120, method 1100 may include receiving non-CD-SSBs for separate initial downlink BWPs for multiple RedCap UEs. In some implementations, for example, UE 104, RX processor 356, or controller / processor 359 may run a RedCap BWP component 140 or a separate initial BWP component 144 to receive non-CD-SSBs 720 for separate initial downlink BWPs 450 for multiple RedCap UEs. Thus, UE 104, RX processor 356, or controller / processor 359 running a RedCap BWP component 140 or a separate initial BWP component 144 may provide means for receiving non-CD-SSBs for separate initial downlink BWPs for multiple RedCap UEs.

[0107] In block 1130, method 1100 may include selecting either CD-SSB or non-CD-SSB to send random access messages based on system information received on a shared initial BWP or a separate initial BWP. In some implementations, for example, UE 104, TX processor 368, or controller / processor 359 may run a RedCap BWP component 140 or a random access component 910 to select either CD-SSB or a non-CD-SSB to send random access messages based on system information received on a shared initial BWP or a separate initial BWP. Thus, UE 104, TX processor 368, or controller / processor 359 running a RedCap BWP component 140 or a random access component 910 may provide means for selecting either CD-SSB or a non-CD-SSB to send random access messages based on system information received on a shared initial BWP or a separate initial BWP.

[0108] Figure 12 is a flowchart of exemplary method 1200 for a RedCap UE configured with multiple BWPs to configure BWP-specific uplink parameters. Method 1200 can be performed by a UE (which may include memory 360 and may be the entire UE 104, or components of UE 104 such as the RedCap BWP component 140, TX processor 368, RX processor 356, or controller / processor 359). Method 1000 can be performed by a RedCap BWP component 140 communicating with the RedCap BWP control component 120 of base station 102. Optional blocks are shown with dashed lines.

[0109] In block 1210, method 1200 may include receiving a CD-SSB that defines a shared initial downlink BWP for multiple RedCap UEs and multiple non-RedCap UEs. In some implementations, for example, UE 104, RX processor 356, or controller / processor 359 may run a RedCap BWP component 140 or a shared initial BWP component 142 to receive a CD-SSB 720 that defines a shared initial downlink BWP 430 for multiple RedCap UEs and multiple non-RedCap UEs. Thus, UE 104, RX processor 356, or controller / processor 359 running a RedCap BWP component 140 or a shared initial BWP component 142 may provide means for receiving a CD-SSB that defines a shared initial downlink BWP for multiple RedCap UEs and multiple non-RedCap UEs.

[0110] In block 1220, method 1200 may include switching to separate initial downlink BWPs for multiple RedCap UEs and initial uplink BWPs for multiple RedCap UEs. In some implementations, for example, UE 104, RX processor 356, or controller / processor 359 may run a RedCap BWP component 140 or a separate initial BWP component 144 to switch to a separate initial downlink BWP 450 and an initial uplink BWP 440 for multiple RedCap UEs. Thus, UE 104, RX processor 356, or controller / processor 359 running a RedCap BWP component 140 or a separate initial BWP component 144 may provide means to switch to separate initial downlink BWPs and initial uplink BWPs for multiple RedCap UEs.

[0111] In block 1230, method 1200 may include receiving BWP-specific uplink parameters for initial uplink BWPs or active uplink BWPs for multiple RedCap UEs configured at the edge of the carrier bandwidth. In some implementations, for example, UE 104, RX processor 356, or controller / processor 359 may run a RedCap BWP component 140 or uplink configuration component 920 to receive BWP-specific uplink parameters 745 for initial uplink BWPs 440 or active uplink BWPs 460 for multiple RedCap UEs configured at the edge of the carrier bandwidth 410. Thus, UE 104, RX processor 356, TX processor 368, or controller / processor 359 running a RedCap BWP component 140 or uplink configuration component 920 may provide means for receiving BWP-specific uplink parameters for initial uplink BWPs or active uplink BWPs for multiple RedCap UEs configured at the edge of the carrier bandwidth.

[0112] Figure 13 is a flowchart of an exemplary method 1300 for a base station to control multiple BWPs for a RedCap UE. Method 1300 can be performed by a base station (for example, base station 102, which may include memory 376 and may be the entire base station 102, or components of base station 102 such as the RedCap BWP control component 120, TX processor 316, RX processor 370, or controller / processor 375). Method 1300 can be performed by a RedCap BWP control component 120 communicating with a RedCap BWP component 140 of a UE 104.

[0113] In block 1310, method 1300 may include transmitting a CD-SSB that defines a shared initial BWP for multiple RedCap UEs and multiple non-RedCap UEs. In some implementations, for example, a base station 102, a TX processor 316, or a controller / processor 375 may run a RedCap BWP control component 120 or a shared initial BWP component 810 to transmit a CD-SSB that defines a shared initial BWP for multiple RedCap UEs and multiple non-RedCap UEs. Thus, a base station 102, a TX processor 316, or a controller / processor 375 running a RedCap BWP control component 120 or a shared initial BWP component 810 may provide means for transmitting a CD-SSB that defines a shared initial BWP for multiple RedCap UEs and multiple non-RedCap UEs.

[0114] In block 1320, method 1300 may include transmitting non-CD-SSB to separate initial downlink BWPs for multiple RedCap UEs. In some implementations, for example, base station 102, TX processor 316, or controller / processor 375 may run a RedCap BWP control component 120 or a separate initial BWP component 820 to transmit non-CD-SSB 720 for separate initial downlink BWPs 450 for multiple RedCap UEs. Thus, base station 102, TX processor 316, or controller / processor 375 running a RedCap BWP control component 120 or a separate initial BWP component 820 may provide means for transmitting non-CD-SSB to separate initial downlink BWPs for multiple RedCap UEs.

[0115] In block 1330, method 1300 may include configuring an active downlink BWP for a RedCap UE that includes a paging search space. In some implementations, for example, a base station 102, an RX processor 370, or a controller / processor 375 may run a RedCap BWP control component 120 or an active BWP component 830 that configures an active downlink BWP 570 for a RedCap UE that includes a paging search space 610. Thus, a base station 102, an RX processor 370, or a controller / processor 375 running a RedCap BWP control component 120 or an active BWP component 830 may provide means for configuring an active downlink BWP for a RedCap UE that includes a paging search space.

[0116] In block 1340, method 1300 may include transmitting a paging PDCCH indicating that system information has been updated. In some implementations, for example, a base station 102, TX processor 316, or controller / processor 375 may run a RedCap BWP control component 120 or a paging component 840 to transmit a paging PDCCH 612 indicating that system information has been updated. Thus, a base station 102, TX processor 316, or controller / processor 375 running a RedCap BWP control component 120 or a paging component 840 may provide means for transmitting a paging PDCCH indicating that system information has been updated.

[0117] In block 1350, method 1300 may include transmitting updated system information on a shared initial downlink BWP, a separate initial downlink BWP, or an active downlink BWP, as shown by the paging PDCCH. In some implementations, for example, a base station 102, a TX processor 316, or a controller / processor 375 may run a RedCap BWP control component 120 or a system information update component 850 to transmit updated system information 750 on a shared initial downlink BWP 430, a separate initial downlink BWP 450, or an active downlink BWP 470, as shown by the paging PDCCH. Thus, a base station 102, a TX processor 316, or a controller / processor 375 running a RedCap BWP control component 120 or a system information update component 850 may provide means for transmitting updated system information on a shared initial downlink BWP, a separate initial downlink BWP, or an active downlink BWP, as shown by the paging PDCCH.

[0118] Figure 14 is a flowchart of an exemplary method 1400 for a base station to control multiple BWPs for a RedCap UE. Method 1300 can be performed by a base station (for example, base station 102, which may include memory 376 and may be the entire base station 102, or components of base station 102 such as the RedCap BWP control component 120, TX processor 316, RX processor 370, or controller / processor 375). Method 1000 can be performed by a RedCap BWP control component 120 communicating with a RedCap BWP component 140 of a UE 104.

[0119] In block 1410, method 1400 may include transmitting a CD-SSB that defines a shared initial BWP for multiple RedCap UEs and multiple non-RedCap UEs. In some implementations, for example, a base station 102, a TX processor 316, or a controller / processor 375 may run a RedCap BWP control component 120 or a shared initial BWP component 810 to transmit a CD-SSB that defines a shared initial BWP for multiple RedCap UEs and multiple non-RedCap UEs. Thus, a base station 102, a TX processor 316, or a controller / processor 375 running a RedCap BWP control component 120 or a shared initial BWP component 810 may provide means for transmitting a CD-SSB that defines a shared initial BWP for multiple RedCap UEs and multiple non-RedCap UEs.

[0120] In block 1420, method 1400 may include transmitting non-CD-SSB to separate initial downlink BWPs for multiple RedCap UEs and initial uplink BWPs for multiple RedCap UEs. In some implementations, for example, a base station 102, TX processor 316, or controller / processor 375 may run a RedCap BWP control component 120 or a separate initial BWP component 820 to transmit non-CD-SSB 720 to separate initial downlink BWPs 450 for multiple RedCap UEs and initial uplink BWPs 440 for multiple RedCap UEs. Thus, a base station 102, TX processor 316, or controller / processor 375 running a RedCap BWP control component 120 or a separate initial BWP component 820 may provide means for transmitting non-CD-SSB to separate initial downlink BWPs for multiple RedCap UEs and initial uplink BWPs for multiple RedCap UEs.

[0121] In block 1430, method 1400 may include transmitting BWP-specific uplink parameters for initial uplink BWPs or active uplink BWPs for multiple RedCap UEs configured at the edge of the carrier bandwidth. In some implementations, for example, a base station 102, TX processor 316, or controller / processor 375 may run a RedCap BWP control component 120 or an uplink configuration component 860 to transmit BWP-specific uplink parameters for initial uplink BWPs 440 or active uplink BWPs 460 for multiple RedCap UEs configured at the edge of the carrier bandwidth 410. Thus, a base station 102, TX processor 316, or controller / processor 375 running a RedCap BWP control component 120 or an uplink configuration component 860 may provide means for transmitting BWP-specific uplink parameters for initial uplink BWPs or active uplink BWPs for multiple RedCap UEs configured at the edge of the carrier bandwidth.

[0122] The following provides an overview of the aspects of this disclosure. Embodiment 1: A method comprising: receiving a cell-defined synchronization signal block (CD-SSB) that defines a shared initial downlink bandwidth portion (BWP) for a plurality of RedCap UEs and a plurality of non-RedCap UEs in a RedCap User Equipment (RedCap UE); switching to a separate initial downlink BWP for the plurality of RedCap UEs; accessing a cell via the separate initial downlink BWP; receiving the configuration of an active downlink BWP for the plurality of RedCap UEs; and determining whether to switch from the active downlink BWP to a shared initial BWP or a separate initial downlink BWP to obtain information.

[0123] Embodiment 2: The method according to Embodiment 1, wherein the configuration of an active downlink BWP for multiple RedCap UEs includes a paging search space, and determining whether to switch to a shared initial BWP or a separate initial downlink BWP to obtain information includes receiving a paging physical downlink control channel (PDCCH) indicating that system information has been updated.

[0124] Embodiment 3: The method according to Embodiment 2, wherein determining whether to switch to a shared initial BWP or a separate initial downlink BWP to obtain information includes switching from an active downlink BWP to a shared initial BWP or a separate initial downlink BWP to obtain updated system information.

[0125] Embodiment 4: The method according to Embodiment 3, further comprising receiving an instruction as to whether the initial downlink BWP for obtaining updated system information is a shared initial BWP or a separate initial downlink BWP.

[0126] Embodiment 5: The method according to Embodiment 4, wherein the instruction is one of the following: the presence of system information in a separate initial downlink BWP, radio network transient identifier (RNTI) scrambling for cyclic redundancy check (CRC) of a paging PDCCH, a BWP identifier in a paging PDCCH, a DMRS configuration of a paging PDCCH, or a paging occasion configuration of a paging PDCCH.

[0127] Embodiment 6: The method according to Embodiment 2, wherein determining whether to switch to a shared initial BWP or a separate initial downlink BWP to acquire information includes decoding a broadcast or multicast physical downlink shared channel (PDSCH) carrying updated system information scheduled by a paging PDCCH on an active downlink BWP for multiple RedCap UEs.

[0128] Embodiment 7: The method of Embodiment 6, wherein the paging PDCCH indicates a PDSCH on an active downlink BWP for multiple RedCap UEs via one of the following: cyclic redundancy check (CRC) radio network temporary identifier (RNTI) scrambling of the paging PDCCH, BWP identifier in the paging PDCCH, DMRS configuration of the paging PDCCH, or paging occasion configuration of the paging PDCCH.

[0129] Embodiment 8: The method according to Embodiment 6 or 7, wherein the broadcast or multicast PDSCH is scrambled by a Group Radio Network Temporary Identifier (RNTI), which is a function of a Cell ID, BWP ID, or Group Common Parameter.

[0130] Embodiment 9: The method according to any one of Embodiments 2 to 8, wherein the paging search space is configured together with or separately from the wake-up signal search space.

[0131] Embodiment 10: The method according to any one of Embodiments 2 to 8, wherein the RedCap UE operates in half-duplex frequency-domain duplex (HD-FDD) on an active downlink BWP, and when paging occasions overlap with semi-static or dynamically configured uplink transmissions, receiving the paging search space takes precedence over uplink transmissions.

[0132] Embodiment 11: The method according to Embodiment 1, wherein the paging search space is not comprised of active downlink BWPs for multiple RedCap UEs, and determining whether to switch to a shared initial BWP or a separate initial downlink BWP to obtain information includes switching to a separate initial downlink BWP to receive a paging PDCCH.

[0133] Embodiment 12: The method according to Embodiment 11, further comprising switching to a shared initial BWP in response to the paging PDCCH indicating updated system information.

[0134] Embodiment 13: The method according to Embodiment 11, further comprising receiving updated system information broadcast on a separate initial downlink BWP.

[0135] Embodiment 14: The method according to Embodiment 11, further comprising receiving updated system information scheduled by a paging PDCCH on a separate initial downlink BWP.

[0136] Embodiment 15: The method according to any one of embodiments 1 to 14, wherein determining whether to switch to a shared initial BWP or a separate initial downlink BWP to acquire information includes determining whether to switch to perform a measurement on one of the active downlink BWP, a separate initial downlink BWP, or a shared initial downlink BWP based on instructions from a measurement resource.

[0137] Embodiment 16: The method according to Embodiment 15, wherein the measurement resource is one or more of the following: a synchronization signal block (SSB), a channel status information reference signal (CSI-RS), or a positioning reference signal (PRS).

[0138] Embodiment 17: The method according to Embodiment 15 or 16, wherein the measurement is a Layer 3 measurement including reference signal received power (RSRP), reference signal received quality (RSRQ), signal-to-interference noise ratio (SINR), signal-to-noise ratio (SNR), or a combination thereof.

[0139] Embodiment 18: The method according to any one of embodiments 15 to 17, wherein the measurement includes an adjacent cell measurement based on system information of adjacent cells received in an active downlink BWP configuration for multiple RedCap UEs.

[0140] Embodiment 19: The method according to any one of Embodiments 1 to 18, wherein the configuration of an active downlink BWP for multiple RedCap UEs includes different measurement gaps for measuring the CD-SSB of a shared initial downlink BWP and the non-CD-SSB of separate initial downlink BWPs.

[0141] Embodiment 20: The method according to Embodiment 19, further comprising receiving instructions for the absolute transmit power of CD-SSB for a shared initial downlink BWP and the differential transmit power of non-CD-SSB for a separate initial downlink BWP.

[0142] Embodiment 21: The method of any one of Embodiments 1 to 20, wherein determining whether to switch to a shared initial BWP or a separate initial downlink BWP to obtain information includes determining a fallback BWP for RRC re-establishment or RRC release with redirection.

[0143] Embodiment 22: The method according to Embodiment 21, wherein the fallback BWP is a shared initial downlink BWP.

[0144] Embodiment 23: The method according to Embodiment 21, wherein determining the fallback BWP includes receiving instructions that all neighboring cells transmit system information on separate initial BWPs for multiple RedCap UEs, and the fallback BWP is a separate initial downlink BWP.

[0145] Embodiment 24: A method comprising, in a RedCap User Equipment (RedCap UE), receiving a cell-defined synchronization signal block (CD-SSB) that defines a shared initial downlink bandwidth portion (BWP) for a plurality of RedCap UEs and a plurality of non-RedCap UEs; receiving a non-CD-SSB for separate initial downlink BWPs for the plurality of RedCap UEs; and selecting one of the CD-SSB or the non-CD-SSB to transmit a random access message based on system information received on the shared initial BWP or the separate initial BWP.

[0146] Embodiment 25: The method of Embodiment 24, wherein the selection is based on system information received on a shared initial BWP or a separate initial BWP.

[0147] Embodiment 26: The method of Embodiment 25, wherein the selection includes selecting CD-SSB for initial transmission of random access messages.

[0148] Embodiment 27: The method of Embodiment 26, further comprising selecting CD-SSB for subsequent transmission of random access messages if the time for retransmission is less than a threshold, or selecting non-CD-SSB for subsequent transmission of random access messages if the time for retransmission is greater than or equal to a threshold.

[0149] Embodiment 28: A method comprising, in a RedCap User Equipment (RedCap UE), receiving a cell-defined synchronization signal block (CD-SSB) that defines a shared initial downlink bandwidth portion (BWP) for a plurality of RedCap UEs and a plurality of non-RedCap UEs; switching to separate initial downlink BWPs and initial uplink BWPs for the plurality of RedCap UEs; and receiving BWP-specific uplink parameters for the initial uplink BWPs or active uplink BWPs for the plurality of RedCap UEs, wherein the initial uplink BWPs and active uplink BWPs for the plurality of RedCap UEs are configured at the edge of the carrier bandwidth.

[0150] Embodiment 29: The method according to Embodiment 28, wherein the BWP-specific uplink parameters include one or more of the following: power control parameters, frequency hopping flags, coverage extension parameters, or waveform configurations for the uplink channel.

[0151] Embodiment 30: The method according to Embodiment 28 or 29, wherein receiving BWP-specific uplink parameters includes receiving the configuration of active uplink BWPs for multiple RedCap UEs.

[0152] Embodiment 31: The method according to Embodiment 28 or 29, wherein receiving BWP-specific uplink parameters includes receiving a BWP switching command.

[0153] Embodiment 32: The method according to Embodiment 28 or 29, wherein receiving BWP-specific uplink parameters includes receiving system information updates specific to multiple RedCap UEs.

[0154] Embodiment 33: A method for supporting a RedCap User Equipment (RedCap UE), comprising: transmitting a cell-defined synchronization signal block (CD-SSB) defining a shared initial downlink bandwidth portion (BWP) for a plurality of RedCap UEs and a plurality of non-RedCap UEs; transmitting a non-CD-SSB for separate initial downlink BWPs for the plurality of RedCap UEs; configuring an active downlink BWP for a RedCap UE that includes a paging search space; transmitting a paging physical downlink control channel (PDCCH) indicating that system information has been updated; and transmitting the updated system information on a shared initial downlink BWP, a separate initial downlink BWP, or an active downlink BWP, as indicated by the paging PDCCH.

[0155] Embodiment 34: The method according to Embodiment 33, further comprising sending an instruction as to whether the initial downlink BWP for obtaining updated system information is a shared initial BWP or a separate initial downlink BWP.

[0156] Embodiment 35: The method of Embodiment 34, wherein the instruction is one of the following: the presence of system information in a separate initial downlink BWP, radio network transient identifier (RNTI) scrambling for cyclic redundancy check (CRC) of a paging PDCCH, a BWP identifier in a paging PDCCH, a DMRS configuration of a paging PDCCH, or a paging occasion configuration of a paging PDCCH.

[0157] Embodiment 36: The method according to Embodiment 33, wherein the paging PDCCH schedules a broadcast or multicast physical downlink shared channel (PDSCH) that carries updated system information over active downlink BWPs for multiple RedCap UEs.

[0158] Embodiment 37: The method of Embodiment 36, wherein the paging PDCCH indicates a PDSCH on an active downlink BWP for multiple RedCap UEs via one of the following: cyclic redundancy check (CRC) radio network temporary identifier (RNTI) scrambling of the paging PDCCH, BWP identifier in the paging PDCCH, DMRS configuration of the paging PDCCH, or paging occasion configuration of the paging PDCCH.

[0159] Embodiment 38: The method according to Embodiment 36 or 37, wherein the broadcast or multicast PDSCH is scrambled by a Group Radio Network Temporary Identifier (RNTI), which is a function of a Cell ID, BWP ID, or Group Common Parameter.

[0160] Embodiment 39: The method according to any one of embodiments 33 to 38, wherein the paging search space is configured together with or separately from the wake-up signal search space.

[0161] Embodiment 40: The method of Embodiment 33, wherein the paging search space is not configured on an active downlink BWP for multiple RedCap UEs, and transmitting updated system information includes transmitting a paging PDCCH on a separate initial downlink BWP.

[0162] Embodiment 41: The method according to any one of embodiments 33 to 40, further comprising transmitting instructions for measurement resources on one of an active downlink BWP, a separate initial downlink BWP, or a shared initial downlink BWP.

[0163] Embodiment 42: The method according to Embodiment 41, wherein the measurement resource is one or more of the following: a synchronization signal block (SSB), a channel status information reference signal (CSI-RS), or a positioning reference signal (PRS).

[0164] Embodiment 43: The method according to Embodiment 41 or 42, wherein the measurement is a Layer 3 measurement including reference signal received power (RSRP), reference signal received quality (RSRQ), signal-to-interference noise ratio (SINR), signal-to-noise ratio (SNR), or a combination thereof.

[0165] Embodiment 44: The method according to any one of Embodiments 41 to 43, wherein the configuration of the active downlink BWP for RedCap UE includes system information of the adjacent cell to be measured.

[0166] Embodiment 45: The method according to any one of embodiments 33 to 44, wherein the configuration of an active downlink BWP for multiple RedCap UEs includes different measurement gaps for measuring the CD-SSB of a shared initial downlink BWP and the non-CD-SSB of separate initial downlink BWPs.

[0167] Embodiment 46: The method of Embodiment 45, further comprising transmitting instructions for the absolute transmit power of CD-SSB for a shared initial downlink BWP and the differential transmit power of non-CD-SSB for a separate initial downlink BWP.

[0168] Embodiment 47: The method of any one of embodiments 33 to 46, further comprising sending an instruction that all neighboring cells transmit system information on a separate initial BWP for multiple RedCap UEs, which is available as a fallback BWP for RRC re-establishment or RRC release with redirection.

[0169] Embodiment 48: A method for supporting RedCap User Equipment (RedCap UEs), comprising: transmitting a cell-defined synchronization signal block (CD-SSB) defining a shared initial downlink bandwidth portion (BWP) for a plurality of RedCap UEs and a plurality of non-RedCap UEs; transmitting non-CD-SSBs for separate initial downlink BWPs for the plurality of RedCap UEs and initial uplink BWPs for the plurality of RedCap UEs; and transmitting BWP-specific uplink parameters for the initial uplink BWPs for the plurality of RedCap UEs or active uplink BWPs for the plurality of RedCap UEs, wherein the initial uplink BWPs for the plurality of RedCap UEs and active uplink BWPs for the plurality of RedCap UEs are configured at the edge of the carrier bandwidth.

[0170] Embodiment 49: The method according to Embodiment 48, wherein the BWP-specific uplink parameters include one or more of the following: power control parameters, frequency hopping flags, coverage extension parameters, or waveform configurations for the uplink channel.

[0171] Embodiment 50: The method according to Embodiment 48 or 49, wherein transmitting BWP-specific uplink parameters transmits the reception of an active uplink BWP configuration for multiple RedCap UEs.

[0172] Embodiment 51: The method according to Embodiment 48 or 49, wherein transmitting BWP-specific uplink parameters includes transmitting a BWP switching command.

[0173] Embodiment 52: The method according to Embodiment 48 or 49, wherein transmitting BWP-specific uplink parameters includes transmitting system information updates specific to multiple RedCap UEs.

[0174] Embodiment 53: The method according to any one of Embodiments 1 to 52, wherein the maximum bandwidth of the RedCap UE is lower than the maximum bandwidth of multiple non-RedCap UEs.

[0175] Embodiment 54: A device for wireless communication, comprising: a transceiver; a memory for storing computer executable instructions; and a processor coupled to the transceiver and the memory, configured to execute computer executable instructions and perform the method described in any of Embodiments 1 to 32.

[0176] Embodiment 55: An apparatus for wireless communication comprising means for performing the method described in any of Embodiments 1 to 32.

[0177] Embodiment 56: A non-temporary computer-readable medium for storing computer executable code, wherein the code, when executed by the processor, causes the processor to perform the method described in any of Embodiments 1 to 32.

[0178] Apparatus 57: Apparatus for wireless communication, comprising: a transceiver; a memory for storing computer executable instructions; and a processor coupled to the transceiver and the memory, configured to execute computer executable instructions and perform the method described in any of Apparatus 33 to 52.

[0179] Embodiment 58: An apparatus for wireless communication comprising means for performing the method described in any of Embodiments 33 to 52.

[0180] Embodiment 59: A non-temporary computer-readable medium for storing computer executable code, wherein the code, when executed by the processor, causes the processor to perform the method described in any of Embodiments 33 to 52.

[0181] Embodiment 60: A method comprising: receiving a cell-defined synchronization signal block (CD-SSB) that defines a shared initial downlink bandwidth portion (BWP) for a first type of user equipment (UE) and a second type of UE having a maximum BWP size smaller than that of the first type of UE; switching to a separate initial downlink BWP for the second type of UE; accessing a cell via the separate initial downlink BWP; receiving the configuration of an active downlink BWP for the second type of UE; and determining whether to switch from the active downlink BWP to a shared initial BWP or a separate initial downlink BWP to obtain information.

[0182] Embodiment 61: A method comprising: receiving a cell-defined synchronization signal block (CD-SSB) defining a shared initial downlink bandwidth portion (BWP) for a first type of user equipment (UE) and a second type of UE having a maximum BWP size smaller than that of the first type of UE; receiving a non-CD-SSB for a separate initial downlink BWP for the second type of UE; and selecting one of the CD-SSB or the non-CD-SSB to transmit a random access message based on system information received on the shared initial BWP or the separate initial BWP.

[0183] Embodiment 62: A method comprising receiving a cell-defined synchronization signal block (CD-SSB) defining a shared initial downlink bandwidth portion (BWP) for a first type of user equipment (UE) and a second type of UE having a maximum BWP size smaller than that of the first type of UE; switching to separate initial downlink BWPs and initial uplink BWPs for the second type of UE; and receiving BWP-specific uplink parameters for the initial uplink BWPs or active uplink BWPs for the second type of UE, wherein the initial uplink BWPs and active uplink BWPs for the second type of UE are configured at the edge of the carrier bandwidth.

[0184] Embodiment 63: A method comprising: transmitting a cell-defined synchronization signal block (CD-SSB) defining a shared initial downlink bandwidth portion (BWP) for a first type of user equipment (UE) and a second type of UE having a maximum BWP size smaller than that of the first type of UE; transmitting a non-CD-SSB for a separate initial downlink BWP for the second type of UE; configuring an active downlink BWP for the UE including a paging search space; transmitting a paging physical downlink control channel (PDCCH) indicating that system information has been updated; and transmitting the updated system information on the shared initial downlink BWP, the separate initial downlink BWP, or the active downlink BWP, as indicated by the paging PDCCH.

[0185] Embodiment 64: A method for supporting user equipment (UE), comprising: transmitting a cell-defined synchronization signal block (CD-SSB) defining a shared initial downlink BWP for a first type UE and a second type UE having a smaller maximum bandwidth portion (BWP) size than the first type UE; transmitting a non-CD-SSB for a separate initial downlink BWP for the second type UE and an initial uplink BWP for the second type UE; and transmitting BWP-specific uplink parameters for the initial uplink BWP for the second type UE or an active uplink BWP for the second type UE to the UE, wherein the initial uplink BWP for the second type UE and the active uplink BWP for the second type UE are configured at the edge of the carrier bandwidth.

[0186] Embodiment 65: The method according to any one of embodiments 59 to 64, wherein the maximum BWP size for the first type of UE is greater than or equal to the size of the shared initial downlink BWP.

[0187] Embodiment 66: The method according to any of Embodiments 59 to 65, wherein the maximum BWP size for a second type of UE is smaller than the size of the shared initial downlink BWP.

[0188] Embodiment 67: The method of Embodiment 66, wherein a second type of UE receives signaling only on a shared initial downlink BWP control resource set (CORESET).

[0189] As used herein, the phrase “at least one of” in an enumeration of items refers to any combination of those items that includes a single member. For example, “at least one of a, b, or c” would include a, b, c, ab, ac, bc, and abc.

[0190] The various exemplary logics, logic blocks, modules, circuits, and algorithmic processes described herein in relation to the implementation forms disclosed herein may be implemented as electronic hardware, computer software, or a combination of both. Hardware and software compatibility is briefly described functionally and illustrated in the various exemplary components, blocks, modules, circuits, and processes described above. Whether such functionality is implemented in hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0191] Hardware and data processing devices used to implement the various exemplary logics, logic blocks, modules, and circuits described in relation to the embodiments disclosed herein may be implemented or run using general-purpose single-chip or multi-chip processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, or any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors working with a DSP core, or any other such configuration. In some implementations, specific processes and methods may be performed by circuit configurations specific to a given function.

[0192] In one or more embodiments, the functions described may be implemented in hardware, digital electronic circuit configurations, computer software, firmware, or any combination thereof, including the structures disclosed herein and their structural equivalents. Implementations of the subject matter described herein may also be implemented as one or more computer programs, i.e., as one or more modules of computer program instructions encoded on a computer storage medium for execution by a data processing device or for controlling the operation of a data processing device.

[0193] When implemented in software, the functionality may be stored on or transmitted via computer-readable media as one or more instructions or code. The processes of the methods or algorithms disclosed herein may be executed in a processor-executable software module that resides on computer-readable media. Computer-readable media includes both computer storage media and communication media, including any media that can transfer computer programs from one location to another. Storage media can be any available media that can be accessed by a computer. Such computer-readable media may include, but are not limited to, RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other media that can be used to store desired program code in the form of instructions or data structures and can be accessed by a computer. Any connection may also be appropriately referred to as computer-readable media. The terms "Disk" and "Disc" as used herein include compact discs (CDs), laser discs, optical discs, digital multipurpose discs (DVDs), floppy disks, and Blu-ray® discs, where a disk typically reproduces data magnetically, and a disc reproduces data optically using a laser. Combinations of the above should also be included within the scope of computer-readable media. In addition, the operation of a method or algorithm may reside on machine-readable and computer-readable media that can be incorporated into computer program products as one or any combination or set of code and instructions.

[0194] Various modifications to the implementations described herein may be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other implementations without departing from the spirit or scope of this disclosure. Accordingly, the claims should not be limited to the implementations shown herein, but should be given the broadest scope consistent with this disclosure, the principles disclosed herein, and the novel features.

[0195] In addition, it will be readily apparent to those skilled in the art that the terms “upper” and “lower” are sometimes used to facilitate the description of a figure, indicating a relative position corresponding to the orientation of the figure on a properly oriented page, and may not reflect the proper orientation of any implemented device.

[0196] In the context of separate implementations, some of the features described herein may also be implemented in combination in a single implementation. Conversely, various features described in the context of a single implementation may also be implemented separately in multiple implementations or in any suitable partial combination. Furthermore, features described above may work in several combinations and may even be initially claimed as such, although one or more features from a claimed combination may, in some cases, be removed from that combination, and the claimed combination may cover partial combinations or variations of partial combinations.

[0197] Similarly, while actions are shown in a specific order in the diagrams, this should not be understood as requiring that such actions be performed in a specific or sequential order, or that all illustrated actions be performed, in order to achieve the desired result. Furthermore, the diagrams may schematically illustrate another exemplary process in the form of a flow chart. However, other actions not shown may be incorporated into the schematically illustrated exemplary process. For example, one or more additional actions may be performed before, after, simultaneously with, or in between any of the illustrated actions. In some situations, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the implementation forms described above should not be understood as requiring such separation in all implementation forms, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products. In addition, other implementation forms fall within the scope of the following claims. In some cases, the actions described in the claims may be performed in a different order, and the desired result can still be achieved.

Claims

1. A device for wireless communication for RedCap user equipment (UE), Transceiver and, Memory that stores executable computer instructions, The transceiver and the memory are coupled and execute the computer executable instructions. Receive a cell-defined synchronization signal block (CD-SSB) that defines a shared initial downlink bandwidth portion (BWP) for multiple RedCap UEs and multiple non-RedCap UEs. Switch to separate initial downlink BWP for multiple RedCap UEs. Access the cell via the aforementioned separate initial downlink BWP, Received an active downlink BWP configuration for multiple RedCap UEs, and A processor configured to determine whether to switch from the active downlink BWP to the shared initial downlink BWP or the separate initial downlink BWP in order to obtain information, A device equipped with the following features.

2. The configuration of the active downlink BWP for multiple RedCap UEs includes a paging search space, The apparatus according to claim 1, wherein the processor is configured to receive a paging physical downlink control channel (PDCCH) indicating that system information has been updated in order to determine whether to switch to the shared initial downlink BWP or the separate initial downlink BWP in order to obtain the aforementioned information.

3. In order to determine whether to switch to the shared initial downlink BWP or the separate initial downlink BWP in order to obtain the aforementioned information, the processor: To obtain updated system information, switch from the active downlink BWP to the shared initial downlink BWP or the separate initial downlink BWP, or Decodes a broadcast or multicast physical downlink shared channel (PDSCH) that carries updated system information scheduled by the paging PDCCH over the active downlink BWP for multiple RedCap UEs. The apparatus according to claim 2, configured as follows.

4. The apparatus according to claim 2, wherein the paging search space is configured together with or separately from the wake-up signal search space.

5. The RedCap UE operates in half-duplex frequency-domain duplex (HD-FDD) mode on the active downlink BWP. The apparatus according to claim 2, wherein when a paging occasion overlaps with a semi-static or dynamically configured uplink transmission, receiving the paging search space takes precedence over the uplink transmission.

6. The paging search space is not configured on the active downlink BWP for multiple RedCap UEs. The apparatus according to claim 1, wherein the processor is configured to switch to the separate initial downlink BWP to receive a paging PDCCH in order to determine whether to switch to the shared initial downlink BWP or the separate initial downlink BWP in order to obtain information.

7. In order to determine whether to switch to the shared initial downlink BWP or the separate initial downlink BWP in order to acquire information, the processor is configured to determine whether to switch to one of the active downlink BWP, the separate initial downlink BWP, or the shared initial downlink BWP to perform a measurement based on instructions from the measurement resource. The measurement resource is one or more of the following: Synchronization Signal Block (SSB), Channel State Information Reference Signal (CSI-RS), or Positioning Reference Signal (PRS), and / or The measurement is a Layer 3 measurement including reference signal received power (RSRP), reference signal received quality (RSRQ), signal-to-interference noise ratio (SINR), signal-to-noise ratio (SNR), or a combination thereof, and / or The apparatus according to claim 1, wherein the measurement includes an adjacent cell measurement based on system information of adjacent cells received in the configuration of the active downlink BWP for a plurality of RedCap UEs.

8. The apparatus according to claim 1, wherein the configuration of the active downlink BWP for a plurality of RedCap UEs includes different measurement gaps for measuring the CD-SSB of the shared initial downlink BWP and the non-CD-SSB of the separate initial downlink BWPs.

9. The apparatus according to claim 1, wherein the processor is configured to determine a fallback BWP for RRC re-establishment or RRC release with redirection in order to determine whether to switch to the shared initial downlink BWP or the separate initial downlink BWP in order to obtain information.

10. A method for a RedCap UE (RedCap User Equipment), Receiving a cell-defined synchronization signal block (CD-SSB) that defines a shared initial downlink bandwidth portion (BWP) for multiple RedCap UEs and multiple non-RedCap UEs, Switching to separate initial downlink BWPs for multiple RedCap UEs, Accessing the cell via the aforementioned separate initial downlink BWP, Receiving the configuration of an active downlink BWP for multiple RedCap UEs, To obtain information, determine whether to switch from the active downlink BWP to the shared initial downlink BWP or the separate initial downlink BWP, Methods that include...

11. A device for a base station to support RedCap User Equipment (RedCap UE), Transceiver and, Memory that stores executable computer instructions, The transceiver and the memory are coupled and execute the computer executable instructions. It transmits a cell-defined synchronization signal block (CD-SSB) that defines a shared initial downlink bandwidth portion (BWP) for multiple RedCap UEs and multiple non-RedCap UEs. Send non-CD-SSB to separate initial downlink BWPs for multiple RedCap UEs, The active downlink BWP for the RedCap UE includes a paging search space, Send a paging physical downlink control channel (PDCCH) indicating that system information has been updated. A processor configured to transmit updated system information on the shared initial downlink BWP, the separate initial downlink BWP, or the active downlink BWP, as indicated by the paging PDCCH, A device equipped with the following features.

12. The apparatus according to claim 11, wherein the processor is further configured to transmit instructions for measurement resources on one of the active downlink BWP, the separate initial downlink BWP, or the shared initial downlink BWP.

13. The apparatus according to claim 11, wherein the configuration of the active downlink BWP for the RedCap UE includes system information of adjacent cells to be measured.

14. The apparatus according to claim 11, further comprising transmitting an instruction that all neighboring cells transmit system information on the separate initial BWP for a plurality of RedCap UEs, which is available as a fallback BWP for RRC re-establishment or RRC release with redirection.

15. A method for supporting RedCap User Equipment (RedCap UE), Transmitting a cell-defined synchronization signal block (CD-SSB) that defines a shared initial downlink bandwidth portion (BWP) for multiple RedCap UEs and multiple non-RedCap UEs, Transmitting non-CD-SSB to separate initial downlink BWPs for multiple RedCap UEs, To configure an active downlink BWP for the RedCap UE, including a paging search space, This involves transmitting a paging physical downlink control channel (PDCCH) indicating that system information has been updated, and Transmitting updated system information on the shared initial downlink BWP, the separate initial downlink BWP, or the active downlink BWP, as indicated by the aforementioned paging PDCCH, Methods that include...

Images