Split next generation-radio access network (NG-ran) with multiple active discontinuous reception (DRX) configurations

Abstract

According to certain embodiments, a method performed by a centralized unit (CU) of a network node comprises sending, to a distributed unit (DU) of the network node, an indication of multiple active discontinuous reception (DRX) configurations. The method comprises receiving, from the DU, one or more parameters configured for the multiple active DRX configurations.

Description

Split Next Generation-Radio Access Network (NG-RAN) with Multiple Active Discontinuous Reception (DRX) Configurations RELATED APPLICATIONS

[0001] This application claims priority to U.S. Provisional Patent Application No. 63 / 678,087, filed on August 1, 2024, the disclosure and content of which is incorporated by reference herein in its entirety. TECHNICAL FIELD

[0002] Certain embodiments of the present disclosure relate, in general, to a split Next Generation-Radio Access Network (NG‐RAN). BACKGROUND

[0003] The 3rd Generation Partnership Project (3GPP) unites telecommunications standard development organizations to produce Technical Reports (TRs) and Technical Specifications (TSs) that define 3GPP technologies. Examples of 3GPP specifications include radio access specifications, core network specifications, and service capabilities specifications for mobile telecommunications, such as cellular telecommunications. Certain 3GPP specifications provide a framework for a NG-RAN. The NG-RAN may be capable of supporting one or more radio access technologies, such as Long Term Evolution (LTE), New Radio (NR) (e.g., 5G), and beyond.

[0004] Figure 1 illustrates an example network architecture. As illustrated in Figure 1, the network architecture includes a 5G Core (5GC) 10 and an NG-RAN 20. The NG-RAN 20 includes one or more gNodeBs (gNBs) to perform operations of a base station, for example. As illustrated in Figure 1, the NG-RAN 20 includes a first gNB 22a and a second gNB 22b. The second gNB 22b in Figure 1 is arranged according to a split architecture. As an example, a split architecture may comprise a centralized unit (CU) and a plurality of distributed units (DU), such as a gNB-CU 24, a first gNB-DU 28a, and a second gNB-DU 28b shown in Figure 1. In general, the gNB-CU 24 may facilitate support for higher layers of the protocol stack, such as radio resource control (RRC) and the control plane part of the packet data convergence protocol (PDCP). The gNB-DUs 28 may facilitate support for lower layers of the protocol stack, such as radio link control (RLC), medium access control (MAC), and the physical layer.

[0005] The network architecture includes one or more NG interfaces (for 5GC-to-gNB communication), one or more Xn-C interfaces (for gNB-to-gNB communication), and one or more F1 interfaces (for gNB-CU-to-gNB-DU communication). In the example shown in Figure 1, the first gNB 22a communicates with the 5GC 10 via a first NG interface and the second gNB 22b communicates with the 5GC 10 via a second NG interface. The first gNB 22a and the second gNB 22b communicate with each other via an Xn-C interface. More particularly, the second gNB 22b’s split architecture uses its gNB-CU 24 to interface with the 5GC 10 (via the second NG interface) and to interface with the first gNB 22a (via the Xn-C interface). The gNB-CU 24 further interfaces with the first gNB-DU 28a via a first F1 interface and with the second gNB-DU 28b via a second F1 interface.

[0006] Figure 2 illustrates a more detailed example of a gNB 22 with a split architecture, such as the second gNB 22b described above with respect to Figure 1. In the example illustrated in Figure 2, the centralized unit of the gNB 22 (e.g., gNB-CU 24) comprises a control plane (CP) and one or more user planes (UPs), illustrated as gNB-CU-CP 25 and gNB-CU-UP 26, respectively. The gNB-CU-CP 25 interfaces with each gNB-CU-UP 26 via a respective E1 interface. The gNB-CU-CP 25 interfaces with each gNB-DU 28 via a respective F1-C interface. Each gNB-CU-UP 26 interfaces with each gNB-DU 28 via a respective F1-U interface.

[0007] DRX parameter signaling in NG-RAN

[0008] In the split NG-RAN architecture, the gNB-CU 24 controls the discontinuous reception (DRX) cycle length, while the gNB-DU 28 controls other DRX parameters. Thus, the gNB-CU 24 sends the DRX cycle length to the gNB-DU 28 via the F1 interface. 3GPP specifies messages for this purpose in 3GPP TS 38.473. See, e.g., TS 38.473 V18.2.0 (2024- 06); Technical Specification Group Radio Access Network; NG-RAN; F1 application protocol (F1AP); (Release 18). Examples of such messages in TS 38.473 include a “UE CONTEXT SETUP REQUEST” message and a “UE CONTEXT MODIFICATION REQUEST” message, specified in Sections 9.2.2.1 and 9.2.2.7, respectively. Each of these messages includes an information element (IE) for “DRX Cycle,” which the gNB-CU 24 uses to indicate the desired DRX cycle to the gNB-DU 28.

[0009] TS 38.473 specifies the DRX Cycle IE in Section 9.3.1.24 as follows: The DRX Cycle IE is to indicate the desired DRX cycle. IE / Group Name Presence Range IE Type and Semantics Reference Description Long DRX Cycle M ENUMERATED Corresponds to the Length (ms10, ms20, ms32, drx-LongCycle which ms40, ms60, ms64, is the length of theIE / Group Name Presence Range IE Type and Semantics Reference Description ms70, ms80, drx- ms128, ms160, LongCycleStartOffset ms256, ms320, contained in the DRX- ms512, ms640, Config IE defined in ms1024, ms1280, TS 38.331 [8]. ms2048, ms2560, ms5120, ms10240, ...) Short DRX Cycle O ENUMERATED Corresponds to the Length (ms2, ms3, ms4, drx-ShortCycle ms5, ms6, ms7, contained in the DRX- ms8, ms10, ms14, Config IE defined in ms16, ms20, ms30, TS 38.331 [8]. ms32, ms35, ms40, ms64, ms80, ms128, ms160, ms256, ms320, ms512, ms640, ...) Short DRX Cycle O INTEGER (1..16) Corresponds to the Timer drx-ShortCycleTimer contained in the DRX- Config IE defined in TS 38.331 [8].

[0010] On the other hand, the gNB-DU 28 signals other DRX parameters to the gNB-CU 24 via the same F1 interface. For example, other DRX parameters may be included in RRC IEs for DRX, such as DRX Long Cycle Start Offset and DRX Config. TS 38.473 specifies messages for this purpose, such as the “UE CONTEXT SETUP RESPONSE” message, the “UE CONTEXT MODIFICATION RESPONSE” message, and the “UE CONTEXT MODIFICATION REQUIRED” message, specified in Sections 9.2.2.2, 9.2.2.8, and 9.2.2.10, respectively. Each of these messages supports the “DU to CU RRC Information” IE specified in Section 9.3.1.26, which in turn supports the gNB-DU 28 sending to the gNB-CU 24 the DRX Long Cycle Start Offset and DRX Config IEs, for example. Further information about these IEs may be found in 3GPP TS 38.331. See, e.g., TS 38.331 V18.2.0 (2024-06); Technical Specification Group Radio Access Network; NR; Radio Resource Control (RRC) protocol specification; (Release 18).

[0011] XR multi-modality in 3GPP

[0012] 3GPP describes Extended Reality (XR) as encompassing real-and-virtual combined environments and human-machine interactions generated by computer technology and wearables. XR may be used as an umbrella term for different types of realities, such asVirtual Reality (VR), Augmented Reality (AR), and Mixed Reality (MR). VR aims at giving the user the feeling of being physically and spatially in a virtual environment. AR provides a user with additional content overlaid upon the user’s environment. MR is an advanced form of AR where some virtual elements are inserted and can be interacted with.

[0013] In an XR work item description (WID) for Release 19 (Rel-19), 3GPP includes the objectives discussed below. ********** Start excerpt from XR WID Rel-19 ********** The Rel-19 XR ph3 objectives are as follows: • Study and if justified, specify aspects related to multi-modality (intra-UE) (with coordination with SA2 / SA4 as needed by LS request). Aim to facilitate efficient and effective support for XR application with Multiple QoS flows with multi-modal inter- dependencies, meeting multi-modal QoS requirements, e.g. synchronization and / or coordination. Efficiency enhancements are expected to be visible in terms of capacity or power consumption. [RAN2]. o Note: Check in RAN#105 (check also other WG involvement if needed). • Specify enhancements to enable transmission / reception in gaps / restrictions that are caused by RRM measurements (from inter-frequency RRM measurement gaps, or intra-frequency measurements, or other scheduling restrictions, etc.). [RAN1, RAN2, RAN4] ^ Specify the corresponding measurement gap and scheduling restriction to enable the identified enhancements with RRM performance impact taken into consideration, work being triggered by LS. [RAN4] • Specify Enhancements for Scheduling, as follows: o For the UL, Study and if justified, Specify enhancements using delay / deadline information, for support of UL scheduling to enable high XR capacity while meeting delay requirements / avoiding too late PDUs. [RAN2]. ^ Note: LCP implementation complexity need to be taken into account when evaluating solutions. ^ Note: Check in RAN#105 • Specify the following user plane enhancements [RAN2] o RLC re-transmission related enhancements for operation of RLC Acknowledged Mode (AM) with small packet delay budget. o If justified, define a mechanism for transmitter to inform the receiver of SN gap (or missing SNs) in PDCP. ^ Specify Core requirements related to the above objectives as necessary [RAN4]Note: Whether / to what extent network exposure / RAN awareness / e.g. RAN involved rate control, possibly additional info for DL scheduling, parallel with SA2 work, shall be covered in this WI is TBD. ********** End excerpt from XR WID Rel-19 **********

