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
SYSTEM AND METHOD FOR HANDLING A PLURALITY OF REQUESTS
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 disclosure relates to network management, more particularly relates to a system and method for handling a plurality of requests.
BACKGROUND OF THE INVENTION
[0002] Various applications are employed in communication systems to provide a wide range of services. However, the applications often face limitations in terms of the number of requests they can efficiently handle. When the incoming request traffic exceeds a certain threshold, these applications become overwhelmed, leading to failures and the inability to process additional orders or requests. Such failures can have detrimental effects on the overall system performance and can disrupt the smooth operation of critical services.
[0003] The primary objective of the present invention is to provide a system and method for effectively analyzing and managing high incoming request traffic in heavy applications. By doing so, the invention aims to prevent failures caused by exceeding the application's capacity limit, ensuring reliable and uninterrupted service provision even under heavy load conditions.
SUMMARY OF THE INVENTION
[0004] One or more embodiments of the present disclosure provide a system and a method for handling a plurality of requests.
[0005] In one aspect of the present invention, a system for handling a plurality of requests is disclosed. The system includes a receiving unit. The receiving unit is configured to receive the plurality of requests from a North Bound Interface (NBI) for execution by an application. The system includes an identification unit. The identification unit is configured to identify the number of the plurality of requests received. The system includes a comparison unit. The comparison unit is configured to compare the number of the plurality of requests with a threshold limit of requests for execution by the application. The system includes a transmittal unit. The transmittal unit is configured to transmit the plurality of requests to a network node if the number of the plurality of requests is less than the threshold limit of requests based on the comparison. The system includes a queueing unit. The queueing unit is configured to queue one or more excess requests from the plurality of requests in a database if the number of the plurality of requests is greater than the threshold limit based on the comparison.
[0006] In one embodiment, the application is adapted to provide services.
[0007] In one embodiment, the threshold limit is a predefined limit defined by a service provider based on network capacity and network traffic.
[0008] In one embodiment, the comparison unit is configured to determine, number of additional requests which are required to be transmitted to the network node by comparing the number of the plurality of requests with the threshold limit in response to the number of the plurality of requests received being lesser than the threshold limit.
[0009] In one embodiment, the comparison unit is configured to check if the one or more excess requests queued in the database aligns with the determined number of additional requests which are required to be transmitted to the network node in response to the number of the plurality of requests received being lesser than the threshold limit.
[0010] In one embodiment, the comparison unit is configured to transmit, by the one or more processors, the one or more excess requests which are queued in the database to the network node for processing in response to the number of the plurality of requests received being lesser than the threshold limit.
[0011] In one embodiment, upon checking if the one or more excess requests queued in the database aligns with the determined number of additional requests, the transmittal unit is configured to transmit, the one or more excess requests which are queued in the database to the network node for processing.
[0012] In another aspect of the present invention, a method of handling a plurality of requests is disclosed. The method includes the step of receiving, by one or more processors, the plurality of requests from a North Bound Interface (NBI) for execution by an application. The method includes the step of identifying, by the one or more processors, the number of the plurality of requests received. The method includes the step of comparing, by the one or more processors, the number of the plurality of requests with a threshold limit of requests for execution by the application. The method includes the step of transmitting, by the one or more processors, the plurality of requests to a network node if the number of the plurality of requests is lesser than the threshold limit of requests based on the comparison. The method includes the step of queuing, by the one or more processors, one or more excess requests from the plurality of requests in a database if the number of the plurality of requests is greater than the threshold limit based on the comparison.
[0013] 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
[0014] 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.
[0015] FIG. 1 is an exemplary block diagram of an environment for handling a plurality of requests, according to various embodiments of the present invention;
[0016] FIG. 2 is a schematic representation of the present system of FIG. 1 for handling the plurality of requests, according to various embodiments of the present invention;
[0017] FIG. 3 is an exemplary embodiment of the system for high incoming request traffic analysis and management, according to various embodiments of the present invention; and
[0018] FIG. 4 illustrates a flow diagram of a method of handling the plurality of requests, according to various embodiments of the present invention.
[0019] The foregoing shall be more apparent from the following detailed description of the invention.
DETAILED DESCRIPTION OF THE INVENTION
[0020] 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.
[0021] 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.
[0022] 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.
[0023] As per various embodiments depicted, the present invention discloses a system and method for handling a plurality of requests. The present invention introduces the system for bidirectional communication and request handling mechanism between a North Bound Interface (NBI) and a Fulfillment Management System (FMS). The system employs a queue to manage high incoming request traffic that exceeds the processing capacity of the FMS. The requests are received by the NBI, processed by the FMS, and forwarded to network nodes for execution. Any requests beyond the FMS capacity are stored in a database in the queue, ensuring that they are not lost. When the system load decreases, the FMS retrieves the requests from the database for processing and delivers the results to the NBI for further handling. By effectively managing the requests and employing the queue-based approach, the system ensures reliable and uninterrupted service provision even under heavy load conditions.
[0024] Referring to FIG. 1, FIG. 1 illustrates an exemplary block diagram of an environment for handling a plurality of requests, according to various embodiments of the present invention. The environment 100 includes a User Equipment (UE) 102, a network 104, a server 106, and a system 108. In one embodiment, the UE 102 is at least one of a first UE 102a, a second UE 102b, and a third UE 102c. The first UE 102a, the second UE 102b and the third UE 102c are communicatively connected to the system 108 via the network 104.
[0025] The first UE 102a, the second UE 102b and the third UE 102c will henceforth collectively and individually be referred to as “the UE 102” without limiting the scope and deviating from the scope of the present disclosure.
[0026] In one embodiment, each of the at least first UE 102a, the second UE 102b, and the third UE 102c are configured to transmit a request from the UE 102 to access an application. Moreover, the application is adapted to provide one or more services. The one or more services includes for example, a payment service, a Customer Relationship Management (CRM) system, an online storefront, an order management system, an Inventory Management System (IMS), a cloud service, charging and billing related services etc.
[0027] The UE 102 includes, but are not limited to, a handheld wireless communication device (e.g., a mobile phone, a smart phone, a tablet device, and so on), a wearable computer device (e.g., a head-mounted display computer device, a head-mounted camera device, a wristwatch computer device, and so on), a Global Positioning System (GPS) device, a laptop computer, a tablet computer, or another type of portable computer, a media playing device, a portable gaming system, and/or any other type of computer device with wireless communication capabilities, and the like.
[0028] The environment 100 includes the server 106 communicably coupled to the UE 102 via the network 104. The server 106 includes 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, a defence facility, or any other facility that provides content.
[0029] The network 104 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 104 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.
[0030] The network 104 also includes, by the way of example but not limitation, one or more wireless interfaces/protocols such as, for example, 802.11 (Wi-Fi), 802.15 (including Bluetooth™), 802.16 (Wi-Max), 802.22, Cellular standards such as CDMA, CDMA2000, WCDMA, Radio Frequency (e.g., RFID), Infrared, laser, Near Field Magnetics, etc.
[0031] The environment further includes the system 108 communicably coupled to the server 106 and the UE 102 via the network 104. The system 108 is configured to handle the plurality of requests from the UE 102 in the network 104. In one embodiment, the plurality of requests is for execution by the application. In one embodiment, the application is adapted to provide one or more services. Further, the system 108 is adapted to be embedded within the server 106 or embedded as the individual entity. However, for the purpose of description, the system 108 is described as an integral part of the server 106, without deviating from the scope of the present disclosure.
[0032] Operational and construction features of the system 108 will be explained in detail with respect to the following figures.
[0033] Referring to FIG. 2, FIG. 2 illustrates a schematic representation of the present system 108 of FIG. 1 for handling the plurality of requests according to various embodiments of the present invention. As per the illustrated embodiment, the system 108 includes one or more processors 202, a memory 204, an Input/Output (I/O) user interface 206, a display unit 208, an input device 210 and a database unit 222. The one or more processors 202, hereinafter referred to as the processor 202 is 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. As per the illustrated embodiment, the system 108 includes one processor 202. However, it is to be noted that the system 108 may include multiple processors as per the requirement and without deviating from the scope of the present disclosure.
[0034] Among other capabilities, the processor 202 is configured to fetch and execute computer-readable instructions stored in the memory 204. The memory 204 is 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 RAM, or non-volatile memory such as EPROM, flash memory, and the like.
[0035] In an embodiment, the I/O user interface 206 includes a variety of interfaces, for example, interfaces for data input and output devices, referred to as Input/Output (I/O) devices, storage devices, and the like. The I/O user interface 206 facilitates communication of the system 108. In one embodiment, the I/O user interface 206 provides a communication pathway for one or more components of the system 108.
[0036] The I/O interface unit 206 may include functionality similar to at least a portion of functionality implemented by one or more computer system interfaces such as those described herein and/or generally known to one having ordinary skill in the art. The I/O user interface 206 is rendered on the display unit 208, implemented using LCD display technology, OLED display technology, and/or other types of conventional display technology. The display unit 208 is integrated within the system 108 or connected externally. Further, the input device 210 may include, but not limited to, keyboard, buttons, scroll wheels, cursors, touchscreen sensors, audio command interfaces, magnetic strip reader, optical scanner, etc.
[0037] The system 108 further comprises the database unit 222. The database unit 222 is communicably connected to the processor 202, and the memory 204. The database unit 222 is configured to store and retrieve the request related data. The database 222 provides structured storage, support for complex queries, and enables efficient data retrieval and analysis. The database 222 is one of, but is not limited to, one of 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 types are non-limiting and may not be mutually exclusive e.g., a database can be both commercial and cloud-based, or both relational and open-source, etc.
[0038] Further, the processor 202, 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 202. 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 202 may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for processor 202 may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the memory 204 may store instructions that, when executed by the processing resource, implement the processor 202. In such examples, the system 108 may comprise the memory 204 storing the instructions and the processing resource to execute the instructions, or the memory 204 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.
[0039] In order for the system 108 to handle the plurality of requests, the processor 202 includes a receiving unit 212, an identification unit 214, a comparison unit 216, a transmittal unit 218, and a queueing unit 220 communicably coupled to each other for handling the plurality of requests.
[0040] The receiving unit 212 of the processor 202 is communicably connected to the UE 102 of the user, via the network 104. Accordingly, the receiving unit 212 is configured to receive an incoming rate of the plurality of requests from a North Bound Interface (NBI) 302 (as shown in FIG.3) for execution by the application. The NBI 302 refers to an interface or communication channel through which higher-level software applications, such as management systems or orchestrators, interact with lower-level components in the system 108. In one embodiment, the application is adapted to provide the one or more services.
[0041] In one embodiment, the one or more services includes for example, but not limited to the payment services, the CRM systems, the online storefronts, the order management systems, the IMS and the cloud services, charging and billing related services etc. After receiving the plurality of requests, the receiving unit 212 is configured to transmit the plurality of requests to the identification unit 214.
[0042] On receipt of the plurality of requests, the identification unit 214 is configured to identify the number of the plurality of requests received from the NBI 302 for execution by the application. After identifying the number of the plurality of requests, the identification unit 214 is configured to transmit the number of plurality of requests to the comparison unit 216.
[0043] Upon receiving the number of plurality of requests, the comparison unit 216 is configured to compare the received number of the plurality of requests with a threshold limit of requests for the execution process. In one embodiment, the threshold limit of the request is a predefined limit defined by a service provider based on the network capacity and the network traffic. Further, the comparison unit 216 is configured to generate the comparison data.
[0044] In one embodiment, the comparison data includes the comparison of the number of the plurality of requests with the threshold limit of requests. In another embodiment, the comparison data includes the number of the plurality of requests received is less than the threshold limit of the requests. Further, the comparison data includes the number of the plurality of requests received is equal to and less than the threshold limit of the requests. In yet another embodiment, the comparison data includes the number of the plurality of requests received is greater than the threshold limit of the requests.
[0045] In one embodiment, based on the comparison data, the transmittal unit 218 configured to transmit the plurality of requests to the one or more network nodes 304 (as shown in FIG.3) if the number of the plurality of requests is lesser than the threshold limit of requests. The one or more network nodes 304 includes, but not limited to a first network node 304a, and a second network node 304b where both network nodes are part of a workflow request received from the NBI 302.
[0046] Further, the comparison unit 216 is configured to determine the number of additional requests which are required to be transmitted to the one or more network nodes 304 by comparing the number of the plurality of requests with the threshold limit. On determination of the number of additional requests, the queueing unit 220 is configured to queue the one or more excess requests from the plurality of requests in the database 222. The database 222 stores the one or more excess requests, i.e. the number of the plurality of requests is greater than the threshold limit based on the received comparison data.
[0047] As per the illustrated embodiment, the comparison unit 216 is configured to check if the one or more excess requests queued in the database 222 aligns with the determined number of additional requests when the one or more excess requests are equal to or less than the threshold limit. Upon checking if the one or more excess requests queued in the database 222 aligns with the determined number of additional requests, the transmittal unit 218 is configured to transmit the one or more excess requests which are queued in the database 222 to the one or more network nodes 304 for processing. When the number of the plurality of requests received is less than the threshold limit of the requests, the already queued one or more requests is aligned with the determined number of additional requests. For example, let us consider the threshold limit is 100 but the system receives 110 requests, the remaining 10 requests are stored in the database 222 in the queue. When the system 108 receives the one or more excess requests are 90, at that time, the queued 10 requests in the database 222 are also added with the one or more excess requests 90 for processing the request.
[0048] Advantageously, the system 108 utilizes the queue to handle high incoming request traffic that surpasses the processing capacity. By leveraging a database-backed queue, the system 108 ensures the efficient storage, retrieval, and processing of excess requests, preventing failures and enhancing overall performance of the system 108.
[0049] Referring to FIG. 3, FIG. 3 illustrates an exemplary embodiment of the system 108 for traffic analysis and management of plurality of requests, according to various embodiments of the present invention.
[0050] The system 108 includes the NBI 302, the one or more network nodes 304, and the database 222. It is to be however noted that the one or more network nodes 304 is only described with respect to the first network node 304a and the second network node 304b for the purpose of description and illustration and should nowhere be construed as limiting the scope of the present disclosure.
[0051] In one embodiment, the NBI 302 serves as the interface through which the plurality of requests is received by the system 108. For example, the system 108 receives 500 requests per second for execution by the application. The system 108 is responsible for managing and processing the incoming plurality of requests.
[0052] The system 108 is configured to receive the entire plurality of requests from the NBI 302 and processes the plurality of requests based on the threshold limit of the request by the application. For example, let us consider, the threshold limit of the request is 400 requests per second but the system 108 receives 500 requests per second. In this situation, the transmittal unit 218 transmits the 400 requests per second to the first network node 304a and the second network node 304b. The remaining 100 requests will not be processed immediately but will be stored in the database 222 in the queue.
[0053] The first network node 304a and the second network node 304b are configured for executing the 400 requests after being forwarded by the system 108. The first network node 304a and the second network node 304b perform the operations of the 400 requests and deliver the desired results. The desired results refer to successful completion of execution of the plurality of requests and encapsulates the intended outcome that drives the execution of the plurality of requests by the one or more network nodes 304. The desired result represents the successful fulfillment of the requirements associated with the plurality of requests, ensuring that the system 108 delivers an output value to the service provider.
[0054] The system 108 employs the queue of the 100 requests, which is stored in the database 222. The database 222 serves as a temporary storage to maintain the remaining queue of the 100 excess requests per second until the remaining queue of the requests are processed. The transmittal unit 218 is configured to transmit the 100 excess requests which are queued in the database 222 to the first network node 304a and the second network node 304b for processing in the event the number of the plurality of requests received is lesser than the threshold limit of the requests.
[0055] Referring to FIG. 4, FIG. 4 illustrates a flow chart of the method 400 for handling the plurality of requests, according to one or more embodiments of the present invention. The method 400 is adapted to handle the plurality of requests in the network 104. For the purpose of description, the method 400 is described with the embodiments as illustrated in FIG. 1 and should nowhere be construed as limiting the scope of the present disclosure.
[0056] At step 402, the method 400 includes the step of receiving the plurality of requests from the North Bound Interface (NBI) for execution by the application. In one embodiment, the application is adapted to provide one or more services. After receiving the plurality of requests, the receiving unit 212 is configured to transmit the plurality of requests to the identification unit 214.
[0057] At step 404, the method 400 includes the step of identifying number of the plurality of requests by the identification unit 214. The identification unit 214 is configured to identify the number of the plurality of requests received from the NBI for execution by an application. After identifying the number of the plurality of requests, the identification unit 214 is configured to transmit the number of the plurality of requests to the comparison unit 216.
[0058] At step 406, the method 400 includes the step of comparing the number of the plurality of requests with a threshold limit of requests by the comparison unit 216. The comparison unit 216 is configured to compare the number of the plurality of requests with a threshold limit of requests for the execution process. In one embodiment, the threshold limit of the request is a predefined limit defined by a service provider based on network capacity and the network traffic. Further, the comparison unit 216 is configured to generate the comparison data.
[0059] At step 408, the method 400 includes the step of transmitting the plurality of requests to the one or more network nodes 304 by the transmittal unit 220 if the number of the plurality of requests is lesser than the threshold limit of requests based on the comparison data.
[0060] At step 410, the method 400 includes the step of queueing the one or more excess requests from the plurality of requests by the queueing unit 218 in the database 222 if the number of the plurality of requests is greater than the threshold limit based on the comparison. Upon receiving the one or more excess requests that are queued in the database 222, the transmittal unit 220 is configured to transmit the one or more excess requests that are queued in the database 222 to the one or more network nodes 304 for executing the request, when the number of requests received by the system 108 is reduced.
[0061] In an embodiment, the present invention further discloses a non-transitory computer-readable medium having stored thereon computer-readable instructions. The computer-readable instructions are executed by a processor 202.The processor 202 is configured to receive the plurality of requests from a North Bound Interface (NBI) for execution by an application. The processor 202 is further configured to identify, number of the plurality of requests received. The processor 202 is further compare, the number of the plurality of requests with a threshold limit of requests for execution by the application The processor 202 is further configured to transmit, the plurality of requests to a network node if the number of the plurality of requests is lesser than the threshold limit of requests based on the comparison. The processor 202 is configured to queue the one or more excess requests from the plurality of requests in the database 222 if the number of the plurality of requests is greater than the threshold limit based on the comparison.
[0062] A person of ordinary skill in the art will readily ascertain that the illustrated embodiments and steps in description and drawings (FIG.1-4) 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.
[0063] The present disclosure incorporates technical advancement by handling the plurality of requests. The method provides high incoming request traffic analysis and management by providing an efficient and reliable approach to handle heavy request traffic in applications. By expanding the serving capacity, preventing failures, and optimizing resource allocation, the invention offers significant advantages in terms of system performance, reliability, and scalability. This ensures that the system can accommodate sudden spikes in traffic or increased demand without encountering failures or service interruptions. The system enhances the overall performance and stability of applications by intelligently distributing requests across multiple instances or servers, load balancing techniques ensure optimal resource utilization and reduce response times.
[0064] 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
[0065] Environment - 100;
[0066] User Equipment- 102;
[0067] Network - 104;
[0068] System-106;
[0069] Server-108;
[0070] Processor(s) -202;
[0071] Memory- 204;
[0072] Input/Output (I/O) user interface-206;
[0073] Display unit- 208;
[0074] Input device-210;
[0075] Receiving unit-212;
[0076] Identification unit -214;
[0077] Comparison unit-216;
[0078] Queueing unit-218;
[0079] Transmittal unit-220;
[0080] Database -222.

