Managing reduced-capability user equipment

Abstract

This document describes methods, devices, systems, and means for managing a reduced-capability user equipment (UE) by a distributed base station. A Distributed Unit (DU) of the base station performs a random access procedure with the UE (504). The DU receives a Media Access Control (MAC) Protocol Data Unit (PDU) from the UE in the random access procedure (545), the MAC PDU including a logical channel identifier (LCID) and a message. The DU includes the received message in a DU-to-CU message and identifies a value of the LCID (550), the value being a first value, a second value, or a third value. If the identified value is a first value, the DU includes an indication of a first-type of UE in the DU-to-CU message and transmits the DU-to-CU message to a Central Unit (CU) (555). If the identified value is the second value, the DU includes an indication of a second-type of UE in the DU-to-CU message and transmits the DU-to-CU message to the CU (555).

Description

MANAGING REDUCED-CAPABILITY SER EQUIPMENTBACKGROUND

[0001] The evolution of wireless communication to fifth generation (5G) standards and technologies provides higher data rates and greater capacity-, with improved reliability and lower latency that enhances mobile broadband services. 5G technologies also provide new classes of sendees for vehicular networking, fixed wireless broadband, and the Internet of Things (loT). 5G distributed base station architecture refers to the network design where base stations are deployed in a distributed manner to enhance coverage, capacity, and efficiency through a combination of Central Units (CUs) that control multiple distributed units (DUs). The CU handles higher-level functions like resource allocation and management, while DUs handle low er-level tasks such as signal processing and radio transmission.

[0002] A unified air interface, which utilizes licensed, unlicensed, and shared license radio spectrum in multiple frequency bands is one aspect of enabling the capabilities of 5G systems. The 5G air interface utilizes radio spectrum in bands below 1 GHz (sub-gigahertz), below 6 GHz (sub-6 GHz), and above 6 GHz. Radio spectrum above 6 GHz includes millimeter wave (mmWave) frequency bands that provide wide channel bandwidths to support higher data rates for wireless broadband. Another aspect of enabling the capabilities of 5G systems is the use of Multiple Input Multiple Output (MIMO) antenna systems to beamform signals transmitted between base stations and user equipment to increase the capacity of 5G radio networks.

[0003] Normal-capability- user equipment (UE) may coexist with reduced-capability- UEs. Compared to normal-capability UEs, reduced-capability UEs (also referred to as RedCap UEs) tend to have a lower bandwidth capability, a reduced processing capability, and / or few er antennas. RedCap UEs also, depending on the device, lack support for dual connectivity and / or carrier aggregation. RedCap UEs have been established yvith a framework for enabling reduced- capability- NR devices suitable for a range of use cases, including industrial sensors, video surveillance, and wearables, with requirements on low UE complexity and sometimes also on low UE power consumption. In addition to RedCap UEs there are UEs with further-reduced capabilities (fRedCap UEs). There are opportunities for establishing netyvork access to a UE that is a normal-capability- UE, a RedCap UE, or a fRedCap UE.SUMMARY

[0004] This summary is provided to introduce simplified concepts of managing reduced- capability- user equipment. The simplified concepts are further described below in the DetailedDescription. This summary is not intended to identify essential features of the claimed subject matter, nor is it intended for use in determining the scope of the claimed subject matter.

[0005] In aspects, methods, devices, systems, and means for managing a reduced- capability user equipment (UE) by a distributed unit (DU) of a base station describes the DU performing a random access procedure with the UE. The DU receives a Media Access Control (MAC) Protocol Data Unit (PDU) from the UE in the random access procedure, the MAC PDU including a logical channel identifier (LCID) and a message. The DU includes the received message in a DU-to-CU message and identifies a value of the LCID, the value being a first value, a second value, or a third value. If the identified value is a first value, the DU includes an indication of a first-type of UE in the DU-to-CU message and transmits the DU-to-CU message to a Central Unit (CU). If the identified value is the second value, the DU includes an indication of a second-type of UE in the DU-to-CU message and transmits the DU-to-CU message to the CU.

[0006] In another aspect, methods, devices, systems, and means for managing a reduced- capability user equipment (UE) by a central unit (CU) of a base station describes the CU receiving first information for a first cell from the first Distributed Unit (DU). Based on the first cell allowing user equipments (UEs) of a first UE type to access the first cell and, based on the first information, the CU generates first configuration information for configuring UEs of the first UE type to measure and / or access the first cell. The CU receives second information for the first cell from the first DU and, based on the first cell allowing UEs of a second UE type to access the first cell and based on the second information, the CU generates second configuration information for configuring UEs of the second UE type to measure and / or access the first cell.BRIEF DESCRIPTION OF THE DRAWINGS

[0007] The details of one or more aspects of managing reduced-capability user equipment are described below. The use of the same reference numbers in different instances in the description and the figures may indicate like elements:FIG. 1 illustrates an example wireless network system in which various aspects of managing reduced-capability user equipment can be implemented.FIG. 2 illustrates an example device diagram that can implement various aspects of managing reduced-capability user equipment.FIG. 3 illustrates an example block diagram of a wireless network stack model in accordance with one or more aspects of managing reduced-capability user equipment.FIG. 4 illustrates an example wireless network protocol stack in which various aspects of managing reduced-capability user equipment can be implemented.FIG. 5 illustrates an example of data and control transactions between devices in accordance with one or more aspects of managing reduced-capability user equipment.FIG. 6 illustrates an example of data and control transactions between devices in accordance with one or more aspects of managing reduced-capability user equipment.FIG. 7 illustrates an example of data and control transactions between devices in accordance with one or more aspects of managing reduced-capability user equipment.FIG. 8 illustrates an example of data and control transactions between devices in accordance with one or more aspects of managing reduced-capability user equipment.FIG. 9 illustrates an example of data and control transactions between devices in accordance with one or more aspects of managing reduced-capability user equipment.FIG. 10 illustrates an example of data and control transactions between devices in accordance with one or more aspects of managing reduced-capability user equipment.FIG. 11 illustrates an example method of identifying UEs supported by a cell in accordance with one or more aspects of managing reduced-capability user equipment.FIG. 12 illustrates an example method of identifying UEs supported by a cell in accordance with one or more aspects of managing reduced-capability user equipment.FIG. 13 illustrates an example method of identifying UEs supported by a cell in accordance with one or more aspects of managing reduced-capability user equipment.FIG. 14 illustrates an example method of identifying UEs supported by a cell in accordance with one or more aspects of managing reduced-capability user equipment.FIG. 15 illustrates an example method of a base station distributed unit to allow access to multiple types of UEs in accordance with one or more aspects of managing reduced- capability user equipment.FIG. 16 illustrates an example method of a base station distributed unit to allow access to multiple types of UEs in accordance with one or more aspects of managing reduced- capability user equipment.FIG. 17 illustrates an example method of generating configurations by a DU in accordance with one or more aspects of managing reduced-capability user equipment.FIG. 18 illustrates an example method of generating configurations by a DU in accordance with one or more aspects of managing reduced-capability user equipment.FIG. 19 illustrates an example method of generating configurations by a CU in accordance with one or more aspects of managing reduced-capability user equipment.FIG. 20 illustrates an example method of generating configurations by a CU in accordance with one or more aspects of managing reduced-capability user equipment.FIG. 21 illustrates an example method of generating configurations by a RAN node in accordance with one or more aspects of managing reduced-capability user equipment.FIG. 22 illustrates an example method of generating configurations by a RAN node in accordance with one or more aspects of managing reduced-capability user equipment.DETAILED DESCRIPTION

[0008] This document describes methods, devices, systems, and means for identifying configurations for connections between a Radio Access Network (RAN) and UEs of various levels of capability. In telecommunication systems, the Packet Data Convergence Protocol (PDCP) sublayer of the wireless network protocol stack provides services such as transfer of user-plane data, ciphering, integrity protection, and the like. For example, the PDCP layer defined for the Evolved Universal Terrestrial Radio Access (EUTRA) radio interface and New Radio (NR) provides sequencing of protocol data units (PDUs) in the uplink (UL) direction (from a user device, also known as a user equipment (UE), to a base station) as well as in the downlink (DL) direction (from the base station to the UE). Further, the PDCP sublayer provides sendees for signaling radio bearers (SRBs) to the Radio Resource Control (RRC) sublayer. The PDCP sublayer also provides services for data radio bearers (DRBs) to a Service Data Adaptation Protocol (SDAP) sublayer or a protocol layer such as an Internet Protocol (IP) layer, an Ethernet protocol layer, and an Internet Control Message Protocol (ICMP) layer. Generally speaking, the UE and a base station use SRBs to exchange RRC messages as well as non-access stratum (NAS) messages and use DRBs to transport data on a user plane.

[0009] Base stations that operate according to modem requirements support significantly larger bandwidth than base stations that operate according to older requirements. Accordingly, modem normal-capability UEs can support a 100 MHz bandwidth in frequency range 1 (FR1) and a 400 MHz bandwidth in a frequency range 2 (FR2). However, normal-capability UEs may coexist with reduced-capability UEs of multiple types such as RedCap and fRedCap. A distributed base station with DU and CU components can use a variety of approaches to distinguish between these three types of UEs.Example Environment

[0010] FIG. 1 illustrates an example environment 100 which includes a user equipment 110 (UE 110) that can communicate with base stations 120 (illustrated as base stations 121 and 122) through one or more wireless communication links 130 (wireless link 130), illustrated as wireless links 131 and 132. For simplicity, the UE 110 is implemented as a smartphone but may be implemented as any suitable computing or electronic device, such as a mobile communicationdevice, modem, cellular phone, gaming device, navigation device, media device, laptop computer, desktop computer, tablet computer, smart appliance, vehicle-based communication system, or an Intemet-of-Things (loT) device such as a sensor or an actuator. The base stations 120 (e.g., an Evolved Universal Terrestrial Radio Access Network Node B, E-UTRAN Node B, evolved Node B, eNodeB, eNB. Next Generation Node B, gNode B, gNB, ng-eNB, or the like) may be implemented in a macrocell, microcell, small cell, picocell, distributed base station, and the like, or any combination or future evolution thereof. Although the base station icons represent terrestrial networks (TNs), the base stations 120 may be implemented using non-terrestrial network (NTN) elements such as satellite gateways, satellites, planes, drones, and other high altitude platforms (HAPS). Nothing herein should be construed to be limited to current wireless standards and associated network elements.

[0011] The base stations 120 communicate with the user equipment 110 using the wireless links 131 and 132, which may be implemented as any suitable type of wireless link. The wireless links 131 and 132 include control and data communication, such as downlink of data and control information communicated from the base stations 120 to the user equipment 110, uplink of other data and control information communicated from the user equipment 110 to the base stations 120, or both. The wireless links 130 may include one or more wireless links (e.g., radio links) or bearers implemented using any suitable communication protocol or standard, or combination of communication protocols or standards, such as 3rd Generation Partnership Project Long-Term Evolution (3GPP LTE), Fifth Generation New Radio (5GNR), and so forth. Multiple wireless links 130 may be aggregated in a carrier aggregation to provide a higher data rate for the UE 110. Multiple wireless links 130 from multiple base stations 120 may be configured for Coordinated Multipoint (CoMP) communication with the UE 110, as well as dual connectivity, such as single- RAT LTE-LTE or NR-NR dual connectivity or Multi-Radio Access Technology (Multi-RAT) Dual Connectivity (MR-DC). MR-DC includes E-UTRA-NR Dual Connectivity (EN-DC), NG- RAN E-UTRA-NR Dual Connectivity (NGEN-DC), and NR-E-UTRA Dual Connectivity (NE- DC).

[0012] The base stations 120 are collectively a Radio Access Network 140 (e.g., RAN, Evolved Universal Terrestrial Radio Access Network, E-UTRAN, 5G NR RAN or NR RAN). The base stations 121 and 122 in the RAN 140 are connected to a 5G core network 150 (5GC 150). The base stations 121 and 122 connect, at 101 and 102 respectively, to the 5GC 150 through an NG interface for control-plane signaling. The base stations 121, 122 connect, at 101 and 102 respectively, to the 5G core network 150 through an NG2 interface for control-plane signaling and use an NG3 interface for user-plane data communications.

[0013] The 5GC 150 includes an Access and Mobility Management Function 152 (AMF 152), which provides control-plane functions, such as registration and authentication of multiple UE 110, authorization, and mobility management in the 5G NR network. The AMF 152 communicates with the base stations 120 in the RAN 140 and also communicates with multiple UE 110, using the base stations 120.

[0014] The base station 121 is illustrated as a non-distributed base station and the base station 122 is illustrated as a distributed base station implemented using a central node-distributed node architecture. The base station 122 includes agNB-Central Unit (gNB-CU) 160 and multiple gNB Distributed-Units (gNB-DU) 170, illustrated as gNB-DU 171 and 172. Although two gNB- DUs 170 are illustrated for the sake of clarity in FIG. 1, any suitable number of gNB-DUs can interface to the gNB-CU 160.

[0015] The base stations 121 and 122 can communicate using an Xn Application Protocol (XnAP) through an Xn interface, at 103, to exchange user-plane and control-plane data. The base stations 121 and 122 communicate through an Xn-C interface at 103 for control-plane communications. In the base station 122, implemented using the central node-distributed node architecture, the Xn-C interface 103 is terminated by the gNB-CU 160.

[0016] In the central node-distributed node architecture, the gNB-CU 160 is a logical node hosting a Radio Resource Control (RRC) layer, a Service Data Adaptation Protocol (SDAP) layer, and a Packet Data Convergence Protocol (PDCP) layer protocol of the gNB or the RRC layer and the PDCP layer entities of an en-gNB (e.g., a gNB connected to an evolved packet core). The gNB-CU 160 partially controls the operation of one or more gNB-DUs 170. The gNB-CU 160 includes an Fl interface to communicate with the gNB-DUs 170, shown at 104 and 105. Although described as logical nodes, the gNB-CU 160 and / or the gNB-DUs 170 devices may include any suitable components described with respect to the base station 120 in FIG. 3.

[0017] The gNB-DUs 170 are logical nodes hosting a Radio Link Control (RLC) layer, a Media Access Control (MAC) layer, and a physical (PHY) layer protocol of the gNB or en-gNB. The operation of the gNB-DUs 170 is partly controlled by gNB-CU 160. One gNB-CU 160 supports one or multiple cells in the RAN 140, but a single cell is only supported by a single gNB- DU 170. Each gNB-DU 170 terminates the Fl interface with the gNB-CU 160 that serves as the central unit for that gNB-DU 170. Each gNB-DU 170 connects operationally to only one gNB- CU 160. Alternatively or optionally, for resiliency in network operations, a gNB-DU 170 may be connected to multiple gNB-CUs 170 using any suitable implementation, for example, network interconnection hardware and / or software that provides failover for a gNB-DU 170 to a backup gNB-CU 160 if a primary gNB-CU 160 fails or becomes unavailable to the gNB-DU 170.Example Devices

