DESC:
FORM 2
THE PATENTS ACT, 1970
(39 of 1970)
&
THE PATENTS RULES, 2003

COMPLETE SPECIFICATION
(See section 10 and rule 13)
1. TITLE OF THE INVENTION
METHOD AND SYSTEM FOR MANAGING RESOURCE RESERVATION DURING A CONTAINER NETWORK FUNCTION (CNF) INSTANTIATION.
2. APPLICANT(S)
NAME NATIONALITY ADDRESS
JIO PLATFORMS LIMITED INDIAN OFFICE-101, SAFFRON, NR. CENTRE POINT, PANCHWATI 5 RASTA, AMBAWADI, AHMEDABAD 380006, GUJARAT, INDIA
3.PREAMBLE TO THE DESCRIPTION

THE FOLLOWING SPECIFICATION PARTICULARLY DESCRIBES THE NATURE OF THIS INVENTION AND THE MANNER IN WHICH IT IS TO BE PERFORMED.

FIELD OF THE INVENTION
[0001] The present invention relates generally to the field of computer networks and cloud computing, and in particular to a system and method for managing resource reservation during a Container Network Function (CNF) instantiation.
BACKGROUND OF THE INVENTION
[0002] In modern networking and telecommunications infrastructures, the adoption of Container Network Functions (CNFs) has become increasingly prevalent due to their flexibility and scalability. CNFs, which are software-defined network functions running within containers, offer the agility needed to meet the evolving demands of network services. However, their successful deployment relies heavily on a meticulous instantiation process.
[0003] In this context, the CNF instantiation call flow encompasses several critical steps to ensure the reliable operation of CNFs within the network. Among these steps, CNF resource reservation and policy checks emerge as vital components. The CNF Lifecycle Manager (CNFLM) takes center stage in this process, responsible for overseeing the creation, scaling, and termination of CNF instances. To guarantee a seamless instantiation, CNFLM collaborates with the Policy Execution Engine (PEEGN).
[0004] The Inventory Management (IM) service is a pivotal component within the system, responsible for overseeing virtual and limited physical inventory. It plays a crucial role in maintaining relationships between these resources, particularly within an overlay context, and describing them using various attributes. What sets this service apart is its reliance on external micro-services to create, update, and delete resources, ensuring that its data accuracy hinges on these micro-services. To facilitate interaction with other system components, the IM service offers Query APIs, allowing them to access information regarding resource relationships and attributes efficiently. During instantiation of network functions, the inventory service reserves some resources that are requested by the Policy Execution Engine. In case the instantiation fails, the reserved resources are still maintained and might not be used for other network functions leading to the waste of storage.
[0005] Thus, there exists a need to unreserve the resources in case of instantiation failure and add the same into available resources for further use. The present invention discloses a system and method for effectively managing resource reservation during CNF instantiation to provide a solution to the above-mentioned drawbacks by removing reserved resources from total resources and adding resources in available resources in case of unreserve.
SUMMARY OF THE INVENTION
[0006] One or more embodiments of the present disclosure provide a method and system for managing resource reservation during a Container Network Function (CNF) instantiation.
[0007] In one aspect of the present invention, the system for managing resource reservation during the CNF instantiation is disclosed. The method includes the step of receiving a request from a user to initiate the CNF instantiation. The method further includes the step of transmitting a request to a life cycle manager for reserving one or more resources for the CNF instantiation. The method further includes the step of reserving the one or more resources as per the request for the CNF instantiation. The method further includes the step of scheduling a task at a microservice to un-reserve the one or more resources. The method further includes the step of transmitting an unreserve request to the life cycle manager on failure of the CNF instantiation. The method further includes the step of deleting the scheduled task at the microservice pertaining to un-reserving the one or more resources on successful instantiation of the CNF.
[0008] In an embodiment, the lifecycle manager determines available resources in an inventory manager on receipt of the request for the reserving the one or more resources.
[0009] In an embodiment, the one or more resources is at least one of a Central Processing Unit (CPU), memory, and bandwidth.
[0010] In an embodiment, the method for initiating the CNF instantiation, includes the steps of updating status of reserved one or more resources at a database.
[0011] In an embodiment, the microservice is capable of running tasks at a pre-defined time interval configured as per the user.
[0012] In an embodiment, on transmitting the unreserve request to the life cycle manager on failure of the CNF instantiation, the method includes the step of assigning a state for the one or more un-reserved resources as available resources.
[0013] In an embodiment, the method is at least one of, an async event-based implementation method, the one or more resources are marked as un-reserved in one of, a termination flow and the CNF instantiation failure.
[0014] In another aspect of the present invention, the system for managing resource reservation during the CNF instantiation is disclosed. The system includes a receiving unit configured to receive a request from a user to initiate the CNF instantiation. The system further includes a transmitting unit configured to transmit a request to a life cycle manager for reserving one or more resources for the CNF instantiation. The system further includes a reserving unit configured to reserve the one or more resources as per the request for the CNF instantiation. The system further includes a scheduling unit configured to schedule a task at a microservice to un-reserve one or more resources. The system further includes the transmitting unit configured to transmit an unreserve request to the life cycle manager on failure of the CNF instantiation. The system further includes a deletion unit configured to delete the scheduled task at the microservice pertaining to un-reserving the one or more resources on successful instantiation of the CNF.
[0015] In another aspect of the invention, a non-transitory computer-readable medium having stored thereon computer-readable instructions is disclosed. The computer-readable instructions are executed by a processor. The processor is configured to receive a request from a user to initiate the CNF instantiation. The processor is configured to transmit a request to a life cycle manager for reserving one or more resources for the CNF instantiation. The processor is configured to reserve the one or more resources as per the request for the CNF instantiation. The processor is configured to schedule a task at a microservice to un-reserve one or more resources. The processor is configured to transmit an unreserve request to the life cycle manager on failure of the CNF instantiation. The processor is configured to delete the scheduled task at the microservice pertaining to un-reserving the one or more resources on successful instantiation of the CNF.
[0016] In another aspect of invention, User Equipment (UE) is disclosed. The UE includes one or more primary processors communicatively coupled to one or more processors, the one or more primary processors coupled with a memory. The processor causes the UE to transmit a request to initiate the CNF instantiation to the one or more processors.
[0017] Other features and aspects of this invention will be apparent from the following description and the accompanying drawings. The features and advantages described in this summary and in the following detailed description are not all-inclusive, and particularly, many additional features and advantages will be apparent to one of ordinary skill in the relevant art, in view of the drawings, specification, and claims hereof. Moreover, it should be noted that the language used in the specification has been principally selected for readability and instructional purposes and may not have been selected to delineate or circumscribe the inventive subject matter, resort to the claims being necessary to determine such inventive subject matter.

