KR20240051123A - Selection of different initial bandwidth fractions for reduced functionality user equipment - Google Patents

Abstract

The present disclosure provides systems, methods, and devices that include computer programs encoded in computer storage media for reduced functionality (RedCap) user equipment (UE) and support cells. A RedCap UE consists of multiple bandwidth parts (BWPs). The maximum bandwidth of a RedCap UE is lower than that of a non-RedCap UE. The UE receives a cell-defined synchronization signal block (CD-SSB) that defines a shared initial downlink BWP for RedCap UEs and non-RedCap UEs. The UE switches to a separate initial downlink BWP for the RedCap UE. The UE accesses the cell via a separate initial downlink BWP. The UE receives the configuration of the active downlink BWP for the RedCap UE. The UE determines whether to switch from the active downlink BWP to a shared initial BWP or a separate initial downlink BWP to obtain information such as updated system information, system measurements, and uplink configuration information.

Description

Selection of different initial bandwidth fractions for reduced functionality user equipment

Cross-reference to related applications

This application is related to U.S. Provisional Application No. 63/234,966, filed on August 19, 2021, entitled “SELECTION OF DIFFERENT INITIAL BANDWIDTH PARTS FOR REDUCED CAPABILITY USER EQUIPMENT” and U.S. Patent Application Serial No. 17/820,371, filed August 17, 2022, entitled “Selection of Different Initial Bandwidth Portions for Reduced Function User Equipment,” which is assigned to its assignee and claims priority in its entirety. The content is incorporated herein by reference.

Technology field

The present disclosure relates to wireless communications including selection of different initial bandwidth portions for reduced functionality user equipment.

Wireless communication systems are widely deployed to provide a variety of telecommunication services such as telephony, video, data, messaging, and broadcast. A typical wireless communication system may employ multi-access technology that can support communication with multiple users by sharing available system resources. Examples of these multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal 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. Includes a synchronous code division multiple access system.

These multiple access technologies have been adopted in various communication standards to provide a common protocol that allows different wireless devices to communicate at city, country, regional and even global levels. An example of a communication standard is 5G New Radio (NR: New Radio). 5G NR is being developed by the Third Generation Partnership Project (3GPP) to meet new requirements related to latency, reliability, security, scalability (such as the Internet of Things (IoT)) and other requirements. It is part of the ongoing mobile broadband evolution announced by . 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communications (mMTC), and ultra-reliable low latency communications (URLLC). Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard.

The systems, methods, and devices of this disclosure each have several innovative aspects, none of which are solely responsible for the desirable properties disclosed herein.

One innovative aspect of the subject matter described in this disclosure may be implemented in a method for obtaining information in reduced capability user equipment (RedCap UE). The method receives a cell-defining synchronization signal block (CD-SSB) that defines a shared initial downlink bandwidth part (BWP) for RedCap UEs and non-RedCap UEs. It includes steps to: The method includes switching to a separate initial downlink BWP for the RedCap UE. The method includes accessing the cell via a separate initial downlink BWP. The method includes receiving a configuration of an active downlink BWP for a RedCap UE. The method includes determining whether to switch from an active downlink BWP to a shared initial BWP or a separate initial downlink BWP to obtain information.

In another innovative aspect, the present disclosure provides a method of initiating a random access procedure. The method includes receiving, at a reduced capability user equipment (RedCap UE), a cell-defined synchronization signal block (CD-SSB) defining a shared initial downlink bandwidth portion (BWP) for RedCap UEs and non-RedCap UEs. do. The method includes receiving, at a RedCap UE, a non-CD-SSB for a separate initial downlink BWP for the RedCap UE. The method includes selecting either a CD-SSB or a non-CD-SSB to transmit the random access message based on system information received on the shared initial BWP or a separate initial BWP.

In another innovative aspect, the present 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 RedCap UEs and non-RedCap UEs. The method includes switching to a separate initial downlink BWP for the RedCap UE and a separate initial uplink BWP for the RedCap UE. The method includes receiving BWP specific uplink parameters for an initial uplink BWP for a RedCap UE or an active uplink BWP for a RedCap UE, the initial uplink BWP for a RedCap UE and an active uplink BWP for a RedCap UE. Link BWP is configured at the edge of the carrier bandwidth.

The present disclosure also provides a device (e.g., a UE) that includes a memory storing computer-executable instructions and at least one processor configured to execute the computer-executable instructions to perform at least one of the above methods. Provided is a device including means for performing at least one of the above methods, and a non-transitory computer-readable medium storing computer-executable instructions for performing at least one of the above methods.

One innovative aspect of the subject matter described in this disclosure may be implemented in a way to support RedCap UEs (e.g., 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 RedCap UEs and non-RedCap UEs. The method includes transmitting a non-CD-SSB for a separate initial downlink BWP for the RedCap UE. The method includes configuring an active downlink BWP for a RedCap UE including 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 updated system information on a shared initial downlink BWP, a separate initial downlink BWP, or an active downlink BWP as indicated by a paging PDCCH.

In another innovative aspect, the present disclosure provides a method for supporting RedCap UE 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 RedCap UEs and non-RedCap UEs. The method includes transmitting a non-CD-SSB for a separate initial downlink BWP for the RedCap UE and an initial uplink BWP for the RedCap UE. The method includes transmitting BWP specific uplink parameters for an initial uplink BWP for a RedCap UE or an active uplink BWP for a RedCap UE, and transmitting BWP specific uplink parameters for an initial uplink BWP for a RedCap UE and an active uplink BWP for a RedCap UE. Link BWP is configured at the edge of the carrier bandwidth.

The present disclosure also provides a device (e.g., a BS) that includes a memory storing computer-executable instructions and at least one processor configured to execute computer-executable instructions to perform at least one of the above methods. Provided is a device including means for performing at least one of the above methods, and a non-transitory computer-readable medium storing computer-executable instructions for performing at least one of the above methods.

Details of one or more implementations of the subject matter described in this disclosure are set forth in the accompanying drawings and the description below. Other features, aspects and advantages will become apparent from the description, drawings and claims. Note that the relative dimensions in the following drawings may not be drawn to scale.

1 is a diagram illustrating an example of a wireless communication system and access network.
2A is a diagram illustrating an example of a first frame.
FIG. 2B is a diagram illustrating an example of a DL channel within a subframe.
Figure 2C is a diagram illustrating an example of a second frame.
2D is a diagram illustrating an example of a subframe.
3 is a diagram illustrating an example of a base station (BS) and user equipment (UE) of an access network.
Figure 4 is a diagram illustrating an example of a cell configuration including separate initial bandwidth portions (BWPs) and active BWPs for a reduced capability (RedCap) UE.
Figure 5 is a diagram illustrating another example of a cell configuration including an active BWP for a RedCap UE.
6 is a diagram illustrating an example of a technique for obtaining updated system information in a configuration with multiple BWPs.
7 is a message diagram illustrating example messages for managing multiple BWPs.
8 is a conceptual data flow diagram illustrating data flow between different means/components of an example BS.
9 is a conceptual data flow diagram illustrating data flow between different means/components of an example UE.
Figure 10 is a flow diagram of an example of a method for a UE to obtain information in a configuration with multiple BWPs.
Figure 11 is a flow diagram of an example of a method for a UE to initiate a random access procedure in a configuration with multiple BWPs.
Figure 12 is a flow diagram of an example of a method for configuring BWP-specific uplink parameters in a configuration where a UE has multiple BWPs.
13 is a flow diagram of an example method for a BS to support a RedCap UE with multiple BWPs.
14 is a flow diagram of an example method for configuring BWP-specific uplink parameters in a configuration where a BS has multiple BWPs.
Like reference numbers and designations in the various drawings identify similar elements.

The following description is directed to specific implementations for the purpose of illustrating innovative aspects of the present disclosure. However, those skilled in the art will readily recognize that the teachings herein may be applied in a number of different ways. Some of the examples of this disclosure include wireless and wired local area networks (LANs) according to the Institute of Electrical and Electronics Engineers (IEEE) 802.11 wireless standard, IEEE 802.3 Ethernet standard, and IEEE 1901 Powerline communication (PLC). : Based on local area network communication. However, the described implementation is consistent with the IEEE 802.11 standard, the Bluetooth® standard, Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), and the Global System for Mobile Communications (GSM). 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 Downlink Packet Access), High Speed Uplink Packet Access (HSUPA), Evolved High Speed Packet Access (HSPA+), Long Term Evolution (LTE) , AMPS, or any of the other known signals used to communicate within wireless, cellular, or Internet of Things (IOT) networks, such as systems utilizing 3G, 4G, or 5G, or any of their additional enabling technologies. Accordingly, it can be implemented in any device, system, or network capable of transmitting and receiving RF signals.

A user equipment (UE) may utilize a subset of the total cell bandwidth of a cell, referred to as a bandwidth portion (BWP). For example, in 5G NR Releases 15 and 16, the maximum BWP size is 100 MHz. In higher frequency ranges (eg FR 2), the size of the bandwidth portion may increase. This wide bandwidth can be designed to meet the needs of premium smartphones leveraging enhanced mobile broadband (eMBB) and other use cases such as ultra-reliable low-latency communications (URLLC) and vehicle to anything (V2X). For some devices, referred to as reduced feature or RedCap devices, the maximum size of the BWP can be reduced to provide power savings and reduced complexity. That is, a first type of UE may use a BWP of the maximum BWP size, while a RedCap UE may be a second type of UE with a lower maximum BWP size than the first type of UE for the frequency range. Examples of RedCap devices may include wearables, industrial wireless sensor networks (IWSN), surveillance cameras, and low-cost smartphones. In some cases, data rates for RedCap devices can be achieved with BWP sizes of less than 100 MHz. In an example implementation, in FR1, the maximum device bandwidth for non-RedCap devices may be 100 MHz, while the maximum device bandwidth for RedCap devices may be 20 MHz. In FR2, the maximum device bandwidth of a non-RedCap device may be 200 MHz, while the maximum device bandwidth of a RedCap device may be 100 MHz. Other maximum device bandwidths may apply in other implementations.

RedCap devices can coexist with non-RedCap devices on the same cell. However, the reduced bandwidth of RedCap devices may be incompatible with some system configurations. For example, a physical uplink control channel (PUCCH) is typically assigned to the edge of an uplink BWP and is connected to an adjacent physical uplink shared channel (PUSCH) near the center of the uplink BWP. ) transmission and random access channel (RACH: random access channel) transmission are allowed. Broadcast signaling for initial access (e.g., channel raster and synchronization signal block (SSB)) is typically transmitted near the middle of the downlink BWP. Therefore, a RedCap UE with a reduced BWP size may transmit on PUCCH and not receive SSB. One proposal to accommodate RedCap UEs is to provide separate initial BWPs for RedCap devices carrying downlink signaling. A separate initial BWP for RedCap devices may be located near the edge of the carrier bandwidth such that the PUCCH resources overlap those for non-RedCap devices. In some proposals, an active BWP may also be configured for RedCap devices. Multiple BWPs can provide flexibility to RedCap devices, but may introduce additional signaling challenges. In general, 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 measurements, random access procedures, radio resource control (RRC) reset, and uplink configuration may be affected by the presence of multiple BWPs.

In one aspect, this disclosure provides signaling using multiple BWPs for RedCap UEs. RedCap UEs may receive cell-defining SSBs (cell-defining (CD)-SSBs) on the shared initial BWP applicable to both RedCap UEs and non-RedCap UEs. CD-SSB refers to a set of SSBs located at SSB raster points. Therefore, CD-SSB can be detected by the UE performing initial access. A RedCap UE may receive a non-CD SSB on a separate initial BWP for the RedCap UE. Non-CD-SSBs are not located at raster points. The UE knows the location of the non-CDSSB only after connecting to the network (e.g. shared initial BWP). The RedCap UE may be further configured with an active BWP for the RedCap UE. The RedCap UE may decide whether to switch from the active BWP to a shared initial BWP or a separate initial BWP. For example, if the active BWP is configured as a paging search space, the RedCap UE receives a paging physical downlink control channel (PDCCH) and whether to receive updated system information on a shared initial BWP, a separate initial BWP, or the active BWP. can be decided. If the active BWP is not configured as a paging search space, the RedCap UE may periodically switch to a separate initial BWP to receive paging messages. Likewise, the configuration of the active BWP may indicate measurement resources (e.g., for layer 3 measurements) on any of the shared initial BWP, separate initial BWP, or active BWP, and measurement gaps on the active BWP. For example, a RedCap UE can measure both CD-SSB on a shared initial downlink BWP and non-CD-SSB on a separate initial downlink BWP. For fallback during RRC release with RRC reset or redirection, a default initial downlink BWP may be standardized, or the network may determine when a separate initial downlink BWP for the RedCap UE is available in the neighboring cell. It can be expressed.