[0018] FIG. 2 illustrates an example device diagram 200 of the UE 110. The UE 110 may include additional functions and interfaces that are omitted from FIG. 2 for the sake of clarity . The user equipment 110 includes antennas 202, a radio frequency front end 204 (RF front end 204). an LTE transceiver 206, and a 5G NR transceiver 208 for communicating with base stations 120 in the RAN 140. The RF front end 204 of the UE 110 can couple or connect the LTE transceiver 206 and the 5GNR transceiver 208 to the antennas 202 to facilitate various types of wireless communication. The antennas 202 of the UE 110 may include an array of multiple antennas that are configured similarly to or differently from each other. The antennas 202 and the RF front end 204 can be tuned to, and / or be tunable to, one or more frequency bands defined by the 3GPP LTE and 5G NR communication standards and implemented by the LTE transceiver 206 and / or the 5G NR transceiver 208. Additionally, the antennas 202, the RF front end 204, the LTE transceiver 206, and / or the 5GNR transceiver 208 may be configured to support beamforming for the transmission and reception of communications with the base stations 120. By way of example and not limitation, the antennas 202 and the RF front end 204 can be implemented for operation in sub-gigahertz bands, sub-6 GHZ bands, and / or above 6 GHz bands that are defined by the 3GPP LTE and 5G NR communication standards.

[0019] The user equipment 110 also includes processor(s) 210 and computer-readable storage media 212 (CRM 212). The processor 210 may be a single core processor or a multiple core processor composed of a variety of materials, such as silicon, polysilicon, high-K dielectric, copper, and so on. The computer-readable storage media described herein excludes propagating signals. CRM 212 may include any suitable memory or storage device such as random-access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), non-volatile RAM (NVRAM), read-only memory (ROM), or Flash memory useable to store device data 214 of the user equipment 110. The device data 214 includes user data, multimedia data, beamforming codebooks, applications, and / or an operating system of the user equipment 110, which are executable by processor(s) 210 to enable user-plane communication, control-plane signaling, and user interaction with the UE 110.

[0020] In some implementations, the CRM 212 may also include a communication manager 216. The communication manager 216 can communicate with the antennas 202, the RF front end 204, the LTE transceiver 206, and / or the 5G NR transceiver 208 to communicate using the wireless communication links 130. Based on monitoring these links, the communication manager 216 can determine to attach or reattach to a RAN 140.

[0021] FIG. 3 illustrates an example device diagram 300 of the distributed base station 122. The base station 122 may include additional functions and interfaces that are omitted from FIG. 3 for the sake of clarity.

[0022] The device diagram for the base station 122, shown in FIG. 3, is distributed across multiple network nodes or devices (e.g., the CU 160 and one or more DUs 170) and may be distributed in any fashion suitable to perform the functions described herein. The nomenclature for this split base station functionality varies and includes terms such Central Unit (CU), Distributed Unit (DU), Baseband Unit (BBU), Remote Radio Head (RRH), and / or Remote Radio Unit (RRU).

[0023] The CU 160 includes processor(s) 302 and computer-readable storage media 304 (CRM 304). The processor 302 may be a single core processor or a multiple core processor composed of a variety of materials, such as silicon, polysilicon, high-K dielectric, copper, and so on. CRM 304 may include any suitable memory or storage device such as random-access memory’ (RAM), static RAM (SRAM), dynamic RAM (DRAM), non-volatile RAM (NVRAM), read-only memory (ROM), or Flash memory useable to store device data 306 of the CU 160. The device data 306 includes network scheduling data, radio resource management data, beamforming codebooks, applications, and / or an operating system of the CU 160, which are executable by processor(s) 302 to enable communication with the user equipment 110.

[0024] CRM 304 also includes a CU manager 308. Alternately or additionally, the base CU manager 308 may be implemented in whole or part as hardware logic or circuitry integrated with or separate from other components of the CU 160. In at least some aspects, the CU manager 308 configures the DU(s) 170 for communication with the user equipment 110. as well as communication with a core network, such as the core network 150, and routing user-plane and control-plane data for joint communication. Additionally, the CU manager 308 includes a Radio Resource Control (RRC) layer, a Service Data Adaptation Protocol (SDAP) layer, and a Packet Data Convergence Protocol (PDCP) layer of the wireless network protocol stack 400.

[0025] The CU 160 includes an Fl interface 310 which the CU uses to exchange userplane and control-plane data with the DU(s) 170. The CU 160 also includes an inter-base station interface 312, such as an Xn and / or X2 interface, which the CU manager 308 configures to exchange user-plane and control-plane data between other base stations 120, to manage the communication of the base stations 120 with the user equipment 110.

[0026] The device diagram for the DU 170, shown in FIG. 3, includes antennas 352, a radio frequency front end 354 (RF front end 354), one or more LTE transceivers 356, and / or one or more 5G NR transceivers 358 for communicating with the UE 110. The RF front end 354 of the DU(s) 170 can couple or connect the LTE transceivers 356 and / or the 5G NR transceivers 358to the antennas 352 to facilitate various types of wireless communication. The antennas 352 of the DU(s) 170 may include an array of multiple antennas that are configured similarly to or differently from each other. The antennas 352 and the RF front end 354 can be tuned to, and / or be tunable to, one or more frequency band defined by the 3GPP LTE and 5G NR communication standards, and implemented by the LTE transceivers 356 and one or more 5G NR transceivers 358. Additionally, the antennas 352, the RF front end 354, the LTE transceivers 356, and / or one or more 5GNR transceivers 358 may be configured to support beamforming, such as Massive- MIMO, for the transmission and reception of communications with the UE 110.

[0027] The DU(s) 170 also include processor(s) 360 and computer-readable storage media 362 (CRM 362). The processor 360 may be a single core processor or a multiple core processor composed of a variety of materials, such as silicon, polysilicon, high-K dielectric, copper, and so on. CRM 362 may include any suitable memory or storage device such as random-access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), non-volatile RAM (NVRAM), read-only memory (ROM), or Flash memory useable to store device data 364 of the DU(s) 170. The device data 364 includes network scheduling data, radio resource management data, beamforming codebooks, applications, and / or an operating system of the DU(s) 170, which are executable by processor(s) 360 to enable communication with the user equipment 110.

[0028] CRM 362 also includes a DU manager 366. Alternately or additionally, the base DU manager 366 may be implemented in whole or part as hardware logic or circuitry integrated with or separate from other components of the DU(s) 170. In at least some aspects, the DU manager 366 configures the LTE transceivers 356 and the 5GNR transceivers 358 for communication with the user equipment 110. as well as communication with the CU 160. Additionally, the DU manager 366 may allocate air interface resources and schedule communications for the UE 110. The DU 170 includes an Fl interface 368 which the DU uses to exchange user-plane and control -plane data with the CU 160.Wireless Network Protocol Stack

[0029] FIG. 4 illustrates, in a simplified manner, an example protocol stack 400 which the UE 110 can communicate with a DU 170 and a CU 160. The radio protocol stack 400 is functionally split between the CU 160 and the DU 170. In the example stack 400, a physical layer (PHY) 402 provides hardware specifications for devices that communicate with each other. As such, the PHY layer 402 establishes how devices connect to each other, assists in managing how communication resources are shared among devices, and the like. The PHY layer 402 provides transport channels to the Media Access Control (MAC) layer 404. The MAC layer 404 specifies how data is transferred between devices. Generally, the MAC layer 404 provides a way in whichdata packets being transmitted are encoded and decoded into bits as part of a transmission protocol. The Mac layer 404, in turn provides logical channels to the RLC sublayer 406. The RLC layer 406 provides data transfer sendees to higher layers in the stack 400. Generally, the RLC layer 406 provides error correction, packet segmentation and reassembly, and management of data transfers in various modes, such as acknowledged, unacknowledged, or transparent modes.

[0030] The RLC layer 406 in turn provides RLC channels to an PDCP layer 408. The PDCP layer 408 provides data transfer sendees to higher layers in the stack 400. Generally, the PDCP layer 408 provides transfer of user plane and control plane data, header compression, ciphering, and integrity protection.

[0031] In 5G NR, the PDCP sublayer 408 in turn can provide data transfer services to a Service Data Adaptation Protocol (SDAP) layer 410. The optional SDAP layer 410 is present in 5G NR networks. The SDAP layer 410 maps a Quality7of Service (QoS) flow for each data radio bearer and marks QoS flow identifiers in uplink and downlink data packets for each packet data session.

[0032] The control plane includes a Radio Resource Control (RRC) layer 420. The RRC layer 420 establishes and releases connections and radio bearers, broadcasts system information, or performs power control. The RRC layer 420 also controls a resource control state of the UE 110 and causes the UE 110 to perform operations according to the resource control state. Example resource control states include a connected state (e.g., an RRC connected state) or a disconnected state, such as an inactive state (e.g., an RRC inactive state) or an idle state (e.g., an RRC idle state). In general, if the UE 110 is in the connected state, the connection with the base station 120 is active. In the inactive state, the connection with the base station 120 is suspended. If the UE 110 is in the idle state, the connection with the base station 120 is released. Generally, the RRC layer 420 supports 3GPP access but does not support non-3GPP access (e g., Wireless Local Area Network (WLAN) communications).Managing RedCap UEs

[0033] FIGs. 5-10 illustrate are messaging diagrams of example scenarios in which nodes of a RAN identify a capability ty pe of a UE during connection establishment. UE types may correspond to different capability types of UEs. For example, this disclosure refers to reduced- capability7UEs as a first UE type, further-reduced-capability UEs as a second UE type, and normal-capability UEs as a third UE type. Although three UE capability types are discussed throughout this disclosure, the techniques described apply to distinguishing a larger number of UE capability7types should they be defined in the future.

[0034] Turning first to FIG. 5, in a scenario 500, a base station 120 includes a CU 160 and a DU 170. In aspects, the DU 170 initiates an Fl setup procedure (502) with the CU 160 by transmitting (505) an Fl Setup Request message to the CU 1 0. In response, the CU 160 transmits (510) an Fl Setup Response message to the DU 170. Depending on the aspect, the DU 170 includes DU configuration information for one or more cells in the F 1 Setup Request message. In some aspects, the DU configuration information includes reduced-capability (RedCap) information, further-reduced-capability (fRedCap) information, configuration for normalcapability UEs, System Information Information Element(s) IE(s), and / or slice supporting information, as described below. In some aspects, the CU 160 includes CU configuration information for one or more cells in the Fl Setup Response message. The Fl Setup Request message and the Fl Setup Response message are non-UE associated signaling messages.

[0035] In further aspects, the DU 170 includes RedCap information (e.g., an IE) in the Fl Setup Request message. In some aspects, the DU 170 configures the RedCap information for a corresponding cell operated by the DU 170, and the RedCap information indicates whether RedCap UEs are allowed to access the corresponding cell. In some aspects, the RedCap UEs can be grouped into different types such as RedCap UEs with one receiving chain or antenna, RedCap UEs with two receiving chains or antennas, and RedCap UEs that support half-duplex operation. In some aspects, the RedCap information indicates which types of UEs have access to the corresponding cell. In some aspects, the CU 160 uses the RedCap information to identity’ that the corresponding cell is a suitable target cell in the case of subsequent outgoing mobility7involving RedCap UEs.

[0036] In some aspects, the RedCap infonnation is a RedCap Broadcast Information IE. In other aspects, the DU 170 includes the RedCap information in a RedCap Broadcast Information IE in the Fl Setup Request message. In some aspects, DU 170 includes multiple sets of RedCap information, one for each corresponding cell in the Fl Setup Request message. In some aspects, the multiple sets of RedCap infonnation have the same content or different contents. In some aspects, the RedCap information is specific to particular types of RedCap UEs that support particular RedCap functionalities (e g., 3GPP Release 17 RedCap UEs that support RedCap functionalities defined in 3GPP Release 17).

[0037] In some aspects, the DU 170 includes fRedCap information (e.g., an IE) in the Fl Setup Request message. This fRedCap information is different from the previously -described RedCap information. In some aspects, the DU 170 configures the fRedCap information for a corresponding cell operated by the DU 170, and the fRedCap information indicates whether fRedCap UEs are allowed to access the corresponding cell. In some aspects, the fRedCap UEs can be grouped into different types such as IRedCap UEs with one receiving chain or antenna,fRedCap UEs with two receiving chains or antennas, and fRedCap UEs that support half-duplex operation. In some aspects, the fRedCap information indicates which types of UEs have access to the corresponding cell. In some aspects, the CU 160 uses the fRedCap information to identify that the corresponding cell is a suitable target cell in the case of subsequent outgoing mobility involving fRedCap UEs.

[0038] In some aspects, the fRedCap information is a fRedCap Broadcast Information IE different from a RedCap Broadcast Information IE. In other aspects, the DU 170 includes the fRedCap infonnation in a RedCap Broadcast Information IE in the Fl Setup Request message. In such cases, the DU 170 includes RedCap information and fRedCap information in a RedCap Broadcast Information IE for the corresponding cell in the Fl Setup Request message. In some aspects, DU 170 includes multiple sets of fRedCap information, one for each corresponding cell in the Fl Setup Request message. In some aspects, the multiple sets of fRedCap information have the same content or different contents. In some aspects, the fRedCap information is specific to particular types of fRedCap UEs that support particular fRedCap functionalities (e.g., 3GPP Release 18 fRedCap UEs and support fRedCap functionalities defined in 3GPP Release 18).

[0039] In some aspects, in the Fl Setup Request message, the DU 170 includes a System Infonnation IE for a cell operated by the DU 170. In some aspects, the System Information IE includes a master information block (MIB) and / or one or more system information blocks (SIB(s)). In some aspects, the DU 170 configures the MIB and SIB(s) for normal-capability UEs, RedCap UEs, and / or fRedCap UEs. In other aspects, in the Fl Setup Request message, the DU 170 includes a first System Information IE and a second System Information IE for a cell operated by the DU 170. In some aspects, the first System Information IE includes an MIB and / or SIB(s) for normal-capability- UEs, and the second System Information IE includes an MIB and / or SIB(s) for RedCap UEs and / or fRedCap UEs. In yet other aspects, in the Fl Setup Request message, the DU 170 includes a first System Information IE, a second System Information IE, and a third System Infonnation IE for a cell operated by the DU 170. In some aspects, the first System Infonnation IE includes an MIB and / or SIB(s) for normal-capability UEs. the second System Infonnation IE includes an MIB and / or SIB(s) for RedCap UEs, and / or the third System Information IE includes an MIB and SIB(s) for fRedCap UEs. In some aspects, the SIB(s) above include a SIB1, a SIB 17, and / or a SIB20.

