Secondary cell configuration

Abstract

The present disclosure relates to secondary cell configuration. Methods, apparatuses and computer programs are described, comprising: receiving, at a UE, from a network node of a mobile communication system, first configuration information for at least one SCell of one or more SCells configured for communication between the UE and the network node, wherein the first configuration comprises an indication indicating that the respective one or more SCells are set to be in a dormant state; receiving, at the UE, from the network node, second configuration information for at least one SCell of the one or more SCells, wherein the second configuration information comprises on-demand DRX configuration information, wherein the on-demand DRX configuration information configures an on-demand configuration timer; and starting, in response to a non-dormant condition, an on-duration timer associated with the at least one SCell, wherein an on-duration duration of each SCell lasts for a duration of the on-duration timer.

Description

Technical Field

[0001] Example embodiments may relate to systems, methods, and / or computer programs for configuring and controlling a secondary cell (SCell) as part of a mobile communication system. Background Technology

[0002] Enabling SCells to be used for communications within mobile networks (besides the primary cell PCell) can provide useful scheduling flexibility and benefits to end-user performance. Further development is still needed in this area. Summary of the Invention

[0003] The scope of protection sought by the various embodiments of the present invention is set forth in the independent claims. Embodiments and features described in this specification that are not within the scope of the independent claims (if any) are to be interpreted as examples for understanding the various embodiments of the invention.

[0004] In a first aspect, this specification describes a user equipment (UE) of a mobile communication system, comprising: components (e.g., input) for receiving discontinuously received DRX configuration information from a network node of the mobile communication system, the DRX configuration information including: on-demand DRX configuration information for at least one of one or more secondary cell SCells configured for communication between the UE and the network node (typically other than PCell), wherein the on-demand DRX configuration information configures an on-demand on-duration timer; and components (e.g., control module) for activating the on-demand on-duration timer associated with at least one SCell in response to the satisfaction of an on-duration indication condition (or some other trigger) for the corresponding SCell.

[0005] The UE may also include a component (e.g., a control module) for performing physical downlink control channel (PDCCH) monitoring for at least one SCell during the duration of the corresponding on-time period.

[0006] The UE may also include a component (e.g., a control module) for omitting PDCCH monitoring for each SCell with on-demand DRX configuration when performing PCell PDCCH monitoring and the on-duty duration indication condition is not met.

[0007] The UE may further include a component (e.g., an input) for receiving (e.g., via a PCell from the network node) a network indication (e.g., explicitly triggered) for at least one of the one or more SCells, such that an on-duration indication condition for the corresponding SCell is satisfied. The network condition may include an on-duration indication such that an on-duration indication condition for the corresponding SCell is satisfied. The network indication may be a downlink control indicator (DCI) (e.g., a wake-up signal DCI WUS-DCI), or may be part of a DCI. Alternatively, the network indication may be a low-power wake-up signal WUS, or may be part of a low-power WUS.

[0008] The UE may further include a component (e.g., a control module) for determining that an on-duration indication trigger event or condition has occurred for the at least one SCell, such that the on-duration indication condition is satisfied. The determination may be an example of implicit triggering. The on-duration indication trigger event or condition may, for example, include receiving at least one DCI that schedules downlink allocations exceeding a threshold level.

[0009] In some example embodiments, the DRX configuration information includes: the number N of on-duration periods monitored for the corresponding SCell. Furthermore, the UE may also include: a component (e.g., a control module) for restarting the on-duration timer N times when the number N of on-duration periods monitored for the corresponding SCell is greater than one. In some example embodiments, each restart of the on-duration timer occurs at the same time as the on-duration timer for the PCell is started.

[0010] The UE may also include components (e.g., outputs) for instructing network nodes of the mobile communication system to perform on-demand DRX configuration supported by the UE.

[0011] The DRX configuration information for the UE may include: on-demand DRX modes for different cells or cell groups.

[0012] In a second aspect, this specification describes a primary cell PCell that can be used for communication between a UE and a network node of a mobile communication system. The PCell includes: a component (e.g., an output) for providing discontinuous reception DRX configuration information to the UE. The DRX configuration information includes: on-demand DRX configuration information for at least one of one or more secondary cell SCells configured for communication between the UE and a network node other than the PCell, wherein the on-demand DRX configuration information configures an on-demand activation duration timer.

[0013] During the corresponding on-duration period, PDCCH monitoring for at least one SCell can be performed at the UE. PDCCH monitoring for each SCell can be omitted at the UE if the on-duration indication condition is not met.

[0014] PCell may further include: a component (e.g., an output) for providing (to the UE) a network indication (e.g., explicit triggering) from the network node for at least one of the one or more SCells, such that an on-duration indication condition for the corresponding SCell is satisfied. The network condition may include an on-duration indication such that an on-duration indication condition for the corresponding SCell is satisfied. The network indication may be a downlink control indicator (DCI) (e.g., a wake-up signal DCI WUS-DCI), or may be part of a DCI. Alternatively, the network indication may be a low-power wake-up signal WUS, or may be part of a low-power WUS.

[0015] In some example embodiments, the DRX configuration information includes the number N of on-duration periods monitored for the corresponding SCell. Additionally, the UE may include a component (e.g., a control module) for restarting the on-duration timer N times if the number N of on-duration periods monitored for the corresponding SCell is greater than one. In some example embodiments, each restart of the on-duration timer occurs at the same time that the on-duration timer for the PCell is started.

[0016] PCell may also include: a component (e.g., an input) for receiving instructions from the UE on-demand DRX configuration supported by the UE.

[0017] The DRX configuration information for the UE may include: on-demand DRX modes for different cells or cell groups.

[0018] In a third aspect, this specification describes a user equipment (UE) of a mobile communication system, comprising: components (e.g., input) for receiving first configuration information from a network node (e.g., PCell) of the mobile communication system, the first configuration information being configured for at least one of one or more secondary cell SCells configured for communication between the UE and the network node (typically other than the PCell), wherein the first configuration includes: an indication that the corresponding one or more SCells are set to a sleep state; components (e.g., input) for receiving second configuration information from the network node for at least one of the one or more SCells, wherein the second configuration information includes on-demand discontinuous reception of DRX configuration information, wherein the on-demand DRX configuration information configures an on-demand configuration timer; and components (e.g., a control module) for activating an on-duration timer associated with at least one SCell in response to a non-sleep condition (or some other trigger), wherein the on-duration for each SCell lasts for the duration of the on-duration timer.