For the random access procedure, the system information may specify whether the RedCap UE will use CD-SSB or non-CD-SSB for initial random access message transmission. The RedCap UE may use CD-SSB for the first transmission of the random access message and switch to non-CD-SSB if retransmission is needed and there is time to measure the non-CD-SSB before retransmission. More generally, the uplink transmission parameters may be BWP specific (eg, different between the initial uplink BWP for a RedCap UE and the active initial uplink BWP for the RedCap UE). The RedCap UE may receive BWP-specific uplink parameters in BWP configuration, BWP switching commands, or system information updates to the RedCap UE.

Certain implementations of the subject matter described in this disclosure may be implemented to realize one or more of the following potential advantages. RedCap devices can coexist on the same carrier bandwidth as non-RedCap UEs and use narrower bandwidth, which can save power. A RedCap UE may consist of multiple BWPs and may switch BWPs to obtain information without interfering with the operation of non-RedCap UEs.

Several aspects of a telecommunication system will now be presented with reference to various devices and methods. These devices and methods will be described in the detailed description that follows and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or combinations thereof. Whether these elements are implemented in hardware or software depends on the specific application and design constraints imposed on the overall system.

For example, an element, any portion of an element, or any combination of elements may be implemented as a “processing system” that includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), and reduced instruction set computing. (RISC: reduced instruction set computing) processor, SoC: systems on a chip, baseband processor, FPGA: field programmable gate array, programmable logic device (PLD) ), state machines, gate logic, discrete hardware circuitry, and other suitable hardware configured to perform the various functions described throughout the present disclosure. A processor may include an interface or be coupled to an interface capable of acquiring or outputting signals. The processor may acquire a signal through the interface and output the signal through the 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 may be implemented to receive or transmit signals, or both. One or more processors of the processing system may execute software. Software means instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, whether referred to as software, firmware, middleware, microcode, hardware description language, etc. , will be broadly interpreted to mean subroutine, object, executor, thread of execution, procedure, function, etc.

Accordingly, in one or more example implementations, the described functionality may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media, which may be referred to as non-transitory computer-readable media. Non-transitory computer-readable media may exclude transient signals. A storage medium can be any available medium that can be accessed by a computer. By way of example, and not limitation, such computer-readable media may include random-access memory (RAM), read-only memory (ROM), and electrically erasable programmable ROM (EEPROM). ), optical disk storage, magnetic disk storage, other magnetic storage devices, or any combination of the types of computer-readable media mentioned above, or for storing computer-executable code in the form of instructions or data structures that can be accessed by a computer. It may include any other media that can be used.

1 is a diagram illustrating an example of a wireless communication system and access network 100. A wireless communication system (also referred to as a wireless wide area network (WWAN)) includes a base station 102, a UE 104, an Evolved Packet Core (EPC) 160, and a 5G core (5GC). (such as) includes other core networks 190. Base station 102 may include a macro cell (high power cellular base station) or a small cell (low power cellular base station). A macrocell includes a base station. 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(D)-RAN) or an open RAN (O(Open)-RAN) architecture, where the functions include a central unit (CU), one or more distributed units It is divided between multiple units, such as distributed unit (DU) or radio unit (RU). Such an architecture may be configured to utilize a protocol stack that is logically partitioned between one or more units (such as one or more CUs and one or more DUs). In some aspects, a CU may be implemented within an edge RAN node, and in some aspects one or more DUs may be co-located with the CU or may be geographically distributed across one or multiple RAN nodes. A DU may be implemented to communicate with one or more RUs.

In some implementations, one or more of the UEs 104 may include a RedCap BWP component 140 that manages multiple BWPs for the RedCap UE. RedCap BWP component 140 may include a shared initial BWP component 142 configured to receive a CD-SSB defining a shared initial BWP for RedCap UEs and non-RedCap UEs. RedCap BWP component 140 may include a separate initial BWP component 144 configured to switch to a separate initial downlink BWP for the RedCap UE. For example, separate initial BWP component 144 may be configured to receive non-CD-SSB for a separate initial downlink BWP for a RedCap UE. RedCap BWP component 140 may access the cell through a separate initial downlink BWP. RedCap BWP component 140 may include an active BWP component 146 configured to receive configuration of an active downlink BWP for a RedCap UE. RedCap BWP component 140 may include a BWP switch 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, RedCap BWP component 140 is configured to select either a CD-SSB or a non-CD-SSB to transmit a random access message based on system information received on the shared initial BWP or a separate initial BWP. May include a random access component 910. In some implementations, RedCap BWP component 140 is configured to receive BWP specific uplink parameters for an initial uplink BWP for a RedCap UE or an active uplink BWP for a RedCap UE (FIG. 9 ) can be optionally included. The initial uplink BWP for RedCap UE and the active uplink BWP for RedCap UE may be configured at the edge of the carrier bandwidth.

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 RedCap UEs. As illustrated in FIG. 8 , RedCap BWP control component 120 may include a shared initial BWP component 810 configured to transmit a CD-SSB defining a shared initial BWP for RedCap UEs and non-RedCap UEs. . RedCap BWP control component 120 may include a separate initial BWP component 820 configured to transmit a non-CD-SSB for a separate initial downlink BWP for a RedCap UE. RedCap BWP control component 120 may include an active BWP component 830 configured to configure an active downlink BWP for the RedCap UE, including a paging search space. RedCap BWP control component 120 may include a paging component 840 configured to transmit a paging PDCCH indicating that system information has been updated. RedCap BWP control component 120 includes 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 indicated by the paging PDCCH. It can be included. In some implementations, RedCap BWP control component 120 optionally configures an uplink configuration component 860 to transmit BWP specific uplink parameters for the initial uplink BWP for a RedCap UE or an active uplink BWP for a RedCap UE. It can be included. The initial uplink BWP for RedCap UE and the active uplink BWP for RedCap UE may be configured at the edge of the carrier bandwidth.

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

Base station 102 may communicate wirelessly with UE 104. Each base station 102 may provide communications coverage for a respective geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, the small cell 102' may have a coverage area 110' that overlaps the coverage area 110 of one or more macro base stations 102. A network containing both small cells and macro cells may be known as a heterogeneous network. The heterogeneous network may also include Home Evolved Node B (HeNB), which can provide services to a limited group known as a closed subscriber group (CSG). Communication link 112 between base station 102 and UE 104 may include UL (also referred to as reverse link) transmission from UE 104 to base station 102 or DL (DL) transmission from base station 102 to UE 104. (also referred to as the forward link) may include transmission. Communication link 112 may use multiple-input and multiple-output (MIMO) antenna technology including spatial multiplexing, beam forming, or transmit diversity. The communication link may be via one or more carrier waves. The base station 102/UE 104 may receive (5, 10, 15, 20, Spectrum up to Y MHz bandwidth (such as 100, 400 MHz, etc.) is available. Carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric for DL and UL (such that more or less carriers may be assigned to DL than UL). The component carrier may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell), and the secondary component carrier may be referred to as a secondary cell (SCell).

Certain UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158 . D2D communication link 158 may use DL/UL WWAN spectrum. D2D communication link 158 includes a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and One or more sidelink channels, such as a physical sidelink control channel (PSCCH), may be used. D2D communication can be achieved through various wireless D2D communication systems, such as, for example, FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

The wireless communication system further includes a Wi-Fi access point (AP) 150 that communicates with a Wi-Fi station (STA) 152 via a communication link 154 in the 5 GHz unlicensed frequency spectrum. It can be included. When communicating in an unlicensed frequency spectrum, the STA 152/AP 150 may perform a clear channel assessment (CCA) before communicating to determine whether the channel is available.

Small cells 102' may operate in licensed or unlicensed frequency spectrum. When operating in the unlicensed frequency spectrum, small cells 102' may employ NR and use the same 5 GHz unlicensed frequency spectrum as used by Wi-Fi AP 150. Small cells 102' employing NR in the unlicensed frequency spectrum can increase coverage of the access network or increase the capacity of the access network.

Base station 102, whether a small cell 102' or a large cell (such as a macro base station), may include an eNB, a gNodeB (gNB), or another type of base station. Some base stations, such as gNB 180, may operate in one or more frequency bands within the electromagnetic spectrum.

The electromagnetic spectrum is often subdivided into various classes, bands, channels, etc. based on frequency/wavelength. In 5G NR, two initial operating bands have been identified with the frequency range designations FR1 (410 MHz - 7.125 GHz) and FR2 (24.25 GHz - 52.6 GHz). The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Although parts of FR1 are greater than 6 GHz, FR1 is often (interchangeably) referred to as the “Sub-6 GHz” band in various documents and papers. Similar nomenclature issues sometimes arise with FR2, which is the extremely high frequency (EHF) band (30 GHz - 300 GHz), identified as the "millimeter wave" band by the International Telecommunications Union (ITU). ) is often (interchangeably) referred to in documents and papers as "millimeter wave" (mmW), despite its difference from

With the above aspects in mind, and unless specifically stated otherwise, terms such as "sub-6 GHz" as used herein may be below 6 GHz, may be within FR1, or may include mid-band frequencies. It should be understood that the frequencies can be expressed in a wide range. Additionally, unless specifically stated otherwise, terms such as "millimeter wave" as used herein broadly refer to frequencies that may include mid-band frequencies, may be within FR2, or may be within the EHF band. You must understand that you can. Communications using the mmW radio frequency band have extremely high path loss and short range. The mmW base station 180 may utilize beamforming 182 with the UE 104 to compensate for path loss and short range.

EPC 160 includes a Mobility Management Entity (MME) 162, another MME 164, a serving gateway 166, a Multimedia Broadcast Multicast Service (MBMS) gateway 168, It may include a Broadcast Multicast Service Center (BM-SC) 170 and a Packet Data Network (PDN) gateway 172. The MME 162 may communicate with a Home Subscriber Server (HSS) 174. MME 162 is a control node that processes signaling between UE 104 and EPC 160. Generally, the MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are delivered through the serving gateway 166, which is itself connected to the PDN gateway 172. The PDN gateway 172 provides UE IP address allocation as well as 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 service. The BM-SC 170 may provide functions for providing and delivering MBMS user services. BM-SC 170 may serve as an entry point for content provider MBMS transmissions and may be used to license and initiate MBMS bearer services within a public land mobile network (PLMN), and may be used to authorize and initiate MBMS bearer services. Can be used to schedule 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 broadcasting specific services, and may be used for session management (start/start) may be responsible for collecting eMBMS related to suspension) and billing information.

The core network 190 includes an Access and Mobility Management Function (AMF) 192, another AMF 193, a Session Management Function (SMF) 194, and a User Plane Function (UPF: User Plane Function) (195) may be included. AMF 192 may communicate with Unified Data Management (UDM) 196. AMF 192 is a control node that processes signaling between UE 104 and core network 190. Generally, AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are passed through UPF 195. UPF 195 provides UE IP address allocation as well as 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 service.