[0040] In some aspects, in the Fl Setup Request message, the DU 170 includes slice supporting information (e.g., an IE) for a corresponding cell operated by the DU 170. The slice supporting information indicates one or more slices supported on the corresponding cell for normal-capability UEs, RedCap UEs, and / or fRedCap UEs. In other aspects, in the Fl Setup Request message, the DU 170 includes first slice supporting infonnation (e.g., an IE) and secondslice supporting information (e.g., an IE) for a corresponding cell operated by the DU 170. The first slice supporting information indicates one or more slices supported on the corresponding cell for normal-capability UEs, and the second slice supporting information indicates one or more slices supported on the corresponding cell for RedCap UEs and / or fRedCap UEs. In yet other aspects, in the Fl Setup Request message, the DU 170 includes first slice supporting information (e.g., an IE), second slice supporting information (e.g., an IE), and third slice supporting information (e.g., an IE) for a corresponding cell operated by the DU 170. The first slice supporting information indicates one or more slices supported on the corresponding cell for nonnal-capability UEs, the second slice supporting infomiation indicates one or more slices supported on the corresponding cell for RedCap UEs, and the third slice supporting information indicates one or more slices supported on the corresponding cell for fRedCap UEs.

[0041] In some aspects, the CU configuration infomiation includes SIB(s). For example, the SIB(s) include SIB2, SIB3. SIB4, SIB5, SIB6, SIB7, SIB8, and / or SIB9. In some aspects, the CU configuration information is different for each cell.

[0042] In some aspects, the DU 170 might initiate a DU configuration update procedure with the CU 160 to update at least a portion of the DU configuration information. Upon initiating the DU configuration update procedure, the DU 170 transmits (515) a DU Configuration Update message, including new DU configuration information, to the CU 160 to update the DU configuration information included in the Fl Setup Request message. In some aspects, the new DU configuration information includes new RedCap information, new fRedCap information, new System Information IE(s), and / or new slice supporting information. In response to the DU Configuration Update message, the CU 160 transmits (520) a DU Configuration Update Acknowledge message to the DU 170. In some aspects, the CU 160 includes new CU configuration information for one or more cells in the DU Configuration Update Acknowledge message to update the CU configuration infomiation in the Fl Setup Response message. In some alternative aspects, the DU 170 transmits (515) a DU Configuration Update message to the CU 160 to include the DU configuration information or at least a portion of the DU configuration information instead of the Fl Setup Request message. In some aspects, the CU 160 includes the CU configuration information for one or more cells in the DU Configuration Update Acknowledge message, as described for the Fl Setup Response message. The DU Configuration Update message and the DU Configuration Update Acknowledge message are non-UE associated signaling messages.

[0043] In some aspects, the DU 170 performs separate procedures with the CU 160 to transmit, to the CU 160, different configuration information for normal-capability UEs, RedCap UEs, and / or fRedCap UEs. For example, the DU 170 performs a first procedure with the CU 160by transmiting a first message including first configuration information for normal-capability UEs to the CU 160. In response, the CU 1 0 transmits a second message to the DU 170. The DU 170 performs a second procedure with the CU 160 by transmiting a third message including second configuration information for RedCap UEs and / or fRedCap UEs to the CU 160. In response, the CU 160 transmits a fourth message to the DU 170. In some alternative aspects, the DU 170 performs a second procedure with the CU 160 by transmitting a third message including second configuration information for RedCap UEs to the CU 160 and performs a third procedure with the CU 160 by transmiting a fifth message including third configuration information for fRedCap UEs to the CU 160.

[0044] In some aspects, the CU 160 transmits a fourth message and a sixth message to the DU 170 in response to the third message and the fifth message, respectively. In some aspects, the procedures include Fl setup procedures and / or DU configuration update procedures. In cases where the procedures are Fl setup procedures, the first message, the third message, and / or the fifth message are F 1 Setup Request messages, and the second message, the fourth message, and / or the sixth message are Fl Setup Response messages. In cases where the procedures are DU configuration update procedures, the first message, the third message, and / or the fifth message are Fl Setup Request messages, and the second message, the fourth message, and / or the sixth message are Fl Setup Response messages.

[0045] The DU 170 periodically transmits (e.g., broadcasts) (525) system information on a cell. In some aspects, the system information includes a MIB and SIB(s). In some aspects, the DU 170 periodically transmits (525) the system information after performing the Fl setup procedure and / or the DU configuration update procedure. In further aspects, the DU 170 transmits the MIB and the SIB(s)as configured by the CU configuration information, above.

[0046] In some aspects, the UE 110 initially operates (530) in an idle state (e.g., the RRC IDLE state), an inactive state (e.g., the RRC INACTIVE state), or a connected state (e.g., the RRC CONNECTED state) with a failure (e.g., radio link failure), or, more generally, in a state in which there is no active radio connection between the UE 110 and the base station 120.

[0047] The UE 1 10 initiates a procedure to establish or restore a radio connection with the base station 120. In particular, in some aspects, the UE 110 performs a random access procedure with the DU 170. Depending on the implementation, the random access procedure is a two-step or a four-step procedure. In a four-step procedure between a UE and a DU. the UE 110 transmits (535) arandom access (RA) preamble, which is also referred to as "Msgl,” to the DU 170 (step 1); the DU 170 transmits (540) a random access response (RAR), or “Msg2,” to the UE 110 (step 2); the UE 110 transmits (545) a scheduled transmission, or “Msg3,” to the DU 170 (step 3); and the DU 170 transmits a contention resolution, or "Msg4." to the UE 110 (step 4). The scheduledtransmission includes a UL MAC PDU that includes a logical channel identity (LCID) and an RRC request.

[0048] In a two-step procedure, the UE 110 transmits (535) a random access (RA) preamble and (545) a payload, or “MsgA,” to the DU 170 (step 1), and the DU 170 transmits a contention resolution, or "MsgB. ‘ to the UE 110 (step 2). More particularly, the MsgA includes two parts sent on different occasions: the RA preamble transmitted via a physical random access channel (PRACH) occasion (e.g., similar to Msgl of the four-step procedure), and the payload transmitted via a PUSCH occasion (e.g., similar to Msg3 of the four-step procedure). The payload includes a UL MAC PDU that includes an LCID and an RRC request. In some aspects, the LCID identifies a UL logical channel for the RRC request. For example, the UL logical channel is a UL common control channel (CCCH).

[0049] In some aspects, if the UE 110 operates (530) in an idle or an inactive state, the RRC request message signals a transition to a connected state (e.g., an RRCSetupRequest message or an RRCResumeRequest message). In further aspects, if the UE 110 operates (530) in a connected state, the RRC request message instructs recover}' of a radio link failure or other failure (e.g., an RRCReestablishmentRequest message). In some aspects, the UE 110 generates a UL- CCCH-Message message, including the RRC request message, and includes the UL-CCCH- Message message in the UL MAC PDU (545). In other aspects, the UE 110 generates a UL- CCCHl-Message message, including the RRC request message, and includes the UL-CCCH1- Message message in the UL MAC PDU (545). In this description, in some aspects, the RRC request message is equivalent to the UL-CCCH-Message message or the UL-CCCH1 -Message message.

[0050] When the DU 170 receives (545) the UL MAC PDU, the DU 170 retrieves the LCID and the RRC request message from the UL MAC PDU. In some aspects, the DU 170 identifies (550) a UE type of the UE 110 based on the LCID. For example, if the LCID is a first value, the DU 170 classifies the UE 110 as a first UE type (e.g., a RedCap UE). If the LCID is a second value, the DU 170 classifies the UE 110 as a second UE type (e.g., a fRedCap UE). If the LCID is a third value, the DU 170 classifies the UE 110 as a third UE type (e.g., a normalcapability UE). For example, when the UE 110 is a fRedCap UE, the UE 110 sets the LCID to the second value and includes the LCID in the UL MAC PDU. Thereafter, the DU 170 identifies, from the LCID value, that the UE 110 is the second UE ty pe.

[0051] After classifying the UE 110 as the second UE type, the DU 170 transmits (555) a DU-to-CU message to the CU 160. The DU-to-CU message includes the RRC request and an indication of the first UE type instead of an indication of the second UE ty pe. In some aspects, the DU-to-CU message is an Initial UL RRC Message Transfer message. If the DU 170 indicates(550) the UE 1 10 as the first UE type, the DU 170 transmits (555) the DU-to-CU message to the CU 160. When the CU 160 receives (555) the DU-to-CU message, the CU 160 categorizes (560) the UE 110 as the first UE type based on the indication.

[0052] There are some benefits to the DU 170 using the same indication for UEs of the first UE type and for UEs of the second UE type. First, using the same indication simplifies UE handling in the CU 160. That is, the CU 160 manages UEs of the first UE type and UEs of the second UE type in the same way. Secondly, when the first UE type is a RedCap UE, the indication of the RedCap UE has been defined (e.g., in 3GPP Release 17). Thus, this approach avoids defining a new indication for the fRedCap UE in the DU-to-CU message (e.g., in 3GPP Release 18) and the CU 160 does not need to be updated to support fRedCap UEs separately from RedCap UEs.

[0053] In some aspects (not shown), the CU 160 transmits a BS-to-CN message to a CN (e.g., the CN 150) or an AMF (e.g., the AMF 152), including an indication of the first UE type for the UE 110. Thus, in some such aspects, the CN 150 categorizes the UE 110 as the first UE type, based on the indication of the first UE ty pe — even when the UE is not the first UE type. In some aspects, the CN 150 applies a charging policy or rate for the first UE ty pe for the UE 110 to charge data traffic communicated with the UE 110 based on the indication or categorization. In some such cases, the CN 150 applies the same charging policy or rate for the first UE type and the second UE type and applies a different charging policy or rate for the third UE type. In some aspects, the BS-to-CN message is an Initial UE Message message. In some aspects (not shown), the AMF 152 transmits a message including an indication of the first UE type to a Session Management Function (SMF) after receiving the BS-to-CN message. Thus, in some such aspects, the SMF takes proper handlings for the UE 110, based on the indication of the first UE type. For example, the SMF interacts with a User Plane Function (UPF) to manage user plane resources for the UE 110 and / or ensure that data of the UE 110 is routed and / or forw arded correctly, based on the indication of the first UE type. In another example, the SMF may transmit a SMF-to-UPF message to the UPF. including an indication of the first UE type. Thus, the UPF manages user plane resources for the UE 110 based on the indication of the first UE type.

[0054] In some aspects (not shown), if the DU 170 identifies (550) that the UE 110 is the third UE type, the DU 170 refrains from including an indication of a UE type in the DU-to-CU message (555). In other aspects (not shown), if the DU 170 identifies (550) that the UE 110 is the third UE type, the DU 170 includes an indication of the third UE ty pe in the DU-to-CU message (555).

[0055] In response to the RRC request message, the CU 160 generates an RRC response message for the UE 110 and transmits (565) a CU-to-DU message including the RRC responsemessage to the DU 170. In turn, the DU 170 transmits (570) the RRC response message to the UE 1 10. In some aspects, the DU 170 includes an LCID and the RRC response message in a DL MAC PDU and transmits (570) the DL MAC PDU to the UE 110. In some aspects, the LCID identifies a DL logical channel where the RRC response message belongs. For example, the DL logical channel is a DL common control channel (CCCH). In some aspects, the CU 160 generates a DL-CCCH-Message message, including the RRC response message, and includes the DL- CCCH-Message message in the DL MAC PDU (570). In the description herein, in some aspects, the RRC response message is equivalent to the DL-CCCH-Message message.

[0056] In some aspects, the RRC response message (565, 570) is an RRCSetup message, an RRCResume message, or an RRCReestablishment message, depending on whether the RRC request message (545) is an RRCSetupRequest message, an RRCResumeRequest message, or an RRCReestablishmentRequest message, respectively. In some aspects, the RRC response message (570) is an RRC reject message (e.g., an RRCReject message) in response to an RRCSetupRequest message or an RRCResumeRequest message. In some aspects, if the RRC response message is neither an RRC reject message nor an RRC release message, the UE 110 transitions (575) to the connected state and transmits (580) an RRC complete message to the DU 170 in response to the RRC response message. In turn, the DU 170 transmits (585) the RRC complete message to the CU 160. Depending on the implementation, the RRC complete message is an RRCSetupComplete message, an RRCResumeComplete message, or an RRCReestablishmentComplete message, in accordance with the RRC response message (570).

[0057] In some aspects, the UE 110 includes an LCID and the RRC complete message in a UL MAC PDU and transmits (545) the UL MAC PDU to the DU 170. In some aspects, the LCID identifies a UL logical channel for the RRC complete message. For example, the UL logical channel is a UL Dedicated Control Channel (DCCH). The DU 170 retrieves (550) the LCID and the RRC complete message from the UL MAC PDU and transmits (555) a DU-to-CU message including the RRC complete message to the CU 160. In some aspects, the UE 110 generates a UL-DCCH-Message message including the RRC complete message, generates a UL PDCP PDU including the UL-CCCH-Message message, generates a UL RLC PDU including the UL PDCP PDU, and includes the UL RLC PDU in the UL MAC PDU (580). In the description herein, in some aspects, the RRC complete message is equivalent to the UL-DCCH-Message message.

[0058] In some aspects, if the RRC response message is an RRC reject message or an RRC release message, the UE 110 stays in the original state as event 530 and refrains from transmitting an RRC complete message to the base station 120.

[0059] In some aspects, after identifying (550) the UE 110 as the second UE type, the DU 170 includes, in the DU-to-CU message (555), configuration parameters (e.g., a cell groupconfiguration) that the second UE type supports for the UE 110. The CU 160 includes the configuration parameters in the RRC response message. In some aspects, if the DU 170 identifies that the UE 110 is the first UE type, the DU 170 still includes, in the DU-to-CU message (555), configuration parameters that the second UE type supports for the UE 110. In such cases, the DU 170 unifies configurations of the first UE type and the second UE type. In other aspects, if the DU 170 identifies that the UE 110 is the first UE type, the DU 170 includes, in the DU-to-CU message (555), configuration parameters (e.g., a cell group configuration) that the first UE type supports for the UE 110. In such cases, the second UE type might not support the configuration parameters that the first UE type supports. In some aspects, if the DU 170 identifies that the UE 1 10 is the third UE type, the DU 170 includes, in the DU-to-CU message (555), configuration parameters (e.g., a cell group configuration) that the third UE type supports for the UE 110. In such cases, the first UE type and the second UE type might not support the configuration parameters that the third UE type supports.