,CLAIMS:
CLAIMS
We Claim
1. A method (400) of handling a plurality of requests, the method (400) comprising the steps of:
receiving, by one or more processors (202), the plurality of requests from a North Bound Interface (NBI) (302) for execution by an application;
identifying, by the one or more processors (202), number of the plurality of requests received;
comparing, by the one or more processors (202), the number of the plurality of requests with a threshold limit of requests for execution by the application;
transmitting, by the one or more processors (202), the plurality of requests to a network node if the number of the plurality of requests is lesser than the threshold limit of requests based on the comparison; and
queuing, by the one or more processors (202), one or more excess requests from the plurality of requests in a database (222) if the number of the plurality of requests is greater than the threshold limit based on the comparison.

2. The method (400) as claimed in claim 1, wherein the application is adapted to provide services.

3. The method (400) as claimed in claim 1, wherein the threshold limit is a predefined limit defined by a service provider based on network capacity and network traffic.

4. The method (400) as claimed in claim 1, wherein in response to the number of the plurality of requests received being lesser than the threshold limit, the method (400) comprises the steps of:
determining, by the one or more processors (202), number of additional requests which are required to be transmitted to the network node by comparing the number of the plurality of requests with the threshold limit;
checking, by the one or more processors (202), if the one or more excess requests queued in the database (222) aligns with the determined number of additional requests which are required to be transmitted to the network node;
transmitting, by the one or more processors (202), the one or more excess requests which are queued in the database (222) to the network node for processing.

