Method and system for managing service plan provisioning in a network

Abstract

The present disclosure provides a system (108) and method (500) for managing service plan provisioning in a network (106). The system (108) receives a request corresponding to provisioning of service plan from external entity. In response, the system (108) checks availability of primary network node, and upon confirming availability, the system (108) provisions service plan in primary network node. The primary network node is monitored to detect any error within predefined time interval. If no error is detected within predefined time interval, the system (108) schedules a plan provisioning task for a set of secondary network nodes after the predefined time interval of provisioning the service plan in primary network node. In case an error is detected, the system (108) terminates the scheduled provisioning task for secondary network nodes, and cancels provisioning in primary network node. By doing this, the system (108) prevents propagation of incorrect service plans across network.

Description

METHOD AND SYSTEM FOR MANAGING SERVICE PLAN PROVISIONING IN A 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 trade5 dress protection, belonging to JIO PLATFORMS LIMITED 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 fully10 reserved by the owner.TECHNICAL FIELD

[0002] The embodiments of the present disclosure generally relate to telecommunication network management. In particular, the present disclosure relates to a system and a method for managing service plan provisioning in a network.DEFINITION

[0003] The term ‘Plan provisioning’ used herein in the specification refers to a process of allocating and configuring a plurality of plans (e.g., service plans), such as air fiber recharge plans, to a specific super core (e.g., a primary super core) 0 within a telecommunication network.

[0004] The term ‘Super core’ used herein in the specification refers to a high-performance network node responsible for processing network traffic and executing the service plans.

[0005] The term ‘Primary super core’ used herein in the specification refers 5 to a main, designated network node or core in a telecommunication network where service plans are initially provisioned. This core serves as the primary point of execution for provisioning tasks and is prioritized for receiving service plans beforeany secondary cores. The primary super core is essential for ensuring that the service plans are deployed effectively and efficiently within the telecommunication network.

[0006] The term ‘Set of secondary super cores’ used herein in the specification refers to one or more network nodes or cores within the telecommunication network that are scheduled to receive provisioning tasks if the primary super core is unavailable or if provisioning in the primary super core is delayed. The set of secondary super cores receives provisioning tasks after a predefined time interval, ensuring that incorrect or wrong service plans are not propagated across the network. However, if any issue or error is detected in the primary super core within the predefined time interval, the provisioning task scheduled for the set of secondary super cores may be canceled.

[0007] The term ‘Fulfillment Management System (FMS)’ as used herein in the specification refers to a system responsible for managing and sending provisioning requests to network functions, including details about the network service plans to be provisioned.

[0008] The term ‘Provisioning Gateway’, as used herein in the specification, may refer to a centralized network component that is responsible for handling, scheduling, and executing the provisioning of service plans across multiple network nodes, such as super cores. The provisioning gateway acts as an intermediary system that receives provisioning requests, validates them, and ensures that service plans are delivered to the correct network nodes in a controlled and reliable manner.

[0009] The term ‘Centralized Command Line Interface (CLI)’ as used herein in the specification refers to a centralized management tool used to control and monitor the provisioning process across multiple provisioning gateways.

[0010] The term ‘Scheduled task’ as used herein in the specification refers to a planned operation to provision service plans to a specific super core at a predetermined time interval.BACKGROUND

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

[0012] In modem telecommunications networks, particularly in Fifth Generation (5G) and next-generation network architectures, the provisioning of service plans is a critical process. The provisioning of service plans involves configuring and allocating various service plans, such as air fiber recharge plans on a monthly basis, a quarterly basis, or a yearly basis to different super cores. The efficient and accurate provisioning of the service plans is crucial for delivering high-quality services to end users.

[0013] At present, the plan provisioning approaches often involve deploying the service plans to all network nodes (e.g., the super cores) simultaneously. This approach can present significant challenges, including propagation of errors throughout the super cores, increased signaling traffic, and administrative overhead, leading to network congestion and performance degradation. For example, if errors occur during the provisioning process, such as typographical errors in plan specifications, such as mistakenly setting a bandwidth to 1000 Mbps instead of 100 Mbps, it can lead to widespread service disruptions and inefficiencies. If not detected and corrected promptly, such errors can affect all the network nodes (e.g., super cores) receiving the plan. There is, therefore, a need for a system and a method that overcomes the limitations of the prior art.SUMMARY OF THE DISCLOSURE

[0014] In an exemplary embodiment, a method for managing service plan provisioning in a network is described. The method comprises receiving, by a receiving unit, a request corresponding to provisioning of at least one service plan from an external entity. The method comprises checking, by a provisioning unit, whether a primary network node is available in response to the received request. The method comprises provisioning, by the provisioning unit, the at least one service plan in the primary network node upon confirming availability of the primary network node. The method comprises monitoring, by the provisioning unit, the primary network node to detect at least one error in the primary network node within a predefined time interval of provisioning the at least one service plan. The method comprises, upon detecting no error in the primary network node within the predefined time interval, scheduling, by a scheduling unit, a plan provisioning task for a set of secondary network nodes after the predefined time interval of provisioning the at least one service plan in the primary network node. The method comprises, upon detecting the at least one error in the primary network node within the predefined time interval, terminating, by the scheduling unit, the scheduled plan provisioning task for the set of secondary network nodes and the provisioning of the at least one service plan in the primary network node.

[0015] In some embodiments, the external entity comprises a fulfillment management system (FMS).

[0016] In some embodiments, checking the availability of the primary network node comprises: accessing, by the provisioning unit, one or more parameters associated with the primary network node, and based on accessing the one or more parameters, determining, by the provisioning unit, an active state of the primary network node, wherein the active state indicates the availability of the primary network node.

[0017] In some embodiments, the one or more parameters comprise a health status of the primary network node, a maintenance schedule of the primary networknode, a response latency of the primary network node, and a configurability of the primary network node.