[0014] Regarding the first objective, a “multi-modal” service refers to a communication service comprising several related data flows subject to application coordination. The data flows can transfer different types of data (e.g., audio, video, positioning, haptic, etc.), and the data flows may come from the same source or different sources (e.g., a single UE, a single device or multiple devices connected to the single UE, or multiple UEs, etc.). A multi-modal service may have synchronization requirements applicable across the different multi-modal data flows.

[0015] In Rel-19 XR, several companies have proposed the use of multiple active DRX configurations under the “multi-modality” objective. See, e.g., RP-240791, “Revised WID on XR (eXtended Reality) for NR Phase 3,” 3GPP TSG RAN Meeting #103, Maastricht, Netherlands, March 18-21, 2024; and R2-2404512, “Discussion on multi-modality,” Ericsson, 3GPP TSG-RAN WG2 Meeting #126, Fukuoka, Japan, 20th May – 26th May 2024. Certain proposals related to the multi-modality objective do not require coordination / synchronization across quality-of-service (QoS) flows.

[0016] R2-2404512 describes a problem in which an interleaved pattern of multiple (quasi-) periodic XR flows running in parallel creates irregular and short sleep opportunities. Current connected-mode DRX (C-DRX) solutions allow the network to configure only one DRX configuration per serving cell, which cannot match the traffic characteristics of all XR flows. Thus, the network cannot closely follow the short sleep opportunities, which results in either low power saving gains or long traffic delays. To address this problem, R2-2404512 proposes a solution to support multiple active DRX configurations. With this solution, the network provides multiple DRX configurations to a user equipment (UE), with the multiple DRX configurations running in parallel. By doing so, the network may use XR traffic information to configure DRX in a way that the DRX parameters in each configuration match each individual (quasi-) periodic traffic flow. Examples of XR traffic information that may be used to configure multiple DRX configurations may include traffic periodicity or jitter characteristics, which, for instance, may be provided by the application. The UE monitors the physical downlink control channel (PDCCH) while the drx-onDurationTimer (or drx- InactivityTimer, or Active Time) is running in any of the DRX configurations.

[0017] International Patent Publication No. WO 2023 / 031877 A1, “Methods for supporting multiple discontinuous reception (drx) configurations,” further describes a multiple active DRX solution. For example, the publication describes (1) how the network can configure the parameters for multiple active DRX at the UE side, and (2) how the UE behaves when it receives such a configuration from the network. SUMMARY

[0018] There currently exist certain challenge(s). For Rel-19 XR, 3GPP has discussed a multiple active DRX solution outlining how the network could configure multiple active DRX configurations at the UE and how the UE could behave when configured with multiple active DRX configurations. The multiple active DRX solution previously discussed by 3GPP does not sufficiently address the effect of the solution on the NG-RAN. The present disclosure recognizes that if 3GPP adopts the multiple active DRX solution in the standard, more signalling solutions are needed to transfer relevant parameters within the NG-RAN over the NG-RAN interfaces.

[0019] For example, the present disclosure recognizes the need for a solution to address the fact that currently the 3GPP specifications do not provide a way of configuring multiple active DRX configurations between the CU to the DU. As discussed above, the CU currently controls the DRX cycle length and sends the DRX cycle length to the DU in the “DRX Cyle” IE over F1 interface. The current “DRX Cycle” IE does not support multiple active DRX configurations. Similarly, the DU currently signals to the CU (via the F1 interface) the RRC IEs for DRX, such as the DRX Long Cycle Start Offset IE and the DRX Config IE. The current RRC IEs for DRX do not support multiple active DRX configurations either.

[0020] Further, 3GPP specified a solution for Network Energy Saving where the NG-RAN node (i.e., the gNB-DU in the case of the split architecture) determines the UE cell discontinuous transmission / discontinuous reception (DTX / DRX or DTRX) based on the UE DRX. The present disclosure recognizes the need for a solution that informs the gNB-DU when a list of UE DRX is introduced (in order for the gNB-DU to decide the best UE cell DTRX configuration(s)).

[0021] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. Certain embodiments allow for configuring multiple active DRX configurations between a CU and a DU in a split NG-RAN architecture. For example, certain embodiments provide solutions for updating the F1AP specifications so that messages sent via the F1 interface between the CU and the DU support multiple active DRX configurations. Asan example, certain embodiments update the “DRX Cycle” IE from the CU to the DU to support multiple DRX cycle lengths. As another example, certain embodiments update one or more RRC IEs for DRX (e.g., the DRX Long Cycle Start Offset IE and / or the DRX Config IE) to support sending one or more parameters for multiple active DRX configurations from the DU to the CU. The CU may be a gNB-CU (such as a gNB-CU-CP configured with an F1-C interface), and the DU may be a gNB-DU.

[0022] According to an embodiment, a method performed by a CU of a network node comprises sending, to a DU of the network node, an indication of multiple active DRX configurations. The method comprises receiving, from the DU, one or more parameters configured for the multiple active DRX configurations.

[0023] According to an embodiment, a method performed by a DU of a network node comprises receiving, from a CU of the network node, an indication of multiple active DRX configurations. The method comprises sending, to the CU, one or more parameters configured for the multiple active DRX configurations.

[0024] Certain embodiments may provide one or more of the following technical advantage(s). Supporting multiple active DRX configurations helps to limit the delay and optimize power saving of UEs with multi-flow XR services. Without signaling support over F1, this benefit cannot be supported in split NG-RAN architecture. The teachings of certain embodiments may improve the battery life of UEs, for example, by facilitating network support of multiple active DRX configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] For a more complete understanding of the disclosed embodiments and their features and advantages, reference is now made to the drawings, in which:

[0026] Figure 1 illustrates an example of a network architecture comprising an NG-RAN, in accordance with some embodiments.

[0027] Figure 2 illustrates an example of a gNB in a split NG-RAN, in accordance with some embodiments.

[0028] Figure 3 illustrates an example of a signal flow diagram, in accordance with some embodiments.

[0029] Figure 4a illustrates an example of a UE Context Setup Request procedure, in accordance with some embodiments.

[0030] Figure 4b illustrates an example of a UE Context Modification procedure, in accordance with some embodiments.

[0031] Figure 5 illustrates an example of a method performed by a CU, in accordance with certain embodiments.

[0032] Figure 6 illustrates an example of a method performed by a DU, in accordance with certain embodiments.

[0033] Figure 7 illustrates an example of a communication system in accordance with some embodiments.

[0034] Figure 8 illustrates an example of a user equipment (UE) in accordance with some embodiments.

[0035] Figure 9 illustrates an example of a network node in accordance with some embodiments.

[0036] Figure 10 illustrates an example of a virtualization environment in accordance with some embodiments. DETAILED DESCRIPTION

[0037] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0038] Figure 3 illustrates an example of a signal flow diagram between a CU and a DU, such as the gNB-CU 24 and the gNB-DU 28 described above with respect to Figure 1. The gNB-CU 24 may comprise the gNB-CU-CP 25 and the gNB-CU-UP 26 described above with respect to Figure 2. The CU and the DU may provide a split NG-RAN.

[0039] In step 32, the DU indicates to the CU whether the DU supports multiple active DRX configurations. In step 34, the CU indicates to the DU multiple active DRX configurations. In step 36, the DU indicates to the CU one or more parameters for the multiple active DRX configurations. In step 38, the CU performs an operation of the CU based on the multiple active DRX configurations. In step 40, the DU performs an operation of the DU based on the multiple active DRX configurations. Modifications, additions, or omissions may be made to the signal flow without departing from the scope of the disclosure. The signal flow may include more, fewer, or other steps. For example, in certain embodiments, any one or more of steps 32, 38, and / or 40 may be optional / omitted. Additionally, steps may be performed in any suitable order. As an example, the operation of the DU performed in step 40 may be performed before, after, or in parallel to the operation of the CU performed in step 38.

[0040] In a first embodiment, a DU indicates to a CU whether the DU supports multiple active DRX configurations (see, e.g., Figure 3 at step 32). For example, the DU indicateswhether it supports multiple active DRX configurations in signaling. The signaling may be communicated via the F1 interface. The signaling may comprise any suitable message, information element, field, parameter, etc. to indicate whether the DU supports multiple active configurations. As an example, the indication may be provided in network capability information to the CU (where the network capability information may be newly specified by 3GPP, e.g., to introduce the solutions proposed herein).

[0041] In a second embodiment, a CU receives from a DU an indication whether the DU supports multiple active DRX configurations (see, e.g., Figure 3 at step 32). The second embodiment may be reciprocal to the first embodiment (e.g., where the CU in the second embodiment receives the indication sent by the DU in the first embodiment). The CU determines whether to configure multiple active DRX configurations based at least in part on the indication received from the DU. As a first example, the CU configures multiple active DRX configurations based at least in part on the indication indicating that the DU supports multiple active DRX configurations. Optionally, the CU may further base the determination to configure multiple active DRX configurations on one or more other criteria (such whether there is a need for multiple active DRX configurations, e.g., to support a multi-modal service). As a second example, the CU abstains from configuring multiple active DRX configurations based on the indication indicating that the DU does not support multiple active DRX configurations. In certain embodiments, the CU takes the indication into account before it configures a potential DRX list. If the DU does not support handling multiple active DRX configurations, the CU sends the DU only one active DRX configuration. When sending only one active DRX configuration, the CU may use an information element specified by a legacy specification (such as a version of a specification that pre-dates introduction of any of the solutions proposed herein).