[0019] The UE may further include: a component (e.g., a control module) for performing physical downlink control channel (PDCCH) monitoring for at least one SCell during the duration of the corresponding on-time duration. The UE may also include a component (e.g., a control module) for omitting PDCCH monitoring for each SCell with on-demand DRX configuration when performing PCell PDCCH monitoring, in the absence of the non-sleep condition.

[0020] The UE may further include: a component (e.g., an input) for receiving from the network node a network indication (or some other explicit trigger) for at least one of the one or more SCells, such that a non-sleep condition of the corresponding SCell is met. The network indication may be received from the network node via a PCell. The network indication may be a downlink control indicator (DCI) (e.g., a wake-up signal DCI WUS-DCI), or may be part of a DCI. Alternatively, the network indication may be a low-power wake-up signal WUS, or may be part of a low-power WUS.

[0021] In some example embodiments, the configuration information includes: the number N of on-duration periods monitored for the corresponding SCell. Furthermore, the UE may also include: a component (e.g., a control module) for restarting the on-duration timer N times when the number N of on-duration periods monitored for the corresponding SCell is greater than one. Each restart of the on-duration timer may occur at the same time as the on-duration timer for the PCell is started.

[0022] The UE may also include components (e.g., outputs) for instructing network nodes of the mobile communication system to perform on-demand DRX supported by the UE.

[0023] In the fourth aspect, this specification describes a primary cell PCell for communication between a UE and a network node of a mobile communication system. The PCell includes: a component (e.g., an output) for providing first configuration information to the UE, the first configuration information being configured for at least one of one or more secondary cell SCells configured for communication between the UE and the network node, excluding the PCell, wherein the first configuration includes: an indication that the corresponding one or more SCells are set to a sleep state; a component (e.g., an output) for providing the UE with second configuration information for at least one of the one or more SCells, wherein the second configuration information includes on-demand discontinuous reception DRX configuration information, wherein the on-demand DRX configuration information configures an on-demand configuration timer; and a component (e.g., an output) for providing the UE with a non-sleep condition (or some other trigger) associated with at least one SCell, wherein the non-sleep trigger configures at least one on-duration timer.

[0024] During the corresponding on-duty duration, the UE can perform PDCCH monitoring for at least one SCell. Furthermore, when performing PCell PDCCH monitoring, the UE can omit PDCCH monitoring for each SCell with on-demand DRX configuration in the absence of the aforementioned non-sleep conditions.

[0025] PCell may further include: a component (e.g., an output) for providing the UE with a network indication (or some other explicit trigger) from the network node for at least one of the one or more SCells, such that the non-sleep condition of the corresponding SCell is met. The network indication may be a downlink control indicator (DCI) (e.g., a wake-up signal DCI WUS-DCI), or may be part of a DCI. Alternatively, the network indication may be a low-power wake-up signal WUS, or may be part of a low-power WUS.

[0026] In some example embodiments, the configuration information includes: the number N of on-duration periods monitored for the corresponding SCell. Furthermore, the UE may also include: a component (e.g., a control module) for restarting the on-duration timer N times when the number N of on-duration periods monitored for the corresponding SCell is greater than one. Each restart of the on-duration timer may occur at the same time as the on-duration timer for the PCell is started.

[0027] PCell may also include: a component (e.g., an input) for receiving (from the UE) an instruction for on-demand DRX supported by the UE.

[0028] In a fifth aspect, this specification describes a method comprising: at a user equipment (UE), receiving discontinuous reception DRX configuration information from a network node of a mobile communication system, wherein the DRX configuration information includes: on-demand DRX configuration information for at least one of one or more secondary cell SCells configured for communication between the UE and the network node (typically other than PCells), wherein the on-demand DRX configuration information configures an on-demand on-duty duration timer; and starting the on-demand on-duty duration timer associated with the at least one SCell in response to the satisfaction of an on-duty duration indication condition (or some other trigger) for the corresponding SCell.

[0029] The method may include: performing PDCCH monitoring for at least one SCell during the duration of the corresponding on-time duration and / or omitting PDCCH monitoring for each SCell with on-demand DRX configuration when the on-time duration indication condition is not met during the performance of PCell PDCCH monitoring.

[0030] The method may include: receiving (e.g., from the network node via a PCell) a network indication (e.g., an explicit trigger) from the network node for at least one of the one or more SCells, such that an on-duration indication condition for the corresponding SCell is satisfied. The network condition may include an on-duration indication such that an on-duration indication condition for the corresponding SCell is satisfied. The network indication may be a downlink control indicator (DCI) (e.g., a wake-up signal DCI WUS-DCI), or may be part of a DCI. Alternatively, the network indication may be a low-power wake-up signal WUS, or may be part of a low-power WUS.

[0031] The method may include: determining that an enable duration indication triggering event or condition has occurred for the at least one SCell, such that the enable duration condition is met. The determination may be an example of implicit triggering. The enable duration indication triggering event or condition may, for example, include: receiving at least one DCI that schedules downlink allocations exceeding a threshold level.

[0032] In some example embodiments, the DRX configuration information includes: the number N of on-time durations monitored for the corresponding SCell. Furthermore, the method may also include: restarting the on-time duration timer N times if the number N of on-time durations monitored for the corresponding SCell is greater than one. In some example embodiments, each restart of the on-time duration timer occurs at the same time as the on-time duration timer for the PCell is started.

[0033] The method may also include: instructing network nodes of the mobile communication system that on-demand DRX configuration is supported by the UE.

[0034] The DRX configuration information for the UE may include: on-demand DRX modes for different cells or cell groups.

[0035] In a sixth aspect, this specification describes a method comprising: (from a PCell of a mobile communication system to a UE of the mobile communication system) providing discontinuous reception DRX configuration information, the DRX configuration information including: on-demand DRX configuration information for at least one of one or more secondary cell SCells configured for communication between the UE and a network node other than the PCell, wherein the on-demand DRX configuration information configures an on-demand activation duration timer.

[0036] During the corresponding on-duration period, PDCCH monitoring for at least one SCell can be performed at the UE. PDCCH monitoring for each SCell can be omitted at the UE if the on-duration indication condition is not met.

[0037] The method may further include: (from the PCell to the UE) providing a network indication (e.g., explicit triggering) from the network node for at least one of the one or more SCells, such that an on-duration indication condition for the corresponding SCell is satisfied. The network condition may include an on-duration indication such that the on-duration indication condition for the corresponding SCell is satisfied. The network indication may be a downlink control indicator (DCI) (e.g., a wake-up signal DCIWUS-DCI), or may be part of a DCI. Alternatively, the network indication may be a low-power wake-up signal WUS, or may be part of a low-power WUS.