[0060] In some aspects, the DU 170 generates a first downlink control information (DCI), including parameters for a UE to use for receiving downlink transmissions and transmitting uplink transmissions. In some aspects, based on the identification (550), the DU 170 generates the parameters conforming to predetermined capabilities for the second UE type. The DU 170 transmits the first DCI to the UE 110 before transmitting (570) the DL MAC PDU, such that, in some aspects, the UE 1 10 configures itself to receive (570) the DL MAC PDU in accordance with the first DCI. Likewise, in further aspects, if the DU 170 identifies that the UE 110 is the first UE type, the DU 170 generates a second DCI for the UE 110 that includes parameters that the first UE type supports. In some aspects (not shown), the base station 120 transmits the second DCI to the UE 110 before transmitting (570) the DL MAC PDU. Alternatively, if the DU 170 identifies that the UE 110 is the first UE type, the DU 170 generates a second DCI for the UE 110 that includes parameters that the second UE type supports, similar to the first DCI. The base station 120 in some aspects transmits the second DCI to the UE 110 before transmitting (570) the DL MAC PDU. Likewise, in further aspects (not shown), if the DU 170 identifies that the UE 110 is the third UE type, the DU 170 generates a third DCI for the UE 110 that includes parameters that the third UE type supports. In some aspects (not shown), the base station 120 transmits the third DCI to the UE 110 before transmitting (570) the DL MAC PDU.

[0061] In some cases, regarding the first DCI, the DU 170 includes parameters scheduling a PDSCH transmission to the UE 110 in the first DCL where the PDSCH transmission includes the DL MAC PDU (570). In some aspects, the parameters include a first time domain resource assignment field and / or a first frequency domain resource assignment field for the PDSCH transmission. In some aspects, the DU 170 sets the first time domain resource assignment field toa first value conforming to one or more predetennined capabilities for the second UE type. In further aspects, the DU 170 sets the first time domain resource assignment field to a first predetermined value. In some aspects, the DU 170 sets the first frequency domain resource assignment field to a first value conforming to the one or more predetennined capabilities for the second UE type. In further aspects, the DU 170 sets the first frequency domain resource assignment field to a first predetermined value. In such aspects, the UE 110 receives the PDSCH transmission at time domain resources (e.g., symbols) in accordance with the first time domain resource assignment field, and / or in frequency domain resources in accordance with the first frequency domain resource assignment field.

[0062] In some aspects, the DU 170 includes a first PDSCH-to-HARQ feedback timing indicator in the first DCI. In some aspects, the DU 170 sets the first PDSCH-to-HARQ feedback timing indicator to a first value conforming to the one or more predetermined capabilities for the second UE type. Thus, in some such aspects, the UE 110 transmits a HARQ feedback in accordance with the first value. In further aspects, the DU 170 sets the first PDSCH-to-HARQ feedback timing indicator to a predetermined value. Depending on the implementation, the HARQ feedback is a HARQ acknowledgement or a HARQ negative acknowledgement.

[0063] In some cases, regarding the second DCI, the DU 170 includes, in the second DCI, parameters scheduling a PDSCH transmission to the UE 110. where the PDSCH transmission includes the DL MAC PDU (570). In some aspects, the parameters include a second time domain resource assignment field and / or a second frequency domain resource assignment field for the PDSCH transmission. In some aspects, the DU 170 sets the second time domain resource assignment field to a second value conforming to the one or more predetermined capabilities for the first UE type. In further aspects, the DU 170 sets the second time domain resource assignment field to a second predetermined value. In still further aspects, the DU 170 sets the second time domain resource assignment field to the same value as the first time domain resource assignment field. In some aspects, the DU 170 sets the second frequency domain resource assignment field to a second value confomiing to the one or more predetennined capabilities for the first UE type. In further aspects, the DU 170 sets the second frequency domain resource assignment field to a second predetermined value. In still further aspects, the DU 170 sets the second frequency domain resource assignment field to the same value as the first time domain resource assignment field. In such aspects, the UE 110 (e.g.. in cases for the first UE type) receives the PDSCH transmission at time domain resources (e.g., symbols) in accordance with the second time domain resource assignment field, and / or in frequency domain resources in accordance with the second frequency domain resource assignment field.

[0064] In some aspects, the DU 170 includes a second PDSCH-to-HARQ feedback timing indicator in the second DCI. In some aspects, the DU 170 sets the second PDSCH-to-HARQ feedback timing indicator to a second value conforming to the one or more predetermined normal capabilities. For example, the second value corresponds to an earlier time resource compared to the first PDSCH-to-HARQ feedback timing indicator because the first UE type is capable of processing the PDSCH transmission more quickly than the second UE type. In some aspects, the UE 110 (e.g., in cases for the first UE type) transmits a HARQ feedback in accordance with the second value. In further aspects, the DU 170 sets the second PDSCH-to-HARQ feedback timing indicator to the same value as the first PDSCH-to-HARQ feedback timing indicator. Depending on the implementation, the HARQ feedback is a HARQ acknowledgement or a HARQ negative acknowl edgement.

[0065] In some cases, regarding the third DCI, the DU 170 includes, in the third DCI, parameters scheduling a PDSCH transmission to the UE 110 (e.g., in cases for the nornial- capability UE, the third UE type), where the PDSCH transmission includes the DL MAC PDU (570). In some aspects, the parameters include a third time domain resource assignment field and / or a third frequency domain resource assignment field for the PDSCH transmission. In some aspects, the DU 170 sets the third time domain resource assignment field to a third value conforming to the one or more predetermined capabilities for the third UE type. In further aspects, the DU 170 sets the third time domain resource assignment field to a third predetermined value. In still further aspects, the DU 170 sets the third time domain resource assignment field to the same value as the first or second time domain resource assignment field. In some aspects, the DU 170 sets the third frequency domain resource assignment field to a third value conforming to the one or more predetermined capabilities for the third UE type. In further aspects, the DU 170 sets the third frequency domain resource assignment field to a third predetermined value. In still further aspects, the DU 170 sets the third frequency domain resource assignment field to the same value as the first or second time domain resource assignment field. In such aspects, the UE 110 (e.g., in cases for the third UE type, normal-capability UE) receives the PDSCH transmission at time domain resources (e.g., symbols) in accordance with the third time domain resource assignment field, and / or in frequency domain resources in accordance with the third frequency domain resource assignment field.

[0066] In some aspects, the DU 170 includes a third PDSCH-to-HARQ feedback timing indicator in the third DCI. In some aspects, the DU 170 sets the third PDSCH-to-HARQ feedback timing indicator to a third value conforming to the one or more predetermined capabilities for the third UE ty pe. For example, the third value corresponds to an earlier time resource compared to the first or second PDSCH-to-HARQ feedback timing indicator because the third UE type iscapable of processing the PDSCH transmission more quickly than the first or second UE type. In some aspects, the UE 110 (e.g., in some cases for the third UE type) transmits a HARQ feedback in accordance with the third value. In further aspects, the DU 170 sets the third PDSCH-to-HARQ feedback timing indicator the same value as the first or second PDSCH-to-HARQ feedback timing indicator. Depending on the implementation, the HARQ feedback is a HARQ acknowledgement or a HARQ negative acknowledgement.

[0067] In some aspects, the DU 170 transmits the first DCI on a time and frequency resource. Depending on the implementation, the time and frequency resource is on a first control resource set (CORESET) or a first search space. In some aspects, the DU 170 broadcasts a first SIB on the cell, including first configuration parameters configuring the first CORESET or first search space for the second UE type. The UE 110 (e.g., in cases for the second UE type) receives the first SIB and receives the first DCI on the time and frequency resource on the first CORESET or first search space in accordance with the first configuration parameters.

[0068] In other aspects (not shown), the DU 170 transmits the second DCI on a time and frequency resource. In some aspects, the time and frequency resource is on a second CORESET or a second search space. In some aspects (not shown), the DU 170 broadcasts a second SIB on the cell, including second configuration parameters configuring the second CORESET or second search space for the first UE type. The UE 110 (e.g.. in cases for the first UE type) receives the second SIB and receives the second DCI on the time and frequency resource on the second CORESET or second search space in accordance with the second configuration parameters. Alternatively (not shown), the DU 170 transmits the second DCI on the first CORESET or first search space, such as in cases where the DU 170 configures the first CORESET or first search space for both the first UE type and second UE type.

[0069] In yet other aspects (not shown), the DU 170 transmits the third DCI on a time and frequency resource. In some aspects, the time and frequency resource is on a third CORESET or a third search space. In some aspects (not shown), the DU 170 broadcasts a third SIB on the cell, including third configuration parameters configuring the third CORESET or third search space for the third UE type. The UE 110 (e g., in cases for the third UE type) receives the third SIB and receives the third DCI on the time and frequency resource on the third CORESET or third search space in accordance with the third configuration parameters. Alternatively, the DU 170 transmits the third DCI on the second CORESET or second search space, such as in cases where the DU 170 configures the second CORESET or second search space for both the first UE type and third UE type.

[0070] In some aspects, the first, second, and / or third SIBs are the same SIB or different SIBs. In some aspects, the first, second, and / or third CORESETs are the same CORESET ordifferent CORESETs. In some aspects, the first, second, and / or third search spaces are the same search space or different search spaces.

[0071] In some aspects, the DU 170 broadcasts a SIB on the cell, including a first PUCCH configuration (e.g.. PUCCH-ConfigCommon IE) that configures PUCCH resource(s) for UEs of the second UE type. The UE 110 (e.g., in cases for the second UE type) transmits the HARQ feedback on a first PUCCH resource configured by the first PUCCH configuration. In some aspects, the UE 110 determines the first PUCCH resource based on a PUCCH resource indicator in the first DCI. Depending on the implementation, the SIB is a SIB1 or a SIB as described above.

[0072] In some aspects, the DU 170 configures the first PUCCH configuration for UEs of the first UE type. The UE 110 (e.g., in cases for the first UE type) transmits the HARQ feedback on a first PUCCH resource configured by the first PUCCH configuration. In some aspects, the UE 110 determines the first PUCCH resource based on a PUCCH resource indicator in the second DCI. In some alternative aspects, the DU 170 broadcasts a SIB on the cell, including a second PUCCH configuration (e.g., PUCCH-ConfigCommon IE) that configures PUCCH resource(s) for UEs of the first UE type. The UE 110 (e.g., in cases for the first UE type) transmits the HARQ feedback on a second PUCCH resource configured by the second PUCCH configuration. In some aspects, the UE 110 determines the second PUCCH resource based on a PUCCH resource indicator in the second DCI. Depending on the implementation, the SIB is a SIB1 or a SIB as described above.

[0073] In some aspects, the DU 170 broadcasts a SIB on the cell, including a third PUCCH configuration (e.g., PUCCH-ConfigCommon IE) that configures PUCCH resource(s) for UEs of the third type. The UE 110 (e.g., in cases for the third UE type) transmits the HARQ feedback on a third PUCCH resource configured by the third PUCCH configuration. In some aspects, the UE 110 determines the third PUCCH resource according to a PUCCH resource indicator in third DCI. Depending on the implementation, the SIB is a SIB1 or a SIB as described above.

[0074] In some aspects, the PUCCH resource(s) configured in the first, second, and / or third PUCCH configurations are exclusive. In other aspects, one or more of the PUCCH resource(s) configured in the first, second, and / or third PUCCH configurations are the same. Depending on the implementation, the remainder in the first, second, and / or third PUCCH configurations is the same or different. In such cases, the DU 170 does not configure more than one UE to transmit HARQ feedback on the same PUCCH resource in the same time instance.

[0075] In other aspects, the base station 120 broadcasts a SIB including a PUCCH configuration (e.g., PUCCH-ConfigCommon IE) that configures PUCCH resource(s) for UEs of the first UE type, the second UE type, and the third UE type. In such cases, the DU 170 does not configure more than one UE to transmit HARQ feedback on the same PUCCH resource in thesame time instance. The UE 110 transmits the HARQ feedback on a PUCCH resource configured by the PUCCH configuration. In some aspects, the UE 110 determines the PUCCH resource according to a PUCCH resource indicator in first DCI. Depending on the implementation, the SIB is an SIB1 or a SIB as described above.

[0076] In some aspects, the DU 170 configures a DL bandwidth part (BWP) and a UL BWP of the cell for communication with UEs of the first UE type, the second UE type, or the third UE type. In some aspects, the DU 170 broadcasts a SIB on the cell, including a DL BWP configuration and a UL BWP configuration configuring the DL BWP and the UL BWP, respectively. Depending on the implementation, the SIB is a SIB1 or a SIB as described above. In other aspects, the DU 170 transmits an RRC reconfiguration message to each UE, including a DL BWP configuration and a UL BWP configuration configuring the DL BWP and the UL BWP, respectively. The DU 170 communicates with UEs of the first, second, and / or third UE ty pe on the cell via the DL BWP and UL BWP.

[0077] In other aspects, the DU 170 configures a first DL BWP and a first UL BWP of the cell for UEs of the first UE type and the second UE type and configures a second DL BWP and a second UL BWP of the cell for UEs of the third UE type. In some aspects, the DU 170 broadcasts a first SIB on the cell, including a first DL BWP configuration and a first UL BWP configuration configuring the first DL BWP and the first UL BWP, respectively. Depending on the implementation, the first SIB is a SIB1 or another SIB as described with respect to the CU configuration information, above. In some aspects, the DU 170 broadcasts a second SIB on the first cell, including a second DL BWP configuration and a second UL BWP configuration configuring the second DL BWP and the second UL BWP, respectively. Depending on the implementation, the second SIB is a SIB1 or another SIB as described above. In some aspects, the first SIB and the second SIB are the same SIB (e g., the same instance or different instances) or different SIBs. In other aspects, the DU 170 transmits an RRC reconfiguration message to each UE of the first UE type or the second UE type, including a first DL BWP configuration and a first UL BWP configuration configuring the first DL BWP and the first UL BWP, respectively. In other aspects, the DU 170 transmits an RRC reconfiguration message to each UE of the third UE type, including a second DL BWP configuration and a second UL BWP configuration configuring the second DL BWP and the second UL BWP, respectively. The DU 170 communicates with UEs of the first UE type and / or second UE type on the cell via the first DL BWP and first UL BWP, and communicates with UEs of the third UE type via the second DL BWP and second UL BWP.