[0042] In a third embodiment, the CU indicates multiple active DRX configurations to the DU (see, e.g., Figure 3 at step 34). The CU indicates the multiple active DRX configurations in signaling. The signaling may be communicated via the F1 interface. The signaling may comprise any suitable message, information element, field, parameter, etc. to indicate the multiple DRX cycle lengths. In certain embodiments, the CU indicates the multiple active DRX configurations in a list to the DU. Optionally, the third embodiment may be implemented such that the CU signals more than one list, such as two separate lists. As an example, the CU signals a first list for active (integer) DRX cycles, and the CU signals a second list for active non- integer cycles (e.g., for a case in which some of the DRX cycles of the multiple active DRX configurations take non-integer values). Optionally, the third embodiment may be combinedwith the second embodiment such that indicating the multiple active DRX configurations occurs after the CU receives an indication from the DU indicating that the DU supports multiple active DRX configurations. Optionally, in certain embodiments, the CU may indicate the multiple active DRX configurations to the DU by providing the DU with multiple DRX cycle lengths. For example, the CU may indicate one DRX cycle length for each of multiple active DRX configurations. One or more lists may be used for this purpose.

[0043] In a fourth embodiment, the DU receives from the CU an indication of multiple active DRX configurations (see, e.g., Figure 3 at step 34). The fourth embodiment may be reciprocal to the third embodiment (e.g., where the DU in the fourth embodiment receives the indication sent by the CU in the third embodiment). The DU may use the indication of the multiple active DRX configurations received from the CU to setup the final DRX configuration(s) (e.g., by configuring parameters that the DU controls for DRX). Optionally, the fourth embodiment may be combined with the first embodiment (where prior to receiving the multiple DRX cycle lengths from the CU, the DU indicates to the CU that the DU supports multiple active DRX configurations).

[0044] In a fifth embodiment, the DU indicates to the CU one or more parameters for the multiple active DRX configurations (e.g., parameters that the DU controls for DRX) (see, e.g., Figure 3 at step 36). The DU indicates the one or more parameters in signaling. The signaling may be communicated via the F1 interface. The signaling may comprise any suitable message, information element, field, parameter, etc. to indicate the one or more parameters. In certain embodiments, the signaling comprises one or more RRC DRX IEs that include the one or more parameters for the multiple active DRX configurations. Such an embodiment may be based on updating the legacy 3GPP specifications to add support for multiple active DRX configurations to the one or more RRC DRX IEs (e.g., DRX Long Cycle Start Offset IE and / or the DRX Config IE). Optionally, the fifth embodiment may be combined with the first embodiment (e.g., where the DU indicates to the CU that the DU supports multiple active DRX configurations) and / or the fourth embodiment (e.g., where the DU receives from the CU multiple DRX cycle lengths or other indication of multiple active DRX configurations).

[0045] In a sixth embodiment, the CU receives from the DU the one or more parameters for the multiple active DRX configurations (see, e.g., Figure 3 at step 36). The sixth embodiment may be reciprocal to the fifth embodiment (e.g., where the CU in the sixth embodiment receives the indication sent by the DU in the fifth embodiment). Optionally, the sixth embodiment may be combined with the second embodiment (e.g., where the CU receives from the DU the indication that the DU supports multiple active DRX configurations) and / orthe third embodiment (e.g., where the CU indicates to the DU the multiple DRX cycle lengths or other indication of multiple active DRX configurations).

[0046] In a seventh embodiment, in any of the preceding embodiments (first through sixth embodiments), either the CU or the DU (or both) may use the multiple active DRX configurations to perform an operation of the CU or the DU (see, e.g., Figure 3 at step 38 and / or step 40). As an example, the multiple active DRX configurations may be based on the DRX cycle lengths sent by the CU and received by the DU (see, e.g., Figure 3 at step 34) together with the one or more parameters for the multiple active DRX configurations sent by the DU and received by the CU (see, e.g., Figure 3 at step 36). An example use of the multiple active DRX configurations includes using the multiple active DRX configurations to determine when a UE is expected to be in a reception mode (e.g., wake mode) or in a non-reception mode (e.g., sleep mode). This may facilitate operations of the CU or the DU, such as scheduling communication with the UE or sending information to the UE when the UE is expected to be in the reception mode. As an example, the information sent to the UE may relate to paging (e.g., sending a wake up signal or a paging indication to the UE). As another example, the information sent to the UE may relate to scheduling (e.g., sending control information, such as a PDCCH, in order to schedule radio resources, such as radio resources for data traffic).

[0047] Certain embodiments of the present disclosure propose solutions that provide a new list of active DRX Cycles and active non-integer DRX Cycles over F1AP from gNB-CU to gNB-DU.

[0048] Certain embodiments of the present disclosure propose solutions that provide a list of Cell DTRX configuration, per gNB-DU or per UE, from gNB-DU to gNB-CU.

[0049] In one embodiment, the CU receives an indication from the DU if the DU supports multiple active DRX configurations. Based on this indication, the CU decides whether to send a list of multiple DRX configurations to DU.

[0050] In one embodiment, the DU receives a list of DRX configurations from CU. In a first sub-embodiment, the list received by the DU from the CU comprises a list of multiple DRX configurations, where each active configuration includes DRX cycle length information. In one example, the DRX cycle length information comprises the Long DRX Cycle Length. In another example, the DRX cycle length information includes the Short DRX Cycle Length. In another example, the DRX cycle length information includes the Long DRX Cycle Length and, optionally, the Short DRX Cycle Length and the associated timer value (Short DRX Cycle Timer). In a second sub-embodiment, the list received by DU from CU comprises a list of multiple active non-integer DRX configurations, where each active non-integer DRXconfiguration includes Long Non-Integer DRX Cycle Length and, optionally, Short Non- Integer DRX Cycle Length and the timer value for the Short DRX Cycle Timer.

[0051] In one embodiment, the CU decides the list of parameter values to be sent to the DU, if active DRX configuration or active non-integer DRX configuration or both, based on the information received from the core network (CN) (e.g., based on Time Sensitive Communication Assistance Information (TSCAI)), or from the UE via (e.g., via UE Assistance Information (UAI)), or based on learning algorithms from UE traffic profiles and previous QoS metrics.

[0052] In one embodiment, the CU receives a set of multiple preferred DRX cycle parameter values from the UE, e.g., via the UAI in RRC. The parameter values can be integer, or non-integer, or both.

[0053] In one embodiment, the gNB-DU, upon receiving the list of UE DRX configuration, determines one or a list of the UE Cell DTRX configuration and sends it to the gNB-CU. The gNB-CU uses the configurations, e.g., to coordinate the Network Energy Saving. Such Cell DTRX configuration list can be sent per gNB-DU entity or per UE.

[0054] In one embodiment, the CU receives from the DU a signaling message indicating the RRC DRX IEs containing the DRX configurations parameters for multiple active DRX.

