Signaling in a split wireless network node architecture

Abstract

The radio network node 14 is divided into a centralized unit 14A and one or more distributed units in the radio access network 10. The distributed unit 14B of the radio network node 14 transmits information 20 indicating that the wireless communication device 12 is a reduced capabilities (RedCap) user equipment (UE) to the centralized unit 14A. The information 20 may be transmitted, for example, in a RedCap indication information element of a message transmitted to the centralized unit 14A, for example, in an INITIAL UL RRC MESSAGE TRANSFER message.

Description

[Technical Field]

[0001] This application relates generally to split wireless network node architectures, and more particularly to signaling in such architectures. [Background technology]

[0002] The initial release of 5G in Release 15 is optimized for mobile broadband (MBB) and ultra-reliable low-latency communications (URLLC). These services require very high data rates and / or low latency, and therefore impose high requirements on user equipment (UE). To enable 5G to be used for other services with more relaxed performance requirements, a new low-complexity UE type, called a "reduced-capability NR device" or RedCap, is introduced in Release 17. The low-complexity UE type is particularly suitable for machine-type communication (MTC) services such as wireless sensors or video surveillance, but can also be used for MBB services with lower performance requirements, such as wearables. A low-complexity UE in Rel-17 has reduced capabilities compared to a Release-15 new radio (NR) UE. See, for example, the Rel-17 work item description in RP-210918. Due to its reduced capabilities, a low-complexity UE is sometimes referred to as an NR RedCap UE.

[0003] A RedCap UE may be defined, for example, by support of a maximum UE bandwidth of 20 MHz (in FR1) or 100 MHz (in FR2), possible support of only one multiple-input multiple-output (MIMO) layer and / or only one Rx antenna branch, support of 64QAM in the downlink (with 256QAM optionally), and half-duplex frequency division duplex (HD-FDD) operation within one carrier.

[0004] While RedCap UEs enable 5G to be used for other services with more relaxed performance requirements, they pose challenges in split radio network architectures. Split radio network architectures split radio network equipment (e.g., base stations) into a so-called centralized unit (CU) and one or more so-called distributed units (DUs). The centralized unit terminates higher-layer and / or less time-critical protocols, such as Packet Data Convergence Protocol (PDCP) and Radio Resource Control (RRC) protocols, that are directed toward wireless devices. The centralized unit also controls the operation of the distributed unit(s). In contrast, the distributed units terminate lower-layer and / or more time-critical protocols, such as Radio Link Control (RLC), Medium Access Control (MAC), and physical layer protocols. The split nature of radio network equipment can isolate the CU and / or DU(s) from the UE's RedCap capabilities, such that RedCap UEs can adversely affect the network. Summary of the Invention

[0005] Some embodiments herein consider reduced capabilities (RedCap) user equipment (UE) in radio access networks with split architectures. In this regard, some embodiments provide support for RedCap UE indications in procedure(s) between a centralized unit (CU) and a distributed unit (DU) of radio network equipment, e.g., in procedures for initial UE access, UE context setup, and / or paging. Support for RedCap UE indications in these and other embodiments may advantageously enable procedures in split radio network architectures to take into account the RedCap nature of UEs, as needed, e.g., to optimize the network and / or otherwise tailor procedures for RedCap UEs.

[0006] More specifically, embodiments herein include a method performed by a distributed unit of a radio network node that is divided into a centralized unit and one or more distributed units in a radio access network, the method including transmitting information from the distributed unit to the centralized unit indicating that a wireless communication device is a reduced capabilities (RedCap) user equipment (UE).

[0007] In some embodiments, the information is transmitted over an F1 interface between the distributed and centralized units.

[0008] In some embodiments, the information is carried in a message sent by the distributed unit to forward the initial Layer 3 message to the centralized unit.

[0009] In some embodiments, the information is transmitted in an INITIAL UL RRC MESSAGE TRANSFER message.

[0010] In some embodiments, the RedCap UE has a maximum bandwidth of 20 MHz in the first frequency range FR1 and a maximum bandwidth of 100 MHz in the second frequency range FR2. In some embodiments, the RedCap UE lacks support for carrier aggregation and lacks support for dual connectivity. In some embodiments, the RedCap UE supports up to two receive branches and / or up to two downlink multiple-input multiple-output layers.

[0011] In some embodiments, the information indicates that the wireless communication device is a New Radio (NR) RedCap UE.

[0012] In some embodiments, the information is included in a RedCap indication information element in a message transmitted from the distributed unit to the centralized unit.

[0013] In some embodiments, the method further includes receiving an indication from the wireless communication device in a random access procedure that the wireless communication device is a RedCap UE. In some embodiments, the information is transmitted to the central unit in response to receiving the indication from the wireless communication device.

[0014] In some embodiments, the method further includes receiving a paging message from the centralized unit requesting the distributed unit to page the wireless communication device. In some embodiments, the paging message includes information indicating that the wireless communication device to be paged is a RedCap UE. In this case, the method further includes paging the wireless communication device based on the information included in the paging message.

[0015] Other embodiments herein include a method performed by a central unit of a radio network node in a radio access network divided into a centralized unit and one or more distributed units, the method including receiving information from a distributed unit of the radio network node that a wireless communication device is a reduced capabilities (RedCap) user equipment (UE).

[0016] In some embodiments, the information is received via an F1 interface between the distributed unit and the centralized unit.

[0017] In some embodiments, the information is received in a message sent by the distributed unit to forward the initial Layer 3 message to the centralized unit.

[0018] In some embodiments, the information is received in an INITIAL UL RRC MESSAGE TRANSFER message.

[0019] In some embodiments, the information indicates that the wireless communication device is a New Radio (NR) RedCap UE.

[0020] In some embodiments, the RedCap UE has a maximum bandwidth of 20 MHz in the first frequency range FR1 and a maximum bandwidth of 100 MHz in the second frequency range FR2. In some embodiments, the RedCap UE lacks support for carrier aggregation and lacks support for dual connectivity. In some embodiments, the RedCap UE supports up to two receive branches and / or up to two downlink multiple-input multiple-output layers.

[0021] In some embodiments, the information is included in a RedCap indication information element of a message received from a distributed unit.

[0022] In some embodiments, the method further includes, in response to receiving the information, transmitting an indication to another network node that the wireless communication device is a RedCap UE. In some embodiments, the indication is transmitted in an INITIAL UE MESSAGE. Additionally or alternatively, in other embodiments, the another network node implements an Access and Mobility Function (AMF).

[0023] In some embodiments, the method further includes transmitting a paging message to the distributed unit requesting the distributed unit to page the wireless communication device, hi some embodiments, the paging message includes information indicating that the wireless communication device to be paged is a RedCap UE.

[0024] Other embodiments herein include a distributed unit of a radio network node that is divided into a centralized unit and one or more distributed units in a radio access network, the distributed units configured to transmit information from the distributed unit to the centralized unit indicating that the wireless communication device is a reduced capabilities (RedCap) user equipment (UE).

[0025] In some embodiments, the distributed unit is configured to perform the steps described above for the distributed unit.

[0026] Other embodiments herein include a central unit of a radio network node in a radio access network divided into a centralized unit and one or more distributed units, the central unit configured to receive information from the distributed units of the radio network node that a wireless communication device is a reduced capabilities (RedCap) user equipment (UE).

[0027] In some embodiments, the central unit is configured to perform the steps described above for the central unit.

[0028] Other embodiments herein include computer programs comprising instructions that, when executed by at least one processor of a distributed unit of a radio network node that is divided into a centralized unit and one or more distributed units in a radio access network, cause the distributed unit to perform the steps described above for the distributed unit. Other embodiments herein include computer programs comprising instructions that, when executed by at least one processor of a central unit of a radio network node that is divided into a centralized unit and one or more distributed units in a radio access network, cause the central unit to perform the steps described above for the central unit. In some embodiments, the carrier containing the computer program is one of an electronic signal, an optical signal, a radio signal, or a computer-readable storage medium.

[0029] Other embodiments herein include a distributed unit of a radio network node that is divided into a centralized unit and one or more distributed units in a radio access network, the distributed unit comprising communication circuitry and processing circuitry, the processing circuitry configured to transmit information from the distributed unit to the centralized unit indicating that the wireless communication device is reduced capabilities (RedCap) user equipment (UE).

[0030] In some embodiments, the processing circuitry is configured to perform the steps described above for the distributed unit.

[0031] Other embodiments herein include a central unit of a radio network node in a radio access network divided into a centralized unit and one or more distributed units, the central unit comprising communication circuitry and processing circuitry configured to receive, from the distributed units of the radio network node, information that a wireless communication device is a reduced capabilities (RedCap) user equipment (UE).

[0032] In some embodiments, the processing circuitry is configured to perform the steps described above for the central unit.

[0033] Although some embodiments herein are illustrated with respect to a RedCap UE, the embodiments herein may generally extend to any type, capability, configuration, and / or feature supported by a wireless communication device. Thus, a wireless communication device that is a RedCap UE is merely one example of a type, capability, configuration, and / or feature supported by a wireless communication device herein. [Brief explanation of the drawings]

[0034] [Figure 1] FIG. 1 is a block diagram of a radio access network according to some embodiments. [Figure 2] FIG. 10 is a logic flow diagram of a method performed by a distributed unit of a radio network node according to some embodiments. [Figure 3] FIG. 10 is a logic flow diagram of a method performed by a centralized unit of a radio network node according to some embodiments. [Figure 4] FIG. 1 is a block diagram of a split radio access network architecture in an LTE network and an NR network, according to some embodiments. [Figure 5] FIG. 10 is a call flow diagram of a UE initial access procedure according to some embodiments. [Figure 6] FIG. 1 is a call flow diagram of a gNB-DU inter-mobility procedure in NR according to some embodiments. [Figure 7] FIG. 10 is a call flow diagram of an F1 paging procedure according to some embodiments. [Figure 8] FIG. 2 is a block diagram of a distributed unit of a radio network node according to some embodiments. [Figure 9] FIG. 2 is a block diagram of a centralized unit of a radio network node according to some embodiments. [Figure 10] FIG. 2 is a block diagram of a network node according to some embodiments. [Figure 11] 1 is a block diagram of a communication system according to some embodiments. [Figure 12] FIG. 1 is a block diagram of a user equipment, according to some embodiments. [Figure 13] FIG. 2 is a block diagram of a network node according to some embodiments. [Figure 14] FIG. 2 is a block diagram of a host according to some embodiments. [Figure 15] FIG. 1 is a block diagram of a virtualization environment in accordance with some embodiments. [Figure 16] FIG. 1 is a block diagram of a host communicating with a UE via a network node over a partial wireless connection according to some embodiments. DETAILED DESCRIPTION OF THE INVENTION

[0035] 1 illustrates a radio access network (RAN) 10 that provides radio access to wireless communication devices 12, according to some embodiments. The RAN 10 may be, for example, a 5G RAN. The RAN 10 includes a radio network node 14 that is divided into a centralized unit 14A and one or more distributed units (DUs), one of which is shown as distributed unit 14B.

[0036] In some embodiments, the centralized unit 14A terminates higher layer and / or less time-critical protocols, such as Packet Data Convergence Protocol (PDCP) and Radio Resource Control (RRC) protocols, for the wireless communication devices 12. The centralized unit 14A also controls the operation of the distributed unit(s), which, in contrast, terminate lower layer and / or more time-critical protocols, such as Radio Link Control (RLC), Medium Access Control (MAC), and physical layer protocols.

[0037] 1, in some embodiments, the distributed unit 14B transmits information 20 to the centralized unit 14A, for example, via an F1 interface between the distributed unit 14B and the centralized unit 14A. The information 20 indicates the type, capabilities, configuration, and / or features supported by the wireless communication device 12.