[0038] In some example embodiments, the DRX configuration information includes: the number N of on-time durations monitored for the corresponding SCell. Furthermore, the method may also include: restarting the on-time duration timer N times if the number N of on-time durations monitored for the corresponding SCell is greater than one. In some example embodiments, each restart of the on-time duration timer occurs at the same time as the on-time duration timer for the PCell is started.

[0039] The method may also include: receiving from the UE an indication that on-demand DRX configuration is supported by the UE.

[0040] The DRX configuration information for the UE may include: on-demand DRX modes for different cells or cell groups.

[0041] In a seventh aspect, this specification describes a method comprising: receiving, at a user equipment (UE), first configuration information from a network node (e.g., a PCell) of a mobile communication system, the first configuration information being configured for at least one SCell of one or more secondary cell SCells (typically other than the PCell) for communication between the UE and the network node, wherein the first configuration includes: an indication that the corresponding one or more SCells are set to a sleep state; receiving, at the UE, second configuration information from the network node for at least one SCell of one or more SCells, wherein the second configuration information includes on-demand DRX configuration information, wherein the on-demand DRX configuration information configures an on-demand configuration timer; and starting an on-duration timer associated with at least one SCell in response to a non-sleep condition (or some other trigger), wherein the on-duration for each SCell lasts for the duration of the on-duration timer.

[0042] The method may include: performing PDCCH monitoring for at least one SCell during the duration of the corresponding on-time duration and / or omitting PDCCH monitoring for each SCell with on-demand DRX configuration when performing PCell PDCCH monitoring, in the absence of the non-sleep condition.

[0043] The method may include: receiving from the network node a network indication (or some other explicit trigger) for at least one of the one or more SCells, such that a non-sleep condition for the corresponding SCell is met. The network indication may be received from the network node via a PCell. The network indication may be a downlink control indicator (DCI) (e.g., a wake-up signal DCI WUS-DCI), or may be part of a DCI. Alternatively, the network indication may be a low-power wake-up signal WUS, or may be part of a low-power WUS.

[0044] In some example embodiments, the configuration information includes: the number N of on-time durations monitored for the corresponding SCell. Furthermore, the method may include: restarting the on-time duration timer N times if the number N of on-time durations monitored for the corresponding SCell is greater than one. Each restart of the on-time duration timer may occur at the same time as the on-time duration timer for the PCell is started.

[0045] The method may include instructing network nodes of the mobile communication system that DRX is supported by the UE on demand.

[0046] In the eighth aspect, this specification describes a method comprising: (from a PCell of a mobile communication system to a UE of the mobile communication system) providing first configuration information for at least one of one or more secondary cell SCells configured for communication between the UE and a network node other than the PCell, wherein the first configuration includes: an indication that the corresponding one or more SCells are set to a sleep state; providing the UE with second configuration information for at least one of the one or more SCells, wherein the second configuration information includes on-demand discontinuous reception DRX configuration information, wherein the on-demand DRX configuration information configures an on-demand configuration timer; and providing the UE with a non-sleep condition (or some other trigger) associated with at least one SCell, wherein the non-sleep trigger configures at least one on duration timer.

[0047] During the duration of the corresponding on-demand duration, the UE may perform PDCCH monitoring for at least one SCell and / or the UE may omit PDCCH monitoring for each SCell with on-demand DRX configuration when performing PCell PDCCH monitoring, in the absence of the non-sleep condition.

[0048] The method may include providing the UE with a network indication (or some other explicit trigger) from the network node for at least one of the one or more SCells, such that the non-sleep condition of the corresponding SCell is met. The network indication may be a downlink control indicator (DCI) (e.g., a wake-up signal DCI WUS-DCI), or may be part of a DCI. Alternatively, the network indication may be a low-power wake-up signal WUS, or may be part of a low-power WUS.

[0049] In some example embodiments, the configuration information includes: the number N of on-time durations monitored for the corresponding SCell. Furthermore, the method may also include: restarting the on-time duration timer N times if the number N of on-time durations monitored for the corresponding SCell is greater than one. Each restart of the on-time duration timer may occur at the same time as the on-time duration timer for the PCell is started.

[0050] The method may include: receiving (from the UE) an indication that on-demand DRX is supported by the UE.

[0051] In the ninth aspect, this specification describes computer-readable instructions that, when executed by a computing device, cause the computing device to perform (at least) any of the methods described herein (including the methods of the fifth to eighth aspects above).

[0052] In the tenth aspect, this specification describes a computer-readable medium (e.g., a non-transitory computer-readable medium) including program instructions stored thereon for performing (at least) any of the methods described herein (including the methods of the fifth to eighth aspects above).

[0053] In the eleventh aspect, this specification describes a computer program product including program instructions that, when executed by a device, cause the device to perform (at least) any of the methods described herein (including the methods described in the fifth to eighth aspects above).

[0054] In the twelfth aspect, this specification describes an apparatus comprising: at least one processor; and at least one memory storing instructions, which, when executed by the at least one processor, cause the apparatus to perform (at least) any of the methods described herein (including the methods of the fifth to eighth aspects above). Attached Figure Description

[0055] Exemplary embodiments will now be described by way of non-limiting example with reference to the accompanying drawings, in which:

[0056] Figure 1 This is a block diagram of a system according to an example embodiment;

[0057] Figure 2 A timing diagram according to an example embodiment is shown;

[0058] Figures 3 to 5 A flowchart according to an example embodiment is shown;

[0059] Figure 6 and Figure 7 A message flow sequence according to an example embodiment is shown;

[0060] Figure 8A flowchart according to an example embodiment is shown;

[0061] Figure 9 and Figure 10 A message flow sequence according to an example embodiment is shown;

[0062] Figure 11 These are schematic diagrams of systems that can be used to implement one or more example embodiments in the example embodiments; and

[0063] Figure 12 A tangible medium for storing computer-readable code is shown, which, when run by a computer, can perform methods according to the example embodiments described herein. Detailed Implementation

[0064] Figure 1 This is a block diagram of a system according to an exemplary embodiment, generally indicated by reference numeral 10. System 10 includes: a user equipment UE 12, a primary cell PCell 14, a first secondary cell SCell 16, and a second SCell 17.