[0018] In some embodiments, the monitoring of the primary network node to detect the at least one error is one of: a real-time monitoring process and a periodic check monitoring process.

[0019] In some embodiments, upon detecting the at least one error in the primary network node within the predefined time interval, the method further comprises: receiving, by the scheduling unit, a termination request from a User Interface (UI), wherein the termination request corresponds to termination of the scheduled plan provisioning task for the set of secondary network nodes and the provisioning of the at least one service plan in the primary network node; and terminating, by the scheduling unit, the scheduled plan provisioning task and the provisioning of the at least one service plan in the primary network node in response to the termination request.

[0020] In some embodiments, the UI is located in a centralized Command Uine Interface (CUI).

[0021] In some embodiments, the at least one error comprises a configuration mismatch in the primary network node, an incorrect plan provisioning in the primary network node, a service failure during the plan provisioning, a network connectivity issue, an ongoing maintenance state of the primary network node, and a latency in a data transfer rate.

[0022] In another exemplary embodiment, a system for managing service plan provisioning in a network is described. The system comprises a receiving unit configured to receive a request corresponding to provisioning of at least one service plan from an external entity. The system comprises a provisioning unit configured to check whether a primary network node is available in response to the received request. The provisioning unit is configured to provision the at least one service plan in the primary network node upon confirming the availability of the primarynetwork node. The provisioning unit is configured to monitor the primary network node to detect at least one error in the primary network node within a predefined time interval of provisioning the at least one service plan. The system comprises a scheduling unit configured to schedule a plan provisioning task for a set of secondary network nodes after a predefined time interval of provisioning the at least one service plan in the primary network node upon detecting no error in the primary network node within the predefined time interval. The scheduling unit is configured to terminate the scheduled plan provisioning task for the set of secondary network nodes and the provisioning of the at least one service plan in the primary network node upon detecting the at least one error in the primary network node within the predefined time interval.

[0023] In an exemplary embodiment, a computer program product comprising a non-transitory computer-readable medium is disclosed. The medium includes instructions that, when executed by one or more processors, cause the one or more processors to execute a method for managing service plan provisioning in a network. The method comprises receiving, by a receiving unit, a request corresponding to provisioning of at least one service plan from an external entity. The method comprises checking, by a provisioning unit, whether a primary network node is available in response to the received request. The method comprises provisioning, by the provisioning unit, the at least one service plan in the primary network node upon confirming availability of the primary network node. The method comprises monitoring, by the provisioning unit, the primary network node to detect at least one error in the primary network node within a predefined time interval of provisioning the at least one service plan. The method comprises, upon detecting no error in the primary network node within the predefined time interval, scheduling, by a scheduling unit, a plan provisioning task for a set of secondary network nodes after the predefined time interval of provisioning the at least one service plan in the primary network node. The method comprises, upon detecting the at least one error in the primary network node within the predefined time interval, terminating, by the scheduling unit, the scheduled plan provisioning taskfor the set of secondary network nodes and the provisioning of the at least one service plan in the primary network node.

[0024] 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.OBJECTIVES OF THE PRESENT DISCLOSURE

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

[0026] An object of the present disclosure is to provide a system and a method for managing plan provisioning in a network.

[0027] Another object of the present disclosure is to enhance the efficiency of provisioning operations by provisioning service plans to a primary super core and scheduling a plan provisioning task for a set of secondary super cores only when no error is detected in the primary super core.

[0028] Another object of the present disclosure is to reduce the risk of widespread disruptions and service inconsistencies by addressing potential issues in the primary super core before executing scheduled tasks for secondary super cores.

[0029] Another object of the present disclosure is to provide a system and a method that enables early detection of errors, enhances overall network performance, efficient task management, and reduces unnecessary signaling traffic.

[0030] Another objective of the present disclosure is to improve latency in data rate by efficiently monitoring the errors before executing scheduled tasks.

[0031] Other objects 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.BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWINGS

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

[0033] FIG. 1 illustrates an exemplary network architecture of a system for managing service plan provisioning in a network, in accordance with an embodiment of the present disclosure.

[0034] FIG. 2 illustrates a block diagram of the system for managing service plan provisioning in the network, in accordance with an embodiment of the present disclosure.

[0035] FIG. 3 illustrates an exemplary system architecture for managing service plan provisioning in the network, in accordance with an embodiment of the present disclosure.

[0036] FIG. 4 illustrates an exemplary process flow diagram of a method for managing service plan provisioning in the network, in accordance with an embodiment of the present disclosure.

[0037] FIG. 5 illustrates a flow diagram of a method for managing service plan provisioning in the network, in accordance with an embodiment of the present disclosure.

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

[0039] 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 - System200 - Block diagram202 - Processor(s)204 - Memory206 - Interface(s)208 - Database210 - Receiving Unit212 - Provisioning Unit214 - Scheduling Unit300 - System architecture302 - Fulfdlment management system (FMS)304 - Provisioning Gateway306 - Command Line Interface (CLI)400 - Process Flow500 - Method600 - Computer system610 - External storage device620 - Bus630 - Main Memory640 - Read Only Memory650 - Mass Storage Device660 - Communication Port670 - ProcessorDETAILED DESCRIPTION OF DISCLOSURE

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

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

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

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

[0025] 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 constmed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniquesknown to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive in a manner similar to the term “comprising” as an open transition word without precluding any additional or other elements.

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

[0027] 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 withoutdeparting from the scope of the invention as defined herein. It should be noted that the terms “graphical user interface” and “user interface” are used interchangeably for the purpose of describing the invention. Also, the terms “software” and “firmware” are used interchangeably for the purpose of describing the invention.

[0028] 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 the other 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.

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