5. The method (400) as claimed in claim 5, wherein the one or more processors (202), checks if the one or more excess requests queued in the database (222) aligns with the determined number of additional requests, when the one or more excess requests are equal to or less than the threshold limit.

6. The method (400) as claimed in claim 5, wherein upon checking if the one or more excess requests queued in the database (222) aligns with the determined number of additional requests, the transmittal unit (218) is configured to transmit, the one or more excess requests which are queued in the database (222) to the network node for processing.

7. A system (108) for handling a plurality of requests, the system (108) comprising:
a receiving unit (212) configured to receive, the plurality of requests from a North Bound Interface (NBI) (302) for execution by an application;
an identification unit (214) configured to identify, number of the plurality of requests received;
a comparison unit (216) configured to compare, the number of the plurality of requests with a threshold limit of requests for execution by the application;
a transmittal unit (218) configured to transmit, the plurality of requests to a network node if the number of the plurality of requests is lesser than the threshold limit of requests based on the comparison; and
a queueing unit (220) configured to queue, one or more excess requests from the plurality of requests in a database (222) if the number of the plurality of requests is greater than the threshold limit based on the comparison.

8. The system (108) as claimed in claim 8, wherein the application is adapted to provide services.

9. The system (108) as claimed in claim 8, wherein the threshold limit is a predefined limit defined by a service provider based on network capacity and network traffic.

10. The system (108) as claimed in claim 8, wherein in response to the number of the plurality of requests received being lesser than the threshold limit, the comparison unit (216) is configured to:
determine, number of additional requests which are required to be transmitted to the network node by comparing the number of the plurality of requests with the threshold limit;
check, if the one or more excess requests queued in the database (222) aligns with the determined number of additional requests which are required to be transmitted to the network node; and
transmit, the one or more excess requests which are queued in the database (222) to the network node for processing.

11. The system (108) as claimed in claim 12, wherein comparison unit (216) is configured to check if the one or more excess requests queued in the database (222) aligns with the determined number of additional requests, when the one or more excess requests are equal to or less than the threshold limit.

12. The system (108) as claimed in claim 12, wherein upon checking if the one or more excess requests queued in the database (222) aligns with the determined number of additional requests, the transmittal unit (218) is configured to transmit, the one or more excess requests which are queued in the database (222) to the network node for processing.