User equipment with reduced management capability

Abstract

This document describes methods, apparatus, systems, and instrumentalities for managing reduced-capability user equipments (UEs) by a distributed base station. A distributed unit (DU) of a 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 a 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 (550) 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 the UE of the first type in a DU-to-CU message, and sends the DU-to-CU message (555) to a central unit (CU). If the identified value is a second value, the DU includes an indication of the UE of the second type in a DU-to-CU message, and sends the DU-to-CU message (555) to the CU.

Description

BACKGROUND

[0001] Wireless communication has evolved to fifth generation (5G) standards and technologies that provide higher data rates and greater capacity with improved reliability and lower latency, which enhances mobile broadband service. 5G technologies also provide new service categories for vehicle networking, fixed wireless broadband, and the Internet of Things (IoT). A 5G distributed base station architecture refers to a network design in which base stations are deployed in a distributed manner to enhance coverage, capacity, and efficiency by combining a central unit (CU) that handles multiple distributed units (DUs) for resource allocation and management, and DUs that handle lower-level tasks such as signal processing and radio transmission.

[0002] A unified air interface that utilizes licensed, unlicensed, and shared licensed radio spectrum in multiple frequency bands is one aspect of enabling 5G systems. The 5G air interface utilizes radio spectrum in sub-gigahertz (sub-1 GHz), 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 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] A capable user equipment (UE) can coexist with reduced-capability UEs. Reduced-capability UEs (also referred to as RedCap UEs) tend to have lower bandwidth capabilities, reduced processing capabilities, and / or fewer antennas compared to capable UEs. Depending on the device, RedCap UEs also lack support for dual connectivity and / or carrier aggregation. RedCap UEs have established a framework for implementing reduced-capability NR devices suitable for a range of use cases, including industrial sensors, video surveillance, and wearable devices, with requirements for low UE complexity, and sometimes low UE power consumption. In addition to RedCap UEs, there are also UEs with further reduced capabilities (fRedCap UEs). There is an opportunity to establish network access for UEs that are either capable UEs, RedCap UEs, or fRedCap UEs. 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 DETAILED DESCRIPTION. This summary is not intended to identify key features of the claimed subject matter, nor is it intended to be used in determining the scope of the claimed subject matter.

[0005] In various aspects, methods, apparatus, systems, and means for a user equipment (UE) whose management capabilities are reduced by a base station's distributed unit (DU) are described, which describe the DU performing a random access procedure with the UE. During the random access procedure, the DU receives a Media Access Control (MAC) Protocol Data Unit (PDU) from the UE. The MAC PDU includes a Logical Channel Identifier (LCID) and a message. The DU includes the received message in a DU-to-CU message and identifies the value of the LCID, which is a first value, a second value, or a third value. If the identified value is a first value, the DU includes an indication for a first type of UE in the DU-to-CU message and sends the DU-to-CU message to the central unit (CU). If the identified value is a second value, the DU includes an indication for a second type of UE in the DU-to-CU message and sends the DU-to-CU message to the CU.

[0006] On the other hand, methods, apparatus, systems, and means for managing user equipment (UE) with reduced management capabilities by a central unit (CU) of a base station describe how the CU receives first information for a first cell from a first distributed unit (DU). Based on the first cell, a UE of a first UE type is allowed to access the first cell, and based on the first information, the CU generates first configuration information for configuring a UE of the first UE type to perform measurements 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, a UE of a second UE type is allowed to access the first cell, and based on the second information, the CU generates second configuration information for configuring a UE of the second UE type to perform measurements and / or access the first cell. Attached Figure Description

[0007] The following describes in detail one or more aspects of user equipment with reduced manageability. The same reference numerals are used in different instances in the specification and figures to indicate the same elements: Figure 1 An example wireless network system is shown in which various aspects of user equipment with reduced management capabilities can be implemented.

[0008] Figure 2 An example device diagram is shown that can realize various aspects of user equipment with reduced management capabilities.

[0009] Figure 3 An example block diagram of a wireless network stack model is shown, based on one or more aspects of user equipment with reduced management capabilities.

[0010] Figure 4 An example wireless network protocol stack is shown, which can implement various aspects of user equipment with reduced management capabilities.

[0011] Figure 5An example of data and control transactions between devices is shown, based on one or more aspects of a user device with reduced management capabilities.

[0012] Figure 6 An example of data and control transactions between devices is shown, based on one or more aspects of a user device with reduced management capabilities.

[0013] Figure 7 An example of data and control transactions between devices is shown, based on one or more aspects of a user device with reduced management capabilities.

[0014] Figure 8 An example of data and control transactions between devices is shown, based on one or more aspects of a user device with reduced management capabilities.

[0015] Figure 9 An example of data and control transactions between devices is shown, based on one or more aspects of a user device with reduced management capabilities.

[0016] Figure 10 An example of data and control transactions between devices is shown, based on one or more aspects of a user device with reduced management capabilities.

[0017] Figure 11 An example method is shown for identifying a cell-supported UE based on one or more aspects of a user equipment with reduced management capabilities.

[0018] Figure 12 An example method is shown for identifying a cell-supported UE based on one or more aspects of a user equipment with reduced management capabilities.

[0019] Figure 13 An example method is shown for identifying a cell-supported UE based on one or more aspects of a user equipment with reduced management capabilities.

[0020] Figure 14 An example method is shown for identifying a cell-supported UE based on one or more aspects of a user equipment with reduced management capabilities.

[0021] Figure 15 An example method is shown where a base station distributed unit allows access to multiple types of UEs based on one or more aspects of a user equipment with reduced management capabilities.

[0022] Figure 16 An example method is shown where a base station distributed unit allows access to multiple types of UEs based on one or more aspects of a user equipment with reduced management capabilities.

[0023] Figure 17An example method for generating configurations from a DU based on one or more aspects of a user device with reduced management capabilities is shown.

[0024] Figure 18 An example method for generating configurations from a DU based on one or more aspects of a user device with reduced management capabilities is shown.

[0025] Figure 19 An example method for generating configurations from the CU based on one or more aspects of a user device with reduced management capabilities is shown.

[0026] Figure 20 An example method for generating configurations from the CU based on one or more aspects of a user device with reduced management capabilities is shown.

[0027] Figure 21 An example method is shown where a RAN node generates a configuration based on one or more aspects of a user equipment with reduced management capabilities.

[0028] Figure 22 An example method is shown where a RAN node generates a configuration based on one or more aspects of a user equipment with reduced management capabilities. Detailed Implementation

[0029] This document describes methods, apparatus, systems, and means for identifying configurations for connections between a Radio Access Network (RAN) and UEs of various capability levels. In telecommunications systems, the Packet Data Convergence Protocol (PDCP) sublayer of the radio network protocol stack provides services such as user plane data delivery, encryption, and integrity protection. For example, the PDCP layer for the Evolved Universal Terrestrial Radio Access (EUTRA) radio interface and New Radio (NR) definitions provides the ordering of Protocol Data Units (PDUs) in the uplink (UL) direction (from the user equipment, also referred to as the user equipment (UE), to the base station) and in the downlink (DL) direction (from the base station to the UE). Furthermore, the PDCP sublayer provides Signaling Radio Bearer (SRB) services to the Radio Resource Control (RRC) sublayer. The PDCP sublayer also provides Data Radio Bearer (DRB) services to the Serving Data Adaptation Protocol (SDAP) sublayer or protocol layers such as the Internet Protocol (IP) layer, Ethernet layer, and Internet Control Message Protocol (ICMP) layer. Generally, the UE and the base station use SRB to exchange RRC messages and non-access stratum (NAS) messages, and use DRB to transmit data on the user plane.

[0030] Base stations operating according to modern requirements support significantly greater bandwidth than those operating according to older standards. Therefore, a modern, fully functional UE can support 100 MHz bandwidth in frequency range 1 (FR1) and 400 MHz bandwidth in frequency range 2 (FR2). However, a fully functional UE can coexist with several types of degraded UEs, such as RedCap and fRedCap. Distributed base stations with DU and CU components can use various methods to distinguish between these three types of UEs.

[0031] Example Environment

[0032] Figure 1 An example environment 100 including user equipment 110 (UE 110) is shown, which can communicate with base station 120 (shown as base station 121 and 122) via one or more wireless communication links 130 (wireless links 130) (shown as wireless links 131 and 132). For simplicity, UE 110 is implemented as a smartphone, but can be implemented as any suitable computing or electronic device, such as a mobile communication device, modem, cellular phone, gaming device, navigation device, media device, laptop computer, desktop computer, tablet computer, smart appliance, vehicle-based communication system, or Internet of Things (IoT) device (such as a sensor or actuator). Base station 120 (e.g., 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, etc.) can be implemented in macro cells, micro cells, small cells, pico cells, distributed base stations, etc., or any combination thereof or future evolution thereof. Although the base station icon represents a terrestrial network (TN), base station 120 can be implemented using non-terrestrial network (NTN) components such as satellite gateways, satellites, aircraft, drones, and other high-altitude platforms (HAPS). Nothing in this document should be construed as limiting oneself to current wireless standards and associated network components.

[0033] Base station 120 uses radio links 131 and 132 to communicate with user equipment 110, which can be implemented as any suitable type of radio link. Radio links 131 and 132 include control and data communications, such as downlinks transmitting data and control information from base station 120 to user equipment 110, uplinks transmitting other data and control information from user equipment 110 to base station 120, or both. Radio link 130 may include one or more radio links (e.g., radio links) or bearers implemented using any suitable communication protocol or standard or combination of communication protocols or standards (such as 3GPP LTE, 5G NR, etc.). Multiple radio links 130 can be aggregated in carrier aggregation to provide higher data rates for UE 110. Multiple radio links 130 from multiple base stations 120 can be configured for coordinated multipoint (CoMP) communication with UE 110 and dual connectivity, such as single RAT LTE-LTE or NR-NR dual connectivity or multiple radio access technology (multiple 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).

[0034] Base station 120 collectively serves as radio access network 140 (e.g., RAN, Evolved Universal Terrestrial Radio Access Network E-UTRAN, 5G NR RAN, or NR RAN). Base stations 121 and 122 in RAN 140 are connected to 5G core network 150 (5GC 150). Base stations 121 and 122 are connected to 5GC 150 at locations 101 and 102, respectively, via NG interfaces for control plane signaling. Base stations 121 and 122 are connected to 5G core network 150 at locations 101 and 102, respectively, via NG2 interfaces for control plane signaling, and use NG3 interfaces for user plane data communication.

[0035] 5GC 150 includes Access and Mobility Management Function 152 (AMF 152), which provides control plane functions such as registration and authentication, authorization, and mobility management in the 5G NR network for multiple UEs 110. AMF 152 communicates with base station 120 in RAN 140 and also uses base station 120 to communicate with multiple UEs 110.

[0036] Base station 121 is shown as a non-distributed base station, and base station 122 is shown as a distributed base station implemented using a central node-distributed node architecture. Base station 122 includes a gNB-central unit (gNB-CU) 160 and multiple gNB-distributed units (gNB-DUs) 170 (shown as gNB-DUs 171 and 172). Although in Figure 1 Two gNB-DU 170s are shown for clarity, but any appropriate number of gNB-DUs can be interfaced to gNB-CU 160.

[0037] At point 103, base stations 121 and 122 can communicate via the Xn interface using the Xn Application Protocol (XnAP) to exchange user plane and control plane data. Base stations 121 and 122 also communicate at point 103 via the Xn-C interface for control plane communication. In base station 122, which uses a central node-distributed node architecture, the Xn-C interface 103 is terminated by gNB-CU 160.

[0038] In a central node-distributed node architecture, gNB-CU 160 is a logical node that hosts the Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), and Packet Data Convergence Protocol (PDCP) layer protocols of a gNB, or the RRC and PDCP layer entities of an en-gNB (e.g., a gNB connected to an evolved packet core). gNB-CU 160 partially controls the operation of one or more gNB-DU 170s. gNB-CU 160 includes an F1 interface for communicating with gNB-DU 170s, as shown at 104 and 105. Although described as a logical node, gNB-CU 160 and / or gNB-DU 170 devices may include... Figure 3 Any suitable components described in the section regarding base station 120.

