System and method for managing discontinuous reception (DRX) configuration in a network

Abstract

The present disclosure relates to a system (108) and a method (400) for managing Discontinuous Reception (DRX) configuration of a User Equipment (UE) (104) in a network (106) The method (400) includes receiving (402), by a processing engine (208), at least one network condition parameter associated with the UE (104). The method further includes comparing (404), by the processing engine (208), the received network condition parameter with at least one predefined performance threshold and determining (406) at least one condition state of the UE (104). The method further includes adjusting (408), by the processing engine (208), one or more DRX parameters associated with the UE (104) based on the determined condition state. The method further includes configuring (410) the UE (104) with the adjusted DRX parameters for DRX operation.

Description

SYSTEM AND METHOD FOR MANAGING DISCONTINUOUS RECEPTION (DRX) CONFIGURATION IN A NETWORK RESERVATION OF RIGHTS

[0001] A portion of the disclosure of this patent document contains material, which is subject to intellectual property rights such as, but are not limited to, copyright, design, trademark, Integrated Circuit (IC) layout design, and / or trade dress protection, belonging to Jio Platforms Limited (JPL) or its affiliates (hereinafter referred as owner). The owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all rights whatsoever. All rights to such intellectual property are fully reserved by the owner.FIELD OF DISCLOSURE

[0002] The embodiments of the present disclosure generally relate to communication networks. In particular, the present disclosure relates to a system and a method for managing Discontinuous Reception (DRX) configuration in a network.DEFINITIONS

[0003] As used in the present disclosure, the following terms are generally intended to have the meaning as set forth below, except to the extent that the context in which they are used to indicate otherwise.

[0004] The term “Discontinuous Reception (DRX)” used hereinafter in the specification refers to a power-saving mechanism in which a User Equipment (UE) alternates between an active state and an inactive state to reduce power consumption while maintaining connectivity with the network. DRX operation is controlled by parameters such as On Duration, DRX Inactivity Timer, and DRX Cycle lengths.

[0005] The term “On Duration” used hereinafter in the specification refers to the specific time interval within a DRX cycle during which the UE actively monitors the Physical Downlink Control Channel (PDCCH) to receive scheduling information and potential downlink transmissions.

[0006] The term “Inactive Time” used hereinafter in the specification refers to the period when the UE is not monitoring the PDCCH and remains in a low-power state until the next On Duration, unless a scheduling event or MAC control message triggers an early wake-up.

[0007] The term “Hybrid Automatic Repeat Request (HARQ) Round-Trip Time (RTT)” used hereinafter in the specification refers to the time interval between an initial transmission and the reception of an acknowledgment (ACK) or negative acknowledgment (NACK), after which the UE may remain awake to receive a retransmission.

[0008] The term “Machine Learning (ML) model” used hereinafter in the specification refers to an artificial intelligence-based model trained using historical network data, UE mobility patterns, and DRX performance metrics to dynamicallyselect an optimal DRX profile based on network conditions and service requirements.

[0009] The term “Block Error Rate (BLER)” used hereinafter in the specification refers to the ratio of the number of erroneous blocks received to the total number of transmitted blocks, which serves as a key metric for evaluating link quality and determining DRX adjustments.

[0010] The term “Modulation and Coding Scheme (MCS) threshold” used hereinafter in the specification refers to a predefined value that indicates whether the channel quality is sufficient for reliable data transmission, influencing DRX profile selection and adjustments.

[0011] The term “On Duration Timer” used hereinafter in the specification refers to a timer that defines the duration at the beginning of a DRX cycle during which the UE actively monitors the Physical Downlink Control Channel (PDCCH) for potential downlink transmissions.

[0012] The term “Off Duration Timer” used hereinafter in the specification refers to a timer that defines the period during which the UE remains in a low-power state and does not monitor the PDCCH after the expiration of the On Duration Timer, unless reactivated by a scheduling request or another trigger event.

[0013] The term “DRX Inactivity Timer” used hereinafter in the specification refers to a timer that determines the duration for which the UE continues monitoring the PDCCH after successfully receiving a downlink or uplink transmission, allowing for continuous reception before entering a DRX sleep state.

[0014] The term “DRX Cycle Lengths” used hereinafter in the specification refers to the periodic duration of DRX operation, which includes both active and inactive phases, and is classified into Short DRX Cycle and Long DRX Cycle. The Short DRX Cycle provides faster reactivation at the cost of higher power consumption, while the Long DRX Cycle extends sleep periods for enhanced power efficiency.

[0015] These definitions are in addition to those expressed in the art.BACKGROUND OF DISCLOSURE

[0016] The following description of related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section be used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of prior art.

[0017] Wireless communication technology has rapidly evolved over the past few decades. The first generation of wireless communication technology was analog technology that offered only voice services. Further, when the second-generation (2G) technology was introduced, text messaging and data services became possible. The 3Gtechnology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth-generation (4G) technology revolutionized wireless communication with efficient data speeds,improved network coverage, and security. Currently, the fifth-generation (5G) technology is being deployed, with even efficient data speeds, low latency, and the ability to connect multiple devices simultaneously. The sixth generation (6G) technology promises to build upon these advancements, pushing the boundaries of wireless communication even further.

[0018] Discontinuous Reception (DRX) is a power-saving mechanism used in cellular networks to reduce the energy consumption of a User Equipment (UE) while maintaining connectivity. The DRX operates by allowing the UE to alternate between active and sleep states based on predefined parameters such as On Duration Timer, Off Duration Timer, DRX Inactivity Timer, and DRX Cycle lengths. When the UE is in a sleep state, DRX the temporarily suspends reception of downlink transmissions from a base station, such as an eNodeB or gNodeB, thereby conserving battery power. However, an overly aggressive DRX configuration can lead to increased latency and degraded user experience, particularly for latencysensitive services. Conversely, an insufficiently optimized DRX configuration may lead to unnecessary power consumption.

[0019] Several prior techniques have been proposed for DRX configuration. In traditional DRX mechanisms, static or semi-static configurations are applied, where DRX parameters are predefined based on generic network conditions and service requirements. The above-mentioned approaches do not account for dynamic variations in network performance, UE mobility, or service-specific demands, leading to suboptimal performance.

[0020] Some DRX adaptation techniques involve rule-based or heuristic methods where DRX parameters are adjusted based on predefined thresholds of network performance metrics such as Signal-to-Noise Ratio (SNR), Channel Quality Indicator (CQI), and Block Error Rate (BLER). However, the above-mentioned techniques rely on fixed thresholding mechanisms that may not effectively capture complex and non-linear relationships between network conditions and optimal DRX settings. For instance, if the SNR drops below a fixed threshold, the DRX parameters may be modified to enhance reliability. Similarly, if the CQI falls below a predefined value, the UE may extend its active time to improve data reception. In cases where the BLER exceeds a set threshold, DRX cycles may be adjusted to ensure better retransmission opportunities. Additionally, some mechanisms consider traffic load-based thresholds, where DRX settings are modified if the number of active users or network congestion surpasses a predefined limit. However, such fixed thresholding mechanisms may not effectively capture complex and non-linear relationships between network conditions and optimal DRX settings, potentially leading to suboptimal power efficiency and performance.

[0021] Therefore, a method and system that can address the shortcomings of existing solutions are needed.OBJECTIVES OF THE PRESENT DISCLOSURE

[0022] Some of the objectives of the present disclosure, which at least one embodiment herein satisfies, are as listed herein below.

[0023] An objective of the present disclosure is to provide a system and a method for an adaptive Discontinuous Reception (DRX) configuration to optimize power consumption and service performance in a network.

[0024] Another objective of the present disclosure is to provide the system and the method for configuring multiple DRX profiles where DRX parameters are dynamically adjusted based on network conditions and feedback from the User Equipment (UE).

[0025] Another objective of this disclosure is to provide the system and the method for evaluating network conditions using a machine learning (ML) model to determine an optimal DRX profile based on predefined performance criteria.

[0026] Another objective of the present disclosure is to provide the system and the method for dynamically updating DRX profiles in response to real-time network conditions to improve efficiency and reliability.