[0030] As portable electronic devices and wireless technologies continue to improve and grow in popularity, the advancing wireless technologies for data transfer are also expected to evolve and replace the older generations of technologies. In the field of wireless data communications, the dynamic advancement of various generations of cellular technology is also seen. The development, in this respect, has been incremental in the order of second generation (2G), third generation (3G), fourth generation (4G), and now fifth generation (5G), and more such generations are expected to continue in the forthcoming time.

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

[0032] In modem telecommunications networks, accurate and efficient service plan provisioning is critical for maintaining network performance and ensuring customer satisfaction. However, current approaches to plan provisioning, particularly in large and complex networks, may have challenges that can lead to significant operational inefficiencies and service disruptions.

[0033] In conventional approaches, service plans are often deployed simultaneously to multiple network nodes without sufficient checks being performed for potential errors in the plan specifications. For example, a typographical mistake, such as provisioning a 5 GB plan instead of a 50 GB plan. If not detected early, such errors may affect all network nodes (e.g., super cores) that receive the provisioning, resulting in significant downtime, customer dissatisfaction, and resource wastage.

[0034] Another challenge is the inefficient management of scheduling tasks, particularly when dealing with multiple network nodes or super cores. In many cases, the absence of a proper mechanism to handle errors and manage task scheduling delays service provisioning and increases signaling traffic. This may cause network congestion, increased administrative overhead, and overall performance degradation.

[0035] Furthermore, the lack of a mechanism to address issues detected in the primary super core before executing tasks on secondary super cores exacerbates these challenges. Without the ability to halt or modify scheduled provisioning tasks based on real-time error detection, networks are prone to unnecessary task execution, which may strain resources and lead to inefficiencies.

[0036] To address the challenges associated with the above-mentioned problems, the present disclosure provides a method and a system for managing service plan provisioning in a network. The system includes a provisioning gateway that receives plan provisioning requests from a Fulfilment Management System (FMS). Upon receiving the request, the provisioning gateway initially checks whether a primary super core is available or not. If the primary super core is available, the provisioning gateway provisions the service plan to the primary super core. If the primary super core is unavailable, a plan provisioning task is scheduled to be executed on all the other secondary super cores after a predefined time interval.

[0037] The present disclosure detect errors in the primary super core before executing the scheduled tasks on the set of secondary super cores. If an issue is identified within the predefined time interval, a Centralized Command Line Interface (CLI) or User Interface (UI) may be used to cancel the scheduled tasks, thereby preventing the propagation of errors across the set of secondary super cores. This approach not only improves the accuracy and reliability of plan provisioning but also enhances the overall efficiency of network operations by reducing unnecessary signaling and administrative effort.

[0038] By implementing the proposed method and system, the network may achieve greater stability, reduce the risk of service disruptions, and optimize the use of network resources. The proposed solution thus provides an advancement over existing provisioning methods, offering a more robust and scalable approach to managing the service plan provisioning.

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

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

[0041] FIG. 1 illustrates an exemplary network architecture 100 of a system 108 for managing service plan provisioning in a network 106, in accordance with embodiments of the present disclosure. As illustrated in FIG. 1, the network architecture 100 may include one or more User Equipments (UEs) 104-1, 104-2, 104-3 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-3... 104-N may be collectively referred to as the UE 104 or the UEs 104. Although only four 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.

[0042] In an embodiment, the UE 104 may include smart devices operating in a smart environment, for example, 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, athermal, 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 / orentities, 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, multisensing, network-connected devices, that may integrate seamlessly with each other and / or with a central server or a cloud-computing system or any other device that is network-connected.