[0065] UE 12 uses PCell 14 to communicate with the mobile communication system's network. One or more SCells, such as SCell 16 and SCell 17, may help improve user throughput (e.g., for downlink data transmission). For example, if data arrives at UE 12 in a burst, (multiple) SCells may be operational when the data is transmitted (i.e., during the data burst), but inactive under other circumstances.

[0066] When UE 12 is configured with carrier aggregation (CA), i.e., when the UE is configured with PCell and one or more SCells, PDCCH monitoring is typically performed periodically for each active carrier. This can result in relatively high power consumption.

[0067] Figure 2 A timing diagram according to an example embodiment is shown, generally indicated by reference numeral 20. Timing diagram 20 illustrates an example discontinuous reception DRX cycle. Periodic PDCCH monitoring occurs during the DRX-ON duration in each active cell and is based on... Figure 2 The DRX configuration shown.

[0068] Many mobile applications include data delivered in bursts (i.e., “bursting” services). For example, downlink data may be received by a UE (e.g., UE 12) in short bursts. These data bursts (which may be on the order of milliseconds) are interspersed with periods of relatively low data activity.

[0069] As an example, Figure 3This is a flowchart according to an exemplary embodiment, generally indicated by reference numeral 30 in the accompanying drawings. Flowchart 30 begins at step 32, where a data burst is received at the UE. Flowchart 30 then moves to step 34, where a period of relative data inactivity occurs. The flowchart then returns to step 32.

[0070] The duration of data inactivity step 34 can be on the order of hundreds of milliseconds, although many other durations are possible. In many example embodiments, the periods of steps 32 and 34 are typically not periodic and may be unpredictable (at least at the UE).

[0071] SCell 16 and SCell 17 of System 10 can be useful during the instance of step 32 (when a data burst is received) to improve data throughput. However, during the instance of step 34, it may be beneficial to reduce or remove PDCCH monitoring of (multiple) SCells to reduce UE power consumption.

[0072] In principle, the traditional dormant SCell framework can be used to achieve this goal. However, a drawback of the traditional framework is that once the SCell is indicated as non-dormant, the relevant UE should perform periodic PDCCH monitoring on the non-dormant cell according to the DRX parameter, which is per UE and therefore will be applied to all cells in the same Media Access Control (MAC) entity. This periodic behavior is applied until the cell is explicitly indicated as dormant again. This periodic monitoring may be unnecessary in many mobile applications.

[0073] Figure 4 This is a flowchart according to an example embodiment, typically indicated by reference numeral 40. Flowchart 40 is implemented at the UE, such as the UE 12 described above.

[0074] Flowchart 40 begins at step 42, where on-demand discontinuous reception DRX configuration information for one or more SCells (e.g., SCell 16 and SCell 17 described above) is received at the UE. Then, in step 44, PDCCH monitoring is performed on the SCell based on the received on-demand DRX configuration information. Flowchart 40 can be used to trigger PDCCH monitoring on the SCell during data bursts (e.g., in step 32 of flowchart 30), but not during periods of data inactivity (e.g., in step 34 of flowchart 30).

[0075] Figure 5 This is a flowchart according to an exemplary embodiment, generally indicated by reference numeral 50 in the accompanying drawings. Flowchart 50 can be used to implement aspects of the above-described flowchart 40.

[0076] Flowchart 50 begins at step 51, where DRX configuration information is provided from the network node of the mobile communication system to the UE (e.g., via PCell). The DRX configuration information includes on-demand DRX configuration information for at least one of one or more SCells configured for communication between the UE and the network node (SCells are used in addition to PCells, as discussed above). Therefore, step 51 can be used to implement step 42 of flowchart 40.

[0077] The on-demand DRX configuration information received in step 51 can be used to configure the on-demand start duration timer, as discussed in detail below.

[0078] In step 52, a determination is made as to whether the "on duration" condition has occurred for the corresponding SCell. If yes, the flowchart moves to step 53, where SCell monitoring is initiated. If not, the flowchart moves to step 55.

[0079] In step 53, in response to the on-duty on duration indication condition for the corresponding SCell being met, the on-demand on-duty on duration timer associated with the corresponding SCell is started. Then flowchart 50 moves to step 54.

[0080] In step 54, during the duration of the corresponding on-time, physical downlink control channel (PDCCH) monitoring is performed for at least one SCell (thus implementing step 44 of flowchart 40). As schematically indicated in flowchart 50, decision step 56 determines whether the on-time duration timer period has ended. If not, step 54 continues. Once the on-time duration timer period has ended, flowchart 50 terminates in step 57. Of course, the provision of this particular step 56 is illustrative—this functionality can be implemented in different ways.

[0081] As indicated above, if the on-duration condition has not yet been met, the flowchart moves to step 55. In step 55, when performing PCell PDCCH monitoring, PDCCH monitoring for each SCell with an on-demand DRX configuration is omitted. The flowchart then terminates at step 57.

[0082] Step 52 can be implemented in many ways. For example, the UE can receive a network indication for at least one of the one or more SCells from the network node (e.g., via PCell), such that an on-duration indication condition for the corresponding SCell is satisfied. The network condition may include an on-duration indication, providing an explicit indication that the on-duration indication condition for the corresponding SCell(s) is satisfied. The network indication may take the form of a downlink control indicator (DCI) (e.g., a wake-up signal DCI WUS-DCI). Alternatively, the network indication may take the form of a low-power wake-up signal (WUS).

[0083] Alternatively or additionally, the UE may be able to achieve step 52 by determining that an on-duration indication trigger event or condition has occurred for the at least one SCell (causing the on-duration indication condition to be satisfied). As discussed further below, the on-duration indication trigger event or condition may take the form of determining that the DCI allocated to the scheduled downlink exceeds a threshold level. Other implicit triggers are also possible.

[0084] Flowchart 50 can be implemented by building upon the existing Connected Mode Discontinuous Receive (C-DRX) algorithm, where SCell is configured with an aperiodic UE DRX configuration.

[0085] DRX configuration for a UE can include different DRX modes associated with different component carriers (CCs) in the same cell group. The default mode can be the traditional periodic DRX behavior, where DRX parameters are provided for each UE (e.g., PDCCH monitoring is performed for the SCell if it is available and the UE is in use). The new behavior is aperiodic (i.e., it is irregular / on-demand and does not follow the periodic structure of the DRX duty cycle) depending on the DRX period.

[0086] In one example embodiment, the DRX configuration is specific to the component carrier (e.g., by extending the traditional Drx-ConfigSecondaryGroup information element IE), and for at least one SCell, the DRX configuration can be configured to be non-periodic / on-demand, meaning that PDCCH monitoring does not occur at regular intervals and does not follow a known period, but is triggered based on certain events as discussed herein.