[0055] The following paragraphs provide non-limiting examples of changes that can be made to the existing 3GPP specifications to implement certain examples of the solutions proposed herein. For brevity, certain portions of the existing 3GPP specifications have been omitted from the examples, as indicated by “[…]”. This means that the example does not propose a change to the omitted portion. Other embodiments may make more, fewer, and / or different changes to the specifications. ********** Start Example Changes to TS 38.473 v18.2.0 ********** 8.3 UE Context Management procedures 8.3.1 UE Context Setup 8.3.1.1 General The purpose of the UE Context Setup procedure is to establish the UE Context including, among others, SRB, DRB, BH RLC channel, Uu Relay RLC channel, PC5 Relay RLC channel, and SL DRB configuration. The procedure uses UE-associated signalling. 8.3.1.2 Successful Operation [See Figure 4a of the present disclosure] Figure 8.3.1.2-1: UE Context Setup Request procedure: Successful OperationThe gNB-CU initiates the procedure by sending UE CONTEXT SETUP REQUEST message to the gNB-DU. If the gNB-DU succeeds to establish the UE context, it replies to the gNB- CU with UE CONTEXT SETUP RESPONSE. If no UE-associated logical F1-connection exists, the UE-associated logical F1-connection shall be established as part of the procedure. Except for RACH based SDT and UE configured with BWP specific ServingCellMO, the gNB-CU shall perform RRC Reconfiguration or RRC connection resume to send UE to the RRC_CONNECTED state as described in TS 38.331 [8], and in this case, the CellGroupConfig IE shall transparently be signaled to the UE as specified in TS 38.331 [8]. In the cases of RACH based SDT procedure and UE configured with BWP specific ServingCellMO, the CellGroupConfig IE shall be ignored by the gNB-CU. If the UE-CapabilityRAT-ContainerList IE is included in the UE CONTEXT SETUP REQUEST, the gNB-DU shall take this information into account for UE specific configurations. If the servingCellMO IE is included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall configure servingCellMO for the indicated SpCell accordingly. If the servingCellMO List IE is included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, select servingCellMO after determining the list of BWPs for the UE and include the list of servingCellMOs that have been encoded in CellGroupConfig IE as ServingCellMO-encoded-in-CGC List IE in the UE CONTEXT SETUP RESPONSE message. If the Configured BWP List IE is included in the UE CONTEXT SETUP RESPONSE message, the gNB-CU shall, if supported, take it into account when requesting the gNB-DU for generating preconfigured measurement GAP for the indicated BWPs. If the SpCell UL Configured IE is included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall configure UL for the indicated SpCell accordingly. If the SCell To Be Setup List IE is included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall consider it as a list of candidate SCells to be set up. If the SCell UL Configured IE is included in the UE CONTEXT SETUP REQUEST message, the gNB- DU shall configure UL for the indicated SCell accordingly. If the servingCellMO IE is included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall configure servingCellMO for the indicated SCell accordingly. If the DRX Cycle IE is contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall use the provided value from the gNB-CU. If the Non-Integer DRX Cycle IE is contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, use the provided value from the gNB-CU. [BEGIN CHANGE] If the List of Active DRX Cycles IE is contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall use the provided values from the gNB-CU. If the List of Active Non-Integer DRX Cycle IE is contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, use the provided values from the gNB-CU. [END CHANGE][…] =============NEXT CHANGE============8.3.4 UE Context Modification (gNB-CU initiated) 8.3.4.1 General The purpose of the UE Context Modification procedure is to modify the established UE Context, e.g., establishing, modifying and releasing radio resources or sidelink resources. This procedure is also used to command the gNB-DU to stop data transmission for the UE for mobility (see TS 38.401 [4]). The procedure uses UE-associated signalling. 8.3.4.2 Successful Operation [See Figure 4b of the present disclosure] Figure 8.3.4.2-1: UE Context Modification procedure. Successful operation The UE CONTEXT MODIFICATION REQUEST message is initiated by the gNB-CU. Upon reception of the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall perform the modifications, and if successful reports the update in the UE CONTEXT MODIFICATION RESPONSE message. If the SpCell ID IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall replace any previously received value and regard it as a reconfiguration with sync as defined in TS 38.331 [8]. If the ServCellIndex IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall take this into account for the indicated SpCell. If the SpCell UL Configured IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall configure UL for the indicated SpCell accordingly. If the servingCellMO IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall configure servingCellMO for the indicated SpCell accordingly. If the servingCellMO List IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, configure servingCellMO after determining the list of BWPs for the UE and include the list of servingCellMOs that have been encoded in CellGroupConfig IE as ServingCellMO-encoded- in-CGC List IE in the UE CONTEXT MODIFICATION RESPONSE message. If the Configured BWP List IE is included in the UE CONTEXT MODIFICATION RESPONSE message the gNB-CU shall, if supported, take it into account when requesting the gNB-DU for generating preconfigured measurement GAP for the indicated BWPs. If the Preconfigured Measurement GAP Request IE is present in the CU to DU RRC Information IE in the UE CONTEXT MODIFICATON REQUEST message, the gNB-DU shall, if supported, consider that the content of the previous CellGroupConfig IE was not sent to the UE and generate the pre-configured measurement GAP for the indicated BWPs in the MeasConfig IE. If the gNB-DU successfully generates pre-configured measurement GAP for the indicated BWPs, the gNB-DU shall update the CellGroupConfig IE with the content of the previous CellGroupConfig IE and the preconfigured measurement GAP configuration in the UE CONTEXT MODIFICATION RESPONSE message.If the SCell To Be Setup List IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall consider it as a list of candidate SCells to be set up. If the SCell To Be Setup List IE is included in the UE CONTEXT MODIFICATION REQUEST message and the indicated SCell(s) are already setup, the gNB-DU shall replace any previously received value. If the SCell UL Configured IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall configure UL for the indicated SCell accordingly. If the servingCellMO IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall configure servingCellMO for the indicated SCell accordingly. If the SCell To Be Removed List IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall consider it as a list of SCells to be removed. If the DRX Cycle IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall use the provided value from the gNB-CU. If the DRX configuration indicator IE is contained in the UE CONTEXT MODIFICATION REQUEST message and set to "release", the gNB-DU shall release DRX configuration. If the Non-Integer DRX Cycle IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, use the provided value from the gNB- CU. [BEGIN CHANGE] If the List of Active DRX Cycle IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall use the provided value from the gNB-CU. If the DRX configuration indicator IE is contained in the UE CONTEXT MODIFICATION REQUEST message and set to "release", the gNB-DU shall release DRX configuration. If the List of Active Non-Integer DRX Cycle IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, use the provided value from the gNB-CU. [END CHANGE] […] =============NEXT CHANGE============ 9.2.2.1 UE CONTEXT SETUP REQUEST This message is sent by the gNB-CU to request the setup of a UE context. Direction: gNB-CU ^ gNB-DU. IE / Group Presence Range IE type and Semantics Criticality Assigned Name reference description Criticality Message M 9.3.1.1 YES reject Type gNB-CU M 9.3.1.4 YES reject UE F1AP IDIE / Group Presence Range IE type and Semantics Criticality Assigned Name reference description Criticality gNB-DU O 9.3.1.5 YES ignore UE F1AP ID SpCell ID M NR CGI Special Cell as YES reject 9.3.1.12 defined in TS 38.321

[0016] . For handover case, this IE is considered as target cell. ServCellIn M INTEGER YES reject dex (0..31,...) […] [BEGIN CHANGE] List of YES ignore Active DRX Cycle >List of 1.. EACH ignore Active <maxn DRX oofDR Cycle Xcycle Item s> >>DRX M 9.3.1.24 - Cycle List of YES ignore Active non- Integer DRX Cycle >List of 1.. EACH ignore Active <maxn non- oofDRIE / Group Presence Range IE type and Semantics Criticality Assigned Name reference description Criticality integer Xcycle DRX s> Cycle Item >>DRX M 9.3.1.344 - Cycle [END CHANGE] […] =============NEXT CHANGE============ 9.2.2.7 UE CONTEXT MODIFICATION REQUEST This message is sent by the gNB-CU to provide UE Context information changes to the gNB- DU. Direction: gNB-CU ^ gNB-DU IE / Group Presence Range IE type and Semantics Criticality Assigned Name reference description Criticality Message M 9.3.1.1 YES reject Type gNB-CU M 9.3.1.4 YES reject UE F1AP ID gNB-DU M 9.3.1.5 YES reject UE F1AP ID SpCell ID O NR CGI Special Cell YES ignore 9.3.1.12 as defined in TS 38.321

[0016] . For handover case, this IE is considered as target cell. ServCellIn O INTEGER YES reject dex (0..31, ...) […]IE / Group Presence Range IE type and Semantics Criticality Assigned Name reference description Criticality [BEGIN CHANGE] List of YES ignore Active DRX Cycle >List of 1.. EACH ignore Active <maxno DRX ofDRXc Cycle ycles> Item >>DRX M 9.3.1.24 - Cycle List of YES ignore Active non- Integer DRX Cycle >List of 1.. EACH ignore Active <maxno non- ofDRXc integer ycles> DRX Cycle Item >>DRX M 9.3.1.344 - Cycle [END CHANGE] ********** End Example Changes to TS 38.473 v18.2.0 ********** ********** Start Example Changes to TS 38.331 v18.2.0 ********** UEAssistanceInformation message -- ASN1START -- TAG-UEASSISTANCEINFORMATION-START UEAssistanceInformation-v1610-IEs ::= SEQUENCE { idc-Assistance-r16 IDC-Assistance-r16 OPTIONAL,drx-Preference-r16 DRX-Preference-r16 OPTIONAL, maxBW-Preference-r16 MaxBW-Preference-r16 OPTIONAL, maxCC-Preference-r16 MaxCC-Preference-r16 OPTIONAL, maxMIMO-LayerPreference-r16 MaxMIMO- LayerPreference-r16 OPTIONAL, minSchedulingOffsetPreference-r16 MinSchedulingOffsetPreference-r16 OPTIONAL, releasePreference-r16 ReleasePreference-r16 OPTIONAL, sl-UE-AssistanceInformationNR-r16 SL-UE- AssistanceInformationNR-r16 OPTIONAL, referenceTimeInfoPreference-r16 BOOLEAN OPTIONAL, nonCriticalExtension UEAssistanceInformation-v1700-IEs OPTIONAL } […] ==== SKIPPED UNCHANGED LINES ========== [BEGIN CHANGE] UEAssistanceInformation-vXXXX-IEs ::= SEQUENCE { drx-PreferenceMultipleDRX-rXX SEQUENCE (SIZE (1..maxNrofActiveDRX)) OF DRX-Preference-rXX OPTIONAL } [END CHANGE] […] ==== SKIPPED UNCHANGED LINES ========== DRX-Preference-r16 ::= SEQUENCE { preferredDRX-InactivityTimer-r16 ENUMERATED { ms0, ms1, ms2, ms3, ms4, ms5, ms6, ms8, ms10, ms20, ms30, ms40, ms50, ms60, ms80, ms100, ms200, ms300, ms500, ms750, ms1280, ms1920, ms2560, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1} OPTIONAL, preferredDRX-LongCycle-r16 ENUMERATED { ms10, ms20, ms32, ms40, ms60, ms64, ms70, ms80, ms128, ms160, ms256, ms320, ms512, ms640, ms1024, ms1280, ms2048, ms2560, ms5120, ms10240, spare12, spare11, spare10, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1 } OPTIONAL,preferredDRX-ShortCycle-r16 ENUMERATED { ms2, ms3, ms4, ms5, ms6, ms7, ms8, ms10, ms14, ms16, ms20, ms30, ms32, ms35, ms40, ms64, ms80, ms128, ms160, ms256, ms320, ms512, ms640, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1 } OPTIONAL, preferredDRX-ShortCycleTimer-r16 INTEGER (1..16) OPTIONAL } […] ==== SKIPPED UNCHANGED LINES ========== [BEGIN CHANGE] DRX-Preference-rXX ::= SEQUENCE { preferredDRX-InactivityTimer-rXX ENUMERATED { ms0, ms1, ms2, ms3, ms4, ms5, ms6, ms8, ms10, ms20, ms30, ms40, ms50, ms60, ms80, ms100, ms200, ms300, ms500, ms750, ms1280, ms1920, ms2560, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1} OPTIONAL, preferredDRX-NonIntegerLongCycle-rXX ENUMERATED { ms1001over240, ms25over6, ms25over3, ms1001over120, ms100over9, ms25over2, ms40over3, ms125over9, ms50over3, ms1001over60, ms125over6, ms200over9, ms250over9, ms100over3, ms1001over30, ms75over2, ms125over3, ms1001over24, ms200over3, ms1001over15, ms250over3, ms1001over12, ms400over3, spare12, spare11, spare10, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1 } OPTIONAL, preferredDRX-NonIntegerShortCycle-rXX ENUMERATED { ms1001over240, ms25over6, ms25over3, ms1001over120, ms100over9, ms25over2, ms40over3, ms125over9, ms50over3, ms1001over60, ms125over6, ms200over9, ms100over3, ms1001over30, ms125over3, ms1001over24, ms200over3, spare15, spare14, spare13, spare12, spare11, spare10, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1 } OPTIONAL, preferredDRX-ShortCycleTimer-rXX INTEGER (1..16) OPTIONAL }[END CHANGE] […] ==== SKIPPED UNCHANGED LINES ========== ********** End Example Changes to TS 38.331 v18.2.0 **********