[0043] 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), awearable computer device (e.g., aheadmounted 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, a touch-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.

[0044] In FIG. 1, the UE 104 may communicate with the system 108 through the network 106 for sending or receiving various types of data. In an embodiment, the network 106 may include at least one of a 5th Generation (5G) network, a 6th 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 someother 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.

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

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

[0047] In an embodiment, the system 108 may receive a plan provisioning request from a Fulfilment Management System (FMS). Upon receiving the plan provisioning request, the system 108 identifies whether a primary network node (e.g., a single super core) is available or not. Upon determining that the primary network node is available, the system 108 provisions at least one service plan in the primary network node. Further, the system 108 monitors the primary network node to detect at least one error within a predefined time interval of provisioning the at least one service plan. Within this predefined time interval, if the system 108 detectsno error or issues, then the system 108 schedules a plan provisioning task to a set of secondary network nodes. Alternatively, if the system 108 detects errors and issues in the primary network node within the predefined time interval, then the system 108 receives a termination request via a User Interface (UI) from the user 102. Upon receiving this termination request, the scheduled plan provisioning task is terminated by the system 108 so that the set of secondary network nodes (i.e., the remaining super cores) remains unaffected.

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

[0045] FIG. 2 illustrates an exemplary block diagram 200 of the system 108 for managing service plan provisioning in the network 106, in accordance with an embodiment of the present disclosure. In some embodiments, the system 108 is embodied as a provisioning gateway. In some embodiments, the system 108 may be implemented in the provisioning gateway.

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

[0047] In an embodiment, the processor(s) 202 that may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processor 202. In examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for theprocessor 202 may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processor 202 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 processor 202. 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 processor 202 may be implemented by electronic circuitry or the Provisioning Gateway. In an embodiment, the processor(s) 202 may include one or more components, but are not limited to, a receiving unit 210, a provisioning unit 212, and a scheduling unit 214.

[0048] Among other capabilities, the one or more processor(s) 202 may be configured to fetch and execute computer-readable instructions stored in 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.

[0049] 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 (I / O), storage devices, and the like. The interface(s) 206 may facilitate communication through the system 108. The interface(s) 206 may also provide a communication pathway for one or more components of the system 108. Examples of such components include, but are not limited to, the processor 202 and a database 208.

[0050] In an embodiment, the database 208 may comprise data that may be either stored or generated as a result of functionalities implemented by any of the components of the processor(s) 202. In at least one example embodiment, the database 208 may be separate from the system 108.

[0051] In an embodiment, the receiving unit 210 may be configured to receive a request corresponding to provisioning of at least one service plan from an external entity. The external entity may include a Fulfillment Management System (FMS). The FMS is a centralized system that is responsible for handling customer service fulfillment operations. The FMS acts as the interface between customerfacing systems such as customer relationship management (CRM) platforms, retail channels, web portals etc, which are responsible for activating and managing service offerings. The FMS receives service order requests initiated by end users, either directly or through automated systems, and translates these high-level service requests into network specific provisioning commands. These network specific commands may include actions such as activation of new plans, modification of existing plans, or deactivation of services. Upon receiving commands, the FMS triggers a provisioning workflow and forwards the relevant instructions to the Provisioning Gateway (PGW). In an example, the request may be triggered by various actions such as a customer subscribing to a new plan, modifying an existing plan, or renewing a service. The FMS may be responsible for managing customer orders and service fulfillment, ensuring that the at least one service plan is accurately and efficiently provisioned across the super cores. The at least one service plan is one or more service configurations or service plans that needs to be provisioned to the PGW either in response to an end-user request or as newly created or updated plans purposely created for the end user. Examples of the at least one service plan may include, but are not limited to, an air fiber subscription plans, voice calling plans, and internet bandwidth allocation plans.

[0052] The request from the FMS may include all necessary details for provisioning, such as the type of the at least one service plan (e.g., internet bandwidth, voice calling, or air fiber subscription), a customer account information,1 and any specific parameters required for the plan (e.g., data limits, speed tiers, and duration of the service). The FMS is responsible for ensuring that all the information provided in the request is accurate and complete before sending it to the provisioning gateway.

[0053] In an embodiment, the provisioning unit 212 may be configured to check whether a primary network node is available in response to the received request. The primary network node is interchangeably referred to as a primary super core. The primary network node refers to a main, designated network node or core in the network where the at least one service plan is initially provisioned. The primary network node or primary super core serves as the primary point of execution for provisioning tasks and is prioritized for receiving the at least one service plan before any secondary network nodes or secondary super cores. The primary network node is essential for ensuring that the at least one service plan is deployed effectively and efficiently within the network 106. The purpose of checking the availability of the primary network node is to ensure that it can handle the received request without any issues, such as being overburdened, undergoing maintenance, or facing other operational constraints. This check is crucial because the primary network node is central to network efficiency, and any problems at the primary network node may significantly affect the service quality and the network performance.

[0054] In an aspect, to check the availability of the primary network node, the provisioning unit 212 may be configured to access one or more parameters associated with the primary network node . In an example, the provisioning unit 212 may access a network monitoring system or the database 210 to retrieve the one or more parameters associated with the primary network node in real-time. The one or more parameters comprise a health status of the primary network node, a maintenance schedule of the primary network node, a response latency of the primary network node, and a configurability of the primary network node. In an aspect, based on accessing the one or more parameters, the provisioning unit 212 is configured to determine an active state of the primary network node. The activestate indicates the availability of the primary network node. For example, the provisioning unit 212 may check the health status of the primary network node, which may include CPU utilization, memory usage, disk space, and software module status. The provisioning unit 212 may initiate a health-check request to the primary network node to confirm that it is currently active and functioning within a predefined acceptable performance thresholds. If the values such as the CPU utilization memory usage, disk space fall within the predefined acceptable thresholds, the primary network node is considered active.

[0055] Additionally, the provisioning unit 212 may access a centralized maintenance schedule repository to determine whether the primary network node is currently under maintenance or scheduled for downtime. If a maintenance window overlaps with the received request time, the primary network node may be marked as temporarily unavailable to prevent service interruption. Furthermore, the response latency of the primary network node may be evaluated by sending a test request and measuring the response time. If the response exceeds a defined latency threshold, the primary network node may be flagged as degraded or unstable, and provisioning may be halted or rerouted accordingly.

[0040] The configurability of the primary network node refers to its ability to support the specific service plan being requested. This may include checking whether the primary network node has the required configurations, service modules, or firmware versions to activate and manage the at least one service plan effectively.

[0041] In an embodiment, upon confirming availability of the primary network node, the provisioning unit 212 may be configured to provision the at least one service plan in the primary network node. The provisioning, in this context, refers to a process of configuring and activating the requested at least one service plan so that it becomes operational and accessible to the end user within the network. In an example, if the primary network node is available, the provisioning unit 212 may proceed to provision the at least one service plan in the database 208of the primary network node. For example, if the service plan is an air fiber subscription plan, it is immediately provisioned into the primary network node, allowing customers to access the service.

[0042] In an aspect, upon confirming the availability of the primary network node, the provisioning unit 212 may establish a secure connection with the primary network node (e.g., primary super core) using predefined communication protocols such as Representational State Transfer (REST) APIs, Simple Object Access Protocol (SOAP) based web services, or proprietary telecom protocols. Through this connection, the provisioning unit 212 may transmit configuration data for provisioning to the primary network node. Once the configuration data is received, the primary network node validates the configuration, applies the at least one service plan setting to its internal systems (such as policy control, subscriber data management, and billing interfaces), and activates the at least one service plan for the targeted subscribers (e.g., end users). In an aspect, the primary network node may return a success response or status code to the provisioning unit 212, confirming that the at least one service plan has been successfully provisioned.

[0043] In an embodiment, the provisioning unit 212 is configured to monitor the primary network node to detect at least one error in the primary network node within a predefined time interval of provisioning the at least one service plan. The predefined time interval refers to a configurable duration that begins immediately after the at least one service plan is provisioned to the primary network node. This time window is reserved for observing and validating the success or failure of the provisioning operation before any further actions are executed. The length of the interval may vary depending on network requirements and can range from a few seconds to several minutes. The predefined time interval ensures that the system 108 has sufficient time to detect and respond to any errors that may arise post-provisioning in the primary network node, thereby acting as a safeguard against propagating faulty configurations to the rest of the network. For example, if the predefined time interval is set to 30 minutes, the provisioning unit 212 may wait for 30 minutes after provisioning the primary network node. During this time,network administrators may observe the performance and stability of the primary network node.

[0044] In an aspect, the monitoring of the primary network node to detect the at least one error is one of a real-time monitoring process and a periodic check monitoring process. In a real-time monitoring process, the provisioning unit 212 may continuously listen for error logs, fault events, or failure signals generated by the primary network node. These may include alerts related to failed plan activation, service disruption, abnormal CPU / memory usage, or other unexpected system behaviour following the provisioning. In a periodic monitoring approach, the provisioning unit 212 may poll the primary network node at regular intervals, such as every few seconds or minutes, to retrieve health metrics and operational status updates. This may involve checking system logs, execution results, or subscriber feedback metrics to identify potential issues.

[0045] In an aspect, the at least one error comprises a configuration mismatch in the primary network node, an incorrect plan provisioning in the primary network node, a service failure during the plan provisioning, a network connectivity issue, an ongoing maintenance state of the primary network node, and latency in data transfer rate. In an example, the at least one error detection may be performed in two modes i.e., an automatic mode or a manual mode. In the manual mode, a network operator or administrator may validate the status of the primary network node through a centralized dashboard, such as the Command Line Interface (CLI), or a log analysis tool. If any provisioning-related anomaly is identified in the primary network node (e.g., incorrect bandwidth setting, failure to activate a plan, degradation in service quality), the user 102 (network operator) may manually intervene to flag or halt further provisioning actions.

[0046] In the automatic mode, the system 108 may utilize predefined rulebased logic or machine learning (ML) models trained to detect anomalies in the primary network node based on historical data. For example, an ML model may be trained to identify deviations in key performance indicators (KPIs), such asprovisioning response time, error codes, subscriber usage patterns, or node-level resource utilization. If the ML model detects abnormal behaviour such as sudden spikes in failure rates or unexpected drops in service response, it may automatically raise a flag or trigger corrective actions, including cancelling scheduled provisioning to the set of secondary network nodes.

[0047] In an embodiment, upon detecting no error in the primary network node within the predefined time interval, the scheduling unit 214 is configured to schedule a plan provisioning task for the set of secondary network nodes after the predefined time interval of provisioning the at least one service plan in the primary network node. The set of secondary network nodes is interchangeably referred to as secondary super cores. If no issue is detected from the start of the predefined time interval until it exceeds, the scheduling unit 214 may proceed with provisioning the at least one service plan in the database of the set of secondary network nodes. This ensures that the at least one service plan is correctly and fully deployed across all necessary network nodes.

[0048] The scheduling unit 214 is also responsible for ensuring that provisioning to the set of secondary network nodes is performed in a controlled, error-free manner only after successfully validating the initial provisioning in the primary network node. The plan provisioning task is a specific, structured operation that is created and scheduled by the system 108 to deploy the at least one service plan (e.g., data plans, voice plans, internet packages) to the set of secondary network nodes. The plan provisioning task may include information about target secondary node, the identity of the secondary network node (e.g., super core B, C, etc.) to which the at least one service plan is to be applied, configuration data of the at least one plan, the at least one service plan details, such as plan type, bandwidth allocation, validity period, quota limits, billing rules, and other configuration settings, execution metadata etc.

[0049] In an aspect, the scheduling unit 214 may maintain a list or configuration map of all relevant secondary network nodes that are eligible forreceiving the at least one service plan. Once the predefined time interval elapses and no errors are detected in the primary network node, the scheduling unit 214 may generate the scheduled plan provisioning task for each of the secondary network nodes. Additionally, the scheduling unit 214 may queue the plan provisioning task with associated metadata such as a task ID, a scheduled execution time, a target node identifier, and one or more service plan parameters. The plan provisioning task may be stored in a task queue or provisioning database and triggered by a time-based scheduler or event-driven system. The provisioning to each secondary network node may be executed sequentially or in parallel, depending on the system capacity, priority rules, or network policies.

[0050] In some embodiments, the scheduled tasks may include built-in retry mechanisms, error logging, and feedback loops to ensure successful delivery and application of the service plan to each secondary node. The scheduling unit 214 may also send notifications or status updates to the FMS, confirming that the provisioning of the set of secondary network nodes has been initiated or completed.

[0051] In an embodiment, upon detecting the at least one error in the primary network node within the predefined time interval, the scheduling unit 214 is configured to terminate the scheduled plan provisioning task for the set of secondary network nodes and the provisioning of the at least one service plan in the primary network node. In other words, within this predefined time interval, if any error or issue is detected in the primary network node where the at least one service plan was provisioned, the scheduling unit 214, may cancel the scheduled tasks for the set of secondary network nodes (e.g., the set of secondary super cores). This mechanism effectively prevents the propagation of incorrect or invalid service plans and ensures that one or more existing service plans in the network core are not adversely affected.

[0052] In an embodiment, upon detecting the at least one error in the primary network node within the predefined time interval, the scheduling unit 214 is configured to receive a termination request from a User Interface (UI). Thetermination request corresponds to termination of the scheduled plan provisioning task for the set of secondary network nodes and the provisioning of the at least one service plan in the primary network node. In an aspect, the UI is located in a centralized Command Line Interface (CLI). In an example, if an incorrect validity period is detected, such as assigning a 365 -day plan instead of a 30-day plan within the primary network node during the predefined time interval, then the termination request is initiated by the network operator using the CLI. The network operator may be the user 102 associated with the UE 104. The termination request is a request to stop the scheduled provisioning task for the at least one service plan in the set of secondary super cores. This may prevent the propagation of the error across the set of secondary super cores. Furthermore, upon receiving the termination request, the scheduling unit 214 is configured to terminate the scheduled plan provisioning task for the set of secondary network nodes and the provisioning of the at least one service plan in the primary network node. In an example, the scheduling unit 214 may maintain a queue of the scheduled tasks in the database 208. Upon receiving the termination command via the CLI, the scheduling unit 214 parses the termination request and identifies all scheduled tasks associated with the same service plan. The scheduling unit then flags those tasks as “cancelled” and prevents them from being executed in the set of secondary network nodes. Simultaneously, the scheduling unit 215 may invoke a REST API call to the provisioning unit 212 to deactivate or roll back the at least one service plan from the primary network node, ensuring the system 108 state is reverted to the last known valid configuration.

[0053] FIG. 3 illustrates an exemplary system architecture 300 for managing service plan provisioning in the network 106, in accordance with an embodiment of the present disclosure. FIG. 3 is explained in conjunction with the FIGs. 1 and 2.

[0054] The system architecture 300 includes an FMS 302, a provisioning gateway 304, a CLI 306 and the database 208. Initially, the FMS 302 sends a request to the provisioning gateway 304 to provision at least one service plan within thenetwork 106. The FMS 302 is configured to ensure that all the information provided in the request is accurate and complete before sending it to the provisioning gateway 304. The provisioning gateway 304 is responsible for implementing the at least one service plan in the primary network node. The provisioning gateway 304 receives the request from the FMS 302 and performs a series of checks based on the one or more parameters (e.g., the health status of the primary network node, the maintenance schedule of the primary network node, the response latency of the primary network node, and the configurability of the primary network node) to determine the availability of the primary network node for provisioning the at least one service plan.

[0055] If the primary network node is available, the provisioning gateway 304 proceeds with the provisioning of the at least one service plan in the database 208 of the primary network node. However, if the primary network node is not available, for example, if the primary network node is undergoing maintenance or is at capacity, the provisioning gateway 304 does not immediately provision the at least one service plan. Instead, the provisioning gateway 304 schedules the plan provisioning task to be executed in a set of secondary super cores after a predefined time interval. This delay allows the network 106 to stabilize or resolve any temporary issues with the primary super core.

[0056] The CLI 306 monitors the primary network node during the predefined time interval of provisioning the at least one service plan. If the at least one error (e.g. the configuration mismatch in the primary network node, the incorrect plan provisioning in the primary network node, the service failure during the plan provisioning, the network connectivity issue, the ongoing maintenance state of the primary network node, and latency in data transfer rate) is detected in the primary network node during the predefined time interval, the network operator use the CLI 306 to send the termination request to the provisioning gateway 304. The termination request is sent to stop the scheduled plan provisioning task for the set of secondary network nodes. Upon receiving the termination request, theprovisioning gateway 304 then cancels the planned provisioning task, thereby preventing the propagation of incorrect service plans across the network 106.

[0057] On the other hand, if no issues are detected in the primary network node within the predefined time interval, the provisioning gateway 304 proceeds with the scheduled plan provisioning task and updates the database 208 of the set of secondary super cores with the at least one service plan.

[0058] FIG. 4 illustrates an exemplary process flow diagram 400 of a method for managing service plan provisioning in network 106, in accordance with an embodiment of the present disclosure. Examples of the telecommunication network may include a Fourth-Generation (4G) network, a Fifth-Generation (5G) network, a Sixth-Generation (6G) network, and the like. FIG. 4 is explained in conjunction with FIGs. 1, 2, and 3.

[0059] At step 402, the FMS 302 sends a request to the provisioning gateway 304 to provision service plans. In an example, this request may be triggered by various actions, such as a customer subscribing to a new plan, modifying an existing plan, or renewing a service. The FMS 302 may be responsible for managing customer orders and service fulfillment, ensuring that the service plans are accurately and efficiently provisioned across the primary network node and the set of secondary network nodes.

[0060] At step 404, the provisioning gateway 304 may receive the request from the FMS 302. The request from the FMS 302 may include all necessary details for provisioning, such as the type of service plan (e.g., internet bandwidth, voice calling, or air fiber subscription), the customer account information, and any specific parameters required for the plan (e.g., data limits, speed tiers, and duration of the service).

[0061] At step 406, once the request is received, the provisioning gateway 304 checks whether the primary network node is available for provisioning or not. In an example, the primary network node is a main network node designated for theinitial provisioning of the service plan. The purpose of checking the availability of the primary network node is to ensure that it may handle the provisioning request without any issues, such as being overburdened, undergoing maintenance, or facing other operational constraints. This check is crucial because the primary network node is central to the network efficiency, and any problems at the primary network node may significantly affect service quality and network performance.

[0062] At step 408, if the primary network node is available, the provisioning gateway 304 provisions service plans in the database 208 of the primary network node. For example, if one of the service plan is an air fiber subscription plan, it is immediately provisioned into the primary network node, allowing customers to access the service plan.

[0063] Further, at step 410, if the primary network node is not available, the provisioning gateway 304 schedule the plan provisioning task for the primary network node after the predefined time interval. For example, the provisioning gateway 304 schedules the plan provisioning task to be provisioned in other network nodes after 15 minutes.

[0064] At step 412, during the predefined time interval, the network operator or administrator may monitor the primary network node where the at least one service plan is already been provisioned to check if there is any issue or if there is at least one error such as the configuration mismatch in the primary network node, the incorrect plan provisioning in the primary network node, the service failure during the plan provisioning, the network connectivity issue, the ongoing maintenance state of the primary network node, and latency in data transfer rate is detected in the primary network node.

[0065] If no issue is detected from the start of the predefined time interval until it exceeds, the provisioning gateway 304 proceeds with provisioning of the service plans in the database of the set of secondary network nodes, at step 414. This ensures that the service plans are correctly and fully deployed across all necessary network nodes.

[0066] At step 416, if any issue is found (e.g., if a typo in the bandwidth allocation is detected, such as allocating 1000 Mbps instead of 100 Mbps) within the primary network node during the predefined time interval, then at step 418, the network operator sends the termination request via the CLI 306 to stop the scheduled provisioning task for the at least one service plan in the set of secondary network nodes. This may prevent the error propagation across the set of secondary super cores.

[0067] Further, at step 420, the provisioning gateway 304 receives the stop request from the CLI 306 and terminates the scheduled tasks for provisioning the service plans. This may ensure that incorrect or problematic configurations are not spread to other parts of the network, preserving the integrity of the network and service quality.

[0056] FIG. 5 illustrates an exemplary flow diagram of a method 500 for managing service plan provisioning in the network 106, in accordance with embodiments of the present disclosure. The steps of the method 500 of the present disclosure will now be explained with reference to the components of the system 108 as depicted in FIGs. 2 and 3.

[0057] At step 502, the method 500 includes receiving, by a receiving unit 210, a request corresponding to provisioning of at least one service plan from an external entity. The external entity comprises a fulfillment management system (FMS), such as the FMS 302.

[0058] At step 504, the method 500 includes checking, by the provisioning unit 212, whether the primary network node is available in response to the received request. The checking of the availability of the primary network node involves accessing, by the provisioning unit 212, one or more parameters associated with the primary network node. The one or more parameters comprise a health status of the primary network node, a maintenance schedule of the primary network node, a response latency of the primary network node, and a configurability of the primary network node. Further, based on accessing the one or more parameters, the method500 includes determining, by the provisioning unit, an active state of the primary network node. The active state indicates the availability of the primary network node.

[0059] At step 506, the method 500 includes provisioning, by the provisioning unit 212, the at least one service plan in the primary network node, upon confirming the availability of the primary network node.

[0060] At step 508, the method 500 includes monitoring, by the provisioning unit 212, the primary network node to detect at least one error in the primary network node within a predefined time interval of provisioning the at least one service plan. The monitoring of the primary network node to detect the at least one error is one of the real-time monitoring process and the periodic check monitoring process.

[0061] At step 510, the method 500 includes scheduling, by the scheduling unit 214, a plan provisioning task for a set of secondary network nodes after the predefined time interval of provisioning the at least one service plan in the primary network node upon detecting no error in the primary network node within the predefined time interval.

[0062] At step 512, the method 500 includes terminating, by the scheduling unit 214, the scheduled plan provisioning task for the set of secondary network nodes and the provisioning of the at least one service plan in the primary network node, upon detecting the at least one error in the primary network node within the predefined time interval. The scheduling unit 214 receives a termination request from a User Interface (UI). The UI is located in a centralized Command Line Interface (CLI). Additionally, the termination request corresponds to termination of the scheduled plan provisioning task for the set of secondary network nodes and the provisioning of the at least one service plan in the primary network node.

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

[0058] 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 Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system 600 connects. The main memory 630 may be 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) including, 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 may be used to store information and / or instructions.