[0038] In some embodiments, the distributed unit 14B transmits this information 20 to the centralized unit 14A in response to or based on receiving an indication from the wireless communication device 12 itself indicating the type, capabilities, settings, and / or features supported by the wireless communication device 12. The distributed unit 14B may receive such an indication, for example, during a random access procedure with the wireless communication device, and then transmit the information 20 to the centralized unit 14A in response to receiving such an indication.

[0039] In any event, armed with information 20, the centralized unit 14A can then take into account the types, capabilities, configurations, and / or features supported by the wireless communication devices 12. The centralized unit 14A can take such into account, for example, when paging the wireless communication devices 12. In one embodiment, for example, the centralized unit 14A transmits a paging message (not shown) to the distributed unit 14B requesting the distributed unit 14B to page the wireless communication devices 12, the paging message including information indicating that the wireless communication devices 12 to be paged have a particular type, capabilities, and / or configuration and / or support particular features. The distributed unit 14B can then control its paging based on the information included in the paging message.

[0040] In one example, the information 20 that the distributed unit 14B transmits to the centralized unit 14A indicates that the wireless communication device 12 is a reduced capabilities (RedCap) user equipment (UE), e.g., a New Radio (NR) RedCap UE. The information 20 may be included, for example, in a RedCap indication information element (IE) 22 of a message transmitted from the distributed unit 14B to the centralized unit 14A, e.g., a message sent by the distributed unit 14B to forward an initial Layer 3 message to the centralized unit 14A, such as an INITIAL UL RRC MESSAGE TRANSFER message. In these embodiments, the centralized unit 14A may then take the RedCap nature of the wireless communication device 12 into account, for example, when paging the wireless communication device 12.

[0041] 2 illustrates a method according to one or more of these embodiments relating to a RedCap UE. The method is performed by a distributed unit (DU) 14B of a radio network node 14 that is divided into a centralized unit (CU) 14A and one or more distributed units (DUs) in a radio access network 10. The method includes transmitting information 20 from the distributed unit 14B to the centralized unit 14A indicating that the wireless communication device 12 is reduced capabilities (RedCap) user equipment (UE) (block 210).

[0042] In some embodiments, the method also includes receiving an indication from the wireless communication device 12 that the wireless communication device 12 is a RedCap UE in a random access procedure (block 200). In one such embodiment, the step of transmitting the information 20 to the centralized unit 14A may then be performed in response to or based on the indication received from the wireless communication device 12.

[0043] In any event, in some embodiments, the method also includes receiving a paging message from the centralized unit 14A requesting the distributed unit 14B to page the wireless communication device 12 (block 220). In one embodiment, the paging message includes information indicating that the wireless communication device 12 being paged is a RedCap UE. The method in this case may also include paging the wireless communication device 12 based on the information included in the paging message (block 230).

[0044] 3 illustrates a method according to another specific embodiment related to RedCap UE. The method is performed by a central unit 14A of a radio network node 14 that is divided into a centralized unit 14A and one or more distributed units within a radio access network 10. The method includes receiving information 20 from a distributed unit 14B of the radio network node 14 that the wireless communication device 12 is a reduced capabilities (RedCap) user equipment (UE) (Block 300).

[0045] In some embodiments, the method also includes transmitting an indication that the wireless communication device 12 is a RedCap UE to another network node in response to receiving the information 20 (block 310).

[0046] Alternatively or additionally, in some embodiments, the method also includes transmitting a paging message to the distributed unit 14B requesting the distributed unit 14B to page the wireless communication device 12 (block 320). In one embodiment, the paging message includes information indicating that the wireless communication device 12 being paged is a RedCap UE.

[0047] In some embodiments herein, a RedCap UE may be as described below. A RedCap UE may have, for example, a reduced maximum UE bandwidth. For example, the maximum bandwidth of a Frequency Range 1 (FR1) RedCap UE during and after initial access may be 20 MHz, and / or the maximum bandwidth of a Frequency Range 2 (FR2) RedCap UE during and after initial access may be 100 MHz. Alternatively or additionally, a RedCap UE may have a reduced minimum number of receive (Rx) branches. For example, for frequency bands where a legacy NR UE is required to be equipped with a minimum of two Rx antenna ports, the minimum number of Rx branches supported by the specification for a RedCap UE may be one. The specification may also support two Rx branches for a RedCap UE in these bands. Or, for frequency bands where a legacy NR UE (other than a 2-Rx vehicular UE) is required to be equipped with a minimum of four Rx antenna ports, the minimum number of Rx branches supported by the specification for a RedCap UE may be one. The specification in this case also supports two Rx branches for RedCap UEs in these bands. Alternatively or additionally, RedCap UEs may have a reduced maximum number of downlink (DL) multiple-input multiple-output (MIMO) layers. For example, for a RedCap UE with one Rx branch, one DL MIMO layer is supported. Or, for a RedCap UE with two Rx branches, two DL MIMO layers are supported. Alternatively or additionally, RedCap UEs may have a relaxed maximum modulation order. For example, for FR1 RedCap UEs, support for 256QAM in the downlink (DL) is optional (rather than mandatory). In one embodiment, no other relaxation of the maximum modulation order is specified for RedCap UEs. Alternatively or additionally, RedCap UEs can support half-duplex frequency division duplex (FDD) Type A with minimal specification impact. (Note that FD-FDD and TDD are also supported.)

[0048] In some embodiments, a RedCap UE type may be defined to include capabilities for RedCap UE identification and capabilities to restrict the use of those RedCap capabilities to only RedCap UEs and prevent RedCap UEs from using capabilities not intended for RedCap UEs, including at least carrier aggregation, dual connectivity, and wider bandwidth. In some embodiments, capabilities are defined to allow RedCap UEs to be explicitly identifiable to the network through random access procedures, e.g., Msg1 and / or Msg3, and, if supported, early indication in Msg A, including capabilities for the early indication to be configurable by the network.

[0049] In some embodiments, a system information indication may be specified to indicate whether a RedCap UE can camp on a cell / frequency. In one embodiment, the indication may be specific to the number of Rx branches of the UE. For example, System Information Block #1 (SIB1), rather than the Master Information Block (MIB), may indicate cell restrictions for one Rx branch and two Rx branches separately for a RedCap UE. Cell restrictions for a RedCap UE are per cell (not per Public Land Mobile Network (PLMN)). In one embodiment, a RedCap UE supports an intra-frequency reselection indicator. Early identification of either Msg1 and / or Msg3 may be supported.

[0050] In some embodiments herein, the split radio network architecture may be consistent with that specified by 3GPP for 5G networks, and the radio network node 14 in Figure 1 is illustrated as a split gNB, where there is an interface referred to as F1 within the gNB that interconnects the gNB-Central Unit (gNB-CU) with one or many gNB-Distributed Units (gNB-DUs).

[0051] As an example of the centralized unit 14A, the gNB central unit (gNB-CU) is a logical node that hosts the RRC, Service Data Adaptation Protocol (SDAP), and PDCP protocols of the gNB, or the RRC and PDCP protocols of the en-gNB that controls the operation of one or more gNB-DUs. The gNB-CU terminates the F1 interface connected to the gNB-DU.

[0052] As an example of a distributed unit 14B, the gNB distributed unit (gNB-DU) is a logical node that hosts the RLC, MAC, and PHY layers of a gNB or en-gNB, and its operation is partially controlled by the gNB-CU. One gNB-DU supports one or more cells. One cell is supported by only one gNB-DU. The gNB-DU terminates the F1 interface connected to the gNB-CU.

[0053] Figure 4 shows the differences between the two NG-RAN architectures for Long Term Evolution (LTE) and NR.

[0054] In these and other situations, the distributed unit 14B in some embodiments herein transmits information 20 to the centralized unit 14A in a UE initial access procedure, as shown in Figure 5. In this regard, as shown in Figure 5, the gNB-DU in some embodiments transmits information 20 herein in an INITIAL UL RRC MESSAGE TRANSFER message in step 2 of Figure 5. Alternatively or additionally, upon receiving an RRC CONNECTION SETUP COMPLETE message indication that the UE is of RedCap type, the gNB-CU finally adds the RedCap indication in the INITIAL UE MESSAGE to the AMF together with the number of Rx branches (step 7). The other steps of the procedure may follow their description in 3GPP TS 38.401 v16.6.0.

[0055] Alternatively or additionally, some embodiments herein take into account the RedCap nature of the UE in the intra-NR inter-gNB-DU mobility procedure shown in Figure 6. This procedure is used when the UE moves from one gNB-DU to another gNB-DU within the same gNB-CU during NR operation.

[0056] In particular, for intra-gNB-DU mobility, this procedure is used when a UE moves from one cell to another within the same gNB-DU or when an intra-cell handover occurs during NR operation, and is supported by the UE Context Modification (gNB-CU Initiated) procedure as specified in TS 38.473 v16.6.0. When an intra-gNB-DU handover is performed (either inter-cell or intra-cell), the gNB-CU provides a new UL General Packet Radio Service (GPRS) Tunneling Protocol (GTP) Tunnel Endpoint ID (TEID) to the gNB-DU, and the gNB-DU provides a new DL GTP TEID to the gNB-CU.

[0057] Alternatively or additionally, some embodiments herein consider the nature of UE RedCap for F1 paging as shown in Figure 7. This procedure is triggered upon receiving a Core Network (CN) paging message for subsequent DL data.

[0058] Generally, in this context, some embodiments herein support RedCap UE-related signaling in a split gNB architecture. In this regard, some embodiments define some extensions in the F1AP specification, for example, to enable RedCap UE barring / cell barring when possible. That is, a gNB-CU according to some embodiments can configure / control which gNB-DU should serve a RedCap UE in which cell, such that the impact of the RedCap UE on the network is minimized.

[0059] Some embodiments herein also consider mobility aspects related to intra / inter gNB-DU mobility when RedCap access restrictions are in place. For example, the gNB-CU according to some embodiments may configure a list of DUs / cells to which a RedCap UE may or may not handover.

[0060] Furthermore, to support Msg1 / Msg3 based on on-demand system information, the gNB-DU is responsible for encoding SIB1. Some embodiments allow SIB1 broadcast to take into account aspects of cell barring.

[0061] Therefore, some embodiments provide methods for supporting RedCap UE identification via F1AP procedures, which may be used for specific reasons, such as initial UE access, UE context setup and paging processes, resource coordination, and gNB-DU mobility restriction.

[0062] For example, from the perspective of the gNB-DU, upon receiving an early indication that the UE is of RedCap type (e.g., in Msg3), the node adds a RedCap UE indication in the F1 INITIAL UL RRC MESSAGE TRANSFER message to the gNB-CU along with the number of Rx branches (step 2 in Figure 5).

[0063] As another example, from the perspective of the gNB-CU, upon receiving an RRC CONNECTION SETUP COMPLETE message indication that the UE is of RedCap type, the gNB-CU finally adds the RedCap indication in the INITIAL UE MESSAGE to the AMF together with the number of Rx branches (step 7 in Figure 5).

[0064] Alternatively or additionally, during the setup of the UE context in the RAN, the gNB-CU can determine which gNB-DU or which cells within a particular gNB-DU are served and to which RedCap UEs should have access restricted. There can be many motivations for this, for example, load balancing between cells serving different types of UEs, and for example, deciding to aggregate all RedCap UE types within one gNB-DU to mitigate their potential interference to non-RedCap UEs. Another reason is to set up DUs serving different Radio Access Technology (RAT) types and separate dedicated traffic coming from those cells.

