Method and system for managing data plans in a telecommunication network

Abstract

A system 108 and a method 500 for managing plans (e.g., hybrid data plans) in a telecommunication network 106. The method includes a Charging Function (CHF) – Broadband Network Gateway (BNG) 110 that receives a plan allocation request from a Session Management Function (SMF) 112. The method includes determining an expiry of an active plan and a quota associated with the active plan. Upon determining the expiry of the active plan and the quota associated with the active plan, one of a presence or an absence of the plan in a plan stack and a plan queue is determined. When the plan is absent in the plan stack, the presence of the plan in the plan queue is performed. When the plan is present in the plan queue, the plan from the plan queue to the plan stack for performing allocations (e.g., data) associated with the plan to a user equipment 104.

Description

METHOD AND SYSTEM FOR MANAGING DATA PLANS IN A TELECOMMUNICATION NETWORKRESERVATION 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.TECHNICAL FIELD

[0002] The present disclosure relates to a telecommunications network. In particular, the present disclosure relates to a method and a system for managing data plans in a telecommunication 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 ‘Session Management Function (SMF)’ used herein in the specification refers to a network function (or a network component) in a telecommunication network that is responsible for session management, including session establishment, modification, and release.

[0005] The term ‘Charging Function -Broadband Network Gateway (CHF)- (BNG)’ as used herein in the specification refers to a specific configuration of a network function (e.g., the CHF) integrated with a gateway (e.g., the BNG). In thisconfiguration, the CHF manages billing and charging rules specifically for broadband services delivered via the BNG. The CHF calculates and records service charges based on usage data and policy rules, enabling accurate billing and financial management in a telecommunication network (e.g., a Fifth Generation (5G) core network).

[0006] The term ‘data plans’ used herein in the specification refers to a set of predefined data usage allowances and associated conditions offered by a network service provider to a User Equipment (UE). These data plans may include various parameters such as data quotas, validity periods, pricing, and policy.

[0007] The term ‘active plan’ used herein in the specification refers to an ongoing plan that is currently in use by a subscriber of the UE, providing the subscriber with data services and features as per the active plan entitlements and the quota.

[0008] The term ‘hybrid plans’ used herein in the specification refers to an additional plan or a new plan that combines features of both pre-paid and post-paid plans. In particular, the hybrid plan is a flexible subscription package that allows the subscribers to access and use services (e.g., voice call, data) by recharging with a set amount of data for a fixed period, as needed.

[0009] The term ‘Packet Gateway (PGW)’ used herein in the specification refers to a core network element in the telecommunication network that manages data traffic between mobile networks and external networks such as the internet. The PGW handles functions like internet protocol (IP) address allocation, data packet routing, and policy enforcement for user data sessions.

[0010] The term ‘Fault Management System (FMS)’ used herein in the specification refers to a network management tool designed to monitor, detect, and respond to faults or issues within the telecommunications network. The FMS helps in identifying, diagnosing, and resolving network problems to maintain operational efficiency and service quality.

[0011] The term ‘Evolved Packet Core (EPC)’ used herein in the specification refers to a core network architecture for the telecommunication network,responsible for managing data traffic, user sessions, and connectivity between the mobile network and the external networks.

[0012] The term ‘Subscriber Profile Repository (SPR)’ used herein in the specification refers to a database in the mobile networks that stores and manages subscriber profiles, including user identities, service entitlements, and subscription details. The SPR provides essential information for authentication, authorization, and accounting processes in the telecommunication network.

[0013] The term ‘Media Access Control Identifier (MAC ID)’ used herein in the specification refers to a universal identifier applicable in case of both type of subscribers, i.e. post-paid subscribers and pre-paid subscribers. The MAC ID is used to streamline subscriber’s data and session retrieval, reducing data fetching latency significantly.

[0014] These definitions are in addition to those expressed in the art.BACKGROUND

[0015] 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.

[0016] The landscape of subscription services has undergone significant transformation in recent years, driven by the need for greater flexibility and efficiency in managing diverse subscription models. As subscription services evolve, there is an increasing demand for systems capable of handling a variety of subscription types, such as pre-paid plans, post-paid plans, and hybrid plans simultaneously. This shift in the usage of the subscription services reflects the growing preference among consumers (or subscribers) for flexible and customizable service options that align with their individual needs and usage patterns. This evolution of the subscription services has led to an increasing demand for flexible and efficient management systems that can handle a variety ofsubscription types concurrently. Currently used management systems for pre-paid and post-paid subscriptions often rely on separate and rigid databases for each subscription type. The conventional management systems frequently lead to complex, redundant entries within the database. For instance, separate records are maintained for different types of plans, even when they are essentially the same but tailored for different billing methods. This redundancy not only complicates the database structure but also results in inefficiencies in processing and managing the subscriber’s information.

[0017] The complexity and duplication inherent in these conventional management systems can adversely affect operational efficiency. Further, the redundant database entries lead to increased storage requirements, causing delays in processing transactions or updates. Additionally, the lack of a unified management approach limits the flexibility offered to the subscribers, making it difficult for the subscribers to seamlessly switch between different types of plans or combine multiple services under a single plan. Moreover, the rigid separation of the subscription types often means that the subscribers are constrained by the limitations of their current plan type. For example, a subscriber on a pre-paid plan might find it challenging to access features or benefits typically available to the subscribers of post-paid plans, and vice versa. This lack of integration impedes the ability to offer comprehensive, hybrid solutions that could better cater to the diverse needs of the subscribers.

[0018] There is, therefore, a need in the art to provide a method and a system that can mitigate the disadvantages of the prior art.OBJECTIVE OF THE PRESENT DISCLOSURE

[0019] Some of the objectives of the present disclosure, which at least one embodiment herein satisfies, are as follows:

[0020] An objective of the present disclosure is to provide a method and a system for managing plans (e.g., data plans) in a telecommunication network.

[0021] Another objective of the present disclosure is to provide flexibility to subscriber’s in managing their plans by using a Media Access Control (MAC)Identifier (ID) to maintain each subscriber profile. This approach allows the subscribers to easily access and manage hybrid plans as well as existing active plans, by enabling the subscribers to select a hybrid plan that best fits their needs, without being restricted by an associated subscription type.

[0022] Another objective of the present disclosure is to optimize a process of managing a database by implementing the hybrid plans that can be assigned to both pre-paid and post-paid subscribers. The implementation of the hybrid plans eliminates the need to create separate duplicate records for a pre-paid and a postpaid subscriber in the database, thereby reducing redundancy and resulting in a more efficient and manageable database structure.

[0023] Another objective of this disclosure is to offer comprehensive recharge options to the subscribers. The hybrid plans (also referred to as pre-over post plans) are designed to serve both the pre-paid and the post-paid subscribers with active rental plans (i.e., the active plans), providing a wide range of recharge options for all types of the subscribers. The integration of the hybrid plans into recharges options enhances the choices available for the subscribers, ensuring the subscribers can easily recharge regardless of their subscription type.

[0024] Another objective of the present disclosure is to provide prioritized the hybrid plans handling by managing the hybrid plans over the active plans using a stack or a queue approach to ensure efficient processing of plan allocation requests. The hybrid plans in the stack are given priority, ensuring that the subscribers with the active rental plans receive prompt service. When the stack is empty, the hybrid plans are automatically moved to the stack, maintaining a continuous flow of service without delays. This queue-to-stack movement enhances subscriber benefits by starting rental or validity only when a hybrid plan is actually needed, rather than from a date of recharging the hybrid plan.

[0025] Another objective of the present disclosure is to provide automated plans management. For automating plans management, the system prioritizes a hybrid plan in a queue when an active plan in the stack expires and activates a queue-to-stack Application Programming Interface (API) to ensure seamless service. The queue-to-stack API ensures that the hybrid plan is moved from thequeue to the stack without requiring a manual input from the subscriber or a network service provider by generating a trigger upon detecting an expiry of the plan (i.e., the active data plan or the hybrid data plan) present in the stack. This automation minimizes the need for manual intervention, streamlines plan management, and ensures uninterrupted service for the subscribers.

[0026] Another objective of the present disclosure is to facilitate direct access to the subscribers and session details associated with the subscribers by using the MAC ID as a primary identifier for each subscriber. The usage of the MAC ID enables a precise and an efficient processing of the hybrid plans, as well as the stack and the queue analysis.

[0027] Another objective of the present disclosure is to provide flexibility of pre-over post plans (i.e., the hybrid data plans) to the subscribers. The hybrid data plans offer the flexibility to boost an existing active data plan speed, which is not available with standard post-paid plans where policy inheritance from the existing data plan limits speed upgrades.

