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 IDENTIFYING STATE OF SUBSCRIBER
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 to communications and networks, more particularly relates to a method and a system for automatically managing a state of subscribers registered to the networks.
BACKGROUND OF THE INVENTION
[0002] The 3rd Generation Partnership Project (3GPP) plays a crucial role in setting the standards for mobile communication systems. In the 3GPP, an Application Programming Interface (API) driven steps are defined to onboard an authorized API provider to a Common Application Programming Interface Frameworks (CAPIF) system. There are users of the API, often called API consumers, who usually subscribe to use the API for using its application, features and services. In real time, some of these users do not utilize the services of the API, or never subscribed to the API, or have remained inactive for a significant duration. An issue arises due to the way the conventional system handles these users. Despite their lack of engagement or ongoing subscription status, conventional systems categorize them as "Active Users." This will affect the reports that are being generated by API publishers. Moreover, this classification misstep leads to the inclusion of their data in various internal data manipulation processes that are conducted to enhance the system performance, which makes the system ineffective in practice due to the inherent discrepancy.
[0003] The utilization of data from inactive or unsubscribed API subscribers in the internal data manipulations introduces inaccuracies into the systems. Consequently, the outcomes and insights generated from these processes become unreliable. Essentially, treating these dormant users as active users skews data representation and compromises the integrity of any decisions or optimizations that rely on this flawed dataset. Further, this dataset being not removed from databases increases the consumption of a memory in the system and may lead to unnecessary storage or storage capacity problems.
[0004] Hence, there exists a need for a system and method to overcome the abovesaid deficiencies of the prior arts, particularly focusing on automatically identifying and evicting the data of stale service API subscribers.
SUMMARY OF THE INVENTION
[0005] One or more embodiments of the present disclosure provide a system and a method for identifying a state of a subscriber.
[0006] In one aspect of the present invention, the method of identifying the state of the subscriber is disclosed. The method includes configuring, by one or more processors, a state identifier pertaining to an Application Programming Interface (API) call. Further, the method includes executing, by the one or more processors, the API call to retrieve API call information pertaining to a User Equipment (UE) of a plurality of UEs based on configuring the state identifier of the respective API call, wherein each UE is associated with a subscriber. Further, the method includes implementing, by the one or more processors, a plurality of rules and a plurality of parameters associated with the state identifier to the retrieved API call information. Further, the method includes determining, by the one or more processors, the state of the subscriber based on the implementation of the plurality of rules and the plurality of parameters to the retrieved API call information. Further, the method includes identifying, by the one or more processors, one or more inactive subscribers based on the determined state of the subscriber.
[0007] In an embodiment, the state identifier includes the plurality of rules and parameters. In an embodiment, configuring the state identifier includes at least one of: reading, appending, and adding the state identifier in run time via at least one of a Command Line Interface (CLI).
[0008] In an embodiment, upon execution, the method comprises the step of logging, by the one or more processors, the API call information in a database.
[0009] In an embodiment, the API call information comprises at least one of: a type of API called, a type of subscriber called, and a number of the API call attempts.
[0010] In an embodiment, upon configuration, the API call is executed in timely intervals, such as daily, weekly, and monthly.
[0011] In an embodiment, the state of the subscriber is one of active, inactive, and temporarily inactive.
[0012] In an embodiment, method includes the step of performing, by the one or more processors, a process to one of deleting the one or more inactive subscribers, disabling the one or more inactive subscribers, temporarily disabling the one or more inactive subscribers upon identification of one or more inactive subscribers.
[0013] In another aspect of the present invention, the system for identifying the state of the subscriber is disclosed. The system includes a configuration unit, an execution unit, an implementation unit, a determination unit and an identification unit. The configuration unit is configured to configure, a state identifier pertaining to an API call. The execution unit is configured to execute, the API call to retrieve API call information pertaining to a UE of a plurality of UEs based on configuring the state identifier of the respective API, where each UE is associated with a subscriber. The implementation unit is configured to implement, a plurality of rules and a plurality of parameters of the state identifier to the retrieved API call information. The determination unit is configured to determine, the state of the subscriber based on the implementation of the plurality of rules and the plurality of parameters to the retrieved API call information. The identification unit is configured to identify, one or more inactive subscribers based on the determined state of the subscriber.
[0014] In another aspect of the present invention, a non-transitory computer-readable medium having stored thereon computer-readable instructions is disclosed. The computer readable instructions when executed by a processor, causes the processor to configure a state identifier pertaining to an API call. The processor is further configured to execute the API call to retrieve API call information pertaining to a UE of a plurality of UEs based on configuring the state identifier of the respective API, where each UE is associated with a subscriber. The processor is configured to implement, a plurality of rules and a plurality of parameters of the state identifier to the retrieved API call information. The processor is further configured to determine the state of the subscriber based on the implementation of the plurality of rules and the plurality of parameters to the retrieved API call information. The processor is further configured to identify one or more inactive subscribers based on the determined state of the subscriber.
[0015] In another aspect of the present invention, a User Equipment (UE) includes one or more primary processors communicatively coupled to one or more processors of a system. The one or more primary processors are coupled with a memory, where the memory stores instructions which when executed by the one or more primary processors causes the UE to transmit a state identifier pertaining to an API call to the one or more processers. The one or more processers are configured to receive the state identifier pertaining to an API call. Further, the one or more processers execute an API call to retrieve API call information pertaining to a UE of a plurality of UEs based on configuring the state identifier of the respective API, where each UE is associated with a subscriber. Further, the one or more processers implement a plurality of rules and a plurality of parameters associated with the state identifier to the retrieved API call information. Further, the one or more processers determine a state of a subscriber based on the implementation of the plurality of rules and the plurality of parameters to the retrieved API call information. Further, the one or more processers identify one or more inactive subscribers based on the determined state of the subscriber.
[0016] 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
[0017] 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.
[0018] FIG. 1 is an exemplary block diagram of an environment for identifying a state of a subscriber, according to various embodiments of the present disclosure.
[0019] FIG. 2 is a block diagram of a system of FIG. 1, according to various embodiments of the present disclosure.
[0020] FIG. 3 is an example schematic representation of the system of FIG. 1 in which various entities operations are explained, according to various embodiments of the present system.
[0021] FIG. 4 shows a block diagram of a system architecture for identifying the state of the subscriber, in accordance with the present disclosure.
[0022] FIG. 5 shows a flow chart of a method for identifying the state of the subscriber, in accordance with another embodiment of the present invention.
[0023] FIG. 6 is an exemplary flow diagram illustrating the method for identifying a state of a subscriber, according to various embodiments of the present disclosure.
[0024] Further, skilled artisans will appreciate that elements in the drawings are illustrated for simplicity and may not have necessarily been drawn to scale. For example, the flow charts illustrate the method in terms of the most prominent steps involved to help to improve understanding of aspects of the present invention. Furthermore, in terms of the construction of the device, one or more components of the device may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the embodiments of the present invention so as not to obscure the drawings with details that will be readily apparent to those of ordinary skill in the art having benefit of the description herein.
[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] Before discussing example, embodiments in more detail, it is to be noted that the drawings are to be regarded as being schematic representations and elements that are not necessarily shown to scale. Rather, the various elements are represented such that their function and general purpose becomes apparent to a person skilled in the art. Any connection or coupling between functional blocks, devices, components, or other physical or functional units shown in the drawings or described herein may also be implemented by an indirect connection or coupling. A coupling between components may also be established over a wireless connection. Functional blocks may be implemented in hardware, firmware, software or a combination thereof.
[0030] Further, the flowcharts provided herein, describe the operations as sequential processes. Many of the operations may be performed in parallel, concurrently or simultaneously. In addition, the order of operations maybe re-arranged. The processes may be terminated when their operations are completed, but may also have additional steps not included in the figured. It should be noted, that in some alternative implementations, the functions/acts/ steps noted may occur out of the order noted in the figured. For example, two figures shown in succession may, in fact, be executed substantially concurrently, or may sometimes be executed in the reverse order, depending upon the functionality/acts involved.
[0031] Further, the terms first, second etc… may be used herein to describe various elements, components, regions, layers and/or sections, it should be understood that these elements, components, regions, layers and/or sections should not be limited by these terms. These terms are used only to distinguish one element, component, region, layer or section from another region, layer, or a section. Thus, a first element, component, region layer, or section discussed below could be termed a second element, component, region, layer, or section without departing form the scope of the example embodiments.
[0032] Spatial and functional relationships between elements (for example, between modules) are described using various terms, including “connected,” “engaged,” “interfaced,” and “coupled.” Unless explicitly described as being “direct,” when a relationship between first and second elements is described in the description below, that relationship encompasses a direct relationship where no other intervening elements are present between the first and second elements, and also an indirect relationship where one or more intervening elements are present (either spatially or functionally) between the first and second elements. In contrast, when an element is referred to as being "directly” connected, engaged, interfaced, or coupled to another element, there are no intervening elements present. Other words used to describe the relationship between elements should be interpreted in a like fashion (e.g., "between," versus "directly between," "adjacent," versus "directly adjacent," etc.).
[0033] The terminology used herein is for the purpose of describing particular example embodiments only and is not intended to be limiting. Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which example embodiments belong. It will be further understood that terms, e.g., those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.
[0034] As used herein, the singular forms “a,” “an,” and “the,” are intended to include the plural forms as well, unless the context clearly indicates otherwise. As used herein, the terms “and/or” and “at least one of” include any and all combinations of one or more of the associated listed items. It will be further understood that the terms “comprises,” “comprising,” “includes,” and/or “including,” when used herein, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
[0035] Unless specifically stated otherwise, or as is apparent from the description, terms such as “processing” or “computing” or “calculating” or “determining” of “displaying” or the like, refer to the action and processes of a computer system, or similar electronic computing device/hardware, that manipulates and transforms data represented as physical, electronic quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the computer system memories or registers or other such information storage, transmission or display devices.
[0036] A glossary used in the patent disclosure.
- 3GPP: The term 3GPP is a 3rd Generation Partnership Project or 3GPP and is a collaborative project between a group of telecommunications associations with the initial goal of developing globally applicable specifications for Third Generation (3G) mobile systems. 3GPP specifications cover cellular telecommunications technologies, including radio access, core network, and service capabilities, which provide a complete system description for mobile telecommunications. The 3GPP specifications also provide hooks for non-radio access to the core network, and for networking with non-3GPP networks.
- CLI : Command Line Interface.
- CAPIF: Common Application Programming Interface Framework.
- AMS : Application Managed Services outsources the task of providing ongoing support for our apps to an external provider that specializes in this type of maintenance and monitoring.
- IAM : Identity and Access Management (IAM) is used for authentication and authorization of the third-party consumers.
- ELB : Edge Load Balancer (ELB) automatically distributes incoming application traffic across multiple targets and virtual appliances in one or more Availability Zones.
- AI/ML :Artificial Intelligence (AI) and Machine Learning (ML).
[0037] Various embodiments of the invention provide a method of identifying a state of a subscriber. The method includes configuring, by one or more processors, a state identifier pertaining to an API call. Further, the method includes executing, by the one or more processors, the API call to retrieve API call information pertaining to a UE of a plurality of UEs based on configuring the state identifier of the respective API call, where each UE is associated with a subscriber. Further, the method includes implementing, by the one or more processors, a plurality of rules and a plurality of parameters of the state identifier to the retrieved API call information. Further, the method includes determining, by the one or more processors, the state of the subscriber based on the implementation of the plurality of rules and the plurality of parameters to the retrieved API call information. Further, the method includes identifying, by the one or more processors, one or more inactive subscribers based on the determined state of the subscriber.
[0038] The present invention provides a solution for detecting inactive API subscribers and removing them from the database to minimize the memory consumption and provide accurate subscription for accessing performance of an API. The present method allows a CAPIF to automatically executes an AI/ML based process installed on the API gateway on a regular interval to identify stale service API subscribers/users who are not using the API and automatically unsubscribe the users from the API. The AI/ML process automatically detects an inactive status of the API subscriber, last used status, or deletion status and accordingly the CAPIF updates the subscriber information in the system.
[0039] In an embodiment of the present invention, a system for identifying a state of the subscriber is disclosed. The system comprises at least one common API gateway, at least one API consumer, and at least one API repository. The at least one API consumer communicates with the common API gateway through a network. The common API gateway is a provisioning server for a 3GPP to onboard and offboard API consumers, register and release APIs.
[0040] FIG. 1 illustrates an exemplary block diagram of an environment (100) for identifying a state of a subscriber, according to various embodiments of the present disclosure. The environment (100) comprises a plurality of user equipment’s (UEs) (102-1, 102-2, ……,102-n). The at least one UE (102-n) from the plurality of the UEs (102-1, 102-2, ……102-n) is configured to connect to a system (108) via a communication network (106). Hereafter, label for the plurality of UEs or one or more UEs is 102.
[0041] In accordance with yet another aspect of the exemplary embodiment, the plurality of UEs (102) may be a wireless device or a communication device that may be a part of the system (108). The wireless device or the UE (102) may include, but are not limited to, a handheld wireless communication device (e.g., a mobile phone, a smart phone, a phablet device, and so on), a wearable computer device (e.g., a head-mounted display computer device, a head-mounted camera device, a wristwatch computer device, and so on), a 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 or Voice over Internet Protocol (VoIP) capabilities. In an embodiment, the UEs (102) may include, but are not limited to, any electrical, electronic, electro-mechanical or an equipment or a combination of one or more of the above devices such as virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other computing device, wherein the computing device may include one or more in-built or externally coupled accessories including, but not limited to, a visual aid device such as camera, audio aid, a microphone, a keyboard, input devices for receiving input from a user such as touch pad, touch enabled screen, electronic pen and the like. It may be appreciated that the UEs (102) may not be restricted to the mentioned devices and various other devices may be used. A person skilled in the art will appreciate that the plurality of UEs (102) may include a fixed landline, and a landline with assigned extension within the communication network (106).
[0042] The communication network (106), may use one or more communication interfaces/protocols such as, for example, Voice Over Internet Protocol (VoIP), 802.11 (Wi-Fi), 802.15 (including Bluetooth™), 802.16 (Wi-Max), 802.22, Cellular standards such as Code Division Multiple Access (CDMA), CDMA2000, Wideband CDMA (WCDMA), Radio Frequency Identification (e.g., RFID), Infrared, laser, Near Field Magnetics, etc.
[0043] The system (108) is communicatively coupled to a server (104) via the communication network (106). The server (104) can be, for example, but not limited to a standalone server, a server blade, a server rack, an application server, a bank of servers, a business telephony application server (BTAS), a server farm, a cloud server, an edge server, home server, a virtualized server, one or more processors executing code to function as a server, or the like. In an implementation, the server (104) may operate at various entities or a single entity (include, but is not limited to, a vendor side, a service provider side, a network operator side, a company side, an organization side, a university side, a lab facility side, a business enterprise side, a defense facility side, or any other facility) that provides service.
[0044] The communication network (106) 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 communication network (106) may include, but is not limited to, a Third Generation (3G) network, a Fourth Generation (4G) network, a Fifth Generation (5G) network, a Sixth Generation (6G) network, a New Radio (NR) network, a Narrow Band Internet of Things (NB-IoT) network, an Open Radio Access Network (O-RAN), and the like.
[0045] The communication network (106) 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 communication network (106) may also include, by way of example but not limitation, one or more of a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a Public-Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, a VOIP or some combination thereof.
[0046] One or more network elements can be, for example, but not limited to a base station that is located in the fixed or stationary part of the communication network (106). The base station may correspond to a remote radio head, a transmission point, an access point or access node, a macro cell, a small cell, a micro cell, a femto cell, a metro cell. The base station enables transmission of radio signals to the UE or mobile transceiver. Such a radio signal may comply with radio signals as, for example, standardized by a 3GPP or, generally, in line with one or more of the above listed systems. Thus, a base station may correspond to a NodeB, an eNodeB, a Base Transceiver Station (BTS), an access point, a remote radio head, a transmission point, which may be further divided into a remote unit and a central unit.
[0047] The environment (100) further includes the system (108) communicably coupled to the server (e.g., remote server or the like) (104) and each UE of the plurality of UEs (102) via the communication network (106). The remote server (104) is configured to execute the requests in the communication network (106).
[0048] The system (108) is adapted to be embedded within the remote server (104) or is embedded as an individual entity. The system (108) is designed to provide a centralized and unified view of data and facilitate efficient business operations. The system (108) is authorized to access to update/create/delete one or more parameters of their relationship between the requests for an API call information, which gets reflected in real-time independent of the complexity of communication network (106).
[0049] In another embodiment, the system (108) may include an enterprise provisioning server (for example), which may connect with the remote server (104). The enterprise provisioning server provides flexibility for enterprises, ecommerce, finance to update/create/delete information related to the requests in real time as per their business needs. A user with administrator rights can access and retrieve the requests for the API call information and perform real-time analysis in the system (108).
[0050] The system (108) 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 business telephony application server (BTAS), 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 implementation, system (108) may operate at various entities or single entity (for example include, but is not limited to, a vendor side, service provider side, a network operator side, a company side, an organization side, a university side, a lab facility side, a business enterprise side, ecommerce side, finance side, a defense facility side, or any other facility) that provides service.
[0051] However, for the purpose of description, the system (108) is described as an integral part of the remote server (104), without deviating from the scope of the present disclosure. Operational and construction features of the system (108) will be explained in detail with respect to the following figures.
[0052] FIG. 2 illustrates a block diagram of the system (108) provided for identifying a state of a subscriber, according to one or more embodiments of the present invention. As per the illustrated embodiment, the system (108) includes the one or more processors (202), the memory (204), an user interface (206), a display (208), an input device (210), and the database (214). Further the system (108) may comprise one or more processors (202). The one or more processors (202), hereinafter referred to as the processor (202) 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. As per the illustrated embodiment, the system (108) includes one processor. 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.
[0053] The information related to the request may be provided or stored in the memory (204) of the system (108). Among other capabilities, the processor (202) is configured to fetch and execute computer-readable instructions stored in the memory (204). The memory (204) may be configured to store one or more computer-readable instructions or routines in a non-transitory computer-readable storage medium, which may be fetched and executed to create or share data packets over a network service. The memory (204) may include any non-transitory storage device including, for example, volatile memory such as RAM, or non-volatile memory such as disk memory, EPROMs, FLASH memory, unalterable memory, and the like.
[0054] The memory (204) may comprise any non-transitory storage device including, for example, volatile memory such as Random-Access Memory (RAM), or non-volatile memory such as Electrically Erasable Programmable Read-only Memory (EPROM), flash memory, and the like. In an embodiment, the system (108) may include an interface(s). The interface(s) may comprise 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 interface(s) may facilitate communication for the system. The interface(s) may also provide a communication pathway for one or more components of the system. Examples of such components include, but are not limited to, processing unit/engine(s) and a database. The processing unit/engine(s) may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing engine(s).
[0055] The information related to the requests may further be configured to render on the user interface (206). The user interface (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 user interface (206) may be rendered on the display (208), implemented using Liquid Crystal Display (LCD) display technology, Organic Light-Emitting Diode (OLED) display technology, and/or other types of conventional display technology. The display (208) may be integrated within the system (108) or connected externally. Further the input device(s) (210) may include, but not limited to, keyboard, buttons, scroll wheels, cursors, touchscreen sensors, audio command interfaces, magnetic strip reader, optical scanner, etc.
[0056] The database (214) may be communicably connected to the processor (202) and the memory (204). The database (214) may be configured to store and retrieve the request pertaining to features, or services or workflow of the system (108), access rights, attributes, approved list, and authentication data provided by an administrator. Further the remote server (104) may allow the system (108) to update/create/delete one or more parameters of their information related to the request, which provides flexibility to roll out multiple variants of the request as per business needs. In another embodiment, the database (214) may be outside the system (108) and communicated through a wired medium and wireless medium.
[0057] 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 the 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 an electronic circuitry.
[0058] In order for the system (108) to identify the state of the subscriber, the processor (202) includes a configuration unit (216), an execution unit (218), an implementation unit (220), a determination engine (224), an identification unit (226), a logging unit (228) and a performing unit (230). The configuration unit (216), the execution unit (218), the implementation unit (220), the determination engine (224), the identification unit (226), the logging unit (228) and the performing unit (230) 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 the 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. 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 the electronic circuitry.
[0059] In order for the system (108) for identifying the state of the subscriber, the configuration unit (216), the execution unit (218), the implementation unit (220), the determination engine (224), the identification unit (226), the logging unit (228) and the performing unit (230) are communicably coupled to each other. In an example embodiment, the configuration unit (216) configures a state identifier pertaining to an API call. The state identifier refers to a unique value or indication that represents a current status or state of the subscriber within the system (108). The state could encompass a range of conditions or statuses that the subscriber may be in. In an example, the state identifier may have values like active, suspended, or expired. In another example, it may reflect the payment status of the subscriber, such as paid, overdue, or payment failed. In another example, it could denote the overall state of the subscriber’s account, such as verified, unverified, suspended, or closed. In another example, the state identifier includes the plurality of rules and the plurality of parameters. The plurality of rules and the plurality of parameters includes LastUpdatedOn (DateTime), IsActive (Boolean), IsDeleted (Boolean), and IsDraft (Boolean). In an embodiment, the configuration unit (216) performs at least one of: reads, appends, and adds the state identifier in run time via at least one of the user interface (206). This results in managing and tracking a subscriber states effectively in the system (108). In other words, managing the state identifier by reading, appending, and adding them helps in maintaining accurate and up-to-date subscriber information, supporting better management, automation, and overall system integrity in the system (108).
[0060] Based on configuring the state identifier of the respective API call, the execution unit (218) executes the API call to retrieve API call information pertaining to the UE (102) of the plurality of UEs. Each UE is associated with the subscriber. The API call refers to a request made to the service to retrieve or update information about the specific subscriber. This process is integral to managing and understanding the status or profile of the subscriber in the system (108) (e.g., telecommunication system, content service system, subscription-based platform or the like). The API call is executed in timely intervals, such as daily, weekly, and monthly. The API call information includes a type of API called, a type of subscriber called, and a number of the API call attempts. The type of the API call can be, for example, but not limited to a GET API call, a PUT API call, a POST API call, a PATCH API call, and a DELETE API call. The GET API call retrieves the subscriber information. The PUT API call updates the subscriber information. The POST API call triggers actions or verify subscriber state. The PATCH API call applies partial updates in the profile. The DELETE API call removes or deactivates the subscriber. The type of subscriber can be, for example, but not limited to an active subscriber, an inactive subscriber, a suspended subscriber or the like. In an API call, the state of the subscriber being "active" may be used to filter or target users who are currently participating in the service, allowing the system (108) to perform actions or deliver content only to those who are considered actively engaged. In an example, the inactive subscriber generally refers to a subscriber who is not currently engaged with the service or whose subscription status is not active. The suspended subscriber typically refers to the subscriber whose access to the service has been temporarily halted or restricted. This status indicates that while the subscriber’s account still exists and their subscription may be valid, they are currently unable to use the service or access its features due to specific reasons. The number of API call attempts refers to a count of times the API request is made to access, retrieve, or update information about the subscriber. This metric is important for understanding the reliability, efficiency, and potential issues related to API interactions.
[0061] Further, the implementation unit (220) implements the plurality of rules and the plurality of parameters of the state identifier to the retrieved API call information. Based on the implementation of the plurality of rules and parameters to the retrieved API call information, the determination unit (224) determines the state of the subscriber. The state of the subscriber is one of active, inactive, and temporarily inactive. The state of the subscriber is already explained above.
[0062] Further, the identification unit (226) identifies one or more inactive subscribers based on the determined state of each subscriber. The logging unit (228) logs the API call information in the database (214) upon execution of the API call to retrieve API call information pertaining to the UE (102). In an embodiment, the performing unit (230) deletes the one or more inactive subscribers. In another embodiment, the performing unit (230) disables the one or more inactive subscribers. In another embodiment, the performing unit (230) temporarily disables the one or more inactive subscribers upon identification of one or more inactive subscribers. The example for identifying the state of the subscriber is explained in FIG. 4.
[0063] FIG. 3 is an example schematic representation of the system (300) of FIG. 1 in which various entities operations are explained, according to various embodiments of the present system. It is to be noted that the embodiment with respect to FIG. 3 will be explained with respect to the first UE (102-1) and the system (108) for the purpose of description and illustration and should nowhere be construed as limited to the scope of the present disclosure.
[0064] As mentioned earlier, the first UE (102-1) includes one or more primary processors (305) communicably coupled to the one or more processors (202) of the system (108). 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) causes the UE (102-1) to transmit a state identifier pertaining to an Application Programming Interface (API) call to the one or more processers (202).
[0065] As per the illustrated embodiment, the system (108) includes the one or more processors (202), the memory (204), the user interface (206), the display (208), and the input device (210). The operations and functions of the one or more processors (202), the memory (204), the user interface (206), the display (208), and the input device (210) are already explained in FIG. 2. For the sake of brevity, we are not explaining the same operations (or repeated information) in the patent disclosure. Further, the processor (202) includes the configuration unit (216), the execution unit (218), the implementation unit (220), the determination engine (224), the identification unit (226), the logging unit (228) and the performing unit (230). The operations and functions of the configuration unit (216), the execution unit (218), the implementation unit (220), the determination engine (224), the identification unit (226), the logging unit (228) and the performing unit (230) are already explained in FIG. 2. For the sake of brevity, we are not explaining the same operations (or repeated information) in the patent disclosure.
[0066] FIG. 4 shows a block diagram of the system architecture (400) for identifying the state of the subscriber, in accordance with an exemplary embodiment of the present disclosure. The system architecture (400) comprises a common API gateway (422), an API consumer (402) communicably connected to the common API gateway (422) via the communication network (106), and an API services repository (424) communicably connected to the common API gateway (422) via the communication network (106). In an embodiment of the present invention, the common API gateway (422) may be a part of a subscriber system (not shown). The common API gateway (422) may be used to expose, secure, and manage backend applications, infrastructure and/or network systems as published APIs. The API consumer (420) may communicate with the common API gateway (422) for accessing the published APIs. In one embodiment of the present invention, the API services repository (424) may be a part of the common API gateway (422).
[0067] In an exemplary embodiment of the present disclosure, the common API gateway (422) comprises an API subscriber stale service and eviction rule configuration unit (412) and an API subscriber stale service and eviction rule engine (418) configured to run AI/ML based process for automatically managing the data of the subscriber (e.g., stale service API subscriber or the like). In an embodiment of the present disclosure, the AI/ML based process is implemented for automatically identifying and evicting the data of stale service API subscribers (for example) from the API services repository (424).
[0068] In an embodiment, the API subscriber stale service and eviction rule engine (418) may include one or more processor(s) (202).
[0069] In an embodiment of the present disclosure, the plurality of parameters are predefined and used in the API subscriber stale service and eviction rule engine (418) for flagging or marking the data of the API subscribers. The plurality of parameters comprises:
-LastUpdatedOn (DateTime),
-IsActive (Boolean),
-IsDeleted (Boolean), and
-IsDraft (Boolean)
[0070] For example, the parameter “LastUpdatedOn” tracks the last time (timestamp) when the API Subscribers was updated and is used to identify stale service API subscribers based on the timestamp. The parameter “IsActive” marks the API subscribers as active or inactive. The inactive API subscribers can be marked stale and may be unsubscribed at a later stage. The parameter “IsDeleted” marks the API subscribers for soft-disabling or subscription. The API subscribers can be effectively stale and these stale subscribers may be unsubscribed/ disable from using API services. Alternatively, these subscribers may be restored to get access from using API services based on the parameters. The parameter “IsDraft” marks draft scenarios such as having API subscribers not yet finalized. The “IsDraft” flag helps to identify API Subscribers to stale or unsubscribe the subscribers with drafts created a long time ago with no recent updates.
[0071] In one embodiment of the present invention, the plurality of parameters and rules in the API subscriber stale service and eviction rule engine (418) are run time configurable and can be added dynamically based on the requirements and conditions of the system / API subscribers.
[0072] In an example of the present invention, if the API subscriber is logged into the system architecture (400) and does not subscribe to any APIs that are being offered to the user. The system architecture (400) generates a list of all types of subscribers and marks different color codes or in a different status for stale subscribers. The same is provided to an internal database for processing and the system architecture (400) generates a report to the internal sub-system for further decision. The generated report can be accessed through a back-end module (not shown) of the system architecture (400) and can be downloaded using the user interface (UI) (206).
[0073] The common API gateway (422) is a provisioning server hosting an application logic for creating/modifying/displaying/deleting the subscription information, authentication information, and the device information. The common API gateway (422) supports NETCONF/ Secure Shell (SSH) and Restful/HTTP interfaces. The common API gateway supports (422) both client and server-side validation of input parameters for syntax and semantic checks. The common API gateway (422) provides lightweight CLI for all provisioning requirements. The common API gateway (422) may communicate with a CAPIF (408), an AMS module (not shown), an IAM unit (406) and an Edge Load Balancer (ELB) unit (404a, 404b). The CAPIF (408) is a complete 3GPP API framework that covers functionality related to on-board and off-board API consumers, register and release APIs. The AMS module outsources the task of providing ongoing support for apps to an external provider that specializes in this type of maintenance and monitoring. The IAM unit (406) is used for authentication and authorization of the API consumers (402). The ELB units (404a, 404b) automatically distributes incoming application traffic across multiple targets and virtual appliances in one or more availability zones.
[0074] In one embodiment of the present invention, the CAPIF (408) may automatically executes the API Subscriber Stale Service and Eviction Engine (418) as per a schedule based on stored instructions and program. Further, the CAPIF (408) may automatically execute the API Subscriber Stale Service and Eviction Engine (418) based on the plurality of parameters of the engine. These parameters may be managed and configured at startup time at the engine. In another embodiment of the present disclosure, these parameters may be managed and configured at runtime / dynamically based on a demand.
[0075] The CAPIF (408) may automatically execute the API Subscriber Stale Service and Eviction Engine (418) and use its AI/ML based processes to identify the stale service API subscribers based on the plurality of parameters marked in the engine and process to at least one of remove subscribed API User, disable already subscribed user, or soft disable a subscribed API user. The CAPIF (408) obtains easy and smooth API access through the API Subscriber Stale Service and Eviction Engine (418) and use its AI/ML based processes.
[0076] In one embodiment of the present invention, the system (400) may comprise an AI/ML (Artificial Intelligence (AI) and Machine Learning (ML)) module configured for automatically managing the data of stale service API subscribers. The AI/ML module may learn and manage the plurality of parameters of the API Subscriber Stale Service and Eviction Engine (418). The AI/ML module may automatically execute the API Subscriber Stale Service and Eviction Engine (418) and identify the stale service API subscribers. The AI/ML module may read all the information of the API subscriber and depends on the parameter configured in the rule configuration, automatically detect the subscribers that are being that are being to be flagged by our system and may generate API report. The report may be published by the AI/ML module. Further, the AI/ML module may automatically process to at least one of removing at least one subscribed API User, disabling already subscribed user, or soft disabling a subscribed API user.
[0077] In another embodiment of the present disclosure, the CAPIF (408) may restore the data of the API subscriber based on at least one requirement or the plurality of parameters. The system (400) may take all decisions automatically on runtime by using the API Subscriber Stale Service and Eviction Rule Engine (418). In another embodiment, the AI/ML module may restore the data of the API subscriber based on at least one requirement or the plurality of parameters.
[0078] In one embodiment of the present invention, the common API gateway (422) may include or comprise, 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 defense facility, or any other facility that provides content.
[0079] An API orchestration configuration unit (410), an API synchronization call unit (414), an API response collection unit (416) and an API asynchronization call unit (420) are included in the API gateway (422).
[0080] The present system (400) may further provides a plurality of features including:
1) Configurable API Orchestration: Configurable API Orchestration allows multiple ways of routing the East Bound API calls to multiple Westbound API calls using the API orchestration configuration unit (410).
2) Dynamic transformation and manipulation of API Data: This feature enables the capability of transforming request as per destination application and also transform response as required by a sender
a) Body to Body transformation and Manipulation,
b) Query param transformation and Manipulation, and
c) Header transformation and Manipulation
3) Template based API provisioning: Template based Service API provisioning feature allows us to create and manage APIs on-demand. It is done using an API gateway. It improves the agility, flexibility, and cost-efficiency of API development and management process as API is integrated dynamically.
[0081] FIG. 5 shows a flow chart (500) for a method for identifying the state of the subscriber, in accordance with the present disclosure. The method comprises a plurality of steps and may be implemented by the system (108). At step 502, the method includes initiating the API call when the system (108) is initially booted up all the configuration files. The configuration files may be read, appended, and added in run time via the CLI and updated via the CLI. At step 504, the method includes running the API subscriber stale service and eviction rule by using the API subscriber state service and eviction rule engine (418). At step 506, the method includes initiating the API call by the subscriber. Further, the method includes reading all the data and logging all the information of the API call information. The API call information includes the type of API called, the type of API subscriber called, and the number of times called. All the logged information is stored in the database (214). Once the configuration file is read by the system (108), the system (108) may execute a decision making part for getting and identifying the API subscriber information over the time-to-time intervals, for example, daily, weekly or monthly.
[0082] At step 508, the method may comprise implementing the API subscriber stale service and eviction rule to detect the subscribers based on the plurality of parameters. The API subscriber stale service and eviction rule can be used for flagging the subscribers who are not using the APIs or not renewing their subscription. At step 510, the method may comprise collecting the API response to prepare the final response configuration to the API provider or the API customer (402). At step 512, the method includes preparing the final response configuration and the sending the final response configuration to the API consumer (402).
[0083] FIG. 6 is an exemplary flow diagram (600) illustrating the method for identifying the state of the subscriber, according to various embodiments of the present disclosure.
[0084] At step 602, the method includes configuring the state identifier pertaining to the API call. In an embodiment, the method allows the configuration unit (216) to configure the state identifier pertaining to the API call. The state identifier refers to the unique value or the indication that represents the current status or state of the subscriber within the system (108). The state could encompass the range of conditions or statuses that the subscriber may be in. At step 604, the method includes executing the API call to retrieve API call information pertaining to the UE (102) of the plurality of UEs based on configuring the state identifier of the respective API. Each UE is associated with the subscriber. In an embodiment, the method allows execution unit (218) to execute the API call to retrieve API call information pertaining to the UE (102) of the plurality of UEs based on configuring the state identifier of the respective API. The API call refers to the request made to the service to retrieve or update information about the specific subscriber.
[0085] At step 606, the method includes implementing the plurality of rules and the plurality of parameters associated with the state identifier to the retrieved API call information. In an embodiment, the method allows the implementation unit (220) to implement the plurality of rules and the plurality of parameters associated with the state identifier to the retrieved API call information. At step 608, the method includes determining the state of the subscriber based on the implementation of the plurality of rules and the plurality of parameters to the retrieved API call information. In an embodiment, the method allows determination unit (224) to determine the state of the subscriber based on the implementation of the plurality of rules and the plurality of parameters to the retrieved API call information. At step 610, the method includes identifying the one or more inactive subscribers based on the determined state of the subscriber. In an embodiment, the method allows identification unit (226) to identify the one or more inactive subscribers based on the determined state of each subscriber.
[0086] Technical advantages of the invention: The method can be used to automatically identify and evict the data of stale service API subscribers in an effective manner, so as to save the memory space in the database (214). The present invention provides a solution for detecting inactive API subscribers and removing them from the database to minimize the memory consumption and provide accurate subscription for accessing performance of an API. The present method allows CAPIF to automatically executes an AI/ML based process installed on the API gateway on a regular interval to identify stale service API subscribers/users who are not using the API and automatically unsubscribe the users from the API. The AI/ML process automatically detects the inactive status of the API Subscriber, Last used status, or deletion status and accordingly the CAPIF updates the subscriber information in the system.
[0087] A person of ordinary skill in the art will readily ascertain that the illustrated embodiments and steps in description and drawings (FIGS. 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.
[0088] 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
[0089] Environment - 100
[0090] UEs– 102, 102-1-102-n
[0091] Server - 104
[0092] Communication network – 106
[0093] System – 108
[0094] Processor – 202
[0095] Memory – 204
[0096] User Interface – 206
[0097] Display – 208
[0098] Input device – 210
[0099] Database – 214
[00100] Configuration unit– 216
[00101] Execution unit – 218
[00102] Implementation unit – 220
[00103] Determination engine – 224
[00104] Identification unit – 226
[00105] Logging unit – 228
[00106] Performing unit -230
[00107] System - 300
[00108] Primary processors -305
[00109] Memory– 310
[00110] Kernel– 315
[00111] Example system - 400
[00112] API consumer – 402
[00113] ELB unit - 404a, 404b
[00114] IAM unit – 406
[00115] CAPIF – 408
[00116] API orchestration configuration unit – 410
[00117] API subscriber state service and eviction rule configuration unit – 412
[00118] API synchronization call unit – 414
[00119] API response collection unit – 416
[00120] API subscriber state service and eviction rule engine – 418
[00121] API asynchronization call unit – 420
[00122] API gateway – 422
[00123] API service repository – 424

,CLAIMS:CLAIMS:
We Claim
1. A method of identifying a state of a subscriber, the method comprising the steps of:
configuring, by one or more processors (202), a state identifier pertaining to an Application Programming Interface (API) call;
executing, by the one or more processors (202), the API call to retrieve API call information pertaining to each User Equipment (UE) of a plurality of UEs based on configuring the state identifier of the respective API call, wherein each UE is associated with a subscriber;
implementing, by the one or more processors (202), a plurality of rules and a plurality of parameters associated with the state identifier to the retrieved API call information;
determining, by the one or more processors (202), a state of the subscriber based on the implementation of the plurality of rules and the plurality of parameters to the retrieved API call information; and
identifying, by the one or more processors (202), one or more inactive subscribers based on the determined state of the subscriber.

2. The method as claimed in claim 1, wherein the state identifier includes the plurality of rules and parameters, wherein configuring the state identifier includes at least one of: reading, appending, and adding the state identifier in run time via at least one of a Command Line Interface (CLI).

3. The method as claimed in claim 1, wherein upon execution, the method comprises the step of logging, by the one or more processors, the API call information in a database,

4. The method as claimed in claim 1, wherein the API call information comprises at least one of: a type of API called, a type of subscriber called, and a number of the API call attempts.

5. The method as claimed in claim 1, wherein upon configuration, the API call is executed in timely intervals.

6. The method as claimed in claim 1, wherein the state of the subscriber is one of active, in active, and temporarily inactive.

7. The method as claimed in claim 1, the method comprises the step of performing, by the one or more processors (202), a process to one of deleting the one or more inactive subscribers, disabling the one or more inactive subscribers, temporarily disabling the one or more inactive subscribers upon identification of one or more inactive subscribers.

8. The method as claimed in claim 1, wherein the state identifier refers to an indication that represents a current status or state of the subscriber within a system (108).

9. A system (108) for identifying a state of a subscriber, the system (108) comprising:
a configuration unit (216) configured to configure, a state identifier pertaining to an Application Programming Interface (API) call;
an execution unit (218) configured to execute, the API call to retrieve API call information pertaining to a User Equipment (UE) (102) of a plurality of UEs based on configuring the state identifier of the respective API call, wherein each UE is associated with a subscriber;
an implementation unit (220) configured to implement, a plurality of rules and a plurality of parameters associated with the state identifier to the retrieved API call information;
a determination unit (224) configured to determine, a state of the subscriber based on the implementation of the plurality of rules and the plurality of parameters to the retrieved API call information; and
an identification unit configured to identify, one or more inactive subscribers based on the determined state of the subscriber.

10. The system (108) as claimed in claim 9, wherein the state identifier includes the plurality of rules and the plurality of parameters, wherein configuring the state identifier includes at least one of: reading, appending, and adding the state identifier in run time via at least one of a Command Line Interface (CLI).

11. The system (108) as claimed in claim 9, wherein, the system comprises a logging unit configured to log, the API call information in a database upon execution of the API call to retrieve API call information pertaining to the UE.

12. The system (108) as claimed in claim 9, wherein the API call information comprises at least one of: a type of API called, a type of subscriber called, and a number of the API call attempts.

13. The system (108) as claimed as claim 9, wherein the API call is executed in timely intervals,.

14. The system (108) as claimed in claim 9, wherein the state of the subscriber is one of active, in active, and temporarily inactive.

15. The system (108) as claimed in claim 9, wherein the system comprises a performing unit configured to perform, a process to one of delete the one or more inactive subscribers, disable the one or more inactive subscribers, temporarily disable the one or more inactive subscribers upon identification of one or more inactive subscribers.

16. The system (108) as claimed in claim 9, wherein the state identifier refers to an indication that represents a current status or state of the subscriber within the system.

17. A User Equipment (UE) (102-1), comprising:
one or more primary processors communicatively coupled to one or more processors of a system, the one or more primary processors coupled with a memory, wherein said memory stores instructions which when executed by the one or more primary processors causes the UE to:
transmit a state identifier pertaining to an Application Programming Interface (API) call to the one or more processers;
wherein the one or more processors are configured to perform the steps as claimed in claim 1.