[0065] Alternatively or additionally, when configuring which DUs can serve a RedCap UE, the gNB-CU transmits UE radio capabilities and possible extended discontinuous reception (eDRX) information (such as eDRX cycle and paging time window (PTW)) to those specific gNB-DUs. For example, when setting up cells in different DUs handling RedCap UEs and non-RedCap UEs, the gNB-CU transmits to the gNB-DU a list of cells that should serve the RedCap UE, or alternatively, a list of cells whose access is restricted to RedCap UEs (e.g., step 9 in Figure 5). Alternatively, the gNB-CU can send a RedCap indication as a new RAT type via F1 signaling. In either case, this can be done via new signaling or using the existing UE CONTEXT SETUP REQUEST procedure (e.g., step 8 in Figure 5).

[0066] Alternatively or additionally, during inter-gNB-DU mobility, when a RedCap UE performs mobility to another DU that is authorized to serve the RedCap UE, the gNB-CU may transmit assistance information, which may be a new indicator or a new RRC container, to this gNB-DU in order to perform load and resource management between the DUs. This may be done via new signaling or by using the existing UE CONTEXT MODIFICATION REQUEST procedure.

[0067] Alternatively or additionally, during the F1 paging process, the gNB-CU provides RedCap UE paging capability information to enable the gNB-DU to calculate the correct paging occasion (PO) and paging frame (PF) for the RedCap UE. The gNB-CU also provides paging eDRX information to the gNB-DU.

[0068] Generally, then, some embodiments herein may advantageously provide support for RedCap UE indication in a split gNB architecture for one or more of the functions described above.

[0069] We now consider some specific examples for RedCap UE. First, consider an example of initial UE access. In one embodiment, the gNB-DU adds a RedCap UE indication with its lower layer configuration in an INITIAL UL RRC MESSAGE TRANSFER to the gNB-CU. This RedCap UE indication is an example of the RedCap UE indication IE 22 of Figure 1. In some embodiments, the number of Rx branches can also be indicated.

[0070] Table 1 below shows the contents of an INITIAL UL RRC MESSAGE TRANSFER according to one or more such embodiments. This message is sent by the gNB-DU to transfer an initial Layer 3 message to the gNB-CU over the F1 interface. As shown, the RedCap Identification IE may have a value Rx1, Rx2, etc., where Rx1 means that the RedCap UE supports one Rx branch, Rx2 means that the RedCap UE supports two Rx branches, etc. TIFF0007738158000001.tif207170

[0071] Next, consider the example of UE context management.

[0072] In one embodiment, the gNB-CU determines which gNB-DUs and which cells among the gNB-DUs should be prohibited or allowed from serving the RedCap UE.

[0073] In another embodiment, the gNB-CU sends information about the RedCap UE to the gNB-DU during the UE context setup request, or to the target gNB-DU in the case of intra-gNB-DU mobility. This may include a list of cells to which the gNB-DU should restrict RedCap UE access; for example, the gNB-DU may use this information when broadcasting SIB1. Alternatively or additionally, the gNB-CU sends a list of cells to which the gNB-DU should allow RedCap UE access. In this case, the gNB-CU may send the RedCap UE identification, Redcap UE NR radio capabilities, RedCap UE capability information required for paging, paging eDRX parameters (eDRX cycle length, paging transmission window (PTW) length for RAN-triggered paging, etc.), as described above, and / or other assistance information for RedCap UE inactive paging, such as an instruction regarding RedCap UE-specific DRX.

[0074] In one such embodiment, the gNB-CU sends a UE CONTEXT SETUP REQUEST message as shown in Table 2. This message is sent by the gNB-CU to request the setup of a UE context. TIFF0007738158000002.tif160170

[0075] The RAN RedCap Paging eDRX Information IE indicates the RAN RedCap Paging eDRX parameters as specified in the SA2 / CT1 / RAN2 specifications. TIFF0007738158000003.tif33170

[0076] In another embodiment, the above mentioned restrictions for cell barring are used based on distinguishing whether the RedCap UE supports 1 Rx branch or 2 Rx branches.

[0077] In one embodiment, the above may be performed during the UE CONTEXT MODIFICATION REQUEST message in case of ongoing inter-gNB-DU mobility.

[0078] In another embodiment, the UE NR capability information can be sent in new signaling from the CU to the DU.

[0079] In another embodiment, the UE NR capability information can be transmitted as part of the RRC information from the CU to the DU.

[0080] Now consider the example of F1 paging. In one embodiment, the gNB-CU sends information about the RedCap UE to the gNB-DU in an F1 PAGING message. This may include: (i) an indication regarding the RedCap UE identity as described above, (ii) Redcap UE capability for paging, and (iii) paging eDRX information such as the eDRX cycle and PTW for RAN-triggered or CN-triggered paging.

[0081] In some embodiments, the paging message is defined as shown in Table 3. This message is sent by the gNB-CU and is used to request the gNB-DU to page the UE. TIFF0007738158000004.tif231170

[0082] Here, maxnoofPagingCells is the maximum number of paging cells, and its maximum value is 512.

[0083] The CN RedCap Paging eDRX Information IE indicates the CN RedCap Paging eDRX parameters as specified in the SA2 / CT1 / RAN2 specification. TIFF0007738158000005.tif32170

[0084] Although the above embodiments are described with respect to NR RedCap UE, all of the above embodiments can be extended if new bandwidth-limited (e.g., further reduced bandwidth from Release-17 RedCap) devices are introduced in future releases, such as Release-18 eRedCap.

[0085] Similarly, embodiments herein may be applicable to cell restrictions between future releases defining NR UE and Rel-17 RedCap UE, may be applicable to coverage extension features described in Release-17 for NR, and / or may be generalized to any feature that may have restricted access and / or different support in different cells.

[0086] Generally, various embodiments of the present specification are listed in the following embodiments: In this case, Group A embodiments list embodiments in which the above gNB-DU is generalized to a distributed unit, Group B embodiments list embodiments in which the above gNB-CU is generalized to a centralized unit, and Group X embodiments list embodiments in which the above AMF is generalized to a network node.

[0087] Group A Embodiments A1. A method performed by a distributed unit of a radio network node that is divided into a centralized unit and one or more distributed units in a radio access network, the method including transmitting information from the distributed unit to the centralized unit indicating a type, capabilities, configuration, and / or features supported by a wireless communication device. A2. The method of embodiment A1, in which the information is transmitted via an F1 interface between the distributed unit and the centralized unit. A3. The method of embodiment A1 or A2, wherein the information is carried in a message sent by the distributed unit to forward the initial Layer 3 message to the centralized unit. A4. The method of any one of embodiments A1 to A3, wherein the information is carried in an INITIAL UL RRC MESSAGE TRANSFER message. A5. The method of any one of embodiments A1 to A4, wherein the information indicates that the wireless communications device is a reduced capabilities (RedCap) user equipment (UE). A6. The method of embodiment A5, wherein the RedCap UE has the capability to support at least one of any one or more of a maximum bandwidth of 100 MHz in the first frequency range FR1 and a maximum bandwidth of 100 MHz in the second frequency range FR2, one or two receive branches, one or two downlink multiple input multiple output layers, and a maximum downlink modulation order of 64QAM. A7. The method of any one of embodiments A1 to A6, wherein the information indicates that the wireless communications device is capable of supporting at least one of any one or more of a maximum bandwidth of 100 MHz in a first frequency range FR1 and a maximum bandwidth of 100 MHz in a second frequency range FR2, one or two receive branches, one or two downlink multiple-input multiple-output layers, and a maximum downlink modulation order of 64QAM. A8. The method of any one of embodiments A1 to A7, wherein the information indicates a physical layer configuration of the wireless communication device. A9. The method of any one of embodiments A1 to A8, wherein the information indicates how many receive branches the wireless communications device supports or is configured with. A10. The method of any of embodiments A1 to A9, further comprising receiving from the wireless communication device an indication of the type, capabilities, settings, and / or features supported by the wireless communication device, the information being transmitted to the central unit in response to receiving the indication from the wireless communication device. A11. The method of embodiment A10, wherein the indication indicates that the wireless communications device is a reduced capability (RedCap) user equipment (UE). A12. The method of embodiment A10 or A11, wherein the indication is received in a random access procedure. A13. The method of embodiment A12, wherein the indication is received in MSG3 or MSGA of the random access procedure. AA1. A method performed by a distributed unit of a radio network node that is divided into a centralized unit and one or more distributed units in a radio access network, the method comprising receiving signaling from the radio access node or the central unit of another radio access node indicating whether the distributed unit serves wireless communication devices having a specified type, capability, configuration, and / or supported features, or whether which cells of the distributed unit serve wireless communication devices having a specified type, capability, configuration, and / or supported features. AA2. The method of embodiment AA1, wherein the signaling indicates whether the distributed unit serves a wireless communication device that is a reduced capability (RedCap) user equipment (UE) or which cell of the distributed unit serves a wireless communication device that is a RedCap UE. AA3. The method of embodiment AA1, wherein the signaling indicates whether the distributed unit serves a wireless communication device that is a reduced capability (RedCap) user equipment (UE) supporting a specified number of receive branches, or which cell of the distributed unit serves a wireless communication device that is a RedCap UE supporting a specified number of receive branches. AA4. The method of embodiment AA1, wherein the signaling also indicates at least one of any one or more of radio access capability information, radio paging information, and enhanced discontinuous reception information. AA5. The method of embodiment AA4, wherein the extended discontinuous reception information indicates RedCap paging eDRX parameters including a RedCap paging eDRX cycle and a RedCap paging time window. AA6. The method of any of embodiments AA1 to AA5, wherein the signaling includes or is included in a UE CONTEXT SETUP REQUEST message requesting the distributed unit to set up a UE context. AA7. The method of any of embodiments AA1 to AA5, wherein the signaling includes or is included in a UE CONTEXT MODIFICATION REQUEST message as part of the inter-gNB-DU mobility procedure. AA8. The method of any of embodiments AA1 to AA7, wherein the RedCap UE has the capability to support at least one of any one or more of a maximum bandwidth of 100 MHz in the first frequency range FR1 and a maximum bandwidth of 100 MHz in the second frequency range FR2, one or two receive branches, one or two downlink multiple input multiple output layers, and a maximum downlink modulation order of 64QAM. AA9. The method of any of embodiments AA1 to AA8, further comprising controlling access to the distributed unit or to one or more cells of the distributed unit by wireless communication devices having specified types, capabilities, configurations, and / or supported features based on the received signaling. AA10. The method of any of embodiments AA1 to AA9, further comprising generating system information based on the received signaling and transmitting the generated system information. AA11. The method of embodiment AA10, wherein generating system information includes generating system information to indicate cell barring information according to the received signaling. AA12. The method of embodiment AA10 or AA11, wherein generating system information includes generating a system information block type 1 (SIB1) based on the received signaling. AAA1. A method performed by a distributed unit of a radio network node that is divided into a centralized unit and one or more distributed units in a radio access network, the method including receiving a paging message from the centralized unit requesting the distributed unit to page a wireless communication device, the paging message including information indicating one or more of: that the wireless communication device has a specified type, capability, configuration, and / or supported features; how many receive branches the wireless communication device supports; and capability information indicating radio capabilities supported by the wireless communication device for paging the wireless communication device. AAA2. The method of embodiment AAA1, wherein the paging message includes information indicating that the wireless communication device has a specified type, capabilities, configuration, and / or supported features. AAA3. The method of any one of embodiments AAA1 to AAA2, wherein the paging message includes information indicating that the wireless communication device is a RedCap UE. AAA4. The method of any of embodiments AAA1 to AAA3, wherein the paging message includes information indicating how many receive branches the wireless communication device supports. AAA5. The method of any one of embodiments AAA1 to AAA4, wherein the paging message includes information indicating capability information. AAA6. The method of any one of embodiments AAA1 to AAA5, wherein the capability information indicates at least one of any one or more of radio access network paging enhanced discontinuous reception information and core network paging enhanced discontinuous reception information. AAA7. The method of any of embodiments AAA1 to AAA6, wherein the capability information indicates at least one of any one or more of a paging extended discontinuous reception cycle for paging the wireless communication device and a paging time window for paging the wireless communication device. AAA8. The method of any one of embodiments AAA1 to AAA7, further comprising paging the wireless communication device based on information contained in the paging message. AAA9. The method of any of embodiments AAA1 to AAA7, further comprising: calculating a paging occasion and / or paging frame for paging the wireless communication device; and paging the wireless communication device in the calculated paging occasion and / or paging frame. AA. The method of any of the preceding embodiments, further comprising providing user data and forwarding the user data to the host via transmission to the network node.