The base station includes gNB, Node B, eNB, access point, base transceiver station, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), and transmission and reception point. (TRP: transmit reception point) or some other suitable term. Base station 102 provides an access point to EPC 160 or core network 190 for UE 104. Examples of UEs 104 include cellular phones, smart phones, session initiation protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radio, global positioning systems, multimedia devices, and video devices. , digital audio players (such as MP3 players), cameras, gaming consoles, tablets, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, medical devices, implants, sensors/actuators, displays, or any Includes other similar functional devices. Some of the UEs 104 may be referred to as IoT devices (such as parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be a 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. It may be referred to as a terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable term.

The following description may focus on 5G NR, but the concepts described herein may also apply to other similar areas such as other wireless technologies, including LTE, LTE-A, CDMA, GSM, and future 6G technologies.

FIG. 2A is a diagram 200 illustrating an example of a first frame. FIG. 2B is a diagram 230 illustrating an example of a DL channel within a subframe. FIG. 2C is a diagram 250 illustrating an example of a second frame. Figure 2D is a diagram 280 illustrating an example subframe. The 5G NR frame structure can be FDD, with subframes within a subcarrier set dedicated to DL or UL, for a specific subcarrier set (carrier system bandwidth), or subframes within a subcarrier set, for a specific subcarrier set (carrier system bandwidth). The frame may be TDD, dedicated to both DL and UL. A subset of the total cell bandwidth of a cell is called a bandwidth portion (BWP), and bandwidth adaptation is achieved by configuring the UE into BWP(s) and informing the UE which of the configured BWPs is the currently active BWP. In one aspect, a narrow bandwidth part (NBWP) refers to a BWP that has a bandwidth that is less than or equal to the maximum configurable bandwidth of the BWP. The bandwidth of NBWP is smaller than the carrier system bandwidth. NBWP can hop through the carrier system bandwidth. Hopping can provide frequency diversity gain without increasing the BWP size or using a narrower active BWP.

In the example provided by Figures 2a, 2c, the 5G NR frame structure is assumed to be TDD, with subframe 4 consisting of slot format 28 (mostly including DL), where D is DL, U is UL, and X is DL/UL. It is flexible for use, and subframe 3 consists of slot format 34 (mostly including UL). Subframes 3 and 4 are shown as slot formats 34 and 28, respectively, but any particular subframe may be configured in any of the various available slot formats 0-61. Slot formats 0 and 1 are both DL and UL, respectively. Other slot formats 2-61 include a mix of DL, UL and flexible symbols. The UE receives a slot format indicator (SFI) (dynamically through DL control information (DCI) or semi-statically through radio resource control (RRC) signaling). statically) configured in slot format. Note that the description below also applies to the 5G NR frame structure, which is TDD.

Different wireless communication technologies may have different frame structures or different channels. A frame (10 milliseconds (ms)) can be divided into 10 equally sized subframes (1 ms). Each subframe may include one or more time slots. A subframe may also include mini-slots, which may contain 7, 4, or 2 symbols. Each slot may contain 7 or 14 symbols depending on the slot configuration. For slot configuration 0, each slot may contain 14 symbols, and for slot configuration 1, each slot may contain 7 symbols. The symbol on the DL may be a cyclic prefix (CP) OFDM (CP-OFDM) symbol. The symbols on the UL are either CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (for power limited scenarios; limited to single stream transmission). It may be (also called a single carrier frequency-division multiple access (SC-FDMA) symbol). The number of slots within a subframe is based on slot configuration and numerology. For slot configuration 0, different numerologies μ 0 to 5 allow 1, 2, 4, 8, 16 and 32 slots per subframe respectively. For slot configuration 1, different numerologies 0 to 2 allow 2, 4, and 8 slots per subframe respectively. Therefore, for slot configuration 0 and numerology μ, there are 14 symbols/slot and 2 ^μ slots/subframe. Subcarrier spacing and symbol length/duration are functions of numerology. The subcarrier spacing is It may be equal to, where μ is numerology 0 to 5. Likewise, numerology μ=0 has a subcarrier spacing of 15 kHz and numerology μ=5 has a subcarrier spacing of 480 kHz. Symbol length/duration is inversely proportional to subcarrier spacing. 2A-2D provide examples of slot configuration 0 with 14 symbols per slot and numerology μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 microseconds (μs).

A resource grid can be used to represent the frame structure. Each time slot includes a resource block (RB) (also referred to as a physical RB (PRB)) spanning 12 consecutive subcarriers. The resource grid is divided into a number of resource elements (RE). The number of bits carried by each RE depends on the modulation scheme.

As illustrated in FIG. 2A, some of the REs carry reference (pilot) signals (RS) for the UE. RS is the Demodulating RS (DM-RS) (denoted as Rx for one specific configuration, where 100x is the port number, but other DM-RS configurations are also possible) and the Channel State Information Reference Signal (CSI-RS) for channel estimation in the UE. : channel state information reference signal) may be included. RS may also include beam measurement RS (BRS), beam refinement RS (BRRS), and phase tracking RS (PT-RS).

Figure 2B illustrates an example of various DL channels within a subframe of a frame. 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 An OFDM symbol contains four consecutive REs. The primary synchronization signal (PSS) may be within symbol 2 of a specific subframe of the frame. PSS is used by UE 104 to determine subframe/symbol timing and physical layer identity. The secondary synchronization signal (SSS) may be within symbol 4 of a specific subframe of the frame. SSS is used by the UE to determine the physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine a physical cell identifier (PCI). The UE can determine the location of the above-mentioned DM-RS based on PCI. A physical broadcast channel (PBCH) carrying a master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS)/PBCH block (SSB). You can. MIB provides multiple RBs of system bandwidth and system frame number (SFN). The Physical Downlink Shared Channel (PDSCH) carries user data and broadcast system information not transmitted over the PBCH, such as system information blocks (SIBs) and paging messages.

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

Figure 2D illustrates an example of various UL channels within a subframe of a frame. PUCCH may be located as shown in one configuration. PUCCH includes uplink control such as scheduling request, channel quality indicator (CQI), precoding matrix indicator (PMI), rank indicator (RI), and HARQ ACK/NACK feedback. Returns information (UCI: uplink control information). PUSCH carries data and can additionally be used to carry a buffer status report (BSR), power headroom report (PHR), or UCI.

3 is a diagram of an example of a base station 310 and a UE 350 in an access network. In the DL, IP packets from EPC 160 may be provided to controller/processor 375. Controller/processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, and a radio link control (RLC) layer. : radio link control) layer and medium access control (MAC: medium access control) layer. Controller/processor 375 is responsible for broadcasting system information (such as MIB, SIB), RRC connection control (such as RRC connection paging, RRC connection establishment, RRC connection modification, RRC connection release), and inter-radio access technology (RAT). RRC layer functions associated with measurement configuration for mobility and UE measurement reporting; PDCP layer functions associated with header compression/decompression, security (encryption, decryption, integrity protection, integrity verification) and handover support functions; Delivery of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs and RLC RLC layer functions associated with reordering of data PDUs; Associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, reporting of scheduling information, error correction via HARQ, priority processing, and logical channel prioritization. Provides MAC layer functions.

Transmit (TX) processor 316 and Receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1, which includes the physical (PHY) layer, includes error detection for the transmission channel, forward error correction (FEC) coding/decoding of the transmission channel, interleaving, rate matching, mapping to the physical channel, and modulation of the physical channel. /May include demodulation and MIMO antenna processing. TX processor 316 (binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK: M- Processes mapping to signal connections based on various modulation schemes (such as phase-shift keying) and M-quadrature amplitude modulation (M-QAM). Coded and modulated symbols can be split into parallel streams. Each stream is mapped to an OFDM subcarrier, multiplexed with a reference signal (such as a pilot) in the time or frequency domain, and combined together using the Inverse Fast Fourier Transform (IFFT) to form a time domain OFDM symbol stream. You can create a physical channel that carries . OFDM streams are spatially precoded to generate multiple spatial streams. Channel estimates from channel estimator 374 may be used for spatial processing as well as for determining coding and modulation schemes. The channel estimate may be derived from a reference signal transmitted by UE 350 or channel state feedback. Each spatial stream may be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX may modulate an RF carrier wave into a respective spatial stream for transmission.

At UE 350, each receiver 354RX receives a signal via its respective antenna 352. Each receiver 354RX recovers the information modulated on the RF carrier wave and provides the information to the reception (RX) processor 356. TX processor 368 and RX processor 356 implement layer 1 functionality associated with various signal processing functions. RX processor 356 may perform spatial processing on information to recover any spatial stream destined for UE 350. If multiple spatial streams are destined for UE 350, they may be combined by RX processor 356 into a single OFDM symbol stream. RX processor 356 converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbol and reference signal of each subcarrier are recovered and demodulated by determining the most likely signal connection transmitted by base station 310. This soft decision may be based on a channel estimate computed by channel estimator 358. The soft decisions are decoded and deinterleaved to recover the data and control signals that were originally transmitted by base station 310 on the physical channel. Data and control signals are provided to a controller/processor 359 that implements layer 3 and layer 2 functions.

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

Similar to the functionality described with respect to DL transmission by base station 310, controller/processor 359 may include RRC layer functions associated with system acquisition (such as MIB, SIB), RRC connectivity, and measurement reporting; PDCP layer functions associated with header compression/decompression, security (encryption, decryption, integrity protection, integrity verification); RLC layer functions associated with delivery of upper layer PDUs, error correction via ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs and reordering of RLC data PDUs; MAC layer functions associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, reporting of scheduling information, error correction through HARQ, priority processing, and logical channel prioritization. to provide.

Channel estimates derived by channel estimator 358 from feedback or reference signals transmitted by base station 310 may be used by TX processor 368 to select appropriate coding and modulation schemes and facilitate spatial processing. . The spatial stream generated by TX processor 368 may be provided to a different antenna 352 via a separate transmitter 354TX. Each transmitter 354TX may modulate an RF carrier wave into a respective spatial stream for transmission.

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

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

At least one of TX processor 368, RX processor 356, and controller/processor 359 may be configured to perform aspects related to RedCap BWP component 140 of FIG. 1. For example, memory 360 may include executable instructions defining RedCap BWP component 140. TX processor 368, RX processor 356, and/or controller/processor 359 may be configured to execute RedCap BWP component 140.

At least one of TX processor 316, RX processor 370, and controller/processor 375 may be configured to perform aspects related to RedCap BWP control component 120 of FIG. 1. For example, memory 376 may include executable instructions defining RedCap BWP control component 120. TX processor 316, RX processor 370, and/or controller/processor 375 may be configured to execute RedCap BWP control component 120.

FIG. 4 is a diagram illustrating an example of a configuration 400 of multiple BWPs for a RedCap UE on a carrier bandwidth 410 . 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 composed of a shared initial UL BWP (420) and a shared initial DL BWP (430). The shared initial UL BWP 420 and shared initial DL BWP 430 may be used by both RedCap UEs and non-RedCap UEs. A non-RedCap UE or baseline device may refer to a first type of UE capable of using a BWP of a maximum BWP size, and a RedCap UE may be a second type of UE with a lower maximum BWP size than the first type of UE for the frequency range. It may refer to a type of UE. Here, the description of non-RedCap UE and RedCap UE can be equally applied to the first type of UE and the second type of UE.

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) is the different use of the shared initial UL BWP 420 and the shared initial DL BWP 430. may result in In particular, a non-RedCap UE may continue to use the shared initial UL BWP 420 and the shared initial DL BWP 430 as the initial BWP after cell acquisition. For example, the maximum BWP size of a non-RedCap UE may be greater than or equal to the size of the shared initial UL BWP 420 and the shared initial DL BWP 430. On the other hand, the maximum BWP size of the RedCap UE may be smaller than the size of the shared initial UL BWP (420) and/or the size of the shared initial DL BWP (430). For example, a RedCap UE cannot communicate in part of the shared initial UL BWP 420 and/or the size of the shared initial DL BWP 430. For example, the shared initial UL BWP 420 may include a PUCCH resource 422 configured at the edge of the carrier bandwidth 410, and the shared initial DL BWP 430 may include a CD resource 422 near the center of the carrier bandwidth 410. -SSB (432) can be returned. CD-SSB 432 may be transmitted according to the channel raster so that the shared initial DL BWP 430 can be located during cell search. In this way, CD-SSB 432 defines a cell. In one aspect, a RedCap UE may receive a portion of the initial DL BWP 430 carrying a CD-SSB 432 (e.g., an initial control resource set (CORESET)), but may receive a portion of the initial UL BWP 420 It may not be possible to transmit on the PUCCH resource 422.