[0039] The gNB-DU 170 is a logical node that hosts the Radio Link Control (RLC), Media Access Control (MAC), and Physical (PHY) layer protocols for a gNB or en-gNB. The operation of the gNB-DU 170 is partially controlled by the gNB-CU 160. One gNB-CU 160 supports one or more cells in RAN 140, but a single cell is supported by only one gNB-DU 170. Each gNB-DU 170 terminates its F1 interface at a gNB-CU 160, which serves as the central unit for that gNB-DU 170. Each gNB-DU 170 is operatively connected to only one gNB-CU 160. Alternatively or optionally, for resilience in network operation, the gNB-DU 170 can be connected to multiple gNB-CU 170s using any suitable implementation, such as network interconnection hardware and / or software that provides failover for the gNB-DU 170 to the backup gNB-CU 160 in the event of failure of the primary gNB-CU 160 or its unavailability to the gNB-DU 170.

[0040] Example device

[0041] Figure 2 Example device diagram 200 of UE 110 is shown. UE 110 may include, for clarity, components from... Figure 2 Additional functions and interfaces are omitted. User equipment 110 includes an antenna 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 station 120 in RAN 140. The RF front-end 204 of UE 110 can couple or connect the LTE transceiver 206 and the 5G NR transceiver 208 to the antenna 202 to facilitate various types of wireless communication. The antenna 202 of UE 110 may include an array of multiple antennas configured similarly or differently from each other. The antenna 202 and the RF front-end 204 can be tuned to and / or are capable of being tuned 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, antenna 202, RF front-end 204, LTE transceiver 206, and / or 5G NR transceiver 208 can be configured to support beamforming for transmitting and receiving communications with UE 120. By way of example, and not limitation, antenna 202 and RF front-end 204 can be implemented for operation in sub-gigahertz, sub-6 GHz, and / or above 6 GHz frequency bands as defined by the 3GPP LTE and 5G NR communication standards.

[0042] User equipment 110 also includes a processor 210 and a computer-readable storage medium 212 (CRM 212). The processor 210 may be a single-core or multi-core processor constructed from various materials, such as silicon, polysilicon, high-k dielectrics, copper, etc. The computer-readable storage medium described herein excludes propagating signals. CRM 212 may include any suitable memory or storage device that can be used to store device data 214 of user equipment 110, such as random access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), non-volatile RAM (NVRAM), read-only memory (ROM), or flash memory. Device data 214 includes user data, multimedia data, beamforming codebooks, applications, and / or the operating system of user equipment 110, which can be executed by the processor 210 to enable user plane communications, control plane signaling, and user interaction with UE 110.

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

[0044] Figure 3 An example apparatus diagram 300 for a distributed base station 122 is shown. The base station 122 may include, for clarity, components from... Figure 3 Additional features and interfaces omitted in the text.

[0045] Figure 3 The arrangement diagram of base station 122 shown is distributed across multiple network nodes or devices (e.g., CU 160 and one or more DU 170), and can be distributed in any manner suitable for performing the functions described herein. The nomenclature for this split-type base station functionality varies and includes terms such as Central Unit (CU), Distributed Unit (DU), Baseband Unit (BBU), Remote Radio Header (RRH), and / or Remote Radio Unit (RRU).

[0046] CU 160 includes a processor 302 and a computer-readable storage medium 304 (CRM 304). The processor 302 can be a single-core or multi-core processor made of various materials, such as silicon, polysilicon, high-k dielectrics, copper, etc. The CRM 304 can include any suitable memory or storage device that can be used to store device data 306 of the CU 160, such as random access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), non-volatile RAM (NVRAM), read-only memory (ROM), or flash memory. Device data 306 includes network scheduling data, radio resource management data, beamforming codebooks, applications, and / or the operating system of the CU 160, executable by the processor 302 to enable communication with user equipment 110.

[0047] CRM 304 also includes CU Manager 308. Alternatively or additionally, the basic CU Manager 308 may be implemented, in whole or in part, as a hardware logic or circuit system integrated with or separate from other components of CU 160. In at least some aspects, CU Manager 308 configures DU 170 for communication with User Equipment 110 and with the core network (such as core network 150), and routes user plane and control plane data for joint communication. Additionally, CU Manager 308 includes the Radio Resource Control (RRC) layer, Service Data Adaptation Protocol (SDAP) layer, and Packet Data Convergence Protocol (PDCP) layer of the Wireless Network Protocol Stack 400.

[0048] CU 160 includes an F1 interface 310 for exchanging user plane and control plane data with DU 170. CU 160 also includes an inter-base station interface 312, such as an Xn and / or X2 interface, which CU manager 308 configures to exchange user plane and control plane data between other base stations 120 to manage communication between base station 120 and user equipment 110.

[0049] Figure 3The device diagram of DU 170 shown includes an antenna 352, an 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 communication with UE 110. The RF front-end 354 of DU 170 can couple or connect the LTE transceivers 356 and 5G NR transceivers 358 to the antenna 352 to facilitate various types of wireless communication. The antenna 352 of DU 170 may include an array of multiple antennas configured similarly or differently from each other. The antenna 352 and RF front-end 354 can be tuned to and / or are capable of being tuned to one or more frequency bands defined by the 3GPP LTE and 5G NR communication standards and implemented by the LTE transceivers 356 and / or one or more 5G NR transceivers 358. Additionally, antenna 352, RF front end 354, LTE transceiver 356 and / or one or more 5G NR transceivers 358 can be configured to support beamforming, such as massive MIMO, for transmitting and receiving communications with UE 110.

[0050] The DU 170 also includes a processor 360 and a computer-readable storage medium 362 (CRM 362). The processor 360 can be a single-core or multi-core processor made of various materials, such as silicon, polysilicon, high-k dielectrics, copper, etc. The CRM 362 can include any suitable memory or storage device that can be used to store device data 364 of the DU 170, such as random access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), non-volatile RAM (NVRAM), read-only memory (ROM), or flash memory. Device data 364 includes network scheduling data, radio resource management data, beamforming codebooks, applications, and / or the operating system of the DU 170, executable by the processor 360 to enable communication with user equipment 110.

[0051] CRM 362 also includes DU manager 366. Alternatively or additionally, the basic DU manager 366 may be implemented, in whole or in part, as a hardware logic or circuit system integrated with or separate from other components of DU 170. In at least some aspects, DU manager 366 configures LTE transceiver 356 and 5G NR transceiver 358 for communication with user equipment 110 and with CU 160. Additionally, DU manager 366 can allocate air interface resources and schedule communications for UE 110. DU 170 includes an F1 interface 368 used by the DU to exchange user plane and control plane data with CU 160.

[0052] Wireless Network Protocol Stack

[0053] Figure 4A simplified example protocol stack 400 is shown for UE 110 to communicate with DU 170 and CU 160. The radio protocol stack 400 is functionally split between CU 160 and DU 170. In the example stack 400, the Physical Layer (PHY) 402 provides hardware specifications for devices communicating with each other. Therefore, the PHY layer 402 establishes how devices connect to each other, helps manage how communication resources are shared between devices, etc. The PHY layer 402 provides a transport channel to the Media Access Control (MAC) layer 404. The MAC layer 404 specifies how data is transferred between devices. Typically, the MAC layer 404, as part of the transport protocol, provides how data packets being transmitted are encoded and decoded into bits. The MAC layer 404 then provides a logical channel to the RLC sublayer 406. The RLC layer 406 provides data transfer services to higher layers in stack 400. Typically, RLC layer 406 provides error correction, packet splitting and reassembly, and management of data transfer in various modes, such as acknowledged mode, unacknowledged mode, or transparent mode.

[0054] RLC layer 406 then provides the RLC channel to PDCP layer 408. PDCP layer 408 provides data delivery services to higher layers in stack 400. Typically, PDCP layer 408 provides delivery, header compression, encryption, and integrity protection for user plane and control plane data.

[0055] In 5G NR, the PDCP sublayer 408 can then provide data delivery services to the Serving Data Adaptation Protocol (SDAP) layer 410. The optional SDAP layer 410 exists in the 5G NR network. The SDAP layer 410 maps the Quality of Service (QoS) flow for each data radio bearer and marks QoS flow identifiers in the uplink and downlink data packets of each packet data session.

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

[0057] Managing RedCap UE

[0058] Figures 5 to 10 A message passing diagram illustrating an example scenario of a RAN node identifying a UE's capability type during connection establishment is shown. UE types can correspond to different capability types of a UE. For example, this disclosure refers to a UE with reduced capability as a first UE type, a UE with further reduced capability as a second UE type, and a UE with normal capability as a third UE type. Although three UE capability types are discussed throughout this disclosure, the described techniques are applicable to distinguishing a larger number of UE capability types (if they are defined in the future).

[0059] First go to Figure 5 In scenario 500, base station 120 includes CU 160 and DU 170. In each aspect, DU 170 initiates an F1 setup procedure (502) with CU 160 by sending an F1 setup request message (505) to CU 160. In response, CU 160 sends an F1 setup response message (510) to DU 170. Depending on the aspect, DU 170 includes DU configuration information for one or more cells in the F1 setup request message. In some aspects, the DU configuration information includes RedCap information, fRedCap information, configuration for a UE with normal capabilities, system information elements (IE), and / or slice support information, as described below. In some aspects, CU 160 includes CU configuration information for one or more cells in the F1 setup response message. The F1 setup request message and the F1 setup response message are non-UE-associated signaling messages.

[0060] In a further aspect, DU 170 includes RedCap information (e.g., IE) in the F1 setup request message. In some aspects, DU 170 configures RedCap information for the corresponding cell operated by DU 170, and the RedCap information indicates whether a RedCap UE is allowed to access the corresponding cell. In some aspects, RedCap UEs can be grouped into different types, such as RedCap UEs with one receive chain or antenna, RedCap UEs with two receive chains or antennas, and RedCap UEs supporting half-duplex operation. In some aspects, RedCap information indicates which types of UEs are allowed to access the corresponding cell. In some aspects, CU 160 uses RedCap information to identify whether the corresponding cell is a suitable target cell in cases involving subsequent outbound mobility of the RedCap UE.

[0061] In some respects, RedCap information is a RedCap broadcast information IE. In other respects, the DU 170 includes RedCap information in the RedCap broadcast information IE within the F1 setup request message. In some respects, the DU 170 includes multiple RedCap information sets, one for each corresponding cell in the F1 setup request message. In some respects, multiple RedCap information sets may have the same content or different content. In some respects, RedCap information is specific to a specific type of RedCap UE that supports a specific RedCap functionality (e.g., a 3GPP version 17 RedCap UE that supports the RedCap functionality defined in 3GPP version 17).

[0062] In some aspects, DU 170 includes fRedCap information (e.g., IE) in the F1 setup request message. This fRedCap information differs from the RedCap information previously described. In some aspects, DU 170 configures fRedCap information for the corresponding cell operated by DU 170, and the fRedCap information indicates whether an fRedCap UE is allowed to access the corresponding cell. In some aspects, fRedCap UEs can be grouped into different types, such as fRedCap UEs with one receive chain or antenna, fRedCap UEs with two receive chains or antennas, and fRedCap UEs supporting half-duplex operation. In some aspects, the fRedCap information indicates which types of UEs are allowed to access the corresponding cell. In some aspects, CU 160 uses the fRedCap information to identify whether the corresponding cell is a suitable target cell in cases involving subsequent outbound mobility of the fRedCap UE.

[0063] In some respects, fRedCap information is a different fRedCap broadcast information IE from the RedCap broadcast information IE. In other respects, DU 170 includes fRedCap information in the RedCap broadcast information IE within the F1 setup request message. In such cases, DU 170 includes both RedCap information and fRedCap information in the RedCap broadcast information IE for the corresponding cell within the F1 setup request message. In some respects, DU 170 includes multiple fRedCap information sets, one for each corresponding cell in the F1 setup request message. In some respects, multiple fRedCap information sets may have the same content or different content. In some respects, fRedCap information is specific to a specific type of fRedCap UE that supports a specific fRedCap functionality (e.g., a 3GPP Release 18 fRedCap UE, and supports the fRedCap functionality defined in 3GPP Release 18).