[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 plans in a network is described. The method comprises receiving, by a first network component, a plan allocation request corresponding to a user equipment (UE), from a second network component and extracting, by the first network component, a first set of parameters from the received plan allocation request. The method further comprises determining, by the first network component, whether at least one active plan and a quota associated with the at least one active plan corresponding to the UE in a plan stack is expired based on the extracted first set of parameters and upon determining, identifying, by the first network component, fulfilment of one or more conditions associated with at least one plan corresponding to the UE. The one or more conditions comprises of detection of one of a presence or absence of the atleast one plan corresponding to the UE in the plan stack and a plan queue. The method comprises upon identifying, performing, by the first network component, one or more operations associated with the at least one plan. The one or more operations comprise transfer of the at least one plan from the plan queue to the plan stack.

[0030] In some embodiments, the first network component is Charging Function-Broadband Network Gateway (CHF)-(BNG) and the second network component is a Session Management Function (SMF).

[0031] In some embodiments, the first set of parameters comprises a Media Access Control (MAC) Identifier (ID).

[0032] In some embodiments, the at least one plan comprises a pre-paid plan, a post-paid plan and a hybrid plan.

[0033] In some embodiments, the method further comprises upon determining the absence of the at least one plan within the plan stack, determining, by the first network component, one of a presence or an absence of the at least one plan corresponding to the UE in the plan queue. The method further comprises upon determining the presence of the at least one plan within the plan queue, transferring, by the first network component, the at least one plan from the plan queue to the plan stack for performing allocation associated with the at least one plan to the UE based on the plan allocation request, and activating, by the first network component, the at least one plan on the UE.

[0034] In some embodiments, the method comprises upon determining the presence of the plan within the plan stack, performing, by the first network component, allocation associated with the plan to the UE based on the plan allocation request.

[0035] In some embodiments, the method comprises upon determining the absence of the plan within the plan queue, rejecting, by the first network component, the plan allocation request.

[0036] In some embodiments, the method comprises upon determining the at least one active plan and the quota associated with the at least one active plan corresponding to the UE in the plan stack is not expired, performing, by the firstnetwork component, allocation available in the at least one active plan to the UE based on the plan allocation request.

[0037] In some embodiments, the method comprises transferring of the plan from the plan queue to the plan stack is based upon a priority order according to a plan priority and recharge dates.

[0038] In some embodiments, the at least one plan comprising of either a dependent plan or an independent plan.

[0039] In some embodiments, the method comprises transferring, by the first network component, the dependent plan into the plan stack and transferring, by the first network component, the independent plan either in the plan stack or in the plan queue based on expiry of the at least one active plan, expiry of the quota associated with the at least one active plan and a plan flag status.

[0040] In another exemplary embodiment, a system for managing plans in a network, the system comprising a first network component and a second network component is described. The first network component comprises a receiving unit configured to receive a plan allocation request corresponding to a user equipment (UE) from a second network component. An extraction unit is configured to extract a first set of parameters from the received plan allocation request. A determining unit is configured to determine whether at least one active plan and a quota associated with the at least one active plan corresponding to the UE in a plan stack is expired based on the extracted first set of parameters. Upon determining, an identification unit is configured to identify fulfilment of one or more conditions associated with at least one plan corresponding to the UE. The one or more conditions comprises of detection of one of a presence or absence of the at least one plan corresponding to the UE in the plan stack and a plan queue. Upon identifying, an execution unit is configured to perform one or more operations associated with the at least one plan, wherein the one or more operations comprise transfer of the at least one plan from a plan queue to a plan stack.

[0041] In yet another exemplary embodiment, 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 processorsto execute a method for managing plans in a network is described. The method comprises receiving, by a first network component, a plan allocation request corresponding to a user equipment (UE), from a second network component and extracting, by the first network component, a first set of parameters from the received plan allocation request. The method further comprises determining, by the first network component, whether at least one active plan and a quota associated with the at least one active plan corresponding to the UE in a plan stack is expired based on the extracted first set of parameters and upon determining, identifying, by the first network component, fulfilment of one or more conditions associated with at least one plan corresponding to the UE. The one or more conditions comprises of detection of one of a presence or absence of the at least one plan corresponding to the UE in the plan stack and a plan queue. The method comprises upon identifying, performing, by the first network component, one or more operations associated with the at least one plan. The one or more operations comprise transfer of the at least one plan from the plan queue to the plan stack.

[0042] 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 THE DRAWINGS

[0043] 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.

[0044] FIG. 1 illustrates an exemplary network architecture comprising a system configured for managing data plans in a network, in accordance with an embodiment of the present disclosure.

[0045] FIG. 2 illustrates an exemplary block diagram of the system configured for managing the data plans in the network, in accordance with an embodiment of the present disclosure.

[0046] FIG. 3 illustrates an exemplary system architecture of the system configured for managing the data plans in the network.

[0047] FIG. 4 illustrates an exemplary flow diagram of a method for managing the data plans in the network, in accordance with an embodiment of the present disclosure.

[0048] FIG. 5 illustrates an exemplary flow diagram of a method for managing plans in the network, in accordance with an embodiment of the present disclosure.

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

[0050] The foregoing shall be more apparent from the following more detailed description of the disclosure.LIST OF REFERENCE NUMERALS100 - Network architecture102 - User(s)104 -User Equipments (UEs)106 - Network108 - System110 - First Network Component / Charging Function (CHF) - Broadband Network Gateway (BNG)112 - Second Network Component / Session Management Function (SMF)200 - Block diagram202 - Processor(s)204 - Memory206 -Interface(s)208 - Processing engine210 - Database212 - Receiving Unit214 - Extraction Unit216 - Determining Unit218 - Identification Unit220 - Execution Unit300 - System Architecture302 - Packet Gateway (PGW)304 - Plan Provisioning Module306 - Customer Provisioning Module308 - Fault Management System (FMS)310 - Evolved Packet Core (EPC)312 - Subscriber Profile Repository (SPR)400 - Flow Diagram500 - Flow Diagram600 - Computer System610 - External Storage Device620 - Bus630 - Main Memory640 - Read Only Memory650 - Mass Storage Device660 - Communication Port670 - ProcessorDETAILED DESCRIPTION

[0051] 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 any 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. Example embodiments of the present disclosure are described below, as illustrated in various drawings in which like reference numerals refer to the same parts throughout the different drawings.

[0052] 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 thefunction and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.

[0053] 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.

[0054] Also, it is noted that individual embodiments may be described as a process that 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.

[0055] 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 like the term “comprising” as an open transition word without precluding any additional or other elements.

[0056] 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.

[0057] The terminology used herein is to describe particular embodiments only and is not intended to be limiting the disclosure. As used herein, the singular forms “a”, “an”, and “the” are intended to include the plural forms as well, unless the context 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 combinations of one or more of the associated listed items. It should be noted that the terms “mobile device”, “user equipment”, “user device”, “communication device”, “device” and similar terms are used interchangeably for the purpose of describing the invention. These terms are not intended to limit the scope of the invention or imply any specific functionality or limitations on the described embodiments. The use of these terms is solely for convenience and clarity of description. The invention is not limited to any particular type of device or equipment, and it should be understood that other equivalent terms or variations thereof may be used interchangeably without departing from the scope of the invention as defined herein.

[0058] As used herein, an “electronic device”, or “portable electronic device”, or “user device” or “communication device” or “user equipment” or “device” refers to any electrical, electronic, electromechanical, and computing device. The user device is capable of receiving and / or transmitting one or parameters, performing function / s, communicating with other user devices, and transmitting data to theother user devices. The user equipment may have a processor, a display, a memory, a battery, and an input-means such as a hard keypad and / or a soft keypad. The user equipment may be capable of operating on any radio access technology including but not limited to IP-enabled communication, Zig Bee, Bluetooth, Bluetooth Low Energy, Near Field Communication, Z-Wave, Wi-Fi, Wi-Fi direct, etc. For instance, the user equipment may include, but not limited to, a mobile phone, smartphone, virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general -purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other device as may be obvious to a person skilled in the art for implementation of the features of the present disclosure.

[0059] Further, the user device may also comprise a “processor” or “processing unit” includes processing unit, wherein processor refers to any logic circuitry for processing instructions. The processor may be a general -purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a Digital Signalling Processing (DSP) core, a controller, a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc. The processor may perform signal coding data processing, input / output processing, and / or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor is a hardware processor.

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

[0061] Embodiments herein relate to a method for managing plans (e.g., data plans) in a telecommunication network. Initially, a first network component may beconfigured to receive a plan allocation request corresponding to a User Equipment (UE) associated with a user, from a second network component. The first network component may be a Charging Function-Broadband Network Gateway (CHF)- (BNG). The second network component may be a Session Management Function (SMF). Upon receiving the plan allocation request, the first network component is configured to determine an expiry of an active plan and a quota associated with the active plan corresponding to the UE, upon receiving plan allocation request. Upon determining the expiry of the active plan and the quota associated with the active plan, the first network component is configured to determine one of a presence or an absence of a hybrid plan corresponding to the UE in a plan stack. Upon determining the absence of the hybrid plan in the plan stack, the first network component is configured to perform a check to determine one of a presence or an absence of the hybrid plan corresponding to the UE in a plan queue. Upon determining the presence of the hybrid plan within the plan queue, the first network component is configured to transfer the hybrid plan from the plan queue to the plan stack for performing allocation (e.g., data allocation) associated with the hybrid plan to the UE based on the plan allocation request.

[0062] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings.

[0063] The various embodiments throughout the disclosure will be explained in more detail with reference to FIG. 1- FIG. 6.

[0064] FIG. 1 illustrates an exemplary network architecture 100 comprising a system 108 for managing data plans in a telecommunication network, in accordance with an embodiment of the present disclosure.

[0065] As illustrated in FIG. 1, the 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 collectively referred to as the users 102. Similarly, a person of ordinary skill in the art will understand that one or more UEs 104-1, 104-2. . . 104-N may be collectively referred to as the UE 104 or the UEs 104. Although only three UE 104 are depicted in FIG.1, however, any number of the UE 104 may be included without departing from the scope of the ongoing description.

[0066] 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 are not limited to, smartphones, smart watches, smart sensors (e.g., a mechanical, a thermal, an electrical, a magnetic, etc.), networked appliances, networked peripheral devices, networked lighting system, communication devices, networked vehicle accessories, networked vehicular devices, smart accessories, tablets, a smart television (TV), computers, a smart security system, a 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 UE 104 may include, but not limited to, intelligent, multi-sensing, network-connected devices, that may integrate seamlessly with each other and / or with a central server or a cloudcomputing system or any other device that is network-connected.

[0067] Additionally, in some embodiments, the UE 104 may include, but 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 headmounted 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 UE 104 may include, but are not limited to, any electrical, electronic, electromechanical, or equipment, or a combination of one or more of the above devices, such as virtual reality (VR) devices, augmented reality (AR) devices, a laptop, a general-purpose computer, a desktop, a personal digital assistant, a tablet computer, a mainframe computer, or any other computing device. Further, the UE 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 an entity such as a touchpad, atouch-enabled screen, an electronic pen, and the like. A person of ordinary skill in the art will appreciate that the UE 104 may not be restricted to the mentioned devices and various other devices may be used.

[0068] In FIG. 1, the UE 104 may communicate with the system 108 through a network 106 (i.e., the telecommunication network) for sending or receiving various types of data. 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 UE 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 some other 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.

[0069] 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, 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.

[0070] 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.

[0071] The system 108 comprises a first network component 110 and a second network component 112. The first network component 110 may include a Charging Function (CHF) - Broadband Network Gateway (BNG). The second network component 112 may include a Session Management Function (SMF). In an aspect, the network component refers to any network element / network function that enables the network to function and support communication, data transfer, and resource sharing among devices or systems. The network components work together to create, manage, and maintain the infrastructure of the network. The CHF manages billing and charging rules for broadband services delivered via the BNG. The CHF calculates and records service charges based on usage data and policy rules, enabling accurate billing and financial management in the telecommunication network (i.e., network 106). The SMF refers to a network function (or a network component) in the telecommunication network (i.e., network 106) responsible for session management, including session establishment, modification, and release.

[0072] Although FIG. 1 shows exemplary components of the network architecture 100, in other embodiments, the network architecture 100 may include 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.

[0073] FIG. 2 illustrates an exemplary block diagram 200 of the system 108 configured for managing the data plans in the telecommunication network, in accordance with an embodiment of the disclosure. FIG. 2 is explained in conjunction with FIG. 1.

[0074] 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 units, logic circuitries, and / or any 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 storedin a 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 include any non-transitory storage device including, for example, volatile memory such as a Random-Access Memory (RAM), or a non-volatile memory such as an Erasable Programmable Read Only Memory (EPROM), a flash memory, and the like.

[0075] In an embodiment, the system 108 may include an interface(s) 206. The interface(s) 206 may include 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, a processing engine 208 and a database 210.

[0076] In an embodiment, the system 108 may include a processing engine 208 that may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing engine 208. In examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processing engine 208 may be processorexecutable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processing engine 208 may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the machine-readable storage medium may store instructions that, when executed by the processing resource, implement the processing engine 208. In such examples, the system 108 may comprise the machine-readable storage medium storing the instructions and the processing resource to execute the instructions, or the machine-readable storage medium may be separate but accessible to the system 108 and the processing resource. In other examples, the processing engine 208 may be implemented by electronic circuitry.

[0077] In an embodiment, the system 108 may include the database 210 that stores data (e.g., the active data plans, the hybrid data plans, the local catalog etc.). This data may be generated as a result of functionalities implemented by any of the components of the processor 202 or the processing engine 208. In an aspect, the local catalog refers to a data repository maintained by the network operator that stores, but is not limited to, service plans and offers, policy rules, charging rules, subscriber’s details, etc. The service plan and offers comprise, but are not limited to, plan identifier (ID), plan description, data volume, validity, speed limit, etc. The policy rules comprise, but are not limited to, data quota, speed limit, app-based restrictions, time-of-day access, fair usage policies (FUP), roaming controls, etc. The processing engine 208 may comprise a receiving unit 212, an extraction unit 214, a determining unit 216, an identification unit 218, and an execution unit 220.

[0078] In an aspect, the processing engine 208 may be part of the first network component 110. The first network component 110 may be a Charging Function- Broadband Network Gateway (CHF)-(BNG). The first network component 110 comprises the receiving unit 212, the extraction unit 214, the determining unit 216, the identification unit 218 and the execution unit 220. In an aspect, the second network component 112 may be a Session Management Function (SMF). The CHF- BNG 110 may be configured to communicate with the SMF 112. In an embodiment, the SMF 112 may be present within a processing engine of another system.

[0079] In an embodiment, the processing engine 208 is configured to manage the plans (e.g., data plans, voice plans, pre-paid plans, post-paid plans, hybrid plans, etc.) in the telecommunication network. Examples of the telecommunication network may include the 4G network, the 5G network, the 6G network, and the like.

[0080] A data plan is a set of predefined data usage allowances and associated conditions offered by a network service provider to the UE. The data plan may include various parameters such as data quotas, validity periods, pricing, and policy. In other words, the data plan is a subscription package that provides a set amount of data usage (e.g., 1000 gigabytes (GB)) for a specified period, such as a month. The data plan allows users, e.g., the user 102 (also referred to as a subscriber) to access the internet and use data services on their mobile devices, e.g., a smartphone,or other connected devices, e.g., a laptop, a tablet, a smart television, etc., (i.e., the UE 104), with varying limits and speeds depending on the data plan.

[0081] The data plans may include an active data plan or a hybrid data plan. The active data plan (also referred to as an active rental plan or a current data plan) is an ongoing plan that is currently in use by the subscriber of the UE, providing the subscriber with data services and features as per the active data plan entitlements and the quota.

[0082] In an aspect, the hybrid plan corresponds to an additional plan or a new plan that combines features of both pre-paid and post-paid plans. The hybrid plan is also referred to as a pre-over post plan. In particular, a hybrid data plan is a flexible subscription package that allows the subscribers to access and use data services by recharging with a set amount of data (e.g., 100 GB) for a fixed period (e.g., 5 days), as needed.

[0083] In an aspect, the voice plan is a subscription service provided by a network operator that allows the users to make and receive phone calls and text messages. These plans can offer unlimited calling and texting, or a set number of minutes and messages per month (e.g., 500 mins / month, 100 SMS) with additional charges for exceeding the limits. The voice plans are often bundled with data plans (e.g., unlimited calls, 1GB / day for 30 days), offering a comprehensive package of mobile services.

[0084] In an aspect, the processing engine 208 manages the plans by transferring plans from a plan queue to a plan stack. In an aspect, multiple plans are stored in the plan stack, and only one plan is active at a time. Any new plan gets added on top and activates immediately by pausing the current plan or waiting for the current plan to expire. In an aspect, the plan queue comprises data corresponding to new plans of the UE. When the user recharges a new plan before the current plan ends, the plan queue ensures that the new plan is scheduled to start only after the current plan expires.

[0085] The receiving unit 212 is configured to receive a plan allocation request corresponding to the UE 104 from the second network component (i.e., SMF) 112. In an aspect, the plan allocation request refers to a request to allocate plans to theUE. For example, the plan allocation request may be a data allocation request, a data + voice plan allocation request. In an aspect, the user 102 may request a new plan by sending the plan allocation request to the SMF 112. The SMF 112 forwards the plan allocation request (e.g., data allocation request) to the CHF-BNG 110. In an example, the CHF-BNG 110 receives a data allocation request (e.g., 30GB additional data for 10 days) from the SMF 112.

[0086] The extraction unit 214 is configured to extract a first set of parameters from the received plan allocation request. The first set of parameters comprises a Media Access Control (MAC) Identifier (ID). In an aspect, the MAC ID is an identifier assigned to each device (e.g., user equipment (UE) (104)) to identify the device (i.e., UE 104). The MAC ID is a primary identifier that enables direct access to the user (e.g., customer) and session details from the database (210). The user and session details comprise information related to an ongoing session between the UE 104 and the network 106, and the details related to the user’s plan. In an aspect, the user and session details comprise, but are not limited to, UE identity information (e.g., international mobile equipment identity (IMEI), International mobile subscriber identity (IMSI), etc.), session identifier, plan data (e.g., active plan, data usage, remaining data, etc.), connection details (e.g., access point name, session start time, session end time, network type (e.g., 4G, 5G, 6G, etc.)), roaming information, add-on services, policy information, etc.

[0087] The database 210 includes a processing unit that maps user and session details to the MAC ID of the UE. In mapping, the user and session details of a particular UE are stored against the MAC ID of the particular UE. These mapped user and session details are stored within the database 210 and indexed based on the MAC ID. Indexed searches for customer data and sessions are performed using the MAC ID as a unique identifier, significantly reducing data retrieval latency. As a result, the MAC ID alone can be used to efficiently fetch the details of the user (e.g., customer or subscriber) regardless of the user type (i.e., postpaid or prepaid). Based on the MAC ID, the user and session details (e.g., plan data) corresponding to the UE are extracted from the database 210. The extracted user and session detailsare used for further processing of the plans. In this way, the use of the MAC ID enables a precise and efficient processing of the plans.

[0088] The determining unit 216 is configured to determine whether at least one active plan and a quota associated with the at least one active plan corresponding to the UE 104 in a plan stack is expired based on the extracted first set of parameters. In an aspect, the plan stack stores data corresponding to the active plan corresponding to the user. The user and session details extracted based on the MAC ID are used to determine whether the active plan and quota associated with the active plan corresponding to the UE 104 have expired or not.

[0089] Upon determining that at least one active plan and the quota associated with the at least one active plan corresponding to the UE 104 in the plan stack have not expired, the execution unit is configured to perform allocation available in the at least one active plan to the UE 104 based on the plan allocation request. In an aspect, the allocation available in the active plan (i.e., remaining data / quota) is allocated to the UE 104, when the active plan and quota associated with the active plan in the plan stack is not expired. In an embodiment, the allocation in the active plan can be done automatically or manually. The automatic allocation uses predefined rules to assign allocations (e.g., subscriptions) to the users based on criteria (e.g., billing periods, usage, or other factors). The manual allocation requires an administrator (e.g., network operators) to manually assign the allocations (e.g., subscriptions).

[0090] In an example, active data plan of the UE is 2GB / per day for 30 days with starting date 5th April to 4th May. On 30th April, the CHF-BNG receives plan allocation request (i.e., 30 GB additional data). The data used on 30th April is 1 GB. The CHF-BNG determines that active data plan (i.e., 2GB / per day for 30 days) and quota (i.e., 2GB) has not expired. The CHF-BNG assigns remaining 1 GB data of 30th April.

[0091] Upon determining that at least one active plan and a quota associated with at least one active plan corresponding to the UE 104 in a plan stack has expired, the identification unit 218 is configured to identify fulfilment of one or more conditions associated with at least one plan corresponding to the UE 104. The oneor more conditions comprise detecting the presence or absence of at least one plan corresponding to the UE 104 in the plan stack and the plan queue. Based on identification of the plan in the plan stack or the plan queue, the execution unit 220 is configured to perform one or more operations associated with the at least one plan. The one or more operations comprise transfer of the at least one plan from the plan queue to the plan stack. In an example, the active data plan of the UE is 2GB / per day for 30 days with starting date 5th April to 4th May. On 4th may, the CHF-BNG receives plan allocation request (i.e., 30 GB additional data). The CHF- BNG determines that active data plan (i.e., 2GB / per day for 30 days) and quota (i.e., 2GB) has expired.

[0092] In an aspect, when the active plan and quota associated with the active plan corresponding to the UE 104 have expired, the identification unit first determines whether at least one plan corresponding to the UE 104 is present in the plan stack. Upon determining the presence of the plan within the plan stack, the execution unit 220 is configured to perform allocation associated with the plan to the UE 104 based on the plan allocation request. In an example, on 4th May, the CHF-BNG determines that active data plan (i.e., 2GB / per day for 30 days starting form 5th April to 4th May) and quota (i.e., 2GB) has expired. The CHF-BNG determines whether any plan is present in the plan stack. In the plan stack, add-on plan (e.g., IGB / per day for 10 days) is present. Upon detecting the presence of the add-on plan (e.g., IGB / per day for 10 days) in the plan stack, the CHF-BNG allocates the IGB / per day for 10 days to the UE.

[0093] Upon determining the absence of at least one plan within the plan stack, the determining unit 216 is configured to determine the presence or absence of at least one plan corresponding to the UE 104 in the plan queue. Upon determining the presence of the at least one plan within the plan queue, the execution unit 220 is configured to transfer the at least one plan from the plan queue to the plan stack for performing allocations associated with the at least one plan to the UE 104 based on the plan allocation request and activate the at least one plan on the UE 104. In an example, on 4th May, the CHF-BNG determines that the active data plan (i.e., 2GB / per day for 30 days starting from 5th April to 4th May) and quota (i.e., 2GB)have expired. The CHF-BNG determines that no other plan is present in the plan stack. The CHF-BNG then determines whether any plan is present in the plan queue. In plan queue, the plan (i.e., IGB / per day for 10 days) is present. The CHF- BNG determines the plan (i.e., IGB / per day for 10 days) is present in the plan queue. Upon determining, the CHF-BNG transfers the plan (i.e., IGB / per day for 10 days) from the plan queue to the plan stack. Upon transferring, the CHF-BNG performs allocation of the plan (i.e., IGB / per day for 10 days) to the UE.

[0094] Upon determining the absence of the plan within the plan queue, the execution unit 220 is configured to reject the plan allocation request. In an aspect, when the plan is absent in the plan queue, the execution unit 220 rejects the plan allocation request. In an example, on 4th May, the CHF-BNG determines that the active data plan (i.e., 2GB / per day for 30 days starting from 5th April to 4th May) and quota (i.e., 2GB) have expired. The CHF-BNG determines that no other plan is present in the plan queue. The CHF-BNG rejects the plan allocation request (i.e., add-on request of 30GB additional data for 10 days).

[0095] In an aspect, the at least one plan comprises a pre-paid plan, a post-paid plan and a hybrid plan. In an aspect, the pre-paid plan refers to a service plan where the user (e.g., subscriber, customer) pays in advance for the services the user wants to use (e.g., voice call / talk time, short messaging service (SMS), data, etc.). In an aspect, the post-paid plan refers to a service plan where the user uses the services first (e.g., voice calls, data, SMS, etc.), and then pays for them later (e.g., at the end of a monthly billing cycle). In an aspect, the hybrid plan refers to a fixed validitybased plan that can be purchased by the user based on the current available quota and the number of days left in the existing bill cycle period. The hybrid plan operates on a pay-as-you-go basis and applies to prepaid and post-paid users. The hybrid plan is also referred to as pre-over post plan. The hybrid plans have inherited expiry and policy from a parent plan, and for rental plans, expiry aligns with the bill cycle. Otherwise, it follows pre-over-post plan.

[0096] In an aspect, transferring of the plan from the plan queue to the plan stack is based upon a priority order according to a plan priority and recharge dates.The plan is transferred from the plan queue to the plan stack based on first-in, firstout (FIFO).

[0097] In an aspect, the at least one plan comprising of either a dependent plan or an independent plan. The hybrid plans may be of two types, i.e., dependent plans and independent plans.

[0098] The dependent plan may be referred to as a plan that allows a primary user to share services (e.g., data) with secondary users (e.g., family members) or devices. The primary user is responsible for the bill and manages the plan. Each of users of the dependent on the plan uses the same data allowance, rather than having separate individual plans.

[0099] The independent plan may be referred to as a plan that is purchased by the user directly from a service provider without being bundled with other users or services. The independent plan offers a set amount of data, voice minutes, and texts for a specific period (e.g., a month, 90 days, one year). The independent plan is often more flexible than the dependent plans, allowing the users to choose the data amount that best suits their needs and potentially switch between providers more easily.

[0100] In an aspect, the dependent plan inherits validity from an existing active plan, while the independent plan has its own fixed validity and policy. The dependent plan remains active as long as the primary plan is valid. If the user has an active main plan (e.g., a monthly prepaid plan) and adds a data add-on pack, the add-on is valid for the same duration as the main plan. The independent plans have a set validity period (e.g., one year, six months, or a month), the policies associated with independent subscriber plans may include usage restrictions, such as limitations on the number of users, devices, or features that can be accessed. The users may renew their subscription at the end of the validity period, either automatically or by making a separate renewal request. If a plan is not renewed, it will expire at the end of the validity period, and access to the services or resources may be terminated. The policies of the independent plan may also specify the procedures for refunds, cancellations, upgrades, or downgrades of the plan.

[0101] In an aspect, the execution unit 220 is configured to transfer the dependent plan into the plan stack. The independent plan is transferred either in the plan stack or in the plan queue based on expiry of the at least one active plan, expiry of the quota associated with the at least one active plan and a plan flag status. In an embodiment, whenever a subscriber associated with the UE 104 does a recharge with a new plan (i.e., the hybrid data plan), the CHF BNG 110 checks the local catalog to determine if the new plan is a dependent plan or an independent plan, considering an associated plan flag. The plan flag helps determining how the new plan should be processed in relation to the existing active plan. In other words, the plan flag helps in determining whether the new plan should be stored in the plan queue for later application after the expiry of the existing active plan (e.g., active data plan) or should be immediately stored in the plan stack with the existing active plan. For instance, when the new plan is the dependent plan (e.g., an add-on recharge), then the plan flag may be marked as a stack flag to immediately store the new plan in the plan stack. Further, when the new plan is the independent plan, then the plan flag may be either marked as the stack flag or a queue flag depending upon the expiry of the existing active plan and the quota available of the existing active plan. For example, when the active plan (e.g., active data plan) is not expired, and the quota is available for the active data plan, the plan flag may be the queue flag to store the new data plan in the plan queue for applying the new data plan after the expiry of the existing active data plan.

[0102] Further, when the active data plan is expired and the quota is not available, the data flag may be marked as the stack flag to store the new data plan in the plan stacks for immediately applying the new data plan to resume the services (e.g., the video calling service, the data services, etc.) for the subscriber. This classification of the new data plan in the dependent data plan and the independent data plan helps in managing how the new data plan is stored and applied. The dependent data plans are automatically moved to the plan stack, while the independent plans can be placed either in the plan stack or the plan queue based on factors like an expiry of the existing active data plan, the quota available of the existing active data plan, and the data plan flag. In an embodiment, the hybrid plans(e.g., hybrid data plans) in the plan queue can be moved to the plan stack either manually or automatically upon expiration of the currently active data plan, following a priority order based on a plan priority and recharge dates, typically on a first-in, first-out (FIFO) basis. The plan priority means that each data plan is assigned a priority level based on a subscription type (e.g., a pre-paid subscription and a post-paid subscription), service level agreements, or network policies. The data plans with higher priority levels are given precedence during the movement from the plan queue to the plan stack. This provides flexibility in the hybrid data plans management.

[0103] In an aspect, the post-paid customers (or the post-paid subscribers) can enhance their existing rental data plans (i.e., the existing active data plans) by purchasing additional new data plans, i.e., the hybrid data plans, through a one-time payment. When provisioning these hybrid data plans, the CHF-BNG 110 first checks for any currently active data plan and available quotas of the currently active data plan within the plan stack. If the currently active data plan is already active, the new data plan is stored in the plan queue. However, when the currently active data plan has expired or its quota is depleted, the hybrid data plan is immediately incorporated into the plan stack. During the recharges done by the subscribers for the hybrid data plans, the CHF-BNG 110 only stores a data plan Identifier (ID) associated with the hybrid data plans, with entitlements such as quota, validity, and network policies being retrieved from the local catalog at the time when the hybrid data plan is moved from the plan queue to the plan stack. The implementation of the hybrid data plans eliminates the need to create duplicate records for the pre-paid and post-paid users (e.g., subscribers) in the database 210, thereby reducing redundancy and resulting in a more efficient and manageable database structure.

[0104] In order to manage the data plans, the processing engine 208 may be configured to receive a plan allocation request (e.g., data allocation request) corresponding to a UE (e.g., the UE 104) associated with a user (e.g., the user 102). In particular, the CHF-BNG 110 may be configured to receive the plan allocation request corresponding to the UE 104 from the SMF 112. The UE 104 may trigger the plan allocation request based on various factors, such as a data consumptionthreshold (e.g., 50%), an expiration of the active data plan, or a purchase of the hybrid data plan. Upon receiving the plan allocation request, the CHF-BNG 110 may be configured to determine an expiry of the active data plan and a quota associated with the active data plan corresponding to the UE 104. In one embodiment, when the active data plan is determined to be not expired, the CHF- BNG 110 is configured to allocate remaining data of the active data plan to the UE 104 in response to receiving the plan allocation request. In another embodiment, when the active data plan is determined to be expired, the CHF-BNG 110 is configured to perform a check to determine one of a presence or an absence of the hybrid data plan corresponding to the UE 104 in a plan stack. The plan stack refers to a data structure that is configured to hold the active data plan that is currently in use along with the hybrid data plans.

[0105] In an embodiment, upon determining the presence of the hybrid data plan corresponding to the UE 104 in the plan stack, the CHF-BNG 110 is configured to allocate data to the UE 104 based on the hybrid data plan present in the plan stack. In another embodiment, upon determining the absence of the hybrid data plan corresponding to the UE 104 within the plan stack, the CHF-BNG 110 is configured to perform a check to determine one of a presence or an absence of the hybrid data plan in a plan queue. The plan queue is a temporary holding area for new data plans (or the hybrid data plans) awaiting activation, which are moved into the plan stack either manually or automatically when the active data plan expire, or its quotas is depleted. In an embodiment, upon determining the absence of the hybrid data plan within the plan queue, the CHF-BNG 110 is configured to reject the plan allocation request received corresponding to the UE 104 from the SMF 112.

[0106] In another embodiment, upon determining the presence of the hybrid data plan in the plan queue, the CHF-BNG 110 is configured to transfer the hybrid data plan from the plan queue to the plan stack. Once the hybrid data plan is transferred from the plan queue to the plan stack, then a re-check is performed to determine one of the presence or the absence of the hybrid data plan in the plan stack. Further, based on performing the check, upon determining the presence of the hybrid data plan within the plan stack, the data associated with the hybrid dataplan is allocated to the UE 104. This complete method of managing the data plans is further explained in detail in conjunction with FIGS 3 and 4.

[0107] The hybrid data plans are designed and provisioned a database (e.g., the database 210) associated with the CHF-BNG 110 using the local catalog. The local catalog refers to a comprehensive listing and management document including details of various products and services, including mobile plans, data packages, broadband services, digital services, and value-added services offered by a network service provider. This provisioning of the hybrid data plans in the database ensures that the hybrid data plans are properly configured and available for use. Further, these hybrid data plans can be purchased by the subscribers based on a current available quota and a number of days left in an existing bill cycle period. The hybrid data plans operate on a pay-as-you-go basis and are applicable to both pre-paid and post-paid subscribers.

[0108] In an embodiment, the CHF-BNG 110 is configured to store the plans (i.e., the active data plans and the hybrid data plans) in an associated database, e.g., the database 210 (also referred to as a local catalog) including essential details of the plans, such as a plan type, a plan category, entitlements, a plan validity, a policy associated with the data plan, and a queue-to stack flag. The plan type may include, a rental plan, a pre-paid plan, a post-paid plan, a hybrid plan (i.e., the hybrid data plan), and the like. The plan category may include a data plan, a voice plan, etc. The entitlements may include a provided data quota, voice minutes, text messages, etc. The plan validity may include a fixed validity (e.g., 30 days data plan), a custom validity (e.g., data plan validity linked to data usage), etc. The policy associated with the data plan may include a data usage policy (e.g., apply data throttling after 50 GB usage), a roaming policy (e.g., enable international roaming with additional charges), and the like. This essential detail of the data plans helps the CHF-BNG in managing and implementing the data plans effectively for each subscriber.

[0109] Further, the database 210 stores data of the plan stack and the plan queue corresponding to the UE using the MAC ID. In this way, the plan stack and the plan queue analysis are performed by extracting data corresponding to the plan stack and plan queue from the database 210 by using the MAC ID.

[0110] Although FIG. 2 shows exemplary components of the system 108, in other embodiments, the system 108 may include fewer components, different components, differently arranged components, or additional functional components than depicted in FIG. 2. Additionally, or alternatively, one or more components of the system 108 may perform functions described as being performed by one or more other components of the system 108.

[0111] FIG. 3 illustrates an exemplary architecture 300 of the system 108 configured for managing the data plans in the telecommunication network, in accordance with an embodiment of the present disclosure. FIG. 3 is explained in conjunction with FIGS. 1 and 2. Examples of the telecommunication network may include, the 4G network, the 5G network, the 6G network, and the like.

[0112] In FIG. 3, a Packet Gateway (PGW) 302, a Fault Management System (FMS) 308, an Evolved Packet Core (EPC) 310, a Subscriber Profile Repository (SPR) 312, the CHF-BNG 110 is depicted. Further, the PGW 302 may include a plan provisioning module 304 and a customer (i.e., a subscriber) provisioning module 306. The PGW 302, the FMS 308, the EPC 310, the SPR 312, and the CHF- BNG 110 are configured to communicate with each other to manage the data plans for each subscriber.

[0113] In an embodiment, the PGW 302 acts a central element that manages data sessions, routes subscriber data, and connects a mobile network to external networks, such as the internet. The PGW 302 handles tasks such as an Internet Protocol (IP) address allocation, policy enforcement, and billing. The PGW 302 plays a key role in managing data traffic and ensuring that data flows efficiently between the mobile network and the external networks.

[0114] The plan provisioning module 304 is responsible for provisioning and managing the data plans (i.e., the active data plans and the hybrid data plans). The plan provisioning module 304 configures and updates the hybrid data plan available to a subscriber, ensuring that the hybrid data plan is correctly applied based on a subscriber profile and a status (e.g., expired or available) of the active data plan.

[0115] The customer provisioning module 306 handles a subscriber specific provisioning, which includes associating each subscriber with appropriate dataplans including the active data plans and the hybrid data plans. The customer provisioning module 306 ensures that each subscriber’s account is set up with a correct data plan details and entitlements. The plan provisioning module 304 and the customer provisioning module 306 utilize the MAC ID to efficiently identify and manage each subscriber profile and their associated data plans. By leveraging the MAC ID, the plan provisioning module 304 and the customer provisioning module 306 can quickly access and update subscriber information, ensuring accurate configuration of both active and hybrid data plans based on the subscriber’s current status and profile. This approach reduces latency in data fetching and enhances overall provisioning accuracy. In an aspect, the MAC ID is used to streamline subscribers’ data and session retrieval, reducing data fetching latency significantly. The MAC ID efficiently retrieves the subscribers’ information regardless of whether they are post-paid subscribers or pre-paid subscribers. In other words, the MAC ID is used as a single universal identifier applicable in case of both type of the subscribers, i.e. the post-paid subscribers and the pre-paid subscribers. The MAC ID based recharge is introduced to support multi-user subscribers where one Outdoor Customer Premise Equipment (ODCPE) can be connected with up to a pre-defined number of subscribers, e.g., seven subscribers or more.

[0116] The FMS 308 is configured to monitor and manage faults and issues within the telecommunication network (e.g., the network 106), including those related to the data plans provisioning and usage. The FMS 308 identifies and resolves the issues that may arise while allocating the data plans, such as plan provisioning errors or service disruptions, to maintain seamless service delivery. The EPC 310 provides a core network functionality for managing the data traffic and user sessions. The EPC 310 interacts with the PGW 302 to enforce and apply the data plans, ensuring that the data usage is monitored and managed according to provisions set by each data plan.

[0117] The SPR 312 (i.e., the local catalog) is configured to store profiles of each subscriber, including information about their data plans, entitlements, and usage history. The SPR 312 provides the necessary subscriber data to the PGW 302and the EPC 310 to ensure that a right data plan features and limits are applied during the telecommunication network interactions. Further, the CHF-BNG 110 integrates with the PGW 302 and the EPC 310 to manage charging aspects of the data plans for each subscriber. The CHF-BNG 110 ensures that the data usage is accurately tracked and billed according to the provisions set for the data plan of each subscriber. The CHF-BNG 110 is configured to handle an application of policies and quota management based on the data plans configured in a system (e.g., the system 108). In other words, the CHF-BNG 110 is responsible for enforcing the policies and the quota for a data plan selected by the subscriber according to the policies and the quota stored in the database (i.e., the data 210) associated with the system 108 for the selected data plan. The CHF-BNG 110 ensures that the subscribers' data usage adheres to the configured policies and the quota associated with their data plans.

[0118] FIG. 4 illustrates an exemplary flow diagram of a method 400 for managing the data plans in the telecommunication network, in accordance with an embodiment of the present disclosure. FIG. 4 is explained in conjunction with FIGS. 1, 2 and 3. The data plans may include the active data plans and the hybrid data plans.

[0119] At step 402, the method 400 starts managing the data plans for the users (e.g., subscribers).

[0120] At step 404, the SMF is configured to send the data allocation request to the CHF-BNG (i.e., the CHF-BNG 110). The data allocation request may be received for the UE 104 associated with a user (i.e., the subscriber).

[0121] At step 406, upon receiving the data allocation request, the CHF-BNG 110 is configured to perform a check to determine the expiry of a rental plan (i.e., active data plan) and the quota associated with the active data plan for the UE 104.

[0122] At step 408, based on the check performed at step 406, upon determining that the active data plan is not expired, the data available in the active data plan (i.e., the active rental plan) may be allocated to the UE 104 in response to receiving the data allocation request.

[0123] At step 410, once the data is allocated, the process 400 ends.

[0124] At step 412, based on the check performed at step 406, upon determining that the active data plan and the quota associated with the active data plan has expired, the CHF-BNG 110 is configured to determine one of the presence or the absence of the hybrid data plan corresponding to the UE 104 in the plan stack. In other words, the CHF-BNG 110 is configured to check whether a valid hybrid data plan is present for the UE 104 in the plan stack or not.

[0125] At step 414, based on performing the check at step 412, when the valid hybrid data plan is present in the plan stack, the CHF-BNG 110 is configured to allocate the data associated with the valid hybrid data plan to the UE 104 in response to receiving the data allocation request.

[0126] At step 416, when the data associated with the hybrid data plan is allocated, the process 400 ends.

[0127] At step 418, based on performing the check at step 412, when the valid hybrid data plan is determined to be absent in the plan stack, the CHF-BNG 110 is configured to determine one of the presence or the absence of the hybrid data plan corresponding to the UE 104 in the plan queue. In other words, the CHF-BNG 110 is configured to check whether the valid hybrid data plan is present for the UE 104 in the plan queue or not.

[0128] At step 420, upon determining the absence of the valid hybrid data plan in the plan queue, the CHF-BNG 110 is configured to reject the data allocation request corresponding to the UE 104. Once the data allocation request is rejected by the CHF-BNG 110, the process 400 ends.

[0129] At step 422, upon determining the presence of the valid hybrid data plan in the plan queue, the CHF-BNG 110 is configured to transfer the hybrid data plan form the plan queue to the plan stack.

[0130] Once the hybrid data plan is transferred from the plan queue to the plan stack, then step 412, step 414, and step 418 are re-executed to allocate the data associated with the hybrid data plan to the UE 104 as depicted by the process 400.

[0131] In an aspect, if the hybrid data plan is provisioned in the plan stack, then a validity of the hybrid data plan starts immediately from day one and expires according to terms of the hybrid data plan or the active data plan. For instance, whenthe hybrid data plan is the dependent data plan (e.g., an add-on plan), then in this case, the validity of the hybrid data plan will depend upon the validity of the active data plan. Further, if the hybrid data plan is provisioned in the plan queue, the validity begins when the hybrid data plan is moved from the plan queue to the plan stack, avoiding activation of rental charges of the hybrid data plan until the movement of the hybrid data plan from the plan queue to the plan stacks. In other words, the validity of the hybrid data plan in the plan queue will being from a day on which the hybrid data plan is moved from the plan queue to the plan stack. In an embodiment, the hybrid data plans remain active and can be used until their expiry, even after a bill cycle has run, whereas a normal post-paid plans expire at an end of the billing cycle. This provides extended usability of the hybrid data plans (also referred to as pre-over post plans) for the subscribers.

[0132] FIG. 5 illustrates an exemplary flow diagram of a method 500 for managing plans in the network, in accordance with an embodiment of the present disclosure.

[0133] At step 502, the method 500 includes receiving, by the first network component 110, a plan allocation request corresponding to the UE 104, from the second network component 112. The first network component 110 is Charging Function-Broadband Network Gateway (CHF)-(BNG) and the second network component 113 is a Session Management Function (SMF). The at least one plan comprises a pre-paid plan, a post-paid plan and a hybrid plan. In an aspect, the user 102 may request a new plan by sending the plan allocation request to the SMF 112. The SMF 112 forwards the plan allocation request (e.g., data allocation request) to the CHF-BNG 110.

[0134] At step 504, the method 500 includes extracting, by the first network component 110, a first set of parameters from the received plan allocation request. The first set of parameters comprises a Media Access Control (MAC) Identifier (ID). In an aspect, the CHF-BNG 110 extracts the MAC ID from the plan allocation request. The MAC ID is associated with the user. The user and session details are extracted from the database 210 using the MAC ID.

[0135] At step 506, the method 500 includes determining, by the first network component 110, whether at least one active plan and a quota associated with the at least one active plan corresponding to the UE 104 in a plan stack is expired based on the extracted first set of parameters. In an aspect, the user and session details comprise, but are not limited to, UE identity information (e.g., IMEI, IMSI etc.), session identifier, plan data (e.g., active plan, data usage, remaining data, etc.), connection details (e.g., access point name, session start time, session end time, network type (e.g., 4G, 5G, 6G, etc.)), roaming information, add-on services, policy information, etc. Based on the extracted user and session details, the CHF-BNG 110 determines whether the active plan and the quota associated with the active plan has expired or not.

[0136] At step 508, the method 500 includes upon determining, identifying, by the first network component 110, fulfilment of one or more conditions associated with at least one plan corresponding to the UE 104. The one or more conditions comprises of detection of one of a presence or absence of the at least one plan corresponding to the UE 104 in the plan stack and a plan queue. In an aspect, when the active plan and the quota associated with the active plan, the CHF-BNG 110 performs detection of the presence and absence of the plan corresponding to the UE 104 in the plan stack and the plan queue. Upon determining the at least one active plan and the quota associated with the at least one active plan corresponding to the UE 104 in the plan stack is not expired, performing, by the first network component 110, allocation available in the at least one active plan to the UE 104 based on the plan allocation request. In an aspect, when the active plan and the quota associated with the active plan has not expired, the CHF-BNG 110 may perform allocation of the active plan.

[0137] At step 510, the method 500 includes upon identifying, performing, by the first network component 110, one or more operations associated with the at least one plan. The one or more operations comprise transfer of the at least one plan from the plan queue to the plan stack. In an aspect, based on determination of presence and absence of the plan in the plan stack and the plan queue, the CHF-BNG 110performs the operations such as transfer of the plan from the plan queue to the plan stack or reject the plan allocation request.

[0138] In an aspect, upon determining the presence of the plan within the plan stack, performing, by the first network component 110, allocation associated with the plan to the UE based on the plan allocation request. When the plan is present in the plan stack, the CHF-BNG 110 performs allocations (e.g., data, voice call) of the plan to the UE.

[0139] In an aspect, upon determining the absence of the at least one plan within the plan stack, determining, by the first network component 110, one of a presence or an absence of the at least one plan corresponding to the UE 104 in the plan queue. When the plan is absent in the plan stack, the CHF-BNG 110 determines whether the plan is present in the plan queue.

[0140] In an aspect, upon determining the presence of the at least one plan within the plan queue, transferring, by the first network component 110, the at least one plan from the plan queue to the plan stack for performing allocation associated with the at least one plan to the UE 104 based on the plan allocation request and activating, by the first network component 110, the at least one plan on the UE 104. When the plan is present in the queue, the CHF-BNG 110 performs allocations (e.g., data, voice calls) of the plan to the UE 104. The CHF-BNG 110 activates the plan on the UE 104.

[0141] In an aspect, upon determining the absence of the plan within the plan queue, rejecting, by the first network component 110, the plan allocation request. When the plan is absent in the plan queue, the CHF-BNG 110 rejects the plan allocation request.

[0142] In an aspect, transferring of the plan from the plan queue to the plan stack is based upon a priority order according to a plan priority and recharge dates, each data plan is assigned a priority level based on a subscription type (e.g., a prepaid subscription and a post-paid subscription), service level agreements, or network policies. The data plans with higher priority levels are given precedence during the movement from the plan queue to the plan stack.

[0143] In an aspect, the at least one plan comprising of either a dependent plan or an independent plan. The method 500 includes transferring, by the first network component 110, the dependent plan into the plan stack and transferring, by the first network component 110, the independent plan either in the plan stack or in the plan queue based on expiry of the at least one active plan, expiry of the quota associated with the at least one active plan and a plan flag status, the execution unit 220 is configured to transfer the dependent plan into the plan stack. The independent plan is transferred either in the plan stack or in the plan queue based on expiry of the at least one active plan, expiry of the quota associated with the at least one active plan and a plan flag status. In an embodiment, whenever a subscriber associated with the UE 104 does a recharge with a new plan (i.e., the hybrid data plan), the CHF BNG 110 checks the local catalog to determine if the new plan is a dependent plan or an independent plan, considering an associated plan flag. The plan flag helps determining how the new plan should be processed in relation to the existing active plan. In other words, the plan flag helps in determining whether the new plan should be stored in the plan queue for later application after the expiry of the existing active plan (e.g., active data plan) or should be immediately stored in the plan stack with the existing active plan.

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

[0145] As shown in FIG. 6, the computer system 600 may include an external storage device 610, a bus 620, a main memory 630, a read-only memory 640, a mass storage device 650, communication port(s) 660, and a processor 670. A person skilled in the art will appreciate that the computer system 600 may include more than one processor and communication ports. The processor 670 may include various modules associated with embodiments of the present disclosure. The communication port(s) 660 may be any of an RS-232 port for use with a modembased 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 port(s) 660 may be chosen depending on a network, such a LocalArea Network (LAN), Wide Area Network (WAN), or any network to which the computer system 600 connects.

[0146] The main memory 630 may be a Random Access Memory (RAM), or any other dynamic storage device commonly known in the art. The read-only memory 640 may be any static storage device(s) e.g., but not limited to, a Programmable Read Only Memory (PROM) chips for storing static information e.g., start-up or Basic Input / Output System (BIOS) instructions for the processor 670. The mass storage device 650 may be any current or future mass storage solution, which can be used to store information and / or instructions. Exemplary mass storage device 650 includes, but is 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), one or more optical discs, Redundant Array of Independent Disks (RAID) storage, e.g. an array of disks.