[0027] Yet another objective of the present disclosure is to provide the system and the method for reducing network latency and optimizing energy efficiency by intelligently adjusting DRX parameters based on dynamic conditions.

[0028] Other objectives and advantages of the present disclosure will be more apparent from the following description, which is not intended to limit the scope of the present disclosure.SUMMARY

[0029] In an exemplary embodiment, a method for managing Discontinuous Reception (DRX) configuration of a User Equipment (UE) in a network is disclosed. The method includes receiving, by a processing engine, at least one network condition parameter associated with the UE. The method includes comparing, by the processing engine, the at least one network condition parameter with at least one predefined performance threshold. The method includes determining, by the processing engine, at least one condition state of the UE based on the comparing. The method includes adjusting, by the processing engine, one or more DRX parameters associated with the UE based on the at least one condition state. The method includes configuring, by the processing engine, the UE with the adjusted one or more DRX parameters for at least one DRX operation.

[0030] In some embodiments, the one or more DRX parameters comprises at least one of an On-Duration timer, a DRX Inactivity timer, a Long DRX cycle and a Short DRX cycle.

[0031] In some embodiments, selecting one or more DRX configuration profiles for the UE, wherein each DRX configuration profile comprises a predefined set of values of the one or more DRX parameters, wherein adjusting the one or more DRX parameters comprises selecting the one or more DRX configuration profiles based on the at least one condition state.

[0032] In some embodiments, the at least one network condition parameter comprises a Channel Quality Indicator (CQI) and a Block Error Rate (BLER), and wherein the CQI determines a Modulation and Coding Scheme (MCS) associated with the UE.

[0033] In some embodiments, comparing the at least one network condition parameter with the at least one predefined threshold comprises comparing the MCS with an MCS threshold and comparing the BLER with a BLER threshold.

[0034] In some embodiments, determining the at least one condition state of the UE comprises determining a first condition state when the MCS is greater than or equal to the MCS threshold and the BLER is less than or equal to the BLER threshold and determining a second condition state when the MCS is less than or equal to the MCS threshold and the BLER is greater than or equal to the BLER threshold.

[0035] In some embodiments, adjusting the at least one DRX parameter comprises increasing at least one of the at least one DRX parameter by a predefined incremental step value when the condition state satisfies the first condition state and decreasing at least one of the at least one DRX parameter by a predefined decremental step value when the condition state satisfies the second condition state.

[0036] In some embodiments, a machine learning model is applied to determine the condition state of the UE, wherein the machine learning model is trained using at least one historical network condition information and corresponding DRX parameter configurations.

[0037] In an exemplary embodiment, a system for managing Discontinuous Reception (DRX) configuration of a User Equipment (UE) in a network is disclosed. The system includes a processing engine configured to receive at least one network condition parameter associated with the UE. The processing engine compares the at least one network condition parameter with at least one predefined performance threshold. The processing engine determine at least one condition state of the UE based on the comparing. The processing engine adjusts one or more DRX parameters associated with the UE based on the at least one condition state. The processing engine configures the UE with the adjusted one or more DRX parameters for at least one DRX operation.

[0038] In an exemplary embodiment, a computer program product including a non-transitory computer-readable medium is disclosed. The medium includes instructions that, when executed by one or more processors, cause the one or more processors to perform a method for managing Discontinuous Reception (DRX) configuration of a User Equipment (UE) in a network is disclosed. The method includes receiving, by a processing engine, at least one network condition parameter associated with the UE. The method includes comparing, by the processing engine, the at least one network condition parameter with at least one predefined performance threshold. The method includes determining, by the processing engine, at least one condition state of the UE based on the comparing. The method includes adjusting, by the processing engine, one or more DRX parameters associated with the UE based on the at least one condition state. The method includes configuring, by the processing engine, the UE with the adjusted one or more DRX parameters for at least one DRX operation.

[0039] The foregoing general description of the illustrative embodiments and the following detailed description thereof are merely exemplary aspects of the teachings of this disclosure and are not restrictive.BRIEF DESCRIPTION OF DRAWINGS

[0040] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each component. It will be appreciated by those skilled in the art that disclosure of such drawings includes the disclosure of electrical components, electronic components or circuitry commonly used to implement such components.

[0041] FIG. 1 illustrates an exemplary network architecture of a system for managing Discontinuous Reception (DRX) configuration in a network, in accordance with an embodiment of the present disclosure.

[0042] FIG. 2 illustrates an exemplary block diagram of a system for managing the DRX configuration in the network, in accordance with an embodiment of the present disclosure.

[0043] FIG. 3A illustrates a Discontinuous Reception (DRX) timing flow diagram, in accordance with an embodiment of the present disclosure.

[0044] FIG. 3B illustrates a differentiation between Adaptive and Default DRX configuration profiles and communication flow diagram between a User Equipment (UE) and the eNodeB, in accordance with an embodiment of the present disclosure, in accordance with an embodiment of the present disclosure.

[0045] FIG. 4 illustrates an exemplary flow diagram of a method for managing the DRX configuration in the network, in accordance with embodiments of the present disclosure.

[0046] FIG. 5 illustrates an exemplary computer system in which or with which embodiments of the present disclosure may be implemented

[0047] The foregoing shall be more apparent from the following more detailed description of the disclosure.LIST OF REFERENCE NUMERALS100 - Network architecture102- 1 , 102-2... 102-N - User(s)104-1, 104-2... 104-N - User equipment(s)106 - Network108 - System200 - Block diagram202 - One or more processor(s)204 - Memory206 - Interface(s)208 - Processing Unit210 - Database300 A - Timing flow diagram300B - Communication flow diagram302 -ENODEB400 - Flow diagram500 - Computer system510 - External Storage Device520 - Bus530 - Main Memory540 - Read Only Memory550 - Mass Storage Device560 - Communication Port570 - ProcessorDETAILED DESCRIPTION OF DISCLOSURE

[0048] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter can each be used independently of one another or with any combination of other features. An individual feature may not address all of the problems discussed above or might address only some of the problems discussed above. Some of the problems discussed above might not be fully addressed by any of the features described herein.

[0049] The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.

[0050] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, networks, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments.

[0051] Also, it is noted that individual embodiments may be described as a process which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination can correspond to a return of the function to the calling function or the main function.

[0052] The word “exemplary” and / or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as “exemplary” and / or “demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive in a manner similar to the term “comprising” as an open transition word without precluding any additional or other elements.

[0053] Reference throughout this specification to “one embodiment” or “an embodiment” or “an instance” or “one instance” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present disclosure. Thus, the appearances of the phrases “in one embodiment” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment.Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0054] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and / or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. As used herein, the term “and / or” includes any and all combinations of one or more of the associated listed items.

[0055] Wireless communication technology has rapidly evolved over the past few decades. The first generation of wireless communication technology was analog, offering only voice services. Further, text messaging and data services became possible when the second-generation (2G) technology was introduced. The third generation (3G) technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth generation (4G) technology revolutionized the wireless communication with faster data speeds, improved network coverage, and security. Currently, fifth generation (5G) technology is being deployed, offering significantly faster data speeds, lower latency, and the ability to connect many devices simultaneously. Further, 6G successor to 5G is expected to provide significantly high data speed with reduced latency, which may offer improved connectivity for a vast number of devices concurrently. The capabilities of 6G enable new types of applications and services, such as advanced augmented reality (AR) and virtual reality (VR), holographic communications, and more immersive digital experiences. These advancements represent a significant leap forward from previous generations, enabling enhanced mobile broadband, improved Internet of Things (loT) connectivity, and more efficient use of network resources. The sixth generation (6G) technology promises to build upon these advancements, pushing the boundaries of wireless communication even further. While the 5G technology is still being rolled out globally, research and development into the 6G are rapidly progressing, with the aim of revolutionizing the way of connecting and interacting with technology.

[0056] The present disclosure relates to a system and a method for managing Discontinuous Reception (DRX) configuration in a network. The disclosed invention enables an intelligent and dynamic adjustment of DRX parameters based on network conditions and user equipment (UE) performance feedback. The system utilizes a machine learning (ML) model to determine the most suitable DRX profile for different services and network environments, ensuring efficient power consumption and optimized service performance.