[0059] The bus 620 communicatively couples the processor 670 with the other memory, storage, and communication blocks. The bus 620 can be, e.g. a Peripheral Component Interconnect (PCI) / PCI Extended (PCI-X) bus, Small Computer System Interface (SCSI), universal serial bus (USB), or the like, for connecting expansion cards, drives, and other subsystems as well as other buses, such a front side bus (FSB), which connects the processor 670 to the computer system 600.

[0060] Optionally, operator and administrative interfaces, e.g. a display, keyboard, and a cursor control device, may also be coupled to the bus 620 to support direct operator interaction with the computer system 600. Other operator and administrative interfaces may be provided through network connections connectedthrough the communication port(s) 660. In no way should the aforementioned exemplary computer system 600 limit the scope of the present disclosure.

[0061] 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 or examples, 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.

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

[0063] The present disclosure provides a technical advancement in the field of telecom network plan provisioning and service configuration management. By introducing a controlled and staged provisioning method that first deploys a service plan to a primary network node and subsequently schedules provisioning to a set of secondary nodes, the system significantly reduces the risk of propagating configuration errors across the network. The architecture supports both manual and automated error detection within a predefined time window, ensuring that only validated service plans are distributed further. Additionally, the integration of acentralized CLI for terminating scheduled tasks in response to detected errors enhances operator control, enables real-time intervention, and prevents disruptions to existing services. This layered and fault-tolerant approach improves operational accuracy and network stability and also minimizes service downtime, optimizes resource utilization, and enhances end-user experience through reliable and error- free provisioning workflows.