[0064] In some aspects, the DU 170 includes a System Information IE for the cell operated by the DU 170 in the F1 setup request message. In some aspects, the System Information IE includes a Master Information Block (MIB) and / or one or more System Information Blocks (SIBs). In some aspects, the DU 170 configures the MIB and SIB for a capable UE, a RedCap UE, and / or an fRedCap UE. In other aspects, the DU 170 includes a first System Information IE and a second System Information IE for the cell operated by the DU 170 in the F1 setup request message. In some aspects, the first System Information IE includes the MIB and / or SIB for a capable UE, and the second System Information IE includes the MIB and / or SIB for a RedCap UE and / or an fRedCap UE. In still other aspects, the DU 170 includes a first System Information IE, a second System Information IE, and a third System Information IE for the cell operated by the DU 170. In some aspects, the first system information IE includes MIBs and / or SIBs for a normally functioning UE, the second system information IE includes MIBs and / or SIBs for a RedCap UE, and / or the third system information IE includes MIBs and SIBs for a RedCap UE. In some aspects, the aforementioned SIBs include SIB1, SIB17, and / or SIB20.

[0065] In some aspects, the F1 setup request message includes slice support information (e.g., IE) for the corresponding cell operated by the DU 170. The slice support information indicates one or more slices supported on the corresponding cell for a capable UE, a RedCap UE, and / or a fRedCap UE. In other aspects, the F1 setup request message includes first slice support information (e.g., IE) and second slice support information (e.g., IE) for the corresponding cell operated by the DU 170. The first slice support information indicates one or more slices supported on the corresponding cell for a capable UE, and the second slice support information indicates one or more slices supported on the corresponding cell for a RedCap UE and / or a fRedCap UE. In yet another aspect, the F1 setup request message includes first slice support information (e.g., IE), second slice support information (e.g., IE), and third slice support information (e.g., IE) for the corresponding cell operated by the DU 170. The first slice support information indicates one or more slices supported on the corresponding cell for a UE with normal capabilities; the second slice support information indicates one or more slices supported on the corresponding cell for a RedCap UE; and the third slice support information indicates one or more slices supported on the corresponding cell for a RedCap UE.

[0066] In some aspects, CU configuration information includes SIBs. For example, SIBs include SIB2, SIB3, SIB4, SIB5, SIB6, SIB7, SIB8, and / or SIB9. In other aspects, CU configuration information is different for each cell.

[0067] In some respects, DU 170 may initiate a DU configuration update procedure with CU 160 to update at least a portion of the DU configuration information. After initiating the DU configuration update procedure, DU 170 sends a DU configuration update message (515) to CU 160, including new DU configuration information, to update the DU configuration information included in the F1 setup request message. In some respects, the new DU configuration information includes new RedCap information, new fRedCap information, new system information IE, and / or new slice support information. In response to the DU configuration update message, CU 160 sends a DU configuration update confirmation message (520) to DU 170. In some respects, CU 160 includes new CU configuration information for one or more cells in the DU configuration update confirmation message to update the CU configuration information in the F1 setup response message. In some alternative respects, DU 170 sends a DU configuration update message (515) to CU 160, including DU configuration information or at least a portion of the DU configuration information instead of the F1 setup request message. In some respects, CU 160 includes CU configuration information for one or more cells in the DU configuration update confirmation message, as described in the F1 setup response message. The DU configuration update message and the DU configuration update confirmation message are non-UE-associated signaling messages.

[0068] In some aspects, DU 170 and CU 160 perform separate procedures to send different configuration information to CU 160 for a capable UE, a RedCap UE, and / or a fRedCap UE. For example, DU 170 performs a first procedure with CU 160 by sending a first message to CU 160 including first configuration information for a capable UE. In response, CU 160 sends a second message to DU 170. DU 170 performs a second procedure with CU 160 by sending a third message to CU 160 including second configuration information for a RedCap UE and / or a fRedCap UE. In response, CU 160 sends a fourth message to DU 170. In some alternative aspects, DU 170 performs a second procedure with CU 160 by sending a third message to CU 160 including second configuration information for a RedCap UE, and a third procedure with CU 160 by sending a fifth message to CU 160 including third configuration information for a fRedCap UE.

[0069] In some aspects, CU 160 sends a fourth and a sixth message to DU 170 in response to the third and fifth messages, respectively. In some aspects, the process includes an F1 setting process and / or a DU configuration update process. When the process is an F1 setting process, the first, third, and / or fifth messages are F1 setting request messages, and the second, fourth, and / or sixth messages are F1 setting response messages. When the process is a DU configuration update process, the first, third, and / or fifth messages are F1 setting request messages, and the second, fourth, and / or sixth messages are F1 setting response messages.

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

[0071] In some respects, UE 110 initially operates in an idle state (e.g., RRC_IDLE state), an inactive state (e.g., RRC_INACTIVE state), or a connected state with a fault (e.g., radio link failure) (e.g., RRC_CONNECTED state), or more generally in a state where there is no active radio connection between UE 110 and base station 120 (530).

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

[0073] In the two-step process, UE 110 sends (535) a random access (RA) preamble and (545) a payload or “MsgA” to DU 170 (step 1), and DU 170 sends a contention resolution or “MsgB” to UE 110 (step 2). More specifically, MsgA comprises two parts sent at different times: the RA preamble sent via the Physical Random Access Channel (PRACH) (e.g., similar to Msg1 in the four-step process), and the payload sent via the PUSCH (e.g., similar to Msg3 in the four-step process). The payload includes a UL MAC PDU, which includes an LCID and an RRC request. In some respects, the LCID identifies the UL logical channel used for the RRC request. For example, the UL logical channel is the UL Common Control Channel (CCCH).

[0074] In some aspects, if UE 110 operates in an idle or inactive state (530), the RRC request message signals a transition to a connected state (e.g., an RRCSetupRequest message or an RRCResumeRequest message). In a further aspect, if UE 110 operates in a connected state (530), the RRC request message instructs recovery from a radio link failure or other fault (e.g., an RRCReestablishmentRequest message). In some aspects, UE 110 generates a UL-CCCH-Message message including the RRC request message and includes the UL-CCCH-Message message in a UL MACPDU (545). In other aspects, UE 110 generates a UL-CCCH1-Message message including the RRC request message and includes the UL-CCCH1-Message message in a UL MAC PDU (545). In this specification, in some aspects, the RRC request message is equivalent to the UL-CCCH-Message message or the UL-CCCH1-Message message.

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

[0076] After classifying UE 110 as a second UE type, DU 170 sends a (555) DU to CU message to CU 160. The DU to CU message includes an RRC request and an indication of a first UE type, but not an indication of a second UE type. In some respects, the DU to CU message is the initial UL RRC message delivery message. If DU 170 indicates (550) UE 110 as a first UE type, then DU 170 sends a (555) DU to CU message to CU 160. When CU 160 receives the (555) DU to CU message, CU 160 classifies (560) UE 110 as a first UE type based on that indication.

[0077] Using the same indication for both the first and second UE types in DU 170 offers several advantages. First, using the same indication simplifies UE handling in CU 160. That is, CU 160 manages both the first and second UE types in the same way. Second, when the first UE type is a RedCap UE, the indication for RedCap UEs is already defined (e.g., in 3GPP Release 17). Therefore, this approach avoids defining new indications for fRedCap UEs in the DU-to-CU message (e.g., in 3GPP Release 18) and eliminates the need to update CU 160 to support fRedCap UEs separately from RedCap UEs.

[0078] In some aspects (not shown), CU 160 sends a BS-to-CN message to the CN (e.g., CN 150) or AMF (e.g., AMF 152), which includes an indication of a first UE type for UE 110. Therefore, in some such aspects, CN 150 classifies UE 110 as a first UE type based on the indication of the first UE type—even when the UE is not a first UE type. In some aspects, CN 150 applies a charging policy or rate for the first UE type of UE 110 based on this indication or classification to charge for data traffic transmitted with UE 110. In some such cases, CN 150 applies the same charging policy or rate for the first UE type and the second UE type, and a different charging policy or rate for the third UE type. In some aspects, the BS-to-CN message is an initial UE message. In some aspects (not shown), AMF 152 sends a message including an indication of the first UE type to the Session Management Function (SMF) after receiving the BS-to-CN message. Therefore, in some aspects, the SMF takes appropriate action for UE 110 based on an indication of the first UE type. For example, the SMF interacts with the User Plane Function (UPF) to manage user plane resources for UE 110 and / or ensure that data for UE 110 is correctly routed and / or forwarded based on the indication of the first UE type. In another example, the SMF may send an SMF-UPF message to the UPF that includes an indication of the first UE type. Thus, the UPF manages user plane resources for UE 110 based on the indication of the first UE type.

[0079] In some respects (not shown), if DU 170 identifies (550) UE 110 as a third UE type, DU 170 avoids including an indication of the UE type in the DU-to-CU message (555). In other respects (not shown), if DU 170 identifies (550) UE 110 as a third UE type, DU 170 includes an indication of the third UE type in the DU-to-CU message (555).

[0080] In response to the RRC request message, CU 160 generates an RRC response message for UE 110 and sends a CU-DU message (565) including the RRC response message to DU 170. DU 170 then sends an RRC response message (570) to UE 110. In some respects, DU 170 includes the LCID and the RRC response message in a DL MAC PDU and sends a DL MAC PDU (570) to UE 110. In some respects, the LCID identifies the DL logical channel to which the RRC response message belongs. For example, the DL logical channel is the DL Common Control Channel (CCCH). In some respects, CU 160 generates a DL-CCCH-Message message including the RRC response message and includes the DL-CCCH-Message message in a DL MAC PDU (570). In this specification, in some respects, the RRC response message is equivalent to the DL-CCCH-Message message.

[0081] In some respects, depending on whether the RRC request message (545) is an RRCSetupRequest, RRCResumeRequest, or RRCReestablishmentRequest message, the RRC response message (565, 570) is an RRCSetup, RRCResume, or RRCReestablishment message. In some respects, the RRC response message (570) is an RRC rejection message (e.g., an RRCReject message) in response to the RRCSetupRequest or RRCResumeRequest message. In some respects, if the RRC response message is neither an RRC rejection nor an RRC release message, the UE 110 transitions (575) to the connected state and sends an RRC completion message (580) to the DU 170 in response to the RRC response message. The DU 170 then sends an RRC completion message (585) to the CU 160. Depending on the implementation, the RRC completion message is either the RRCSetupComplete message, the RRCResumeComplete message, or the RRCReestablishmentComplete message, depending on the RRC response message (570).

[0082] In some respects, UE 110 includes the LCID and RRC completion message in a UL MAC PDU and sends (545) a UL MAC PDU to DU 170. In some respects, the LCID identifies the UL logical channel used for the RRC completion message. For example, the UL logical channel is the UL Dedicated Control Channel (DCCH). DU 170 retrieves (550) the LCID and RRC completion message from the UL MAC PDU and sends (555) a DU-CU message including the RRC completion message to CU 160. In some respects, UE 110 generates a UL-DCCH-Message message including the RRC completion message, generates a UL PDCP PDU including a UL-CCCH-Message message, generates a UL RLC PDU including the UL PDCP PDU, and includes the UL RLC PDU in a UL MAC PDU (580). In this specification, in some respects, the RRC completion message is equivalent to the UL-DCCH-Message message.

[0083] In some respects, if the RRC response message is an RRC rejection message or an RRC release message, then UE 110 remains in its original state as in event 530 and avoids sending an RRC completion message to base station 120.

[0084] In some respects, after identifying UE 110 as a second UE type (550), DU 170 includes the configuration parameters (e.g., cell group configuration) supported by the second UE type of UE 110 in the DU to CU message (555). CU 160 includes the configuration parameters in the RRC response message. In some respects, if DU 170 identifies UE 110 as a first UE type, DU 170 still includes the configuration parameters supported by the second UE type of UE 110 in the DU to CU message (555). In such a case, DU 170 unifies the configurations of the first and second UE types. In other respects, if DU 170 identifies UE 110 as a first UE type, DU 170 includes the configuration parameters (e.g., cell group configuration) supported by the first UE type of UE 110 in the DU to CU message (555). In such a case, the second UE type may not support the configuration parameters supported by the first UE type. In some respects, if DU 170 identifies UE 110 as a third UE type, then DU 170 includes the configuration parameters (e.g., cell group configuration) supported by the third UE type for UE 110 in the DU-to-CU message (555). In such a case, the first UE type and the second UE type may not support the configuration parameters supported by the third UE type.