[0057] The various embodiments throughout the disclosure will be explained in more detail with reference to FIGS. 1- 5.

[0058] FIG. 1 illustrates an exemplary network architecture (100) for managing Discontinuous Reception (DRX) configuration in a network (106), in accordance with embodiments of the present disclosure.

[0059] Referring to FIG. 1, the exemplary network architecture (100) may include one or more User Equipments (UEs) (104-1, 104-2... 104-N) associated with one or more users (102-1, 102-2... 102 -N) in an environment. A person of ordinary skill in the art will understand that one or more users (102-1, 102-2... 102-N) may be individually referred to as the user (102) and collectively referred to as the users (102). Similarly, a person of ordinary skill in the art will understand that one or more user equipments (104-1, 104-2... 104-N) may be individually referred to as the user equipment (104) and collectively referred to as the user equipment (104). A person of ordinary skill in the art will appreciate that the terms “computing device(s)” and “user equipment” may be used interchangeably throughout the disclosure. Further, any number of the UEs (104) may be included without departing from the scope of the ongoing description. In an embodiment, each of the user equipment (104) may have a first unique identifier attribute associated therewith. In an embodiment, the first unique identifier attribute may be indicative of Mobile Station International Subscriber Directory Number (MSISDN), International Mobile Equipment Identity (IMEI) number, International Mobile Subscriber Identity (IMSI), Subscriber Permanent Identifier (SUPI) and the like.

[0060] In an embodiment, the UE (104) may include smart devices operating in a smart environment, for example, an Internet of Things (loT) system. In such an embodiment, the UE (104) may include but is not limited to, smartphones, smart watches, smart sensors (e.g., mechanical, thermal, electrical, magnetic, etc.), networked appliances, networked peripheral devices, networked lighting system, communication devices, networked vehicle accessories, networked vehicular devices, smart accessories, tablets, smart television (TV), computers, smart security system, smart home system, other devices for monitoring or interacting with or for the users (102) and / or entities, or any combination thereof. A person of ordinary skill in the art will appreciate that the user equipment (104) may include, but is not limited to, intelligent, multi -sensing, network-connected devices that can integrate seamlessly with each other and / or with a central server or a cloud-computing system or any other device that is network-connected.

[0061] In an embodiment, the UE (104) may include, but is not limited to, a handheld wireless communication device (e.g., a mobile phone, a smartphone, a phablet device, and so on), a wearable computer device (e.g., a head-mounted display computer device, a head-mounted camera device, a wristwatch computer device, and so on), a Global Positioning System (GPS) device, a laptop computer, a tablet computer, or another type of portable computer, a media playing device, a portable gaming system, and / or any other type of computer device with wireless communication capabilities, and the like. In an embodiment, the user equipment (104) may include but is not limited to, any electrical, electronic, electromechanical, or an equipment, or a combination of one or more of the above devicessuch as virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other computing device, the user equipment (104) may include one or more in-built or externally coupled accessories including, but not limited to, a visual aid device such as a camera, an audio aid, a microphone, a keyboard, and input devices for receiving input from the user (102) or the entity such as touchpad, touch-enabled screen, electronic pen, and the like. A person of ordinary skill in the art will appreciate that the user equipment (104) may not be restricted to the mentioned devices and various other devices may be used.

[0062] Referring to FIG. 1, the user equipment (104) may communicate with the integrated RU (108) via the network (106). The UE (104) may be communicatively coupled with the network (106). The communicative coupling comprises receiving, from the UE (104), a connection request by the network (106), sending an acknowledgment of the connection request to the UE (104), and transmitting a plurality of signals in response to the connection request. In an embodiment, the network (106) may include at least one of a Fourth Generation (4G) network, a Fifth Generation (5G) network, a Sixth Generation (6G) network, or the like. The network (106) may enable the user equipment (104) to communicate with other devices in the network architecture (100) and / or with the system (108). The network (106) may include a wireless card or another transceiver connection to facilitate this communication. In another embodiment, the network (106) may be implemented as or include any of a variety of different communication technologies such as a wide area network (WAN), a local area network (LAN), a wireless network, a mobile network, a Virtual Private Network (VPN), the Internet, the Public Switched Telephone Network (PSTN), or the like.

[0063] In an embodiment, the network (106) may include, by way of example but not limitation, at least a portion of one or more networks having one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process, or a combination thereof, etc. one or more messages, packets, signals, waves, voltage or current levels, some combination thereof, or so forth. The network (106) may also include, by way of example but not limitation, one or more of a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a Public Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, or some combination thereof.

[0064] In an embodiment, the UE (104) is communicatively coupled with the network (106). The network (106) may receive a connection request from the UE (104). The network (106) may send an acknowledgment of the connection request to the UE (104). The UE (104) may transmit a plurality of signals in response to the connection request.

[0065] Although FIG. 1 shows exemplary components of the network architecture (100), in other embodiments, the network architecture (100) mayinclude fewer components, different components, differently arranged components, or additional functional components than depicted in FIG. 1. Additionally, or alternatively, one or more components of the network architecture (100) may perform functions described as being performed by one or more other components of the network architecture (100).

[0066] FIG. 2 illustrates an exemplary block diagram (200) of the system (108) for managing Discontinuous Reception (DRX) configuration in a network (106), in accordance with an embodiment of the present disclosure.

[0067] In an embodiment, the system (108) is implemented within a base station of the network (106). The base station may comprise a Next Generation Node B (gNB) or equivalent radio access network node. The system (108) comprises a processor (202), a memory (204), an interface (206), a processing engine (208) and a database (210).

[0068] Referring to FIG. 2, in an embodiment, the system (108) may include one or more processor(s) (202). The one or more processor(s) (202) may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing engines, logic circuitries, and / or devices that process data based on operational instructions. Among other capabilities, the one or more processor(s) (202) may be configured to fetch and execute computer-readable instructions stored in the memory (204) of the system (108). The memory (204) may be configured to store one or more computer-readable instructions or routines in a non-transitory computer readable storage medium, which may be fetched and executed to create or share data packets over a network service. The memory (204) may comprise any non-transitory storage device including, for example, volatile memory such as random-access memory (RAM), or non-volatile memory such as erasable programmable read-only memory (EPROM), flash memory, and the like.

[0069] In an embodiment, the system (108) may include an interface(s) (206). The interface(s) (206) may comprise a variety of interfaces, for example, interfaces for data input and output devices (VO), storage devices, and the like. The interface(s) (206) may facilitate communication through the system (108). The interface(s) (206) may also provide a communication pathway for one or more components of the system (108). Examples of such components include, but are not limited to, the processing engine (208) and the database (210). The processing engine (208) executes instructions stored in the memory (204) to perform the DRX management functions described herein. The interface (206) enables communication between the processing engine (208), the UE (104), and other components of the network (106). The database (210) stores predefined DRX configuration profiles, predefined performance thresholds, historical network condition data, and trained Machine Learning (ML) model parameters.

[0070] In an embodiment, the processing engine (208) is configured to configure a plurality of service-based adaptive Discontinuous Reception (DRX) profiles for the user equipment (104), wherein each DRX profile comprises a set ofDRX parameters. The plurality of DRX profiles is designed to adaptively adjust DRX settings based on real-time network conditions and service-specific requirements. The processing engine (208) retrieves predefined DRX profiles stored in the database (210) and applies a selected DRX profile to the user equipment (104) based on service type, mobility status, and network feedback. The service type of the UE (104) may include Fixed Wireless Access (FWA), Voice over New Radio (VoNR), Vehicle-to-Network Radio (VINR), and Reduced Capability (RedCap) devices.