[0064] 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 to be implemented merely as illustrative of the disclosure and not as limitation.ADVANTAGES OF THE PRESENT DISCLOSURE

[0065] As is evident from the above, the present disclosure provides a technically advanced solution by providing an improved method and system for managing service plan provisioning in a network.

[0066] The present disclosure provides an optimized approach for detecting errors during the provisioning process. By provisioning the service plan first to a primary super core and scheduling a plan provisioning task for a set of secondary super cores only after a predefined time interval, the system allows for the identification and rectification of any issues before they propagate across the network.

[0067] The present disclosure reduces the risk of widespread disruptions and service inconsistencies by addressing potential issues in the primary super core before executing scheduled tasks for the secondary super cores.31

[0068] The present disclosure provides a system and a method that enables early detection of errors, enhances overall network performance, efficient task management, and saves time and resources in the long run.

[0069] The present disclosure provides flexibility and configurability by allowing network operators to define the primary super core and the predefined time interval based on network requirements and operational preferences, ensuring adaptability across diverse deployment scenarios.

[0070] The present disclosure enhances administrative control and operational efficiency by incorporating a centralized CLI-based termination mechanism, allowing network operators to intervene promptly and halt erroneous provisioning tasks across all super cores with minimal effort.

Claims

We claim:

1. A method (500) for managing service plan provisioning in a network (106), the method (500) comprising: receiving (502), by a receiving unit (210), a request corresponding to provisioning of at least one service plan from an external entity; checking (504), by a provisioning unit (212), whether a primary network node is available in response to the received request; upon confirming the availability of the primary network node, provisioning (506), by the provisioning unit (212), the at least one service plan in the primary network node; monitoring (508), by the provisioning unit (212), the primary network node to detect at least one error in the primary network node within a predefined time interval of provisioning the at least one service plan; upon detecting no error in the primary network node within the predefined time interval, scheduling (510), by a scheduling unit (214), a plan provisioning task for a set of secondary network nodes after the predefined time interval of provisioning the at least one service plan in the primary network node; and upon detecting the at least one error in the primary network node within the predefined time interval, terminating (512), by the scheduling unit (214), the scheduled plan provisioning task for the set of secondary network nodes and the provisioning of the at least one service plan in the primary network node.