[0085] In some aspects, DU 170 generates a first downlink control information (DCI) including parameters for the UE to receive downlink transmissions and transmit uplink transmissions. In some aspects, based on this identification (550), DU 170 generates parameters conforming to predetermined capabilities for a second UE type. DU 170 sends the first DCI to UE 110 before sending (570) a DL MAC PDU, such that, in some aspects, UE 110 configures itself according to the first DCI to receive (570) a DL MAC PDU. Similarly, in a further aspect, if DU 170 identifies UE 110 as a first UE type, DU 170 generates a second DCI for UE 110, including parameters supported by the first UE type. In some aspects (not shown), base station 120 sends the second DCI to UE 110 before sending (570) a DL MAC PDU. Alternatively, if DU 170 identifies UE 110 as a first UE type, DU 170 generates a second DCI for UE 110 similar to the first DCI, which includes parameters supported by the second UE type. In some aspects, base station 120 sends the second DCI to UE 110 before sending the (570) DL MAC PDU. Similarly, in a further aspect (not shown), if DU 170 identifies UE 110 as a third UE type, DU 170 generates a third DCI for UE 110, which includes parameters supported by the third UE type. In some aspects (not shown), base station 120 sends the third DCI to UE 110 before sending the (570) DL MAC PDU.

[0086] In some cases, regarding the first DCI, DU 170 includes parameters of the PDSCH transmission scheduled to UE 110 in the first DCI, wherein the PDSCH transmission includes a 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, DU 170 sets the first time-domain resource assignment field to a first value conforming to one or more predetermined capabilities for a second UE type. In a further aspect, DU 170 sets the first time-domain resource assignment field to a first predetermined value. In some aspects, DU 170 sets the first frequency-domain resource assignment field to a first value conforming to one or more predetermined capabilities for a second UE type. In a further aspect, DU 170 sets the first frequency-domain resource assignment field to a first predetermined value. In such aspects, UE 110 receives PDSCH transmissions at time-domain resources (e.g., symbols) and / or in frequency-domain resources according to the first time-domain resource assignment field.

[0087] In some aspects, DU 170 includes a first PDSCH to HARQ feedback timing indicator in the first DCI. In some aspects, DU 170 sets the first PDSCH to HARQ feedback timing indicator to a first value that conforms to one or more predetermined capabilities for a second UE type. Therefore, in some such aspects, UE 110 sends HARQ feedback based on the first value. In further aspects, DU 170 sets the first PDSCH to HARQ feedback timing indicator to a predetermined value. Depending on the implementation, the HARQ feedback is either a HARQ acknowledgment or a HARQ negative acknowledgment.

[0088] In some cases, regarding the second DCI, DU 170 includes parameters of the PDSCH transmission scheduled to UE 110 in the second DCI, wherein the PDSCH transmission includes a DL MAC PDU (570). In some aspects, the parameters include a second time-domain resource allocation field and / or a second frequency-domain resource allocation field for the PDSCH transmission. In some aspects, DU 170 sets the second time-domain resource allocation field to a second value conforming to one or more predetermined capabilities for the first UE type. In a further aspect, DU 170 sets the second time-domain resource allocation field to a second predetermined value. In an even further aspect, DU 170 sets the second time-domain resource allocation field to the same value as the first time-domain resource allocation field. In some aspects, DU 170 sets the second frequency-domain resource allocation field to a second value conforming to one or more predetermined capabilities for the first UE type. In a further aspect, DU 170 sets the second frequency-domain resource allocation field to a second predetermined value. In an even further aspect, DU 170 sets the second frequency-domain resource allocation field to the same value as the first time-domain resource allocation field. In this respect, UE 110 (e.g., in the case of a first UE type) receives PDSCH transmissions at a time domain resource (e.g., a symbol) according to a second time domain resource assignment field and / or in a frequency domain resource according to a second frequency domain resource assignment field.

[0089] In some aspects, DU 170 includes a second PDSCH to HARQ feedback timing indicator in the second DCI. In some aspects, DU 170 sets the second PDSCH to HARQ feedback timing indicator to a second value that conforms to one or more predetermined normal capabilities. For example, the second value corresponds to an earlier time resource than the first PDSCH to HARQ feedback timing indicator because the first UE type is able to process PDSCH transmissions faster than the second UE type. In some aspects, UE 110 (e.g., in the case of the first UE type) sends HARQ feedback based on the second value. In a further aspect, 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 acknowledgment or a HARQ negative acknowledgment.

[0090] In some cases, regarding the third DCI, DU 170 includes parameters of the PDSCH transmission scheduled to UE 110 in the third DCI (e.g., in the case of a UE with normal capabilities, a third UE type), where the PDSCH transmission includes DL MACPDU (570). In some aspects, the parameters include a third time-domain resource assignment field and / or a third frequency-domain resource assignment field for PDSCH transmission. In some aspects, DU 170 sets the third time-domain resource assignment field to a third value conforming to one or more predetermined capabilities for the third UE type. In a further aspect, DU 170 sets the third time-domain resource assignment field to a third predetermined value. In an even further aspect, 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, DU 170 sets the third frequency-domain resource assignment field to a third value conforming to one or more predetermined capabilities for the third UE type. In a further aspect, DU 170 sets the third frequency-domain resource assignment field to a third predetermined value. In a further aspect, DU 170 sets the third frequency domain resource assignment field to the same value as the first time domain resource assignment field or the second time domain resource assignment field. In this aspect, UE 110 (e.g., in the case of a third UE type, a UE with normal capabilities) receives PDSCH transmissions at time domain resources (e.g., symbols) according to the third time domain resource assignment field and / or in frequency domain resources according to the third frequency domain resource assignment field.

[0091] In some aspects, DU 170 includes a third PDSCH to HARQ feedback timing indicator in the third DCI. In some aspects, DU 170 sets the third PDSCH to HARQ feedback timing indicator to a third value that conforms to one or more predetermined capabilities for a third UE type. For example, the third value corresponds to an earlier time resource than the first or second PDSCH to HARQ feedback timing indicator, because the third UE type is able to process PDSCH transmissions faster than the first or second UE type. In some aspects, UE 110 (e.g., in some cases for the third UE type) sends HARQ feedback based on the third value. In a further aspect, DU 170 sets the third PDSCH to HARQ feedback timing indicator to the same value as the first or second PDSCH to HARQ feedback timing indicator. Depending on the implementation, the HARQ feedback is a HARQ acknowledgment or a HARQ negative acknowledgment.

[0092] In some aspects, DU 170 transmits the first DCI on time and frequency resources. Depending on the implementation, the time and frequency resources are on a first control resource set (CORESET) or a first search space. In some aspects, DU 170 broadcasts a first SIB on the cell, which includes first configuration parameters configured for the first CORESET or first search space for the second UE type. UE 110 (e.g., in the case of the second UE type) receives the first SIB and receives the first DCI on the time and frequency resources of the first CORESET or first search space according to the first configuration parameters.

[0093] In other aspects (not shown), DU 170 transmits a second DCI on time and frequency resources. In some aspects, the time and frequency resources are on a second CORESET or a second search space. In some aspects (not shown), DU 170 broadcasts a second SIB on the cell, which includes second configuration parameters configured for a second CORESET or a second search space for a first UE type. UE 110 (e.g., in the case of a first UE type) receives the second SIB and receives the second DCI on time and frequency resources in the second CORESET or second search space according to the second configuration parameters. Alternatively (not shown), DU 170 transmits the second DCI on a first CORESET or a first search space, such as when DU 170 is configured for a first CORESET or a first search space for both the first UE type and the second UE type.

[0094] In other aspects (not shown), DU 170 transmits a third DCI on time and frequency resources. In some aspects, the time and frequency resources are on a third CORESET or a third search space. In some aspects (not shown), DU 170 broadcasts a third SIB on the cell, which includes third configuration parameters configured for a third CORESET or a third search space for a third UE type. UE 110 (e.g., in the case of a third UE type) receives the third SIB and receives the third DCI on time and frequency resources in the third CORESET or third search space according to the third configuration parameters. Alternatively, DU 170 transmits the third DCI on a second CORESET or a second search space, such as when DU 170 is configured for both a first UE type and a third UE type.

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

[0096] In some aspects, DU 170 broadcasts an SIB on the cell, which includes a first PUCCH configuration (e.g., PUCCH-ConfigCommon IE) configuring PUCCH resources for a UE of the second UE type. UE 110 (e.g., in the case of the second UE type) sends HARQ feedback on the first PUCCH resource configured by the first PUCCH configuration. In some aspects, UE 110 determines the first PUCCH resource based on the PUCCH resource indicator in the first DCI. Depending on the implementation, the SIB is SIB1 or an SIB as described above.

[0097] In some aspects, DU 170 configures a first PUCCH configuration for a UE of a first UE type. UE 110 (e.g., in the case of the first UE type) sends HARQ feedback on the first PUCCH resource configured by the first PUCCH configuration. In some aspects, UE 110 determines the first PUCCH resource based on a PUCCH resource indicator in a second DCI. In some alternative aspects, DU 170 broadcasts an SIB on the cell that includes a second PUCCH configuration (e.g., PUCCH-ConfigCommon IE) for configuring PUCCH resources for a UE of the first UE type. UE 110 (e.g., in the case of the first UE type) sends HARQ feedback on the second PUCCH resource configured by the second PUCCH configuration. In some aspects, UE 110 determines the second PUCCH resource based on a PUCCH resource indicator in a second DCI. Depending on the implementation, the SIB is SIB1 or an SIB as described above.

[0098] In some aspects, DU 170 broadcasts an SIB on the cell, which includes a third PUCCH configuration (e.g., PUCCH-ConfigCommon IE) configuring PUCCH resources for a third type of UE. UE 110 (e.g., in the case of a third UE type) sends HARQ feedback on the third PUCCH resources configured by the third PUCCH configuration. In some aspects, UE 110 determines the third PUCCH resource based on the PUCCH resource indicator in the third DCI. Depending on the implementation, the SIB is SIB1 or an SIB as described above.

[0099] In some respects, the PUCCH resources configured in the first, second, and / or third PUCCH configurations are exclusive. In other respects, one or more PUCCH resources configured in the first, second, and / or third PUCCH configurations are identical. Depending on the implementation, the remainders in the first, second, and / or third PUCCH configurations may be identical or different. In such cases, DU 170 will not configure more than one UE to send HARQ feedback on the same PUCCH resource in the same time instance.

[0100] In other aspects, base station 120 broadcasts an SIB that includes a PUCCH configuration (e.g., PUCCH-ConfigCommon IE) for configuring PUCCH resources for UEs of the first, second, and third UE types. In this case, DU170 does not configure more than one UE to send HARQ feedback on the same PUCCH resource in the same time instance. UE110 sends HARQ feedback on the PUCCH resource configured by the PUCCH configuration. In some aspects, UE 110 determines the PUCCH resource based on the PUCCH resource indicator in the first DCI. Depending on the implementation, the SIB is SIB1 or an SIB as described above.

[0101] In some aspects, the DU 170 configures the cell's DL Bandwidth Part (BWP) and UL BWP for communication with UEs of a first UE type, a second UE type, or a third UE type. In some aspects, the DU 170 broadcasts an SIB on the cell, which includes DL BWP configuration and UL BWP configuration, respectively. Depending on the implementation, the SIB may be SIB1 or an SIB as described above. In other aspects, the DU 170 sends an RRC reconfiguration message to each UE, which includes DL BWP configuration and UL BWP configuration, respectively. The DU 170 communicates with UEs of the first UE type, the second UE type, and / or the third UE type on the cell via the DL BWP and UL BWP.