[0071] In an embodiment, the DRX configuration profile (or “DRX Profile”) represent the predefined set of values assigned to the DRX parameters that control DRX operation of the UE (104). Each DRX configuration profile may define specific values for parameters such as the On Duration Timer, DRX Inactivity Timer, Long DRX Cycle, and Short DRX Cycle. For example, a first DRX profile configured for low-latency services may include an On Duration Timer of 10 ms, a DRX Inactivity Timer of 20 ms, a Long DRX Cycle of 40 ms, and a Short DRX Cycle of 20 ms. A second DRX profile configured for powersaving operation may include an On Duration Timer of 5 ms, a DRX Inactivity Timer of 100 ms, a Long DRX Cycle of 160 ms, and a Short DRX Cycle of 40 ms. A third DRX profile configured for balanced performance may include an On Duration Timer of 8 ms, a DRX Inactivity Timer of 40 ms, a Long DRX Cycle of 80 ms, and a Short DRX Cycle of 30 ms. The processing engine (208) selects one of the DRX configuration profiles based on the determined condition state of the UE (104), thereby applying the corresponding DRX parameter values.

[0072] In an embodiment, the processing engine (208) is configured to receive at least one network condition parameter associated with the UE (104). The one or more network condition parameters may include at least one of a Channel Quality Indicator (CQI), a Block Error Rate (BLER), a Signal-to-Noise Ratio (SNR), and a Reference Signal Received Power (RSRP). The processing engine (208) continuously monitors real-time network feedback received through the interface (206) and stores the received parameters in the memory (204) for evaluation. The received parameters are used to assess the current state of the wireless channel and the quality of communication between the user equipment (104) and the network (106).

[0073] In an embodiment, the processing engine (208) is configured to compare the received one or more network condition parameters with at least one predefined performance threshold retrieved from the database (210). The predefined performance thresholds are a set of predetermined values set by the network operator or system to evaluate network conditions. The predefined performance thresholds define the acceptable range for network condition parameters and serve as decision points for adjusting DRX configurations. The predefined performance thresholds serve as benchmarks for determining whether adjustments to DRX parameters are required to optimize network performance and power efficiency. One example of a predefined performance threshold is theModulation and Coding Scheme (MCS) Threshold, which represents the minimum Channel Quality Indicator (CQI) value required to maintain an efficient modulation and coding scheme. For instance, an MCS threshold may be set at CQI > 10, ensuring that higher-order modulation schemes such as 64-QAM are utilized only when the signal conditions permit reliable data transmission. Another example is the Block Error Rate (BLER) Threshold, which defines the maximum acceptable BLER percentage before DRX parameters require adjustment. A BLER threshold of BLER < 10% ensures that if the BLER exceeds this value, retransmissions increase, prompting a potential modification of DRX settings to improve link reliability and reduce power consumption. The Signal-to-Noise Ratio (SNR) Threshold is another predefined performance parameter that specifies the minimum SNR level required for efficient communication. An SNR threshold of SNR > -5 dB ensures that DRX parameters are adjusted dynamically if signal conditions deteriorate beyond an acceptable level. Maintaining an optimal SNR helps in reducing transmission errors and improving data throughput. The Reference Signal Received Power (RSRP) Threshold assesses signal strength and determines whether adjustments to DRX configurations are required. An RSRP threshold of RSRP > -100 dBm ensures that the UE (104) maintains a stable connection. If the RSRP value falls below this threshold, the DRX parameters may be adjusted to enhance connectivity and ensure efficient power management. The processing engine (208) retrieves the predefined performance threshold values from the database (210) and evaluates to determine whether the current network conditions meet the predefined performance criteria. The processing engine (208) assesses whether adjustments to the DRX parameters are required to optimize power consumption and network efficiency. The comparison determines whether current channel conditions satisfy the predefined performance criteria.

[0074] In an embodiment, the processing engine (208) is configured to determine at least one condition state of the UE (104) based on the comparison of the network condition parameters with the predefined thresholds. A first condition state may be determined when the MCS is greater than or equal to the MCS threshold and the BLER is less than or equal to the BLER threshold, indicating favorable channel conditions. A second condition state may be determined when the MCS is less than or equal to the MCS threshold and the BLER is greater than or equal to the BLER threshold, indicating degraded channel conditions. The determined condition state represents the operational status of the UE (104) in relation to current network quality.

[0075] In an embodiment, the processing engine (208) is configured to adjust one or more DRX parameters associated with the UE (104) based on the determined condition state. The one or more DRX parameters comprise at least one timer parameter or cycle parameter that controls DRX operation of the UE (104). The one or more DRX parameters comprise at least one timer parameter or cycle parameter that controls DRX operation of the UE (104). The DRX parameters may include the On Duration Timer, which defines the duration during which the UE(104) remains active at the beginning of a DRX cycle to monitor the Physical Downlink Control Channel (PDCCH), an Off Duration Timer, which represents the period during which the UE (104) may remain inactive to conserve power, a DRX Inactivity Timer, which determines how long the UE (104) remains active after receiving data before entering DRX mode, a Short DRX cycle, which defines a shorter periodic wake-up interval for the UE (104), a Long DRX cycle, which defines a longer periodic wake-up interval used for extended power saving; a DRX Retransmission Timer, which specifies the duration the UE (104) waits for a potential retransmission before transitioning to DRX mode, and a DRX ShortCycleTimer, which determines how long the UE (104) follows the short DRX cycle before switching to the long DRX cycle. Adjustment of these parameters controls the active and sleep behavior of the UE (104) to optimize power consumption and network performance.

[0076] In an embodiment, the processing engine (208) is configured to modify the one or more DRX parameters using predefined incremental and decremental step values. The incremental parameters Istep ON Duration Timer, Istep DRX Inactivity Timer, and Istep Off Duration Timer represent predefined step values used to increase the respective DRX timers when network conditions require the UE (104) to remain active for longer periods. Similarly, the decremental parameters Dstep ON Duration Timer, Dstep DRX Inactivity Timer, and Dstep Off Duration Timer represent predefined step values used to decrease the respective DRX timers when the UE (104) can enter sleep mode sooner to improve power efficiency. These step parameters enable controlled and gradual adjustment of DRX timer values based on the determined condition state. When the condition state corresponds to degraded channel conditions, the processing engine (208) may increase the DRX Inactivity Timer and adjust DRX cycle lengths to enhance reliability and maintain service continuity.

[0077] In an embodiment, the processing engine (208) is configured to configure one or more DRX configuration profiles for the UE (104), wherein each DRX configuration profile comprises a predefined set of DRX parameter values corresponding to the one or more DRX parameters. The DRX configuration profiles are stored in the database (210) and may be retrieved based on service type, mobility status, and network feedback. Service types may include Fixed Wireless Access (FWA), Voice over New Radio (VoNR), Vehicle-to-Network Radio (VINR), and Reduced Capability (RedCap) devices. The selection of a DRX configuration profile allows rapid adjustment of DRX behavior by applying a predefined parameter set.

[0078] In an embodiment, the processing engine (208) is configured to select one of the configured DRX configuration profiles based on the determined condition state. The selected DRX profile defines the DRX behavior of the UE (104) in terms of active duration, inactivity duration, and DRX cycle lengths. The selected DRX profile is applied to the UE (104) through the interface (206), thereby configuring the UE (104) for subsequent DRX operation.

[0079] In an embodiment, the processing engine (208) is configured to apply a Machine Learning (ML) model to determine the condition state of the UE (104) or to select an appropriate DRX configuration profile. The ML model is trained using historical network condition information, including MCS values, BLER values, throughput data, latency measurements, and carried traffic patterns. The processing engine (208) continuously stores performance metrics in the database (210) and uses such data to iteratively train and refine the ML model. The ML model evaluates multiple DRX configuration possibilities and identifies the most suitable configuration satisfying predefined performance thresholds for the specific service type of the UE (104).

[0080] In an embodiment, the processing engine (208) is configured to continuously monitor subsequent network condition parameters and performance feedback after applying a DRX configuration profile. Based on changes in network conditions or UE (104) performance, the processing engine (208) dynamically repeats the steps of receiving parameters, comparing with thresholds, determining condition state, adjusting DRX parameters, and selecting updated DRX profiles to ensure optimal operation.

[0081] In an embodiment, the processing engine (208) is configured to revert the UE (104) to a baseline DRX configuration when the received network condition parameters fail to satisfy predefined performance thresholds. The baseline DRX configuration comprises default values for the one or more DRX parameters, including standard On Duration Timer, Off Duration Timer, DRX Inactivity Timer, and DRX cycle lengths. The baseline configuration ensures service continuity and prevents excessive degradation in network performance.