[0078] In yet other aspects, the DU 170 configures a first DL BWP and a first UL BWP of the cell for UEs of the first UE type, configures a second DL BWP and a second UL BWP forUEs of the second UE type, and configures a third DL BWP and a third UL BWP of the cell for UEs of the third UE type. In some aspects, the DU 170 broadcasts a first SIB on the cell, including a first DL BWP configuration and a first UL BWP configuration configuring the first DL BWP and the first UL BWP, respectively. Depending on the implementation, the first SIB is a SIB1 or another SIB as described with respect to the CU configuration information, above. In some aspects, the DU 170 broadcasts a second SIB on the first cell, including a second DL BWP configuration and a second UL BWP configuration configuring the second DL BWP and the second UL BWP, respectively. Depending on the implementation, the second SIB is a SIB1 or another SIB as described with respect to the CU configuration information, above. In some aspects, the DU 170 broadcasts a third SIB on the first cell, including a third DL BWP configuration and a third UL BWP configuration configuring the third DL BWP and the third UL BWP, respectively . Depending on the implementation, the third SIB is an SIB1 or another SIB as described with respect to the CU configuration information, above. In some aspects, the first SIB, the second SIB, and the third SIB are the same SIB (e.g., the same instance or different instances) or different SIBs. In other aspects, the DU 170 transmits an RRC reconfiguration message to each UE of the second UE type, including a first DL BWP configuration and a first UL BWP configuration configuring the first DL BWP and the first UL BWP, respectively. In other aspects, the DU 170 transmits an RRC reconfiguration message to each UE of the first UE type, including a second DL BWP configuration and a second UL BWP configuration configuring the second DL BWP and the second UL BWP, respectively. In other aspects, the DU 170 transmits an RRC reconfiguration message to each UE of the third UE ty pe, including a third DL BWP configuration and a third UL BWP configuration configuring the third DL BWP and the third UL BWP, respectively. The DU 170 communicates with UEs of the second UE type on the cell via the first DL BWP and first UL BWP, communicates with UEs of the first UE type on the cell via the second DL BWP and second UL BWP, and communicates with UEs of the third UE type via the third DL BWP and third UL BWP.

[0079] The events 535, 540, 545, 550, 555, 560, 565, 570, 575. 580. and 585 are collectively referred to in FIG. 5 as a connection establishment procedure, a connection resume procedure, or a connection reestablishment procedure 508 (sub-diagram 508). The sub-diagram 508 includes sub-diagrams 504 and 506.

[0080] FIGs. 6-10 illustrate variations on the scenario described in FIG. 5. FIG. 6 illustrates an aspect for an alternative transmission of UE-type information to the CU 160. FIG. 7 illustrates an aspect for an alternative identification of UE-tj pe information based on a random access preamble by the DU 170. FIG. 8 illustrates an aspect for an alternative transmission of UE-type information, identified based on a random access preamble, to the CU 160. FIG. 9illustrates an aspect for an alternative categorization of UE-type information by the CU 160. FIG. 10 illustrates an aspect for an alternative identification of UE-type information, based on time and frequency resources, by the DU 170.

[0081] FIG. 6. illustrates a scenario 600 similar to the scenario 500 of FIG. 5, except that the scenario 600 includes events 605 and 610 instead of events 555 and 560, that describe an alternative transmission of UE-type information to the CU 160. As described with respect to subdiagram 502 of FIG. 5, the DU 170 initiates an Fl setup procedure with the CU 160.

[0082] In the scenario 600, the DU 170 transmits (605) a DU-to-CU message, including the RRC request message and an indication of the second UE type, to the CU 160. The DU-to- CU message (605) is similar to the DU-to-CU message 555 except that the DU-to-CU message (605) includes the indication of the second UE type instead of the indication of the first UE type. Thus, the CU 160 categorizes (610) the UE 110 as the second UE type, based on the indication of the second UE type. Thus, the CU 160 takes proper handlings for the UE 110. based on the indication of the second UE type. For example, the CU 160 may manage user plane resources for the UE 1 10 based on the indication of the second UE type. To manage user plane resources, the CU 160 may determine quality of sendee (QoS) information and / or user plane transport layer information based on the indication of the second UE type. The CU 160 may then transmit a CU- to-DU message (e.g., UE Context Setup Request message) to the DU 170. including the QoS information and / or the user plane transport layer information.

[0083] In some aspects (not shown), the CU 160 transmits a BS-to-CN message to a CN (e.g., the CN 150) or an AMF (e.g., the AMF 152), including an indication of the second UE type for the UE 110. Thus, in some aspects, the CN 150 categorizes the UE 110 as the second UE type, based on the indication of the second UE type. In some aspects, the CN 150 applies a charging policy or rate for the second UE type for the UE 110 to charge data traffic communicated with the UE 110 based on the indication or categorization. In some such cases, the CN 150 applies different charging policies or rates for the first UE type, the second UE type, and / or the third UE type. In some aspects, the BS-to-CN message is an Initial UE Message message. In some aspects, the AMF 152 transmits (not show n) a message including an indication of the second UE type to an SMF after receiving the BS-to-CN message. Thus, in some aspects, the SMF takes proper handlings for the UE 110 based on the indication of the second UE type. For example, the SMF interacts with the UPF to manage user plane resources for the UE 110 and / or ensure that data of the UE 1 10 is routed and / or forwarded correctly, based on the indication of the second UE type. In another example, the SMF may transmit a SMF-to-UPF message to the UPF, including an indication of the second UE type. Thus, the UPF manages user plane resources for the UE 110 based on the indication of the second UE type.

[0084] The sub-diagrams 504 and 506, and events 550, 605, and 610 are collectively referred to in FIG. 6 as a connection establishment procedure, a connection resume procedure, or a connection reestablishment procedure 602 (sub-diagram 602).

[0085] Turning to FIG. 7, a scenario 700 is similar to the scenario 500. except that the scenario 700 includes event 705 instead of event 550, that describes an alternative identification of UE-type information based on a random access preamble by the DU 170. As described with respect to sub-diagram 502 of FIG. 5, the DU 170 initiates an Fl setup procedure with the CU 160. In the scenario 700, the DU 170 identifies (705) that the UE 110 is the second UE type when (i) the RA preamble (535) is configured specifically for the second UE type or (ii) the DU 170 receives (535) the RA preamble on time and frequency resources particularly configured for the second UE type. Based on the identification, the DU 170 transmits (555) the DU-to-CU message, including the RRC request message and the indication of the first UE ty pe, to the CU 160.

[0086] In some aspects, if the DU 170 receives, from a UE, an RA preamble not configured specifically for the second UE type (e.g., the RA preamble is configured for the first UE type or the third UE type), the DU 170 identifies that the UE is the first UE type or the third UE type.

[0087] The sub-diagrams 504 and 506, and events 705, 555, and 560 are collectively referred to in FIG. 7 as a connection establishment procedure, a connection resume procedure, or a connection reestablishment procedure 702 (sub-diagram 702).

[0088] Turning to FIG. 8, a scenario 800 is similar to the scenario 600 and describes an alternative transmission of UE-type infonnation, identified based on a random access preamble, to the CU 160. As described with respect to sub-diagram 502 of FIG. 5, the DU 170 initiates an Fl setup procedure with the CU 160. In the scenario 800, based on the identification (705), the DU 170 transmits (605) the DU-to-CU message, including the RRC request message and the indication of the second UE type, to the CU 160. The sub-diagrams 504 and 506, and events 605, 610, and 705 are collectively referred to in FIG. 8 as a connection establishment procedure, a connection resume procedure, or a connection reestablishment procedure 802 (sub-diagram 802).

[0089] Turning to FIG. 9, a scenario 900 is similar to the scenarios 500-800 that describes an alternative categorization of UE-type information by the CU 160. As described with respect to sub-diagram 502 of FIG. 5, the DU 170 initiates an Fl setup procedure with the CU 160. In the scenario 900, the CU 160 classifies (905) the UE 110 as the second UE type based on the RRC request message. In some aspects, because the UE 110 is the second UE type, the UE 110 generates the RRC request message (i.e., a type 2 RRC request message) in accordance with a format of the type 2 RRC request message. If the UE 110 is the first UE type or the third UE type, the RRC request message is a type 1 RRC request message. Thus, when the CU 160 receives theRRC request message in accordance with the format of the type 2 RRC request message, the CU 160 categorizes the UE 110 as the second UE type despite the CU 160 receiving the indication of the first UE ty pe (555). In other words, the CU 160 discards or ignores the indication of the first UE type (555).

[0090] In some aspects, if the UE 110 is the second UE type and operates (530) in the idle state, the type 2 RRC request message is an RRCSetupRequestl message. In some aspects, if the UE 110 is the first or third UE type and operates (530) in the idle state, the type 2 RRC request message is an RRCSetupRequest message. In some aspects, if the UE 110 is the second UE type and operates (530) in the connected state, the RRC request message is an RRCReestablishmentRequestl message. If the UE 110 is the first or third UE ty pe and operates (530) in the connected state, the RRC request message is an RRCReestablishmentRequest message. In some aspects, if the UE 110 is the second UE type and operates (530) in the inactive state, the RRC request message is an RRCResumeRequest2 message or an RRCResumeRequest3 message. If the UE 110 is the first or third UE type and operates (530) in the inactive state, the RRC request message is an RRCResumeRequest message or an RRCResumeRequestl message.

[0091] In some alternative aspects, the UE 110 sets the LCID to the first value instead of the second value, and the DU 170 identifies that the UE 110 is the first UE type, based on the first value of the LCID. A benefit of using the first value is to save a reserved value of the LCID for use in the future.

[0092] The sub-diagrams 504 and 506, and events 550, 555, and 905 are collectively referred to in FIG. 9 as a connection establishment procedure, a connection resume procedure, or a connection reestablishment procedure 902 (sub-diagram 902).

[0093] Turning to FIG. 10, a scenario 1000 is similar to the scenarios 500-900 that describe an alternative identification of UE-type information, based on time and frequency resources, by the DU 170. As described w ith respect to sub-diagram 502 of FIG. 5, the DU 170 initiates an Fl setup procedure with the CU 160. In some alternative aspects, the DU 170 configures the same RA resources for both the first UE type and the second UE type. The RA resources include RA preambles and / or time and frequency resources for a physical RA channel (PRACH). In some such cases, the DU 170 identifies that the UE 110 is the first UE ty pe when the DU 170 receives (535) the RA preamble in accordance with the RA resources. A benefit of configuring the same RA resources for both the first UE type and the second UE type is to save RA resources.

[0094] The sub-diagrams 504 and 506, and events 555, 805, and 905 are collectively referred to in FIG. 10 as a connection establishment procedure, a connection resume procedure,or a connection reestablishment procedure a connection establishment procedure or a connection resume procedure 1002 (sub-diagram 1002).Example Methods

[0095] Example methods 1100-2200 are described with reference to FIGs. 11-22 in accordance with one or more aspects of managing reduced-capability user equipment. FIGs. 11- 14 are flow diagrams of example methods in which a DU of a base station can identify whether a UE is a first UE type (e.g., a RedCap UE), a second UE type (e g., a fRedCap UE). or a third UE type (e.g., a normal-capability UE), and provide an indication of the first, second, or third UE type to a CU of the base station. FIGs. 15 and 16 are flow diagrams of example methods in which the DU of a base station can indicate, to a CU of the base station, which types of UEs are allowed to access one or more cells operated by the DU. FIGs. 17 and 18 are flow diagrams of example methods in which a DU of a base station can provide a configuration for a UE, to a CU of the base station, based on a UE type of the UE. FIGs. 19 and 20 are flow diagrams of example methods in which a CU of a base station can identify whether a cell allows a UE of a particular type to access based on information received from a DU of the base station. FIGs. 21 and 22 are flow diagrams of example methods in which RAN node can configure radio resources and communicate with UEs of a first, second, and / or third UE type.

[0096] FIG. 11 illustrates example method(s) 1100 of managing reduced-capability user equipment as generally related to identifying, by a DU (e.g., DU 170) of a base station (e.g., base station 120), whether a UE (e.g., UE 110) is a first UE type (e.g., a RedCap UE), a second UE type (e.g., a fRedCap UE), or a third UE type (e.g., a normal-capability UE), and providing an indication of the first, second, or third UE type to a CU (e.g., CU 160) of the base station as generally described with respect to FIG. 5. At block 1102, the DU performs a random access procedure with the UE. For example, the UE initiates a procedure to establish or restore a radio connection with the base station 120 using a four-step procedure or a two-step procedure as described above with respect to FIG. 5.

[0097] At block 1104, the DU receives a Media Access Control (MAC) Protocol Data Unit (PDU) from the UE in the random access procedure, the MAC PDU including a logical channel identifier (LCID) and a message. For example, the DU, at 545, receives a MAC PDU that includes an LCID and an RRC request message.

[0098] At block 1106, the DU includes the received message in a DU-to-CU message. For example, the DU includes the received RRC request message in a DU-to-CU message.

[0099] At block 1108, the DU identifies a value of the LCID as being a first value, a second value, or a third value. For example, the DU identifies if the LCID has a first value, a secondvalue, or a third value that indicates that the UE is a RedCap UE, an fRedCap UE, or a normalcapability UE, respectively.

[0100] At block 1110, if the identified value is a first value or a second value, the DU includes an indication of a first-type of UE in the DU-to-CU message, and at block 1112, the DU transmits the DU-to-CU message to the CU. For example, the DU includes the indication of the first-type of UE in the DU-to-CU message and transmits the DU-to-CU message to the CU that is effective to direct the CU to generate an RRC response message based on the received indication.

[0101] At block 1108, if the DU identifies the third RA configuration, then the DU transmits the DU-to-CU message to the CU, without the insertion of an indication of type of UE at 1112.

[0102] FIG. 12 illustrates example method(s) 1200 of managing reduced-capability user equipment as generally related to identifying, by a DU (e.g., DU 170) of a base station (e.g., base station 120), whether a UE (e.g., UE 110) is a first UE type (e.g., a RedCap UE), a second UE type (e.g., a fRedCap UE), or a third UE type (e.g., a normal-capability UE), and providing an indication of the first, second, or third UE type to a CU (e.g., CU 160) of the base station as generally described with respect to FIG. 6. At block 1202, the DU performs a random access procedure with the UE. For example, the UE initiates a procedure to establish or restore a radio connection with the base station 120 using a four-step procedure or a two-step procedure as described above with respect to FIG. 5.