[0056] Figure 5 illustrates an example of a method 500 performed by a CU of a network node, in accordance with some embodiments. As an example, method 500 may be performed by gNB-CU 24 of gNB 22b shown in Figure 1 or by gNB-CU-CP 25 and / or gNB-CU-UP 26 of gNB 22 shown in Figure 2. In certain embodiments, the CU may comprise processing circuitry configured to perform some or all of the steps of method 500, such as processing circuitry 302 of network node 300 described below with respect to Figure 9.

[0057] In certain embodiments, method 500 begins at step 502 with receiving from a DU of the network node, an indication whether the DU supports a multiple active DRX configurations capability. Method 500 proceeds to step 504 with determining, by the CU, whether to configure multiple active DRX configurations. In the example of Figure 5, the determining is based at least in part on the indication received in step 502, which indicates whether the DU supports the multiple active DRX configurations capability. If the indication in step 502 indicates that the DU does not support the multiple active DRX configurations capability, method 500 proceeds via the “no” branch of step 504 to step 506. In step 506, method 500 abstains from sending the DU an indication of multiple active DRX configurations. For example, instead, method 500 may proceed from step 506 to step 508 with sending the DU an indication of a single active DRX configuration. Optionally, method 500 may further include steps to complete the setup / configuring of the single active DRX configuration (e.g., according to legacy behavior). Embodiments of method 500 that proceed along the “no” branch from step 504 then end.

[0058] If, on the other hand, the indication in step 502 indicates that the DU supports the multiple active DRX configurations capability, method 500 may determine in step 504 to configure multiple active DRX configurations. Optionally, the determination to configure multiple active DRX configurations may further be based on one or more other factors, such as whether there is a need for multiple active DRX configurations (e.g., to support a multi- modal service). In response to determining in step 504 to configure multiple active DRX configurations, method 500 proceeds via the “yes” branch of step 504 to step 510 withdetermining, by the CU, multiple DRX cycle lengths for the multiple active DRX configurations.

[0059] Method 500 may continue with step 512, where the CU sends to the DU an indication of the multiple active DRX configurations. The indication in step 512 comprises the multiple DRX cycle lengths determined in step 510. That is, in certain embodiments, the CU may send to the DU the multiple DRX cycle lengths to indicate to the DU to configure multiple active DRX configurations. In one example, 3GPP TS 38.473 may be modified to support sending multiple DRX cycle lengths to the DU. For example, the UE CONTEXT SETUP REQUEST message and / or the UE CONTEXT MODIFICATION REQUEST message may be modified to support multiple DRX cycle lengths. Examples of new information elements that may be included in one or both of these messages are discussed in the example changes section above. The examples include a List of Active DRX Cycle IE with corresponding List of Active DRX Cycle Item and DRX Cycle IEs. Optionally, if using a second list for non-integer values, the information elements may further include a List of Active non-Integer DRX Cycle IE with corresponding List of Active non-integer DRX Cycle Item and DRX Cycle IEs. Other embodiments may use other messages and / or other IEs to send the multiple DRX cycle lengths from the CU to the DU.

[0060] At step 514, method 500 receives, from the DU, one or more parameters configured for the multiple active DRX configurations. Method 500 may then configure the CU to use the multiple active DRX configurations, as shown in step 516. Configuring the CU to use the multiple active DRX configurations may comprise the CU applying (a) the one or more parameters configured for the multiple active DRX configurations and received from the DU in step 514, and (b) the multiple DRX cycle lengths determined by the CU in step 510.

[0061] Method 500 proceeds to step 518 with performing an operation of the CU using the multiple active DRX configurations. An example use of the multiple active DRX configurations includes using the multiple active DRX configurations to determine when a UE is expected to be in a reception mode (e.g., wake mode) or in a non-reception mode (e.g., sleep mode). Certain embodiments of step 518 comprise using the multiple active DRX configurations to facilitate scheduling communication with the UE based on when the UE is expected to be in the reception mode and / or to facilitate sending information to the UE when the UE is expected to be in the reception mode. As an example, the information sent to the UE may relate to paging (e.g., sending a wake up signal or a paging indication to the UE). As another example, the information sent to the UE may relate to scheduling (e.g., sending control information, such as a PDCCH, in order to schedule radio resources, such as radio resourcesfor data traffic). Embodiments of method 500 that proceed along the “yes” branch from step 504 then end.

[0062] Figure 6 illustrates an example of a method 600 performed by a DU of a network node, in accordance with some embodiments. As an example, method 600 may be performed by a gNB-DU 28 of gNB 22b shown in Figure 1 or by a gNB-DU 28 of gNB 22 shown in Figure 2. In certain embodiments, the DU may comprise processing circuitry configured to perform some or all of the steps of method 600, such as processing circuitry 302 of network node 300 described below with respect to Figure 9. In some embodiments, at least certain steps of method 600 may be reciprocal to certain steps of method 500 such that information described as being sent from the CU to the DU in method 500 may be received by the DU from the CU in method 600, and information described as being received by the CU from the DU in method 500 may be sent by the DU to the CU in method 600.

[0063] In certain embodiments, method 600 begins at step 602 with sending an indication to a CU of the network node. The indication indicates whether the DU supports a multiple active DRX configurations capability. The subsequent steps of method 600 illustrate the case when the DU does support the multiple active DRX configurations.

[0064] At step 604, method 600 receives, from the CU, an indication of the multiple active DRX configurations. As an example, the DU receives from the CU multiple DRX cycle lengths as the indication of the multiple active DRX configurations. See, e.g., the above description of step 512 in Figure 5 for examples of messages / IEs that may be used for this purpose. Returning to the description of method 600. In response to receiving the indication in step 604, method 600 proceeds to step 606. In step 606, method 600 determines values for one or more parameters configured for the multiple active DRX configurations. Method 600 then proceeds to step 608 with sending, to the CU, the one or more parameters configured for the multiple active DRX configurations (as determined by the DU ins step 606). In step 610, method 600 configures the DU to use the multiple active DRX configurations. Configuring the DU to use the multiple active DRX configurations may comprise the DU applying (a) the one or more parameters configured for the multiple active DRX configurations as determined by the DU in step 606 and sent from the DU to the CU in step 608, and (b) the multiple DRX cycle lengths received from the CU (e.g., the multiple DRX cycle lengths received as the indication from the CU in step 604).

[0065] Method 600 ends with performing an operation of the DU using the multiple active DRX configurations, as shown in step 612. An example use of the multiple active DRX configurations includes using the multiple active DRX configurations to determine when a UEis expected to be in a reception mode (e.g., wake mode) or in a non-reception mode (e.g., sleep mode). Certain embodiments of step 612 comprise using the multiple active DRX configurations to facilitate scheduling communication with the UE based on when the UE is expected to be in the reception mode and / or to facilitate sending information to the UE when the UE is expected to be in the reception mode. As an example, the information sent to the UE may relate to paging (e.g., sending a wake up signal or a paging indication to the UE). As another example, the information sent to the UE may relate to scheduling (e.g., sending control information, such as a PDCCH, in order to schedule radio resources, such as radio resources for data traffic).

[0066] Further examples of configuring multiple active DRX configurations are provided in the following enumerated embodiments:

[0067] In an embodiment 1, a method for configuring multiple active DRX configurations is performed by a CU of a network node. The method comprises sending, to a DU of the network node, an indication of the multiple active DRX configurations. The method comprises receiving, from the DU, one or more parameters configured for the multiple active DRX configurations. For examples, see Figure 3 (steps 34 and 36) and Figure 5 (steps 512 and 514).

[0068] In an embodiment 2, the sending and / or receiving of embodiment 1 via signaling over an F1 interface that communicatively couples the CU and the DU. As an example, the indication of multiple active DRX configurations is sent in a UE CONTEXT SETUP REQUEST message or a UE CONTEXT MODIFICATION REQUEST message via an F1 interface that communicatively couples the CU and the DU. As another example, the one or more parameters configured for the multiple active DRX configurations is received in a UE CONTEXT SETUP RESPONSE message or a UE CONTEXT MODIFICATION RESPONSE message via an F1 interface that communicatively couples the CU and the DU. See, e.g., above discussion of example changes to TS 38.473.

[0069] In an embodiment 3, the method of any of embodiments 1-2, wherein the indication of the multiple active DRX configurations comprises multiple DRX cycle lengths. Each DRX cycle length of the multiple DRX cycle lengths is associated with a respective active DRX configuration of the multiple active DRX configurations.

[0070] In an embodiment 4, the method of any of embodiments 1-3, wherein the indication of the multiple active DRX configurations is sent in one or more lists.