[0147] The bus 620 communicatively couples the processor 670 with the other memory, storage, and communication blocks. The bus 620 may be, e.g. a Peripheral Component Interconnect (PCI) / PCI Extended (PCLX) 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 670 to the computer system 600.

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

[0149] While the foregoing describes various embodiments of the invention, other and further embodiments of the invention may be devised without departing from the basic scope thereof. The scope of the invention is determined by the claims that follow. The invention is not limited to the described embodiments, versions orexamples, which are included to enable a person having ordinary skill in the art to make and use the invention when combined with information and knowledge available to the person having ordinary skill in the art.

[0150] The method and system of the present disclosure may be implemented in a number of ways. For example, the methods and systems of the present disclosure may be implemented by software, hardware, firmware, or any combination of software, hardware, and firmware. The above-described order for the steps of the method is for illustration only, and the steps of the method of the present disclosure are not limited to the order specifically described above unless specifically stated otherwise. Further, in some embodiments, the present disclosure may also be embodied as programs recorded in a recording medium, the programs including machine-readable instructions for implementing the methods according to the present disclosure. Thus, the present disclosure also covers a recording medium storing a program for executing the method according to the present disclosure.

[0151] The exemplary computer system (600) is configured to execute 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 for managing plans in a network. The method comprises receiving, by a first network component, a plan allocation request corresponding to a user equipment (UE), from a second network component and extracting, by the first network component, a first set of parameters from the received plan allocation request. The method further comprises determining, by the first network component, whether at least one active plan and a quota associated with the at least one active plan corresponding to the UE in a plan stack is expired based on the extracted first set of parameters and upon determining, identifying, by the first network component, fulfilment of one or more conditions associated with at least one plan corresponding to the UE. The one or more conditions comprises of detection of one of a presence or absence of the at least one plan corresponding to the UE in the plan stack and a plan queue. The method comprises upon identifying, performing, by the first network component, one or more operationsassociated with the at least one plan. The one or more operations comprise transfer of the at least one plan from the plan queue to the plan stack.