In one aspect, CD-SSB 432 contains or identifies system information for a distinct initial DL BWP 450 for a RedCap UE. A separate initial DL BWP 450 may carry a non-CD-SSB 452. The non-CD-SSB 452 may carry some or all of the information about the cell and a separate initial DL BWP 450. Non-CD-SSB 452 may contain information about a separate UL BWP 440 for RedCap UE. A separate UL BWP 440 may be located at the edge of the carrier bandwidth 410 and may include PUCCH resources 442 that overlap with the PUCCH resources 422 of the shared initial UL BWP 420. RedCap UE 104 may connect to the cell via a separate initial DL BWP 450 and a separate initial UL BWP 440. For example, RedCap UE 104 may receive non-CD-SSB 452 to obtain system information and perform measurements. RedCap UE 104 may perform a random access procedure on a separate initial UL BWP 440. For example, a separate initial UL BWP 440 may include a physical random access channel (PRACH) opportunity to transmit an initial random access message. A separate initial DL BWP 450 may contain a common search space for receiving subsequent random access messages.

When RedCap UE 104 accesses the cell, the network may configure RedCap UE 104 with an active UL BWP 460 for the RedCap UE and an active DL BWP 470 for the RedCap UE. The active DL BWP 470 may be outside of the shared initial DL BWP 430 and/or a separate initial DL BWP 450. In one aspect, the active DL BWP 470 may be configured with signaling to facilitate operation of the RedCap UE. For example, the active DL BWP 470 may include a periodic reference signal, such as a tracking reference signal (TRS), a channel state information reference signal (CSI-RS), and/or a positioning reference signal (PRS). can be returned. The active DL BWP 470 may include a common search space (CSS) for paging and wake-up signals (WUS). The active DL BWP 470 may include dedicated RRC signaling for system information updates when a paging search space is not configured. The active DL BWP 470 is a layer 3 intra-frequency (e.g., a shared initial DL BWP 430 and/or a separate initial DL BWP 450) for measuring neighboring cells and/or reference signals on other BWPs (e.g., may include intra-frequency measurement gaps.

FIG. 5 is a diagram illustrating another example of a configuration 500 of multiple BWPs for a RedCap UE on a carrier bandwidth 510 . Similar to configuration 400, configuration 500 provides a shared initialization configuration that can be used by both a first type of UE (e.g., a non-RedCap UE) and a second type of UE (e.g., a RedCap UE). It may include a UL BWP (520) and a shared initial DL BWP (530). 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 CORESET0 carrying CD-SSB 532 .

RedCap UE 104 may access the cell through the shared initial DL BWP 530. The network may configure the RedCap UE 104 with an active UL BWP 540 for the RedCap UE and an active DL BWP 550 for the RedCap UE. The active DL BWP 470 may be external to the shared initial DL BWP 530 . In one aspect, the active DL BWP 470 may be configured with signaling to facilitate 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 intra-frequency measurement gap for measuring neighboring cells and/or reference signals on other BWPs (e.g., shared initial DL BWP 530). .

In one aspect, under configuration 400 or configuration 500, a RedCap UE configured with an active DL BWP 460, 540 may be configured to use an active DL BWP 460, 540, a shared DL BWP 430, 530, and/or a separate Various information can be obtained from the initial DL BWP (450). For simplicity, the additional description refers to configuration 400 but may also apply to configuration 500. Examples of information that the RedCap UE can obtain include paging messages, updated system information, measurements such as layer 3 measurements and neighbor cell measurements, and neighbor cell system information during release with RRC reset or redirection.

In connected mode, UE 104 may receive updated system information. When the cell updates system information, the cell may transmit a paging message to inform the connected UE to obtain updated system information. For a non-RedCap UE, the UE receives paging information for the CSS of the initial DL BWP, obtains a management information block (MIB) from the CD-SSB 432, and obtains remaining minimum system information (RMSI) from the MIB. system information) can be found. In configurations 400 and 500, the RedCap UE's active BWP may not overlap with the initial DL BWP or the CSS of the CD-SSB.

6 is a diagram 600 illustrating a technique for obtaining updated system information for a RedCap UE 104 configured with an active DL BWP 470, 550 for the RedCap UE. Active DL BWPs 470, 550 may be configured with a paging search space 610. Paging search space 610 may be part of CSS. Paging search space 610 may be configured jointly or separately from the WUS search space. UE 104 may monitor paging search space 610 for paging PDCCH 612 . When RedCap UE 104 operates with half-duplex frequency domain duplexing (HD-FDD) on an active downlink BWP, paging opportunities overlap with semi-statically or dynamically configured uplink transmissions. If available, receiving the paging search space may be prioritized over uplink transmission. If the paging PDCCH 612 indicates that system information has been updated, the UE switches to the shared initial DL BWP 430, 530 or a separate initial DL BWP 450 to receive system information updates or to the active DL BWP 470, 550. ), you can decode the broadcast/multicast PDSCH.

For example, at block 620, paging PDCCH 612 may indicate switching BWP to receive system information updates. At block 622, the paging PDCCH notifies the RedCap UE to switch to another DL BWP to receive system information updates. The UE may receive an indication whether the initial downlink BWP for obtaining updated system information is a shared initial BWP or a separate initial downlink BWP. For example, indications include the presence of system information in a separate initial downlink BWP, radio network temporary identifier (RNTI) scrambling of the cyclic redundancy check (CRC) of the paging PDCCH 612, It may be one of the BWP identifier of the paging PDCCH 612, the DMRS configuration of the paging PDCCH 612, or the paging opportunity configuration of the paging PDCCH 612. Based on the indication, UE 104 may switch to the initial shared DL BWP 430, 530 at block 622 or to a separate initial DL BWP 450 at block 624.

As another example, at block 630, paging PDCCH 612 may indicate that the RedCap UE receives system information updates without switching the DL BWP. Paging PDCCH 612 may schedule system information updates on active DL BWPs 470 and 550. For example, the paging PDCCH may be configured by a PDSCH on the active downlink BWP 470, 550 for the RedCap UE via one of the RNT scrambling of the CRC of the paging PDCCH, the BWP identifier within the paging PDCCH, the DMRS configuration of the paging PDCCH, or the paging PDCCH. It can represent opportunity composition. At block 632, the system information update is broadcast or multicast to RedCap UEs on the PDSCH scheduled by the paging PDCCH using the group RNTI, which may be a function of the cell ID, BWP ID, or group common parameters.

FIG. 7 is a message diagram 700 illustrating an example message between base station 102 and UE 104 to obtain information with multiple BWPs for a RedCap UE. Base station 102 may broadcast CD-SSB 710 for the shared initial DL BWP 430, 530. In some implementations, base station 102 may also broadcast non-CD-SSB 720 to a separate DL BWP 450.

UE 104 may transmit a random access message 730. For example, the random access message 730 may be a first random access message, such as Msg1 in a 4-step random access procedure or MsgA in a 2-step random access procedure. Once the cell is configured with both a shared initial DL BWP 430 and a separate initial DL BWP 450, the UE 104 configures the CD-SSB 710 and the non-CD-SSB (710) to transmit the first random access message. 720). In some implementations, the system information displayed by CD-SSB 710 and/or non-CD-SSB 720 may explicitly indicate which SSB to use. In some implementations, a rule may identify the preference or ranking of an SSB. For example, UE 104 may initially transmit a first random access message based on CD-SSB 710 and, if the time between initial transmission and retransmission is greater than a threshold, non-CD-SSB ( A retransmission of the first random access message may be transmitted based on 720) (whereby the UE may measure non-CD-SSB 720).

After the random access procedure, base station 102 may transmit active RedCap BWP configuration 740 for active DL BWPs 470, 550 and active UL BWPs 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 of the paging search space 610. RedCap UE 104 may switch to active DL BWP 470, 550 and active UL BWP 460, 540 for communication in connected mode.