[0102] In other aspects, DU 170 configures a first DL BWP and a first UL BWP for UEs of a first UE type and a second UE type, and configures a second DL BWP and a second UL BWP for UEs of a third UE type. In some aspects, DU 170 broadcasts a first SIB on the cell, which includes a first DLBWP configuration and a first UL BWP configuration respectively configuring the first DL BWP and the first UL BWP. Depending on the implementation, the first SIB is SIB1 or another SIB as described above regarding CU configuration information. In some aspects, DU 170 broadcasts a second SIB on the first cell, which includes a second DL BWP configuration and a second UL BWP configuration respectively configuring the second DL BWP and the second UL BWP. Depending on the implementation, the second SIB is 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, DU 170 sends an RRC reconfiguration message to each UE of the first or second UE type, the RRC reconfiguration message including a first DL BWP configuration and a first UL BWP configuration respectively. In other aspects, DU 170 sends an RRC reconfiguration message to each UE of the third UE type, the RRC reconfiguration message including a second DL BWP configuration and a second UL BWP configuration respectively. DU 170 communicates with UEs of the first and / or second UE types on the cell via the first DL BWP and the first UL BWP, and communicates with UEs of the third UE type via the second DL BWP and the second UL BWP.

[0103] In other aspects, DU 170 configures a first DL BWP and a first UL BWP for a UE of a first UE type, a second DL BWP and a second UL BWP for a UE of a second UE type, and a third DL BWP and a third UL BWP for a UE of a third UE type. In some aspects, DU 170 broadcasts a first SIB on the cell, which includes a first DL BWP configuration and a first UL BWP configuration respectively configuring the first DL BWP and the first UL BWP. Depending on the implementation, the first SIB is SIB1 or another SIB as described above regarding the CU configuration information. In some aspects, DU 170 broadcasts a second SIB on the first cell, which includes a second DL BWP configuration and a second UL BWP configuration respectively configuring the second DL BWP and the second UL BWP. Depending on the implementation, the second SIB is SIB1 or another SIB as described above regarding the CU configuration information. In some aspects, DU 170 broadcasts a third SIB on the first cell, which includes a third DL BWP configuration and a third UL BWP configuration respectively configuring the third DL BWP and the third UL BWP. Depending on the implementation, the third SIB is SIB1 or another SIB as described above regarding the CU configuration information. In some respects, the first, second, and third SIBs are the same SIB (e.g., the same instance or different instances) or different SIBs. In other respects, DU 170 sends an RRC reconfiguration message to each UE of the second UE type, which includes the first DL BWP configuration and the first UL BWP configuration, respectively. In other respects, DU 170 sends an RRC reconfiguration message to each UE of the first UE type, which includes the second DL BWP configuration and the second UL BWP configuration, respectively. In other respects, DU 170 sends an RRC reconfiguration message to each UE of the third UE type, which includes the third DL BWP configuration and the third UL BWP configuration, respectively. DU 170 communicates with a UE of type 2 on the cell via a first DL BWP and a first UL BWP, communicates with a UE of type 1 on the cell via a second DL BWP and a second UL BWP, and communicates with a UE of type 3 via a third DL BWP and a third UL BWP.

[0104] Events 535, 540, 545, 550, 555, 560, 565, 570, 575, 580, and 585 are in Figure 5This is collectively referred to as the connection establishment process, connection recovery process, or connection reconstruction process 508 (subgraph 508). Subgraph 508 includes subgraphs 504 and 506.

[0105] Figures 6 to 10 It shows in Figure 5 The changes in the scene described in the text. Figure 6 This illustrates an alternative transmission method for UE type information to CU 160. Figure 7 This illustrates an aspect of alternative identification of UE type information by DU 170 based on random access preamble. Figure 8 An alternative transmission of UE type information to CU 160 based on random access preamble identification is shown. Figure 9 This illustrates an alternative classification of UE type information by CU 160. Figure 10 This illustrates an aspect of alternative identification of UE type information by DU 170 based on time and frequency resources.

[0106] Figure 6 It shows the relationship with Figure 5 Scenario 500 is similar to Scenario 600, except that Scenario 600 includes events 605 and 610 instead of events 555 and 560, which describe the alternative transmission of UE type information to CU 160. (See also: Regarding...) Figure 5 As described in sub-Figure 502, DU 170 and CU 160 initiate the F1 setup process.

[0107] In scenario 600, DU 170 sends a DU-to-CU message (605) to CU 160, which includes an RRC request message and an indication of a second UE type. The DU-to-CU message (605) is similar to DU-to-CU message 555, except that it includes an indication of a second UE type instead of an indication of a first UE type. Therefore, CU 160 classifies UE 110 (610) as a second UE type based on the indication of the second UE type. Thus, CU 160 takes appropriate action against UE 110 based on the indication of the second UE type. For example, CU 160 may manage user plane resources for UE 110 based on the indication of the second UE type. To manage user plane resources, CU 160 may determine Quality of Service (QoS) information and / or user plane transport layer information based on the indication of the second UE type. Then, CU 160 can send a CU to DU message (e.g., a UE context setting request message) to DU 170, which includes QoS information and / or user plane transport layer information.

[0108] In some aspects (not shown), CU 160 sends a BS-to-CN message to a CN (e.g., CN 150) or an AMF (e.g., AMF 152), the BS-to-CN message including an indication of a second UE type for UE 110. Therefore, in some aspects, CN 150 classifies UE 110 as a second UE type based on the indication of the second UE type. In some aspects, CN 150 applies a charging policy or rate for the second UE type of UE 110 based on this indication or classification to charge for data traffic transmitted with UE 110. In some such cases, 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. In some aspects, AMF 152 sends a message (not shown) including an indication of the second UE type to the SMF after receiving the BS-to-CN message. Therefore, in some aspects, the SMF takes appropriate action against 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 UE 110 and / or ensure that UE 110's data is correctly routed and / or forwarded based on an indication of the second UE type. In another example, the SMF may send an SMF-UPF message to the UPF that includes an indication of the second UE type. Therefore, the UPF manages user plane resources for UE 110 based on the indication of the second UE type.

[0109] Subgraphs 504 and 506, and events 550, 605, and 610 in Figure 6 This is collectively referred to as the connection establishment process, connection recovery process, or connection reconstruction process 602 (sub-graph 602).

[0110] Go to Figure 7 Scenario 700 is similar to Scenario 500, except that Scenario 700 includes event 705 instead of event 550, which describes an alternative identification of UE type information by DU 170 based on the random access preamble. (See also: Regarding...) Figure 5 As depicted in sub-Figure 502, DU 170 and CU 160 initiate the F1 setup procedure. In scenario 700, when (i) the RA preamble (535) is specifically configured for the second UE type or (ii) DU 170 receives the (535) RA preamble on time and frequency resources specifically configured for the second UE type, DU 170 identifies (705) UE 110 as the second UE type. Based on this identification, DU 170 sends a (555) DU to CU message to CU 160, which includes an RRC request message and an indication of the first UE type.

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

[0112] Subgraphs 504 and 506, and events 705, 555, and 560 in Figure 7 This is collectively referred to as the connection establishment process, connection recovery process, or connection reconstruction process 702 (sub-figure 702).

[0113] Go to Figure 8 Scenario 800 is similar to Scenario 600 and describes an alternative transmission of UE type information based on random access preamble identification to CU 160. (See also: Regarding...) Figure 5 As depicted in subfigure 502, DU 170 initiates an F1 setup procedure with CU 160. In scenario 800, based on this identification (705), DU 170 sends a DU-to-CU message (605) to CU 160, which includes an RRC request message and an indication of a second UE type. Subfigures 504 and 506, as well as events 605, 610, and 705, in... Figure 8 This is collectively referred to as the connection establishment process, connection recovery process, or connection reconstruction process 802 (sub-graph 802).

[0114] Go to Figure 9 Scenario 900 is similar to scenarios 500-800, which describe alternative classifications of UE type information by CU 160. (See also: Regarding...) Figure 5 As depicted in sub-Figure 502, DU 170 and CU 160 initiate the F1 setup procedure. In scenario 900, CU 160 classifies UE 110 as a second UE type (905) based on the RRC request message. In some respects, because UE 110 is a second UE type, UE 110 generates the RRC request message according to the format of a type 2 RRC request message (i.e., a type 2 RRC request message). If UE 110 is a first UE type or a third UE type, the RRC request message is a type 1 RRC request message. Therefore, when CU 160 receives the RRC request message according to the format of a type 2 RRC request message, CU 160 classifies UE 110 as a second UE type, even though CU 160 receives an indication for a first UE type (555). In other words, CU 160 discards or ignores the indication for a first UE type (555).

[0115] In some aspects, if UE 110 is a second UE type and operates in an idle state (530), the type 2 RRC request message is an RRCSetupRequest1 message. In some aspects, if UE 110 is a first or third UE type and operates in an idle state (530), the type 2 RRC request message is an RRCSetupRequest message. In some aspects, if UE 110 is a second UE type and operates in a connected state (530), the RRC request message is an RRCReestablishmentRequest1 message. If UE 110 is a first or third UE type and operates in a connected state (530), the RRC request message is an RRCReestablishmentRequest message. In some aspects, if UE 110 is a second UE type and operates in an inactive state (530), the RRC request message is an RRCResumeRequest2 message or an RRCResumeRequest3 message. If UE 110 is a first UE type or a third UE type and is operating in an inactive state (530), then the RRC request message is an RRCResumeRequest message or an RRCResumeRequest1 message.

[0116] In some alternatives, UE 110 sets the LCID as the first value instead of the second value, and DU 170 identifies UE 110 as a first UE type based on the first value of the LCID. The advantage of using the first value is that it saves reserved LCID values ​​for future use.

[0117] Subgraphs 504 and 506, and events 550, 555, and 905 in Figure 9 This is collectively referred to as the connection establishment process, connection recovery process, or connection reconstruction process 902 (sub-graph 902).

[0118] Go to Figure 10 Scenario 1000 is similar to scenarios 500-900, which describe alternative identification of UE type information based on time and frequency resources by DU 170. (See also: Regarding...) Figure 5As depicted in sub-Figure 502, DU 170 and CU 160 initiate the F1 setup procedure. In some alternatives, DU 170 configures the same RA resources for both the first UE type and the second UE type. RA resources include RA preambles and / or time and frequency resources for the physical RA channel (PRACH). In some such cases, when DU 170 receives the RA preamble (535) based on the RA resources, DU 170 identifies UE 110 as the first UE type. The benefit of configuring the same RA resources for both the first UE type and the second UE type is the saving of RA resources.

[0119] Subgraphs 504 and 506, and events 555, 805, and 905 in Figure 10 This is collectively referred to as the connection establishment process, connection recovery process, or connection reconstruction process, or connection establishment process or connection recovery process 1002 (sub-figure 1002).

[0120] Example Method

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

[0122] Figure 11Example method 1100 for managing user equipment with reduced management capabilities is shown in general as involving the identification by a DU (e.g., DU 170) of a base station (e.g., base station 120) of whether a UE (e.g., UE 110) is a first UE type (e.g., RedCap UE), a second UE type (e.g., fRedCap UE), or a third UE type (e.g., a UE with normal capabilities), and providing an indication of the first UE type, second UE type, or third UE type to a CU (e.g., CU 160) of the base station, as per [reference to...]. Figure 5 As generally described. At box 1102, the DU and UE perform a random access procedure. For example, the UE uses a four-step procedure or a two-step procedure to initiate a process with base station 120 for establishing or restoring a radio connection, as described above. Figure 5 As described.

[0123] At box 1104, the DU receives a Media Access Control (MAC) Protocol Data Unit (PDU) from the UE during random access. The MAC PDU includes a Logical Channel Identifier (LCID) and a message. For example, at box 545, the DU receives a MAC PDU that includes the LCID and an RRC request message.

[0124] At box 1106, the DU includes the received message in the DU-CU message. For example, the DU includes the received RRC request message in the DU-CU message.

[0125] At box 1108, the DU identifies the LCID value as a first value, a second value, or a third value. For example, the DU identifies whether the LCID has a first value, a second value, or a third value, which respectively indicate that the UE is a RedCap UE, an fRedCap UE, or a UE with normal capabilities.

[0126] At box 1110, if the identified value is a first value or a second value, the DU includes the indication for the first type of UE in the DU-CU message, and at box 1112, the DU sends the DU-CU message to the CU. For example, the DU includes the indication for the first type of UE in the DU-CU message and sends the DU-CU message to the CU, which effectively instructs the CU to generate an RRC response message based on the received indication.