[0152] In an aspect, the CHF BNG handles a hybrid plan (also referred to as pre-over-post plan) based on a MAC ID. The MAC ID enables indexed searching of customer data and sessions. In the hybrid plan provisioning, the system checks for any existing active plans and available quotas within a plan stack. When the plan is already available in the stack, the CHF-BNG moves a new plan (i.e., an independent plan) to a plan queue. However, if the existing plan has expired, its quota is exhausted, or it is dependent, the CHF-BNG moves the new plan directly into the plan stack. If the plan is provisioned in the queue, it can be moved manually or automatically into the plan stack when the existing plan expires. The movement of plans from the plan queue to the plan stack is based on a priority order according to the plan priority and recharge dates (i.e., FIFO basis). During recharges, the CHF- BNG only stores the plan ID, while the parameters (e.g., quota, validity, and policy) are fetched from a local catalog at the time of plan movement. If the plan is provisioned in the plan stack, the plan validity will start from day 1 and expire after its validity, but if the plan is in the plan queue, its validity will begin at the time of plan movement.

[0153] While considerable emphasis has been placed herein on the preferred embodiments, it will be appreciated that many embodiments can be made and that 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 disclosure herein, 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.

[0154] The present disclosure provides technical advancement related to managing data plans in a network. The advancement addresses the limitations of existing solutions by providing flexibility to the subscribers in managing their data plans by using a Media Access Control (MAC) Identifier (ID) to maintain each subscriber profile. The subscribers easily access and manage hybrid data plans aswell as existing active data plans. The subscribers select the hybrid data plan that best fits their needs, without being restricted by an associated subscription type. The hybrid data plans eliminate the need to create duplicate records for a pre-paid and a post-paid subscriber in the database, thereby reducing redundancy and resulting in a more efficient and manageable database structure. The hybrid data plans handling efficiently manages the hybrid data plans over the active data plans using a stack or a queue approach to ensure efficient processing of plan allocation requests. The use of the MAC ID enables precise and efficient processing of the hybrid data plans, as well as stack and queue analysis.ADVANTAGES OF THE PRESENT DISCLOSURE