2. The method as claimed in claim 1, wherein the external entity comprises a fulfillment management system (FMS) (302).

3. The method as claimed in claim 1, wherein checking the availability of the primary network node comprises: accessing, by the provisioning unit (212), one or more parameters associated with the primary network node; anddetermining, by the provisioning unit (212), an active state of the primary network node based on the one or more parameters, wherein the active state indicates the availability of the primary network node.

4. The method as claimed in claim 3, wherein the one or more parameters comprise a health status of the primary network node, a maintenance schedule of the primary network node, a response latency of the primary network node, and a configurability of the primary network node.

5. The method as claimed in claim 1, wherein the monitoring of the primary network node to detect the at least one error is one of a real-time monitoring process and a periodic check monitoring process.

6. The method as claimed in claim 1, wherein upon detecting the at least one error in the primary network node within the predefined time interval, receiving, by the scheduling unit (214), a termination request from a User Interface (UI), wherein the termination request corresponds to termination of the scheduled plan provisioning task for the set of secondary network nodes and the provisioning of the at least one service plan in the primary network node; and terminating, by the scheduling unit (214), the scheduled plan provisioning task and the provisioning of the at least one service plan in the primary network node in response to the termination request.

7. The method as claimed in claim 6, wherein the UI is located in a centralized Command Uine Interface (CUI) (306).