[0088] Group B Embodiments B1. A method performed by a central unit of a radio network node that is divided into a centralized unit and one or more distributed units in a radio access network, the method including receiving, from the distributed unit of the radio network node, information indicating a type of wireless communication device, a capability of the wireless communication device, a configuration of the wireless communication device, and / or features supported by the wireless communication device. B2. The method of embodiment B1, in which the information is received via an F1 interface between the distributed unit and the centralized unit. B3. The method of embodiment B1 or B2, wherein the information is received in a message sent by the distributed unit to forward the initial Layer 3 message to the centralized unit. B4. The method of any one of embodiments B1 to B3, wherein the information is received in an INITIAL UL RRC MESSAGE TRANSFER message. B5. The method of any one of embodiments B1 to B4, wherein the information indicates that the wireless communications device is a reduced capabilities (RedCap) user equipment (UE). B6. The method of embodiment B5, wherein the RedCap UE has the capability to support at least one of any one or more of a maximum bandwidth of 100 MHz in the first frequency range FR1 and a maximum bandwidth of 100 MHz in the second frequency range FR2, one or two receive branches, one or two downlink multiple input multiple output layers, and a maximum downlink modulation order of 64QAM. B7. The method of any of embodiments B1 to B6, wherein the information indicates that the wireless communications device is capable of supporting at least one of any one or more of a maximum bandwidth of 100 MHz in a first frequency range FR1 and a maximum bandwidth of 100 MHz in a second frequency range FR2, one or two receive branches, one or two downlink multiple-input multiple-output layers, and a maximum downlink modulation order of 64QAM. B8. The method of any one of embodiments B1 to B7, wherein the information indicates a physical layer configuration of the wireless communication device. B9. The method of any of embodiments B1-B8, wherein the information indicates how many receive branches the wireless communications device supports or is configured with. B10. The method of any of embodiments B1-B9, further comprising, in response to receiving the information, transmitting to another network node an indication of the type, capabilities, configurations, and / or features supported by the wireless communications device. B11. The method of embodiment B10, wherein the indication indicates that the wireless communications device is a reduced capability (RedCap) user equipment (UE). B12. The method of embodiment B10 or B11, wherein the instruction is transmitted in an INITIAL UE MESSAGE. B13. The method of embodiment B12, wherein the other network node implements an Access and Mobility Function (AMF). BB1. A method performed by a central unit of a radio network node that is divided into a centralized unit and one or more distributed units in a radio access network, the method comprising transmitting from the central unit to another network node an indication of a wireless communication device type, capabilities, configuration, and / or features supported by the wireless communication device. BB2. The method of embodiment BB1, wherein the other network node implements an Access and Mobility Function (AMF). BB3. The method of embodiment BB1 or BB2, wherein the instruction is transmitted in an INITIAL UE MESSAGE. BB4. The method of any one of embodiments BB1 to BB3, wherein the indication is or is included in paging assistance information. BB5. The method of any one of embodiments BB1 to BB4, wherein the indication indicates that the wireless communications device is a reduced capability (RedCap) user equipment (UE). BB6. The method of embodiment BB5, wherein the RedCap UE has the capability to support at least one of any one or more of a maximum bandwidth of 100 MHz in the first frequency range FR1 and a maximum bandwidth of 100 MHz in the second frequency range FR2, one or two receive branches, one or two downlink multiple input multiple output layers, and a maximum downlink modulation order of 64QAM. BB7. The method of any of embodiments BB1 to BB6, wherein the instruction indicates that the wireless communications device is capable of supporting at least one of any one or more of: a maximum bandwidth of 100 MHz in a first frequency range FR1 and a maximum bandwidth of 100 MHz in a second frequency range FR2, one or two receive branches, one or two downlink multiple-input multiple-output layers, and a maximum downlink modulation order of 64QAM. BB8. The method of any one of embodiments BB1 to BB7, wherein the indication indicates a physical layer configuration of the wireless communication device. BB9. The method of any one of embodiments BB1 to BB8, wherein the indication indicates how many receive branches the wireless communications device supports or is configured with. BB10. The method of any of embodiments BB1 to BB9, further comprising receiving information from the distributed unit of the radio network node indicating a type, capabilities, configuration, and / or features supported by the wireless communication device, wherein the indication is transmitted to another network node in response to receiving the information. BB11. The method of embodiment BB10, wherein the information indicates that the wireless communications device is a reduced capabilities (RedCap) user equipment (UE). BB12. The method of embodiment BB10 or BB11, wherein the information is received in an INITIAL UL RRC MESSAGE TRANSFER message. BBB1. A method performed by a central unit of a radio network node that is divided into a centralized unit and one or more distributed units in a radio access network, the method including transmitting signaling from the central unit to the radio access node or a distributed unit of another radio access node indicating whether the distributed unit serves wireless communication devices having a specified type, capability, configuration, and / or supported features, or whether which cells of the distributed unit serve wireless communication devices having a specified type, capability, configuration, and / or supported features. BBB2. The method of embodiment BBB1, wherein the signaling indicates whether the distributed unit serves a wireless communication device that is a reduced capability (RedCap) user equipment (UE) or which cell of the distributed unit serves a wireless communication device that is a RedCap UE. BBB3. The method of embodiment BBB1, wherein the signaling indicates whether the distributed unit serves a wireless communication device that is a reduced capability (RedCap) user equipment (UE) supporting a specified number of receive branches, or which cell of the distributed unit serves a wireless communication device that is a RedCap UE supporting a specified number of receive branches. BBB4. The method of embodiment BBB1, wherein the signaling also indicates at least one of any one or more of radio access capability information, radio paging information, and extended discontinuous reception information. BBB5. The method of embodiment BBB4, wherein the extended discontinuous reception information indicates RedCap paging eDRX parameters including a RedCap paging eDRX cycle and a RedCap paging time window. BBB6. The method of any of embodiments BBB1 to BBB5, wherein the signaling includes or is included in a UE CONTEXT SETUP REQUEST message requesting the distributed unit to set up a UE context. BBB7. The method of any of embodiments BBB1 to BBB5, wherein the signaling includes or is included in a UE CONTEXT MODIFICATION REQUEST message as part of a gNB-DU inter-mobility procedure. BBB8. The method of any of embodiments BBB1 to BBB7, wherein the RedCap UE has the capability to support at least one of any one or more of a maximum bandwidth of 100 MHz in the first frequency range FR1 and a maximum bandwidth of 100 MHz in the second frequency range FR2, one or two receive branches, one or two downlink multiple input multiple output layers, and a maximum downlink modulation order of 64QAM. BBB9. The method of any of embodiments BBB1 to BBB8, further including making a determination regarding whether the distributed unit should serve, or which one or more cells of the distributed unit should serve, that wireless communication device having the specified type, capability, configuration, and / or supported features, and generating signaling based on the determination. BBB10. The method of embodiment BBB9, wherein according to the determination, either different distributed units of the radio access node will serve wireless communication devices having different respective types, capabilities, configurations, and / or supported features, or different cells of the distributed units will serve wireless communication devices having different respective types, capabilities, configurations, and / or supported features. BBBB1. A method performed by a central unit of a radio network node divided into a centralized unit and one or more distributed units in a radio access network, the method including transmitting to the distributed unit of the radio network node a paging message requesting the distributed unit to page a wireless communication device, the paging message including information indicating one or more of: that the wireless communication device has a specified type, capability, configuration, and / or supported features; how many receive branches the wireless communication device supports; and capability information indicating radio capabilities supported by the wireless communication device for paging the wireless communication device. BBBB2. The method of embodiment BBBB1, wherein the paging message includes information indicating that the wireless communication device has a specified type, capabilities, configuration, and / or supported features. BBBB3. The method of embodiment BBBB1 or BBBB2, wherein the paging message includes information indicating that the wireless communication device is a RedCap UE. BBBB4. The method of any of embodiments BBBB1 to BBBB3, wherein the paging message includes information indicating how many receive branches the wireless communication device supports. BBBB5. The method of any of embodiments BBBB1 to BBBB4, wherein the paging message includes information indicating capability information. BBBB6. The method of any of embodiments BBBB1 to BBBB5, wherein the capability information indicates at least one of any one or more of radio access network paging enhanced discontinuous reception information and core network paging enhanced discontinuous reception information. BBBB7. The method of any of embodiments BBBB1 to BBBB6, wherein the capability information indicates at least one of any one or more of a paging extended discontinuous reception cycle for paging the wireless communication device and a paging time window for paging the wireless communication device.

[0089] Group X Embodiments X1. A method performed by a network node, the method including receiving, from a central unit of a radio network node that is divided into a central unit and one or more distributed units, an indication of a type of wireless communication device, a capability of the wireless communication device, a configuration of the wireless communication device, and / or features supported by the wireless communication device. X2. The method of embodiment X1, wherein the network node implements an Access and Mobility Function (AMF). X3. The method of embodiment X1 or X2, wherein the instruction is received in an INITIAL UE MESSAGE. X4. The method of any one of embodiments X1 to X3, wherein the instruction is or is included in paging assistance information. X5. The method of any one of embodiments X1 to X4, wherein the indication indicates that the wireless communications device is a reduced capability (RedCap) user equipment (UE). X6. The method of embodiment X5, wherein the RedCap UE is capable of supporting at least one of any one or more of a maximum bandwidth of 100 MHz in the first frequency range FR1 and a maximum bandwidth of 100 MHz in the second frequency range FR2, one or two receive branches, one or two downlink multiple-input multiple-output layers, and a maximum downlink modulation order of 64QAM. X7. The method of any one of embodiments X1 to X6, wherein the instructions indicate that the wireless communications device is capable of supporting at least one of any one or more of: a maximum bandwidth of 100 MHz in a first frequency range FR1, and a maximum bandwidth of 100 MHz in a second frequency range FR2, one or two receive branches, one or two downlink multiple-input multiple-output layers, and a maximum downlink modulation order of 64QAM. X8. The method of any one of embodiments X1 to X7, wherein the instruction indicates a physical layer configuration of the wireless communication device. X9. The method of any one of embodiments X1 to X8, wherein the indication indicates how many receive branches the wireless communications device supports or is configured with.