[0155] The present disclosure provides a method and a system for managing data plans in a telecommunication network.

[0156] The present disclosure provides flexibility to the subscribers in managing their data plans by using a Media Access Control (MAC) Identifier (ID) to maintain each subscriber profile. This approach allows the subscribers to easily access and manage hybrid data plans as well as existing active data plans, by enabling the subscribers to select a hybrid data plan that best fits their needs, without being restricted by an associated subscription type.

[0157] The present disclosure provides an optimized process for managing a database by implementing the hybrid data plans that can be assigned to both prepaid and post-paid subscribers. The implementation of the hybrid data plans eliminates the need to create duplicate records for a pre-paid and a post-paid subscriber in the database, thereby reducing redundancy and resulting in a more efficient and manageable database structure.

[0158] The present disclosure provides an approach that offers comprehensive recharge options to the subscribers. The hybrid data plans (also referred to as pre- over post plans) are designed to serve both the pre-paid and the post-paid subscribers with active rental plans (i.e., the active data plans), providing a wide range of recharge options for all types of the subscribers. The integration of the hybrid data plans into recharges options enhances the choices available for thesubscribers, ensuring the subscribers can easily recharge regardless of their subscription type.

[0159] The present disclosure provides prioritized the hybrid data plans handling by managing the hybrid data plans over the active data plans using a stack or a queue approach to ensure efficient processing of plan allocation requests. The hybrid data plans in the stack are given priority, ensuring that the subscribers with the active rental plans receive prompt service. When the stack is empty, the hybrid data plans are automatically moved to the stack, maintaining a continuous flow of service without delays. This queue-to-stack movement enhances subscriber benefits by starting rental or validity only when a hybrid data plan is actually needed, rather than from a date of recharging the hybrid data plan.