[0087] As indicated above, step 52 of flowchart 50 determines whether the on-duration condition has occurred for the corresponding SCell. The triggering of the on-duration condition can be implemented in many ways.

[0088] In the first example embodiment, an explicit network indication is used to trigger the event. For example, whenever burst data for the UE is present (causing the SCell to be activated), the PCell can send an indication (e.g., via DCI) that triggers the initiation of an aperiodic on-time duration on the SCell. Steps 53 to 56 of flowchart 50 can then be implemented.

[0089] Note that, as used herein, the term "aperiodic on-demand duration" refers to an on-demand duration triggered on demand rather than periodically, based on network indications (or some other trigger). Furthermore, the start time of an aperiodic on-demand duration may not necessarily be at the beginning of a DRX cycle as in a traditional arrangement, but could potentially occur at any time during the DRX cycle (e.g., upon receiving a network indication or after a specific offset, as configured). Aperiodic on-demand durations can be used to provide aperiodic / irregular DRX behavior, which may be more suitable for mobile traffic data occurring in bursts.

[0090] In one example embodiment, the non-periodic on-duration of the SCell is valid for a single on-duration (which may be referred to as a "one-off" on-duration) or for a specific number of configured on-durations. Multiple additional on-duration timers following the first timer can be started simultaneously with the on-duration for the PCell (or reference cell). This means that the start of the on-duration for the SCell can be scheduled to occur based on the start of the on-duration for the PCell (or similarly, the reference cell).

[0091] In some example embodiments, the network indicator can dynamically configure at least one DRX parameter to be applied to the SCell, such as one or more of the following: • The on-duration duration applied in at least two on-duration values ​​configured for SCell. • Apply an inactive timer to at least two values ​​configured for SCell. • The number of on durations applied in at least two values ​​configured for SCell.

[0092] By enabling dynamic selection of DRX parameters for a given UE, the network can be provided with greater flexibility to optimally configure DRX parameters, depending on one or more of the following: current data in the buffer for the UE; data predicted in the near future (e.g., within the same DRX cycle or the next cycle); and the current cell load level.

[0093] As indicated above, the dynamic network indicator can be provided by the PCell via DCI. In one example embodiment, the dynamic network indicator can be provided via WUS-DCI (e.g., DCI_2_6) Provided with a new bit / bitmap associated with the SCell / secondary cell group. In another example embodiment, the dynamic network indication can be provided via the scheduling DCI (a DCI carrying scheduling authority). In this case, the identifier of the SCell to which the indication is applied can be provided in the DCI. If multiple DRX parameter values ​​are configured, the indication can also indicate which value should be applied (e.g., a default value or some other value). Where selection of each parameter among multiple values ​​is supported, more than one bit per parameter can be added to the DCI.

[0094] In alternative embodiments, aperiodic DRX can be implicitly triggered based on the satisfaction of pre-configured or anticipated events or conditions (making it possible to provide event-based, on-demand aperiodic DRX). In one example embodiment, receiving a specific number of scheduling grants (DCIs) on a PCell during its on-duty period, or extending the on-duty period of a PCell by X milliseconds, can trigger the application of an aperiodic on-duty period on the SCell. Therefore, step 52 of flowchart 50 can be based at least in part on the detection of implicit triggering.

[0095] Figure 6 A message flow sequence according to an example embodiment is illustrated, generally indicated by reference numeral 60. Message flow sequence 60 is an example implementation of flowchart 50, in which on-demand DRX configuration is implemented with a single on-duty duration.

[0096] Message flow sequence 60 illustrates the messages transmitted between UE 62 (e.g., UE 12), PCell 64 (e.g., PCell 14), and SCell 66 (e.g., one of SCells 16 and SCell 17) and the actions taken at them.

[0097] In step 1, UE capability information is provided by UE 62 to PCell 64. In this way, UE 62 can indicate to the network nodes of the mobile communication system that on-demand DRX configuration is supported by the UE. UE 62 also provides measurement reports (e.g., L3 measurements) to PCell 64 in step 2.

[0098] In step 3, an RRC reconfiguration message is sent from PCell 64 to UE 62. The network configures the UE with configuration for (multiple) SCells along with a DRX-ConfigSecondaryGroup information element (IE), which includes parameters for enabling DRX aperiodic operation modes for (multiple) added SCells and / or DRX-NumberOfonDurationOccasions and drx-SlotOffset, described below. An RRC reconfiguration complete message is sent in response (step 4).

[0099] In steps 5 and 6, SCell is activated at UE, PCell, and SCell.

[0100] Steps 7 through 10 involve the first PCell DRX cycle. In step 9, UE 62 performs PDCCH monitoring for PCell 64, but does not monitor the PDCCH on the SCell because the DRX aperiodic parameter is set to true, and (unlike conventional operating modes) the UE will not monitor the PDCCH on the SCell. Therefore, step 55 of flowchart 50 is implemented (instead of steps 53, 54, and 56).

[0101] Steps 11 through 15 involve the second PCell DRX cycle. In step 13, UE 62 still does not monitor the PDCCH on the SCell because the drx aperiodic parameter is set to true.

[0102] In step 14, UE 62 receives PDCCH on PCell, which enables a one-time SCell on-duration duration based on RRC configuration parameters drx-NumberOfonDurationOccasions = 1 and drx-SlotOffset = 0 (the PDCCH monitoring / on-duration start for SCell will begin in the same time slot). The on-duration duration condition is triggered at UE 62 in step 15 (e.g., causing flowchart 50 to move from step 52 to step 53).

[0103] Steps 16 through 22 concern the SCell on-time (a unique on-time, as this is a one-time example). Perform PDCCH monitoring on the SCell (see steps 17 through 21).

[0104] In step 22, the SCell's active time ends because there is no further authorization and the inactivity timer has expired. Furthermore, the UE will not attempt to initiate SCell PDCCH monitoring in the next PCell DRX cycle, as this is intended only as a one-time DCI trigger for SCell monitoring of the PDCCH.

[0105] Figure 7 A message flow sequence according to an example embodiment is illustrated, generally indicated by reference numeral 70. Message flow sequence 70 is an example implementation of flowchart 50, in which on-demand DRX configuration is implemented with two on-duty durations. Message flow sequence 70 illustrates the messages transmitted between the aforementioned UE 62, PCell 64, and SCell 66, and the actions taken at them.