[0103] At block 1204, the DU receives a Media Access Control (MAC) Protocol Data Unit (PDU) from the UE in the random access procedure, the MAC PDU including a logical channel identifier (LCID) and a message. For example, the DU, at 545, receives a MAC PDU that includes an LCID and an RRC request message.

[0104] At block 1206, the DU includes the received message in a DU-to-CU message. For example, the DU includes the received RRC request message in a DU-to-CU message.

[0105] At block 1208, the DU identifies a value of the LCID as being afirst value, a second value, or a third value. For example, the DU identifies if the LCID has a first value, a second value, or a third value that indicates that the UE is a RedCap UE, an fRedCap UE, or a normalcapability UE, respectively.

[0106] At block 1210, if the identified value is a first value, the DU includes an indication of a first-type of UE in the DU-to-CU message, and at block 1214. the DU transmits the DU-to- CU message to the CU. For example, the DU includes the indication of the first-type of UE in the DU-to-CU message and transmits the DU-to-CU message to the CU that is effective to direct the CU to generate an RRC response message based on the received indication.

[0107] At block 1212, if the identified value is a second value, the DU includes an indication of a second-type of UE in the DU-to-CU message, and at block 1214, the DU transmits the DU-to-CU message to the CU. For example, the DU includes the indication of the second- type of UE in the DU-to-CU message and transmits the DU-to-CU message to the CU that is effective to direct the CU to generate an RRC response message based on the received indication.

[0108] At block 1208, if the DU identifies the third RA configuration, then the DU transmits the DU-to-CU message to the CU, without the insertion of an indication of type of UE at 1212.

[0109] FIG. 13 illustrates example method(s) 1300 of managing reduced-capability user equipment as generally related to identifying, by a DU (e.g., DU 170) of a base station (e.g., base station 120), whether a UE (e.g., UE 110) is a first UE type (e.g., a RedCap UE), a second UE type (e.g., a fRedCap UE), or a third UE type (e.g., a normal-capability UE), and providing an indication of the first, second, or third UE type to a CU (e.g., CU 160) of the base station as generally described with respect to FIG. 7. At block 1302, the DU broadcasts a first random access (RA) configuration. At block 1304, the DU broadcasts a second RA configuration. Optionally at block 1306, the DU broadcasts athird RA configuration. For example, the DU configures the first RA configuration, the second RA configuration, and the third RA configuration for UEs of a first UE type. UEs of a second UE type, and UEs of a third UE type, respectively. In some aspects, the RA configurations include configuration parameters configuring one or more random access preambles, association(s) between the random access preamble(s) and synchronization signal and physical broadcast channel blocks (SSBs), and / or time and / or frequency resources for transmission of the random access preamble(s).

[0110] At block 1308, the DU performs a random access procedure with the UE. For example, the UE initiates a procedure to establish or restore a radio connection with the base station 120 using a four-step procedure or a two-step procedure as described above with respect to FIG. 5.

[0111] At block 1310. the DU receives a Media Access Control (MAC) Protocol Data Unit (PDU) from the UE in the random access procedure, the MAC PDU including a logical channel identifier (LCID) and a message. For example, the DU, at 545, receives a MAC PDU that includes an LCID and an RRC request message.

[0112] At block 1312, the DU includes the received message in a DU-to-CU message. For example, the DU includes the received RRC request message in a DU-to-CU message.

[0113] At block 1314, the DU identifies an RA configuration used for the RA procedure, the RA configuration used for the RA procedure being the first RA configuration, the second RA configuration, or the third RA configuration. For example, the DU identifies if the first RAconfiguration, the second RA configuration, or the third RA configuration indicates that the UE is a RedCap UE, an fRedCap UE, or a normal-capability UE, respectively.

[0114] At block 1316, if the identified RA configuration is a first RA configuration or a second RA configuration, the DU includes an indication of a first-type of UE in the DU-to-CU message, and at block 1318. the DU transmits the DU-to-CU message to the CU. For example, the DU includes the indication of the first-type of UE in the DU-to-CU message and transmits the DU-to-CU message to the CU that is effective to direct the CU to generate an RRC response message based on the received indication.

[0115] At block 1314, if the DU identifies the third RA configuration, then the DU transmits the DU-to-CU message to the CU, without the insertion of an indication of type of UE at 1318.

[0116] FIG. 14 illustrates example method(s) 1400 of managing reduced-capability user equipment as generally related to identifying, by a DU (e.g., DU 170) of a base station (e.g., base station 120), whether a UE (e.g., UE 110) is a first UE type (e.g., a RedCap UE), a second UE type (e g., a fRedCap UE), or a third UE type (e.g., a normal-capability UE), and providing an indication of the first, second, or third UE type to a CU (e.g., CU 160) of the base station as generally described with respect to FIG. 8. At block 1402, the DU broadcasts a first random access (RA) configuration. At block 1404, the DU broadcasts a second RA configuration. Optionally at block 1406, the DU broadcasts athird RA configuration. For example, the DU configures the first RA configuration, the second RA configuration, and the third RA configuration for UEs of a first UE type, UEs of a second UE type, and UEs of a third UE type, respectively. In some aspects, the RA configurations include configuration parameters configuring one or more random access preambles, association(s) between the random access preamble(s) and synchronization signal and physical broadcast channel blocks (SSBs), and / or time and / or frequency resources for transmission of the random access preamble(s).

[0117] At block 1408, the DU performs a random access procedure with the UE. For example, the UE initiates a procedure to establish or restore a radio connection with the base station 120 using a four-step procedure or a two-step procedure as described above with respect to FIG. 5.

[0118] At block 1410, the DU receives a Media Access Control (MAC) Protocol Data Unit (PDU) from the UE in the random access procedure, the MAC PDU including a logical channel identifier (LCID) and a message. For example, the DU, at 545, receives a MAC PDU that includes an LCID and an RRC request message.

[0119] At block 1412, the DU includes the received message in a DU-to-CU message. For example, the DU includes the received RRC request message in a DU-to-CU message.

[0120] At block 1414, the DU identifies an RA configuration used for the RA procedure, the RA configuration used for the RA procedure being the first RA configuration, the second RA configuration, or the third RA configuration. For example, the DU identifies if the first RA configuration, the second RA configuration, or the third RA configuration indicates that the UE is a RedCap UE. an fRedCap UE, or a normal-capability UE, respectively.

[0121] At block 1416, if the identified RA configuration at 1414 is a first RA configuration, the DU includes an indication of a first-type of UE in the DU-to-CU message, and at block 1420, the DU transmits the DU-to-CU message to the CU. For example, the DU includes the indication of the first-type of UE in the DU-to-CU message and transmits the DU-to-CU message to the CU that is effective to direct the CU to generate an RRC response message based on the received indication.

[0122] At block 1418, if the identified RA configuration at 1414 is a second RA configuration, the DU includes an indication of a second-type of UE in the DU-to-CU message, and at block 1420, the DU transmits the DU-to-CU message to the CU. For example, the DU includes the indication of the second-type of UE in the DU-to-CU message and transmits the DU- to-CU message to the CU that is effective to direct the CU to generate an RRC response message based on the received indication.

[0123] At block. 1414, if the DU identifies the third RA configuration, then the DU transmits the DU-to-CU message to the CU, without the insertion of an indication of type of UE at 1420.

[0124] FIG. 15 illustrates example method(s) 1500 of managing reduced-capability user equipment as generally related to communication between a DU (e.g., DU 170) and a CU (e.g., CU 160) of a base station (e.g., base station 120) to configure the base station to handle UEs (e.g., UEs 110) of various types, including is a first UE type (e g., a RedCap UE), a second UE type (e.g., a fRedCap UE), or a third UE type (e.g., a normal-capability UE) as generally described with respect to FIG. 5, sub-diagram 502. At block 1502, the DU transmits a first DU-to-CU message to a CU. including first information for a first cell, the first information indicating whether UEs of a first UE type are allowed to access the first cell (e.g., event 505 or 515). At block 1504, the DU transmits a second DU-to-CU message to the CU, including second information for the first cell, the second information indicating whether UEs of a second UE type are allowed to access the first cell (e.g., event 505 or 515). At block 1506, the DU broadcasts the first information on the first cell (e.g., event 525). At block 1508, the DU broadcasts the second information on the first cell (e.g., event 525).

[0125] In some aspects, the first UE type is a RedCap UE and the second UE type is fRedCap UE. In some implementations, the DU refrains from transmitting information indicating whether normal-capability UEs are allowed to access a cell to the CU.

[0126] In other aspects, the first and second DU-to-CU messages are Fl application protocol (F1AP) messages. In some aspects, the first DU-to-CU message and the second DU-to- CU message are Fl Setup Request messages or gNB-DU Configuration Update messages. In other aspects, one of the first and second DU-to-CU messages is an Fl Setup Request message and the other is a gNB-DU Configuration Update message. In some aspects, the DU generates a first IE and a second IE including the first infonnation and the second information, respectively. In some aspects, the DU includes the first IE and the second IE in a first field / IE and a second field / IE of an interface protocol in the first DU-to-CU message and the second DU-to-CU message, respectively. In some aspects, the interface protocol is an Fl application protocol (F1AP). In some aspects, the first IE and the second IE are lEs of an RRC protocol. In other aspects, the first IE and the second IE are lEs of an interface protocol (e.g., F1AP). In some aspects, the first IE and the second IE are the same IE with different contents. In other aspects, the first UE and the second IE are different lEs.

[0127] In some aspects, the DU includes the first information and the second information in a first SIB and a second SIB, respectively, and broadcasts the first SIB and the second SIB on the first cell. In other aspects, the first information and the second information are the RedCap infonnation and the fRedCap information, respectively, as described in FIGs. 5-10.

[0128] FIG. 16 illustrates example method(s) 1600 of managing reduced-capability user equipment as generally related to communication between a DU (e.g., DU 170) and a CU (e.g., CU 160) of a base station (e.g., base station 120) to configure the base station to handle UEs (e.g., UEs 110) of various types, including is a first UE type (e g., a RedCap UE), a second UE type (e.g., a fRedCap UE), or a third UE type (e.g., a normal-capability UE) as generally described with respect to FIG. 5, sub-diagram 502. At block 1602, the DU transmits a first DU-to-CU message to a CU, including first information and second information for a first cell, the first information indicating whether UEs of a first UE type are allowed to access the first cell and the second infonnation indicating whether UEs of a second UE type are allowed to access the first cell (e.g., event 505 or 515).

[0129] At block 1604, the DU broadcasts the first information on the first cell (e.g., event 525). At block 1606, the DU broadcasts the second information on the first cell (e.g., event 525).

[0130] In some aspects, the DU-to-CU message is a F1AP message such as a Fl Setup Request message or a gNB-DU Configuration Update message. In some aspects, the DU generates a first IE including the first information and the second information and includes thefirst IE in a field or an IE of an interface protocol in the DU-to-CU message. In some aspects, the first information and the second information are combined as single information and includes the single information in a first IE. In some aspects, the interface protocol is an Fl application protocol (F1AP). In some aspects, the first IE is an IE of a RRC protocol. In other aspects, the first IE is an IE of the interface protocol. In some aspects, the DU generates a SIB including the first information and the second information and broadcasts the SIB on the first cell. In some aspects, the DU generates a SIB including the first IE and broadcasts the SIB on the first cell. In some aspects, the DU includes the SIB in the DU-to-CU message in addition to the first IE. In some aspects, the SIB is a SIB1.

[0131] In other aspects, the DU generates a first IE and a second IE including the first information and the second information, respectively, and includes the first IE and the second IE in a first field / IE and a second field / IE of an interface protocol in the DU-to-CU message. In some aspects, the first IE and the second IE are the same IE with different contents. In other aspects, the first UE and the second IE are different IES. In some aspects, the first IE and the second IE are IEs of a RRC protocol. In other aspects, the first IE and the second IE are IEs of the interface protocol.

[0132] FIG. 17 illustrates example method(s) 1700 of managing reduced-capability user equipment as generally related to generating configurations by aDU (e.g.. DU 170) for a CU (e.g., CU 160) of a base station (e.g., base station 120) to configure the base station to handle UEs (e.g., UEs 110) of various types, including is a first UE type (e.g., a RedCap UE), a second UE type (e.g., a fRedCap UE), or a third UE type (e.g., a normal-capability7UE) as generally described with respect to FIG. 5. At block 1702. the DU communicates with a UE and a CU (e.g., events in sub-diagram 508). At block 1704, the DU identifies whether a type of the UE is a first type, a second ty pe, or a third ty pe (e.g., event 550). If the DU identifies that the type is the first type at block 1704, the flow proceeds to block 1706. At block 1706, the DU generates a first configuration for the UE. At block 1708, the DU sends the first configuration to the CU. In some aspects, the DU sends a DU-to-CU message including the first configuration to the CU.

[0133] Ifthe DU identifies that the type is the second type at block 1704, the flow proceeds to block 1710. At block 1710, the DU generates a second configuration for the UE (e.g., event 555). At block 1712, the DU sends the second configuration to the CU. In some aspects, the DU sends a DU-to-CU message including the second configuration to the CU. Otherwise, if the DU identifies that the type is the third type at block 1704, the flow proceeds to block 1714. At block 1714, the DU generates a third configuration for the UE. At block 1718, the DU sends the third configuration to the CU. In some aspects, the DU sends a DU-to-CU message including the third configuration to the CU.

[0134] In some aspects, the DU includes, in the first configuration, one or more configuration parameters suitable for the UE in the case of the first UE type. In other aspects, the DU includes, in the second configuration, one or more configuration parameters suitable for the UE in the case of the second UE type. In further aspects, the DU includes, in the third configuration, one or more configuration parameters suitable for the UE in the case of the third UE type. In some aspects, the first, second, and third configurations are cell group configurations (e.g., CellGroupConfig IES). In some aspects, the first, second, and third configurations include different configuration parameters and / or the same configuration parameters.

[0135] In some aspects, the DU-to-CU message is an Initial UL RRC Message Transfer message. In other aspects, the DU-to-CU message is a UE Context Modification Required message, a UE Context Modification Response message, or a UE Context Setup Response message.

[0136] FIG. 18 illustrates example method(s) 1800 of managing reduced-capability user equipment as generally related to generating configurations by a DU (e.g., DU 170) for a CU (e.g., CU 160) of abase station (e g., base station 120) to configure the base station to handle UEs (e.g., UEs 110) of various types, including is a first UE type (e.g., a RedCap UE), a second UE type (e.g., a fRedCap UE), or a third UE type (e.g., a normal-capability UE) as generally described with respect to FIG. 5 and is similar to method 1700.