[0082] In an embodiment, the processing engine (208) is configured to apply different DRX configuration profiles to different UEs (104) based on mobility status, traffic patterns, and service requirements. The processing engine (208) differentiates DRX behavior for stationary, low-mobility, and high-mobility UEs (104) to optimize both power efficiency and network throughput.

[0083] In an embodiment, the processing engine (208) is configured to store updated DRX configuration profiles and corresponding performance metrics in the database (210) for future reference and ML model training. The stored data enables iterative learning and continuous refinement of DRX parameter optimization across the network (106).

[0084] In an embodiment, the processing engine (208) is configured to autonomously and dynamically modify DRX settings for each UE (104) using an ML-based algorithm, thereby improving power efficiency, reducing unnecessary wake-up instances, and ensuring optimal network performance tailored to real-time channel conditions and service-specific requirements. The ML-based algorithm dynamically modifies the DRX settings of each service-specific profile based on the channel quality reported by the UE (104). The Modulation and Coding Scheme (MCS) is assigned to each UE (104) by the scheduler, based on the Channel Quality Indicator (CQI) reported by the UE (104). The MCS reflects the priority assignedto the UE (104) during the last scheduling instance and, consequently, the relative channel quality of the UE (104). The algorithm employs a channel quality threshold, MCS thresh, to determine whether to increase or decrease different DRX timer values. The algorithm utilizes a Block Error Rate (BLER) threshold, BLER thresh, to dynamically adjust DRX settings. The BLER thresh parameter helps identify scenarios where the UE (104) is experiencing a highly favorable channel condition with minimal block errors, ensuring an optimal Hybrid Automatic Repeat Request (HARQ) acknowledgment (ACK) and negative acknowledgment (NACK) ratio.

[0085] To enhance flexibility, the algorithm introduces new incremental and decremental parameters for the On Duration Timer, the Off Duration Timer, and the DRX Inactivity Timer. These parameters can be defined by a network operator as follows:• Incremental parameters:a) Istep ON Duration Timerb) Istep DRX Inactivity Timerc) Istep Off Duration Timer• Decremental parameters:a) Dstep ON Duration Timerb) Dstep DRX Inactivity Timerc) Dstep Off Duration Timer

[0086] The network (106) continuously stores key information, such as MCS and BLER, for all UEs (104) and shares the data with the processing engine (208). The processing engine (208) trains the Machine Learning model using multiple features, including MCS, throughput, latency, carried traffic, and BLER. The trained Machine Learning model derives the most suitable DRX configuration for different UEs (104) in the network, expressed in terms of the following parameters• On duration Timer: The duration at the beginning of a DRX cycle during which the UE (104) remains active to monitor the Physical Downlink Control Channel (PDCCH).• Drx Inactivity timer: The duration after a PDCCH occasion in which the PDCCH indicates a new uplink (UL), downlink (DL), or sidelink (SL) transmission for the Medium Access Control (MAC) entity.• Short Drx cycle: The Short DRX cycle duration, which is followed if configured, before switching to the Long DRX cycle• Long Drx Cycle: The Long DRX cycle duration that the UE (104) follows after the expiration of the Short DRX cycle.• Drx-Retransmission time: The duration the UE (104) waits for a DL retransmission before transitioning into the DRX mode.• Drx ShortCycleTimer: The timer controlling how long the UE (104) follows the Short DRX cycle before transitioning to the Long DRX cycle.

[0087] The implementation of the Machine Learning-based DRX configuration mechanism improves power efficiency, reduces unnecessary wakeup instances, and ensures optimal network performance tailored to the specific conditions of the UE (104).

[0088] FIG. 3A illustrates a Discontinuous Reception (DRX) timing flow diagram, in accordance with an embodiment of the present disclosure. FIG. 3A is explained in conjunction with the FIG. 1 and FIG. 2. to provide a comprehensive understanding of DRX functionality.

[0089] The DRX timing flow diagram (300 A) represents the DRX cycle, which includes one or more DRX configuration parameters. The one or more DRX configuration parameters include:• Short DRX On-time: Duration during which the UE (104) actively monitors the Physical Downlink Control Channel (PDCCH) in a short DRX cycle.• Long DRX On-time: Duration during which the UE (104) monitors PDCCH in a long DRX cycle.• Short DRX Cycle: Frequent sleep / wake pattern to balance power efficiency and network responsiveness.• Long DRX Cycle: Less frequent sleep / wake pattern to enhance power savings.• DRX ShortCycleTimer: Duration for which the UE (104) remains in the short DRX cycle before transitioning to the long DRX cycle.

[0090] The System Frame Number (SFN) is a 10-bit counter that identifies the current radio frame in a sequence of frames transmitted over the network. Each radio frame consists of 10 subframes (0-9), and subframes are the fundamental time units in LTE scheduling. The subframes in FIG. 3 A range from 0 to 9 within each SFN value, showing how time progresses in sequential DRX cycles.

[0091] PDCCH (DCI): The Physical Downlink Control Channel (PDCCH) is checked by the UE (104) for downlink scheduling or uplink grants. In FIG. 3 A, shaded blocks indicate active monitoring periods.

[0092] DRX Inactivity Timer defines the time period after the last successfully received data packet during which the UE (104) remains active before transitioning into DRX mode. If no further data is received within this time, the UE enters a low-power sleep state. In FIG. 3A, the DRX inactivity timer is shown as an extended shaded area, indicating the duration before the DRX cycle starts.

[0093] On-Duration Timer represents the duration for which the UE (104) stays awake at the beginning of each DRX cycle to monitor for incoming downlink data. If no scheduling assignment is received during this period, the UE (104) returns to sleep mode. In FIG. 3A, the on-duration timer is indicated with cross-hatched blocks within each DRX cycle. The on-duration timer occurs at specific intervals corresponding to short DRX on-time and long DRX on-time.

[0094] The System Frame Number (SFN) represents the radio frame index used by the network (106) to maintain time synchronization between the basestation and the UE (104). Each SFN corresponds to a radio frame of 10 milliseconds, and each radio frame contains 10 subframes indexed from 0 to 9. The SFN value increments sequentially and wraps around after reaching its maximum value. In the context of Discontinuous Reception (DRX), the SFN values are used to determine the precise timing of DRX cycles, including when the UE wakes up to monitor the PDCCH and when the UE transitions into sleep mode to conserve power. The relation of SFN values (0, 1,2,3) to DRX cycles is depicted as follows:• SFN Values (0, 1, 2, 3): Represent different radio frames in the sequence, with each frame comprising 10 subframes.• Subframe Indexing (0-9): Each SFN consists of 10 subframes, which define when the UE (104) monitors PDCCH and when it enters sleep mode.• Short DRX Cycle: The short DRX on-time occurs within a short DRX cycle (e.g., within SFN = 0, subframe 2-3, and SFN = 3, subframe 5-6).• Long DRX Cycle: After the DRX ShortCycleTimer expires, the UE enters the long DRX cycle (e.g., spanning SFN = 1 to SFN = 2).• DRX Start Offset (0): Indicates that the DRX cycle starts at SFN 0, subframe 0, without any delay.• DRX Short Cycle Restart (SFN 3, subframe 5-6): The FIG. 3A illustrates the restart of the short DRX cycle if new data is received, showing how DRX dynamically adapts to network conditions.

[0095] The DRX timing diagram further illustrates how one or more DRX parameters impact power consumption and network latency of the UE (104). Fig.3 A visually differentiates between short and long DRX cycles and depicts the restart mechanism of the short DRX cycle based on network conditions.

[0096] FIG. 3B illustrates a differentiation between Adaptive and Default DRX Profiles and communication flow diagram between the User Equipment (UE) (104) and the ENODEB (302), in accordance with an embodiment of the present disclosure. FIG. 3 A is explained in conjunction with the FIG. 1, FIG. 2 and FIG.3A

[0097] FIG. 3B differentiates between Adaptive DRX Profiles and Default DRX Profiles. The Adaptive DRX Profiles are dynamically adjusted based on one or more network conditions, whereas the Default DRX Profiles follow predefined DRX cycles. The one or more DRX profiles are categorized based on one or more service requirements, including:• DRX Profile 1: Delay -tolerant services.• DRX Profile 2: Different services.• DRX Profile n: Real-time services.