[0071] In an embodiment 5, the method of embodiment 4, wherein the one or more lists comprise a first list and a second list. The first list indicates one or more DRX cycles for a first subset of the multiple active DRX configurations. The second list indicates one or more DRXcycles for a second subset of the multiple active DRX configurations, wherein each of the one or more DRX cycles for the second subset of the multiple active DRX configurations has a non-integer value.

[0072] In an embodiment 6, the method of any of embodiments 1-5, wherein sending the indication of the multiple active DRX configurations indicates to the DU to determine values for the one or more parameters configured for the multiple active DRX configurations.

[0073] In an embodiment 7, the method of any of embodiments 1-6, wherein at least one of the one or more parameters configured for the multiple active DRX configurations is received in one or more RRC DRX IEs.

[0074] In an embodiment 8, the method of embodiment 7, wherein the one or more RRC DRX IEs comprise a DRX Long Cycle Start Offset IE, a DRX Config IE, or both.

[0075] In an embodiment 9, the method of any of embodiments 1-8 further comprises receiving, from the DU, an indication whether the DU supports a multiple active DRX configurations capability. For examples, see Figure 3 (step 32) and Figure 5 (step 502).

[0076] In an embodiment 10, the receiving of embodiment 9 via signaling over an F1 interface that communicatively couples the CU and the DU.

[0077] In an embodiment 11, the method of any of embodiments 9-10, the indication whether the DU supports the multiple active DRX configurations capability received in network capability information.

[0078] In an embodiment 12, the method of any of embodiments 9-11, further comprising determining, by the CU, whether to configure the multiple active DRX configurations based at least in part on the indication whether the DU supports the multiple active DRX configurations capability. See, e.g., Figure 5 at step 504.

[0079] In an embodiment 13, the method of embodiment 12, wherein the determining whether to configure the multiple active DRX configurations is further based on whether there is a need for the multiple active DRX configurations.

[0080] In an embodiment 14, the method of embodiment 12 or 13, wherein the method determines to proceed with configuring the multiple active DRX configurations based at least in part on the indication indicating that the DU does support the multiple active DRX configurations capability. See, e.g., Figure 5 at step 510.

[0081] In an embodiment 15, the method of any of embodiments 1-14, the method further comprising configuring the CU to use the multiple active DRX configurations, wherein configuring the CU comprises applying the one or more parameters configured for the multiple active DRX configurations and received from the DU. See, e.g., Figure 5 at step 516.

[0082] In an embodiment 16, the method of embodiment 15, wherein configuring the CU further comprises applying multiple DRX cycle lengths determined by the CU.

[0083] In an embodiment 17, the method of any of embodiments 1-16 further comprises performing an operation of the CU using the multiple active DRX configurations. As an example, the method uses the multiple active DRX configurations to facilitate sending information to a UE when the multiple active DRX configurations indicate that the UE is expected to be in reception mode. Examples of information sent to the UE may include information related to paging (e.g., wake up signal or paging indication) or information related to scheduling (e.g., control information or PDDCH). See, e.g., Figure 3 (step 38) and Figure 5 (step 518).

[0084] In an embodiment 18, the method of embodiment 17, wherein the operation of the CU comprises any one or more of the following: using the multiple active DRX configurations to determine when a UE is expected to be in a reception mode and / or when the UE is expected to be in a non-reception mode; using the multiple active DRX configurations to facilitate scheduling communication with the UE based on when the UE is expected to be in the reception mode; using the multiple active DRX configurations to facilitate sending information to the UE when the UE is expected to be in the reception mode; using the multiple active DRX configurations to facilitate sending information related to paging to the UE when the UE is expected to be in the reception mode; using the multiple active DRX configurations to facilitate sending a wake up signal or a paging indication to the UE when the UE is expected to be in the reception mode; using the multiple active DRX configurations to facilitate sending information related to scheduling to the UE when the UE is expected to be in the reception mode; using the multiple active DRX configurations to facilitate sending control information to the UE when the UE is expected to be in the reception mode, wherein the control information schedules radio resources for communication between the UE and the network node; and / or using the multiple active DRX configurations to facilitate sending a PDDCH to the UE when the UE is expected to be in the reception mode, wherein the PDCCH schedules radio resources for communicating data traffic between the UE and the network node.

[0085] In an embodiment 19, the method of any of embodiments 1-18, further comprises receiving, from the DU, a list of Cell DTRX configurations, the list of Cell DTRX configurations configured per DU or per UE.

[0086] In an embodiment 20, a method is performed by a DU of a network node for configuring multiple active DRX configurations. The method comprises receiving, from a CU of the network node, an indication of the multiple active DRX configurations. The methodcomprises sending, to the CU, one or more parameters configured for the multiple active DRX configurations. For examples, see Figure 3 (steps 34 and 36) and Figure 6 (steps 604 and 608).

[0087] In an embodiment 21, the sending and / or receiving of embodiment 20 via signaling over an F1 interface that communicatively couples the CU and the DU. As an example, the indication of multiple active DRX configurations is received in a UE CONTEXT SETUP REQUEST message or a UE CONTEXT MODIFICATION REQUEST message via an F1 interface that communicatively couples the CU and the DU. As another example, the one or more parameters configured for the multiple active DRX configurations is sent in a UE CONTEXT SETUP RESPONSE message or a UE CONTEXT MODIFICATION RESPONSE message via an F1 interface that communicatively couples the CU and the DU. See, e.g., above discussion of example changes to TS 38.473.

[0088] In an embodiment 22, the method of any of embodiments 20-21, wherein the indication of the multiple active DRX configurations comprises multiple DRX cycle lengths. Each DRX cycle length of the multiple DRX cycle lengths is associated with a respective active DRX configuration of the multiple active DRX configurations.

[0089] In an embodiment 23, the method of any of embodiments 20-22, wherein the indication of the multiple active DRX configurations is received in one or more lists.

[0090] In an embodiment 24, the method of embodiment 23, wherein the one or more lists comprise a first list and a second list. The first list indicates one or more DRX cycles for a first subset of the multiple active DRX configurations. The second list indicates one or more DRX cycles for a second subset of the multiple active DRX configurations, wherein each of the one or more DRX cycles for the second subset of the multiple active DRX configurations has a non-integer value.

[0091] In an embodiment 25, the method of any of embodiments 20-24, wherein in response to receiving the indication of the multiple active DRX configurations from the CU, the method further comprises determining, by the DU, values for the one or more parameters configured for the multiple active DRX configurations; wherein the sending the one or more parameters configured for the multiple active DRX configurations comprises sending the values determined by the DU. See, e.g., Figure 6 at step 606.

[0092] In an embodiment 26, the method of any of embodiments 20-25, wherein at least one of the one or more parameters configured for the multiple active DRX configurations is sent in one or more RRC DRX IEs.

[0093] In an embodiment 27, the method of embodiment 26, wherein the one or more RRC DRX IEs comprise a DRX Long Cycle Start Offset IE, a DRX Config IE, or both.

[0094] In an embodiment 28, the method of any of embodiments 20-27 further comprises sending, to the CU, an indication whether the DU supports a multiple active DRX configurations capability. For examples, see Figure 3 (step 32) and Figure 6 (step 602).

[0095] In an embodiment 29, the sending of embodiment 28 via signaling over an F1 interface that communicatively couples the CU and the DU.

[0096] In an embodiment 30, any of embodiments 28-29, the indication whether the DU supports the multiple active DRX configurations capability sent in network capability information.

[0097] In an embodiment 31, the method of any of embodiments 20-30 further comprises configuring the DU to use the multiple active DRX configurations. Configuring the DU comprises applying the one or more parameters configured for the multiple active DRX configurations as determined by the DU and sent from the DU to the CU. See, e.g., Figure 6 at step 610.

[0098] In an embodiment 32, the method of embodiment 31, wherein configuring the DU further comprises applying multiple DRX cycle lengths received by the DU from the CU (such as the multiple DRX cycle lengths described above with respect to embodiment 22).

[0099] In an embodiment 33, the method of any of embodiments 20-32 further comprises performing an operation of the DU using the multiple active DRX configurations. As an example, the method uses the multiple active DRX configurations to facilitate sending information to a UE when the multiple active DRX configurations indicate that the UE is expected to be in reception mode. Examples of information sent to the UE may include information related to paging (e.g., wake up signal or paging indication) or information related to scheduling (e.g., control information or PDDCH). For examples, see Figure 3 (step 40) and Figure 6 (step 612).

[0100] In an embodiment 34, the method of embodiment 33, wherein the operation of the DU comprises any one or more of the following: using the multiple active DRX configurations to determine when a UE is expected to be in a reception mode and / or when the UE is expected to be in a non-reception mode; using the multiple active DRX configurations to facilitate scheduling communication with the UE based on when the UE is expected to be in the reception mode; using the multiple active DRX configurations to facilitate sending information to the UE when the UE is expected to be in the reception mode; using the multiple active DRX configurations to facilitate sending information related to paging to the UE when the UE is expected to be in the reception mode; using the multiple active DRX configurations to facilitate sending a wake up signal or a paging indication to the UE when the UE is expected to be in thereception mode; using the multiple active DRX configurations to facilitate sending information related to scheduling to the UE when the UE is expected to be in the reception mode; using the multiple active DRX configurations to facilitate sending control information to the UE when the UE is expected to be in the reception mode, wherein the control information schedules radio resources for communication between the UE and the network node; and / or using the multiple active DRX configurations to facilitate sending a physical downlink control channel (PDCCH) to the UE when the UE is expected to be in the reception mode, wherein the PDCCH schedules radio resources for communicating data traffic between the UE and the network node.

[0101] In an embodiment 35, the method of any of embodiments 20-34 further comprises sending, to the CU, a list of Cell DTRX configurations, the list of Cell DTRX configurations configured per DU or per UE.