In some implementations, base station 102 may transmit BWP-specific uplink parameters 745. For example, the transmit BWP-specific uplink parameters 745 may include BWP-specific power control parameters, frequency hopping flags, coverage enhancement parameters, and/or one or more UL BWPs (e.g., shared UL BWP 420, separate It may include a waveform configuration for a UL channel (e.g., PRACH/PUSCH/PUCCH/SRS) for the UL BWP 440 or the active UL BWP 460. BWP-specific uplink parameters 745 may be conveyed as BWP configuration or reconfiguration information (e.g., in active RedCap BWP configuration 740). BWP-specific uplink parameters 745 may be conveyed as a BWP switching command (e.g., on DCI or MAC-CE). BWP-specific uplink parameters 745 may be conveyed as updated system information dedicated to the RedCap UE (e.g., on a separate DL BWP 450 or an active DL BWP 470, 550).

Base station 102 may transmit a paging PDCCH 612. If paging search space 610 is configured on active DL BWPs 470, 550, UE 104 can receive paging PDCCH 612 without BWP switching. As discussed above in relation to FIG. 6 , RedCap UE 104 may switch to a shared DL BWP 430, 530 or a separate initial DL BWP 550 to receive updated system information 750. . Alternatively, when indicated by paging PDCCH 612, RedCap UE 104 may remain on the active DL BWP 470, 550 and receive PDSCH carrying updated system information.

If the active DL BWP 470, 550 is not configured with a paging search space 610, the RedCap UE 104 may use a separate initial DL to receive the paging PDCCH 612 and/or updated system information 750. It can be switched periodically with BWP (550). In a first option, RedCap UE 104 may receive paging PDCCH 612 on a separate initial DL BWP 550 . If the paging PDCCH 612 indicates updated system information, RedCap UE 104 may switch to the shared DL BWP 430 to receive updated system information 750. In a second option, the updated system information 750 may be broadcast on a separate initial DL BWP 550 and the RedCap UE 104 may receive the update (e.g., without receiving the paging PDCCH 612). Updated system information 750 may be periodically received to determine whether an event has occurred. In a third option, the RedCap UE 104 receives the paging PDCCH 612 on a separate initial DL BWP 550 and updates system information on the separate initial DL BWP 550 based on the paging PDCCH 612 ( 750) can be received.

The base station 102 may transmit a reference signal (RS) indication 760. RS indication 760 may identify a measurement resource on either an active downlink BWP, a separate initial downlink BWP, or a shared initial downlink BWP. For example, measurement resources include reference signal received power (RSRP), reference signal received quality (RSRQ), signal to interference plus noise ratio (SINR), and signal It may be for layer 3 measurements such as 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 may transmit the indicated reference signal 770 on the indicated measurement resource.

RS indication 760 may be conveyed through a combination of one or more of system information, RRC signaling, MAC-CE, and DCI. If the measurement resources are on a separate initial downlink BWP or a shared initial downlink BWP, the RS indication 760 indicates whether the RedCap UE 104 is on the active DL BWP 470, 550 to switch BWPs to perform measurements. A measurement gap can be configured. In some implementations, the measurements include neighboring cell measurements based on system information of the neighboring cells. System information of neighboring cells may be provided in the active RedCap BWP configuration 740. Accordingly, the RedCap UE can obtain the system information of the neighboring cell even if the entire system information is not transmitted in the separate initial DL BWP 450 of the neighboring cell.

In some implementations, base station 102 may transmit a neighbor cell indication 780. The neighboring cell indication 780 may indicate whether the neighboring cell is configured with a separate DL BWP 450 for the RedCap UE carrying system information. Neighbor cell indication 780 may indicate whether a separate DL BWP 450 is used for RRC reset or RRC release with redirection. For example, the default configuration may be to use the shared initial downlink BWP 430 as a fallback BWP during RRC release with RRC reset or redirection. When the RedCap UE 104 receives the neighboring cell indication 780, the RedCap UE 104 may use the neighboring cell's separate DL BWP 450 as a fallback BWP.

In some implementations, the active RedCap BWP configuration 740 includes different measurement gaps to measure the CD-SSB 710 of the shared initial downlink BWP and the non-CD-SSB 720 of the separate initial downlink BWP. do. Base station 102 may transmit SSB Tx power indication 790 for CD-SSB 710 and non-CD-SSB 720. The SSB Tx power indication 790 is the absolute transmit power of the CD-SSB 710 of the shared initial downlink BWP 430, 530 and the differential of the non-CD-SSB 720 of the separate initial downlink BWP 450. May include an indication of transmit power.

8 is a conceptual data flow diagram 800 illustrating data flow between different means/components of an example base station 802, which may be an example of base station 102 including a RedCap BWP control component 120. RedCap BWP control component 120 may be implemented by memory 376 and TX processor 316, RX processor 370, and/or controller/processor 375 of FIG. 3. For example, memory 376 may store executable instructions defining RedCap BWP control component 120, and TX processor 316, RX processor 370, and/or controller/processor 375 may store those instructions. You can run .

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. Base station 102 may include a transmitter component 872, which may include, for example, an RF transmitter for transmitting signals as described herein. In one aspect, receiver component 870 and transmitter component 872 may be co-located in a transceiver, as illustrated by TX/RX 318 in FIG. 3.

As discussed in relation to FIG. 1 , RedCap BWP control component 120 includes a shared initial BWP component 810, a separate initial BWP component 820, an active BWP component 830, a paging component 840, and system information. May include an update component 850. RedCap BWP control component 120 may optionally include an uplink configuration component 860.

Receiver component 870 may receive UL signals from UE 104, including UL communications. In some implementations, receiver component 870 may optionally receive a random access message from a UE 104 seeking a connection to base station 802. Receiver component 870 may provide identification of UE 104 to active BWP component 830 .

Shared initial BWP component 810 may transmit CD-SSB 710 defining shared initial downlink BWPs 430, 530 for RedCap UEs and non-RedCap UEs via transmitter component 872. For example, CD-SSB 710 may contain or identify system information. The shared initial BWP component 810 may update system information and provide an indication of the update to the paging component 840.

The separate initial BWP component 820 may transmit the non-CD-SSB 720 for a separate initial downlink BWP for the RedCap UE via the transmitter component 872. For example, non-CD-SSB 710 may contain or identify system information specific to the RedCap UE. In some implementations, system information transmitted by separate initial BWP components 820 on separate initial downlink BWPs 550 may include some or all of the system information transmitted by shared initial BWP component 810. You can. A separate initial BWP component 820 may update the system and provide an indication of the update to paging component 840.

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

Paging component 840 may receive an indication that system information has been updated from shared initial BWP component 810 and/or separate initial BWP component 820. Paging component 840 may transmit a paging PDCCH 612 indicating updates to system information via transmitter component 872. When updated system information is transmitted as a PDSCH over the active DL BWP 470, 550, paging component 840 may schedule the PDSCH and include scheduling information in paging PDCCH 612. The paging component 840 may provide resources for the PDSCH to the system information update component 850.

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 paging PDCCH 612. For example, system information update component 850 receives resources for a PDSCH from paging component 840 and transmits updated system information 750 as a PDSCH on active DL BWPs 470, 550.

Uplink configuration component 860 may transmit BWP-specific uplink parameters 745 for an initial uplink BWP 440 for a RedCap UE or an active uplink BWP 460, 540 for a RedCap UE.

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

UE 104 may include receiver component 970, which may include, for example, an RF receiver for receiving signals as described herein. UE 104 may include a transmitter component 972, which may include, for example, an RF transmitter for transmitting signals as described herein. In one aspect, receiver component 970 and transmitter component 972 may be co-located in a transceiver, such as TX/RX 352 in FIG. 3 .

As discussed in relation to Figure 1, 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. You can. In some implementations, RedCap BWP component 140 may optionally include a random access component 910 and/or an uplink configuration component 920.

Receiver component 970 includes CD-SSB 710, non-CD-SSB 720, active RedCap BWP configuration 740, BWP-specific uplink parameters 745, paging PDCCH 612, and updated system information. DL signals described herein may be received, such as 750, RS indication 760, RS 770, neighbor cell indication 780, and SSB Tx power indication 790. Receiver component 970 may provide CD-SSB 710 to shared initial BWP component 142. Receiver component 970 may provide non-CD-SSB 720 to a separate initial BWP component 144. Receiver component 970 provides active RedCap BWP configuration 740, updated system information 750, RS indication 760, RS 770, neighbor cell indication 780, and SSB Tx power indication 790. Provided to component 146. Receiver component 970 may provide BWP-specific uplink parameters 745 to uplink configuration component 920. Receiver component 970 may provide paging PDCCH 612 to BWP switching component 148.

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

A separate initial BWP component 144 may receive non-CD-SSB 720 via receiver component 970. A separate initial BWP component 144 may receive system information for the RedCap UE based on the non-CD-SSB 720. For example, separate initial BWP components 144 may determine RACH opportunities for separate initial uplink BWPs 440. A separate initial BWP component 144 may provide a RACH opportunity to the random access component 910.

Random access component 910 may receive a RACH opportunity from a separate initial BWP component 144. In some implementations, random access component 910 can receive CD-SSB 710 and non-CD-SSB 720 or measurements thereof. Random access component 910 may access the cell via a distinct initial downlink BWP 450 (e.g., based on identified RACH opportunities). For example, random access component 910 may transmit a random access message on a RACH opportunity. Random access component 910 may select either CD-SSB 710 or non-CD-SSB 720 to transmit a random access message based on system information received on the shared initial BWP or a separate initial BWP. there is.

Active BWP component 146 may receive active RedCap BWP configuration 740 via receiver component 970. An active RedCap BWP configuration 740 may respond to a random access procedure (e.g., a UE connecting to a cell). Active BWP component 146 may forward signaling received on active downlink BWP 470 to BWP switching component 148.

BWP switching component 148 may switch 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, BWP switching component 148 can select a BWP to receive various information. For example, BWP switching component 148 controls UE 904 to receive paging PDCCH on a separate initial downlink BWP 450 or active downlink BWP 470 depending on the configuration of paging search space 610. can do. Once the paging PDCCH 612 is received, the BWP switching component 148 can control the UE 904 to receive updated system information 750 on the BWP indicated by the paging PDCCH.

FIG. 10 is a flow diagram of an example method 1000 for a RedCap UE configured with multiple BWPs to obtain information. Method 1000 may include a memory 360 and may be used to configure a UE (such as an entire UE 104 or a RedCap BWP component 140, a TX processor 368, an RX processor 356, or a controller/processor 359). It may be performed by a UE (such as UE 104), which may be a component of 104). Method 1000 may be performed by RedCap BWP component 140 in communication with RedCap BWP control component 120 of base station 102. Optional blocks are shown with dashed lines.

At block 1010, the method 1000 may include receiving a CD-SSB defining a shared initial downlink BWP for RedCap UEs and non-RedCap UEs. In some implementations, for example, UE 104, RX processor 356, or controller/processor 359 may configure a CD-SSB (CD-SSB) that defines a shared initial downlink BWP 430 for RedCap UEs and non-RedCap UEs. 720), the RedCap BWP component 140 or the shared initial BWP component 142 may be executed. Accordingly, a UE 104, RX processor 356, or controller/processor 359 running a RedCap BWP component 140 or a shared initial BWP component 142 may provide a shared initial downlink for RedCap UEs and non-RedCap UEs. A means for receiving a CD-SSB defining a BWP may be provided.

At block 1020, the method 1000 may include switching to a separate initial downlink BWP for the RedCap UE. For example, in some implementations, UE 104, RX processor 356, or controller/processor 359 executes RedCap BWP component 140 or a separate initial BWP component 144 to create a separate BWP component for the RedCap UE. You can switch to the initial downlink BWP (450). Accordingly, a UE 104, RX processor 356, or controller/processor 359 running RedCap BWP component 140 or a separate initial BWP component 144 switches to a separate initial downlink BWP for the RedCap UE. The means to do so can be provided.

At block 1030, the method 1000 may include accessing the cell via a separate initial downlink BWP. In some implementations, for example, UE 104, TX processor 368 or controller/processor 359 executes RedCap BWP component 140 or random access component 910 to configure a separate initial downlink BWP ( The cell can be accessed through 450). Accordingly, a UE 104 running RedCap BWP component 140 or random access component 910, TX processor 368 or controller/processor 359 may have a means for accessing the cell via a separate initial downlink BWP. can be provided.

At block 1040, method 1000 may include receiving a configuration of an active downlink BWP for a RedCap UE. In some implementations, for example, UE 104, RX processor 356, or controller/processor 359 executes RedCap BWP component 140 or active BWP component 146 to maintain an active downlink for a RedCap UE. Configuration 740 of BWP 470 may be received. Accordingly, a UE 104, RX processor 356, or controller/processor 359 running RedCap BWP component 140 or active BWP component 146 may be configured to receive configuration of an active downlink BWP for a RedCap UE. We can provide the means.

At block 1050, the method 1000 may include determining whether to switch from the active downlink BWP to a shared initial BWP or a separate initial downlink BWP to obtain information. In some implementations, for example, UE 104, RX processor 356 or controller/processor 359 executes RedCap BWP component 140 or BWP switching component 148 to obtain information about active down You can decide whether to switch from the link BWP to a shared initial BWP or to a separate initial downlink BWP. Accordingly, the UE 104, RX processor 356, TX processor 368, or controller/processor 359 running the RedCap BWP component 140 or BWP switching component 148 must use the active down signal to obtain information. A means may be provided to determine whether to switch from a link BWP to a shared initial BWP or to a separate initial downlink BWP.

FIG. 11 is a flow diagram of an example method 1100 for a RedCap UE configured with multiple BWPs to initiate random access. Method 1100 may include the entire UE 104 or a UE (such as a RedCap BWP component 140, TX processor 368, RX processor 356, or controller/processor 359) (which may include memory 360). It may be performed by a UE (such as UE 104), which may be a component of 104). Method 1100 may be performed by RedCap BWP component 140 in communication with RedCap BWP control component 120 of base station 102. Optional blocks are shown with dashed lines.

At block 1110, method 1100 may include receiving a CD-SSB defining a shared initial downlink BWP for RedCap UEs and non-RedCap UEs. In some implementations, for example, UE 104, RX processor 356, or controller/processor 359 may configure a CD-SSB (CD-SSB) that defines a shared initial downlink BWP 430 for RedCap UEs and non-RedCap UEs. 720), the RedCap BWP component 140 or the shared initial BWP component 142 may be executed. Accordingly, a UE 104, RX processor 356, or controller/processor 359 running a RedCap BWP component 140 or a shared initial BWP component 142 may provide a shared initial downlink for RedCap UEs and non-RedCap UEs. A means for receiving a CD-SSB defining a BWP may be provided.

At block 1120, method 1100 may include receiving a non-CD-SSB for a separate initial downlink BWP for a RedCap UE. For example, in some implementations, UE 104, RX processor 356, or controller/processor 359 executes RedCap BWP component 140 or a separate initial BWP component 144 to create a separate BWP component for the RedCap UE. Non-CD-SSB 720 for the initial downlink BWP 450 may be received. Accordingly, the UE 104, RX processor 356, or controller/processor 359 running the RedCap BWP component 140 or a separate initial BWP component 144 may be responsible for the separate initial downlink BWP for the RedCap UE. A means for receiving non-CD-SSB may be provided.

At block 1130, the method 1100 may include selecting either a CD-SSB or a non-CD-SSB to transmit the random access message based on system information received on the shared initial BWP or a separate initial BWP. You can. In some implementations, for example, UE 104, TX processor 368 or controller/processor 359 executes RedCap BWP component 140 or random access component 910 to generate a shared initial BWP or a separate initial BWP. The RedCap BWP component 140 or the random access component 910 may be executed to select either a CD-SSB or a non-CD-SSB to transmit a random access message based on system information received on the BWP. Accordingly, a UE 104, TX processor 368, or controller/processor 359 running RedCap BWP component 140 or random access component 910 may be responsible for system information received on the shared initial BWP or separate initial BWP. A means may be provided for selecting either CD-SSB or non-CD-SSB to transmit a random access message based on