[0090] Group C Embodiments C1. A distributed unit of a radio network node that is divided into a centralized unit and one or more distributed units in a radio access network, the distributed unit being configured to perform any of the steps of any of the embodiments in Group A. C2. A distributed unit of a radio network node that is divided into a centralized unit and one or more distributed units in a radio access network, the distributed unit comprising processing circuitry configured to perform any of the steps of any of the embodiments of Group A. C3. A distributed unit of a radio network node that is divided into a centralized unit and one or more distributed units in a radio access network, the distributed unit comprising communications circuitry and processing circuitry configured to perform any of the steps of any of the embodiments of Group A. C4. A distributed unit of a radio network node that is divided into a centralized unit and one or more distributed units in a radio access network, the distributed unit comprising: processing circuitry configured to perform any of the steps of any of the embodiments of Group A; and power supply circuitry configured to provide power to the distributed unit. C5. A distributed unit of a radio network node in a radio access network that is divided into a centralized unit and one or more distributed units, the distributed unit comprising a processing circuit and a memory, the memory containing instructions executable by the processing circuit, whereby the distributed unit is configured to perform any of the steps of any of the embodiments of Group A. C6. Reserved. C7. A computer program comprising instructions that, when executed by at least one processor of a distributed unit of a radio network node that is divided into a centralized unit and one or more distributed units in a radio access network, cause the distributed unit to perform any of the steps of the embodiments of Group A. C8. A carrier comprising the computer program of embodiment C7, the carrier being one of an electronic signal, an optical signal, a radio signal, or a computer-readable storage medium. C9. A central unit of a radio network node that is divided into a centralized unit and one or more distributed units in a radio access network, the central unit being configured to perform any of the steps of any of the embodiments of Group B. C10. A central unit of a radio network node that is divided into a centralized unit and one or more distributed units in a radio access network, the central unit comprising processing circuitry configured to perform any of the steps of any of the embodiments of Group B. C11. A central unit of a radio network node that is divided into a centralized unit and one or more distributed units in a radio access network, the central unit comprising communication circuitry and processing circuitry configured to perform any of the steps of any of the embodiments of Group B. C12. A central unit of a radio network node that is divided into a centralized unit and one or more distributed units in a radio access network, the central unit comprising: processing circuitry configured to perform any of the steps of any of the embodiments of Group B; and power supply circuitry configured to supply power to the central unit. C13. A central unit of a radio network node that is divided into a centralized unit and one or more distributed units in a radio access network, the central unit comprising a processing circuit and a memory, the memory containing instructions executable by the processing circuit, whereby the central unit is configured to perform any of the steps of any of the embodiments of Group B. C14. Reserved. C15. A computer program comprising instructions that, when executed by at least one processor of a central unit of a radio network node that is divided into a centralized unit and one or more distributed units in a radio access network, cause the central unit to perform any of the steps of the embodiments of Group B. C16. Reserved. C17. A carrier comprising the computer program of embodiment C15 or C16, wherein the carrier is one of an electronic signal, an optical signal, a radio signal, or a computer-readable storage medium. C18. A network node configured to perform any of the steps of any of the embodiments of group X. C19. A network node comprising processing circuitry configured to perform any of the steps of any of the embodiments of Group X. C20. A network node comprising: communications circuitry; and processing circuitry configured to perform any of the steps of any of the embodiments of Group X. C21. A network node comprising: processing circuitry configured to perform any of the steps of any of the embodiments of group X; and power supply circuitry configured to supply power to the network node. C22. A network node comprising a processing circuit and a memory, the memory comprising instructions executable by the processing circuit, whereby the network node is configured to perform any of the steps of any of the embodiments of group X. C23. A computer program comprising instructions that, when executed by at least one processor of a network node, cause the network node to perform the steps of any of the embodiments of group X. C24. A carrier comprising the computer program of embodiment C23, the carrier being one of an electronic signal, an optical signal, a radio signal, or a computer-readable storage medium.

[0091] Group D Embodiments D1. A communications system including a host computer having processing circuitry configured to provide user data and a communications interface configured to forward the user data to a cellular network for transmission to user equipment (UE), the cellular network comprising a base station having a radio interface and processing circuitry, the processing circuitry of the base station being configured to perform any of the steps of any of the Group A or Group B embodiments. D2. The communication system of any preceding embodiment, further comprising a base station. D3. The communication system according to the two preceding embodiments, further comprising a UE, the UE being configured to communicate with the base station. D4. A communication system as described in the three preceding embodiments, wherein the processing circuitry of the host computer is configured to execute a host application and thereby provide user data, and the UE comprises processing circuitry configured to execute a client application associated with the host application. D5. A method implemented in a communications system including a host computer, a base station, and user equipment (UE), comprising: providing user data at the host computer; and initiating transmission at the host computer to carry the user data to the UE via a cellular network including the base station, wherein the base station performs any of the steps of any of the Group A or Group B embodiments. D6. The method of any preceding embodiment, further comprising transmitting user data at the base station. D7. The method according to the two preceding embodiments, wherein the user data is provided in the host computer by executing a host application, and the method further comprises executing, in the UE, a client application associated with the host application. D8. A user equipment (UE) configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to perform any of the three preceding embodiments. D9~D22. Reserved. D23. A communications system including a host computer having a communications interface configured to receive user data resulting from a transmission from a user equipment (UE) to a base station, the base station having a radio interface and processing circuitry, the base station's processing circuitry configured to perform any of the steps of any of the Group A or Group B embodiments. D24. The communication system of any preceding embodiment, further comprising a base station. D25. The communication system according to the two preceding embodiments, further comprising a UE, the UE being configured to communicate with the base station. D26. A communication system as described in the three preceding embodiments, wherein the processing circuitry of the host computer is configured to execute a host application, and the UE is configured to execute a client application associated with the host application, thereby providing user data to be received by the host computer.

[0092] Embodiments herein also include corresponding apparatus, for example, a distributed unit 14B of a radio network node 14 configured to perform any of the steps of any of the embodiments described above for the distributed unit 14B.

[0093] The embodiment also includes a distributed unit 14B of the radio network node 14 comprising processing circuitry and power supply circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the distributed unit 14B. The power supply circuitry is configured to provide power to the distributed unit 14B.

[0094] Embodiments further include a distributed unit 14B of the radio network node 14 comprising processing circuitry configured to perform any of the steps of any of the embodiments described above for the distributed unit 14B. In some embodiments, the distributed unit 14B further comprises communications circuitry.

[0095] The embodiment further includes a distributed unit 14B of the radio network node 14 comprising processing circuitry and a memory, the memory including instructions executable by the processing circuitry to configure the distributed unit 14B to perform any of the steps of any of the embodiments described above for the distributed unit 14B.

[0096] Embodiments herein also include a centralized unit 14A of a radio network node 14 configured to perform any of the steps of any of the embodiments described above with respect to the centralized unit 14A.

[0097] The embodiment also includes a centralized unit 14A of the radio network node 14 comprising processing circuitry and power supply circuitry, the processing circuitry configured to perform any of the steps of any of the embodiments described above for the centralized unit 14A, and the power supply circuitry configured to provide power to the centralized unit 14A.

[0098] Embodiments further include a centralized unit 14A of the radio network node 14 comprising processing circuitry configured to perform any of the steps of any of the embodiments described above for the centralized unit 14A. In some embodiments, the centralized unit 14A further comprises communications circuitry.

[0099] The embodiment further includes a centralized unit 14A of the radio network node 14 comprising processing circuitry and a memory, the memory including instructions executable by the processing circuitry to configure the centralized unit 14A to perform any of the steps of any of the embodiments described above for the centralized unit 14A.

[0100] Embodiments herein further include a network node (e.g., implementing AMF) configured to perform any of the steps of any of the embodiments described above for the network node.

[0101] Embodiments also include a network node (e.g., implementing AMF) comprising a processing circuit and a power supply circuit, the processing circuit configured to perform any of the steps of any of the embodiments described above for the network node, and the power supply circuit configured to supply power to the network node.

[0102] Embodiments further include a network node (e.g., implementing AMF) comprising processing circuitry configured to perform any of the steps of any of the embodiments described above for the network node. In some embodiments, the network node further comprises communications circuitry.

[0103] Embodiments further include a network node (e.g., implementing AMF) including a processing circuit and a memory, the memory including instructions executable by the processing circuit, whereby the network node is configured to perform any of the steps of any of the embodiments described above for the network node.

[0104] More specifically, the apparatus described above may perform the methods and any other processes herein by implementing any functional means, modules, units, or circuits. In one embodiment, for example, an apparatus comprises a respective circuit or circuit configuration configured to perform the steps illustrated in the method diagrams. In this regard, the circuit or circuit configuration may include dedicated circuitry for performing specific functional processes and / or one or more microprocessors in conjunction with memory. For example, the circuit may include one or more microprocessors or microcontrollers, as well as other digital hardware that may include digital signal processors (DSPs), dedicated digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or more types of memory, such as read-only memory (ROM), random access memory, cache memory, flash memory devices, optical storage devices, and the like. The program code stored in memory, in some embodiments, may include program instructions for implementing one or more communication and / or data communication protocols, as well as instructions for performing one or more of the techniques described herein. In embodiments employing memory, the memory stores program code that, when executed by one or more processors, performs the techniques described herein.

[0105] FIG. 8 illustrates a distributed unit 14B implemented in accordance with one or more embodiments. As shown, the distributed unit 14B includes processing circuitry 810 and communication circuitry 820. The communication circuitry 820 (e.g., radio circuitry) is configured to transmit information to and / or receive information from one or more other nodes, e.g., via any communication technology. Such communication may occur via one or more antennas either internal or external to the distributed unit 14B. The processing circuitry 810 is configured to perform the processing described above for the gNB-DU and / or in FIG. 2, e.g., by executing instructions stored in memory 830. In this regard, the processing circuitry 810 may implement specific functional means, units, or modules.

[0106] 9 illustrates an implemented centralized unit 14A in accordance with one or more embodiments. As illustrated, the centralized unit 14A includes processing circuitry 910 and communication circuitry 920. The communication circuitry 920 is configured to transmit information to and / or receive information from one or more other nodes, e.g., via any communication technology. The processing circuitry 910 is configured to perform, e.g., the processing described above for the gNB-CU and / or in FIG. 3, such as by executing instructions stored in memory 930. In this regard, the processing circuitry 910 may implement specific functional means, units, or modules.

[0107] 10 illustrates a network node 1000 implemented in accordance with one or more embodiments. As shown, the network node 1000 includes a processing circuit 1010 and a communication circuit 1020. The communication circuit 1020 is configured to transmit information to one or more other nodes and / or receive information from one or more other nodes, e.g., via any communication technology. The processing circuit 1010 is configured to perform the processing described above for AMF, e.g., by executing instructions stored in a memory 1030. In this regard, the processing circuit 1010 may implement specific functional means, units, or modules.

[0108] Those skilled in the art will also appreciate that the embodiments herein further include corresponding computer programs.

[0109] The computer program comprises instructions that, when executed on at least one processor of the device, cause the device to perform any of the respective operations described above. In this regard, the computer program may comprise one or more code modules corresponding to the means or units described above.

[0110] Embodiments further include a carrier containing such a computer program, which may include one of an electronic signal, an optical signal, a radio signal, or a computer-readable storage medium.

[0111] In this regard, embodiments herein also include a computer program product that is stored on a non-transitory computer-readable (storage or recording) medium and includes instructions that, when executed by a processor of the device, cause the device to perform as described above.

[0112] Embodiments further include a computer program product comprising program code portions for performing the steps of any of the embodiments herein when the computer program product is executed by a computing device, and the computer program product may be stored on a computer-readable recording medium.

[0113] Additional embodiments are now described, at least some of which may be described, for purposes of illustration, as being applicable in particular contexts and / or wireless network types, although the embodiments may be equally applicable in other contexts and / or wireless network types not expressly described.

[0114] FIG. 11 illustrates an example of a communication system 1100, according to some embodiments.

[0115] In this example, communications system 1100 includes a communications network 1102 including an access network 1104, such as a radio access network (RAN), and a core network 1106 including one or more core network nodes 1108. Access network 1104 includes one or more access network nodes, such as network nodes 1110a and 1110b (one or more of which may be generally referred to as network nodes 1110), or any other similar Third Generation Partnership Project (3GPP) access nodes or non-3GPP access points. Network nodes 1110 facilitate direct or indirect connectivity of user equipment (UE), such as by connecting UEs 1112a, 1112b, 1112c, and 1112d (one or more of which may be generally referred to as UEs 1112), to the core network 1106 via one or more wireless connections.

[0116] Exemplary wireless communications over wireless connections include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for carrying information without the use of wires, cables, or other material conductors. Additionally, in different embodiments, communications system 1100 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or be involved in the communication of data and / or signals, whether via wired or wireless connections. Communications system 1100 may include and / or interface with any type of communications, remote communications, data, cellular, wireless networks, and / or other similar types of systems.