[0106] Steps 1-10 of message flow sequence 70 are the same as steps 1-10 of message flow sequence 60 above.

[0107] Steps 11 through 15 involve the second PCell DRX cycle. In step 13, UE 62 still does not monitor the PDCCH on the SCell because the drx aperiodic parameter is set to true.

[0108] In step 14, UE 62 receives the PDCCH on the PCell, which triggers the application for two on-duration periods for the SCell according to the RRC configuration parameters. This is triggered in step 15.

[0109] Steps 16 through 22 relate to the first SCell on-time (the first of two on-time durations in this example). Perform PDCCH monitoring on the SCell (see steps 17 through 21).

[0110] In steps 24 and 25, the third PCell DRX cycle begins with the PCell on-duration duration, and the SCell on-duration duration also starts simultaneously due to drx-NumberOfonDurationOccasions = 2. From this point onward, the UE simultaneously monitors the PDCCH on both the PCell and SCell.

[0111] In step 30, the SCell's active time ends because there is no further authorization and the inactivity timer has expired. The UE will no longer attempt to initiate SCell PDCCH monitoring on the next PCell DRX cycle because the second on-duration count configured by drx-NumberOfonDurationOccasions has been completed.

[0112] Therefore, in message flow sequence 70, the DRX configuration information includes: the number N of on-duration monitoring for the corresponding SCell (N=2 in this example, but may be a different number in other example implementations). The on-duration timer is restarted based on the number N (if the number N of on-duration monitoring for the corresponding SCell is greater than one). Each restart of the on-duration timer can occur at the same time as the on-duration timer for the PCell is started.

[0113] It should be noted that the dynamic configuration of DRX parameters via DCI can be achieved via network indication in step 14 of message flow sequence 70. By dynamically selecting the DRX parameters that a given UE should use, the network can be provided with greater flexibility to optimally configure DRX parameters, depending on the current data in the buffer for the UE (buffer occupancy), or the data predicted for the UE in the near future (within the same DRX cycle or the next cycle), and the current cell load level.

[0114] The example implementations of message sequences 60 and 70 may include one or more of the following parameters: • drx-non-cyclic This parameter can be set to true to indicate the duration of non-periodic / irregular DRX on-time for PDCCH monitoring on the SCell in the DRX secondary cell group. • drx-NumberOfonDurationOccasions This parameter specifies the number of times a configured SCell can remain on once the UE is triggered to start monitoring the PDCCH on that SCell. When this count ends, the UE stops monitoring the PDCCH on that SCell. • drx-SlotOffset This parameter specifies the delay before drx-onDurationTimer is started. drx-onDurationTimer is the duration at the start of the DRX cycle during which the UE actively monitors the Physical Downlink Control Channel (PDCCH) for potential downlink transmissions.

[0115] Figure 8 A flowchart according to an example embodiment is shown, generally indicated by reference numeral 80. Flowchart 80 can be used to implement aspects of flowchart 40 described above (and has many similarities to flowchart 50 described above).

[0116] Flowchart 80 begins at step 81, where DRX configuration information is provided to the UE from the network node of the mobile communication system (e.g., via PCell). The DRX configuration information includes on-demand DRX configuration information for at least one of one or more SCells configured for communication between the UE and the network node (SCells used in addition to PCells). The on-demand DRX configuration information configures an on-demand activation duration timer, as discussed in detail below. Therefore, step 81 can be used to implement step 42 of flowchart 40.

[0117] In step 82, a determination is made as to whether the corresponding SCell has entered a "dormant" state. If not, the flowchart moves to step 83, where SCell monitoring is initiated. If the cell is considered dormant, the flowchart moves to step 85.

[0118] In step 83, the on-demand start duration timer associated with the corresponding SCell (which is in a non-sleep condition) is started. Then flowchart 80 moves to step 84.

[0119] In step 84, physical downlink control channel (PDCCH) monitoring is performed for at least one SCell during the duration of the corresponding enable duration timer (thus implementing step 44 of flowchart 40). As schematically indicated in flowchart 80, step 86 determines whether the enable duration timer has ended. If not, step 84 continues. Once the enable duration timer has ended, flowchart 80 terminates in step 87.

[0120] As indicated above, if a hibernation condition exists, the flowchart moves to step 85. In step 85, when performing PCell PDCCH monitoring, PDCCH monitoring for each SCell with an on-demand DRX configuration is omitted. The flowchart then terminates at step 87.

[0121] Step 82 can be implemented in many ways. For example, the UE can receive a network indication from the network node (e.g., via PCell) for at least one of the one or more SCells, such that a non-sleep condition for the corresponding SCell is met. The network condition may include an on-duration indication, providing an explicit indication that the on-duration condition for the corresponding SCell is met. The network indication may take the form of a downlink control indicator (DCI) (e.g., a wake-up signal DCIWUS-DCI). Alternatively, the network indication may take the form of a low-power wake-up signal (WUS).

[0122] Flowchart 80 can be implemented by building upon the existing Connected Mode Discontinuous Receive (C-DRX) algorithm, where the SCell is configured to sleep and not configured for DRX.

[0123] A UE's (multiple) DRX configurations can include different DRX modes associated with different component carriers (CCs) in the same cell group. The indication can be a bitmap of size equal to the number of active CCs, which can indicate 0 or 1 respectively if DRX applies to a CC.

[0124] In one example, the DRX configuration applies only to PCells (or only to CCs with associated PDCCH configurations). CCs for which DRX does not apply can be configured to implicitly hibernate.

[0125] In one example embodiment, dedicated parameters related to on-demand PDCCH monitoring of SCells that are not applicable to DRX can be provided in the DormantBWP-Config, such as including at least one non-sleep on-duration duration and a non-sleep inactivity timer that can be introduced. Therefore, these parameters can be applied during the period when the SCell is non-sleep (i.e., when the network indicates a non-sleep state).

[0126] The UE-DRX configuration may also include dedicated parameters related to PDCCH monitoring of SCells that are not applicable to DRX, where these parameters should be applied when the SCell is not in a dormant state (i.e., when the network indicates a non-dormant state). This may include on-duration parameters or similar new parameters (e.g., non-dormant on-duration duration).

[0127] When a UE receives, for example, a sleep indication for one or more SCells (CCs) set to "non-sleep state" via DCI / L1 signaling (using the conventional method, i.e., DCI format 2_6, DCI format 1_0, or DCI format 1_1), flowchart 80 can move from step 82 to step 83. The network can send this indication during a burst of traffic, where the traffic volume for the UE is high, for example, exceeding a certain data volume threshold.