8. The method as claimed in claim 1, wherein the at least one error comprises a configuration mismatch in the primary network node, an incorrect plan provisioning in the primary network node, a service failure during the plan provisioning, a network connectivity issue, an ongoing maintenance state of the primary network node, and latency in data transfer rate.

9. A system (108) for managing service plan provisioning in a network (106), the system (108) comprising: a receiving unit (210) configured to receive a request corresponding to provisioning of at least one service plan from an external entity; a provisioning unit (212) configured to: check whether a primary network node is available in response to the received request; upon confirming the availability of the primary network node, provision the at least one service plan in the primary network node; and monitor the primary network node to detect at least one error in the primary network node within a predefined time interval of provisioning the at least one service plan; a scheduling unit (214) configured to: schedule a plan provisioning task for a set of secondary network nodes after a predefined time interval of provisioning the at least one service plan in the primary network node upon detecting no error in the primary network node within the predefined time interval; and terminate the scheduled plan provisioning task for the set of secondary network nodes and the provisioning of the at least one service plan in the primary network node upon detecting the at least one error in the primary network node within the predefined time interval.

10. The system (108) as claimed in claim 9, wherein the external entity comprises a fulfillment management system (FMS) (302).

11. The system (108) as claimed in claim 9, wherein to check the availability of the primary network node, the provisioning unit (212) is configured to: access one or more parameters associated with the primary network node; anddetermine an active state of the primary network node based on the one or more parameters, wherein the active state indicates the availability of the primary network node.

12. The system (108) as claimed in claim 11, wherein the one or more parameters comprise a health status of the primary network node, a maintenance schedule of the primary network node, a response latency of the primary network node, and a configurability of the primary network node.

13. The system (108) as claimed in claim 9, wherein the monitoring of the primary network node to detect the at least one error is one of a real-time monitoring process and a periodic check monitoring process.

14. The system (108) as claimed in claim 9, wherein upon detection of the at least one error in the primary network node within the predefined time interval, the scheduling unit (214) is configured to: receive a termination request from a User Interface (UI), wherein the termination request corresponds to termination of the scheduled plan provisioning task for the set of secondary network nodes and the provisioning of the at least one service plan in the primary network node; and terminate the scheduled plan provisioning task and the provisioning of the at least one service plan in the primary network node in response to the termination request.

15. The system (108) as claimed in claim 14, wherein the UI is located in a centralized Command Uine Interface (CUI) (306).

16. The system (108) as claimed in claim 9, wherein the at least one error comprises a configuration mismatch in the primary network node, an incorrect plan provisioning in the primary network node, a service failure during the planprovisioning, a network connectivity issue, an ongoing maintenance state of the primary network node, and latency in data transfer rate.

17. 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 execute a method (500) for managing service plan provisioning in a network (106), the method (500) comprising: receiving (502), by a receiving unit (210), a request corresponding to provisioning of at least one service plan from an external entity; checking (504), by a provisioning unit (212), whether a primary network node is available in response to the received request; upon confirming the availability of the primary network node, provisioning (506), by the provisioning unit (212), the at least one service plan in the primary network node; monitoring (508), by the provisioning unit (212), the primary network node to detect at least one error in the primary network node within a predefined time interval of provisioning the at least one service plan; upon detecting no error in the primary network node within the predefined time interval, scheduling (510), by a scheduling unit (214), a plan provisioning task for a set of secondary network nodes after the predefined time interval of provisioning the at least one service plan in the primary network node; and upon detecting the at least one error in the primary network node within the predefined time interval, terminating (512), by the scheduling unit (214), the scheduled plan provisioning task for the set of secondary network nodes and the provisioning of the at least one service plan in the primary network node.

Images