[0117] The UE 1112 may be any of a wide variety of communications devices, including a wireless device that is positioned, configured, and / or operative to communicate wirelessly with the network node 1110 and other communications devices. Similarly, the network node 1110 is positioned, enabled, configured, and / or operative to communicate, directly or indirectly, with the UE 1112 and / or other network nodes or equipment within the communications network 1102 to enable and / or provide network access, such as wireless network access, and / or perform other functions, such as management, within the communications network 1102.

[0118] In the depicted example, the core network 1106 connects the network node 1110 to one or more hosts, such as the host 1116. These connections may be direct or indirect via one or more intermediate networks or devices. In other examples, the network nodes may be directly coupled to the hosts. The core network 1106 includes one or more core network nodes (e.g., the core network node 1108) constructed of hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, and therefore, those descriptions are generally applicable to the corresponding components of the core network node 1108. Exemplary core network nodes include one or more of the following functions: a Mobile Switching Center (MSC), a Mobility Management Entity (MME), a Home Subscriber Server (HSS), an Access and Mobility Management Function (AMF), a Session Management Function (SMF), an Authentication Server Function (AUSF), a Subscription Identifier Deconceal Function (SIDF), a Unified Data Management (UDM), a Security Edge Protection Proxy (SEPP), a Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0119] The host 1116 may be owned or under the control of, and may be operated by, or on behalf of, a service provider other than the operator or provider of the access network 1104 and / or the communications network 1102. The host 1116 may host various applications to provide one or more services. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data about various ambient conditions detected by multiple UEs, analytics functions, social media, functions for controlling or otherwise interacting with remote devices, functions for alarm and monitoring centers, or any other such functions performed by a server.

[0120] 11 enables connectivity between UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as a particular standard, including, but not limited to, Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable next-generation standard (e.g., 6G), a wireless local area network (WLAN) standard such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard (WiFi), and / or any other suitable wireless communication standard such as Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC), ZigBee, LiFi, and / or any low-power wide area network (LPWAN) standard such as LoRa and Sigfox.

[0121] In some examples, the communication network 1102 is a cellular network that implements 3GPP standardized features. Thus, the communication network 1102 can support network slicing to provide different logical networks to different devices connected to the communication network 1102. For example, the communication network 1102 can provide Ultra-Reliable Low Latency Communications (URLLC) services to some UEs, while providing enhanced Mobile Broadband (eMBB) services to other UEs and / or massive machine-type communications (mMTC) / massive IoT services to yet further UEs.

[0122] In some examples, the UE 1112 is configured to transmit and / or receive information without direct human interaction. For example, the UE may be designed to transmit information to the access network 1104 on a predetermined schedule, when triggered by an internal or external event, or in response to a request from the access network 1104. Additionally, the UE may be configured to operate in a single or multi-RAT or multi-standard mode. For example, the UE may operate with any one or a combination of Wi-Fi, NR (New Radio), and LTE, i.e., may be configured for Multi-Radio Dual Connectivity (MR-DC), such as E-UTRAN (Enhanced UMTS Terrestrial Radio Access Network) New Radio Dual Connectivity (EN-DC).

[0123] In this example, the hub 1114 communicates with the access network 1104 to facilitate indirect communication between one or more UEs (e.g., UEs 1112c and / or 1112d) and a network node (e.g., network node 1110b). In some examples, the hub 1114 may be a controller, a router, a content source, an analytics, or any of the other communication devices described herein with respect to UEs. For example, the hub 1114 may be a broadband router that enables access to the core network 1106 for the UE. As another example, the hub 1114 may be a controller that sends commands or instructions to one or more actuators in the UE. The commands or instructions may be received from the UE, the network node 1110, or by executable code, scripts, processes, or other instructions within the hub 1114. As another example, the hub 1114 may be a data collector that serves as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 1114 may be a content source. For example, in the case of a UE that is a VR headset, display, loudspeaker, or other media distribution device, the hub 1114 may retrieve VR assets, video, audio, or other media or data related to the sensory information via a network node, which the hub 1114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In yet another example, the hub 1114 acts as a proxy server or orchestrator for the UEs, particularly if one or more of the UEs are low energy IoT devices.

[0124] The hub 1114 may have a constant / permanent or intermittent connection to the network node 1110b. The hub 1114 may also enable different communication schemes and / or schedules between the hub 1114 and the UEs (e.g., UEs 1112c and / or 1112d) and between the hub 1114 and the core network 1106. In other examples, the hub 1114 is connected to the core network 1106 and / or one or more UEs via a wired connection. Additionally, the hub 1114 may be configured to connect to an M2M service provider via the access network 1104 and / or to another UE via a direct connection. In some scenarios, a UE may establish a wireless connection with the network node 1110b while still connected through the hub 1114 via a wired or wireless connection. In some embodiments, the hub 1114 may be a dedicated hub, i.e., a hub whose primary function is to route communications to / from the UEs to / from the network node 1110b. In other embodiments, the hub 1114 may be a non-dedicated hub, i.e., a device that is operable to route communications between the UE and the network node 1110b, but that is additionally operable to act as a communication initiation and / or termination point for particular data channels.

[0125] Figure 12 illustrates a UE 1200 according to some embodiments. As used herein, a UE refers to a device that is configured, arranged, and / or operable to communicate wirelessly with a network node and / or other UEs. Examples of a UE include, but are not limited to, a smartphone, a mobile phone, a cell phone, a voice-over-IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless camera, a game console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop embedded equipment (LEE), a laptop mounted equipment (LME), a smart device, a wireless customer premises equipment (CPE), an in-vehicle or in-vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a Narrowband Internet of Things (NB-IoT) UE, a Machine Type Communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0126] A UE may support device-to-device (D2D) communications, for example, by implementing 3GPP standards for sidelink communications, dedicated short-range communications (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates an associated device. Instead, a UE may represent a device (e.g., a smart sprinkler controller) that is intended for sale to or operation by a human user, but that may not be associated with or initially associated with a particular human user. Alternatively, a UE may represent a device (e.g., a smart power meter) that is not intended for sale to or operation by an end user, but that may be associated with or operated for the benefit of a user.

[0127] The UE 1200 includes a processing circuit 1202 operably coupled to an input / output interface 1206, a power source 1208, a memory 1210, a communication interface 1212, and / or any other components, or any combination thereof, via a bus 1204. A particular UE may utilize all or a subset of the components shown in FIG. 12. The level of integration between components may vary from one UE to another. Furthermore, a particular UE may include multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0128] Processing circuitry 1202 is configured to process instructions and data, and may be configured to implement any sequential state machine operable to execute instructions stored as a machine-readable computer program in memory 1210. Processing circuitry 1202 may be implemented as one or more hardware-implemented state machines (e.g., discrete logic, field programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), etc.), programmable logic with appropriate firmware, one or more stored computer programs with appropriate software, a general-purpose processor such as a microprocessor or digital signal processor (DSP), or any combination of the above. For example, processing circuitry 1202 may have multiple central processing units (CPUs).

[0129] In this example, the input / output interface 1206 may be configured to provide an input device, an output device, or one or more interfaces to one or more input and / or output devices. Examples of output devices include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smart card, another output device, or any combination thereof. An input device may enable a user to capture information into the UE 1200. Examples of input devices include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a webcam, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smart card, etc. A presence-sensitive display may include a capacitive or resistive touch sensor for sensing input from a user. The sensor may be, for example, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a universal serial bus (USB) port may be used to accommodate input and output devices.

[0130] In some embodiments, the power source 1208 is constructed as a battery or battery pack. Other types of power sources may be used, such as an external power source (e.g., an electrical outlet), a photovoltaic device, or a power cell. The power source 1208 may further include power circuitry for delivering power to various portions of the UE 1200 from the power source 1208 itself and / or from an external power source via an interface, such as an input circuit or a power cable. Delivering power may be for charging the power source 1208, for example. The power circuitry may perform any formatting, conversion, or other modification of the power from the power source 1208 to make it suitable for the respective components of the UE 1200 being powered.

[0131] The memory 1210 may be or be configured to include random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disk, optical disk, hard disk, removable cartridge, flash drive, or other memory. In one example, the memory 1210 includes one or more application programs 1214, such as an operating system, a web browser application, a widget, a gadget engine, or other applications, and corresponding data 1216. The memory 1210 may store any of a wide variety of operating systems or combinations of operating systems for use by the UE 1200.

[0132] The memory 1210 may be configured to include multiple physical drive units, such as a redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smart card memory, such as a tamper-resistant module in the form of a universal integrated circuit card (UICC) containing one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may be, for example, an embedded UICC (eUICC), an integrated UICC (iUICC), or a removable UICC, commonly known as a "SIM card." The memory 1210 may enable the UE 1200 to access, offload, or upload data, instructions, application programs, and the like, stored on a temporary or non-transitory memory medium. An article of manufacture, such as one utilizing a communication system, may be tangibly embodied as or in memory 1210, which may be or comprise a device-readable storage medium.

[0133] The processing circuit 1202 may be configured to communicate with an access network or other networks using a communication interface 1212. The communication interface 1212 may comprise one or more communication subsystems and may include, or be communicatively coupled to, an antenna 1222. The communication interface 1212 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 1218 and / or a receiver 1220 suitable for providing network communication (e.g., optical, electrical, frequency allocation, etc.). Furthermore, the transmitter 1218 and receiver 1220 may be coupled to one or more antennas (e.g., antenna 1222) and may share circuit components, software, or firmware or may be implemented separately.

[0134] In the illustrated embodiment, the communication capabilities of communication interface 1212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, short-range communication, location-based communication such as using a Global Positioning System (GPS) to determine position, another similar communication capability, or any combination thereof. Communications may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, Transmission Control Protocol / Internet Protocol (TCP / IP), Synchronous Optical Network (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), etc.

[0135] Regardless of the type of sensor, the UE can provide an output of data captured by its sensors through its communication interface 1212 via a wireless connection to a network node. Data captured by a UE's sensors can be communicated to a network node via another UE via a wireless connection. The output may be periodic (e.g., once every 15 minutes when reporting sensed temperature), random (e.g., to balance the load from reports from multiple sensors), in response to a trigger event (e.g., when moisture is detected, an alert is sent), in response to a request (e.g., a user-initiated request), or a continuous stream (e.g., a live video feed of the patient).

[0136] As another example, the UE may include an actuator, motor, or switch associated with a communications interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input, the actuator, motor, or switch may change state. For example, the UE may include a motor that adjusts a control surface or rotor of a drone in flight according to the received input, or adjusts a robotic arm that performs a medical procedure according to the received input.

[0137] When the UE is in the form of an Internet of Things (IoT) device, it may be a device for use in one or more application domains, including, but not limited to, urban wearable technology, augmented industrial applications, and healthcare. Non-limiting examples of such IoT devices are, or devices incorporated into, a connected refrigerator or freezer, a TV, a connected lighting device, an electric meter, a robotic vacuum cleaner, a voice-controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electric door lock, a connected doorbell, an air conditioning system such as a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for augmented reality or virtual reality, a wearable device for haptic augmentation or sensory enhancement, a water sprinkler, an animal or item tracking device, a sensor for monitoring plants or animals, an industrial robot, an unmanned aerial vehicle (UAV), and any type of medical device such as a heart rate monitor or a remotely controlled surgical robot. A UE in the form of an IoT device includes circuitry and / or software depending on the intended application of the IoT device, in addition to other components such as those described in connection with the UE 1200 shown in FIG. 12 .

[0138] As yet another specific example, in an IoT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements and transmits the results of such monitoring and / or measurements to another UE and / or a network node. The UE may in this case be an M2M device, and in a 3GPP context may be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, bus, truck, ship, and airplane, or other equipment capable of monitoring and / or reporting its operational status or other functions related to its operation.