[0127] At box 1108, if the DU recognizes the third RA configuration, then at box 1112, the DU sends a DU-to-CU message to the CU without inserting an indication of the UE type.

[0128] Figure 12Example method 1200 for managing user equipment with reduced management capabilities is shown as generally involving the identification by a DU (e.g., DU 170) of a base station (e.g., base station 120) of whether a UE (e.g., UE 110) is a first UE type (e.g., RedCap UE), a second UE type (e.g., fRedCap UE), or a third UE type (e.g., a UE with normal capabilities), and providing an indication of the first UE type, second UE type, or third UE type to a CU (e.g., CU 160) of the base station, as per [reference to...]. Figure 6 As generally described. At box 1202, the DU and UE perform a random access procedure. For example, the UE uses a four-step procedure or a two-step procedure to initiate a procedure with base station 120 for establishing or restoring a radio connection, as described above. Figure 5 As described.

[0129] At box 1204, the DU receives a Media Access Control (MAC) Protocol Data Unit (PDU) from the UE during random access. The MAC PDU includes a Logical Channel Identifier (LCID) and a message. For example, at box 545, the DU receives a MAC PDU that includes the LCID and an RRC request message.

[0130] At box 1206, the DU includes the received message in the DU-CU message. For example, the DU includes the received RRC request message in the DU-CU message.

[0131] At box 1208, the DU identifies the LCID value as a first value, a second value, or a third value. For example, the DU identifies whether the LCID has a first value, a second value, or a third value, which respectively indicate that the UE is a RedCap UE, an fRedCap UE, or a UE with normal capabilities.

[0132] At box 1210, if the identified value is a first value, the DU includes the indication for the first type of UE in the DU to CU message, and at box 1214, the DU sends the DU to CU message. For example, the DU includes the indication for the first type of UE in the DU to CU message and sends the DU to CU message, which effectively instructs the CU to generate an RRC response message based on the received indication.

[0133] At box 1212, if the identified value is a second value, the DU includes the indication for the second type of UE in the DU to CU message, and at box 1214, the DU sends the DU to CU message. For example, the DU includes the indication for the second type of UE in the DU to CU message and sends the DU to CU message, which effectively instructs the CU to generate an RRC response message based on the received indication.

[0134] At box 1208, if the DU recognizes the third RA configuration, then at box 1212, the DU sends a DU-CU message to the CU without inserting an indication of the UE type.

[0135] Figure 13 Example method 1300 for managing user equipment with reduced management capabilities is shown as generally involving the identification by a DU (e.g., DU 170) of a base station (e.g., base station 120) of whether a UE (e.g., UE 110) is a first UE type (e.g., RedCap UE), a second UE type (e.g., fRedCap UE), or a third UE type (e.g., a UE with normal capabilities), and providing an indication of the first UE type, second UE type, or third UE type to a CU (e.g., CU 160) of the base station, as per [reference to...]. Figure 7 As generally described. 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 a third 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 configuration includes configuration parameters that configure one or more random access preambles, the association between the random access preamble and the synchronization signal and the physical broadcast channel block (SSB), and / or the time and / or frequency resources used for the transmission of the random access preamble.

[0136] At box 1308, the DU and UE perform a random access procedure. For example, the UE uses a four-step or two-step procedure to initiate a process with base station 120 for establishing or restoring a radio connection, as described above. Figure 5 As described.

[0137] At box 1310, the DU receives a Media Access Control (MAC) Protocol Data Unit (PDU) from the UE during random access. The MAC PDU includes a Logical Channel Identifier (LCID) and a message. For example, at box 545, the DU receives a MAC PDU that includes the LCID and an RRC request message.

[0138] At box 1312, the DU includes the received message in the DU-CU message. For example, the DU includes the received RRC request message in the DU-CU message.

[0139] At box 1314, the DU identifies the RA configuration used for the RA procedure, which is a first RA configuration, a second RA configuration, or a third RA configuration. For example, the DU identifies the first RA configuration, the second RA configuration, or the third RA configuration as indicating whether the UE is a RedCap UE, an fRedCap UE, or a UE with normal capabilities, respectively.

[0140] At box 1316, if the identified RA configuration is a first RA configuration or a second RA configuration, the DU includes the indication for the first type of UE in the DU-CU message, and at box 1318, the DU sends the DU-CU message to the CU. For example, the DU includes the indication for the first type of UE in the DU-CU message and sends the DU-CU message to the CU, which effectively instructs the CU to generate an RRC response message based on the received indication.

[0141] At box 1314, if the DU recognizes a third RA configuration, then at box 1318, the DU sends a DU-to-CU message to the CU without inserting an indication of the UE type.

[0142] Figure 14 Example method 1400 for managing user equipment with reduced management capabilities is shown as generally involving the identification by a DU (e.g., DU 170) of a base station (e.g., base station 120) of whether a UE (e.g., UE 110) is a first UE type (e.g., RedCap UE), a second UE type (e.g., fRedCap UE), or a third UE type (e.g., a UE with normal capabilities), and providing an indication of the first UE type, second UE type, or third UE type to a CU (e.g., CU 160) of the base station, as per [reference to...]. Figure 8 As generally described. 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 a third 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 configuration includes configuration parameters that configure one or more random access preambles, the association between the random access preamble and the synchronization signal and the physical broadcast channel block (SSB), and / or the time and / or frequency resources used for the transmission of the random access preamble.

[0143] At box 1408, the DU and UE perform a random access procedure. For example, the UE uses a four-step or two-step procedure to initiate a process with base station 120 for establishing or restoring a radio connection, as described above. Figure 5 As described.

[0144] At box 1410, the DU receives a Media Access Control (MAC) Protocol Data Unit (PDU) from the UE during random access. The MAC PDU includes a Logical Channel Identifier (LCID) and a message. For example, at box 545, the DU receives a MAC PDU that includes the LCID and an RRC request message.

[0145] At box 1412, the DU includes the received message in the DU-CU message. For example, the DU includes the received RRC request message in the DU-CU message.

[0146] At box 1414, the DU identifies the RA configuration used for the RA procedure, which is a first RA configuration, a second RA configuration, or a third RA configuration. For example, the DU identifies the first RA configuration, the second RA configuration, or the third RA configuration to indicate whether the UE is a RedCap UE, an fRedCap UE, or a UE with normal capabilities, respectively.

[0147] At box 1416, if the RA configuration identified at box 1414 is the first RA configuration, the DU includes the indication for the first type of UE in the DU-CU message, and at box 1420, the DU sends the DU-CU message to the CU. For example, the DU includes the indication for the first type of UE in the DU-CU message and sends the DU-CU message to the CU, which effectively instructs the CU to generate an RRC response message based on the received indication.

[0148] At box 1418, if the RA configuration identified at box 1414 is a second RA configuration, the DU includes the indication for the second type of UE in the DU-CU message, and at box 1420, the DU sends the DU-CU message to the CU. For example, the DU includes the indication for the second type of UE in the DU-CU message and sends the DU-CU message to the CU, which effectively instructs the CU to generate an RRC response message based on the received indication.

[0149] At box 1414, if the DU recognizes a third RA configuration, then at box 1420, the DU sends a DU-to-CU message to the CU without inserting an indication of the type of UE.

[0150] Figure 15Example method 1500 for managing user equipment with reduced capabilities is shown as generally involving communication between a DU (e.g., DU 170) and a CU (e.g., CU 160) of a base station (e.g., base station 120) for configuring the base station to handle various types of UEs (e.g., UE 110) (including a first UE type (e.g., RedCap UE), a second UE type (e.g., fRedCap UE), or a third UE type (e.g., a UE with normal capabilities)), such as regarding Figure 5 Sub-Figure 502 is generally described. At block 1502, the DU sends a first DU-CU message to the CU including first information about the first cell, indicating whether a UE of a first UE type is allowed to access the first cell (e.g., event 505 or 515). At block 1504, the DU sends a second DU-CU message to the CU including second information about the first cell, indicating whether a UE of a second UE type is 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).

[0151] In some implementations, the first UE type is RedCap UE, and the second UE type is fRedCap UE. In some implementations, the DU avoids sending information to the CU indicating whether a capable UE is allowed to access the cell.

[0152] In some aspects, the first DU to CU message and the second DU to CU message are F1 Application Protocol (F1AP) messages. In some aspects, the first DU to CU message and the second DU to CU message are F1 setup request messages or gNB-DU configuration update messages. In some aspects, one of the first DU to CU message and the second DU to CU message is an F1 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 that respectively include first information and second information. In some aspects, the DU includes the first IE and the second IE in the first field / IE and the second field / IE of the interface protocol in the first DU to CU message and the second DU to CU message, respectively. In some aspects, the interface protocol is the F1 Application Protocol (F1AP). In some aspects, the first IE and the second IE are IEs of the RRC protocol. In other aspects, the first IE and the second IE are IEs of the interface protocol (e.g., F1AP). In some aspects, the first IE and the second IE are the same IE with different content. In other aspects, the first UE and the second IE are different IEs.

[0153] In some aspects, the DU includes the first information and the second information in the first SIB and the 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 RedCap information and fRedCap information respectively, as in... Figures 5 to 10 As described in [the text].

[0154] Figure 16 Example method 1600 for managing user equipment with reduced management capabilities is shown as generally involving communication between a DU (e.g., DU 170) and a CU (e.g., CU 160) of a base station (e.g., base station 120) for configuring the base station to handle various types of UEs (e.g., UE 110) (including a first UE type (e.g., RedCap UE), a second UE type (e.g., fRedCap UE), or a third UE type (e.g., a UE with normal capabilities)), such as regarding Figure 5 Sub-Figure 502 is generally described. At block 1602, the DU sends a first DU-CU message to the CU, which includes first information and second information for the first cell. The first information indicates whether a UE of a first UE type is allowed to access the first cell and the second information indicates whether a UE of a second UE type is allowed to access the first cell (e.g., event 505 or 515).

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

[0156] In some aspects, the DU to CU message is an F1AP message, such as an F1 setup request message or a gNB-DU configuration update message. In some aspects, the DU generates a first IE including first information and second information, and includes the first IE in the interface protocol field or IE of the DU to CU message. In some aspects, the first information and second information are combined into a single message, and this single message is included in the first IE. In some aspects, the interface protocol is the F1 Application Protocol (F1AP). In some aspects, the first IE is an IE of the RRC protocol. In other aspects, the first IE is an IE of the interface protocol. In some aspects, the DU generates an SIB including first information and second information, and broadcasts the SIB on the first cell. In some aspects, the DU generates an SIB including the first IE, and broadcasts the SIB on the first cell. In some aspects, the DU also includes the SIB in the DU to CU message in addition to the first IE. In some aspects, the SIB is SIB1.

[0157] In other aspects, the DU generates a first IE and a second IE, which respectively include first information and second information, and includes the first IE and the second IE in the first field / IE and the second field / IE of the interface protocol in the DU-to-CU message. In some aspects, the first IE and the second IE are the same IE with different content. 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 the RRC protocol. In other aspects, the first IE and the second IE are IEs of the interface protocol.

[0158] Figure 17 Example method 1700 for managing user equipment with reduced management capabilities is shown as generally involving the generation of configurations from DUs (e.g., DU 170) for CUs (e.g., CU 160) for a base station (e.g., base station 120) to configure the base station to handle various types of UEs (e.g., UE 110) (including a first UE type (e.g., RedCap UE), a second UE type (e.g., fRedCap UE), or a third UE type (e.g., a UE with normal capabilities)), as per [reference to...]. Figure 5 The general description is as follows. At box 1702, the DU communicates with the UE and CU (e.g., the event in sub-figure 508). At box 1704, the DU identifies whether the UE is of type one, type two, or type three (e.g., event 550). If at box 1704 the DU identifies the type as type one, the process proceeds to box 1706. At box 1706, the DU generates a first configuration for the UE. At box 1708, the DU sends the first configuration to the CU. In some aspects, the DU sends a DU-CU message to the CU including the first configuration.