[0098] The categorization of the one or more DRX profiles ensures servicespecific DRX optimization, balancing power efficiency and network responsiveness. The interaction between the UE (104) and the ENODEB (302) is depicted, illustrating how one or more network metrics such as the Channel QualityIndicator (CQI) and the Block Error Rate (BLER) are utilized to dynamically refine one or more DRX profiles.

[0099] Further FIG. 3B illustrates the interaction between the UE (104) and the ENODEB (302), outlining the communication flow involved in DRX configuration and data exchange. The ENODEB (302) is configured to assign one or more DRX profiles based on one or more network conditions. The system (108) dynamically optimizes one or more DRX parameters by continuously exchanging CQI and BLER values between the UE (104) and the ENODEB (302). The Default DRX Profiles are a fallback mechanism when Adaptive DRX Profiles do not meet performance requirements.Conditions and Configurations:For Delay-Tolerant Data Services:• When the Channel Quality is high (MCS is greater than MCSthresh), and BLER is good enough (i.e., calculated BLER is below BLERthres), it implies that the UE (104) is receiving good service overall while experiencing good channel quality. Hence, the DRX Inactivity Timer is decreased to enable the UE (104) to go to sleep sooner. The On-Duration Timer is increased slightly to improve the chances of the UE getting scheduled. The Off-Duration Time (Long DRX Cycle - On-Duration Time) is increased to save more energy. The Short DRX cycle can be deactivated if already activated.o If MCS >= MCSthresh and DLBLER <= BLERthres■ DRX Inactivity Timer = DRX Inactivity Timer - Dstep DRX Inactivity Timer■ On-Duration Timer = On-Duration Timer + Istep ON Duration Timer■ Long DRX Cycle = Long DRX Cycle + Istep Off Duration Time• When the Channel Quality is low (MCS is less than the threshold), and BLER is not good enough (i.e., calculated BLER is above BLERthres), the DRX Inactivity Timer and the On-Duration Timer are both increased to improve the chances of scheduling. The Off-Duration Time is decreased so that the UE (104) sleeps for a shorter duration. The Short DRX cycle can be activated if deactivated already.o If MCS <= MCSthresh and DLBLER >= BLERthres■ DRX Inactivity Timer = DRX Inactivity Timer + Istep DRX Inactivity Timer■ On-Duration Timer = On-Duration Timer + Istep ON Duration Timer■ Long DRX Cycle = Long DRX Cycle - Dstep Off Duration Time• When the Channel Quality is high (MCS is greater than MCSthresh), and BLER is not good enough (i.e., calculated BLER is above BLERthres), itimplies that the UE (104) is receiving good quality, but high BLER is the limiting factor in the services. Then the current values of the DRX Inactivity Timer and Off-Duration Time are maintained so that the chances of sleeping remain the same. However, the On-Duration Timer is increased to improve the chances of scheduling. The Short DRX cycle can be activated if deactivated already.o If MCS >= MCSthresh and DLBLER >= BLERthres■ On-Duration Timer = On-Duration Timer + Istep ON Duration Timer• When the Channel Quality is low (MCS is less than the threshold), and BLER is good enough (i.e., calculated BLER is below BLERthres), then the DRX Inactivity Timer and the On-Duration Timer are both decreased to improve the chances of sleeping. The Off-Duration Time is increased so that the UE (104) sleeps for a longer time. The Short DRX cycle can be deactivated if activated already.o If MCS <= MCSthresh and DLBLER <= BLERthres■ DRX Inactivity Timer = DRX Inactivity Timer - Dstep DRX Inactivity Timer■ On-Duration Timer = On-Duration Timer - Dstep ON Duration Timer■ Long DRX Cycle = Long DRX Cycle + Istep Off Duration TimeForNon-Delay Tolerant Services (e.g„ VoLTE and Video):• When the Channel Quality is high (MCS is greater than MCSthresh), and BLER is good enough (i.e., calculated BLER is below BLERthres), it implies that the UE (104) is receiving good service overall while experiencing good channel quality. Hence, the DRX Inactivity Timer is decreased. This will enable the UE (104) to go to sleep sooner. The On- Duration Timer is increased slightly to improve the chances of the UE (104) getting scheduled. The Off-Duration Time (Long DRX Cycle - On- Duration Time) is increased to save more energy. The Short DRX cycle can be deactivated if already activated.o If MCS >= MCSthresh and DLBLER <= BLERthres■ DRX Inactivity Timer = DRX Inactivity Timer - Dstep DRX Inactivity Timer■ On-Duration Timer = On-Duration Timer + Istep ON Duration Timer■ Long DRX Cycle = Long DRX Cycle + Istep Off Duration Time• When the Channel Quality is low (MCS is lower than the threshold), and BLER is not good enough (i.e., calculated BLER is above BLERthres), the DRX Inactivity Timer is increased to reduce the chances of sleeping. The Off-Duration Time is decreased so that the UE (104) sleeps for a shortertime. The On-Duration Time remains unchanged or as specified by servicespecific settings. The Short DRX cycle can be activated if deactivated already.o If MCS <= MCSthresh and DLBLER >= BLERthres■ DRX Inactivity Timer = DRX Inactivity Timer + Istep DRX Inactivity Timer■ Long DRX Cycle = Long DRX Cycle - Dstep Off Duration TimeFor Real-Time Services:• When the Channel Quality is low and BLER is within acceptable limits, the system (108) maintains a short DRX cycle to ensure low latency.• When the Channel Quality is high and BLER is below BLERthres, the system (108) allows more aggressive DRX parameters to optimize energy savings without compromising latency.For Adaptive DRX Mechanisms:• When CQI degrades, the system (108) dynamically adjusts DRX profiles to prioritize reliability.• When CQI improves, the system (108) shifts to power-efficient DRX settings while maintaining service continuity.

[0100] In an embodiment, FIG. 3B further suggests the integration of machine learning (ML)-based DRX optimization. The one or more Adaptive DRX Profiles dynamically adjust based on ML-driven insights that analyze CQI and BLER trends. An ML model is utilized to learn from historical network performance data and predict optimal DRX parameters for different services. The ML-based approach ensures an intelligent and adaptive power-saving mechanism tailored to real-time network conditions. Additionally, the presence of Default DRX Profiles provides a safeguard mechanism, reverting to predefined settings when ML-based adaptations fail to enhance performance. For example, one or more delay-tolerant services are assigned longer DRX cycles to maximize energy savings, whereas one or more real-time services utilize shorter DRX cycles to maintain low latency. The one or more DRX configuration mechanisms ensure an optimal balance between power efficiency and service quality. The communication flow between the UE (104) and the ENODEB (302) demonstrates how one or more network conditions are continuously assessed to refine one or more DRX profiles dynamically.

[0101] In an embodiment, FIG. 3B provides a visual representation of one or more DRX decision-making processes by showcasing one or more key network parameters, one or more service-based DRX differentiations, and one or more realtime DRX adaptations. The presence of CQI and BLER as core decision-making factors reinforces their role in determining one or more optimal DRX cycles.

[0102] FIG. 4 illustrates an exemplary flow diagram of a method for managing the DRX configuration of the User Equipment (UE) (104) in the network, in accordance with embodiments of the present disclosure. The method is disclosedto implement the system (108). The method is explained in conjunction with FIGS.1, 2, 3 A and 3B.

[0103] At step (402), the method (400) includes receiving, by the processing engine (208), at least one network condition parameter associated with the UE (104) operating within the network (106). In an embodiment, the processing engine (208) receives the network condition parameter from the UE (104) through the interface of the network node. The network condition parameters may include at least one of the Channel Quality Indicator (CQI), the Block Error Rate (BLER), the Signal-to-Noise Ratio (SNR), and the Reference Signal Received Power (RSRP). The processing engine (208) monitors real-time communication feedback from the UE (104) and stores the received parameters in memory for further evaluation. The received parameters collectively represent the quality of the radio link and communication performance between the UE (104) and the network (106).