FIG. 12 is a flow diagram of an example method 1200 for a RedCap UE configured with multiple BWPs to configure BWP-specific uplink parameters. Method 1200 may include a memory 360 and may be used to configure a UE (such as the entire UE 104 or a RedCap BWP component 140, a TX processor 368, an RX processor 356, or a controller/processor 359). It may be performed by a UE (such as UE 104), which may be a component of 104). Method 1000 may be performed by RedCap BWP component 140 in communication with RedCap BWP control component 120 of base station 102. Optional blocks are shown with dashed lines.

At block 1210, the method 1200 may include receiving a CD-SSB defining a shared initial downlink BWP for RedCap UEs and non-RedCap UEs. In some implementations, for example, UE 104, RX processor 356, or controller/processor 359 may configure a CD-SSB (CD-SSB) that defines a shared initial downlink BWP 430 for RedCap UEs and non-RedCap UEs. 720), the RedCap BWP component 140 or the shared initial BWP component 142 may be executed. Accordingly, a UE 104, RX processor 356, or controller/processor 359 running a RedCap BWP component 140 or a shared initial BWP component 142 may provide a shared initial downlink for RedCap UEs and non-RedCap UEs. A means for receiving a CD-SSB defining a BWP may be provided.

At block 1220, method 1200 may include switching to a separate initial downlink BWP for the RedCap UE and a separate initial uplink BWP for the RedCap UE. In some implementations, for example, UE 104, RX processor 356, or controller/processor 359 executes RedCap BWP component 140 or a separate initial BWP component 144 to create a separate BWP component for the RedCap UE. may switch to the initial downlink BWP 450 for and the initial uplink BWP 440 for the RedCap UE. Accordingly, a UE 104, RX processor 356, or controller/processor 359 running a RedCap BWP component 140 or a separate initial BWP component 144 may configure a separate initial downlink BWP for a RedCap UE and a RedCap A means for switching to the initial uplink BWP for the UE may be provided.

At block 1230, the method 1200 may include receiving BWP specific uplink parameters for an initial uplink BWP for a configured RedCap UE or an active uplink BWP for a RedCap UE at the edge of the carrier bandwidth. In some implementations, for example, UE 104, RX processor 356, or controller/processor 359 executes RedCap BWP component 140 or uplink configuration component 920 to configure carrier bandwidth 410. It may receive BWP-specific uplink parameters 745 for an initial uplink BWP 440 for a RedCap UE configured at the edge or an active uplink BWP 460 for a RedCap UE. Accordingly, a UE 104, RX processor 356, TX processor 368, or controller/processor 359 running RedCap BWP component 140 or uplink configuration component 920 can configure RedCap at the edge of the carrier bandwidth. A means may be provided to receive BWP specific uplink parameters for an initial uplink BWP for a UE or an active uplink BWP for a RedCap UE.

FIG. 13 is a flow diagram of an example method 1300 for a base station to control multiple BWPs for a RedCap UE. Method 1300 may include the entire base station 102 (memory 376) or the base station 102, such as a RedCap BWP control component, TX processor 316, RX processor 370, or controller/processor 375. It may be performed by a base station (such as base station 102), which may be a component of. Method 1300 may be performed by RedCap BWP control component 120 in communication with RedCap BWP component 140 of UE 104.

At block 1310, method 1300 may include transmitting a CD-SSB defining a shared initial BWP for RedCap UEs and non-RedCap UEs. In some implementations, for example, base station 102, TX processor 316 or controller/processor 375 executes RedCap BWP control component 120 or shared initial BWP component 810 to enable RedCap UE and non- A CD-SSB may be transmitted that defines a shared initial BWP for the RedCap UE. Accordingly, the base station 102, TX processor 316, or controller/processor 375 running the RedCap BWP control component 120 or the shared initial BWP component 810 can configure the shared initial BWP for RedCap UEs and non-RedCap UEs. A means for transmitting a CD-SSB that defines can be provided.

At block 1320, the method 1300 may include transmitting a non-CD-SSB for a separate initial downlink BWP for the RedCap UE. In some implementations, for example, base station 102, TX processor 316, or controller/processor 375 executes RedCap BWP control component 120 or a separate initial BWP component 820 to configure Non-CD-SSB 720 may be transmitted for a separate initial downlink BWP 450. Accordingly, a base station 102, TX processor 316, or controller/processor 375 running RedCap BWP control component 120 or a separate initial BWP component 820 may be connected to a separate initial downlink BWP for a RedCap UE. A means for transmitting non-CD-SSB may be provided.

At block 1330, method 1300 may include configuring an active downlink BWP for the RedCap UE, including a paging search space. In some implementations, for example, base station 102, RX processor 370, or controller/processor 375 executes RedCap BWP control component 120 or active BWP component 830 to access paging search space 610. An active downlink BWP 570 for the RedCap UE may be configured, including. Accordingly, a base station 102, RX processor 370, or controller/processor 375 running RedCap BWP control component 120 or active BWP component 830 may provide an active downlink to a RedCap UE, including a paging search space. It can provide a means to form a BWP.

At block 1340, method 1300 may include transmitting a paging PDCCH indicating that system information has been updated. In some implementations, for example, base station 102, TX processor 316, or controller/processor 375 executes RedCap BWP control component 120 or paging component 840 to perform paging to indicate that system information has been updated. PDCCH (612) can be transmitted. Accordingly, base station 102, TX processor 316, or controller/processor 375 executing RedCap BWP control component 120 or paging component 840 may provide means for transmitting a paging PDCCH indicating that system information has been updated. can be provided.

At 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 indicated by the paging PDCCH. In some implementations, for example, base station 102, TX processor 316, or controller/processor 375 executes RedCap BWP control component 120 or system information update component 850 to As such, updated system information 750 may be transmitted for a shared initial downlink BWP 430, a separate initial downlink BWP 450, or an active downlink BWP 470. Accordingly, the base station 102, TX processor 316, or controller/processor 375 executing RedCap BWP control component 120 or system information update component 850 may perform a shared initial downlink, as indicated by the paging PDCCH. A means may be provided for transmitting updated system information on a BWP, a separate initial downlink BWP, or an active downlink BWP.

FIG. 14 is a flow diagram of an example method 1400 for a base station to control multiple BWPs for a RedCap UE. Method 1300 may include a memory 376 and a base station, such as the entire base station 102 or the RedCap BWP control component 120, TX processor 316, RX processor 370, or controller/processor 375. It may be performed by a base station (such as base station 102, which may be a component of 102). Method 1000 may be performed by RedCap BWP control component 120 in communication with RedCap BWP component 140 of UE 104.

At block 1410, method 1400 may include transmitting a CD-SSB defining a shared initial BWP for RedCap UEs and non-RedCap UEs. In some implementations, for example, base station 102, TX processor 316 or controller/processor 375 executes RedCap BWP control component 120 or shared initial BWP component 810 to enable RedCap UE and non- A CD-SSB may be transmitted that defines a shared initial BWP for the RedCap UE. Accordingly, the base station 102, TX processor 316, or controller/processor 375 running the RedCap BWP control component 120 or the shared initial BWP component 810 can configure the shared initial BWP for RedCap UEs and non-RedCap UEs. A means for transmitting a CD-SSB that defines can be provided.

At block 1420, the method 1400 may include transmitting a non-CD-SSB for a separate initial downlink BWP for the RedCap UE and an initial uplink BWP for the RedCap UE. In some implementations, for example, base station 102, TX processor 316, or controller/processor 375 executes RedCap BWP control component 120 or a separate initial BWP component 820 to configure A non-CD-SSB 720 may be transmitted for a separate initial downlink BWP 450 and an initial uplink BWP 440 for the RedCap UE. Accordingly, the base station 102, TX processor 316, or controller/processor 375 running the RedCap BWP control component 120 or a separate initial BWP component 820 may configure a separate initial downlink BWP and A means for transmitting non-CD-SSB for the initial uplink BWP for the RedCap UE may be provided.

At block 1430, the method 1400 may include transmitting BWP specific uplink parameters for an initial uplink BWP for a RedCap UE or an active uplink BWP for a RedCap UE that is configured at the edge of the carrier bandwidth. In some implementations, for example, base station 102, TX processor 316, or controller/processor 375 executes RedCap BWP control component 120 or uplink configuration component 860 to configure carrier bandwidth 410. BWP-specific uplink parameters may be transmitted for an initial uplink BWP 440 for a RedCap UE configured at the edge of or an active uplink BWP 460 for a RedCap UE. Accordingly, the base station 102, TX processor 316, or controller/processor 375 executing RedCap BWP control component 120 or uplink configuration component 860 configures the initial configuration for RedCap UEs at the edge of the carrier bandwidth. A means may be provided for transmitting BWP specific uplink parameters for an uplink BWP or an active uplink BWP for a RedCap UE.

The following provides an overview of aspects of the present disclosure:

Aspect 1: A method as seen at a reduced functionality user equipment (RedCap UE): Receiving a cell-defined synchronization signal block (CD-SSB) defining a shared initial downlink bandwidth portion (BWP) for RedCap UEs and non-RedCap UEs. steps; switching to a separate initial downlink BWP for the RedCap UE; accessing the cell via a separate initial downlink BWP; Receiving configuration of an active downlink BWP for a RedCap 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.

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

Aspect 3: The method of Aspect 2, wherein determining whether to switch to a shared initial BWP or a separate initial downlink BWP to obtain updated system information comprises switching to a shared initial BWP from an active downlink BWP to obtain updated system information. and switching to the BWP or a separate initial downlink BWP.

Aspect 4: The method of Aspect 3, further comprising receiving an indication of whether the initial downlink BWP for obtaining updated system information is a shared initial BWP or a separate initial downlink BWP.

Aspect 5: The method of Aspect 4, wherein the indication is presence of system information of a separate initial downlink BWP, a radio network temporary identifier (RNTI) of a cyclic redundancy check (CRC) of a paging PDCCH. ) is one of scrambling, BWP identifier of the paging PDCCH, DMRS configuration of the paging PDCCH, or paging opportunity configuration of the paging PDCCH.

Aspect 6: The method of aspect 2, wherein determining whether to switch to a shared initial BWP or a separate initial downlink BWP to obtain information comprises the steps scheduled by the paging PDCCH on the active downlink BWP for the RedCap UE. and decoding a broadcast or multicast Physical Downlink Shared Channel (PDSCH) carrying updated system information.

Aspect 7: The method of Aspect 6, wherein the paging PDCCH comprises radio network temporary identifier (RNTI) scrambling of a cyclic redundancy check (CRC) of the paging PDCCH, a BWP identifier of the paging PDCCH, DMRS configuration of the paging PDCCH, or paging of the paging PDCCH. Indicates the PDSCH on the active downlink BWP for the RedCap UE through one of the opportunistic configurations.

Aspect 8: The method of aspect 6 or 7, wherein the broadcast or multicast PDSCH is scrambled by a group radio network temporary identifier (RNTI) that is a function of a cell ID, BWP ID, or group-common parameter.

Aspect 9: The method of any one of Aspects 2 to 8, wherein the paging search space is constructed jointly or separately with the wake-up signal search space.

Aspect 10: The method of any of Aspects 2-8, wherein the RedCap UE operates with half-duplex frequency domain duplexing (HD-FDD) on an active downlink BWP, and receiving the paging search space occurs when paging opportunities are half-duplexed. -If it overlaps with statically or dynamically configured uplink transmissions, it is prioritized over the uplink transmission.

Aspect 11: The method of aspect 1, wherein the paging search space is not configured on an active downlink BWP for a RedCap UE and determine whether to switch to a shared initial BWP or a separate initial downlink BWP to obtain information. The step includes switching to a separate initial downlink BWP to receive the paging PDCCH.