[0159] If the DU identifies the type as type two at box 1704, the process proceeds to box 1710. At box 1710, the DU generates a second configuration for the UE (e.g., event 555). At box 1712, the DU sends the second configuration to the CU. In some aspects, the DU sends a DU-CU message including the second configuration to the CU. Otherwise, if the DU identifies the type as type three at box 1704, the process proceeds to box 1714. At box 1714, the DU generates a third configuration for the UE. At box 1718, the DU sends the third configuration to the CU. In some aspects, the DU sends a DU-CU message including the third configuration to the CU.

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

[0161] In some respects, the DU to CU message is Initial UL RRC message transfer Messages. In other respects, DU to CU messages are UE context modification request messages, UE context modification response messages, or UE context setting response messages.

[0162] Figure 18 Example method 1800 for managing user equipment with reduced capabilities is shown as generally involving the generation of configurations from DUs (e.g., DU 170) for CUs (e.g., CU 160) for a base station (e.g., base station 120) to configure the base station to handle various types of UEs (e.g., UE 110) (including a first UE type (e.g., RedCap UE), a second UE type (e.g., fRedCap UE), or a third UE type (e.g., a UE with normal capabilities)), as per [reference to...]. Figure 5 The general description is similar to method 1700.

[0163] At box 1802, the DU communicates with the UE and CU (e.g., the event in subfigure 508). At box 1804, the DU identifies whether the UE is of type one, type two, or type three (e.g., event 550). If at box 1804 the DU identifies the type as type one or type two, the process proceeds to box 1806. At box 1806, the DU generates a second configuration for the UE. At box 1808, the DU sends the second configuration to the CU. In some aspects, the DU sends a DU-CU message to the CU including the second configuration.

[0164] If the DU identifies the type as Type 3 at box 1804, the process proceeds to box 1810. At box 1810, the DU generates a third configuration for the UE (e.g., event 555). At box 1812, the DU sends the third configuration to the CU. In some aspects, the DU sends a DU-CU message including the third configuration to the CU.

[0165] Figure 19Example method 1900 for managing user equipment with reduced management capabilities is shown as generally involving 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 generate a configuration to configure the base station to handle various types of UEs (e.g., UE 110) (including a first UE type (e.g., RedCap UE), a second UE type (e.g., fRedCap UE), or a third UE type (e.g., a UE with normal capabilities)), as per [reference to...]. Figure 5 The overall description.

[0166] At block 1902, the CU receives first information (e.g., event 505 or 515) from the first DU for the first cell. At block 1904, the CU uses the first information to determine whether the first cell allows access to a UE of the first UE type. At block 1906, based on the determination that the first cell allows access to a UE of the first UE type, the CU configures the UE of the first UE type for measurement and / or access to the first cell. If the CU determines, based on the first information, that the first cell does not allow access to a UE of the first UE type, the CU avoids configuring the UE of the first UE type for measurement and / or access to the first cell.

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

[0168] In some aspects, the CU receives third information (e.g., event 505 or 515) regarding the second cell from the first DU. The CU uses this third information to determine whether the second cell allows a UE of the first UE type to access the second cell. Based on the determination that the second cell allows a UE of the first UE type to access the second cell, the CU configures the UE of the first UE type to measure and / or access the second cell. If the CU determines, based on the third information, that the second cell does not allow a UE of the first UE type to access the cell, the CU avoids configuring the UE of the first UE type to measure and / or access the second cell. The CU receives fourth information (e.g., event 505 or 515) regarding the second cell from the first DU. Based on this fourth information, the CU determines that the second cell allows a UE of the second UE type to access the second cell. Based on the determination that the second cell allows access for the second type of UE, the CU configures the UE of the second UE type to measure and / or access the second cell. If the CU determines, based on the fourth information, that the second cell does not allow a UE of the second UE type to access the second cell, the CU avoids configuring the UE of the second UE type to measure and / or access the second cell.

[0169] In some aspects, the CU receives fifth information regarding the third cell from the 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 the UEs of the first UE type for measurement and / or access to 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, the CU avoids configuring the UEs of the first UE type for measurement and / or access to the third cell. The CU receives sixth information regarding 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 UEs of the second type to access the third cell, the CU configures the UEs of the second UE type for measurement and / or access to 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 avoids configuring the UEs of the second UE type for measurement and / or access to the third cell.

[0170] In some aspects, such as targeting Figure 15 and Figure 16 The described examples and implementations can be applied to Figure 19 In some respects, the examples and implementations described for the first and second information can be applied to the third and fourth information, respectively. In some respects, the examples and implementations described for the first and second information can be applied to the fifth and sixth information, respectively.

[0171] Figure 20Example method 2000 for managing user equipment with reduced management capabilities is shown as generally involving 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 generate a configuration to configure the base station to handle various types of UEs (e.g., UE 110) (including a first UE type (e.g., RedCap UE), a second UE type (e.g., fRedCap UE), or a third UE type (e.g., a UE with normal capabilities)), as per [reference to...]. Figure 5 The overall description.

[0172] At box 2002, the CU receives cell information (e.g., event 505 or 515) from the DU. At box 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 process proceeds to box 2006, where the CU operates in a state where the cell does not allow UEs of the first UE type to access the cell. Otherwise, if the CU identifies that the cell information includes the first information, the process proceeds to box 1904. At box 1904, the CU identifies whether the first cell allows UEs of the first UE type to access the cell based on the first information. At box 1906, based on the identification that the first cell allows UEs of the first UE type to access the cell, the CU configures the UE of the first UE type to measure and / or access the first cell. At box 2008, the CU identifies whether the cell information includes second information. If the CU identifies that the cell information does not include the second information, the process proceeds to box 2010, where the CU operates in a state where the cell does not allow UEs of the second UE type to access the cell. Otherwise, if the CU identifies that the cell information includes the second information, the process proceeds to box 1910. At box 1910 and based on the second information, the CU identifies whether the first cell allows a UE of the second UE type to access the cell. At box 1912, based on the identification that the first cell allows a UE of the second type to access the cell, the CU configures the UE of the second UE type to measure and / or access the first cell.

[0173] In some respects, cell information is the interface protocol (e.g., F1AP) IE. In other respects, cell information is the service cell information IE. In some respects, such as for... Figure 15 , Figure 16 and Figure 19 The described examples and implementations can be applied to Figure 20 .

[0174] Figure 21Example method 2100 for managing user equipment with reduced management capabilities is shown as generally involving RAN nodes (base station 120, DU 170) generating configurations to provide access for various types of UEs (e.g., UE 110) (including a first UE type (e.g., RedCap UE), a second UE type (e.g., fRedCap UE), or a third UE type (e.g., a UE with normal capabilities)), as per [reference to...]. Figure 5 The overall description.

[0175] At box 2102, the RAN node configures a first portion of radio resources for communication with a UE of a first UE type on the cell. At box 2104, the RAN node configures a second portion of radio resources for communication with a UE of a second UE type on the cell. At box 2106, the RAN node configures a third portion of radio resources for communication with a UE of a third UE type on the cell. At box 2108, the RAN node uses the first portion of radio resources to communicate with a UE of the first UE type on the cell. At box 2110, the RAN node uses the second portion of radio resources to communicate with a UE of the second UE type on the cell. At box 2112, the RAN node uses the third portion of radio resources to communicate with a UE of the third UE type on the cell.

[0176] In some aspects, the RAN node transmits system information (e.g., one or more SIBs) on the cell to configure the first, second, and / or third portions of radio resources (e.g., event 525). In some aspects, the RAN node transmits a dedicated message (e.g., an RRC reconfiguration message) to each UE of a first UE type to configure the first portion of the radio resources. In some aspects, the RAN node transmits a dedicated message (e.g., an RRC reconfiguration message) to each UE of a second UE type to configure 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 UE of a third UE type to configure the third portion of the radio resources. In some aspects, the first, second, and third UE types are RedCap UE, fRedCap UE, and a normally functioning UE, respectively.

[0177] In some respects, radio resources include the DL system bandwidth of the cell. In such cases, the first part is a first DL BWP of the DL system bandwidth, the second part is a second DL BWP of the DL system bandwidth, and the third part is a third DL BWP of the DL system bandwidth. In some respects, the third DL BWP is greater than the second DL BWP, and the second DL BWP is greater than or equal to the first DL BWP. In some respects, the first DL BWP, the second DL BWP, and the third DL BWP partially or completely overlap. In some respects, the third DL BWP includes the second DL BWP, and / or the second DL BWP includes the first DL BWP. In other respects, the first DL BWP, the second DL BWP, and / or the third DL BWP do not overlap.

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

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

[0180] Figure 22Example method 2200 for managing user equipment with reduced management capabilities is shown as generally involving RAN nodes (base station 120, DU 170) generating configurations to provide access for various types of UEs (e.g., UE 110) (including a first UE type (e.g., RedCap UE), a second UE type (e.g., fRedCap UE), or a third UE type (e.g., a UE with normal capabilities)), as per [reference to...]. Figure 5 The overall description.

[0181] At block 2202, the RAN node configures a first portion of radio resources for communication with a UE of a first UE type on the cell. At block 2204, the RAN node configures a first portion of radio resources for communication with a UE of a second UE type on the cell. At block 2206, the RAN node configures a second portion of radio resources for communication with a UE of a third UE type on the cell. At block 2208, the RAN node uses the first portion of radio resources to communicate with a UE of the first UE type on the cell. At block 2210, the RAN node uses the first portion of radio resources to communicate with a UE of the second UE type on the cell. At block 2212, the RAN node uses the second portion of radio resources to communicate with a UE of the third UE type on the cell.

[0182] In some aspects, the RAN node transmits system information (e.g., one or more SIBs) on the cell to configure the first and second portions of radio resources (e.g., event 525). In some aspects, the RAN node transmits a dedicated message (e.g., an RRC reconfiguration message) to each UE of the first and second UE types to configure the first portion of radio resources. In some aspects, the RAN node transmits a dedicated message (e.g., an RRC reconfiguration message) to each UE of the third UE type to configure the second portion of radio resources. In some aspects, the first, second, and third UE types are RedCap UE, fRedCap UE, and a normally functioning UE, respectively.

[0183] In some respects, radio resources include the 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 respects, the second DL BWP is larger than the first DL BWP. In some respects, the first DL BWP and the second DL BWP partially or completely overlap. In some respects, the second DL BWP includes the first DL BWP. In other respects, the first DL BWP and the second DL BWP do not overlap.

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

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

[0186] The following additional considerations apply to the foregoing discussion. In some implementations, "message" is used, and "information element (IE)" may be used instead of "message". In some implementations, "IE" is used, and "field" may be used instead of "IE". The description for CU or DU may apply to aggregation base stations that implement the communication functions of CU and DU for communication with UE. In the case of aggregation base stations, the messages exchanged between CU and DU may be omitted, or regarded as internal computer instructions or internal messages exchanged between different processes in the aggregation base station.

[0187] 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 may be skipped or combined in any order to implement a method or an alternative method. Generally, any of the components, modules, methods, and operations described herein may be implemented using software, firmware, hardware (e.g., a fixed logic circuit system), 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 located locally and / or remotely on a computer processing system, and aspects may include software applications, programs, functions, etc. Alternatively or additionally, any functionality described herein may be performed at least in part by one or more hardware logic components such as, but not limited to, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), system-on-a-chip (SoCs), complex programmable logic devices (CPLDs), etc.

[0188] Although aspects of the user equipment with reduced management capabilities have been described in language specific to features and / or methods, the subject matter 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 the user equipment with reduced management capabilities, and other equivalent features and methods are intended to be within the scope of the appended claims. Furthermore, various different aspects have been described, and it should be understood that each described aspect can be implemented independently or in combination with one or more other described aspects.

[0189] Some examples are described below: Example 1: A method for user equipment (UE) with reduced management capabilities due to a base station's distributed unit (DU), the method comprising: Perform a random access procedure with the UE; During the random access process, the UE receives a Media Access Control (MAC) Protocol Data Unit (PDU), which includes a Logical Channel Identifier (LCID) and a message. Include the received message in the DU to CU message; Identify the value of the LCID, wherein the value is a first value, a second value, or a third value; If the identified value is the first value, then the indication for the first type of UE will be included in the DU to CU message; If the identified value is the second value, then the indication for the first type of UE will be included in the DU to CU message; and The DU to CU message is sent to the central unit (CU).