BRIEF DESCRIPTION OF THE DRAWINGS
[0018] 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 disclosure of electrical components, electronic components or circuitry commonly used to implement such components.
[0019] FIG. 1 is an exemplary block diagram of an environment for managing resource reservation during a Container Network Function (CNF) instantiation, according to one or more embodiments of the present invention;
[0020] FIG. 2 is an exemplary block diagram of a system for managing resource reservation during the CNF instantiation, according to one or more embodiments of the present invention;
[0021] FIG. 3 is a schematic representation of a workflow of the system of FIG. 1, according to the one or more embodiments of the present invention;
[0022] FIG. 4 is an exemplary block diagram of an architecture implemented in the system of the FIG. 2, according to one or more embodiments of the present invention;
[0023] FIG. 5 is a signal flow diagram for managing resource reservation during the CNF instantiation, according to one or more embodiments of the present invention; and
[0024] FIG. 6 is a schematic representation of a method of managing resource reservation during the CNF instantiation, according to one or more embodiments of the present invention.
[0025] The foregoing shall be more apparent from the following detailed description of the invention.
DETAILED DESCRIPTION OF THE INVENTION
[0026] Some embodiments of the present disclosure, illustrating all its features, will now be discussed in detail. It must also be noted that as used herein and in the appended claims, the singular forms "a", "an" and "the" include plural references unless the context clearly dictates otherwise.
[0027] Various modifications to the embodiment will be readily apparent to those skilled in the art and the generic principles herein may be applied to other embodiments. However, one of ordinary skill in the art will readily recognize that the present disclosure including the definitions listed here below are not intended to be limited to the embodiments illustrated but is to be accorded the widest scope consistent with the principles and features described herein.
[0028] A person of ordinary skill in the art will readily ascertain that the illustrated steps detailed in the figures and here below are set out to explain the exemplary embodiments shown, and it should be anticipated that ongoing technological development will change the manner in which particular functions are performed. These examples are presented herein for purposes of illustration, and not limitation. Further, the boundaries of the functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. Such alternatives fall within the scope and spirit of the disclosed embodiments.
[0029] FIG. 1 illustrates an exemplary block diagram of an environment 100 for managing resource reservation during a Container Network Function (CNF) instantiation, according to one or more embodiments of the present disclosure. In this regard, the environment 100 includes a User Equipment (UE) 110, a server 115, a network 105 and a system 120 communicably coupled to each other to manage resource reservation during the CNF instantiation. Examples of the one or more resources include, but are not limited to, CPU, memory, and bandwidth, which are essential for the successful deployment and operation of CNFs. Managing resource reservation refers to the process of allocating, tracking, and freeing up the one or more resources during various stages of the CNF instantiation, ensuring optimal usage and availability for other tasks.
[0030] As per the illustrated embodiment and for the purpose of description and illustration, the UE 110 includes, but not limited to, a first UE 110a, a second UE 110b, and a third UE 110c, and should nowhere be construed as limiting the scope of the present disclosure. In alternate embodiments, the UE 110 may include a plurality of UEs as per the requirement. For ease of reference, each of the first UE 110a, the second UE 110b, and the third UE 110c, will hereinafter be collectively and individually referred to as the “User Equipment (UE) 110”.
[0031] In an embodiment, the UE 110 is one of, but not limited to, any electrical, electronic, electro-mechanical or an equipment and a combination of one or more of the above devices such as a 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 computing device.
[0032] The environment 100 includes the server 115 accessible via the network 105. The server 115 may include, by way of example but not limitation, one or more of a standalone server, a server blade, a server rack, a bank of servers, a server farm, hardware supporting a part of a cloud service or system, a home server, hardware running a virtualized server, one or more processors executing code to function as a server, one or more machines performing server-side functionality as described herein, at least a portion of any of the above, some combination thereof. In an embodiment, the entity may include, but is not limited to, a vendor, a network operator, a company, an organization, a university, a lab facility, a business enterprise side, a defense facility side, or any other facility that provides service.
[0033] The network 105 includes, by way of example but not limitation, one or more of a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a Public-Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, or some combination thereof. The network 105 may include, but is not limited to, a Third Generation (3G), a Fourth Generation (4G), a Fifth Generation (5G), a Sixth Generation (6G), a New Radio (NR), a Narrow Band Internet of Things (NB-IoT), an Open Radio Access Network (O-RAN), and the like.
[0034] The network 105 may also 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 105 may also include, by way of example but not limitation, one or more of a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a Public-Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, a VOIP or some combination thereof.
[0035] The environment 100 further includes the system 120 communicably coupled to the server 115 and the UE 110 via the network 105. The system 120 is configured for managing resource reservations during the CNF instantiation. As per one or more embodiments, the system 120 is adapted to be embedded within the server 115 or embedded as an individual entity.
[0036] Operational and construction features of the system 120 will be explained in detail with respect to the following figures.
[0037] FIG. 2 is an exemplary block diagram of the system 120 for managing resource reservation during the CNF instantiation, according to one or more embodiments of the present invention.
[0038] As per the illustrated embodiment, the system 120 includes one or more processors 205, a memory 210, a user interface 215, and a database 220. For the purpose of description and explanation, the description will be explained with respect to one processor 205 and should nowhere be construed as limiting the scope of the present disclosure. In alternate embodiments, the system 120 may include more than one processor 205 as per the requirement of the network 105. The one or more processors 205, hereinafter referred to as the processor 205 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, single board computers, and/or any devices that manipulate signals based on operational instructions.
[0039] As per the illustrated embodiment, the processor 205 is configured to fetch and execute computer-readable instructions stored in the memory 210. The memory 210 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 210 may include any non-transitory storage device including, for example, volatile memory such as RAM, or non-volatile memory such as disk memory, EPROMs, FLASH memory, unalterable memory, and the like.
[0040] In an embodiment, the user interface 215 includes a variety of interfaces, for example, interfaces for a graphical user interface, a web user interface, a Command Line Interface (CLI), and the like. The user interface 215 facilitates communication of the system 120. In one embodiment, the user interface 215 provides a communication pathway for one or more components of the system 120. Examples of such components include, but are not limited to, the UE 110 and the database 220.
[0041] The database 220 is one of, but not limited to, a centralized database, a cloud-based database, a commercial database, an open-source database, a distributed database, an end-user database, a graphical database, a No-Structured Query Language (NoSQL) database, an object-oriented database, a personal database, an in-memory database, a document-based database, a time series database, a wide column database, a key value database, a search database, a cache databases, and so forth. The foregoing examples of database 220 types are non-limiting and may not be mutually exclusive e.g., a database 220 can be both commercial and cloud-based, or both relational and open-source, etc.
[0042] In order for the system 120 to manage resource reservation during the CNF instantiation, the processor 205 includes one or more modules. In one embodiment, the one or more modules/units includes, but not limited to, a receiving unit 225, an updating unit 230, a transmitting unit 235, an assigning unit 240, a reserving unit 245, a scheduling unit 250, and a deletion 255 communicably coupled to each other for managing resource reservation during the CNF instantiation.
[0043] In one embodiment, the one or more modules may be used in combination or interchangeably for managing resource reservation during the CNF instantiation.
[0044] The receiving unit 225, the updating unit 230, the transmitting unit 235, the assigning unit 240, the reserving unit 245, the scheduling unit 250, and the deletion 255, in an embodiment, may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processor 205. In the examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processor 205 may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processor may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the memory 210 may store instructions that, when executed by the processing resource, implement the processor. In such examples, the system 120 may comprise the memory 210 storing the instructions and the processing resource to execute the instructions, or the memory 210 may be separate but accessible to the system 120 and the processing resource. In other examples, the processor 205 may be implemented by electronic circuitry.
[0045] In an embodiment, the receiving unit 225 is configured to receive a request from a user to initiate the Containerized Network Function (CNF) instantiation. The CNF instantiation refers to the process of deploying and initializing the CNF within the network infrastructure, specifically designed to operate in cloud-native environments such as networks 105. The CNFs perform specific tasks like some of, but not limited to, traffic routing, network slicing, or user authentication in networks 105. Further, the updating unit 230 is configured to update the status of the one or more reserved resources in the database 220 during the CNF instantiation process.
[0046] In an embodiment, the one or more resources in the CNF instantiation refer to the specific computational, network, or storage resources required to deploy and run the CNF effectively within the network 105. The one or more resources are critical for ensuring that the CNF has the necessary capacity to perform its function without disruption. The one or more resources is at least one of a Central Processing Unit (CPU), memory and bandwidth. The CPU handles data processing tasks such as, but not limited to, packet inspection, routing decisions, and algorithm execution. The memory is crucial for running applications smoothly, especially when multiple tasks are being processed simultaneously. In CNFs, the memory is used to store temporary data, buffers, and context for ongoing processes. The bandwidth determines how much data can be transmitted simultaneously over the network 105. High bandwidth is essential for applications that require real-time data transfer, such as, but not limited to, video streaming or online gaming.
[0047] Upon receipt of the CNF instantiation, the transmitting unit 235 is configured to transmit the request to a life cycle manager 405 for reserving one or more resources for the CNF instantiation. The life cycle manager 405 is a specialized component responsible for managing the entire life cycle of the CNFs functions within the network 105. The life cycle manager 405 includes processes from deployment and operation to scaling and decommissioning of the CNF in the network environment.
[0048] In an embodiment, the lifecycle manager determines available resources in an inventory manager 420 on receipt of the request for the reserving the one or more resources. The inventory manager 420 refers to the component that manages and maintains an up-to-date record of all the network resources, services, and components. The inventory manager 420 provides visibility into the assets available within the network, including both physical and virtual elements, ensuring efficient management and allocation. When the lifecycle manager receives the request to instantiate the CNF, the lifecycle manager must first check if there are enough available resources (for example, CPU cores, memory, bandwidth) to support the CNFs operation. The life cycle manager 405 is a critical component in network management responsible for overseeing the entire lifecycle of the network function including, but not limited to, deployment, operation, scaling, updating, and termination. The life cycle manager 405 also includes, but not limited to, open network automation platform, cloud-native network functions virtualization orchestrator, and kubernetes-based life cycle manager 405 for CNFs. Subsequently, the inventory manager 420 keeps track of all the available physical and virtual resources within the network infrastructure. The inventory manager 420 maintains the dynamic database 220 of resource allocations and availability, ensuring that the one or more resources are efficiently used across the network 105.
[0049] Upon reserving the one or more resources as per the request for the CNF instantiation, the scheduling unit 250 is configured to schedule a task at a microservice 415 to un-reserve the one or more resources. More specifically, the scheduling unit 250 is configured to schedule the task at the microservice 415 to un-reserve the one or more resources based on one of a failure of the CNF instantiation and a successful instantiation. The microservice 415 is capable of running tasks at a pre-defined time interval configured as per the user. The microservice 415 refers to the specialized component within the network architecture 400 that performs the distinct function related to the management, deployment, or operation of the CNFs. Each microservice 415 operates independently, allowing for modularity and flexibility in network management. The microservice 415 has the ability to execute various tasks or operations and involves in such actions like some of but not limited to, monitoring resources, underserving resources, or performing other maintenance functions. The microservice 415 operates based on the schedule that is established in advance. The tasks microservice 415 runs are not executed randomly instead, they occur at specific intervals that have been set ahead of time.
[0050] Once the CNF instantiation is one of a success and a failure, the one or more resources may be released, making the one or more resources available for other uses.
[0051] In this regard, the transmitting unit 235 is configured to transmit an unreserve request to the lifecycle manager 405. The unreserve request refers to the request transmitted to the lifecycle manager 405 to free up unreserve one or more resources that were previously reserved for the CNF instantiation. The one or more resources (example, CPU, memory, bandwidth) are no longer needed because the CNF instantiation has failed. When the CNF instantiation process fails, whether due to insufficient resources, software errors, or network issues, the one or more resources reserved for the CNF are no longer required.
[0052] On transmitting the unreserve request to the life cycle manager 405 on failure of the CNF instantiation, the assigning unit 240 is configured to assign a state for the one or more un-reserved resources. The state for the one or more un-reserved resources is one of an available resource and an unavailable resource. With regards to the present disclosure, the assigning unit 240 is configured to assign the state for the one or more un-reserved resources as available resources on failure of the CNF instantiation.
[0053] In one embodiment, when the CNF instantiation fails due to issues such as, but not limited to, insufficient resources or software errors, the unreserve request is sent to the lifecycle manager. The unreserve request notifies the lifecycle manager that the one or more resources previously allocated for the failed CNF are no longer needed.
[0054] Once the unreserve request is processed, the assigning unit 240 updates the state of the one or more unreserved resources. The assigning unit 240 designates the one or more resources as available, indicating that they can now be allocated to other CNF instantiations or tasks. On successful instantiation of the CNF, the deletion unit 255 is configured to delete the scheduled task at the microservice 415. More specifically, the deletion unit 255 is configured to delete the task corresponding to un-reserving the one or more resources on successful instantiation of the CNF.
[0055] In an alternate embodiment, upon transmitting the unreserved request to the life cycle manager 405 following failure of the CNF instantiation, the reserving unit 245 is configured to reserve the one or more resources as per the request for the CNF instantiation. Even after the failure and the unreserve process, the reserving unit 245 is still ready to reserve the required resources when the new request for CNF instantiation is received. Thereafter, when the CNF instantiation fails and the process of deploying the CNF cannot be completed due to an issue, the CNF instantiation transmits an unreserve request to the lifecycle manager. Further, the unreserve request instructs the lifecycle manager to release the one or more resources that were previously reserved for the failed CNF.
[0056] In addition, the system as disclosed involves an asynchronous event-based implementation. The asynchronous event-based implementation refers to a programming and architectural approach where the system 120 reacts to events or changes in the state of the one or more resources, rather than following a strict sequence of instructions. The approach is particularly effective in dynamic environments like networks105, where events can occur asynchronously and may require immediate responses. The examples of the asynchronous event-based implementation = include, but not limited to, resource management, network scaling, and monitoring and alerts. The event-based implementation method allows for asynchronous processing where events are handled independently of the main execution flow, enabling loosely coupled components to operate flexibly, triggering specific actions based on events, utilizing event queues to manage spikes in occurrences, and often employing an observer pattern for real-time notifications and updates.
[0057] The one or more resources are marked as unreserved in scenarios such as, a termination flow or CNF instantiation failure. If the CNF instantiation fails, the system asynchronously processes the event to unreserve the virtual machine and mark it as available for other uses. Similarly, if the CNF instance is terminated successfully, the virtual machine and any associated resources, such as storage volumes, are also marked as unreserved and made available for reuse. In an embodiment, the CNF termination refers to the process of stopping, deactivating, and removing the CNF instance from a cloud or virtualized environment. The CNF termination process is typically initiated when the CNF instance is no longer needed, such as when scaling down due to decreased workload, updating to a new version, or decommissioning the CNF altogether. The CNF termination includes, but not limited to, scaling down due to decreased workload, decommissioning the CNF altogether, load balancing, and updating to the new version.
[0058] The CNF instantiation failure refers to the situation where the process of setting up or/and deploying the CNF instance does not complete successfully, usually due to errors or issues during the deployment. The examples of the CNF instantiation failure include some of, but not limited to resource allocation failures, configuration error, and network connectivity issues. The resource allocation failures occur when the system is unable to allocate the required one or more resources for the CNF instantiation. The configuration errors happen when the parameters specified for the CNF deployment are incorrect or incompatible with the existing infrastructure. The network connectivity issues failures occur when the CNF cannot communicate with other necessary components or services due to network problems. Identifying resource allocation failures, configuration errors, and network connectivity issues is crucial for network operators to ensure reliable and efficient operations within the network environment.
[0059] FIG. 3 describes a preferred embodiment of the system 120 of FIG. 2, according to various embodiments of the present invention. It is to be noted that the embodiment with respect to FIG. 3 will be explained with respect to the first UE 110a and the system 120 for the purpose of description and illustration and should nowhere be construed as limited to the scope of the present disclosure.
[0060] As mentioned earlier in FIG. 1, each of the first UE 110a, the second UE 110b, and the third UE 110c may include an external storage device, a bus, a main memory, a read-only memory, a mass storage device, communication port(s), and a processor. The exemplary embodiment as illustrated in FIG. 3 will be explained with respect to the first UE 110a without deviating from the scope of the present disclosure and the limiting the scope of the present disclosure. The first UE 110a includes one or more primary processors 305 communicably coupled to the one or more processors 205 of the system 120.
[0061] The one or more primary processors 305 are coupled with a memory 310 storing instructions which are executed by the one or more primary processors 305. Execution of the stored instructions by the one or more primary processors 305 enables the first UE 110a transmit a request to initiate the CNF instantiation to the one or more processors.
[0062] As mentioned earlier in FIG. 2, the one or more processors 205 of the system 120 is configured for managing resource reservation during the CNF instantiation. As per the illustrated embodiment, the system 120 includes the one or more processors 205, the memory 210, the user interface 215, and the database 220. The operations and functions of the one or more processors 205, the memory 210, the user interface 215, and the database 220 are already explained in FIG. 2. For the sake of brevity, a similar description related to the working and operation of the system 120 as illustrated in FIG. 2 has been omitted to avoid repetition.
[0063] Further, the processor 205 includes the receiving unit 225, the updating unit 230, the transmitting unit 235, the assigning unit 240, the reserving unit 245, the scheduling unit 250, and the deletion 255. The operations and functions of the receiving unit 225, the updating unit 230, the transmitting unit 235, the assigning unit 240, the reserving unit 245, the scheduling unit 250, and the deletion 255 are already explained in FIG. 2. Hence, for the sake of brevity, a similar description related to the working and operation of the system 120 as illustrated in FIG. 2 has been omitted to avoid repetition. The limited description provided for the system 120 in FIG. 3, should be read with the description provided for the system 120 in the FIG. 2 above, and should not be construed as limiting the scope of the present disclosure.
[0064] FIG. 4 is an exemplary block diagram of an architecture 400 of the system 120 for managing resource reservation during the CNF instantiation, according to one or more embodiments of the present invention.
[0065] The architecture 400 includes the user interface 215, the lifecycle manager 405, a Policy Execution Engine (PEEGN) 410, the microservice 415, the inventory manager 420, the database 220. The PEEGN 410 is the key component in the network architecture 400 that enforces and manages operational policies for the CNFs. The PEEGN 410 interprets and executes policy rules to control resource allocation, service deployment, and overall network behavior. The examples of the PEEGN 410 include, but not limited to, resource allocation policy, security policy management, and resource un-reservation policy.
[0066] The architecture includes the user interface 215 which facilitates the initiation of CNF requests by being positioned between the life cycle manager 405 and the PEEGN 410. The PEEGN
[0067] In one embodiment, the life cycle manager 405 is a Container Network Function Life-cycle Manager (CNFLM).
[0068] The user interface 215 allows the user to create and submit requests for CNF instantiation. The user interface 215 acts as the communication bridge between the life cycle manager 405 and the microservice 410. In an embodiment, the microservice 415 is a Platform Scheduler & Cron Job Micro Service (PSC).
[0069] The user interface 215 ensures that CNF requests are properly communicated and provides a platform for users to input the CNF requirements, view status updates, and manage the lifecycle of CNFs. The user interface 215 handles the submission of CNF requests from users to the life cycle manager 405. The user interface 215 facilitates further actions or queries to PEEGN410 based on the user instruction.
[0070] Upon CNF instantiation request is initiated either from the user interface 215 or the system-triggered event, the life cycle manager 405 transmits the request to the PEEGN 410. The request typically involves asking the PEEGN 410 to check the network policies and determine the one or more resources required for deploying the CNF instantiation. The life cycle manager 405 depends on the PEEGN 410 to check and validate the CNF policy requirements. The PEEGN 410 evaluates the policies related to the CNF request which includes, but is not limited to compliance with network standards, security protocols, and resource allocation rules.
[0071] Subsequently, the life cycle manager 405 requests the PEEGN 410 to reserve the one or more resources for the CNF instantiation. The PEEGN 410 after interacts with the inventory manager 420 to allocate the appropriate one or more resources such as, but not limited to, physical or/and virtual as per the policy requirements and availability and the life cycle manager 405 ensures that the CNF deployment remains the policies checked by the PEEGN 410.
[0072] Once the PEEGN 410 confirms resource availability and policy compliance, the life cycle manager 405 proceeds with deploying the CNF using the one or more reserved resources. The life cycle manager 405 manages the lifecycle of the CNF instantiation including, but not limited to deployment, scaling, and eventual termination or removal, based on the one or more resources allocated and policies required. In the event any issues arise during the one or more resource reservation or policy checks, the life cycle manager 405 may receive feedback from the PEEGN 410. Additionally, the life cycle manager 405 may provide updates and status reports to the PEEGN 410 regarding the CNF instantiation process and reports help the PEEGN 410 to monitor and review the resource usage and policy observance throughout the CNFs lifecycle.
[0073] Upon checking CNF policy and the one or more reserve resources in the PEEGN 410 by the life cycle manager 405, the microservice 415 is connected to the PEEGN 410 via the network 105 for scheduling the tasks in CNF instantiation at specified time intervals. In an embodiment, the microservice for example, g built-in cron schedules of 1 minute, 15 minutes, 1 hour, or 1 day, and customizable intervals, with the capability to store task results or send them directly to the user. The microservice 415 schedules the task to unreserve the one or more resources. The one or more resources are tracked and managed by the inventory manager 420. If the CNF instantiation fails, the microservice 415 sends the request to the inventory manager 420 to unreserve the one or more resources. Conversely, if the CNF instantiation succeeds, the microservice 415 deletes the scheduled un-reservation task.
[0074] Upon receiving the unreserve request from the microservice 415, the inventory manager 420 frees up the one or more resources. The inventory manager 420 interacts with the microservice 415 to receive scheduling commands for resource-related tasks, such as, reserving or/and un-reserving resources. The inventory manager 420 is responsible for managing both physical and virtual resources, ensuring that resource availability and usage are accurately tracked and managing the allocation of the one or more resources required for the CNF instantiation and scaling. The inventory manager 420 is connected to the microservice 415 via the network 105, and the database 220 is connected to the inventory manager 420 via the network 105. The inventory manager 420 updates database 220 with details about the status of reserved and unreserved the one or more resources, ensuring that the database 220 reflects the current state of the one or more resource allocation and availability. The inventory manager 420 tracks and updates the status of the one or more resources to indicate whether the one or more resources are reserved or available, providing accurate information for resource planning and management.
[0075] FIG. 5 is a signal flow diagram to manage resource reservation during the CNF instantiation, according to one or more embodiments of the present invention.
[0076] At step 505, the user interface 215 starts the process by sending the request to create or instantiate the CNF to the life cycle manager 405. This request includes all necessary details about the CNF instantiation that needs to be instantiated.
[0077] At step 510, upon receiving the request, the life cycle manager 405 processes by querying or requesting to the PEEGN 410 and involves checking if the one or more resources needed for the CNF instantiation are available and if any policies related to resource allocation need to be required and the life cycle manager 405 may provide updates and status reports to the PEEGN 410 regarding the CNF instantiation process.
[0078] At step 515, upon receiving the query from the life cycle manager 405, the PEEGN 410 proceeds to request the inventory manager 420 to reserve the one or more resources. The PEEGN 410 ensures that the resources allocated submit with any relevant policies.
[0079] At step 520, upon receiving the request to reserve the one or more resources from the life cycle manager 405, the inventory manager 420 calculates available resources and reserves the necessary resources for the CNF and updates the database 220 with the details of the one or more reserved resources. The process ensures that the one or more resources are marked as reserved and are not available for other tasks.
[0080] At step 525, subsequently, the inventory manager 420 notifies or enables the microservice 415 to schedule the task that will unreserve the one or more resources if needed. The task is set up as the precaution to confirm that the one or more resources may be freed if the CNF instantiation does not complete successfully.
[0081] At step 530, upon failure instantiation of the CNF, the microservice 415 sends the request to the inventory manager 420 to free the one or more resources previously allocated and ensures that the one or more resources are released and may be reused for other purposes.
[0082] At step 535, upon successful instantiation of the CNF, the scheduled task for un-reserving the one or more resources are deleted by the microservice 415 and prevents unnecessary un-reservation of the one or more resources that are now actively being used by the successfully instantiated CNF.
[0083] At step 540, upon successful instantiation of the CNF, the microservice 415 notifies the life cycle manager 405. The life cycle manager 405 subsequently transmits the final response to the user interface 215 and the user interface 215 processes the response and dispatches the notification to the user.
[0084] FIG. 6 is a flow diagram of a method 600 to manage resource reservation during the CNF instantiation, according to one or more embodiments of the present invention. For the purpose of description, the method 600 is described with the embodiments as illustrated in FIG. 2 and should nowhere be construed as limiting the scope of the present disclosure.
[0085] At step 605, the method 600 includes the step of receiving the request from the user to initiate the CNF instantiation. The method 600 for initiating the CNF instantiation, includes the steps of updating the status of reserved one or more resources at the database 220.
[0086] At step 610, the method 600 includes the step of transmitting the request to the life cycle manager for reserving one or more resources for the CNF instantiation. The lifecycle manager determines available resources in the inventory manager on receipt of the request for the reserving the one or more resources. On transmitting the unreserve request to the life cycle manager on failure of the CNF instantiation, the method includes the step of assigning the state for the one or more un-reserved resources as available resources
[0087] At step 615, the method 600 includes the step of reserving the one or more resources as per the request for the CNF instantiation. The one or more resources is at least one of the CPU, memory, and bandwidth.
[0088] At step 620, the method 600 further includes the step of scheduling the task at the microservice 415 to un-reserve the one or more resources. The microservice 415 is capable of running tasks at the pre-defined time interval configured as per the user.
[0089] At step 625, the method 600 further includes the step of transmitting the unreserve request to the life cycle manager on failure of the CNF instantiation. The method is at least one of, the async event-based implementation method, the one or more resources are marked as un-reserved in one of, a termination flow and the CNF instantiation failure.
[0090] At step 620, the method 600 further includes the step of deleting the scheduled task at the microservice 415 pertaining to un-reserving the one or more resources on successful instantiation of the CNF.
[0091] The present invention further discloses a non-transitory computer-readable medium having stored thereon computer-readable instructions. The computer-readable instructions are executed by the processor 205. The processor 205 is configured to receive the request from the user to initiate the CNF instantiation. The processor 205 is configured to transmit the request to the life cycle manager for reserving one or more resources for the CNF instantiation. The processor 205 is configured to reserve the one or more resources as per the request for the CNF instantiation. The processor 205 is configured to schedule the task at the microservice 415 to un-reserve the one or more resources. The processor 205 is configured to transmit the unreserve request to the life cycle manager on failure of the CNF instantiation. The processor 205 is configured to delete the scheduled task at the microservice 415 pertaining to un-reserving the one or more resources on successful instantiation of the CNF.
[0092] A person of ordinary skill in the art will readily ascertain that the illustrated embodiments and steps in description and drawings (FIG.1-6) are set out to explain the exemplary embodiments shown, and it should be anticipated that ongoing technological development will change the manner in which particular functions are performed. These examples are presented herein for purposes of illustration, and not limitation. Further, the boundaries of the functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. Such alternatives fall within the scope and spirit of the disclosed embodiments.
[0093] The present disclosure incorporates technical advancement by integrating the microservice with the inventory manager. The invention introduces the automated scheduling mechanism for resource reservation and un-reservation tasks based on the CNF instantiation outcome. The system dynamically adjusts resource allocation, updates the database in real-time, and handles asynchronous events for both successful and failed CNF instantiations, enhancing resource efficiency and management precision.
[0094] The present invention offers multiple advantages that enhanced failure management quickly identifies and addresses CNF instantiation failures by automatically un-reserving resources, avoiding blockages. The invention helps in efficient resource lifecycle management ensures optimized resource handling through real-time updates and scheduled un-reservation tasks and also reduced administrative overhead simplifies operations by automating the processes, minimizing manual intervention. Also, the invention helps in scalability and flexibility which are supported through adaptable scheduling and resource management for diverse scenarios. Lastly, the invention helps to improve resource tracking by providing accurate availability records, enhancing planning and allocation.
[0095] The present invention offers multiple advantages over the prior art and the above listed are a few examples to emphasize on some of the advantageous features. The listed advantages are to be read in a non-limiting manner.