Aspect 12: The method of aspect 11, further comprising switching to the shared initial BWP in response to a paging PDCCH indicating updated system information.

Aspect 13: The method of aspect 11, further comprising receiving updated system information broadcast on a separate initial downlink BWP.

Aspect 14: The method of aspect 11, further comprising receiving updated system information scheduled by a paging PDCCH on a separate initial downlink BWP.

Aspect 15: The method of any of Aspects 1 to 14, wherein determining whether to switch to a shared initial BWP or a separate initial downlink BWP to obtain information comprises: an active downlink BWP, a separate initial downlink BWP; and determining whether to switch to perform measurements based on an indication of a measurement resource on one of the BWP or the shared initial downlink BWP.

Aspect 16: The method of aspect 15, wherein the measurement resource is one or more of a synchronization signal block (SSB), a channel state information reference signal (CSI-RS), or a positioning reference signal (PRS).

Aspect 17: The method of aspect 15 or 16, wherein the measurements comprise reference signal received power (RSRP), reference signal received quality (RSRQ), signal to interference plus noise ratio (SINR), signal to noise ratio (SNR), or a combination thereof. Tier 3 measures include:

Aspect 18: The method of any of aspects 15-17, wherein the measurements include neighbor cell measurements based on system information of the neighbor cell received in configuration of an active downlink BWP for the RedCap UE.

Aspect 19: The method of any of Aspects 1 to 18, wherein the configuration of the active downlink BWP for the RedCap UE measures the CD-SSB of the shared initial downlink BWP and the non-CD-SSB of the separate initial downlink BWP. Includes different measurement gaps for:

Aspect 20: The method of aspect 19, further comprising receiving an indication of the absolute transmit power of the CD-SSB of the shared initial downlink BWP and the differential transmit power of the non-CD-SSB of the separate initial downlink BWP. do.

Aspect 21: The method of any of Aspects 1 to 20, wherein determining whether to switch to a shared initial BWP or a separate initial downlink BWP to obtain information comprises: for RRC release with RRC reset or redirect. It includes determining a fallback BWP.

Aspect 22: The method of aspect 21, wherein the fallback BWP is the shared initial downlink BWP.

Aspect 23: The method of aspect 21, wherein determining a fallback BWP includes receiving an indication that all neighboring cells transmit system information on a distinct initial BWP for the RedCap UE, and wherein the fallback BWP is a distinct initial down BWP. This is the link BWP.

Aspect 24: A method in a reduced functionality user equipment (RedCap UE), comprising: receiving a cell-defined synchronization signal block (CD-SSB) defining a shared initial downlink bandwidth portion (BWP) for a RedCap UE and a non-RedCap UE. steps; Receiving a non-CD-SSB for a separate initial downlink BWP for a RedCap UE; and selecting either a CD-SSB or a non-CD-SSB to transmit the random access message based on system information received on the shared initial BWP or the separate initial BWP.

Aspect 25: The method of aspect 24, wherein the selecting step is based on system information received on the shared initial BWP or a separate initial BWP.

Aspect 26: The method of aspect 25, wherein selecting includes selecting a CD-SSB for initial transmission of the random access message.

Aspect 27: The method of aspect 26, wherein the selecting step includes selecting a CD-SSB for subsequent transmission of the random access message if the time for retransmission is less than a threshold; or selecting a non-CD-SSB for subsequent transmission of the random access message when the time for retransmission is greater than or equal to the threshold.

Aspect 28: A method in a reduced functionality user equipment (RedCap UE), comprising: receiving a cell-defined synchronization signal block (CD-SSB) defining a shared initial downlink bandwidth portion (BWP) for a RedCap UE and a non-RedCap UE. steps; switching to separate initial downlink BWPs for RedCap UEs and separate initial uplink BWPs for RedCap UEs; and receiving BWP specific uplink parameters for an initial uplink BWP for a RedCap UE or an active uplink BWP for a RedCap UE, comprising: an initial uplink BWP for a RedCap UE and an active uplink BWP for a RedCap UE; is constructed at the edge of the carrier bandwidth.

Aspect 29: The method of aspect 28, wherein the BWP specific uplink parameters include one or more of a power control parameter, a frequency hopping flag, a coverage enhancement parameter, or a waveform configuration for the uplink channel.

Aspect 30: The method of aspects 28 or 29, wherein receiving BWP specific uplink parameters includes receiving a configuration of an active uplink BWP for a RedCap UE.

Aspect 31: The method of aspect 28 or 29, wherein receiving BWP specific uplink parameters includes receiving a BWP switching command.

Aspect 32: The method of aspects 28 or 29, wherein receiving BWP specific uplink parameters includes receiving a system information update specific to the RedCap UE.

Aspect 33: A method of supporting reduced functionality user equipment (RedCap UE) comprising: a cell-defined synchronization signal block (CD-SSB) defining a shared initial downlink bandwidth portion (BWP) for RedCap UE and non-RedCap UE. transmitting; transmitting a non-CD-SSB for a separate initial downlink BWP for the RedCap UE; Configuring an active downlink BWP for the RedCap 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, separate initial downlink BWP, or active downlink BWP as indicated by the paging PDCCH.

Aspect 34: The method of aspect 33, further comprising transmitting an indication of whether the initial downlink BWP for obtaining updated system information is a shared initial BWP or a separate initial downlink BWP.

Aspect 35: The method of aspect 34, wherein the indication is presence of system information of a separate initial downlink BWP, radio network temporary identifier (RNTI) scrambling of the cyclic redundancy check (CRC) of the paging PDCCH, BWP identifier of the paging PDCCH, paging. It is either a DMRS configuration of the PDCCH, or a paging opportunity configuration of the paging PDCCH.

Aspect 36: The method of aspect 33, wherein the paging PDCCH schedules a broadcast or multicast physical downlink shared channel (PDSCH) carrying updated system information on an active downlink BWP for a RedCap UE.

Aspect 37: The method of aspect 36, wherein the paging PDCCH comprises radio network temporary identifier (RNTI) scrambling of a cyclic redundancy check (CRC) of the paging PDCCH, a BWP identifier of the paging PDCCH, DMRS configuration of the paging PDCCH, or paging of the paging PDCCH. Indicates the PDSCH on the active downlink BWP for the RedCap UE through one of the opportunistic configurations.

Aspect 38: The method of aspect 36 or 37, wherein the broadcast or multicast PDSCH is scrambled by a group radio network temporary identifier (RNTI) that is a function of a cell ID, BWP ID, or group-common parameter.

Aspect 39: The method of any of aspects 33 to 38, wherein the paging search space is constructed jointly or separately with the wake-up signal search space.

Aspect 40: The method of aspect 33, wherein the paging search space is not configured on an active downlink BWP for the RedCap UE, and transmitting the updated system information comprises transmitting a paging PDCCH on a separate initial downlink BWP. Includes.

Aspect 41: The method of any of aspects 33-40, further comprising transmitting an indication of a measurement resource on one of an active downlink BWP, a separate initial downlink BWP, or a shared initial downlink BWP.

Aspect 42: The method of aspect 41, wherein the measurement resource is one or more of a synchronization signal block (SSB), a channel state information reference signal (CSI-RS), or a positioning reference signal (PRS).

Aspect 43: The method of aspect 41 or 42, wherein the measurements comprise reference signal received power (RSRP), reference signal received quality (RSRQ), signal to interference plus noise ratio (SINR), signal to noise ratio (SNR), or a combination thereof. Tier 3 measures include:

Aspect 44: The method of any of aspects 41 to 43, wherein the configuration of the active downlink BWP for the RedCap UE includes system information of the neighboring cell to be measured.

Aspect 45: The method of any of Aspects 33-44, wherein the configuration of the active downlink BWP for the RedCap UE measures the CD-SSB of the shared initial downlink BWP and the non-CD-SSB of the separate initial downlink BWP. Includes different measurement gaps for:

Aspect 46: The method of aspect 45, further comprising transmitting an indication of the absolute transmit power of the CD-SSB of the shared initial downlink BWP and the differential transmit power of the non-CD-SSB of the separate initial downlink BWP. do.

Aspect 47: The method of any of aspects 33-46, further comprising transmitting an indication that all neighboring cells transmit system information on a separate initial BWP for the RedCap UE, which may result in an RRC reset or redirection. It can be used as a fallback BWP for RRC releases.

Aspect 48: A method of supporting reduced functionality user equipment (RedCap UE) comprising: a cell-defined synchronization signal block (CD-SSB) defining a shared initial downlink bandwidth portion (BWP) for RedCap UE and non-RedCap UE. transmitting; transmitting non-CD-SSB for separate initial downlink BWPs for RedCap UEs and separate initial uplink BWPs for RedCap UEs; and transmitting BWP specific uplink parameters for the initial uplink BWP for the RedCap UE or the active uplink BWP for the RedCap UE, wherein the initial uplink BWP for the RedCap UE and the active uplink BWP for the RedCap UE are: is constructed at the edge of the carrier bandwidth.

Aspect 49: The method of aspect 48, wherein the BWP specific uplink parameters include one or more of a power control parameter, a frequency hopping flag, a coverage enhancement parameter, or a waveform configuration for an uplink channel.

Aspect 50: The method of aspects 48 or 49, wherein transmitting BWP specific uplink parameters transmits a configuration reception of an active uplink BWP for the RedCap UE.

Aspect 51: The method of aspect 48 or 49, wherein transmitting the BWP specific uplink parameter includes transmitting a BWP switching command.

Aspect 52: The method of aspects 48 or 49, wherein receiving BWP specific uplink parameters includes transmitting a system information update specific to the RedCap UE.

Aspect 53: The method of any of aspects 1 to 52, wherein the maximum bandwidth of the RedCap UE is lower than the maximum bandwidth of the non-RedCap UE.

Aspect 54: A device for wireless communication comprising: a transceiver; Memory that stores computer executable instructions; and a processor coupled with the transceiver and the memory and configured to execute computer-executable instructions to perform the methods of any one of aspects 1-32.

Aspect 55: An apparatus for wireless communication, comprising means for performing the method of any one of aspects 1 to 32.

Aspect 56: A non-transitory computer-readable medium storing computer-executable code, wherein the code, when executed by a processor, causes the processor to perform the method of any of aspects 1-32.

Aspect 57: An apparatus for wireless communication, comprising: a transceiver; Memory that stores computer executable instructions; and a processor coupled with the transceiver and the memory and configured to execute computer-executable instructions to perform the method of any one of aspects 33-52.

Aspect 58: An apparatus for wireless communication, comprising means for performing the method of any one of aspects 33 to 52.

Aspect 59: A non-transitory computer-readable medium storing computer-executable code, wherein the code, when executed by a processor, causes the processor to perform the method of any of aspects 33-52.

Aspect 60: A method comprising: a cell defining a shared initial downlink bandwidth portion (BWP) for a first type of user equipment (UE) and a second type of UE having a smaller maximum BWP size than the first type of UE- Receiving a definition synchronization signal block (CD-SSB); switching to a separate initial downlink BWP for a second type of UE; accessing the cell via a separate initial downlink BWP; Receiving configuration of an active downlink BWP for a 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.

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

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

Aspect 63: A method comprising: a cell defining a shared initial downlink bandwidth portion (BWP) for a first type of user equipment (UE) and a second type of UE having a smaller maximum BWP size than the first type of UE- transmitting a definition synchronization signal block (CD-SSB); transmitting a non-CD-SSB for a separate initial downlink BWP for the UE of a 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 updated system information on the shared initial downlink BWP, separate initial downlink BWP, or active downlink BWP as indicated by the paging PDCCH.

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

Aspect 65: The method of any of aspects 59 to 64, wherein the maximum BWP size for a first type of UE is greater than or equal to the size of the shared initial downlink BWP.

Aspect 66: The method of any of Aspects 59-65, wherein the maximum BWP size for a second type of UE is less than the size of the shared initial downlink BWP.