[0102] In an embodiment 36, the method of any of embodiments 1-19 (the embodiments performed by the CU) or the method of any of embodiments 20-35 (the embodiments performed by the DU), the multiple active DRX configurations configured for a multi-modal service.

[0103] In an embodiment 37, the method of embodiment 36, the multi-modal service comprising an XR service.

[0104] In an embodiment 38, the method of any of embodiments 36-37, the multi-modal service comprising a plurality of related data flows subject to application coordination.

[0105] In an embodiment 39, the method of any of embodiments 1-38, the multiple active DRX configurations configured per serving cell.

[0106] In an embodiment 40, the method of any of embodiments 1-39, the multiple active DRX configurations applicable to a single UE.

[0107] In an embodiment 41, the method of any of embodiments 1-39, the multiple active DRX configurations applicable to multiple UEs, the multiple UEs supporting a plurality of related data flows.

[0108] In an embodiment 42, a method performed by a CU of a network node, the method comprises receiving, from a DU of the network node, an indication whether the DU supports a multiple active DRX configurations capability. The method comprises, in response to the indication indicating that the DU does not support the multiple active DRX configurations capability, abstaining from sending the DU an indication of multiple active DRX configurations. For examples, see Figure 3 (step 32) and Figure 5 (step 502 and step 506).

[0109] In an embodiment 43, the method of embodiment 42, further comprising sending, to the DU, an indication of a single active DRX configuration. See, e.g., Figure 5 at step 508.

[0110] In an embodiment 44, the method of any of the preceding embodiments (embodiments 1-43), wherein the network node comprises a gNB, the CU comprises a gNB- CU, and the DU comprises a gNB-DU.

[0111] In an embodiment 45, a network node (22, 24, 28, 110, or 300). The network node comprises processing circuitry (302) configured to perform any of the steps of any of embodiments 1-44. The network node comprises power supply circuitry (308) configured to supply power to the processing circuitry.

[0112] In an embodiment 46, a CU (24) of a network node (22, 110, 300). The CU comprises processing circuitry (302) configured to perform any of the steps of any of the above embodiments performed by a CU (see, e.g., embodiments 1-19 and 36-44). The CU comprises power supply circuitry (308) configured to supply power to the processing circuitry.

[0113] In an embodiment 47, a DU (28) of a network node (22, 110, 300). The DU comprises processing circuitry (302) configured to perform any of the steps of any of the above embodiments performed by a DU (see, e.g., embodiments 20-41). The DU comprises power supply circuitry (308) configured to supply power to the processing circuitry.

[0114] Figure 7 shows an example of a communication system 100 in accordance with some embodiments.

[0115] In the example, the communication system 100 includes a telecommunication network 102 that includes an access network 104, such as a radio access network (RAN), and a core network 106, which includes one or more core network nodes 108. An example of an access network 104 includes the NG-RAN 20 described above with respect to Figure 1 and / or Figure 2. An example of a core network 106 includes the 5GC 10 described above with respect to Figure 1. The access network 104 includes one or more access network nodes, such as network nodes 110a and 110b (one or more of which may be generally referred to as network nodes 110), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPP access points. Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network 102 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 102 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement oneor more functionalities of any node in the telecommunication network 102, including one or more network nodes 110 and / or core network nodes 108.

[0116] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O- CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an A1, F1, W1, E1, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an O-2 interface defined by the O-RAN Alliance or comparable technologies. The network nodes 110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 112a, 112b, 112c, and 112d (one or more of which may be generally referred to as UEs 112) to the core network 106 over one or more wireless connections.

[0117] Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 100 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0118] The UEs 112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 110 and other communication devices. Similarly, the network nodes 110 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 112 and / or with other network nodes or equipment in the telecommunication network 102to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network 102.

[0119] In the depicted example, the core network 106 connects the network nodes 110 to one or more host computing systems, such as host 116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 106 includes one more core network nodes (e.g., core network node 108) that are structured with 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, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 108. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0120] The host 116 may be under the ownership or control of a service provider other than an operator or provider of the access network 104 and / or the telecommunication network 102. The host 116 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0121] As a whole, the communication system 100 of Figure 7 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are 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 future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access(WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.

[0122] In some examples, the telecommunication network 102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 102. For example, the telecommunications network 102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive IoT services to yet further UEs.

[0123] In some examples, the UEs 112 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 104. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved- UMTS Terrestrial Radio Access Network) New Radio – Dual Connectivity (EN-DC).

[0124] In the example, the hub 114 communicates with the access network 104 to facilitate indirect communication between one or more UEs (e.g., UE 112c and / or 112d) and network nodes (e.g., network node 110b). In some examples, the hub 114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 114 may be a broadband router enabling access to the core network 106 for the UEs. As another example, the hub 114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 110, or by executable code, script, process, or other instructions in the hub 114. As another example, the hub 114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 114 may be a content source. For example, for a UE that is a VR device, display, loudspeaker, or other media delivery device, the hub 114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 114 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy IoT devices.

[0125] The hub 114 may have a constant / persistent or intermittent connection to the network node 110b. The hub 114 may also allow for a different communication scheme and / or schedule between the hub 114 and UEs (e.g., UE 112c and / or 112d), and between the hub 114 and the core network 106. In other examples, the hub 114 is connected to the core network 106 and / or one or more UEs via a wired connection. Moreover, the hub 114 may be configured to connect to an M2M service provider over the access network 104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 110 while still connected via the hub 114 via a wired or wireless connection. In some embodiments, the hub 114 may be a dedicated hub – that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 110b. In other embodiments, the hub 114 may be a non-dedicated hub – that is, a device which is capable of operating to route communications between the UEs and network node 110b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0126] Figure 8 shows a UE 200 in accordance with some embodiments. The UE 200 presents additional details of some embodiments of the UE 112 of Figure 1. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage / playback device, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), an Augmented Reality (AR) or Virtual Reality (VR) device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0127] A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (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 the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller).Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0128] The UE 200 includes processing circuitry 202 that is operatively coupled via a bus 204 to an input / output interface 206, a power source 208, a memory 210, a communication interface 212, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 8. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

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

[0130] In the example, the input / output interface 206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 200. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, 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 provide an input device and an output device.

[0131] In some embodiments, the power source 208 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 208 may further include power circuitry for delivering power from the power source 208 itself, and / or an external power source, to the various parts of the UE 200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 208. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 208 to make the power suitable for the respective components of the UE 200 to which power is supplied.

[0132] The memory 210 may be or be configured to include memory such as 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 disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 210 includes one or more application programs 214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 216. The memory 210 may store, for use by the UE 200, any of a variety of various operating systems or combinations of operating systems.

[0133] The memory 210 may be configured to include a number of physical drive units, such as 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, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 210 may allow the UE 200 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 210, which may be or comprise a device-readable storage medium.

[0134] The processing circuitry 202 may be configured to communicate with an access network or other network using the communication interface 212. The communication interface 212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 222. The communication interface 212 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 218 and / or a receiver 220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 218 and receiver 220 may be coupled to one or more antennas (e.g., antenna 222) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0135] In the illustrated embodiment, communication functions of the communication interface 212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing 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 networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0136] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 212, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering 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 a patient).

[0137] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, themotor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0138] A UE, when in the form of an Internet of Things (IoT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an IoT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot 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 electrical door lock, a connected doorbell, an air conditioning system like 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 wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an IoT device comprises circuitry and / or software in dependence of the intended application of the IoT device in addition to other components as described in relation to the UE 200 shown in Figure 8.

[0139] 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, which may in a 3GPP context 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, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0140] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in 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 the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second UE can also include more than one of thefunctionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0141] Figure 9 shows a network node 300 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

[0142] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0143] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0144] The network node 300 includes a processing circuitry 302, a memory 304, a communication interface 306, and a power source 308. The network node 300 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 300 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in someinstances be considered a single separate network node. In some embodiments, the network node 300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 304 for different RATs) and some components may be reused (e.g., a same antenna 310 may be shared by different RATs). The network node 300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 300.

[0145] The processing circuitry 302 may comprise a combination of one or more 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 encoded logic operable to provide, either alone or in conjunction with other network node 300 components, such as the memory 304, to provide network node 300 functionality.

[0146] In some embodiments, the processing circuitry 302 includes a system on a chip (SOC). In some embodiments, the processing circuitry 302 includes one or more of radio frequency (RF) transceiver circuitry 312 and baseband processing circuitry 314. In some embodiments, the radio frequency (RF) transceiver circuitry 312 and the baseband processing circuitry 314 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 312 and baseband processing circuitry 314 may be on the same chip or set of chips, boards, or units.

[0147] The memory 304 may comprise any form of volatile or non-volatile computer- readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), 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 may be used by the processing circuitry 302. The memory 304 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 302 and utilized by the network node 300. The memory 304 may be used to store anycalculations made by the processing circuitry 302 and / or any data received via the communication interface 306. In some embodiments, the processing circuitry 302 and memory 304 is integrated.

[0148] The communication interface 306 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface 306 comprises port(s) / terminal(s) 316 to send and receive data, for example to and from a network over a wired connection. The communication interface 306 also includes radio front-end circuitry 318 that may be coupled to, or in certain embodiments a part of, the antenna 310. Radio front-end circuitry 318 comprises filters 320 and amplifiers 322. The radio front-end circuitry 318 may be connected to an antenna 310 and processing circuitry 302. The radio front-end circuitry may be configured to condition signals communicated between antenna 310 and processing circuitry 302. The radio front-end circuitry 318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 320 and / or amplifiers 322. The radio signal may then be transmitted via the antenna 310. Similarly, when receiving data, the antenna 310 may collect radio signals which are then converted into digital data by the radio front-end circuitry 318. The digital data may be passed to the processing circuitry 302. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0149] In certain alternative embodiments, the network node 300 does not include separate radio front-end circuitry 318, instead, the processing circuitry 302 includes radio front-end circuitry and is connected to the antenna 310. Similarly, in some embodiments, all or some of the RF transceiver circuitry 312 is part of the communication interface 306. In still other embodiments, the communication interface 306 includes one or more ports or terminals 316, the radio front-end circuitry 318, and the RF transceiver circuitry 312, as part of a radio unit (not shown), and the communication interface 306 communicates with the baseband processing circuitry 314, which is part of a digital unit (not shown).