[0128] If the indication is given during the PCell's active time, the UE can immediately start the SCell's on-duration (or non-sleep on-duration) timer when indicating a non-sleep state (see step 83). In this case, the network can send the indication via the PCell during a burst of service, such as during the PCell's on-duration or active time.

[0129] In another example embodiment, if the indication occurs outside the active time of the PCell, the UE starts the on-duration timer of the SCell during the next active time of the PCell when the non-sleep state is indicated (in step 83).

[0130] In some example embodiments, the SCell (CC) sleep indicator may explicitly indicate whether the start duration timer must start immediately or after an indicated delay.

[0131] In some example implementations, the UE applies the same PDCCH monitoring to the SCell as it does to the PCell during the current PCell's DRX cycle. At the end of the current DRX cycle, the UE stops PDCCH monitoring on the SCell.

[0132] It should be noted that although flowcharts 50 and 80 provide different examples of SCell on-duration triggering, the two algorithms can be combined (so that both options are available in the same implementation).

[0133] Figure 9 A message flow sequence according to an example embodiment is illustrated, generally indicated by reference numeral 90. Message flow sequence 90 is an example implementation of flowchart 80, wherein a SCell non-sleep trigger is received during the PCell active time. Message flow sequence 90 illustrates the messages transmitted between UE 92 (e.g., UE 12), PCell 94 (e.g., PCell 14), and SCell 96 (e.g., one of SCell 16 and SCell 17), and the actions taken at them.

[0134] In step 1, a measurement report (L3 measurement) is sent from UE 92 to PCell 94.

[0135] In step 2, PCell 94 sends an RRC reconfiguration message to UE 92. In this way, the network adds configuration to (multiple) SCells for UE 92, the SCell state is set to sleep, along with `withoutdrx-ConfigSecondaryGroup` being set to true, and the PDCCH monitoring configuration is included in `DormantBWP-DRX-Config-r20`. Due to this configuration, the UE will only monitor the PDCCH on the PCell at the start of the DRX activation time, and the SCell will remain in sleep mode.

[0136] In step 4, UE 92 activates the SCell and moves it to a sleep state.

[0137] Steps 5 through 8 involve the first PCell DRX cycle. In step 6, UE 92 monitors the PDCCH for PCell 94, but it does not monitor the PDCCH on the SCell (the SCell is dormant – see step 7). Therefore, step 85 of flowchart 80 is implemented (instead of steps 83, 84, and 86).

[0138] In step 8, the DCI (DCI_1_1 / DCI_1_0) received on the PCell PDCCH sets the SCell to a non-sleep state. Note that in this example, the SCell wake-up from the non-sleep state is received during the PCell's active time.

[0139] DCI can indicate: the length of the on-duration period and the number of on-duration periods that should be monitored for PDCCH on non-sleeping SCells. If the RRC configuration includes more than one PDCCH monitoring parameter value or more than one PDCCH monitoring configuration, DCI can simply indicate: the index of the applicable PDCCH monitoring configuration to be applied.

[0140] Steps 9 through 15 relate to the SCell on-time duration.

[0141] In step 9, the UE initiates the SCell on-time and begins monitoring the SCell PDCCH. In step 15, the SCell's active time ends because there is no further authorization and the inactivity timer has expired. Furthermore, the UE will not attempt to initiate SCell PDCCH monitoring in the next PCell DRX cycle, as this is intended only as a one-time DCI trigger for SCell PDCCH monitoring.

[0142] Figure 10 A message flow sequence according to an example embodiment is illustrated, generally indicated by reference numeral 100. Message flow sequence 100 is an example implementation of flowchart 80, wherein a non-sleep trigger of the SCell is received outside of PCell active time. Message flow sequence 100 illustrates the messages transmitted between the aforementioned UE 92, PCell 94, and SCell 96, and the actions taken at them.

[0143] In step 1, a measurement report (L3 measurement) is sent from UE 92 to PCell 94.

[0144] In step 2, PCell 94 sends an RRC reconfiguration message to UE 92. In this way, the network adds configuration to (multiple) SCells for UE 92, the SCell state is set to sleep, along with `withoutdrx-ConfigSecondaryGroup` being set to true, and the PDCCH monitoring configuration is included in `DormantBWP-DRX-Config-r20`. Due to this configuration, the UE will only monitor the PDCCH on the PCell at the start of the DRX activation time, and the SCell will remain in sleep mode.

[0145] In step 4, the UE activates the SCell and moves it to a sleep state.

[0146] In step 5, a non-sleep trigger is received (outside of PCell active time). Specifically, in this example, the non-sleep trigger takes the form of a wake-up signal (in DCI_2_6 format in the illustrated example) received from the network via PCell 94. The wake-up signal sets the SCell to a non-sleep state, which takes effect at the start of the next PCell DRX on time.

[0147] DCI can indicate: the length of the on-duration period, and the number of on-duration periods that should be monitored on non-sleeping SCells. If the RRC configuration includes more than one PDCCH monitoring parameter value or more than one PDCCH monitoring configuration, DCI can indicate only the index of the applicable PDCCH monitoring configuration to be applied.

[0148] Steps 7 through 15 involve the first PCell DRX cycle and the first SCell DRX cycle. In step 7, UE 92 initiates the PCell on-time and SCell on-time durations. In step 8, UE 92 begins monitoring the PCell and PDCCH for the SCell. Therefore, steps 83, 84, and 86 of flowchart 80 are implemented.

[0149] Note: In this example, we consider an RRC configuration for SCell PDCCH monitoring with numberOfOnDurationOccasions = 1.

[0150] In step 14, the SCell's active time ends because there is no further authorization and the inactivity timer has expired. Furthermore, the UE will not attempt to initiate SCell PDCCH monitoring in the next PCell DRX cycle, as this is intended only as a one-time DCI trigger for SCell monitoring of the PDCCH.

[0151] In one example implementation (Configuration Option 1 – see below), non-dormant PDCCH monitoring can be configured by the network in the DormantBWP-Config for each configured SCell. This type of non-dormant PDCCH monitoring configuration can be activated during or outside of PCell activity time, when the SCell's bandwidth BWP is switched from a dormant BWP to an active BWP.

[0152] Configuration Option 1:

[0153] In another example (configuration option 2 – see below), the non-dormant PDCCH monitoring configuration can be configured by the network in a container for non-dormant SCell PDCCH monitoring within the ServingCellConfig structure for each SCell. This type of non-dormant PDCCH monitoring configuration can be activated during or outside of PCell activity time, when the SCell's BWP is switched from a dormant BWP to an active BWP. Configuration Option 2:

[0154] Example device

[0155] Figure 11 An apparatus according to some example embodiments is shown, which may include a user terminal 200. The apparatus may be configured to perform operations described herein, such as those described with reference to any disclosed process. The apparatus includes at least one processor 202 and at least one memory 204 directly or closely connected to the processor. The memory 204 includes at least one random access memory (RAM) and at least one read-only memory (ROM). Computer program code (software) 205 is stored in the memory (typically in the ROM). The apparatus may be connected to a radio interface 206, typically including a transmitter (TX) and a receiver (RX). The apparatus may optionally be connected to a user interface UI 208 for indicating the apparatus and / or for outputting data. At least one processor 202, together with at least one memory 204 and computer program code 205, is arranged such that the apparatus performs at least one method according to any of the foregoing processes, such as those described above. Figures 3 to 10 The flowcharts and message sequences and their associated characteristics are disclosed.

[0156] Figure 12A non-transitory medium 250 is illustrated according to some embodiments. The non-transitory medium 250 is a computer-readable storage medium. It may be, for example, a CD, DVD, USB flash drive, Blu-ray disc, etc. The non-transitory medium 250 stores computer program code that causes a device to perform any of the aforementioned processes, such as those disclosed with respect to the flowcharts and their related features.

[0157] The names of network elements, protocols, and methods are based on current standards. In other versions or other technologies, the names of these network elements and / or protocols and / or methods may differ, as long as they provide the corresponding functionality. For example, embodiments may be deployed in 2G / 3G / 4G / 5G networks and 3GPP next-generation networks, but may also be deployed in non-3GPP radio networks, such as WiFi.

[0158] The memory can be volatile or non-volatile. It can be, for example, RAM, SRAM, flash memory, FPGA block RAM, DVD, CD, USB memory stick, and Blu-ray disc.

[0159] Unless otherwise stated or clearly indicated from the context, different statements about two entities mean that they perform different functions. This does not necessarily mean that they are based on different hardware. That is, each entity described in this specification may be based on different hardware, or some or all entities may be based on the same hardware. This does not necessarily mean that they are based on different software. That is, each entity described in this specification may be based on different software, or some or all entities may be based on the same software. Each entity described in this specification can be implemented in the cloud.

[0160] Implementations of any of the foregoing blocks, devices, systems, techniques, or methods include (by way of non-limiting example) implementations as hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers, or other computing devices or some combination thereof. Some embodiments may be implemented in the cloud.

[0161] It should be understood that the above description represents what is currently considered a preferred embodiment. However, it should be noted that the description of the preferred embodiment is given by way of example only, and various modifications can be made without departing from the scope defined by the appended claims.

Claims

1. A user equipment (UE), comprising: At least one processor; as well as At least one memory stores instructions that, when executed by the at least one processor, cause the UE to at least: Discontinuous reception DRX configuration information is received from a network node of a mobile communication system. The DRX configuration information includes: on-demand DRX configuration information for at least one SCell among one or more secondary cell SCells configured for communication between the UE and the network node, wherein the on-demand DRX configuration information configures an on-demand activation duration timer; and In response to the fulfillment of the on-duty on duration indication condition for the corresponding SCell, an on-demand on-duty on duration timer associated with the at least one SCell is started.

2. The UE of claim 1, wherein the instruction, when executed by the at least one processor, further causes the UE to: During the duration of the corresponding activation duration, physical downlink control channel (PDCCH) monitoring is performed for the at least one SCell; and / or When performing PCell PDCCH monitoring, if the on-duty duration indication condition is not met, PDCCH monitoring is omitted for each SCell with on-demand DRX configuration.

3. The UE according to claim 1, wherein the instruction, when executed by the at least one processor, further causes the UE to: Receive network indication from the network node for at least one of the one or more SCells, such that the on-duration indication condition for the corresponding SCell is satisfied; The network conditions include an on-duration indication, such that the on-duration indication condition for the corresponding SCell is satisfied.

4. The UE of claim 3, wherein the network indication is received from the network node via PCell; The network indication mentioned therein is a Downlink Control Indicator (DCI) or is part of a DCI; The DCI mentioned therein is the wake-up signal DCI WUS-DCI; or The network indication is either a low-power wake-up signal (WUS) or a part of a low-power WUS.

5. The UE according to any one of claims 1 to 4, wherein the instructions, when executed by the at least one processor, further cause the UE to: Determine that an on-duration indication trigger event or condition has occurred for the at least one SCell, such that the on-duration condition is satisfied; The activation duration indicates the triggering event or condition, including: Receive at least one DCI, the at least one DCI scheduling downlink allocations exceeding a threshold level.

6. The UE according to any one of claims 1 to 4, wherein the DRX configuration information includes: For the number N of on-time durations monitored by the corresponding SCell, wherein the instruction, when executed by the at least one processor, also causes the UE to: If the number N of the on-duration times monitored for the corresponding SCell is greater than one, the on-duration timer is restarted N times; and Each restart of the on-duration timer occurs when the on-duration timer for the PCell is started.

7. The UE according to any one of claims 1 to 4, wherein the instructions, when executed by the at least one processor, further cause the UE to: Indicate to the network node of the mobile communication system that on-demand DRX configuration is supported by the UE.

8. The UE according to any one of claims 1 to 4, wherein the DRX configuration information for the UE includes: On-demand DRX mode for different communities or community groups.

9. A primary cell PCell, used for communication between a UE and a network node of a mobile communication system, the PCell comprising: At least one processor; as well as At least one memory stores instructions that, when executed by the at least one processor, cause the PCell to at least: The UE is provided with discontinuous reception DRX configuration information, which includes on-demand DRX configuration information for at least one of one or more secondary cell SCells configured for communication between the UE and the network node, excluding the PCell, wherein the on-demand DRX configuration information configures an on-demand activation duration timer.

10. A method for communication, comprising: At the User Equipment (UE), discontinuous reception DRX configuration information is received from a network node of a mobile communication system. The DRX configuration information includes: on-demand DRX configuration information for at least one SCell among one or more secondary cell SCells configured for communication between the UE and the network node, wherein the on-demand DRX configuration information configures an on-demand activation duration timer; and In response to the fulfillment of the on-duty on duration indication condition for the corresponding SCell, an on-demand on-duty on duration timer associated with the at least one SCell is started.

Images