[0139] In practice, any number of UEs may be used together for a single use case. For example, a first UE may be a drone or integrated into a drone and provide the drone's speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When a user makes a change from the remote controller, the first UE may adjust a throttle on the drone (e.g., by controlling an actuator) to increase or decrease the drone's speed. The first and / or second UE may also include two or more of the above-mentioned functions. For example, a UE may include a sensor and an actuator and handle communication of data for both the speed sensor and the actuator.

[0140] 13 illustrates a network node 1300 according to some embodiments. As used herein, a network node refers to a device capable of, configured to, arranged to, and / or operable to communicate directly or indirectly with UEs and / or other network nodes or devices in a communications network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., wireless access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs), and NR Node Bs (gNBs)).

[0141] Base stations may be classified based on the amount of coverage they provide (or, stated differently, their transmit power level), and may therefore be referred to as femto, pico, micro, or macro base stations depending on the amount of coverage provided. A base station may be a relay node or a relay donor node that controls a relay. A network node may also include one or more (or all) parts of a distributed radio base station, such as a centralized digital unit and / or a remote radio unit (RRU) (sometimes referred to as a remote radio head (RRH)). Such remote radio units may or may not be integrated with an antenna, such as an antenna-integrated radio. Some of the distributed radio base stations may also be referred to as nodes in a distributed antenna system (DAS).

[0142] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as an MSR BS, a network controller such as a radio network controller (RNC) or base station controller (BSC), a base transceiver station (BTS), a transmission point, a transmission node, a multi-cell / multicast coordination entity (MCE), an operation and maintenance (O&M) node, an operation support system (OSS) node, a self-organizing network (SON) node, a positioning node (e.g., an evolved serving mobile location center (E-SMLC)), and / or minimization of drive tests (MDTs).

[0143] The network node 1300 includes a processing circuit 1302, a memory 1304, a communication interface 1306, and a power source 1308. The network node 1300 may be composed of multiple physically separate components (e.g., a Node B component and an RNC component, or a BTS component and a BSC component, etc.), each of which may have its own respective components. In certain scenarios in which the network node 1300 comprises multiple separate components (e.g., a BTS and a BSC component), one or more of the separate components may be shared among multiple network nodes. For example, a single RNC may control multiple Node Bs. In such scenarios, each unique Node B and RNC pair may, in some cases, be considered a single separate network node. In some embodiments, the network node 1300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 1304 for different RATs) and some components may be reused (e.g., the same antenna 1310 may be shared by different RATs). Network node 1300 may also include multiple sets of the various illustrated components for different wireless technologies, e.g., GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, radio frequency identification (RFID), or Bluetooth wireless technologies, integrated into network node 1300. These wireless technologies may be integrated into the same or different chips or sets of chips and other components within network node 1300.

[0144] The processing circuitry 1302 may comprise one or more combinations of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and / or coded logic operable, alone or in conjunction with other network node 1300 components, such as memory 1304, to provide network node 1300 functionality.

[0145] In some embodiments, the processing circuit 1302 comprises a system on a chip (SOC). In some embodiments, the processing circuit 1302 includes one or more of a radio frequency (RF) transceiver circuit 1312 and a baseband processing circuit 1314. In some embodiments, the radio frequency (RF) transceiver circuit 1312 and the baseband processing circuit 1314 may be on separate chips (or sets of chips), boards, or units, such as a radio unit and a digital unit. In other embodiments, some or all of the RF transceiver circuit 1312 and the baseband processing circuit 1314 may be on the same chip or set of chips, board, or unit.

[0146] The memory 1304 may include any form of volatile or non-volatile computer-readable memory, including, but not limited to, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disks), removable storage media (flash drives, compact discs (CDs), digital video discs (DVDs), etc.), and / or any other volatile or non-volatile non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that can be used by the processing circuit 1302. The memory 1304 may store any suitable instructions, data, or information, including computer programs, software, applications that include one or more of logic, rules, code, tables, and / or other instructions that can be executed by the processing circuit 1302 and utilized by the network node 1300. The memory 1304 may be used to store any calculations performed by the processing circuit 1302 and / or any data received via the communications interface 1306. In some embodiments, the processing circuitry 1302 and the memory 1304 are integrated.

[0147] The communication interface 1306 is used in wired or wireless communication of signaling and / or data between network nodes, access networks, and / or UEs. As shown, the communication interface 1306 includes port(s) / terminal(s) 1316 for transmitting and receiving data to and from a network, e.g., via a wired connection. The communication interface 1306 also includes radio front-end circuitry 1318, which may be coupled to, or in certain embodiments may be part of, the antenna 1310. The radio front-end circuitry 1318 includes a filter 1320 and an amplifier 1322. The radio front-end circuitry 1318 may be connected to the antenna 1310 and the processing circuit 1302. The radio front-end circuitry may be configured to condition signals communicated between the antenna 1310 and the processing circuit 1302. The radio front-end circuitry 1318 may receive digital data to be transmitted to other network nodes or UEs via a wireless connection. The radio front-end circuitry 1318 may convert the digital data into a radio signal having appropriate channel and bandwidth parameters using a combination of filters 1320 and / or amplifiers 1322. The radio signal may then be transmitted via the antenna 1310. Similarly, when receiving data, the antenna 1310 may collect the radio signal, which is then converted into digital data by the radio front-end circuitry 1318. The digital data may be passed to the processing circuitry 1302. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0148] In certain alternative embodiments, the network node 1300 does not include a separate radio front-end circuit 1318; instead, the processing circuit 1302 includes the radio front-end circuitry and is connected to the antenna 1310. Similarly, in some embodiments, all or a portion of the RF transceiver circuitry 1312 is part of the communications interface 1306. In still other embodiments, the communications interface 1306 includes one or more ports or terminals 1316, the radio front-end circuitry 1318, and the RF transceiver circuitry 1312 as part of a radio unit (not shown), and the communications interface 1306 communicates with baseband processing circuitry 1314 that is part of a digital unit (not shown).

[0149] Antenna 1310 may include one or more antennas or an antenna array configured to transmit and / or receive wireless signals. Antenna 1310 may be coupled to radio front-end circuitry 1318 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In certain embodiments, antenna 1310 is separate from network node 1300 and may be connectable to network node 1300 via an interface or port.

[0150] The antenna 1310, the communication interface 1306, and / or the processing circuit 1302 may be configured to perform any receiving operation and / or certain acquisition operations described herein as being performed by a network node. Any information, data, and / or signals may be received from a UE, another network node, and / or any other network equipment. Similarly, the antenna 1310, the communication interface 1306, and / or the processing circuit 1302 may be configured to perform any transmitting operation described herein as being performed by a network node. Any information, data, and / or signals may be transmitted to a UE, another network node, and / or any other network equipment.

[0151] The power source 1308 provides power to the various components of the network node 1300 in a form appropriate for each component (e.g., at the voltage and current levels required for each component). The power source 1308 may further comprise or be coupled to power management circuitry for providing power to the components of the network node 1300 for performing the functions described herein. For example, the network node 1300 may be connectable to an external power source (e.g., a power grid, an electrical outlet) via an input circuit or interface, such as an electrical cable, whereby the external power source provides power to the power circuitry of the power source 1308. As a further example, the power source 1308 may comprise a power source in the form of a battery or battery pack connected to or incorporated into the power circuitry. The battery may provide backup power in the event of a failure of the external power source.

[0152] Embodiments of network node 1300 may include additional components other than those shown in Figure 13 to provide particular aspects of network node functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, network node 1300 may include user interface devices to enable input of information into network node 1300 and output of information from network node 1300. This may allow a user to perform diagnostic, maintenance, repair, and other management functions on network node 1300.

[0153] 14 is a block diagram of a host 1400, which may be an embodiment of the host 1116 of FIG. 11 , in accordance with various aspects described herein. As used herein, the host 1400 may be or comprise various combinations of hardware and / or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, a container, or processing resources within a server farm. The host 1400 may provide one or more services to one or more UEs.

[0154] Host 1400 includes a processing circuit 1402 operably coupled to an input / output interface 1406, a network interface 1408, a power supply 1410, and a memory 1412 via a bus 1404. In other embodiments, other components may be included. Features of these components may be substantially similar to features described with respect to the devices of previous figures, such as Figures 12 and 13, such that the descriptions are generally applicable to the corresponding components of host 1400.

[0155] Memory 1412 may include one or more computer programs, including one or more host application programs 1414, and data 1416, which may include user data, e.g., data generated by the UE for the host 1400 or data generated by the host 1400 for the UE. An embodiment of host 1400 may utilize only a subset or all of the components shown. Host application programs 1414 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UE (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application program 1414 may also provide user authentication and licensing checks and may periodically report health, route, and content availability to a central node, such as a device in or on the edge of the core network. Thus, the host 1400 can select and / or indicate different hosts for over-the-top services for the UE. The host application program 1414 may support various protocols, such as HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive HTTP Streaming over (MPEG-DASH), etc.

[0156] FIG. 15 is a block diagram illustrating a virtualization environment 1500 in which functionality implemented by some embodiments may be virtualized. In this context, virtualization means creating a virtual version of an apparatus or device, which may include a virtualized hardware platform, storage devices, and networking resources. As used herein, virtualization may apply to any device described herein, or components thereof, and refers to implementations in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functionality described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 1500 hosted by one or more hardware nodes, such as a network node, a UE, a core network node, or a hardware computing device acting as a host. Furthermore, in embodiments in which the virtualized node does not require wireless connectivity (e.g., a core network node or a host), the node may be fully virtualized.

[0157] An application 1502 (which may alternatively be referred to as a software instance, a virtual appliance, a network function, a virtual node, a virtual network function, etc.) executes within the virtualized environment Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0158] Hardware 1504 includes processing circuitry, memory that stores software and / or instructions executable by the hardware processing circuitry, and / or other hardware devices described herein, such as network interfaces, input / output interfaces, etc. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 1506 (also referred to as a hypervisor or virtual machine monitor (VMM)), provide VMs 1508a and 1508b (one or more of which may be generally referred to as VMs 1508), and / or implement any of the functions, features, and / or benefits described with respect to some embodiments described herein. Virtualization layer 1506 may present a virtual operating platform to VMs 1508 that appears to be networking hardware.

[0159] The VMs 1508 may comprise virtual processing, virtual memory, virtual networking or interfaces, and virtual storage and may be executed by a corresponding virtualization layer 1506. Different embodiments of instances of virtual appliances 1502 may be implemented on one or more of the VMs 1508, and the implementation may be done in different ways. Hardware virtualization is, in some contexts, referred to as network functions virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry-standard high-volume server hardware, physical switches, and physical storage that can be deployed in data centers and customer premises equipment.

[0160] In the context of NFV, a VM 1508 may be a software implementation of a physical machine that executes programs as if the programs were running on a non-virtualized physical machine. Each VM 1508, and the portion of hardware 1504 on which that VM runs, whether that hardware is dedicated to that VM and / or shared by that VM with other VMs, forms a separate virtual network element. Further, in the context of NFV, a virtual network function executes in one or more VMs 1508 on hardware 1504 and is responsible for handling specific network functions corresponding to application 1502.

[0161] The hardware 1504 may be implemented in a standalone network node having general-purpose or specific components. The hardware 1504 may implement some functionality through virtualization. Alternatively, the hardware 1504 may be part of a larger cluster of hardware (e.g., in a data center or CPE) where many hardware nodes work together and are managed through a management and orchestration 1510 that oversees, among other things, the lifecycle management of the application 1502. In some embodiments, the hardware 1504 is coupled to one or more radio units, each including one or more transmitters and one or more receivers that may be coupled to one or more antennas. The radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces or may be used in combination with virtual components to provide radio functionality to a virtual node, such as a radio access node or base station. In some embodiments, some signaling may be provided using a control system 1512, which may alternatively be used for communication between the hardware nodes and the radio units.