[0137] At block 1802, the DU communicates with a UE and a CU (e.g., events in subdiagram 508). At block 1804, the DU identifies whether a type of the UE is a first ty pe, a second type, or a third ty pe (e.g., event 550). If the DU identifies that the type is the first type or the second type at block 1804, the flow proceeds to block 1806. At block 1806. the DU generates a second configuration for the UE. At block 1808, the DU sends the second configuration to the CU. In some aspects, the DU sends a DU-to-CU message including the second configuration to the CU.

[0138] If the DU identifies that the type is the third type at block 1804, the flow proceeds to block 1810. At block 1810, the DU generates athird configuration for the UE (e.g., event 555). At block 1812, the DU sends the third configuration to the CU. In some aspects, the DU sends a DU-to-CU message including the third configuration to the CU.

[0139] FIG. 19 illustrates example method(s) 1900 of managing reduced-capability user equipment as generally related to generating configurations by a CU (e.g., CU 160) using information received from a DU (e.g., DU 170) of a base station (e.g., base station 120) to configure the base station to handle UEs (e.g., UEs 110) of various types, including is a first UE type (e.g., a RedCap UE), a second UE type (e.g., a fRedCap UE), or a third UE type (e.g., a nonnal-capability UE) as generally described with respect to FIG. 5.

[0140] At block 1902, the CU receives first information for a first cell from a first DU (e.g., event 505 or 515). At block 1904, the CU identifies, based on the first information, whether the first cell allows access to UEs of a first UE type. At block 1906, the CU configures UEs of the first UE type to measure and / or access the first cell based on the identification that the first cell allows UEs of the first UE type to access the cell. If the CU identifies that the first cell does not allow UEs of the first UE type to access the cell, based on the first information, the CU refrains from configuring UEs of the first UE type to measure and / or access the first cell.

[0141] At block 1908, the CU receives second information for the first cell from the first DU (e.g.. event 505 or 515). At block 1910 and based on the second information, the CU identifies whether the first cell allows UEs of a second UE type to access the cell. At block 1912, the CU configures UEs of the second UE type to measure and / or access the first cell based on the identification that the first cell allows the second type UE to access the cell. If the CU identifies that the first cell does not allow UEs of the second UE type to access based on the second information, the CU refrains from configuring UEs of the second UE type to measure and / or access the first cell.

[0142] In some aspects, the CU receives third information for a second cell from the first DU (e.g., event 505 or 515). The CU identifies, based on the third information, whether the second cell allows UEs of the first UE type to access the second cell. The CU configures UEs of the first UE type to measure and / or access the second cell based on the identification that the second cell allows UEs of the first UE ty pe to access the second cell. If the CU identifies, based on the third information, that the second cell does not allow UEs of the first UE type to access the cell, the CU refrains from configuring UEs of the first UE type to measure and / or access the second cell. The CU receives fourth information for the second cell from the first DU (e.g., event 505 or 515). Based on the fourth information, the CU identifies that the second cell allows UEs of the second UE ty pe to access the second cell. The CU configures UEs of the second UE ty pe to measure and / or access the second cell based on the identification that the second cell allows the second type UE to access. If the CU identifies, based on the fourth information, that the second cell does not allow UEs of the second UE ty pe to access the second cell, the CU refrains from configuring UEs of the second UE type to measure and / or access the second cell.

[0143] In some aspects, the CU receives fifth information for a third cell from a second DU, similar to event 505 or 515. Based on the fifth information, the CU identifies that the third cell allows UEs of the first UE type to access the third cell. Based on the identification that the third cell allows UEs of the first UE type to access the third cell, the CU configures UEs of the first UE type to measure and / or access the third cell. If the CU identifies, based on the fifth information, that the third cell does not allow UEs of the first UE type to access the third cell, theCU refrains from configuring UEs of the first UE type to measure and / or access the third cell. The CU receives sixth information for the third cell from the second DU, similar to event 505 or 515. Based on the sixth information, the CU identifies that the third cell allows UEs of the second UE type to access the third cell. Based on the identification that the third cell allows the second type UE to access the third cell, the CU configures UEs of the second UE type to measure and / or access the third cell. If the CU identifies, based on the sixth information that the third cell does not allow UEs of the first UE type to access the third cell, the CU refrains from configuring UEs of the second UE type to measure and / or access the third cell.

[0144] In some aspects, examples and implementations as described for FIGs. 15 and 16 can apply to FIG. 19. In some aspects, examples and implementations described for the first information and the second information can apply to the third information and the fourth information, respectively. In some aspects, examples and implementations described for the first information and second information can apply to the fifth information and the sixth information, respectively.

[0145] FIG. 20 illustrates example method(s) 2000 of managing reduced-capability user equipment as generally related to generating configurations by a CU (e.g., CU 160) using information received from a DU (e.g., DU 170) of a base station (e.g., base station 120) to configure the base station to handle UEs (e.g., UEs 110) of various types, including is a first UE type (e.g., a RedCap UE), a second UE type (e.g., a fRedCap UE), or a third UE type (e.g., a normal-capability UE) as generally described with respect to FIG. 5.

[0146] At block 2002, the CU receives cell infonnation for a cell from a DU (e.g., event 505 or 515). At block 2004, the CU identifies whether the cell information includes first information. If the CU identifies that the cell information does not include the first information, the flow proceeds to block 2006 where the CU operates in a state in which the cell does not allow UEs of a first UE type to access the cell. Otherwise, if the CU identifies that the cell infonnation includes first infonnation, the flow proceeds to block 1904. At block 1904, the CU identifies, based on the first information, whether the first cell allows access to UEs of a first UE type. At block 1906, the CU configures UEs of the first UE type to measure and / or access the first cell based on the identification that the first cell allows UEs of the first UE type to access the cell. At block 2008, the CU identifies whether the cell infonnation includes second infonnation. If the CU identifies that the cell information does not include the second information, the flow proceeds to block 2010 where the CU operates in a state in which the cell does not allow UEs of a second UE type to access the cell. Otherwise, if the CU identifies that the cell information includes second information, the flow proceeds to block 1910. At block 1910 and based on the second information, the CU identifies whether the first cell allows UEs of a second UE type to access the cell. Atblock 1912, the CU configures UEs of the second UE type to measure and / or access the first cell based on the identification that the first cell allows the second type UE to access the cell.

[0147] In some aspects, the cell information is an IE of an interface protocol (e.g., F1AP). In other aspects, the cell information is a Serving Cell Information IE. In some aspects, examples and implementations as described for FIGs. 15, 16, and 19 can apply to FIG. 20.

[0148] FIG. 21 illustrates example method(s) 2100 of managing reduced-capability user equipment as generally related to generating configurations by aRAN node (e.g., base station 120, DU 170) to provide access for UEs (e.g., UEs 110) of various types, including is a first UE type (e.g., a RedCap UE). a second UE type (e.g., a fRedCap UE), or a third UE type (e.g.. a normalcapability UE) as generally described with respect to FIG. 5.

[0149] At block 2102, the RAN node configures a first portion of radio resources for communication with UEs of a first UE ty pe on a cell. At block 2104, the RAN node configures a second portion of radio resources for communication with UEs of a second UE type on the cell. At block 2106. the RAN node configures a third portion of radio resources for communication with UEs of a third UE type on the cell. At block 2108, the RAN node communicates with UEs of the first UE type on the cell, using the first portion of radio resources. At block 2110, the RAN node communicates with UEs of the second UE type on the cell, using the second portion of radio resources. At block 2112, the RAN node communicates with UEs of the third UE type on the cell, using the third portion of radio resources.

[0150] In some aspects, the RAN node transmits system information (e.g., one or more SIBs) on the cell, configuring the first portion, second portion, and / or third portion of the radio resources (e.g.. event 525). In some aspects, the RAN node transmits a dedicated message (e.g., a RRC reconfiguration message) to each of UEs of the first UE type, configunng the first portion of the radio resources. In some aspects, the RAN node transmits a dedicated message (e.g., a RRC reconfiguration message) to each of UEs of the second UE type, configuring the second portion of the radio resources. In some aspects, the RAN node transmits a dedicated message (e.g., an RRC reconfiguration message) to each of UEs of the third UE type, configuring the third portion of the radio resources. In some aspects, the first UE type, the second UE type, and the third UE type are a RedCap UE, fRedCap UE, and a normal-capability UE, respectively.

[0151] In some aspects, the radio resources include a DL system bandwidth of the cell. In such cases, the first portion is a first DL BWP of the DL system bandwidth, the second portion is a second DL BWP of the DL system bandwidth, and the third portion is a third DL BWP of the DL system bandwidth. In some aspects, the third DL BWP is larger than the second DL BWP and the second DL BWP is larger than or equal to the first DL BWP. In some aspects, the first, second, and third DL BWPs partially or completely overlap. In some aspects, the third DL BWPincludes the second DL BWP and / or the second DL BWP includes the first DL BWP. In other aspects, the first, second, and / or third DL BWPs do not overlap.

[0152] In some aspects, the radio resources include a UL system bandwidth of the cell. In such cases, the first portion is a first UL BWP of the UL system bandwidth, the second portion is a second UL BWP of the UL system bandwidth, and the third portion is a third UL BWP of the UL system bandwidth. In some aspects, the third UL BWP is larger than the second UL BWP and the second UL BWP is larger than or equal to the first UL BWP. In some aspects, the first, second, and third UL BWPs partially or completely overlap. In some aspects, the third UL BWP includes the second UL BWP, and the second UL BWP includes the first UL BWP. In other aspects, the first, second, and / or third UL BWPs do not overlap.

[0153] In some aspects, the radio resources include RA preambles and / or time and frequency resources for transmission of RA preambles. In some aspects, the first, second, and / or third portions include different RA preambles and / or time and frequency resources for transmission of RA preambles. In other aspects, the first, second, and / or third portions include at least one identical RA preamble and / or identical time and frequency resources for transmission of RA preambles. In some aspects, the second portion includes the first portion. In other aspects, the second portion does not include the first portion. In some aspects, the third portion does not include the first portion and the second portion. In other aspects, the third portion includes the first portion and / or the second portion.

[0154] FIG. 22 illustrates example method(s) 2200 of managing reduced-capability user equipment as generally related to generating configurations by aRAN node (e.g., base station 120, DU 170) to provide access for UEs (e.g., UEs 110) of various types, including is a first UE type (e.g., a RedCap UE), a second UE type (e.g., a fRedCap UE), or a third UE type (e.g., a normalcapability UE) as generally described with respect to FIG. 5.

[0155] At block 2202, the RAN node configures a first portion of radio resources for communication with UEs of a first UE type on a cell. At block 2204, the RAN node configures the first portion of radio resources for communication with UEs of a second UE type on the cell. At block 2206, the RAN node configures a second portion of radio resources for communication with UEs of a third UE type on the cell. At block 2208, the RAN node communicates with UEs of the first UE type on the cell, using the first portion of radio resources. At block 2210, the RAN node communicates with UEs of the second UE type on the cell, using the first portion of radio resources. At block 2212, the RAN node communicates with UEs of the third UE t pe on the cell, using the second portion of radio resources.

[0156] In some aspects, the RAN node transmits system information (e.g., one or more SIBs) on the cell, configuring the first portion and second portion of the radio resources (e.g.,event 525). In some aspects, the RAN node transmits a dedicated message (e.g., a RRC reconfiguration message) to each of UEs of the first and second UE types, configuring the first portion of the radio resources. In some aspects, the RAN node transmits a dedicated message (e.g., a RRC reconfiguration message) to each of UEs of the third UE type, configuring the second portion of the radio resources. In some aspects, the first UE type, the second UE type, and the third UE type are a RedCap UE, fRedCap UE, and a normal-capability UE, respectively.

[0157] In some aspects, the radio resources include a DL system bandwidth of the cell. In such cases, the first portion is a first DL BWP of the DL system bandwidth and the second portion is a second DL BWP. In some aspects, the second DL BWP is larger than the first DL BWP. In some aspects, the first and second DL BWPs partially or completely overlap. In some aspects, the second DL BWP includes the first DL BWP. In other aspects, the first and second DL BWPs do not overlap.

[0158] In some aspects, the radio resources include a UL system bandwidth of the cell. In such cases, the first portion is a first UL BWP of the UL system bandwidth and the second portion is a second UL BWP. In some aspects, the second UL BWP is larger than the first UL BWP. In some aspects, the first and second UL BWPs partially or completely overlap. In some aspects, the second UL BWP includes the first UL BWP. In other aspects, the first and second UL BWPs do not overlap.

[0159] In some aspects, the radio resources include RA preambles and / or time and frequency resources for transmission of RA preambles. In some aspects, the first and second portions include different RA preambles and / or time and frequency resources for transmission of RA preambles. In other aspects, the first and second portions include at least one identical RA preamble and / or identical time and frequency resources for transmission of RA preambles. In some aspects, the second portion includes the first portion. In other aspects, the second portion does not include the first portion.

[0160] The following additional considerations apply to the foregoing discussion. In some implementations, "message” is used and can be replaced by "information element (IE).” In some implementations, “IE” is used and can be replaced by “field.” The description for the CU or DU can apply to an aggregated base station implementing communication functions of CU and DU for communicating with a UE. In the case of the aggregated base station, the messages exchanged between the CU and DU can be omitted or seen as internal computer instructions or internal messages exchanged between different processes in the aggregated base station.

[0161] The order in which the method blocks are described is not intended to be construed as a limitation, and any number of the described method blocks can be skipped or combined in any order to implement a method or an alternate method. Generally, any of the components,modules, methods, and operations described herein can be implemented using software, firmware, hardware (e g., fixed logic circuitry), manual processing, or any combination thereof. Some operations of the example methods may be described in the general context of executable instructions stored on computer-readable storage memory that is local and / or remote to a computer processing system, and aspects can include software applications, programs, functions, and the like. Alternatively or in addition, any of the functionality described herein can be performed, at least in part, by one or more hardware logic components, such as, and without limitation, Field- programmable Gate Arrays (FPGAs), Application-specific Integrated Circuits (ASICs), Application-specific Standard Products (ASSPs), System-on-a-chip systems (SoCs). Complex Programmable Logic Devices (CPLDs), and the like.

[0162] Although aspects of managing reduced-capability user equipment have been described in language specific to features and / or methods, the subject of the appended claims is not necessarily limited to the specific features or methods described. Rather, the specific features and methods are disclosed as example aspects of managing reduced-capability user equipment, and other equivalent features and methods are intended to be within the scope of the appended claims. Further, various different aspects are described, and it is to be appreciated that each described aspect can be implemented independently or in connection with one or more other described aspects.