REFERENCE NUMERALS

[0096] Environment- 100
[0097] User Equipment (UE) - 110
[0098] Server- 115
[0099] Network- 105
[00100] System -120
[00101] Processor- 205
[00102] Memory- 210
[00103] User interface- 215
[00104] Database- 220
[00105] Receiving unit - 225
[00106] Updating unit - 230
[00107] Transmitting unit - 235
[00108] Assigning unit - 240
[00109] Reserving unit - 245
[00110] Scheduling unit - 250
[00111] Deletion unit - 255
[00112] Primary processor - 305
[00113] Primary Memory - 310
[00114] Life-cycle Manager - 405
[00115] Policy Execution Engine (PEEGN) – 410
[00116] Microservice - 415
[00117] Inventory manager - 420
,CLAIMS:CLAIMS:
We Claim:
1. A method (600) for managing resource reservation during a Container Network Function (CNF) instantiation, the method (600) comprises the steps of:
receiving, by the one or more processors (205), a request from a user to initiate the CNF instantiation;
transmitting, by the one or more processors (205), a request to a life cycle manager (405) for reserving one or more resources for the CNF instantiation; and
reserving, by the one or more processors (205), the one or more resources as per the request for the CNF instantiation;
scheduling, by one or more processors (205), a task at a microservice to un-reserve the one or more resources;
transmitting, by the one or more processors (205), an unreserve request to the life cycle manager (405) on failure of the CNF instantiation; and
deleting, by the one or more processors (205), the scheduled task at the microservice (415) pertaining to un-reserving the one or more resources.