[0162] Figure 16 illustrates a communication diagram of a host 1602 communicating with a UE 1606 via a network node 1604 over a partial wireless connection, according to some embodiments. Exemplary implementations of the UE (such as the UE 1112a of Figure 11 and / or the UE 1200 of Figure 12), network node (such as the network node 1110a of Figure 11 and / or the network node 1300 of Figure 13), and host (such as the host 1116 of Figure 11 and / or the host 1400 of Figure 14) discussed in the previous paragraph, according to various embodiments, will now be described with reference to Figure 16.

[0163] Similar to the host 1400, an embodiment of the host 1602 includes hardware such as a communications interface, processing circuitry, and memory. The host 1602 also includes software stored within or accessible by the host 1602 and executable by the processing circuitry. The software includes a host application that may be operable to provide services to a remote user, such as a UE 1606, connecting via an over-the-top (OTT) connection 1650 extending between the UE 1606 and the host 1602. In providing services to the remote user, the host application may provide user data that is transmitted using the OTT connection 1650.

[0164] The network node 1604 includes hardware that enables it to communicate with the host 1602 and the UE 1606. The connection 1660 can be directly through or transit a core network (such as the core network 1106 of FIG. 11 ) and / or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, the intermediate network may be a backbone network or the Internet.

[0165] The UE 1606 includes hardware and software stored within or accessible by the UE 1606 and executable by the UE's processing circuitry. The software includes a client application, such as a web browser or operator-specific "app," that may be operable to provide services to a human or non-human user via the UE 1606 with the support of the host 1602. Host applications running on the host 1602 can communicate with running client applications via an OTT connection 1650 that terminates at the UE 1606 and the host 1602. In providing services to a user, the client application on the UE may receive request data from the host application on the host and provide user data in response to the request data. The OTT connection 1650 can transfer both request data and user data. The client application on the UE can interact with the user and generate user data to provide to the host application through the OTT connection 1650.

[0166] The OTT connection 1650 may extend via a connection 1660 between the host 1602 and the network node 1604 and via a wireless connection 1670 between the network node 1604 and the UE 1606 to provide a connection between the host 1602 and the UE 1606. The connections 1660 and wireless connections 1670 over which the OTT connection 1650 may be provided are depicted abstractly to illustrate communication between the host 1602 and the UE 1606 via the network node 1604, without explicit reference to any intermediate devices and the precise routing of messages through these devices.

[0167] As an example of transmitting data over the OTT connection 1650, in step 1608, the host 1602 provides user data, which may be done by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE 1606. In other embodiments, the user data is associated with a UE 1606 that shares data with the host 1602 without explicit human interaction. In step 1610, the host 1602 initiates a transmission carrying the user data toward the UE 1606. The host 1602 may initiate the transmission in response to a request transmitted by the UE 1606. The request may be triggered by human interaction with the UE 1606 or by the operation of a client application running on the UE 1606. The transmission may pass through the network node 1604 in accordance with the teachings of the embodiments described throughout this disclosure. Thus, in step 1612, the network node 1604 transmits the user data carried in the transmission initiated by the host 1602 to the UE 1606, in accordance with the teachings of embodiments described throughout this disclosure. In step 1614, the UE 1606 receives the user data carried in the transmission, which may be done by a client application running on the UE 1606 that is associated with a host application executed by the host 1602.

[0168] In some examples, the UE 1606 executes a client application that provides user data to the host 1602. The user data may be provided in reaction or response to data received from the host 1602. Thus, in step 1616, the UE 1606 can provide the user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from a user via an input / output interface of the UE 1606. Regardless of the particular manner in which the user data is provided, the UE 1606 initiates transmission of the user data to the host 1602 via the network node 1604 in step 1618. In step 1620, the network node 1604 receives the user data from the UE 1606 and initiates transmission of the received user data to the host 1602, in accordance with the teachings of embodiments described throughout this disclosure. In step 1622, the host 1602 receives the user data carried in the transmission initiated by the UE 1606.

[0169] One or more of the various embodiments improve performance of an OTT service provided to a UE 1606 using an OTT connection 1650 of which the wireless connection 1670 forms the final segment.

[0170] In an exemplary scenario, factory status information may be collected and analyzed by host 1602. As another example, host 1602 may process audio and video data that may have been retrieved from UEs for use in creating maps. As another example, host 1602 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, host 1602 may store surveillance video uploaded by UEs. As another example, host 1602 may store or control access to media content, such as video, audio, VR, or AR, that may be broadcast, multicast, or unicast to UEs. As another example, host 1602 may be used for energy pricing, remote control of non-time-critical electrical loads to balance power generation demands, location services, presentation services (e.g., compiling diagrams, etc. from data collected from remote devices), or any other function that collects, retrieves, stores, analyzes, and / or transmits data.

[0171] In some examples, measurement procedures may be provided for the purpose of monitoring data rates, latency, and other factors that one or more embodiments improve. There may also be optional network functionality for reconfiguring the OTT connection 1650 between the host 1602 and the UE 1606 in response to fluctuations in the measurement results. The measurement procedures and / or network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host 1602 and / or the UE 1606. In some embodiments, sensors (not shown) may be located in or associated with other devices through which the OTT connection 1650 passes, and the sensors may participate in the measurement procedures by providing values ​​of monitored quantities, as exemplified above, or other physical quantities from which software can calculate or estimate monitored quantities. Reconfiguration of the OTT connection 1650 may include message formats, retransmission settings, preferred routing, etc., and the reconfiguration need not directly change the operation of the network node 1604. Such procedures and functionality are known and may be implemented in the art. In particular embodiments, the measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation time, latency, etc. by the host 1602. The measurements may be implemented in that software causes messages, particularly empty or "dummy" messages, to be transmitted using the OTT connection 1650 while monitoring propagation time, errors, etc.

[0172] While the computing devices (e.g., UEs, network nodes, hosts) described herein may include the illustrated combination of hardware components, other embodiments may comprise computing devices having different combinations of components. It should be understood that these computing devices may comprise any suitable combination of hardware and / or software necessary to perform the tasks, features, functions, and methods disclosed herein. The determining, calculating, obtaining, or similar operations described herein may be performed by a processing circuit, which may process information by, for example, transforming the obtained information into other information, comparing the obtained or transformed information with information stored in the network node, and / or performing one or more operations based on the obtained or transformed information and making a decision as a result of such processing. Furthermore, while components are shown as a single box disposed within a larger box or nested within multiple boxes, in reality, a computing device may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned among the separate components. For example, a communication interface may be configured to include any of the configuration elements described herein, and / or the functionality of a configuration element may be divided between the processing circuit and the communication interface. In another example, the non-computationally intensive functions of any of such components may be implemented in software or firmware, and the computationally intensive functions may be implemented in hardware.

[0173] In particular embodiments, some or all of the functionality described herein may be provided by a processing circuit executing instructions stored on a memory, which in particular embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by a processing circuit without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hardwired manner. In any of these particular embodiments, the processing circuit may be configured to perform the described functionality, regardless of whether or not it executes instructions stored on a non-transitory computer-readable storage medium. Benefits provided by such functionality are not limited to just the processing circuit or to other components of the computing device, but are enjoyed by the computing device as a whole and / or by end users and wireless networks generally.

[0174] In particular, modifications and other embodiments of the disclosed invention(s) will come to mind to one skilled in the art having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. It is to be understood, therefore, that the invention(s) are not limited to the specific embodiments disclosed, and that modifications and other embodiments are intended to be included within the scope of the present disclosure. Although specific terms may be employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.

[0175] References 1.TR 38.875 V2.0.0,“Study on support of reduced capability NR devices”,V2.0.0 2.RP-2011574(RedCap WID) 3.TS 38.413 V16.5.0 4.TS 38.473 V16.5.0

Claims

1. A method performed by a distributed unit (14B) of a radio network node (14) in a radio access network (10) divided into a centralized unit (14A) and one or more distributed units, the method comprising: transmitting (210) information (20) from the distributed unit (14B) to the centralized unit (14A) indicating that the wireless communication device (12) is a reduced capabilities (RedCap) user equipment (UE); receiving (220) a paging message from the centralized unit (14A) requesting the distributed unit (14B) to page a wireless communication device (12), the paging message including information indicating that the wireless communication device (12) to be paged is a RedCap UE; paging (230) the wireless communication device (12) based on the information included in the paging message; A method comprising:

2. 2. The method of claim 1, wherein the information (20) is transmitted via an F1 interface between the distributed unit (14B) and the centralized unit (14A).

3. 2. The method of claim 1, wherein the information (20) is conveyed in a message sent by the distributed unit (14B) to forward an initial Layer 3 message to the centralized unit (14A).

4. 2. The method of claim 1, wherein the information (20) is transmitted in an INITIAL UL RRC MESSAGE TRANSFER message.

5. The method of claim 1 , wherein the RedCap UE has a maximum bandwidth of 20 MHz in the first frequency range FR1 and a maximum bandwidth of 100 MHz in the second frequency range FR2.

6. The method of claim 5 , wherein a RedCap UE lacks support for carrier aggregation and lacks support for dual connectivity.

7. The method of claim 5 , wherein the RedCap UE supports up to two receive branches and / or up to two downlink multiple-input multiple-output layers.

8. 2. The method of claim 1, wherein the information indicates that the wireless communication device is a New Radio (NR) RedCap UE.

9. 2. The method of claim 1, wherein the information (20) is included in a RedCap indication information element of a message transmitted from the distributed unit (14B) to the centralized unit (14A).

10. 2. The method of claim 1, further comprising receiving, in a random access procedure, an indication from the wireless communication device that the wireless communication device is a RedCap UE, wherein the information is transmitted to a central unit in response to receiving the indication from the wireless communication device.

11. A method performed by a central unit of a radio network node (14) in a radio access network (10) divided into a centralized unit (14A) and one or more distributed units, said method comprising: receiving information (300) from a distributed unit (14B) of the radio network node (14) that the wireless communication device (12) is a reduced capabilities (RedCap) user equipment (UE); transmitting (320) a paging message to the distributed unit (14B) requesting the distributed unit (14B) to page the wireless communication device (12), the paging message including information indicating that the wireless communication device (12) to be paged is a RedCap UE; A method comprising:

12. A distributed unit (14B) of a radio network node (14) in a radio access network (10) divided into a centralized unit (14A) and one or more distributed units, the distributed unit (14B) comprising: transmitting information (20) from the distributed unit (14B) to the centralized unit (14A) indicating that the wireless communication device (12) is a reduced capabilities (RedCap) user equipment (UE); receiving a paging message from the centralized unit (14A) requesting the distributed unit (14B) to page the wireless communication device (12), the paging message including information indicating that the wireless communication device (12) to be paged is a RedCap UE; A distributed unit (14B) configured to page the wireless communication device (12) based on the information included in the paging message.

13. A central unit of a radio network node (14) in a radio access network (10) divided into a centralized unit (14A) and one or more distributed units, said central unit comprising: receiving information (20) from a distributed unit (14B) of the radio network node (14) that the wireless communication device (12) is a reduced capabilities (RedCap) user equipment (UE); a central unit configured to transmit to the distributed unit a paging message requesting the distributed unit to page the wireless communication device, the paging message including information indicating that the wireless communication device to be paged is a RedCap UE;

14. 11. A computer program comprising instructions that, when executed by at least one processor of a distributed unit (14B) of a radio network node (14) that is divided into a centralized unit (14A) and one or more distributed units in a radio access network (10), cause the distributed unit (14B) to perform the method of any one of claims 1 to 10.

15. 12. A computer program comprising instructions, when executed by at least one processor of a central unit of a radio network node (14) that is divided into a centralized unit (14A) and one or more distributed units in a radio access network (10), causing the central unit to perform the method of claim 11.

Images