[0163] In the following some examples are described:Example 1: A method for managing a reduced-capability user equipment (UE) by a distributed unit (DU) of a base station, the method comprising: performing a random access procedure with the UE; receiving a Media Access Control (MAC) Protocol Data Unit (PDU) from the UE in the random access procedure, the MAC PDU including a logical channel identifier (LCID) and a message; including the received message in a DU-to-CU message; identifying a value of the LCID, the value being a first value, a second value, or a third value; if the identified value is a first value, including an indication of a first-type of UE in the DU-to-CU message; if the identified value is a second value, including an indication of a first-type of UE in the DU-to-CU message; and transmitting the DU-to-CU message to a Central Unit (CU).Example 2: The method of example 1, wherein the first value indicates that the UE is a reduced-capability (RedCap) UE; wherein the second value indicates that the UE is a further- reduced-capability (fRedCap) UE; and wherein the third value indicates that the UE is a normalcapability UE.Example 3: The method of example 1 or example 2, wherein the message is a Radio Resource Control (RRC) request message.Example 4: The method of any one of the preceding examples, wherein the transmitting of the DU-to-CU message to the CU directs the CU to generate RRC response message for the UE, the method comprising: receiving, from the CU, the RRC response message for the UE; and transmitting the RRC response message to the UE.Example 5: The method of example 4, comprising: receiving, from the UE, an RRC complete message; and transmitting the RRC complete message to the CU in an other DU-to-CU message.Example 6: The method of example 5, wherein the RRC complete message is one of: RRCSetupComplete message; an RRCResumeComplete message; or an RRCReestablishmentComplete message.Example 7: The method of example 4, wherein the RRC response message is one of: an RRCSetupRequest message; an RRCResumeRequest message; or an RRCReestablishmentRequest message.Example 8: A method of performing an Fl setup procedure with a first Distributed Unit (DU) by a Central Unit (CU), the method comprising: receiving first information for a first cell from the first DU; based on the first information indicating that the first cell allows user equipments (UEs) of a first UE type to access the first cell, generating first configuration information for configuring UEs of the first UE type to measure and / or access the first cell; receiving second information for the first cell from the first DU;based on the second information indicating that the first cell allows UEs of a second UE type to access the first cell, generating second configuration information for configuring UEs of the second UE type to measure and / or access the first cell; receiving third information for the first cell from the first DU; and based on the third information indicating that the first cell allows UEs of a third UE type of access the first cell, generating third configuration information for configuring UEs of the third type to measure and / or access the first cell.Example 9: The method of example 8, comprising: transmitting, to the DU, an FI Setup Response message, including: the first configuration information; the second configuration information; or both the first configuration information and the second configuration information.Example 10: The method of example 9, wherein the first configuration includes first System Information Block(s) (SIB(s)); wherein the first SIB(s) include one or more of SIB2, SIB3, SIB4, SIB5, SIB6, SIB7, SIB8, and / or SIB9; wherein the second configuration includes second SIB(s); and wherein the second SIB(s) include one or more of SIB2, SIB3. SIB4, SIB5, SIB6, SIB7, SIB8, and / or SIB9.Example 11 : The method of any one of examples 8 to 10, wherein the first information includes one or more of: reduced-capability (RedCap) infomiation; further-reduced-capability (fRedCap) information; one or more System Information IE(s); and / or slice supporting information; and wherein the second information includes one or more of: the RedCap information; the fRedCap information; the one or more System Information IE(s); and / or the slice supporting information.Example 12: The method of example 11, wherein the RedCap information includes a RedCap Broadcast Information IE.Example 13: The method of any one of examples 8 to 12, the receiving of the first information for the first cell from the first DU comprising: receiving, from the DU, an Fl Setup Request message.Example 14: The method of any one of examples 8 to 13, comprising: receiving, from the DU, a DU Configuration Update message to update at least a portion of the first configuration information or the second configuration information; and in response to the receiving of the DU Configuration Update message, transmitting a DU Configuration Update Acknowledge message to the DU.Example 15: The method of 14, comprising: including new CU configuration information for the first cell in the DU Configuration Update Acknowledge message to update the CU configuration information included in a Fl Setup Response message.Example 16: The method of any one of claims 8 to 15, wherein the first UE type is a reduced-capability (RedCap) UE; wherein the second UE type is a further-reduced-capability (IRedCap) UE; and wherein the third UE type is a normal-capability UE.Example 17: A method for managing a reduced-capability user equipment (UE) by a distributed unit (DU) of a base station, the method comprising: performing a random access procedure with the UE; receiving a Media Access Control (MAC) Protocol Data Unit (PDU) from the UE in the random access procedure, the MAC PDU including a logical channel identifier (LCID) and a message; including the received message in a DU-to-CU message; identifying a value of the LCID. the value being a first value, a second value, or a third value; if the identified value is a first value or a second value, including an indication of a second- type of UE in the DU-to-CU message; and transmitting the DU-to-CU message to a Central Unit (CU).Example 18: A method for managing a reduced-capability user equipment (UE) by a distributed unit (DU) of a base station, the method comprising: broadcasting a first random access (RA) configuration;broadcasting a second RA configuration; broadcasting a third RA configuration; performing a random access procedure with the UE; receiving a Media Access Control (MAC) Protocol Data Unit (PDU) from the UE in the random access procedure, the MAC PDU including a logical channel identifier (LCID) and a message; including the received message in a DU-to-CU message; based on the RA configuration used for the random access procedure, if the RA configuration is the first RA configuration or the second RA configuration, including an indication of a first-type of UE in the DU-to-CU message; and transmitting the DU-to-CU message to a Central Unit (CU).Example 19: A method for managing a reduced-capability user equipment (UE) by a distributed unit (DU) of a base station, the method comprising: broadcasting a first random access (RA) configuration; broadcasting a second RA configuration; broadcasting a third RA configuration; performing a random access procedure with the UE; receiving a Media Access Control (MAC) Protocol Data Unit (PDU) from the UE in the random access procedure, the MAC PDU including a logical channel identifier (LCID) and a message; including the received message in a DU-to-CU message; based on the RA configuration used for the random access procedure, if the RA configuration is the first RA configuration or the second RA configuration, including an indication of a second-type of UE in the DU-to-CU message; and transmitting the DU-to-CU message to a Central Unit (CU).Example 20: A method for managing a reduced-capability user equipment (UE) by a distributed unit (DU) of a base station, the method comprising: transmitting a first DU-to-CU message to a CU, including first information for a first cell, the first infonnation indicating whether UEs of a first UE type are allowed to access the first cell; transmitting a second DU-to-CU message to the CU, including second information for the first cell, the second information indicating whether UEs of a second UE type are allowed to access the first cell; broadcasting the first infonnation on the first cell; andbroadcasting the second information on the first cell.Example 21 : A method for managing a reduced-capability user equipment (UE) by a distributed unit (DU) of a base station, the method comprising: transmitting a first DU-to-CU message to a CU, including first information and second information for a first cell, the first information indicating whether UEs of a first UE type are allowed to access the first cell and the second information indicating whether UEs of a second UE type are allowed to access the first cell; broadcasting the first information on the first cell; and broadcasting the second information on the first cell.Example 22: A method for managing a reduced-capability user equipment (UE) by a distributed unit (DU) of a base station, the method comprising: communicating with a UE and a Central Unit (CU); if the ty pe of the UE is a first type: generating a first configuration; and sending the first configuration to the CU; if the type of the UE is a second type: generating a second configuration; and sending the second configuration to the CU; if the type of the UE is a third type: generating a third configuration; and sending the third configuration to the CU.Example 23 : A method for managing a reduced-capability7user equipment (UE) by a distributed unit (DU) of a base station, the method comprising: communicating with a UE and a Central Unit (CU); if the type of the UE is a first type or a second ty pe: generating a second configuration; and sending the second configuration to the CU; if the type of the UE is a third type: generating a third configuration; and sending the third configuration to the CU.Example 24: A method for managing a reduced-capability user equipment (UE) by a central unit (CU) of a base station, the method comprising: receiving first information for a first cell from a first DU; identifying whether the first cell allows UEs of a first UE type to access based on the first information; configuring UEs of the first UE type to measure and / or access the first cell based on the identification that the first cell allows UEs of the first UE type to access; receiving second infonnation for the first cell from the first DU; identifying whether the first cell allows UEs of a second UE type to access based on the second information; and configuring UEs of the second UE type to measure and / or access the first cell based on the identification of whether the first cell allows UEs of the second UE type to access.Example 25: A method for managing a reduced-capability user equipment (UE) by a central unit (CU) of a base station, the method comprising: receiving cell information for a cell from a DU; if the cell infonnation includes first infonnation: if the first cell allows UEs of a first UE type to access based on the first information, configuring UEs of the first UE type to measure and / or access the first cell; if the cell information includes second information: if the first cell allows UEs of a second UE type to access based on the first information, configuring UEs of the second UE type to measure and / or access the first cell.Example 26: A method for managing a reduced-capability user equipment (UE) by a radio access network (RAN) node, the method comprising: configuring a first portion of radio resources for communication with UEs of a first UE type on a cell; configuring a second portion of radio resources for communication with UEs of a second UE type on the cell; configuring a third portion of radio resources for communication with UEs of a third UE type on the cell; communicating with UEs of the first UE type on the cell, using the first portion of radio resources; communicating with UEs of the second UE type on the cell, using the second portion of radio resources; andcommunicating with UEs of the third UE type on the cell, using the third portion of radio resources.Example 27 : A method for managing a reduced-capability user equipment (UE) by a radio access network (RAN) node, the method comprising: configuring a first portion of radio resources for communication with UEs of a first UE type on a cell; configuring the first portion of radio resources for communication with UEs of a second UE t pe on the cell; configuring a second portion of radio resources for communication with UEs of a third UE type on the cell; communicating with UEs of the first UE type on the cell, using the first portion of radio resources; communicating with UEs of the second UE type on the cell, using the first portion of radio resources; and communicating with UEs of the third UE type on the cell, using the second portion of radio resources.Example 28: An apparatus comprising: a processor; and computer-readable storage media comprising instructions that, responsive to execution by the processor, direct the apparatus to perform any method as recited in any one of examples 1 to 27.

Claims

CLAIMSWhat is claimed is:

1. A method for managing a reduced-capability user equipment (UE) by a distributed unit (DU) of a base station, the method comprising: performing a random access procedure with the UE; receiving a Media Access Control (MAC) Protocol Data Unit (PDU) from the UE in the random access procedure, the MAC PDU including a logical channel identifier (LCID) and a message; including the received message in a DU-to-CU message; identifying a value of the LCID, the value being a first value, a second value, or a third value; if the identified value is a first value, including an indication of a first-type of UE in the DU-to-CU message; if the identified value is a second value, including an indication of a first-type of UE in the DU-to-CU message; and transmitting the DU-to-CU message to a Central Unit (CU).

2. The method of claim 1, wherein the first value indicates that the UE is a reduced- capability (RedCap) UE; wherein the second value indicates that the UE is a further-reduced- capability (fRedCap) UE; and wherein the third value indicates that the UE is a normal-capability' UE.

3. The method of claim 1 or claim 2. wherein the message is a Radio Resource Control (RRC) request message.

4. The method of any one of the preceding claims, wherein the transmitting of the DU-to-CU message to the CU directs the CU to generate RRC response message for the UE, the method further comprising: receiving, from the CU, the RRC response message for the UE; and transmitting the RRC response message to the UE.

5. The method of claim 4, further comprising: receiving, from the UE, an RRC complete message; and transmitting the RRC complete message to the CU in an other DU-to-CU message.

6. The method of claim 5, wherein the RRC complete message is one of:RRCSetupComplete message; an RRCResumeComplete message; or an RRCReestablishmentComplete message.

7. The method of claim 4, wherein the RRC response message is one of: an RRCSetupRequest message; an RRCResumeRequest message; or an RRCReestablishmentRequest message.

8. A method of performing an Fl setup procedure with a first Distributed Unit (DU) by a Central Unit (CU), the method comprising: receiving first infonnation for a first cell from the first DU; based on the first information indicating that the first cell allows user equipments (UEs) of a first UE type to access the first cell, generating first configuration information for configuring UEs of the first UE t pe to measure and / or access the first cell; receiving second information for the first cell from the first DU; based on the second information indicating that the first cell allows UEs of a second UE type to access the first cell, generating second configuration information for configuring UEs of the second UE ty pe to measure and / or access the first cell; receiving third information for the first cell from the first DU; and based on the third information indicating that the first cell allows UEs of a third UE type of access the first cell, generating third configuration information for configuring UEs of the third type to measure and / or access the first cell.

9. The method of claim 8, comprising: transmitting, to the DU, an FI Setup Response message, including: the first configuration infonnation; the second configuration information; or both the first configuration infonnation and the second configuration information.

10. The method of claim 9, wherein the first configuration includes first System Information Block(s) (SIB(s)); wherein the first SIB(s) include one or more of SIB2, SIB3, SIB4, SIB5, SIB6, SIB7, SIB8, and / or SIB9; wherein the second configuration includes second SIB(s); and wherein the second SIB(s) include one or more of SIB2, SIB3. SIB4, SIB5, SIB6, SIB7, SIB8, and / or SIB9.

11. The method of any one of claims 8 to 10, wherein the first information includes one or more of: reduced-capability (RedCap) infomiation; further-reduced-capability (fRedCap) information; one or more System Information IE(s); and / or slice supporting information; and wherein the second information includes one or more of: the RedCap information; the fRedCap information; the one or more System Information IE(s); and / or the slice supporting infonnation.

12. The method of claim 11, wherein the RedCap infonnation includes a RedCap Broadcast Information IE.

13. The method of any one of claims 8 to 12, the receiving of the first information for the first cell from the first DU comprising: receiving, from the DU, an Fl Setup Request message.

14. The method of any one of claims 8 to 13, comprising: receiving, from the DU, a DU Configuration Update message to update at least a portion of the first configuration information or the second configuration information; and in response to the receiving of the DU Configuration Update message, transmitting a DU Configuration Update Acknowledge message to the DU.

15. The method of claim 14, comprising: including new CU configuration information for the first cell in the DU Configuration Update Acknowledge message to update the CU configuration information included in a Fl Setup Response message.

16. The method of any one of claims 8 to 15, wherein the first UE type is a reduced- capability (RedCap) UE; wherein the second UE type is a further-reduced-capability (fRedCap) UE; and wherein the third UE type is a normal-capability UE.

17. An apparatus comprising: a processor; and computer-readable storage media comprising instructions that, responsive to execution by the processor, direct the apparatus to perform any method as recited in any one of claims 1 to 16.

Images