[0160] The present disclosure provides automated data plans management. For automating data plans management, the system prioritizes a hybrid data plan in a queue when an active data plan in the stack expires and activates a queue-to-stack Application Programming Interface (API) to ensure seamless service. The queue- to-stack API ensures that the hybrid data plan is moved from the queue to the stack without requiring a manual input from the subscriber or a network service provider by generating a trigger upon detecting an expiry of the data plan (i.e., the active data plan or the hybrid data plan) present in the stack. This automation minimizes the need for manual intervention, streamlines data plans management, and ensures uninterrupted service for the subscribers.

[0161] The present disclosure facilitates direct access to the subscribers and session details associated with them by using the MAC ID as a primary identifier for each subscriber. The use of the MAC ID enables precise and efficient processing of the hybrid data plans, as well as stack and queue analysis.

[0162] The present disclosure provides flexibility of pre-over post plans (i.e., the hybrid data plans) to the subscribers. The hybrid data plans offer the flexibility to boost an existing active data plan speed, which is not available with standard post-paid plans where policy inheritance from the existing data plan limits speed upgrades.

Claims

CLAIMSWe Claim:

1. A method 500 for managing plans in a network 106, the method 500 comprising: receiving 502, by a first network component 110, a plan allocation request corresponding to a user equipment (UE) 104, from a second network component 112; extracting 504, by the first network component 110, a first set of parameters from the received plan allocation request; determining 506, by the first network component 110, whether at least one active plan and a quota associated with the at least one active plan corresponding to the UE 104 in a plan stack is expired based on the extracted first set of parameters; upon determining, identifying 508, by the first network component 110, fulfilment of one or more conditions associated with at least one plan corresponding to the UE 104, wherein the one or more conditions comprises of detection of one of a presence or absence of the at least one plan corresponding to the UE 104 in the plan stack and a plan queue; and upon identifying, performing 510, by the first network component 110, one or more operations associated with the at least one plan, wherein the one or more operations comprise transfer of the at least one plan from the plan queue to the plan stack.

