Patent Grant
11900179
Aspects of the present disclosure are directed to techniques for detecting abnormal application programming interface (API) sessions. More particularly, the present disclosure is directed to techniques for detecting an abnormal sequence of API requests included in an API session.
Application programming interfaces (APIs) are generally used to expose various routines and methods to software developers for use in obtaining and modifying data using features of a software application. APIs may be accessible programmatically (e.g., as function calls in an application or function library) or via a web-service (e.g., Web Services Description Language (WSDL)) for web-based applications. For example, developers may use APIs to build web applications or mobile applications that include functionality and user interface components invoked through the API.
Because APIs are so commonplace, bad actors (e.g., hackers) may perform different attacks through APIs to gain access to an organizations' infrastructure. To that end, API security models have been developed to automatically detect and prevent certain types of API attacks implemented by bad actors. For instance, conventional API security models may detect API attacks in which the bad actor sends an abnormal volume of API requests. However, conventional API security models may not detect every type of API attack. For instance, API attacks in the form of an abnormal sequence of API requests associated with an API session may go undetected by conventional API security models.
Accordingly, there is a need for improved techniques for automatically detecting and preventing API attacks.
In one aspect, a computer-implemented method is provided. The method includes receiving training data including a plurality of API requests from a plurality of client devices. The method includes generating a plurality of permissible API sessions based on the training data. The plurality of permissible API sessions is associated with a corresponding client device of the plurality of client devices and includes a sequence of API requests originating from the corresponding client device. The method includes applying a sequence embedding technique to the plurality of permissible API sessions to generate a plurality of embeddings. Each of the embeddings is representative of a corresponding permissible API session of the plurality of permissible API sessions. The method includes applying a dimensionality reduction technique to the plurality of embeddings to generate a plurality of compact embeddings. The method includes applying a clustering technique to the plurality of compact embeddings to determine a plurality of different clusters of the compact embeddings. The method includes generating a plurality of patterns based on the plurality of different clusters. Each of the plurality of patterns is descriptive of permissible API sessions associated with a corresponding cluster of the plurality of different clusters.
In another aspect, a computer-implemented method is provided. The method includes receiving data including a plurality of API requests from a plurality of client devices. The method includes generating a plurality of API sessions based on the data. Each of the API sessions is associated with a corresponding client device of the plurality of client devices and includes a sequence of API requests originating from the corresponding client device. The method includes comparing each of the plurality of API sessions to one or more of a plurality of different patterns indicative of permissible API sessions determined based on training data. The method includes determining one or more API sessions of the plurality of API sessions generated based on the data are abnormal based, at least in part, on the comparing. The method includes performing one or more actions based on determining the one or more API sessions are abnormal.
In yet another aspect, a computing system is provided. The computing system includes one or more processors and one or more memory configured to store computer executable instructions that, when executed by the one or more processors, cause the one or more processors to: receive training data including a plurality of API requests from a plurality of client devices; generate a plurality of permissible API sessions based on the training data, with each of the permissible API sessions being associated with a corresponding client device of the plurality of client devices and including a sequence of API requests originating from the corresponding client device; apply a sequence embedding technique to the plurality of permissible API sessions to generate a plurality of embeddings, with each of the embeddings being representative of a corresponding permissible API session of the plurality of permissible API sessions; apply a dimensionality reduction technique to the plurality of embeddings to generate a plurality of compact embeddings; apply a clustering technique to the plurality of compact embeddings to determine a plurality of different clusters of the compact embeddings; and generate a plurality of patterns based on the plurality of different clusters, with each of the plurality of patterns being descriptive of permissible API sessions associated with a corresponding cluster of the plurality of different clusters.
The following description and the related drawings set forth in detail certain illustrative features of one or more embodiments.
The appended figures depict certain aspects of the one or more embodiments and are therefore not to be considered limiting of the scope of this disclosure.
To facilitate understanding, identical reference numerals have been used, where possible, to designate identical elements that are common to the drawings. It is contemplated that elements and features of one embodiment may be beneficially incorporated in other embodiments without further recitation.
Aspects of the present disclosure provide apparatuses, methods, computing systems, and computer readable medium for detecting abnormal sequences of API requests.
Existing API security models may automatically detect and prevent certain types of API attacks by bad actors (e.g., hackers). For instance, existing API security models may detect API attacks in which a bad actor sends an abnormal volume of API requests. However, existing API security models cannot automatically detect every type of API attack. For instance, existing API security models cannot detect API attacks in the form of an abnormal sequence of API requests. Thus, organizations utilizing existing API security models to protect their infrastructure are vulnerable to these types of API attacks (e.g., abnormal sequences of API requests).
Example aspects of the present disclosure are directed to API security models for automatically detecting and preventing API attacks in the form of abnormal sequences of API requests. An API security model according to the present disclosure may be operable in a training phase and an inference phase. When the API security model is operating in the training phase, the API security model may obtain training data that includes a plurality of API requests from a plurality of different client devices. The API security model may generate a plurality of permissible API sessions based on the training data. Each of the plurality of permissible API sessions may include a sequence of API requests originating from a corresponding client device of the plurality of client devices. It should be understood that the sequence of API requests refers to a sequence of API requests made to various endpoints (e.g., API services). It should also be understood that the number of API requests included in the sequence of API requests may range from 3 API requests to 1,000 or more API requests.
Given the large volume of permissible API sessions, the API security model may be configured to apply a sequence embedding technique to the plurality of permissible API sessions to embed the plurality of permissible API sessions in a multi-dimensional Euclidian space. For instance, in some embodiments, the sequence embedding technique used to generate the embeddings (that is, a vector representation of the sequence of API requests in the Euclidian space) may be a sequence graph transformation technique. This particular technique generates the embeddings in such a way so as to preserve similarity between API sessions that are similar to one another. More specifically, the embeddings generated for similar API sessions are close to one another in the multi-dimensional Euclidian space.
As described in more detail below with respect to
The API security model may be configured to apply a clustering technique to the plurality of compact embeddings to determine a plurality of different clusters of the compact embeddings. For instance, the API security model may determine a first cluster that includes a first grouping of the compact embeddings, a second cluster that includes a second grouping of the compact embeddings, and a third cluster that includes a third grouping of the compact embeddings. The API security model may be configured to generate a plurality of expressions, with each of the expressions being descriptive of permissible API sessions (e.g., the compact embeddings thereof) associated with a corresponding cluster of the plurality of different clusters.
After determining the plurality of patterns, the API security model may operate in the inference phase to detect abnormal API sessions. In some embodiments, the API security model may detect that the sequence of API requests associated with an API session generated while the API security model is operating in the inference phase is dissimilar from each of the plurality of patterns representative of permissible API sessions. For instance, the API security model may compare the API session with a first pattern of the plurality of patterns that is closest (e.g., in Euclidian space) to the API session. If the distance between the API session and the first pattern exceeds a threshold distance, the API security model may determine the API session is abnormal and, in some embodiments, may generate a notification indicative of the API session being determined to be abnormal. Remedial action may be taken based on such a determination and/or notification, such as preventing the API session from continuing, blocking access to one or more resources by one or more devices, components, and/or users associated with the API session, and/or the like.
Example aspects of the present disclosure provide numerous technical effects and benefits. For instance, API security models according to the present disclosure provide improved automated security against API attacks in the form of abnormal sequences of API requests to which existing API security models are vulnerable. Furthermore, by utilizing a sequence embedding technique as well as dimensionality reduction techniques, API security models according to the present disclosure may allow API sessions to be compared in a more computationally efficient manner, thereby improving the efficiency of involved processes and improving the functioning of involved computing devices.
Each of the plurality of client devices 120 may communicate a plurality of API requests 140 to the server 110. For instance, a first client device of the client devices 120 may communicate a first sequence of API requests to the server 110. Likewise, a second client device of the client devices 120 may communicate a second sequence of API requests to the server 110.
It should be understood that the first sequence of API requests the server 110 receives from the first client device may be different from the second sequence of API requests the server 110 receives from the second client device. For example, the first sequence of API requests received from the first client device may be “ABBBBC” and the second sequence of API requests received from the second client device may be “ABCBCBBC” in which “A” represents an API request for a first API service (e.g., endpoint) of a plurality of different API services 112, “B” represents an API request for a second API service (e.g., endpoint) of the plurality of different API services 112, and “C” represents an API request for a third API service (e.g., endpoint) of the plurality of different API services 112. It should also be understood that the sequence of API requests may include any suitable number of API requests. For instance, in some embodiments, the sequence of API requests 140 may include 100 or more API requests.
In some embodiments, the server 110 may include an API gateway 114. The API gateway 114 may be configured to receive the sequence of API requests from each of the plurality of client devices 120. For instance, the API gateway 114 may receive the first sequence of API requests (e.g., “ABBBBC”) from the first client device and the second sequence of API requests (e.g., “ABCBCBB”) from the second client device.
The API gateway 114 may be configured to communicate each of the plurality of API requests within the sequence of API requests to a corresponding API service of the API services 112. For example, the API gateway 114 may communicate API request “A” within the sequence of API requests to a first API service of the API services 112. Likewise, the API gateway 114 may communicate API request “B” within the sequence of API requests to a second API of the API services 112.
The API gateway 114 may be configured to receive responses from the API services 112. For instance, a first API service may generate a response to receiving API request “A” from the first client device. The API gateway 114 may receive the response and communicate the response to the first client device. In this manner, responses to API requests may be communicated from an API service to a corresponding client device.
In some embodiments, the server 110 may include an API security model 150. As will be discussed below in more detail with reference to
Although the API security model 150 is depicted as being on the server 110, it should be appreciated that, in alternative embodiments, functions associated with the API security model 150 may be distributed across multiple devices. For instance, in some embodiments, certain functions (e.g., functions associated with inference phase of
The computing environment 100 may include a database 160 communicatively coupled to the server 110 via the network(s) 130. In this manner, the server 110, specifically the API security model 150 thereof, may access (e.g., read, write) the database 160. For instance, the plurality of patterns of permissible API sessions determined by the API security model 150 during the training phase may be stored on the database 160. Furthermore, the plurality of patterns of permissible API sessions may be accessed by the API security model 150 during the inference phase. In this manner, the API security model 150 may compare API sessions generated during the inference phase to the plurality of patterns to determine whether the API sessions are abnormal.
The data processing module 210 may include one or more submodules. For instance, in some embodiments, the one or more submodules may include a session generator 212. The session generator 212 may be configured to generate a plurality of permissible API sessions based on the training data 202. In some embodiments, the session generator 212 may group the API requests by client device. For instance, the session generator 212 may generate a first permissible API session for all API requests included in the training data 202 and originating from a first client device of the plurality of client devices. Additionally, the session generator 212 may generate a second API session for all API requests included in the training data 202 and originating from a second client device of the plurality of client devices. It should be understood that the session generator 212 may be configured to generate the plurality of permissible API sessions based on any suitable attribute (e.g., similar user, similar network location, and similar time) of the training data 202 and, more specifically, the sequences of API requests included therein.
In some embodiments, the one or more submodules of the data processing module 210 may include a normalization module 214. The normalization module 214 may be configured to process the permissible API sessions generated by the session generator 212. For instance, in some embodiments, the normalization module 214 may be configured to determine whether a sequence of API requests included in each of the permissible API sessions includes greater than a threshold number of consecutive API requests for a particular API service. For example, if the sequence of API requests for one of the permissible API sessions is “ABBBBBC”, the normalization module 314 may determine whether the consecutive API requests for API service “B” exceeds a threshold number. Furthermore, if the normalization module 214 determines the number of consecutive API requests for API service “B”, the normalization module 214 may, in some embodiments, remove one or more instances of the API request for API service “B” until the API session includes the threshold number of consecutive API requests for API service “B”.
In some embodiments, the one or more submodules of the data processing module 210 may include a cleanup module 216. In some embodiments, the cleanup module 216 may be configured to process each of the permissible API sessions to determine whether the sequence of API requests included in each of the permissible API sessions includes a threshold number (e.g., at least 3) of API requests. Furthermore, if the cleanup module 216 determines the sequence of API requests included in one or more of the API session is less than the threshold number, the cleanup module 216 may be configured to remove (e.g., delete) the one or more permissible API sessions from the plurality of permissible API sessions. Alternatively, or additionally, the cleanup module 216 may be configured to determine whether the sequence of API requests for one or more of the permissible API session is suspicious. For instance, if the sequence of API requests is similar or identical to a sequence of API requests that is known to be associated with an API attack (e.g., based on historical data associated with historical API attacks and/or user input indicating sequences of API requests that are associated with API attacks), the cleanup module 216 may be configured to remove (e.g., delete) the permissible API session from the plurality of permissible API sessions.
The API security model 150 may include an embedding module 220. The embedding module 220 may receive the plurality of permissible API sessions (e.g., first API session, second API session . . . nth API session) from the data processing module 210. The embedding module 220 may be configured to apply a sequence embedding technique to the plurality of permissible API sessions to generate a plurality of embeddings (e.g., first embedding, second embedding . . . nth embedding). Each of the plurality of embeddings corresponds to a different permissible API session of the plurality of permissible API sessions received from the data processing module 210. Furthermore, in some embodiments, each of the embeddings may be a vector representation of the corresponding permissible API session. Still further, in some embodiments, the vector representation may include 100 or more dimensions. More specifically, in some embodiments, the vector representation may include 1,000 or more dimensions.
In some embodiments, the sequence embedding technique may include a sequence graph transformation. The sequence graph transformation technique may generate the plurality of embeddings in a way that preserves similarity between permissible API sessions that are similar to one another. For instance, embeddings for permissible API sessions that are similar to one another will be vectors that are close to one another in the multi-dimensional Euclidian space.
The API security model 150 may include a dimensionality reduction module 230. The dimensionality reduction module 230 may receive the plurality of embeddings (e.g., first embedding, second embedding . . . nth embedding) from the embedding module 220. The dimensionality reduction module 230 may be configured to apply a dimensionality reduction technique to the plurality of embeddings to generate a plurality of compact embeddings (e.g., first compact embedding, second compact embedding . . . nth compact embedding). For instance, in some embodiments, the dimensionality reduction technique may include a principal component analysis (PCA).
It should be appreciated that the dimensionality reduction module 230 may, in some embodiments, be configured to reduce the number of dimensions in each of the plurality of embeddings by a threshold number. For instance, in some embodiments, the dimensionality reduction module 230 may be configured to reduce the number of dimensions from about 1,000 dimension to about 30 dimensions (these numbers are included as examples, and other numbers are possible). As used herein, the term “about” refers to a range of values within 20 percent of the stated numerical value.
The API security model 150 may include a clustering module 240. The clustering module 240 may be configured to receive the plurality of compact embeddings (e.g., first compact embedding, second compact embedding . . . nth compact embedding) from the dimensionality reduction module 230. The clustering module 240 may be configured to apply a clustering technique to the plurality of compact embeddings. As shown, the clustering module 240 may output cluster data 242 that includes a plurality of different groups or clusters of the compact embeddings. For instance, in some embodiments, the plurality of different clusters of the compact embeddings may include a first cluster that includes a first grouping of the compact embeddings that are similar to one another (e.g., close to one another in Euclidian space), a second cluster that includes a second grouping of the compact embeddings that are similar to one another, and a third cluster that includes a third group of the compact embeddings that are similar to one another. It should be appreciated that the different groups (e.g., first, second, third) of compact embeddings that make up each cluster are representative of permissible API sessions that are therefore not abnormal and not indicative of a potential API attack.
The API security model 150 may include a pattern extraction module 250. The pattern extraction module 250 may be configured to receive the cluster data 242 (e.g., groups of clusters) from the clustering module 240. The pattern extraction module 250 may be configured to generate a plurality of patterns (e.g., first pattern, second pattern . . . nth pattern) based on the cluster data 242. Each of the patterns may be descriptive of the permissible API sessions associated with a corresponding cluster of the cluster data 242. For instance, a first pattern of the plurality of patterns may be descriptive of permissible API sessions (e.g., first grouping of compact embeddings) associated with the first cluster of the cluster data 242. Additionally, a second pattern of the plurality of patterns may be descriptive of permissible API sessions (e.g., second grouping of compact embeddings) associated with the second cluster of the cluster data 242. Finally, a third pattern may be descriptive of permissible API sessions (e.g., third grouping of compact embeddings) associated with the third cluster of the cluster data 242.
In some embodiments, each of the plurality of patterns may include a regular expression that is descriptive of the permissible API sessions associated with a corresponding cluster of the plurality of clusters. The regular expression may include one or more operators, such as one or more of an OR operator, a concatenation operator (CONCAT), recursive operator (RECUR), or an optional operator (OPTIONAL). The regular expression may also include a plurality of endpoints (e.g., API service), with each of the endpoints being associated with a corresponding API request included in the sequence of API requests associated with the corresponding cluster.
As an example, a first regular expression for a first cluster of the cluster data 242 may be A→B→C. It should be appreciated that the regular expression indicates that permissible API sessions associated with the first cluster of the cluster data 242 includes an API request for “A” followed by an API request for “B” followed by a an API request for “C”. As another example, a second regular expression for a second cluster of the cluster data 242 may be A→B*→D?→(D|A). As yet another example, a third regular expression for a third cluster of the cluster data 242 may be B→A→(C|D|E)→B*→D?. For each of these examples, it should be appreciated that the letters “A”, “B”, “C”, “D”, and “E” refer to endpoints (that is, particular API services) associated with one or more API requests included in the permissible API sessions. Additionally, other symbols (e.g., “?”, “*”) refer to the one or more operators, such as an or operator, a recursive operator, a concatenation operator, or an optional operator.
In some embodiments, the API security model 150 may, as discussed above with reference to
It should be appreciated that one or more components of the API security model 150 may be implemented using a machine learning model. For example, in some embodiments, the embedding module 220 may be implemented by a machine learning model. More specifically, the embedding module 220 may be implemented in an embedding layer of the machine learning model. Alternatively, or additionally, the dimensionality reduction module 230 may be implemented by a machine learning model.
The data processing module 210 may be configured to generate a plurality API sessions (e.g, first API session, second API session . . . nth API session) based on the data 302. It should be appreciated that the data processing module 210 may process the data 302 in the same manner as the data processing module 210 processes the training data 202 as discussed above with reference to
The API security model 150 may include an anomaly detection module 304. The anomaly detection module 304 may be configured to receive the plurality of API sessions from the data processing module 310. Furthermore, the anomaly detection module 304 may be configured to access the database 160 to obtain the plurality of patterns of permissible API sessions 306 that are stored thereon. It should be appreciated that the plurality of patterns of permissible API sessions 306 may be the plurality of patterns output by the pattern extraction module 250 discussed above with reference to the API security model 150 of
The anomaly detection module 304 may be configured to compare each of the plurality of API sessions generated based on the data 302 to each of the plurality of patterns of permissible API sessions 306. If the anomaly detection module 304 determines a distance between one or more of the plurality of API sessions and a first pattern of the plurality of patterns of permissible API sessions 306 that is closest to the one or more API sessions exceeds a threshold distance, the anomaly detection module 304 may be configured to determine the one or more API sessions are abnormal and may, in some embodiments, generate a notification 308 indicating the same (that is, that the one or more API sessions are abnormal).
At (402), the method 400 may include receiving training data that includes a plurality of API requests from a plurality of client devices. For example, the training data may include multiple API requests originating from a first client device and multiple API requests originating from a second client device.
At (404), the method 400 may include generating a plurality of permissible API sessions based on the training data. In some embodiments, each of the permissible API sessions may be associated with a corresponding client device of the plurality of client devices. Furthermore, each of the permissible API sessions may include a sequence of API requests originating from the corresponding client device.
At (406), the method 400 may include applying a sequence embedding technique to the plurality of API sessions to generate a plurality of embeddings. For instance, in some embodiments, the sequence embedding technique may include a sequence graph transformation technique.
At (408), the method 400 may include applying a dimensionality reduction technique to the plurality of embeddings to generate a plurality of compact embeddings. For instance, in some embodiments, the dimensionality reduction technique may include a principal component analysis technique that reduces the number of dimensions in the plurality of embeddings generated at (406) by a predetermined amount to generate the plurality of compact embeddings. In some embodiments, the predetermined amount may be greater than 100. In alternative embodiments, the predetermined amount may be greater than 1,000.
At (410), the method 400 may include applying a clustering technique to the plurality of compact embeddings to determine a plurality of different clusters of the compact embeddings. It should be understood that performing the dimensionality reduction technique at (408) improves the results (e.g., clusters) of the clustering technique that is applied to the compact embeddings at (410). Stated another way, the different groups or clusters that are determined by the clustering technique would not be as well defined if the clustering technique were applied to the plurality of embeddings at (406) due, at least in part, to the fact that the number of dimensions of each of the plurality of embeddings is significantly greater (e.g., at least 10 times) than the number of dimensions included in each of the compact embeddings.
At (412), the method 400 may include generating a plurality of patterns based on the plurality of different clusters determined at (410). Each of the patterns generated at (412) may be descriptive of permissible API sessions associated with a corresponding cluster of the plurality of different clusters. For instance, each of the patterns may include one or more operators (e.g., OR, CONCAT, RECUR, OPTIONAL) and each of the endpoints (e.g., API services) associated with the sequence of API requests that make up the permissible API sessions associated with the corresponding cluster.
In some embodiments, generating the plurality of patterns at (412) may include applying a greedy algorithm to each of the plurality of different clusters to facilitate generating the corresponding pattern of permissible API sessions. It should be understood that any suitable type of greedy algorithm may be used to facilitate generating the patterns. It should also be understood that the greedy algorithm may allow for the patterns to be determined in a more computationally efficient manner.
Some embodiments further include preprocessing the plurality of API sessions prior to applying the sequence embedding algorithm to generate the plurality of embeddings. For instance, in some embodiments, the method 400 may include determining whether each of the permissible API sessions generated at (404) include a threshold number (e.g., at least 3) of API requests. Alternatively, or additionally, the method 400 may include determining whether the sequence of API requests for one or more of the permissible API sessions include more than a threshold number of consecutive API requests for an API service. Additionally, in response to determining the sequence of API requests for the one or more API sessions include more than the threshold number of consecutive API requests for the API service, the method 400 may include removing one or more instances of the consecutive API requests until the sequence of API requests includes the threshold number of consecutive API requests for the API service.
At (502), the method 500 may include receiving data that includes a plurality of API requests from a plurality of client devices. For example, the training data may include multiple API requests originating from a first client device and multiple API requests originating from a second client device.
At (504), the method 500 may include generating a plurality of API sessions based on the data received at (502). In some embodiments, each of the API sessions may be associated with a corresponding client device of the plurality of client devices. Furthermore, each of the API sessions may include a sequence of API requests originating from the corresponding client device.
At (506), the method 500 may include comparing each of the plurality of API sessions to one or more of a plurality of different patterns descriptive of permissible API sessions. Each of the patterns may be descriptive of permissible API sessions included in a corresponding cluster of a plurality of clusters determined by a model based, at least in part, on training data received by the model and including a plurality of API requests.
At (508), the method may include determining one or more of the API sessions are abnormal based on the comparison at (506). For instance, in some embodiments, determining one or more API sessions of the plurality of API sessions are abnormal may include determining a distance (e.g., Euclidian distance) between the one or more API sessions and a first patter of the plurality of patterns of permissible API sessions that is closest to the one or more API sessions is greater than a threshold distance.
At (510), the method 500 may include performing one or more actions based, at least in part, on determining the one or more API sessions are abnormal at (508). For instance, in some embodiments, the one or more actions may include generating a notification indicative of the one or more API sessions being abnormal. In some embodiments, the notification may be displayed on a display device for viewing by a user. In this manner, the user can determine whether the one or more API sessions are, in fact, abnormal. Alternatively, or additionally, the one or more actions may include updating a database (e.g., database 260) to include the one or more API sessions determined to be abnormal. In this manner, a record (e.g., a list) of abnormal API sessions may be maintained.
Some embodiments further include preprocessing the plurality of API sessions prior to applying the sequence embedding algorithm to generate the plurality of embeddings. For instance, in some embodiments, the method 500 may include determining whether each of the API sessions generated at (504) include a threshold number (e.g., at least 3) of API requests. Alternatively, or additionally, the method 400 may include determining whether the sequence of API requests for one or more of the API sessions include more than a threshold number of consecutive API requests for an API service. Additionally, in response to determining the sequence of API requests for the one or more API sessions include more than the threshold number of consecutive API requests for the API service, the method 500 may include removing one or more instances of the consecutive API requests until the sequence of API requests for the one or more API sessions includes the threshold number of consecutive API requests for the API service.
The computing system 600 includes a central processing unit (CPU) 602, one or more I/O device interfaces 604 that may allow for the connection of various I/O device interfaces 604 (e.g., keyboards, displays, mouse devices, pen input, etc.) to the computing system 600, a network interface 606, a memory 608, and an interconnect 612. It is contemplated that one or more components of the computing system 600 may be located remotely and accessed via a network 610 (e.g., which may be the network 130 of
The CPU 602 may retrieve and execute programming instructions stored in the memory 608. Similarly, the CPU 602 may retrieve and store application data residing in the memory 608. The interconnect 612 transmits programming instructions and application data, among the CPU 602, the I/O device interfaces 604, the network interface 606, the memory 608. The CPU 602 is included to be representative of a single CPU, multiple CPUs, a single CPU having multiple processing cores, and other arrangements.
Additionally, the memory 608 is included to be representative of a random access memory or the like. In some embodiments, the memory 608 may include a disk drive, solid state drive, or a collection of storage devices distributed across multiple storage systems. Although shown as a single unit, the memory 608 may be a combination of fixed and/or removable storage devices, such as fixed disc drives, removable memory cards or optical storage, network attached storage (NAS), or a storage area-network (SAN).
As shown, the memory 608 may, in some embodiments, include the API security model 150 discussed above with reference to
The computing system 650 includes a central processing unit (CPU) 652, one or more I/O device interfaces 654 that may allow for the connection of various I/O device interfaces 654 (e.g., keyboards, displays, mouse devices, pen input, etc.) to the computing system 650, a network interface 656, a memory 658, and an interconnect 660. It is contemplated that one or more components of the computing system 650 may be located remotely and accessed via a network 662 (e.g., which may be the network 130 of
The CPU 652 may retrieve and execute programming instructions stored in the memory 658. Similarly, the CPU 562 may retrieve and store application data residing in the memory 658. The interconnect 660 transmits programming instructions and application data, among the CPU 652, the I/O device interfaces 654, the network interface 656, the memory 658. The CPU 652 is included to be representative of a single CPU, multiple CPUs, a single CPU having multiple processing cores, and other arrangements.
Additionally, the memory 658 is included to be representative of a random access memory or the like. In some embodiments, the memory 658 may include a disk drive, solid state drive, or a collection of storage devices distributed across multiple storage systems. Although shown as a single unit, the memory 658 may be a combination of fixed and/or removable storage devices, such as fixed disc drives, removable memory cards or optical storage, network attached storage (NAS), or a storage area-network (SAN).
The preceding description provides examples, and is not limiting of the scope, applicability, or embodiments set forth in the claims. Changes may be made in the function and arrangement of elements discussed without departing from the scope of the disclosure. Various examples may omit, substitute, or add various procedures or components as appropriate. For instance, the methods described may be performed in an order different from that described, and various steps may be added, omitted, or combined. Also, features described with respect to some examples may be combined in some other examples. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein. In addition, the scope of the disclosure is intended to cover such an apparatus or method that is practiced using other structure, functionality, or structure and functionality in addition to, or other than, the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of a claim.
The preceding description is provided to enable any person skilled in the art to practice the various embodiments described herein. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments. For example, changes may be made in the function and arrangement of elements discussed without departing from the scope of the disclosure. Various examples may omit, substitute, or add various procedures or components as appropriate. Also, features described with respect to some examples may be combined in some other examples. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein. In addition, the scope of the disclosure is intended to cover such an apparatus or method that is practiced using other structure, functionality, or structure and functionality in addition to, or other than, the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of a claim.
As used herein, a phrase referring to “at least one of” a list of items refers to any combination of those items, including single members. As an example, “at least one of: a, b, or c” is intended to cover a, b, c, a-b, a-c, b-c, and a-b-c, as well as any combination with multiples of the same element (e.g., a-a, a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b, b-b-b, b-b-c, c-c, and c-c-c or any other ordering of a, b, and c).
As used herein, the term “determining” encompasses a wide variety of actions. For example, “determining” may include calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, a database or another data structure), ascertaining and other operations. Also, “determining” may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory) and other operations. Also, “determining” may include resolving, selecting, choosing, establishing and other operations.
The methods disclosed herein comprise one or more steps or actions for achieving the methods. The method steps and/or actions may be interchanged with one another without departing from the scope of the claims. In other words, unless a specific order of steps or actions is specified, the order and/or use of specific steps and/or actions may be modified without departing from the scope of the claims. Further, the various operations of methods described above may be performed by any suitable means capable of performing the corresponding functions. The means may include various hardware and/or software component(s) and/or module(s), including, but not limited to a circuit, an application specific integrated circuit (ASIC), or processor. Generally, where there are operations illustrated in figures, those operations may have corresponding counterpart means-plus-function components with similar numbering.
The various illustrative logical blocks, modules and circuits described in connection with the present disclosure may be implemented or performed with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any commercially available processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
A processing system may be implemented with a bus architecture. The bus may include any number of interconnecting buses and bridges depending on the specific application of the processing system and the overall design constraints. The bus may link together various circuits including a processor, machine-readable media, and input/output devices, among others. A user interface (e.g., keypad, display, mouse, joystick, etc.) may also be connected to the bus. The bus may also link various other circuits such as timing sources, peripherals, voltage regulators, power management circuits, and other types of circuits, which are well known in the art, and therefore, will not be described any further. The processor may be implemented with one or more general-purpose and/or special-purpose processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuitry that may execute software. Those skilled in the art will recognize how best to implement the described functionality for the processing system depending on the particular application and the overall design constraints imposed on the overall system.
If implemented in software, the functions may be stored or transmitted over as one or more instructions or code on a computer-readable medium. Software shall be construed broadly to mean instructions, data, or any combination thereof, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. Computer-readable media include both computer storage media and communication media, such as any medium that facilitates transfer of a computer program from one place to another. The processor may be responsible for managing the bus and general processing, including the execution of software modules stored on the computer-readable storage media. A computer-readable storage medium may be coupled to a processor such that the processor may read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. By way of example, the computer-readable media may include a transmission line, a carrier wave modulated by data, and/or a computer readable storage medium with instructions stored thereon separate from the wireless node, all of which may be accessed by the processor through the bus interface. Alternatively, or in addition, the computer-readable media, or any portion thereof, may be integrated into the processor, such as the case may be with cache and/or general register files. Examples of machine-readable storage media may include, by way of example, RAM (Random Access Memory), flash memory, ROM (Read Only Memory), PROM (Programmable Read-Only Memory), EPROM (Erasable Programmable Read-Only Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory), registers, magnetic disks, optical disks, hard drives, or any other suitable storage medium, or any combination thereof. The machine-readable media may be embodied in a computer-program product.
A software module may comprise a single instruction, or many instructions, and may be distributed over several different code segments, among different programs, and across multiple storage media. The computer-readable media may comprise a number of software modules. The software modules include instructions that, when executed by an apparatus such as a processor, cause the processing system to perform various functions. The software modules may include a transmission module and a receiving module. Each software module may reside in a single storage device or be distributed across multiple storage devices. By way of example, a software module may be loaded into RAM from a hard drive when a triggering event occurs. During execution of the software module, the processor may load some of the instructions into cache to increase access speed. One or more cache lines may then be loaded into a general register file for execution by the processor. When referring to the functionality of a software module, it will be understood that such functionality is implemented by the processor when executing instructions from that software module.
The following claims are not intended to be limited to the embodiments shown herein, but are to be accorded the full scope consistent with the language of the claims. Within a claim, reference to an element in the singular is not intended to mean “one and only one” unless specifically so stated, but rather “one or more.” Unless specifically stated otherwise, the term “some” refers to one or more. No claim element is to be construed under the provisions of 35 U.S.C. § 112(f) unless the element is expressly recited using the phrase “means for” or, in the case of a method claim, the element is recited using the phrase “step for.” All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims.
| Number | Name | Date | Kind |
|---|---|---|---|
| 9990687 | Kaufhold et al. | Jun 2018 | B1 |
| 11263321 | Subbarayan et al. | Mar 2022 | B2 |
| 11537448 | Chari et al. | Dec 2022 | B1 |
| 11687540 | Pushak et al. | Jun 2023 | B2 |
| 20190114417 | Subbarayan et al. | Apr 2019 | A1 |
| 20210075805 | Cavallari | Mar 2021 | A1 |
| 20220100800 | Georgopoulos et al. | Mar 2022 | A1 |
| 20230027149 | Kuan | Jan 2023 | A1 |
| Number | Date | Country |
|---|---|---|
| 116361801 | Jun 2023 | CN |