Aspect 67: The method of aspect 66, wherein the UE of the second type only receives signaling for the control resource set (CORESET) of the shared initial downlink BWP.

As used herein, a phrase referring to “at least one of” a list of items refers to any combination of those items, including a single member. For example, “at least one of a, b, or c” is intended to include a, b, c, a-b, a-c, b-c, and a-b-c.

The various illustrative logic, logical blocks, modules, circuits, and algorithmic processes described in connection with implementations disclosed herein may be implemented in electronic hardware, computer software, or a combination of the two. The interchangeability of hardware and software has been generally described in terms of functionality and illustrated by the various example components, blocks, modules, circuits, and processes described above. Whether this functionality is implemented in hardware or software depends on the specific application and design constraints imposed on the overall system.

The hardware and data processing devices used to implement the various illustrative logic, logic blocks, modules and circuits described in connection with the aspects disclosed herein include general-purpose single or multi-chip processors, digital signal processors (DSPs), and ), application specific integrated circuit (ASIC), field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware component or functionality described herein. It may be implemented or performed as any combination thereof designed to perform. 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, a plurality of microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration. In some implementations, particular processes and methods may be performed by circuitry specific to a given function.

In one or more aspects, the functionality described may be implemented in hardware, digital electronic circuitry, computer software, firmware, including the structures disclosed herein and structural equivalents thereof, or any combination thereof. Implementations of the subject matter described herein may also be implemented as one or more computer programs, i.e., one or more computer program instruction modules encoded on a computer storage medium for execution by or to control the operation of a data processing device. You can.

If implemented in software, the functions may be stored or transmitted as one or more instructions or code in a computer-readable medium. The processes of the methods or algorithms disclosed herein may be implemented as processor-executable software modules that may reside on a computer-readable medium. Computer-readable media includes both computer storage media and communication media, including any medium that can transmit a computer program from one place to another. A storage medium can be any available medium that can be accessed by a computer. By way of example, and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or storage of desired program code in the form of instructions or data structures. and may include any other media that can be accessed by a computer. Additionally, any connection may properly be termed a computer-readable medium. Disk and disc as used herein include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc. Disks generally reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media. Additionally, the operations of a method or algorithm may reside as one or any combination or set of codes and instructions on a machine-readable medium and computer-readable medium that may be incorporated into a computer program product.

Various modifications to the implementations described in this disclosure 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 the disclosure. Accordingly, the claims are not intended to be limited to the implementations shown herein but are to be accorded the widest scope consistent with the disclosure, the principles and novel features disclosed herein.

Additionally, those skilled in the art will recognize that the terms "top" and "bottom" are sometimes used to facilitate the description of the drawings and refer to relative positions corresponding to the orientation of the drawings on a properly oriented page, and to refer to any of the features implemented. It will be readily appreciated that this may not reflect the proper orientation of the device.

Certain features described herein in the context of separate implementations 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 in multiple implementations separately or in any suitable sub-combination. Additionally, although features may be described above and initially claimed to function in certain combinations, one or more features from a claimed combination may in some cases be deleted from the combination, and the claimed combination may be a sub-combination. Or it may be about a variation of a sub-combination.

Similarly, although operations are depicted in the drawings in a particular order, this should not be construed as requiring that these operations be performed in the particular order or sequential order shown or that all of the illustrated operations be performed to achieve the desired results. do. Additionally, the drawings may schematically depict one or more example processes in the form of a flow diagram. However, other operations not depicted may be incorporated into the example processes schematically illustrated. For example, one or more additional actions may be performed before, after, concurrently with, or in between any illustrated actions. In certain situations, multitasking and parallel processing may be advantageous. Additionally, the separation of various system components in the above-described implementations should not be construed as requiring such separation in all implementations, and the program components and systems described will generally be integrated together into a single software product or packaged into multiple software products. It must be understood that it can be done. Additionally, other implementations are within the scope of the following claims. In some cases, the actions recited in the claims can be performed in a different order and still achieve the desired result.

Claims (30)

A device for wireless communication for reduced capability (RedCap) user equipment (UE),
transceiver;
memory storing computer-executable instructions; and
A processor coupled to the transceiver and the memory, the processor comprising:
Receive a cell-defining synchronization signal block (CD-SSB) defining a shared initial downlink bandwidth part (BWP) for RedCap UEs and non-RedCap UEs;
Switching to a separate initial downlink BWP for RedCap UEs;
access a cell via the separate initial downlink BWP;
Receive configuration of active downlink BWP for RedCap UEs; and
and execute the computer-executable instructions to determine whether to switch from the active downlink BWP to the shared initial BWP or to the separate initial downlink BWP to obtain information. A device for communication. According to paragraph 1,
The configuration of the active downlink BWP for RedCap UEs includes a paging search space, and determines whether to switch to the shared initial BWP or to the separate initial downlink BWP to obtain the information. An apparatus for wireless communication to reduced function user equipment, wherein the processor is configured to receive a paging physical downlink control channel (PDCCH) indicating that system information has been updated. According to paragraph 2,
To determine whether to switch to the shared initial BWP or to the separate initial downlink BWP to obtain the information, the processor may switch from the active downlink BWP to the shared initial BWP or Apparatus for wireless communication for reduced functionality user equipment, configured to switch to the separate initial downlink BWP. According to paragraph 2,
To determine whether to switch to the shared initial BWP or to the separate initial downlink BWP to obtain the information, the processor updates scheduled by the paging PDCCH on the active downlink BWP for RedCap UEs. An apparatus for wireless communication to reduced function user equipment, configured to decode a broadcast or multicast physical downlink shared channel (PDSCH) carrying system information. According to paragraph 2,
wherein the paging search space is configured jointly or separately with a wake-up signal search space. According to paragraph 2,
The RedCap UE operates with half-duplex frequency domain duplexing (HD-FDD) on the active downlink BWP, and receiving the paging search space provides paging opportunities semi-statically or dynamically. An apparatus for wireless communications to reduced-capability user equipment, where uplink transmissions are prioritized if they overlap with configured uplink transmissions. According to paragraph 1,
A paging search space is not configured on the active downlink BWP for RedCap UEs, and to determine whether to switch to the shared initial BWP or to the separate initial downlink BWP to obtain information, the processor and switching to the separate initial downlink BWP to receive a paging PDCCH. According to paragraph 1,
To determine whether to switch to the shared initial BWP or to the separate initial downlink BWP to obtain information, the processor determines whether to switch to the active downlink BWP, the separate initial downlink BWP, or the shared initial downlink BWP. An apparatus for wireless communication to a reduced-function user equipment, configured to determine whether to switch to perform measurements based on an indication of a measurement resource on one of the devices. According to clause 8,
The measurement resource is one or more of a synchronization signal block (SSB), a channel state information reference signal (CSI-RS), or a positioning reference signal (PRS), for a reduced-function user. A device for wireless communication to equipment. According to clause 8,
The measurements include reference signal received power (RSRP), reference signal received quality (RSRQ), signal to interference plus noise ratio (SINR), and signal to noise ratio (SNR). A device for wireless communications to reduced-function user equipment, Layer 3 measurements including signal to noise ratio (signal to noise ratio) or a combination thereof. According to clause 8,
wherein the measurements include neighboring cell measurements based on system information of neighboring cells received in the configuration of the active downlink BWP for RedCap UEs. According to paragraph 1,
The configuration of the active downlink BWP for 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 BWP. Reduced functionality A device for wireless communication to user equipment. According to paragraph 1,
To determine whether to switch to the shared initial BWP or to the separate initial downlink BWP to obtain information, the processor may fallback to RRC release with RRC reset or redirection. An apparatus for wireless communication to reduced function user equipment, configured to determine a BWP. A method in a reduced functionality user equipment (RedCap UE), comprising:
Receiving a cell-defined synchronization signal block (CD-SSB) defining a shared initial downlink bandwidth portion (BWP) for RedCap UEs and non-RedCap UEs;
switching to a separate initial downlink BWP for RedCap UEs;
accessing a cell via the separate initial downlink BWP;
Receiving configuration of active downlink BWP for RedCap UEs; and
Determining whether to switch from the active downlink BWP to the shared initial BWP or to the separate initial downlink BWP to obtain information. According to clause 14,
The configuration of the active downlink BWP for RedCap UEs includes a paging search space, and determining whether to switch to the shared initial BWP or to the separate initial downlink BWP to obtain the information includes the system A method in a reduced functionality user equipment comprising receiving a paging physical downlink control channel (PDCCH) indicating that information has been updated. According to clause 15,
Determining whether to switch to the shared initial BWP or to the separate initial downlink BWP may include switching from the active downlink BWP to the shared initial BWP or the separate initial BWP to obtain updated system information. A method in a reduced functionality user equipment comprising switching to an initial downlink BWP. According to clause 14,
Determining whether to switch to the shared initial BWP or to the separate initial downlink BWP to obtain information comprises: A method in a reduced functionality user equipment, comprising determining whether to switch to perform measurements based on an indication of a measurement resource. According to clause 17,
The method of claim 1 , wherein the measurement resource is one or more of a synchronization signal block (SSB), a channel state information reference signal (CSI-RS), or a positioning reference signal (PRS). According to clause 18,
The reduced-function user equipment, wherein the measurements are layer 3 measurements including reference signal received power (RSRP), reference signal received quality (RSRQ), signal-to-interference-plus-noise ratio (SINR), signal-to-noise ratio (SNR), or a combination thereof. method in. According to clause 18,
wherein the measurements include neighboring cell measurements based on system information of neighboring cells received in the configuration of the active downlink BWP for RedCap UEs. According to clause 14,
The configuration of the active downlink BWP for 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 BWP. How to reduce functionality on user equipment. According to clause 14,
Deciding whether to switch to the shared initial BWP or to a separate initial downlink BWP to obtain information includes determining a fallback BWP for RRC release with RRC reset or redirection. Method on equipment. A device for a base station to support reduced-function user equipment (RedCap UE),
transceiver;
memory storing computer-executable instructions; and
A processor coupled to the transceiver and the memory, the processor comprising:
transmit a cell-defined synchronization signal block (CD-SSB) that defines a shared initial downlink bandwidth portion (BWP) for RedCap UEs and non-RedCap UEs;
transmit non-CD-SSB for a separate initial downlink BWP for RedCap UEs;
configure an active downlink BWP for the RedCap UE including a paging search space;
transmit a paging physical downlink control channel (PDCCH) indicating that system information has been updated; and
configured to execute the computer-executable instructions 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. Device for base stations to support user equipment. 24. The user equipment of claim 23, wherein the processor is further configured to transmit an indication of a measurement resource on one of the active downlink BWP, the separate initial downlink BWP, or the shared initial downlink BWP. A device for a base station to do this. 25. The apparatus of claim 24, wherein the measurement resource is one or more of a synchronization signal block (SSB), a channel state information reference signal (CSI-RS), or a positioning reference signal (PRS). . According to clause 24,
The reduced-function user equipment, wherein the measurements are layer 3 measurements including reference signal received power (RSRP), reference signal received quality (RSRQ), signal-to-interference-plus-noise ratio (SINR), signal-to-noise ratio (SNR), or a combination thereof. A device for a base station to support. According to clause 23,
The configuration of the active downlink BWP for the RedCap UE includes system information of neighboring cells to be measured. According to clause 23,
The configuration of the active downlink BWP for 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 BWP. Device for base stations to support reduced user equipment. According to clause 23,
further comprising transmitting an indication that all neighboring cells are transmitting system information on the separate initial BWP for RedCap UEs, which can be used as a fallback BWP for RRC release with RRC reset or redirection. Devices for base stations to support equipment. As a method of supporting reduced functionality user equipment (RedCap UE),
Transmitting a cell-defined synchronization signal block (CD-SSB) defining a shared initial downlink bandwidth portion (BWP) for RedCap UEs and non-RedCap UEs;
Transmitting non-CD-SSB for a separate initial downlink BWP for RedCap UEs;
configuring an active downlink BWP for the RedCap UE including a paging search space;
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 paging PDCCH.

Images