[0104] At step (404), the method (400) includes comparing, by the processing engine (208), the at least one network condition parameter with at least one predefined performance threshold. The predefined performance thresholds represent benchmark values configured within the network (106) to determine acceptable communication conditions. In an embodiment, the predefined performance thresholds include the MCS threshold corresponding to a minimum CQI value required for efficient modulation and coding operation, and the BLER threshold corresponding to a maximum tolerable block error rate. Additional thresholds such as the SNR threshold and the RSRP threshold may also be used. The processing engine (208) retrieves the predefined threshold values from the database and evaluates whether the received network condition parameters satisfy the predefined performance criteria.

[0105] At step (406), the method (400) includes determining, by the processing engine (208), at least one condition state of the UE (104) based on the comparison performed at step (404). In an embodiment, the processing engine (208) determines the first condition state when the MCS associated with the UE (104) is greater than or equal to the MCS threshold and the BLER is less than or equal to the BLER threshold, indicating favorable channel conditions. The processing engine (208) determines the second condition state when the MCS is less than or equal to the MCS threshold and the BLER is greater than or equal to the BLER threshold, indicating degraded communication conditions. The condition state represents the current operational state of the UE (104) relative to the communication quality of the network (106).

[0106] At step (408), the method (400) includes adjusting, by the processing engine (208), one or more DRX parameters associated with the UE (104) based on the determined condition state. The one or more DRX parameters comprise timer parameters or cycle parameters that control DRX operation of the UE (104). In an embodiment, the DRX parameters include the On Duration Timer, the Off Duration Timer, the DRX Inactivity Timer, the Short DRX Cycle, and the Long DRX Cycle. The DRX configuration prevents the UE (104) from continuously monitoring thePhysical Downlink Control Channel (PDCCH) during every Transmission Time Interval. Instead, the UE (104) monitors the PDCCH only during specific intervals configured through the DRX parameters.

[0107] The method (400) further includes modifying the DRX parameters according to the determined condition state using predefined incremental and decremental step values. When the condition state corresponds to favorable channel conditions, the processing engine (208) increases certain DRX parameters such as the On Duration Timer and decreases other parameters such as the DRX Inactivity Timer to optimize scheduling opportunities while maintaining power efficiency. When the condition state corresponds to degraded channel conditions, the processing engine (208) increases the DRX Inactivity Timer and adjusts DRX cycle durations to improve communication reliability and maintain service continuity. The step values used for such adjustments may include incremental parameters such as Istep ON Duration Timer, Istep DRX Inactivity Timer, and Istep Off Duration Timer, and decremental parameters such as Dstep ON Duration Timer, Dstep DRX Inactivity Timer, and Dstep Off Duration Timer.

[0108] The method (400) may further include configuring one or more DRX configuration profiles for the UE (104). Each DRX configuration profile comprises a predefined set of the DRX parameters that define the DRX behavior of the UE (104). The processing engine (208) stores the DRX configuration profiles in memory or the database and selects one of the DRX configuration profiles based on the determined condition state. The selected DRX configuration profile determines the active and inactive monitoring periods of the UE (104), thereby optimizing power consumption and communication performance.

[0109] The method (400) may additionally include applying the Machine Learning (ML) model to determine the condition state of the UE (104) or to select the DRX configuration profile corresponding to the UE (104). The ML model is trained using historical network condition information, UE mobility patterns, throughput data, latency measurements, and previous DRX profile performance metrics. The ML model evaluates different DRX configurations and determines the DRX profile that satisfies the predefined performance thresholds for the service type associated with the UE (104). The service type may include Fixed Wireless Access (FWA), Voice over New Radio (VoNR), Video Interactive New Radio (VINR), and Reduced Capability (RedCap) devices.

[0110] At step (410), the method (400) includes configuring, by the processing engine (208), the UE (104) with the adjusted DRX parameters for subsequent DRX operation. The processing engine (208) transmits configuration instructions to the UE (104) so that the UE (104) operates according to the selected DRX parameters or the selected DRX configuration profile. When DRX is configured and the UE (104) is in the active state, the UE monitors the current subframe to receive packets from the base station and continues monitoring the PDCCH until the On Duration expires. If the UE (104) successfully decodes aPDCCH transmission during the On Duration, the UE (104) initiates the DRX Inactivity Timer and remains active to receive further data.

[0111] The method (400) may further include monitoring subsequent network conditions and performance feedback of the UE (104) after applying the DRX configuration. The processing engine (208) continuously evaluates updated network condition parameters and dynamically repeats the steps of receiving the network condition parameters, comparing them with predefined performance thresholds, determining the condition state, adjusting the DRX parameters, and reconfiguring the DRX profile in response to changes in network conditions.

[0112] The method (400) may additionally include applying different DRX configuration profiles to different UEs (104) based on mobility status, traffic patterns, and service requirements. For example, stationary UEs may be assigned longer DRX cycles to maximize power savings, whereas highly mobile UEs may be assigned shorter DRX cycles to ensure reliable connectivity and reduced communication delay.

[0113] The method (400) may further include reverting the UE (104) to the baseline DRX configuration if the received network condition parameters fail to satisfy the predefined performance thresholds. The baseline DRX configuration includes standard values of the DRX parameters and ensures continuity of service while maintaining acceptable power efficiency.

[0114] The method (400) may additionally include implementing short DRX cycles and long DRX cycles depending on the DRX configuration. When the short DRX cycle is configured, the UE (104) follows the short DRX cycle and initiates the DRX Short Cycle Timer. After expiration of the Short Cycle Timer, the UE (104) transitions to the long DRX cycle. When the short DRX cycle is not configured, the UE (104) directly follows the long DRX cycle for subsequent DRX operation.

[0115] FIG. 5 illustrates a computer system (500) in which or with which the embodiments of the present disclosure may be implemented.

[0116] As shown in FIG. 5, the computer system (500) may include an external storage device (510), a bus (520), a main memory (530), a read-only memory (540), a mass storage device (550), a communication port(s) (560), and a processor (570). A person skilled in the art will appreciate that the computer system (500) may include more than one processor and communication ports. The processor (570) may include various modules associated with embodiments of the present disclosure. The communication port(s) (560) may be any of an RS-232 port for use with a modem -based dialup connection, a 10 / 100 Ethernet port, a Gigabit or 10 Gigabit port using copper or fiber, a serial port, a parallel port, or other existing or future ports. The communication ports(s) (560) may be chosen depending on a network, such as a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system (500) connects.

[0117] In an embodiment, the main memory (530) may be Random Access Memory (RAM), or any other dynamic storage device commonly known in the art.The read-only memory (540) may be any static storage device(s) e.g., but not limited to, a Programmable Read Only Memory (PROM) chip for storing static information e.g., start-up or basic input / output system (BIOS) instructions for the processor (570). The mass storage device (550) may be any current or future mass storage solution, which can be used to store information and / or instructions. Exemplary mass storage solutions include, but are not limited to, Parallel Advanced Technology Attachment (PATA) or Serial Advanced Technology Attachment (SATA) hard disk drives or solid-state drives (internal or external, e.g., having Universal Serial Bus (USB) and / or Firewire interfaces).

[0118] In an embodiment, the bus (520) may communicatively couple the processor(s) (570) with the other memory, storage, and communication blocks. The bus (520) may be, e.g. a Peripheral Component Interconnect PCI) / PCI Extended (PCI-X) bus, Small Computer System Interface (SCSI), Universal Serial Bus (USB), or the like, for connecting expansion cards, drives, and other subsystems as well as other buses, such a front side bus (FSB), which connects the processor (570) to the computer system (500).

[0119] In another embodiment, operator, and administrative interfaces, e.g., a display, keyboard, and cursor control device may also be coupled to the bus (520) to support direct operator interaction with the computer system (500). Other operator and administrative interfaces can be provided through network connections connected through the communication port(s) (560). Components described above are meant only to exemplify various possibilities. In no way should the aforementioned exemplary computer system (500) limit the scope of the present disclosure.