2. The method 500 as claimed in claim 1, wherein the first network component 110 is Charging Function-Broadband Network Gateway (CHF)-(BNG) and the second network component 112 is a Session Management Function (SMF).

3. The method 500 as claimed in claim 1, wherein the first set of parameters comprises a Media Access Control (MAC) Identifier (ID).

4. The method 500 as claimed in claim 1, wherein the at least one plan comprises a pre-paid plan, a post-paid plan and a hybrid plan.

5. The method 500 as claimed in claim 1, further comprising: upon determining the absence of the at least one plan within the plan stack, determining, by the first network component 110, one of a presence or an absence of the at least one plan corresponding to the UE 104 in the plan queue; upon determining the presence of the at least one plan within the plan queue, transferring, by the first network component 110, the at least one plan from the plan queue to the plan stack for performing allocation associated with the at least one plan to the UE 104 based on the plan allocation request; and activating, by the first network component 110, the at least one plan on the UE 104.

6. The method 500 as claimed in claim 1, wherein upon determining the presence of the plan within the plan stack, performing, by the first network component 110, allocation associated with the plan to the UE 104 based on the plan allocation request.

7. The method 500 as claimed in claim 5, wherein upon determining the absence of the plan within the plan queue, rejecting, by the first network component 110, the plan allocation request.