2. The method (600) as claimed in claim 1, wherein the lifecycle manager (405) determines available resources in an inventory manager (420) on receipt of the request for the reserving the one or more resources.
.

3. The method (600) as claimed in claim 1, wherein the one or more resources is at least one of a Central Processing Unit (CPU), memory, and bandwidth.

4. The method (600) as claimed in claim 1, wherein the method (600) for initiating the CNF instantiation, includes the steps of:

updating, by the one or more processors (205), status of reserved one or more resources at a database (220).

5. The method (600) as claimed in claim 1, wherein the microservice (415) is capable of running tasks at a pre-defined time interval configured as per the user.

6. The method (600) as claimed in claim 1, wherein on transmitting the unreserve request to the life cycle manager (405) on failure of the CNF instantiation, the method comprises the step of:
assigning a state for the one or more un-reserved resources as available resources.

7. The method (600) as claimed in claim 1, wherein the method (600) is at least one of, an async event-based implementation method, wherein the one or more resources are marked as un-reserved in one of, a termination flow and the CNF instantiation failure.

8. A system (120) for managing resource reservation during a Container Network Function (CNF) instantiation, the system (120) comprising:
a receiving unit (225), configured to, receive, a request from a user to initiate the CNF instantiation;
a transmitting unit (235), configured to, transmit, a request to a life cycle manager (405) for reserving one or more resources for the CNF instantiation; and
a reserving unit (245), configured to, reserve, the one or more resources as per the request for the CNF instantiation;
a scheduling unit (250), configured to, schedule, a task at a microservice (415) to un-reserve one or more resources;
the transmitting unit (235), configured to, transmit, an unreserve request to the life cycle manager (405) on failure of the CNF instantiation; and
a deletion unit (255), configured to, delete, the scheduled task at the microservice (415) pertaining to un-reserving the one or more resources on successful instantiation of the CNF.