[0120] In an exemplary embodiment, a computer program product comprising a non-transitory computer-readable medium is disclosed. The medium includes instructions that, when executed by one or more processors, cause the one or more processors to execute a method for managing Discontinuous Reception (DRX) configuration of a User Equipment (UE) in a network is disclosed. The method includes receiving, by a processing engine, at least one network condition parameter associated with the UE. The method includes comparing, by the processing engine, the at least one network condition parameter with at least one predefined performance threshold. The method includes determining, by the processing engine, at least one condition state of the UE based on the comparing. The method includes adjusting, by the processing engine, one or more DRX parameters associated with the UE based on the at least one condition state. The method includes configuring, by the processing engine, the UE with the adjusted one or more DRX parameters for at least one DRX operation.

[0121] While considerable emphasis has been placed herein on the preferred embodiments, it will be appreciated that many embodiments can be made, and many changes can be made in the preferred embodiments without departing from the principles of the disclosure. These and other changes in the preferred embodiments of the disclosure will be apparent to those skilled in the art from the disclosureherein, whereby it is to be distinctly understood that the foregoing descriptive matter is to be implemented merely as illustrative of the disclosure and not as a limitation.

[0122] The present disclosure provides a technical advancement in adaptive Discontinuous Reception (DRX) management for networks by introducing a network-driven mechanism that dynamically adjusts DRX parameters of a User Equipment (UE) based on real-time network condition parameters and predefined performance thresholds. The present disclosure enables the processing engine to determine a condition state of the UE using parameters such as Channel Quality Indicator (CQI) and Block Error Rate (BLER), and accordingly adjust DRX parameters including On Duration Timer, DRX Inactivity Timer, and DRX cycle lengths. The integration of service-based DRX configuration profiles and machine learning-assisted decision mechanisms enables intelligent selection of DRX configurations tailored to network conditions and service types. The present disclosure reduces unnecessary Physical Downlink Control Channel (PDCCH) monitoring, improves power efficiency of the UE, and enhances overall network performance through dynamic and adaptive DRX control.ADVANTAGES OF THE PRESENT DISCLOSURE

[0123] The present disclosure, as described above, offers several significant technical advantages that enhance the functionality and efficiency of the network, including, but not limited to:• Reducing latency and transmission delays by optimizing DRX parameters dynamically, leading to faster data transmission and improved user experience.• Increasing energy efficiency by adapting DRX configurations in response to network fluctuations, helping to extend the battery life of user equipment (UE).• Enabling efficient DRX profile management during 5CC (Five Component Carrier) aggregation by dynamically adjusting DRX settings for each component carrier, instead of applying a uniform DRX profile.• Optimizing sleep and wake-up cycles through an adaptive and dynamic DRX mechanism, ensuring that network conditions and traffic variations are efficiently accommodated for better overall system performance.

Claims

1. CLAIMSWe claim:

1. A method (400) for managing Discontinuous Reception (DRX) configuration of a User Equipment (UE) (104) in a network (106), the method (400) comprising:receiving (402), by a processing engine (208), at least one network condition parameter associated with the UE (104);comparing (404), by the processing engine (208), the at least one network condition parameter with at least one predefined performance threshold;determining (406), by the processing engine (208), at least one condition state of the UE (104) based on the comparing;adjusting (408), by the processing engine (208), one or more DRX parameters associated with the UE (104) based on the at least one condition state; andconfiguring ( 10), by the processing engine (208), the UE (104) with the adjusted one or more DRX parameters for at least one DRX operation.

2. The method (400) as claimed in claim 1, wherein the one or more DRX parameters comprises at least one of:an On-Duration timer;a DRX Inactivity timer;a Long DRX cycle; anda Short DRX cycle.

3. The method (400) as claimed in claim 1, comprising selecting one or more DRX configuration profiles for the UE (104), wherein each DRX configuration profile comprises a predefined set of values of the one or more DRX parameters, wherein adjusting the one or more DRX parameters comprises selecting the one or more DRX configuration profiles based on the at least one condition state.

4. The method (400) as claimed in claim 1, wherein the at least one network condition parameter comprises a Channel Quality Indicator (CQI) and a Block Error Rate (BLER), and wherein the CQI determines a Modulation and Coding Scheme (MCS) associated with the UE (104).

5. The method (400) as claimed in claim 4, wherein comparing the at least one network condition parameter with the at least one predefined threshold comprises:comparing the MCS with an MCS threshold; andcomparing the BLER with a BLER threshold.

6. The method (400) as claimed in claim 5, wherein determining the at least one condition state of the UE (104) comprises:determining a first condition state when the MCS is greater than or equal to the MCS threshold and the BLER is less than or equal to the BLER threshold; anddetermining a second condition state when the MCS is less than or equal to the MCS threshold and the BLER is greater than or equal to the BLER threshold.

7. The method (400) as claimed in claim 6, wherein adjusting the at least one DRX parameter comprises:increasing at least one of the at least one DRX parameter by a predefined incremental step value when the condition state satisfies the first condition state; anddecreasing at least one of the at least one DRX parameter by a predefined decremental step value when the condition state satisfies the second condition state.

8. The method (400) as claimed in claim 1, comprising applying a machine learning model to determine the condition state of the UE (104), wherein the machine learning model is trained using at least one historical network condition information and corresponding DRX parameter configurations.

9. A system (108) for managing Discontinuous Reception (DRX) configuration of a User Equipment (UE) (104) in a network (106), the system (108) comprising:a processing engine (208) configured to:receive at least one network condition parameter associated with the UE (104);compare the at least one network condition parameter with at least one predefined performance threshold;determine at least one condition state of the UE (104) based on the comparing;adjust one or more DRX parameters associated with the UE (104) based on the at least one condition state; andconfigure the UE (104) with the adjusted one or more DRX parameters for at least one DRX operation.

10. The system (108) as claimed in claim 9, wherein the one or more DRX parameters comprise at least one of:an On-Duration timer;a DRX Inactivity timer;a Long DRX cycle; anda Short DRX cycle.

11. The system (108) as claimed in claim 9, wherein the processing engine (208) is further configured to select one or more DRX configuration profiles for the UE (104), wherein each DRX configuration profile comprises a predefined set of values of the one or more DRX parameters, wherein adjusting the one or more DRX parameters comprises selecting the one or more DRX configuration profiles based on the at least one condition state.

12. The system (108) as claimed in claim 9, wherein the at least one network condition parameter comprises a Channel Quality Indicator (CQI) and a Block Error Rate (BLER), and wherein the CQI determines a Modulation and Coding Scheme (MCS) associated with the UE (104).

13. The system (108) as claimed in claim 12, wherein the CQI is used to determine a Modulation and Coding Scheme (MCS), and wherein the comparison comprises:comparing the MCS with an MCS threshold; andcomparing the BLER with a BLER threshold.

14. The system (108) as claimed in claim 13, wherein the processing engine (208) is configured to:determine a first condition state when the MCS is greater than or equal to the MCS threshold and the BLER is less than or equal to the BLER threshold; anddetermine a second condition state when the MCS is less than or equal to the MCS threshold and the BLER is greater than or equal to the BLER threshold.

15. The system (108) as claimed in claim 14, wherein the processing engine (208) is configured to:increase at least one of the one or more DRX parameters by a predefined incremental step value when the condition state corresponds to the first condition state; anddecrease at least one of the one or more DRX parameters by a predefined decremental step value when the condition state corresponds to the second condition state.

16. The system (108) as claimed in claim 9, wherein the processing engine (208) is configured to apply a machine learning model to determine the condition state of the UE (104), wherein the machine learning model is trained using historical network condition information and corresponding DRX parameter configurations.

7. A computer program product comprising a non-transitory computer- readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform a method (400) for managing Discontinuous Reception (DRX) configuration of a User Equipment (UE) (104) in a network (106), the method (400) comprising:receiving (402), by a processing engine (208), at least one network condition parameter associated with the UE (104);comparing (404), by the processing engine (208), the at least one network condition parameter with at least one predefined performance threshold;determining (406), by the processing engine (208), at least one condition state of the UE (104) based on the comparing;adjusting (408), by the processing engine (208), one or more DRX parameters associated with the UE (104) based on the at least one condition state; andconfiguring (410), by the processing engine (208), the UE (104) with the adjusted one or more DRX parameters for at least one DRX operation.

Images