[0190] Example 2: According to the method in Example 1, wherein the first value indicates that the UE is a RedCap UE; wherein the second value indicates that the UE is a RedCap UE; and wherein the third value indicates that the UE is a normal UE.

[0191] Example 3: The method described in Example 1 or Example 2, wherein the message is a Radio Resource Control (RRC) request message.

[0192] Example 4: The method according to any one of the foregoing examples, wherein sending the DU to CU message to the CU instructs the CU to generate an RRC response message for the UE, the method includes: Receive the RRC response message for the UE from the CU; and Send the RRC response message to the UE.

[0193] Example 5: The method described in Example 4 includes: Receive an RRC completion message from the UE; and In another DU to CU message, the RRC completion message is sent to the CU.

[0194] Example 6: According to the method described in Example 5, the RRC completion message is one of the following: RRCSetupComplete message; RRCResumeComplete message; or RRCReestablishmentComplete message.

[0195] Example 7: According to the method described in Example 4, the RRC response message is one of the following: RRCSetupRequest message; RRCResumeRequest message; or RRCReestablishmentRequest message.

[0196] Example 8: A method for performing an F1 setup procedure by a central unit (CU) and a first distributed unit (DU), the method comprising: Receive first information for the first cell from the first DU; Based on the first information, the first cell is instructed to allow a UE of the first user equipment (UE) type to access the first cell, and first configuration information is generated for configuring the UE of the first UE type to measure and / or access the first cell; Receive second information for the first cell from the first DU; Based on the second information, the first cell is instructed to allow a UE of the second UE type to access the first cell, and second configuration information is generated for configuring a UE of the second UE type to measure and / or access the first cell. Receive third information for the first cell from the first DU; and Based on the third information, the first cell is instructed to allow a UE of the third UE type to access the first cell, and third configuration information is generated for configuring the third type of UE to measure and / or access the first cell.

[0197] Example 9: The method described in Example 8 includes: Send a FI setting response message to the DU, the FI setting response message including: The first configuration information; The second configuration information; or Both the first configuration information and the second configuration information.

[0198] Example 10: According to the method of Example 9, wherein the first configuration includes a first system information block (SIB); wherein the first SIB includes one or more of SIB2, SIB3, SIB4, SIB5, SIB6, SIB7, SIB8 and / or SIB9; wherein the second configuration includes a second SIB; and wherein the second SIB includes one or more of SIB2, SIB3, SIB4, SIB5, SIB6, SIB7, SIB8 and / or SIB9.

[0199] Example 11: The method according to any one of Examples 8 to 10, wherein the first information includes one or more of the following: Information indicating reduced capabilities (RedCap); Information indicating further reduction in capabilities (fRedCap); One or more system information IEs; and / or Slice support information; and The second information includes one or more of the following: The RedCap information; The fRedCap information; The one or more system information IEs; and / or The slice supports information.

[0200] Example 12: The method described in Example 11, wherein the RedCap information includes RedCap broadcast information (IE).

[0201] Example 13: According to any one of Examples 8 to 12, receiving the first information for the first cell from the first DU includes: Receive F1 setup request message from the DU.

[0202] Example 14: The method according to any one of Examples 8 to 13 includes: Receive a DU configuration update message from the DU to update at least a portion of the first configuration information or the second configuration information; and In response to receiving the DU configuration update message, a DU configuration update confirmation message is sent to the DU.

[0203] Example 15: The method described in Example 14 includes: The new CU configuration information for the first cell is included in the DU configuration update confirmation message to update the CU configuration information included in the F1 setting response message.

[0204] Example 16: The method according to any one of Examples 8 to 15, wherein the first UE type is a RedCap UE with reduced capability; wherein the second UE type is a RedCap UE with further reduced capability; and wherein the third UE type is a UE with normal capability.

[0205] Example 17: A method for a user equipment (UE) whose management capabilities are reduced by a base station's distributed unit (DU), the method comprising: Perform a random access procedure with the UE; During the random access process, the UE receives a Media Access Control (MAC) Protocol Data Unit (PDU), which includes a Logical Channel Identifier (LCID) and a message. Include the received message in the DU to CU message; Identify the value of the LCID, wherein the value is a first value, a second value, or a third value; If the identified value is either the first or the second value, then the indication for the second type of UE will be included in the DU-to-CU message; and The DU to CU message is sent to the central unit (CU).

[0206] Example 18: A method for a user equipment (UE) whose management capabilities are reduced by a base station's distributed unit (DU), the method comprising: Broadcast first random access (RA) configuration; Broadcast second RA configuration; Broadcast third RA configuration; Perform a random access procedure with the UE; During the random access process, the UE receives a Media Access Control (MAC) Protocol Data Unit (PDU), which includes a Logical Channel Identifier (LCID) and a message. Include the received message in the 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, an indication for the first type of UE is included in the DU to CU message; and The DU to CU message is sent to the central unit (CU).

[0207] Example 19: A method for a user equipment (UE) whose management capabilities are reduced by a base station's distributed unit (DU), the method comprising: Broadcast first random access (RA) configuration; Broadcast second RA configuration; Broadcast third RA configuration; Perform a random access procedure with the UE; During the random access process, the UE receives a Media Access Control (MAC) Protocol Data Unit (PDU), which includes a Logical Channel Identifier (LCID) and a message. Include the received message in the 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, an indication for the second type of UE will be included in the DU to CU message; and The DU to CU message is sent to the central unit (CU).

[0208] Example 20: A method for a user equipment (UE) whose management capabilities are reduced by a base station's distributed unit (DU), the method comprising: Send a first DU to CU message to the CU, including first information about the first cell, wherein the first information indicates whether a UE of the first UE type is allowed to access the first cell; Send a second DU to CU message to the CU, including second information about the first cell, wherein the second information indicates whether a UE of a second UE type is allowed to access the first cell; Broadcast the first information on the first cell; and The second information is broadcast on the first cell.

[0209] Example 21: A method for a user equipment (UE) whose management capabilities are reduced by a base station's distributed unit (DU), the method comprising: Send a first DU to CU message to the CU, including first information and second information for the first cell, wherein the first information indicates whether a UE of a first UE type is allowed to access the first cell, and the second information indicates whether a UE of a second UE type is allowed to access the first cell; Broadcast the first information on the first cell; and The second information is broadcast on the first cell.

[0210] Example 22: A method for a user equipment (UE) whose management capabilities are reduced by a base station's distributed unit (DU), the method comprising: Communicates with the UE and the central unit (CU); If the type of the UE is the first type, then: Generate the first configuration; and Send the first configuration to the CU; If the type of the UE is type 2, then: Generate a second configuration; and Send the second configuration to the CU; If the type of the UE is type 3, then: Generate a third configuration; and The third configuration is sent to the CU.

[0211] Example 23: A method for a user equipment (UE) whose management capabilities are reduced by a base station's distributed unit (DU), the method comprising: Communicates with the UE and the central unit (CU); If the type of the UE is type 1 or type 2, then: Generate a second configuration; and Send the second configuration to the CU; If the type of the UE is type 3, then: Generate a third configuration; and The third configuration is sent to the CU.

[0212] Example 24: A method for user equipment (UE) with reduced management capabilities due to a central unit (CU) of a base station, the method comprising: Receive first information for the first cell from the first DU; Based on the first information, identify whether the first cell allows access for a UE of the first UE type; Based on the identification that the first cell allows UEs of the first UE type to access, the UEs of the first UE type are configured to measure and / or access the first cell; Receive second information for the first cell from the first DU; Based on the second information, determine whether the first cell allows access for a UE of the second UE type; and Based on whether the first cell allows access for the second UE type, the second UE type is configured to measure and / or access the first cell.

[0213] Example 25: A method for a user equipment (UE) whose management capabilities are reduced by the central unit (CU) of a base station, the method comprising: Receive cell information for the cell from the DU; If the cell information includes the first information, then: If, based on the first information, the first cell allows a UE of the first UE type to access, then the UE of the first UE type is configured to measure and / or access the first cell; If the cell information includes the second information, then: If, based on the first information, the first cell allows access for a UE of the second UE type, then the UE of the second UE type is configured to measure and / or access the first cell.

[0214] Example 26: A method for a user equipment (UE) whose management capabilities are reduced due to a radio access network (RAN) node, the method comprising: The first part of configuring radio resources is used for communication with UEs of the first UE type on the cell; The second part configures radio resources for communication with a UE of the second UE type on the cell; The third part of the configuration radio resources is used for communication with a UE of a third UE type on the cell; The first portion of the radio resources is used to communicate with a UE of the first UE type on the cell; The second portion of the radio resources is used to communicate with a UE of the second UE type on the cell; and The third portion of radio resources is used to communicate with the third type of UE on the cell.

[0215] Example 27: A method for a user equipment (UE) whose management capabilities are reduced due to a radio access network (RAN) node, the method comprising: The first part of configuring radio resources is used for communication with UEs of the first UE type on the cell; The first part of the radio resources is configured for communication with a UE of the second UE type on the cell; The second part configures radio resources for communication with a third type of UE on the cell; The first portion of the radio resources is used to communicate with a UE of the first UE type on the cell; Using the first portion of radio resources to communicate with a UE of the second UE type on the cell; and The second portion of the radio resources is used to communicate with the third type of UE on the cell.

[0216] Example 28: A device comprising: Processor; and A computer-readable storage medium comprising instructions that, in response to execution by the processor, instruct the device to perform any of the methods according to any one of Examples 1 to 27.

Claims

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 medium access control, MAC, protocol data unit, PDU, from the UE in the random access procedure, the MAC PDU comprising 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 the first value, including an indication of a first type of UE in the DU-to-CU message; if the identified value is the second value, including an indication of the first type of UE in the DU-to-CU message; and sending the DU-to-CU message to a central unit, CU.

2. The method of claim 1, wherein, the first value indicating 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 according to any of the preceding claims, wherein, sending the DU-to-CU message to the CU directs the CU to generate an RRC response message for the UE, the method further comprising: receiving the RRC response message for the UE from the CU; and sending the RRC response message to the UE.

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

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

7. The method of claim 4, wherein, an RRCSetupRequest message; an RRCResumeRequest message; or an RRCReestablishmentRequest message.

8. A method of performing a F1 setup procedure by a central unit, CU, with a first distributed unit, DU, 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 a first type of user equipment, UE, to access the first cell, generating first configuration information for configuring the first type of UE 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 a second type of UE to access the first cell, generating second configuration information for configuring the second type of UE 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 a third type of UE to access the first cell, generating third configuration information for configuring the third type of UE to measure and / or access the first cell.

9. The method of claim 8, comprising: sending, to the DU, a FI setup response message, the FI setup response message including: the first configuration information; the second configuration information; or both the first configuration information and the second configuration information.

10. The method of claim 9, wherein, the first configuration includes a first system information block, SIB; wherein the first SIB includes one or more of SIB2, SIB3, SIB4, SIB5, SIB6, SIB7, SIB8, and / or SIB9; wherein the second configuration includes a second SIB; and wherein the second SIB includes one or more of SIB2, SIB3, SIB4, SIB5, SIB6, SIB7, SIB8, and / or SIB9.

11. The method of any one of claims 8-10, wherein, the first information includes one or more of: RedCap information of reduced capability; fRedCap information of further reduced capability; one or more system information IEs; and / or slice support information; and wherein the second information includes one or more of: the RedCap information; the fRedCap information; the one or more system information IEs; and / or the slice support information.

12. The method of claim 11, wherein, the RedCap information includes a RedCap broadcast information IE.

13. The method of any of claims 8-12, receiving, from the first DU, the first information for the first cell comprises: receiving, from the DU, a F1 setup request message.

14. The method of any of claims 8-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 receiving the DU configuration update message, sending, to the DU, a DU configuration update acknowledgement message.

15. The method of claim 14, comprising: including, in the DU configuration update acknowledgement message, new CU configuration information for the first cell to update CU configuration information included in a F1 setup response message.

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

17. An apparatus comprising: a processor; and a computer readable storage medium comprising instructions that, in response to execution by the processor, direct the apparatus to perform any of the methods of any of claims 1-16. ​

Images