8. The method 500 as claimed in claim 1, wherein upon determining the at least one active plan and the quota associated with the at least one active plan corresponding to the UE 104 in the plan stack is not expired, performing, by the first network component 110, allocation available in the at least one active plan to the UE 104 based on the plan allocation request.

9. The method 500 as claimed in claim 1, wherein transferring of the plan from the plan queue to the plan stack is based upon a priority order according to a plan priority and recharge dates.

10. The method 500 as claimed in claim 5, wherein the at least one plan comprising of either a dependent plan or an independent plan.

11. The method 500 as claimed in claim 10, further comprising: transferring, by the first network component 110, the dependent plan into the plan stack; and transferring, by the first network component 110, the independent plan either in the plan stack or in the plan queue based on expiry of the at least one active plan, expiry of the quota associated with the at least one active plan and a plan flag status.

12. A system 108 for managing plans in a network 106, the system 108 comprising a first network component 110 and a second network component 112, the first network component 110 comprising: a receiving unit 212 configured to receive a plan allocation request corresponding to a user equipment (UE) 104 from a second network component 112; an extraction unit 214 configured to extract a first set of parameters from the received plan allocation request; a determining unit 216 configured to determine whether at least one active plan and a quota associated with the at least one active plan corresponding to the UE 104 in a plan stack is expired based on the extracted first set of parameters; upon determining, an identification unit 218 is configured to identify fulfilment of one or more conditions associated with at least one plan corresponding to the UE 104, wherein the one or more conditionscomprises of detection of one of a presence or absence of the at least one plan corresponding to the UE 104 in the plan stack and a plan queue; and upon identifying, an execution unit 220 is configured to perform one or more operations associated with the at least one plan, wherein the one or more operations comprise transfer of the at least one plan from the plan queue to the plan stack.

13. The system 108 as claimed in claim 12, wherein the first network component 110 is Charging Function-Broadband Network Gateway (CHF)-(BNG) and the second network component 112 is a Session Management Function (SMF).

14. The system 108 as claimed in claim 12, wherein the first set of parameters comprises a Media Access Control (MAC) Identifier (ID).

15. The system 108 as claimed in claim 12, wherein the at least one plan comprises a pre-paid plan, a post-paid plan and a hybrid plan.

16. The system 108 as claimed in claim 12, wherein upon determining the absence of the at least one plan within the plan stack, the determining unit 216 is configured to determine one of a presence or an absence of the at least one plan corresponding to the UE 104 in the plan queue; and upon determining the presence of the at least one plan within the plan queue, the execution unit 220 is configured to: transfer the at least one plan from the plan queue to the plan stack for performing allocation associated with the at least one plan to the UE 104 based on the plan allocation request; and activate the at least one plan on the UE 104.

17. The system 108 as claimed in claim 12, wherein upon determining the presence of the plan within the plan stack, the execution unit 220 is configured to perform allocation associated with the plan to the UE 104 based on the plan allocation request.

18. The system 108 as claimed in claim 16, wherein upon determining the absence of the plan within the plan queue, the execution unit 220 is configured to reject the plan allocation request.

19. The system 108 as claimed in claim 12, wherein upon determining the at least one active plan and the quota associated with the at least one active plan corresponding to the UE 104 in the plan stack is not expired, the execution unit 220 is configured to perform allocation available in the at least one active plan to the UE 104 based on the plan allocation request.

20. The system 108 as claimed in claim 12, wherein transferring of the plan from the plan queue to the plan stack is based upon a priority order according to a plan priority and recharge dates.

21. The system 108 as claimed in claim 12, wherein the at least one plan comprising of either a dependent plan or an independent plan.

22. The system 108 as claimed in claim 21, wherein the execution unit 220 is configured to: transfer the dependent plan into the plan stack; and transfer the independent plan either in the plan stack or in the plan queue based on expiry of the at least one active plan, expiry of the quota associated with the at least one active plan and a plan flag status.

23. A computer program product comprising a non-transitory computer- readable medium comprising instructions that, when executed by one ormore processors, cause the one or more processors to execute a method 500 for managing plans in a network, the method 500 comprising: receiving 502, by a first network component 110, a plan allocation request corresponding to a user equipment (UE) 104, from a second network component 112; extracting 504, by the first network component 110, a first set of parameters from the received plan allocation request; determining 506, by the first network component 110, whether at least one active plan and a quota associated with the at least one active plan corresponding to the UE 104 in a plan stack is expired based on the extracted first set of parameters; upon determining, identifying 508, by the first network component 110, fulfilment of one or more conditions associated with at least one plan corresponding to the UE 104, wherein the one or more conditions comprises of detection of one of a presence or absence of the at least one plan corresponding to the UE 104 in the plan stack and a plan queue; and upon identifying, performing 510, by the first network component 110, one or more operations associated with the at least one plan, wherein the one or more operations comprise transfer of the at least one plan from the plan queue to the plan stack.

Images