[0150] The antenna 310 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 310 may be coupled to the radio front-end circuitry 318 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 310 is separate from the network node 300 and connectable to the network node 300 through an interface or port.

[0151] The antenna 310, communication interface 306, and / or the processing circuitry 302 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the 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 310, the communication interface 306, and / or the processing circuitry 302 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0152] The power source 308 provides power to the various components of network node 300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 300 with power for performing the functionality described herein. For example, the network node 300 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 308. As a further example, the power source 308 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0153] Embodiments of the network node 300 may include additional components beyond those shown in Figure 9 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 300 may include user interface equipment to allow input of information into the network node 300 and to allow output of information from the network node 300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 300. In some embodiments providing a core network node, such as core network node 108 of FIG.1, some components, such as the radio front-end circuitry 318 and the RF transceiver circuitry 312 may be omitted.

[0154] Examples of a network node 300 include the gNB 22 (e.g., gNB 22a and gNB 22b) described with respect to Figure 1 and / or Figure 2. For the case of a gNB 22 implemented with a split architecture, components of the network node 300 may be distributed in any suitable manner. As an example, the gNB-CU 24 and the gNB-DU 28 may each include respective processing circuitry 302, memory 304, and power supply circuitry (e.g., power source 308).The gNB-CU 24 may further include at least one or more ports or terminals 316 of communication interface 306, for example, for connection of the E1 and F1 interfaces. However, the radio front-end circuitry 318 with antenna 310 may be optional and therefore omitted from certain embodiments of the gNB-CU 24. The gNB-DU 28’s communication interface 306 may include at least one or more ports or terminals 316 (e.g., for connection of the F1 interfaces) and the radio front-end circuitry 318 with antenna 310 (e.g., for communication with UEs). Embodiments of the network node 300 may include additional components beyond those shown in Figure 9 for providing certain aspects of the gNB 22, gNB- CU 24, and / or gNB-DU 28 functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein.

[0155] Figure 10 is a block diagram illustrating a virtualization environment 400 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 400 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 400 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface. Virtualization may facilitate distributed implementations of a network node, UE, core network node, or host.

[0156] Applications 402 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0157] Hardware 404 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 406(also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 408a and 408b (one or more of which may be generally referred to as VMs 408), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 406 may present a virtual operating platform that appears like networking hardware to the VMs 408.

[0158] The VMs 408 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 406. Different embodiments of the instance of a virtual appliance 402 may be implemented on one or more of VMs 408, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0159] In the context of NFV, a VM 408 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 408, and that part of hardware 404 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 408 on top of the hardware 404 and corresponds to the application 402.

[0160] Hardware 404 may be implemented in a standalone network node with generic or specific components. Hardware 404 may implement some functions via virtualization. Alternatively, hardware 404 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 410, which, among others, oversees lifecycle management of applications 402. In some embodiments, hardware 404 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 412 which may alternatively be used for communication between hardware nodes and radio units.

[0161] Although the computing devices described herein (e.g., UEs, network nodes) may include the illustrated combination of hardware components, other embodiments may comprisecomputing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0162] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain 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 the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer- readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.

Claims

CLAIMS 1. A method performed by a centralized unit (CU) of a network node, the method comprising: sending (34, 512), to a distributed unit (DU) of the network node, an indication of multiple active discontinuous reception (DRX) configurations; and receiving (36, 514), from the DU, one or more parameters configured for the multiple active DRX configurations.

2. The method of claim 1, wherein the indication of the multiple active DRX configurations comprises multiple DRX cycle lengths, each DRX cycle length of the multiple DRX cycle lengths associated with a respective active DRX configuration of the multiple active DRX configurations.

3. The method of any of claims 1-2, the indication of multiple active DRX configurations sent in a UE CONTEXT SETUP REQUEST message or a UE CONTEXT MODIFICATION REQUEST message via an F1 interface that communicatively couples the CU and the DU.

4. The method of any of claims 1-3, wherein sending the indication of the multiple active DRX configurations indicates to the DU to determine values for the one or more parameters configured for the multiple active DRX configurations.

5. The method of any of claims 1-4, wherein at least one of the one or more parameters configured for the multiple active DRX configurations is received in one or more radio resource control (RRC) DRX information elements (IEs).

6. The method of claim 5, wherein the one or more RRC DRX IEs comprise a DRX Long Cycle Start Offset IE, a DRX Config IE, or both.

7. The method of any of claims 1-6, the one or more parameters configured for the multiple active DRX configurations received in a UE CONTEXT SETUP RESPONSE message or a UE CONTEXT MODIFICATION RESPONSE message via an F1 interface that communicatively couples the CU and the DU.

8. The method of any of claims 1-7, wherein prior to sending the indication of the multiple active DRX configurations, the method further comprises receiving (32, 502), from the DU, an indication that the DU supports a multiple active DRX configurations capability.

9. The method of any of claims 1-8, further comprising using the multiple active DRX configurations to facilitate sending information to a user equipment (UE) when the multiple active DRX configurations indicate that the UE is expected to be in reception mode.

10. The method of any of claims 1-9, the method further comprising: configuring (516) the CU to use the multiple active DRX configurations, the configuring the CU based at least in part on: applying the one or more parameters configured for the multiple active DRX configurations and received from the DU; and applying multiple DRX cycle lengths determined by the CU; and performing (38, 518) an operation of the CU using the multiple active DRX configurations.

11. The method of any of claims 1-10: the multiple active DRX configurations applicable to a single user equipment (UE); or the multiple active DRX configurations applicable to multiple UEs supporting related data flows.

12. The method of any of claims 1-11, further comprising: receiving, from the DU, one or more cell discontinuous transmission / discontinuous reception (DTRX) configurations, the one or more cell DTRX configurations configured per DU or per UE and determined by the DU based on the multiple active DRX configurations.

13. A centralized unit (CU) (24) of a network node (22, 110, 300), the CU comprising: processing circuitry (302) configured to perform the steps of any of claims 1-12; and power supply circuitry (308) configured to supply power to the processing circuitry.

14. A method performed by a distributed unit (DU) of a network node, the method comprising: receiving (34, 604), from a centralized unit (CU) of the network node, an indication ofmultiple active discontinuous reception (DRX) configurations; and sending (36, 608), to the CU, one or more parameters configured for the multiple active DRX configurations.

15. The method of claim 14, wherein the indication of the multiple active DRX configurations comprises multiple DRX cycle lengths, each DRX cycle length of the multiple DRX cycle lengths associated with a respective active DRX configuration of the multiple active DRX configurations.

16. The method of any of claims 14-15, the indication of multiple active DRX configurations received in a UE CONTEXT SETUP REQUEST message or a UE CONTEXT MODIFICATION REQUEST message via an F1 interface that communicatively couples the CU and the DU.

17. The method of any of claims 14-16, wherein in response to receiving the indication of the multiple active DRX configurations from the CU, the method further comprises: determining (606), by the DU, values for the one or more parameters configured for the multiple active DRX configurations; wherein the sending the one or more parameters configured for the multiple active DRX configurations comprises sending the values determined by the DU.

18. The method of any of claims 14-17, wherein at least one of the one or more parameters configured for the multiple active DRX configurations is sent in one or more radio resource control (RRC) DRX information elements (IEs).

19. The method of claim 18, wherein the one or more RRC DRX IEs comprise a DRX Long Cycle Start Offset IE, a DRX Config IE, or both.

20. The method of any of claims 14-19, the one or more parameters configured for the multiple active DRX configurations sent in a UE CONTEXT SETUP RESPONSE message or a UE CONTEXT MODIFICATION RESPONSE message via an F1 interface that communicatively couples the CU and the DU.

21. The method of any of claims 14-20, further comprising:sending (32, 602), to the CU, an indication whether the DU supports a multiple active DRX configurations capability.

22. The method of any of claims 14-21, further comprising using the multiple active DRX configurations to facilitate sending information to a user equipment (UE) when the multiple active DRX configurations indicate that the UE is expected to be in reception mode.

23. The method of any of claims 14-22, the method further comprising: configuring (610) the DU to use the multiple active DRX configurations, the configuring the DU based at least in part on: applying the one or more parameters configured for the multiple active DRX configurations as determined by the DU and sent from the DU to the CU; and applying multiple DRX cycle lengths received by the DU from the CU; and performing (40, 612) an operation of the DU using the multiple active DRX configurations.

24. The method of any of claims 14-23: the multiple active DRX configurations applicable to a single user equipment (UE); or the multiple active DRX configurations applicable to multiple UEs supporting related data flows.

25. The method of any of claims 14-24, further comprising: sending, to the CU, one or more cell discontinuous transmission / discontinuous reception (DTRX) configurations, the one or more cell DTRX configurations configured per DU or per UE and determined by the DU based on the multiple active DRX configurations.

26. A distributed unit (DU) (28) of a network node (22, 110, 300), the DU comprising: processing circuitry (302) configured to perform the steps of any of claims 14-25; and power supply circuitry (308) configured to supply power to the processing circuitry.

Images