9. The system (120) as claimed in claim 8, wherein the lifecycle manager (405) determines available resources in an inventory manager (420) on receipt of the request for the reserving the one or more resources.

10. The system (120) as claimed in claim 8, wherein the one or more resources is at least one of a Central Processing Unit (CPU), memory, and bandwidth.

11. The system (120) as claimed in claim 8, wherein the system (120) initiates the CNF instantiation, includes the steps of:
an updating unit (230), configured to, update a status of reserved one or more resources at a database (220).

12. The system (120) as claimed in claim 8, wherein the microservice (415) is capable of running tasks at a pre-defined time interval configured as per the user.

13. The system (120) as claimed in claim 8, wherein on transmitting unit (235), configured to, transmits the unreserve request to the life cycle manager (405) on failure of the CNF instantiation, the system (120) comprises the step of:
an assigning unit (240), configured to, assigning a state for the one or more un-reserved resources as available resources.

14. The system (120) as claimed in claim 8, wherein the system (120) is at least one of an async event-based implementation, wherein the one or more resources are marked as un-reserved in one of, a termination flow and the CNF instantiation failure.

15. A User Equipment (UE) (110), comprising:
one or more primary processor (305) communicatively coupled to one or more processors (205), the one or more primary processors (305) coupled with a memory (310), wherein said memory (310) stores instructions which when executed by the one or more primary processors (305) causes the UE (110) to:
transmit, a request to initiate the CNF instantiation to the one or more processors;
wherein the one or more processors are configured to perform the steps as claimed in claim 1.