Patent Grant
10671452
This invention relates generally to the application platform field, and more specifically to a new and useful system and method for tagging and tracking events of an application platform in the application platform field.
In application platforms, developers using the platform often want to be able to detect when particular events occur. To do so, many developers develop polling systems to detect when an event occurs. Building such a system can be time consuming and difficult to maintain. Furthermore, some events of the application platform may not be exposed through an API or other programmatic interface. The application platform may have logistical reasons, security reasons, or business reasons for not exposing all internal events to third party developers. Thus, for some events, developers may not be able to detect the event. Thus, there is a need in the application platform field to create a new and useful system and method for triggering on platform usage. This invention provides such a new and useful system and method.
The following description of preferred embodiments of the invention is not intended to limit the invention to these preferred embodiments, but rather to enable any person skilled in the art to make and use this invention.
1. System for Triggering on Platform Usage
As shown in
The system is preferably implemented alongside an application platform. Preferably, the application platform is a multitenant, distributed computing system providing an HTTP-based application programming interface (API). The application platform may alternatively be any suitable platform. The application platform preferably provides a service used by outside applications or devices. In one preferred variation, the application platform preferably provides a usage-based API service. In one variation, the usage-based API service enables use of communication channels such as the telephony application platform described in patent application Ser. No. 12/417,630 filed 2 Apr. 2009, entitled “System and Method for Processing Telephony Sessions”, which is hereby incorporated in its entirety by this reference. A telephony or communication application platform can enable synchronous communication sessions such as voice sessions, video sessions, screen sharing sessions, or any suitable synchronous form of media communication. The communication can be carried out over PSTN channels, SIP channels, IP-based channels, WebRTC, or any suitable communication protocol. The communication application platform can similarly facilitate asynchronous communication such as SMS, MMS, IP-based client application messaging, proprietary platform messaging (e.g., social network messaging), or any suitable form of asynchronous communication. The application platform may alternatively provide any suitable service. The system is preferably integrated within an application platform. Alternatively, the system may serve as a standalone service and may include an interface to enable at least one application platform or applications to generate events, toggle counters, generate usage triggers, perform responses for a usage trigger, and/or interact with the system in any suitable manner.
The application platform is preferably a multitenant platform with multiple accounts using the platform to supplement operation of external applications. The application platform is a different system from the external applications, and mode of interaction and the security between the application platform and the application of an account can characterize that separation. As with the telephony application platform described above, the application platform can include characteristics of operating according to responses of an outside developer application. In some instances, the application platform submits requests to the client application, and the application platform will perform a service according to the response. Such a model can be common in communication-based service platforms where the service platform provides significant infrastructure to handle incoming calls. The application platform acts as infrastructure delegate for a particular service. In some instances, the application platform will post data to the application server (e.g., an HTTP POST). In the telephony application platform, the platform detects external events such as an incoming telephone calls. In response to a call associated with an account, the application platform requests direction from an application server of the account. The application server can be hosted and operated by an outside party independent of the telephony platform. From the perspective of the application server, the telephony application platform is a type of client device (e.g., a browser session). However, unlike a user controlled client device, customized client-side code cannot be created and installed on the client side. Such client-side custom browser code can be used by a developer to catch and responsively relay suitable data to the application server, but that option may not exist in such an application platform. Within the telephony application platform, application instructions are executed and managed according to the platform infrastructure and logic. In the case of a telephony application platform, considerable infrastructure and services are required to provide the calling services. Logistically, the complexity of the system can be a barrier to allow customer customization (i.e., customization by outside application developers). Unlike a system where an application server communicates with a developer-implemented client application, the developer cannot modify the platform components beyond the interfaces exposed by the application platform. Additionally or alternatively, even when customization would be feasible privacy issues, business strategy, and security issues can pose other barriers that the system functions to support.
At least one security layer can additionally exist between the application platform and an external application. The application platform can depend on application API requests to include account authentication information. An application server can additionally include security to protect access by entities external to the respective application system. In particular, the resources referenced by a callback URI can be secured through an authentication layer, a certificate verification layer, an IP whitelist/blacklist, or any suitable form of security.
A transaction system of a preferred embodiment functions to increment counters of application platform events. The transaction system is preferably coupled to an application platform. The transaction system is preferably integrated into the operation of the application platform. A variety of different services and resources of an application platform can be configured to notify the transaction system of events, usage updates, errors, warnings, or any suitable usage event of the application platform. The transaction system can log individual platform events. In some variations, a sub-set of the stored platform events can be queried and accessed through a platform API or user interface. Another sub-set of stored platform events could be internal and include private event information. The internal platform events can contain private information. The internal platform events can be used in combination to initiate a usage trigger. In the case of the telephony application platform, call routers, SMS services, MMS severs, video servers, client servers, SIP servers, and other suitable components can send event information for individual storage. The transaction system preferably includes counter storage and a counter buffer. The counter storage and buffer preferably store the count of particular types of events and facilitate triggering when a counter reaches usage trigger threshold. In some situations, the transaction system can include a summarizer which functions to process individual event logs and appropriately store a new counter or update an existing counter in the counter storage.
A counter storage module can function as a log of transaction history of an application platform. The counter storage preferably stores a plurality of counters. The counter storage is preferably a database but may be any suitable system for storing counter data. The counters may be tied to a particular account, subaccounts, and/or any suitable entity. The counters preferably include a parameter indicating the number of occurrences or instances for a particular application platform event of the application platform. Since counters can exist for a variety of different types of information within a system and may have different configuration requirements (e.g., time periods, update frequency, etc.), counters can be created by an account. A counter can be created through an API or user interface. In one implementation, a REST API is used to create a usage trigger by posting trigger customization parameters to a platform URI resource of “/usage/trigger/” with daily counter parameter of 365 and hourly counter parameter of 24, and event pattern of a block of particular area codes. In some cases, maintaining a counter is associated with some expense either for the application platform and/or the associated account. Accordingly, the system enables flexibility of creating counters without automatically counting every type of event for all accounts. In some cases, the system can include default counters that are created for particular types of events. Triggers stored in the usage trigger database can preferably be attached or associated with a particular counter. As shown in
A counter buffer can function as a temporary collection of counters that are awaiting analysis by the trigger monitoring system. The counter buffer can temporarily store newly incremented counters in the buffer. After the trigger monitoring system has processed a counter in the counter buffer, the counter can be deleted or removed from the buffer in a suitable manner. In an alternative configuration, the counter buffer can be replaced or function as a record of events yet to be counted. To avoid constantly updating counters, the counter buffer can store a pointer to stored events that should be processed into a counter. When a counter should be updated according to timing of a usage trigger, the summarizer or other suitable component processes unaccounted events into the counter. The system can use other alternative approaches to updating a counter such as recording a timestamp of last update and retrieving events after that timestamp when updating the counter.
The summarizer can function as a service to process individual event logs into counters. In some instances, a counter may be created for a class of events. Events sharing common properties can be counted together. For example, an event can be logged for every communication session established on behalf of the account. Those sessions can be directed at different destination endpoints or addresses. All of these events can be counted as a whole to measure total number of calls, but the summarizer can alternatively count one sub-set or multiple subsets of the events. Some events can additionally contribute to the count of multiple counters. For example, communication events directed at telephone numbers with a particular area code can be counted in a counter for that area code and with a total outbound call counter. The summarizer pattern matching can be rule based, use regular expressions, or use any suitable approach to detect patterns. The summarizer can additionally do fuzzy detection of groups to automatically detect events that match patterns of a group of events. In the case of error events, multiple events may be logged with the same error code; the summarizer can process an error report stored with the error events to further distinguish between the error events. For example, an error code could be caused by an internal error of the platform or by malformed instructions from an application server. The summarizer could process the error report and distinguish between these two types of errors based on natural language processing of the code or data leading up to the error.
A usage trigger database of a preferred embodiment functions to store resources characterizing how to monitor usage and actions to perform. The usage trigger database preferably stores a plurality of usage triggers. A usage trigger is preferably a data object characterizing when to trigger and at least one response action. The usage trigger is preferably set for a particular type of counter. Additionally, a trigger evaluation interval may be set such that the usage trigger will only constitute a trigger on a periodic basis (e.g., hourly, daily, monthly, one time, etc), for a particular event, and/or according to any suitable rule. Polling is one variation for implementing the trigger evaluation intervals. The usage trigger preferably additionally includes at least one parameter defining a response when the trigger is satisfied. One parameter could be a callback URI, where an HTTP response can be sent. The callback URI preferably references a web application controlled by the developer creating the usage trigger, and the web application may perform any suitable action the developer configures. The trigger monitoring system will preferably use the stored callback URI as a destination endpoint for a transmitted message with the counter status. Additionally or alternatively, the usage trigger may specify a particular application platform response. For example, in a telephony application platform, a call can be ended even if the call is in progress. Enabling counter based manipulation of an application can allow applications to respond to events that could otherwise not be possible by outside developers. Private data and platform functions can be performed on behalf of the developer in response to internal counters. Similarly, the platform response could include modifying an account, a communication session, application instance, or any suitable response. The usage triggers are preferably set for particular accounts or other groupings. The usage triggers in the usage trigger database can be keyed by application platform accounts or subaccounts or any suitable key. The usage triggers may alternatively be globally set.
A trigger monitoring system functions to monitor the counters in the context of the set usage triggers. The trigger monitoring system is preferably communicatively coupled to the counter buffer of the transaction system. The trigger monitoring system preferably reads recently updated counters from the counter buffer, compares counters to an associated usage trigger if one exists, initiates a response by the trigger action processor if required, and removes the counter from the counter buffer. The trigger monitoring system may alternatively retrieve counters from the transaction system in any suitable manner. If a particular counter does not have an associated usage trigger or the usage trigger evaluation interval doesn't call for processing, then the counter is simply removed from the buffer and no response is triggered.
A trigger action processor of a preferred embodiment functions to initialize or perform the response of an activated usage trigger. The trigger action processor is preferably a subprocess of the trigger monitoring system, but may alternatively be an independent module, at least a sub-portion of an integrated application platform, or any suitable component. As described above, the response of a usage trigger can include a callback URI. The trigger action processor will preferably make an HTTP request to the callback URI when a usage trigger is processed. The HTTP request may include parameters associated with the usage trigger and/or the counter. Additionally or alternatively, the trigger action processor may use a component to access an API of an application platform to perform a designated action specified in the usage trigger.
In an alternative embodiment, the system can additionally include a tagging engine and a tracking mechanism as shown in
The tagging engine functions to enable identifiers to be associated with account platform interactions. When an account is interacting with the platform, a tag parameter can be added to the interaction or request. That tag engine then associates that tag identifier with the corresponding logged records of the platform. In one instance, a single event record is recorded in response to an outside account request. That event record is stored such that event can be retrieved by querying the logs for the tag identifier. In another instance, an outside account request results in multiple events and/or services logging event information while completing the request. For example, two internal services may facilitate completing a request. Events logged by the two internal services that are a result of completing the usage instance can both be associated with the usage-instance identifier. In one implementation, the tag is associated with a usage-instance identifier such as a session identifier, an API call identifier, or message identifier. For example, a telephony platform can use call identifiers to identify any action taken while servicing a particular call. When querying the tag, the associated events and logs are retrieved.
The application platform preferably includes a mechanism through which tags can be attached to interactions. The tags can be attached during API requests, SDK function calls, application instructions, or other suitable interfaces that an account uses when directing a platform. As shown in
The tracking engine functions to configure monitored usage within the application platform. The tracking engine is operative on logged events and metadata recorded during usage of the application platform. The tracking engine manages a plurality of trackers, which can operate similarly to customizable counter objects. A tracker is preferably created by an account holder. A benefit of trackers is that account holders can use the trackers in combination with the tags to customize the usage analytics of an independent application platform. When creating a tracker, an account holder can specify one or more tags. The specified tags determine which logged events are evaluated for the tracker. Any suitable set and combination of Boolean operators can be applied to tags. The tracker can be for the union of two tags, the overlap of the two tags, the difference between two tags, the opposite of the union of two tags, or any suitable set of events defined through the tags. The tracker can additionally include event filters, which can use event types, event patterns, and other event properties to further define events evaluated by the tracker. Trackers can additionally include temporal properties that define the update frequency of the tracker. Trackers are preferably generated by an account holder through an API, a user interface, application instructions, or through any suitable interface mechanism of the application platform.
The tracker updates usage metrics of associated events according to the temporal property of the tracker. Similar to a counter, a tracker can maintain a measurement on the accumulated usage of associated events. API access is additionally made to read the status of a tracker as shown in
The tracker engine can additionally enable trackers to be used in combination with usage triggers. Triggers can be associated or attached to trackers in addition to or in place of a counter. The triggers enable automatic action or responses according to thresholds or conditions. Callback URIs or automatic internal actions can be triggered based on the tracker metrics. An account can use tags, trackers, and triggers in combination to configure highly customized operations within a closed platform. The account holder will often operate an application server that has at least one security layer between the application server and the platform.
2. Method of Triggering on Platform Usage
As shown in
Step S110, which includes operating the platform, functions to execute processes of the platform to generate events. As the method can enable multitenant usage triggers controlled by outside entities, the triggers enabled by the method may provide insight into events otherwise not viewable from outside entities through an API (e.g., for reasons relating to business issues, technical limitations, security concerns, and/or other reasons). The method can be particularly beneficial to application platforms that operate according to responses of an outside developer application. While the application platform can be actively prompted to perform an action, the application platform preferably includes an operation model where the platform independently processes data/information/events and communicates requests to outside applications for direction. An outside developer can configure an external application server to direct the application platform through instructions. Such a delegate operational platform model can be useful in infrastructure specialized platforms and/or platforms managing secure or private information. Telephony and/or communication service platforms are one example of an application platform that would have specialized infrastructures—there would be numerous business and security reasons why the system architecture and the raw event information could not be exposed to enable outsiders to build such a counter event system. Similarly, many application platforms would have access to a large amount of event information which could be pooled from within an account or across multiple accounts in a multitenant environment. Again, there would be numerous privacy, security, competitive advantage, and logistical reasons that could prevent directly exposing information enabling a counter event system, but the method of the preferred embodiment can accommodate such concerns. One characteristic of a delegate operational platform is that the platform can operate asynchronous to the execution of the outside application that uses the platform. In one embodiment, the method can function as an asynchronous try-catch feature of a platform for outside developers. In another embodiment, the method can function to integrate application business logic of an outside application with unexposed operations of an application platform.
Operating the platform preferably executes a process on behalf of an account, and, during execution of the process, events can be published. The events can be notifications from various services of the platform, errors, warnings, status updates or any suitable event log. Various services and resources of the platform publish the events. The method can work in cooperation with an existing event logging system or alternatively platform resources can directly publish events to the transaction system. Executing the process is preferably performed on resources inaccessible by an account holder (i.e., an account holder has limited visibility into events occurring). Executing a process can include processing a request made by an outside resource. Executing a process can alternatively include processing application instructions at least partially supplied by an account holder. In a communication service platform, executing the process can include facilitating/hosting/managing a synchronous communication session (e.g., voice, video, screen sharing or other suitable communication session). Application instructions can additionally be executed during that communication session. Executing the process can additionally or alternatively include a communication service platform sending/receiving messages (e.g., SMS messages, MMS messages).
Step S120, which includes receiving a trigger configuration, functions to configure settings that control trigger events within a system. The trigger configuration is preferably received as a request through an application programming interface (API). The API may be used to enable applications to programmatically create, read, update, and/or delete trigger configurations. The trigger configuration may alternatively be specified and transmitted through a user interface. For example, a user may be able to input usage trigger settings from an account management website. Usage trigger configuration preferably specifies at least one usage key to which the usage trigger relates. The usage key specifies the event, resource, error, or item counted and used to trigger a response. Exemplary usage keys can include total sales, call time, counts of events like sent or received messages, counts of particular API calls, measure of a particular resource usage, or any suitable usage type. The usage triggers are additionally set for a subset of usage of an application platform. The trigger request can additionally specify the type of counter such as an absolute counter that tracks a total number of events, a change counter that tracks number of new events from a starting point, time counters that track absolute or changes in usage time, a percentage counter that can measure ratios or percentage changes, rate counters that updates a counter to be the current rate or frequency of a particular event, or other suitable approaches of measuring usage. The usage key can include filters or pattern parameters, or other specifications to limit the counter (and correspondingly the trigger) to a subset of types of events. For example, the subset of events counted may be phone call events originating from a phone number within a set of area codes. Preferably, the subset of usage is defined by the account associated with the usage and the usage trigger. Additionally or alternatively, a subset of usage may include usage related to a sub-account, a type of usage, a regional grouping of usage, or any suitable subset of usage of an application. A usage trigger configuration is submitted along with an account or sub-account identifier. A token or key can be used to authenticate permission sot create a usage trigger for the specified account or sub-account. The usage trigger will be scoped to apply to usage of the corresponding account or sub-account. For example, usage triggers are preferably set by an account, and the usage triggers are only enforced for counters for that particular account.
The usage trigger parameters may additionally define a callback URI, an evaluation interval, and/or a trigger action.
The callback URI is preferably a resource identifier that can be messaged when the usage trigger is activated. The callback URI can be any URI. The callback URI can be a website URL of an application server operated by the account developer. For example, the callback URI can be to the same application server system used to generate application instructions for the application platform, the application server can modify subsequent instructions based on state generated in response to a usage trigger. The callback URI can alternatively be a URI of a resource of a third party. For example, a developer could setup a usage trigger to send usage-triggered events to a third party analytics server where logging and event analysis is performed.
A usage trigger parameters can additionally include security credentials, which can enable access to resources specified by a callback URI. In one variation, the resource of the callback URI (e.g., an application server operated by an account holder) may have a security layer isolating the resource from unwarranted traffic. Some security mechanisms may be communicated when receiving a trigger configuration. In one variation, an authentication token can be submitted which the application platform can store and use to sign outbound communications to the callback URI.
The security credentials are preferably stored by the application platform and used when acting in response to a usage trigger. In one implementation, the security credentials are authentication credentials that are included in transmission from the application platform to the external application. The authentication credentials can be a username/password combination, a certificate, an authentication token or key, and/or any suitable authentication mechanism. An alternative approach to interfacing with security of an external application can use identifiable resources when accessing the application. Use of the identifiable resources preferably includes transmitting communication to a callback URI from a pre-defined IP address. In such a variation, the method can further include responding with a communication address of a resource of the platform. The communication address is preferably used when transmitting a communication to the callback URI. The account can use the communication address to configure an IP white list or a black list to selectively allow traffic. Such communication address information can alternatively be pre-configured through administrator controls. In another approach, virtual private network credentials can be shared between the application platform and an external system of an account, and a VPN tunnel is used when accessing a callback URI.
An evaluation interval is preferably the rule specifying when the usage trigger should be checked. In one variation, the evaluation interval is a polling interval. The polling interval could be hourly, daily, monthly, yearly, one-time event, or any suitable time interval. In another variation, the evaluation interval may be an event-based interval. In an event-based interval, the usage trigger may be checked when a particular event or series of events are detected. The usage trigger is preferably checked in Step S140 if the evaluation interval deems a check appropriate. The trigger request can additionally or alternatively specify counter thresholds that can define when the usage trigger and/or the associated counter are evaluated or acted upon. A threshold of a usage trigger can be used in combination or in place of a polling interval.
A trigger action of a usage trigger is preferably a response taken by the application platform when the usage trigger is enforced/activated. Exemplary actions can include suspending an account, sending a notification, ending a communication session, cancelling a message, and changing permissions. The trigger action may be used in combination with a callback URI or use as an alternative for the callback URI. The trigger action preferably enables system/platform functionality that could be configured in the creation of the usage trigger. In some variations, a trigger action can function to enable a response to be made that is not exposed through an API. Some exemplary trigger actions may include suspending an account, charging stored value from an account, charging a credit card, sending a notification or alert message by email, SMS, phone, IM, or altering the behavior of an application, and/or any suitable action. As an example, a calling card application may configure a usage trigger with a trigger action that prevents a customer to continue making international calls. Any suitable number and combination of callback URIs and trigger actions may be used.
Step S120, which additionally includes storing the trigger configuration in a usage trigger database, functions to create a repository of usage trigger configurations. The usage triggers may be stored in any suitable manner. The usage triggers are preferably retrievable based on the related counter. For example, a usage trigger for the number of messages sent from a particular account can preferably be retrieved using the account and the type of counter (e.g., number of messages sent). The application platform can be a multitenant platform. Storing the trigger configuration can include storing a plurality of trigger configurations of multiple accounts. The trigger configurations can be stored as accessible API resources. For example, a REST API usage trigger resource can be updated by an account holder submitting API calls to a “/usage/triggers/” resource or a particular trigger resource within the triggers resource path.
Step S130, which includes a transaction system incrementing a counter, functions to measure the usage from an application or platform. The transaction system preferably exposes an interface used by an application platform to update counters. Events are preferably published or generated by resources of the platform and submitted to a transaction system that logs and/or counts the events. The events can be any suitable type of events such as notifications, status updates, errors, warnings, summaries of multiple events, or any suitable event notification. In a preferred implementation, the platform is a communication service platform managing communication sessions of an account. The communication sessions are preferably telephony communication sessions controlled by telephony instructions managed by an outside account resource. In one variation, the communication service platform is used for voice calls such as PSTN, SIP, or other suitable forms of synchronous communication sessions. The synchronous sessions can alternatively be video, screen sharing or other suitable mediums of communication. In another variation, the communication services platform can additionally or alternatively be used for asynchronous telephony messaging over SMS, MMS, proprietary IP protocols, or other suitable forms of messaging. Individual events of the application platform are logged and added to the counter. In one variation, the events may only be counted if a usage trigger depends on counting such an event, which can function to sparsely account for counting events. In a multitenant platform counting all events of every account could incur considerable storage resources. The method preferably selectively counts events if a usage trigger depends on counting the event. The method can include the transaction system receiving an uncounted event, searching for associated usage triggers associated with the uncounted event, and if a usage trigger is associated with the event, counting the event in a corresponding counter. Searching for an associated usage trigger can include querying usage trigger resources of related accounts or sub-accounts. Global usage triggers can additionally be queried. The query can search for usage triggers with usage keys that match the event. If no usage triggers are identified then the event is not counted. If a usage trigger is identified then the event is counted. There can additionally be multiple counters that may be updated if for example multiple usage triggers have different usage keys that count the event. For example, an inbound mobile call can be counted in a counter for mobile calls and in a counter for inbound calls. If a counter object does not exist, a new one is created. If a counter does exist, the event is accounted for in the existing counter object.
Counters are preferably any suitable data objects characterizing a metric of the application platform. Counters can be defined for any suitable type of usage. In some implementations, default counters can be defined for a plurality of types of events regardless of existence of a related usage trigger. Such counters can be for commonly counted events. Usage triggers can be added and immediately act on the current state of usage with default counters. More preferably, counters are sparsely defined according to the active usage triggers stored in the application platform. Sparsely defined describes the property of counter storage where counters are not stored for the full set of countable items for all accounts on the platform. Counters are created or updated if a usage trigger depends on counting a new event. As shown in
As shown in
Step S140, which includes monitoring counters in context of an associated usage trigger, functions to determine if a counter requires action by a usage trigger. A trigger monitoring system preferably monitors the status of counters updated by the transaction system. The trigger monitoring system preferably monitors the buffer maintained by the transaction system, but the monitoring system may use any suitable technique to check the status of the counters. When a counter is updated, it is preferably added to a buffer. Once in the buffer, the trigger monitoring system will preferably read the counter from the buffer. It will then see if the account associated with that particular counter has a usage trigger for that type of counter. If there is an associated usage trigger, the trigger monitoring system may additionally check if the evaluation interval of the usage trigger is satisfied. When a usage trigger is identified for the counter and any additional conditions such as the evaluation interval are satisfied, then the usage trigger is processed and acted upon in Step S150. The counter is preferably removed from the buffer once the counter is analyzed. In a related approach, the usage trigger may be processed according to the timing of the evaluation interval and the related counters are updated in response. When it is time to process the usage trigger, a trigger monitoring system can update associated counters. In one variation, a counter buffer is used to record which events have not been accounted for in the current counters, and in particular, which events that contribute to the counter associated with the currently processed usage trigger. The evaluation interval prompts the counters to be updated. Events referenced in the counter buffer are measured and accounted for in the counters associated with the usage trigger. Such a variation can be used with usage triggers for errors and warnings. A similar variation can prioritize the update of counters with usage triggers with upcoming intervals.
Additionally, the method can include identifying events satisfying a pattern of a counter type, which functions to allow pattern matching, fuzzy grouping, or algorithmic identification of event types. A summarizer as described above or any suitable grouping engine can determine if an event should contribute to a particular group and if so which one. If a usage trigger defines a counter type that depends on pattern detection, an event pattern definition can be created and used within a summarizer system when processing events. The summarizer can consume events from a raw event log, and if the event satisfies an event pattern definition, accounts for the event in the associated counter.
Step S150, which includes processing usage trigger upon a counter satisfying a condition of the usage trigger, functions to perform the response specified by the usage trigger. In a first variation, the usage trigger is satisfied when the evaluation interval has expired and the measurement of the counter satisfies a condition. The condition is preferably defined by a threshold limit defined in the usage trigger configuration. The threshold can be a maximum threshold where the usage trigger is processed when the measurement of the counter exceeds the threshold. The threshold can be a minimum threshold where the usage trigger is processed when the measurement of the counter is less than the threshold. The condition can alternatively be a range, a function of other properties including at least one measurement of a counter object. Processing a usage trigger preferably invokes the action configured for the usage trigger.
In one variation, the usage trigger configuration includes a callback URI parameter. Processing the usage trigger can include sending a request (e.g., HTTP request) to the callback URI, which functions to alert, message, or notify a resource of the counter status. The URI is preferably for an internet accessible resource that can perform any suitable action after receiving the request. The URI is preferably an external resource operated by the account associated with the usage trigger. For example, a first application created by a first account can create a usage trigger. When a counter of the usage trigger satisfies a condition, the external transmits a message to a resource specified by the callback URI. The callback URI request may additionally include data parameters characterizing properties of the counter and/or usage trigger. The application server can then perform any suitable action. As exemplary external application actions, an application server could update a database based on the event, alter state of a session controlled by the application server, send an alert to a developer, or any suitable response. In one implementation, an application server can respond by sending a response to the callback URI call. The response can include application platform instructions. The application platform instructions can act similarly to the trigger actions described below in that they alter state of the application platform. In one variation, a callback URI could be to a third party application server, such as an analytics service operated by a service distinct from the account holder and the application platform operator.
When sending a request to the callback URI, the method can additionally include sending the request according to security procedures. The resource referenced by the callback URI can be secured against unwarranted access. An open URI or a private URI can be contacted by any outside entity, which may be sufficient for some situations. A secured callback URI includes some mechanism to limit access of the callback URI. In one variation, security credentials of the usage trigger are used to access the callback URI. The external application can use the security credentials to authenticate or authorize access to the callback URI as shown in
As an additional or alternative variation, the usage trigger configuration may include a trigger action. Processing the usage trigger can include performing an action specified by the associated usage trigger. This variation preferably enables real-time response within an application platform. In some situations the actions that may be performed may not be exposed to outside entities through an API, thus the action enables responses that in some situations wouldn't be available to outside entities. For example, if there is a call being performed over a telephony application platform, and the call uses up all pre-paid minutes during the call, the usage trigger may have a trigger action to end the call. Thus the usage trigger enables an outside entity to build event based functionality without having to maintain an application to cancel the in-progress call or even be reliant on that functionality being exposed through an API. Executing a trigger action may additionally or alternatively include suspending an account, charging stored value account, charging a credit card, sending a notification or alert message by email, SMS, phone, IM, or altering the behavior of an application, and/or any suitable action.
Additionally, processing the usage trigger can include resetting or removing the usage trigger. In some instances, a usage trigger can be configured as a single use usage trigger. After the usage trigger is processed, the usage trigger resource can be removed or suitable managed to end use of the usage trigger. A counter associated with the usage trigger can similarly be deleted or closed. In some instances, a usage trigger can be configured to reset. Preferably, resetting a usage trigger includes creating a new counter or clearing the counter. Resetting a usage trigger can be used to enable actions that are triggered after a specified number of occurrences.
3. Method for Tagging and Tracking Platform Usage
As shown in
Block S210, which includes receiving a tag identifier, functions to obtain direction for customized classification of the interaction and resulting events and logs. The tag identifier is preferably received through an account-initiated action. An account can be any suitable entity. Preferably, the account is used by an outside party to which internal operations of the platform are hidden. The account is preferably a developer account to which a developer can build applications and software services that use account credentials in making requests and/or instructing a platform in how it should be used. At least one security layer preferably exists between the account and at least a subset of internal resources and services of the platform. The tag identifier can alternatively be automatically applied to application platform interactions according to pre-defined event classifiers. The pre-defined event classifiers can be defined by an account entity, the application platform, or a third party. A tag identifier is preferably a descriptive text phrase or word used to mark or denote a characteristic of the event. Multiple events and interactions can be identified with an identical/shared tag identifier. A tag identifier shared between two or more events can enable those events to be grouped for analytics and/or usage-based event triggering.
Receiving a tag identifier preferably includes detecting a tag identifier as a metadata parameter of a platform instruction. Platform instructions may be executed through an API, through application instruction processing, through user interface actions, or through any suitable mechanism. In one variation, detecting a tag identifier as a metadata parameter of a platform instruction can include receiving an API request that includes at least one tag identifier. As shown in
An account holder can arbitrarily define tag identifiers. A new tag identifier can be used to create a new tag identifier. The tags can additionally include a hierarchical relationship, such that a first tag identifier can be a parent tag that includes child tags identifiers. A set of tags may additionally be received or detected, and associated with the platform interaction. A set of tags associated with a platform interaction is then accordingly mapped to related events. For example, if a developer wants to track calls made by pro account and that are initiated from their mobile app, the developer can use the tags “pro” and “mobile-app” for different platform interactions. If one platform interaction is made by a pro account using the mobile app then that related instruction may specify the field “tags:[pro, mobile-app]”. The tag identifiers can be used by the account holder in any suitable manner. Account-side metadata around the platform can be attached to platform actions without exposing the internal operation of the platform and without the platform needing account specific knowledge of how the account is using the platform. An application of an account can use internal log and data to classify different uses of the application platform. Multiple accounts may have various requirements when using the application platform, and the different accounts can customize the manner of tag usage to meet their respective application requirements.
As mentioned above, a tag identifier may additionally or alternatively be detected and associated with a platform interaction through automatic tagging as shown in
An auto-tagging rule configuration, in one implementation, is specified as a markup document as shown in
An auto-tagging rule configuration can preferably specify any suitable condition for when to apply an automatic tag. A set of properties can be exposed, on which a condition can be formed. The properties may include platform interaction type (e.g., PSTN call, SIP call, video call, text message, media message, etc.), endpoint properties, carrier properties, communication metrics, and/or any suitable properties. Endpoint properties are preferably properties relating to a caller, callee, or any suitable endpoint involved in the communication. Endpoint properties may include country code, mobile/landline, regional area code, endpoint type, the endpoint address, geographic information of where the endpoint communicated from, and/or other endpoint properties. Call metrics may include media quality, duration of the session, and/or any suitable metrics.
The conditions may use Boolean algebra (AND, OR, XOR, NOT, etc.), set mathematics (Unions, intersections, etc) or any suitable mechanism for defining a condition. In one variation, a callback mechanism may enable customizable processing to be performed to indicate if a element matches a condition. When a particular context has one or more auto-tagging rule configurations, a set of platform interactions are preferably processed to determine if they satisfy an auto-tagging rule, and, if an event does meet the conditions, the tag is applied. Otherwise, the event is not automatically tagged. Multiple auto-tagging rules may be defined, and each condition is preferably checked. In one variation, auto-tagging detection is applied as the events occurred (e.g., in real-time). Auto-tagging detection may alternatively be applied as a synchronous step at any suitable time after an event. For example, auto-tagging may be applied periodically on a batch of logged events.
Block S220, which includes associating the tag identifier with logged event, functions to assign the tag identifier to related platform events and usage. The tag identifiers are preferably used to track and monitor internal operations. An event is preferably logged in association with an account that is associated with the platform interaction that resulted in the logged event. When executing a platform interaction, a set of different actions can occur, and the tag identifier association is preferably maintained for the set of different actions. For example, to service an API request, multiple different internal platform resources may perform different steps to completing the API request. The multiple internal platform resources can log different events as part of internal logging measures, and the various logged events are associated with the specified tag identifier. Associating the tag identifier with an identified platform interaction event preferably includes associating the tag identifier with a set of logged events that are within the same session context as the initially identified platform interaction event. A session context is preferably any property or conditional set of properties that define a collection of related events platform interactions. As described below a context session can be a communication session. Synchronous communication, such as a phone call or video call, may be defined as all the events relating to one particular sustained session of communication between a set of endpoints. Such a communication session may be identified in the logs by a call identifier. A communication session for asynchronous communication may be defined by all communications that occur between a consistent set of endpoints at some frequency. For example, an SMS, MMS, or IP messaging communication session may be segmented by delays of 30 minutes or more between messages. A session context may alternatively be within set time windows. For example, all communications for a particular day. In one variation, the tag identifier is applied to the set of subsequent events in the session context. In another variation, the tag identifier may be retroactively assigned to previously logged events.
In a telephony application platform of a preferred embodiment, the tags can be assigned through API requests or through telephony instructions in an application document supplied by an application server of an account. An API request can be used to initiate an outgoing voice call (e.g., PSTN, SIP, etc.), video call, screen sharing session, message (e.g., SMS, MMS, push notification, or IP message), or other forms of communication. A communication API request can include one or more tag identifiers. Logs, events, and other metadata stored in association with the communication can be associated with the tag identifier. An API request can be used to augment an active communication session. Such API requests can similarly include a tag identifier. The tag identifier can be added to the whole call session, to subsequent logs, or to a subset of events that directly relate to the action used to augment the communication session. A new tag can alternatively replace a previously specified tag attached to the call session. A telephony instruction within an application instruction document can include a specific tag identifier
Block S230, which includes defining a tracking resource with at least one tag identifier, functions to create an object within the application platform to count and measure usage and events. A tracking resource is preferably created according to the direction of an account. An account holder can use an API, graphical user interface, a configuration file, or any suitable mechanism to specify properties of one or more tracker resources. The tracker resources are preferably active within the account. A tracker can include a tracking pattern and a temporal update parameter. The tracking pattern is preferably a tag parameter that can include one or more tag identifiers. In one variation, the tracking resource is defined by a markup language document as shown in
Block S240, which includes measuring platform interactions associated with the tag identifier, functions to account for relevant logged events. Measuring platform interactions is preferably achieved in connection with operating the computing platform. Operating the computing platform preferably includes internally executing a process on behalf of the platform interaction and logging at least one event. In response to those generated events, block S240 can facilitate accounting/measuring at least one metric of the tracking resource in response to a logged event satisfying a tracking condition of the tracking resource. The tracking resource is used to track the occurrences of particular types of events. The tracker resource is preferably updated according to the temporal update parameters. When updating a tracker resource, an event log is queried for new events matching the tracking condition. In one simple scenario, tracker resource, the tracking condition is a single tag. An event log record that matches the tag parameter of the tracker resource is Boolean function with multiple Tag identifier arguments. If the event record satisfies the Boolean function based on the tag identifiers for that event then it is included in the measurement. In yet another scenario, the tracking condition can be a Boolean function with tag identifier arguments and general event properties. The retrieved events can then be processed and appropriately added to the tracker measurement. In one variation, the measurement is a measure of number of events, and a tally of event occurrences can be used in an event tracker. Accordingly, Block S240 can include recording a running number of events that satisfy the tracking pattern. In another variation, the measurement is a measure of a property related to the event, wherein Block S240 can include updating an aggregated metric of events that satisfy the tracking pattern. The property is preferably a usage property such as such as data usage, call duration, request size, or other usage property. The aggregated metric may alternatively be an overall statistic such as an average, median, maximum, minimum or other suitable statistical metric of one ore more property values of an event. An aggregated metric may be particularly beneficial if all events include metadata with measurable data. As an example, communication application event records may include a property for call duration, call quality, amount of data used, and/or other suitable metrics. Measuring platform interactions may additionally involve updating several measurements. For example, a count of events and an average value of a particular event property (e.g., quality score) could be measured.
Block S250, which includes providing access to measured platform interactions through an application programming interface, functions to enable account users to build interactions through an interface. A tracker resource is preferably made accessible as an API resource. Writing to the API resource can update or change the state of the tracker resource. Reading from the API resource can enable access to the measured usage associated with the tracker. An account holder can poll the tracker resource and build external logic in an application based on that information. The measured usage associated with a tracker resource can additionally be presented through a user interface. One potential use of data of a tracker resource is with analytics by an account holder. The analytics can be presented to users as charts, graphs, tables, and other suitable data infographics.
Additionally or alternatively, the method can include creating a usage trigger conditionally activated by a tracker S260, which functions to use trackers in the conditions of a trigger resource. The integration of trigger resources with a method involving tags and tracking resources may additionally include receiving a trigger configuration from an account, wherein the received trigger configuration includes a callback uniform resource identifier and a trigger condition based on the tracking resource; monitoring the tracking resource in the context of the associated trigger configuration; and processing the trigger, wherein processing the trigger comprises transmitting a request to the callback uniform resource identifier of an application server upon the tracking resource satisfying the trigger condition of the associated trigger. A trigger resource can preferably be created by an account holder in a manner substantially similar to above. In place of or in addition to a counter, a trigger resource can depend on at least one tracker resource. The triggers can similarly include a defined callback URI and/or a platform action. The trigger can function substantially similar to the triggers described above. However, the triggers can be configured to react to events tracked through customize tagging and tracking. The trigger can similarly message a callback URI. Communicating with a callback URI can involve similar security measures as described above.
The usage trigger can alternatively invoke an internal action. The internal action may include actions not otherwise permitted to an account such as immediate communication session suspension, account suspension, endpoint usage suspension, or other suitable actions.
In one variation, the method may apply block S260 in place of or in addition to block S250. In another variation, the process of using counters may be used in combination with tags and triggers without a defined tracking resource. In this variation, a counter functions as a special case counter wherein the counter measures platform interactions based on events with one defined tag. Blocks S210 and S220 are preferably used in combination with processes of method S100, wherein the counter is configured to count events with a particular set of tags.
In one application of the method, tags may be used by an account holder to provide multitenant experiences to users of the account holder's system. The method may include the tag identifiers being associated with a unique identifier of sub-accounts of an account; and measuring accumulated credit of platform usage broken down by tags. An account holder supplying the tags preferably facilitates tagging platform interactions with an associated sub-account of that account during block S210. Measuring accumulated credit is preferably applied during block S240. Preferably the price of various events is indicated in the event records. For example, ending a call will result in the price of the call being recorded in the call event log. As one exemplary scenario, a third party app using the communication platform may allow users to make phone calls from the third party app. In this example, the third party app may represent an account of the communication platform and the user may represent a sub-account segment of the account. The use of tags may be used to handle subaccounts, when subaccounts are not enabled in the platform or the use scenario doesn't lend itself well to a sub-account model. If the third party app manages a handful of phone numbers of which all the users share, then it may be hard to otherwise breakup use of the platform into distinct sub-accounts in the platform. The billing or crediting of an account may be all attributed to the third party app account on the communication application. The method may be applied to allow billing to be divided between the users of the third party application. The third party app preferably tags all interactions with the communication platform using a user identifier created within their application. Then, the tags are leveraged to breakdown platform usage so that usage can be attributed to distinct user accounts. In one variation, a tracking resource is setup for each user identifying tag, and used to measure the accrued bill for each user of the third party app. The third party app can query the measured bill or credit for a tag, and then charge the appropriate end user. In another variation, an event trigger may be used to automatically redirect billing of the account to the end users. A triggered event may be used to execute a billing event for given segment of usage within an account. The tags, trackers, and/or triggers may alternatively be used in any suitable manner.
The system and method of the preferred embodiment and variations thereof can be embodied and/or implemented at least in part as a machine configured to receive a computer-readable medium storing computer-readable instructions. The instructions are preferably executed by computer-executable components preferably integrated with the tagging engine, tracking engine, and/or the triggering engine of an application platform. The computer-readable medium can be stored on any suitable computer-readable media such as RAMs, ROMs, flash memory, EEPROMs, optical devices (CD or DVD), hard drives, floppy drives, or any suitable device. The computer-executable component is preferably a general or application specific processor, but any suitable dedicated hardware or hardware/firmware combination device can alternatively or additionally execute the instructions.
As a person skilled in the art will recognize from the previous detailed description and from the figures and claims, modifications and changes can be made to the preferred embodiments of the invention without departing from the scope of this invention defined in the following claims.
This application is a continuation of U.S. patent application Ser. No. 15/926,381, filed 20 Mar. 2018, which is a continuation of U.S. patent application Ser. No. 15/719,860, filed 29 Sep. 2017, which is a continuation of U.S. patent application Ser. No. 15/002,774, filed 21 Jan. 2016, which is a continuation of U.S. patent application Ser. No. 14/489,387, filed 17 Sep. 2014, which claims the benefit of U.S. Provisional Application Ser. No. 61/879,035, filed on 17 Sep. 2013, all of which are incorporated in their entirety by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5274700 | Gechter et al. | Dec 1993 | A |
| 5333302 | Hensley et al. | Jul 1994 | A |
| 5526416 | Dezonno et al. | Jun 1996 | A |
| 5581608 | Jreij et al. | Dec 1996 | A |
| 5598457 | Foladare et al. | Jan 1997 | A |
| 5867495 | Elliott et al. | Feb 1999 | A |
| 5934181 | Adamczewski | Aug 1999 | A |
| 5978465 | Corduroy et al. | Nov 1999 | A |
| 6026440 | Shrader et al. | Feb 2000 | A |
| 6034946 | Roginsky et al. | Mar 2000 | A |
| 6094681 | Shaffer et al. | Jul 2000 | A |
| 6138143 | Gigliotti et al. | Oct 2000 | A |
| 6185565 | Meubus et al. | Feb 2001 | B1 |
| 6192123 | Grunsted et al. | Feb 2001 | B1 |
| 6206564 | Adamczewski | Mar 2001 | B1 |
| 6223287 | Douglas et al. | Apr 2001 | B1 |
| 6232979 | Shochet | May 2001 | B1 |
| 6269336 | Ladd et al. | Jul 2001 | B1 |
| 6317137 | Rosasco | Nov 2001 | B1 |
| 6363065 | Thornton et al. | Mar 2002 | B1 |
| 6373836 | Deryugin et al. | Apr 2002 | B1 |
| 6425012 | Trovato et al. | Jul 2002 | B1 |
| 6426995 | Kim et al. | Jul 2002 | B1 |
| 6430175 | Echols et al. | Aug 2002 | B1 |
| 6434528 | Sanders | Aug 2002 | B1 |
| 6445694 | Swartz | Sep 2002 | B1 |
| 6445776 | Shank et al. | Sep 2002 | B1 |
| 6459913 | Cloutier | Oct 2002 | B2 |
| 6463414 | Su et al. | Oct 2002 | B1 |
| 6493558 | Bernhart et al. | Dec 2002 | B1 |
| 6496500 | Nance et al. | Dec 2002 | B2 |
| 6501739 | Cohen | Dec 2002 | B1 |
| 6501832 | Saylor et al. | Dec 2002 | B1 |
| 6507875 | Mellen-Garnett et al. | Jan 2003 | B1 |
| 6571245 | Huang et al. | May 2003 | B2 |
| 6574216 | Farris et al. | Jun 2003 | B1 |
| 6577721 | Vainio et al. | Jun 2003 | B1 |
| 6600736 | Ball et al. | Jul 2003 | B1 |
| 6606596 | Zirngibl et al. | Aug 2003 | B1 |
| 6614783 | Sonesh et al. | Sep 2003 | B1 |
| 6625258 | Ram et al. | Sep 2003 | B1 |
| 6625576 | Kochanski et al. | Sep 2003 | B2 |
| 6636504 | Albers et al. | Oct 2003 | B1 |
| 6662231 | Drosset et al. | Dec 2003 | B1 |
| 6704785 | Koo et al. | Mar 2004 | B1 |
| 6707889 | Saylor et al. | Mar 2004 | B1 |
| 6711129 | Bauer et al. | Mar 2004 | B1 |
| 6711249 | Weissman et al. | Mar 2004 | B2 |
| 6738738 | Henton | May 2004 | B2 |
| 6757365 | Bogard | Jun 2004 | B1 |
| 6765997 | Zirngibl et al. | Jul 2004 | B1 |
| 6768788 | Langseth et al. | Jul 2004 | B1 |
| 6771955 | Imura et al. | Aug 2004 | B2 |
| 6778653 | Kallas et al. | Aug 2004 | B1 |
| 6785266 | Swartz | Aug 2004 | B2 |
| 6788768 | Saylor et al. | Sep 2004 | B1 |
| 6792086 | Saylor et al. | Sep 2004 | B1 |
| 6792093 | Barak et al. | Sep 2004 | B2 |
| 6798867 | Zirngibl et al. | Sep 2004 | B1 |
| 6807529 | Johnson et al. | Oct 2004 | B2 |
| 6807574 | Partovi et al. | Oct 2004 | B1 |
| 6819667 | Brusilovsky et al. | Nov 2004 | B1 |
| 6820260 | Flockhart et al. | Nov 2004 | B1 |
| 6829334 | Zirngibl et al. | Dec 2004 | B1 |
| 6831966 | Tegan et al. | Dec 2004 | B1 |
| 6834265 | Balasuriya | Dec 2004 | B2 |
| 6836537 | Zirngibl et al. | Dec 2004 | B1 |
| 6842767 | Partovi et al. | Jan 2005 | B1 |
| 6850603 | Eberle et al. | Feb 2005 | B1 |
| 6870830 | Schuster et al. | Mar 2005 | B1 |
| 6873952 | Bailey et al. | Mar 2005 | B1 |
| 6874084 | Dobner et al. | Mar 2005 | B1 |
| 6885737 | Gao et al. | Apr 2005 | B1 |
| 6888929 | Saylor et al. | May 2005 | B1 |
| 6895084 | Saylor et al. | May 2005 | B1 |
| 6898567 | Balasuriya | May 2005 | B2 |
| 6912581 | Johnson et al. | Jun 2005 | B2 |
| 6922411 | Taylor | Jul 2005 | B1 |
| 6928469 | Duursma et al. | Aug 2005 | B1 |
| 6931405 | El-shimi et al. | Aug 2005 | B2 |
| 6937699 | Schuster et al. | Aug 2005 | B1 |
| 6940953 | Eberle et al. | Sep 2005 | B1 |
| 6941268 | Porter et al. | Sep 2005 | B2 |
| 6947417 | Laursen et al. | Sep 2005 | B2 |
| 6947988 | Saleh et al. | Sep 2005 | B1 |
| 6961330 | Cattan et al. | Nov 2005 | B1 |
| 6964012 | Zirngibl et al. | Nov 2005 | B1 |
| 6970915 | Partovi et al. | Nov 2005 | B1 |
| 6977992 | Zirngibl et al. | Dec 2005 | B2 |
| 6981041 | Araujo et al. | Dec 2005 | B2 |
| 6985862 | Strom et al. | Jan 2006 | B2 |
| 6999576 | Sacra | Feb 2006 | B2 |
| 7003464 | Ferrans et al. | Feb 2006 | B2 |
| 7006606 | Cohen et al. | Feb 2006 | B1 |
| 7010586 | Allavarpu et al. | Mar 2006 | B1 |
| 7020685 | Chen et al. | Mar 2006 | B1 |
| 7039165 | Saylor et al. | May 2006 | B1 |
| 7058042 | Bontempi et al. | Jun 2006 | B2 |
| 7058181 | Wright et al. | Jun 2006 | B2 |
| 7062709 | Cheung | Jun 2006 | B2 |
| 7065637 | Nanja | Jun 2006 | B1 |
| 7076037 | Gonen et al. | Jul 2006 | B1 |
| 7076428 | Anastasakos et al. | Jul 2006 | B2 |
| 7089310 | Ellerman et al. | Aug 2006 | B1 |
| 7099442 | Da Palma et al. | Aug 2006 | B2 |
| 7103003 | Brueckheimer et al. | Sep 2006 | B2 |
| 7103171 | Annadata et al. | Sep 2006 | B1 |
| 7106844 | Holland | Sep 2006 | B1 |
| 7111163 | Haney | Sep 2006 | B1 |
| 7136932 | Schneider | Nov 2006 | B1 |
| 7140004 | Kunins et al. | Nov 2006 | B1 |
| 7143039 | Stifelman et al. | Nov 2006 | B1 |
| 7197331 | Anastasakos et al. | Mar 2007 | B2 |
| 7197461 | Eberle et al. | Mar 2007 | B1 |
| 7197462 | Takagi et al. | Mar 2007 | B2 |
| 7197544 | Wang et al. | Mar 2007 | B2 |
| D540074 | Peters | Apr 2007 | S |
| 7225232 | Elberse | May 2007 | B2 |
| 7227849 | Rasanen | Jun 2007 | B1 |
| 7245611 | Narasimhan et al. | Jul 2007 | B2 |
| 7260208 | Cavalcanti | Aug 2007 | B2 |
| 7266181 | Zirngibl et al. | Sep 2007 | B1 |
| 7269557 | Bailey et al. | Sep 2007 | B1 |
| 7272212 | Eberle et al. | Sep 2007 | B2 |
| 7272564 | Phillips et al. | Sep 2007 | B2 |
| 7277851 | Henton | Oct 2007 | B1 |
| 7283515 | Fowler | Oct 2007 | B2 |
| 7283519 | Girard | Oct 2007 | B2 |
| 7286521 | Jackson et al. | Oct 2007 | B1 |
| 7287248 | Adeeb | Oct 2007 | B1 |
| 7289453 | Riedel et al. | Oct 2007 | B2 |
| 7296739 | Mo et al. | Nov 2007 | B1 |
| 7298732 | Cho | Nov 2007 | B2 |
| 7298834 | Homeier et al. | Nov 2007 | B1 |
| 7308085 | Weissman | Dec 2007 | B2 |
| 7308408 | Stifelman et al. | Dec 2007 | B1 |
| 7324633 | Gao et al. | Jan 2008 | B2 |
| 7324942 | Mahowald et al. | Jan 2008 | B1 |
| 7328263 | Sadjadi | Feb 2008 | B1 |
| 7330463 | Bradd et al. | Feb 2008 | B1 |
| 7330890 | Partovi et al. | Feb 2008 | B1 |
| 7340040 | Saylor et al. | Mar 2008 | B1 |
| 7349714 | Lee et al. | Mar 2008 | B2 |
| 7369865 | Gabriel et al. | May 2008 | B2 |
| 7370329 | Kumar et al. | May 2008 | B2 |
| 7373660 | Guichard et al. | May 2008 | B1 |
| 7376223 | Taylor et al. | May 2008 | B2 |
| 7376733 | Partovi Hadi et al. | May 2008 | B2 |
| 7376740 | Porter et al. | May 2008 | B1 |
| 7412525 | Cafarella et al. | Aug 2008 | B2 |
| 7418090 | Reding et al. | Aug 2008 | B2 |
| 7428302 | Zirngibl et al. | Sep 2008 | B2 |
| 7440898 | Eberle et al. | Oct 2008 | B1 |
| 7447299 | Partovi et al. | Nov 2008 | B1 |
| 7454459 | Kapoor et al. | Nov 2008 | B1 |
| 7457249 | Baldwin et al. | Nov 2008 | B2 |
| 7457397 | Saylor et al. | Nov 2008 | B1 |
| 7473872 | Takimoto | Jan 2009 | B2 |
| 7486780 | Zirngibl et al. | Feb 2009 | B2 |
| 7496054 | Taylor | Feb 2009 | B2 |
| 7496188 | Saha et al. | Feb 2009 | B2 |
| 7496651 | Joshi | Feb 2009 | B1 |
| 7500249 | Kampe et al. | Mar 2009 | B2 |
| 7505951 | Thompson et al. | Mar 2009 | B2 |
| 7519359 | Chiarulli et al. | Apr 2009 | B2 |
| 7522711 | Stein et al. | Apr 2009 | B1 |
| 7536454 | Balasuriya | May 2009 | B2 |
| 7542761 | Sarkar | Jun 2009 | B2 |
| 7552054 | Stifelman et al. | Jun 2009 | B1 |
| 7571226 | Partovi et al. | Aug 2009 | B1 |
| 7606868 | Le et al. | Oct 2009 | B1 |
| 7613287 | Stifelman et al. | Nov 2009 | B1 |
| 7623648 | Oppenheim et al. | Nov 2009 | B1 |
| 7630900 | Strom | Dec 2009 | B1 |
| 7631310 | Henzinger | Dec 2009 | B1 |
| 7644000 | Strom | Jan 2010 | B1 |
| 7657433 | Chang | Feb 2010 | B1 |
| 7657434 | Thompson et al. | Feb 2010 | B2 |
| 7668157 | Weintraub et al. | Feb 2010 | B2 |
| 7672275 | Yajnik et al. | Mar 2010 | B2 |
| 7672295 | Andhare et al. | Mar 2010 | B1 |
| 7675857 | Chesson | Mar 2010 | B1 |
| 7676221 | Roundtree et al. | Mar 2010 | B2 |
| 7685280 | Berry et al. | Mar 2010 | B2 |
| 7685298 | Day et al. | Mar 2010 | B2 |
| 7715547 | Ibbotson et al. | May 2010 | B2 |
| 7716293 | Kasuga et al. | May 2010 | B2 |
| 7742499 | Erskine et al. | Jun 2010 | B1 |
| 7779065 | Gupta et al. | Aug 2010 | B2 |
| 7809125 | Brunson et al. | Oct 2010 | B2 |
| 7809791 | Schwartz et al. | Oct 2010 | B2 |
| 7875836 | Imura et al. | Jan 2011 | B2 |
| 7882253 | Pardo-Castellote et al. | Feb 2011 | B2 |
| 7920866 | Bosch et al. | Apr 2011 | B2 |
| 7926099 | Chakravarty et al. | Apr 2011 | B1 |
| 7929562 | Petrovykh | Apr 2011 | B2 |
| 7936867 | Hill et al. | May 2011 | B1 |
| 7949111 | Harlow et al. | May 2011 | B2 |
| 7962644 | Ezerzer et al. | Jun 2011 | B1 |
| 7979555 | Rothstein et al. | Jul 2011 | B2 |
| 7992120 | Wang et al. | Aug 2011 | B1 |
| 8023425 | Raleigh | Sep 2011 | B2 |
| 8024785 | Andress et al. | Sep 2011 | B2 |
| 8045689 | Provenzale et al. | Oct 2011 | B2 |
| 8046378 | Zhuge et al. | Oct 2011 | B1 |
| 8046823 | Begen et al. | Oct 2011 | B1 |
| 8069096 | Ballaro et al. | Nov 2011 | B1 |
| 8078483 | Hirose et al. | Dec 2011 | B1 |
| 8081744 | Sylvain | Dec 2011 | B2 |
| 8081958 | Soderstrom et al. | Dec 2011 | B2 |
| 8103725 | Gupta et al. | Jan 2012 | B2 |
| 8126128 | Hicks, III et al. | Feb 2012 | B1 |
| 8126129 | Mcguire | Feb 2012 | B1 |
| 8130750 | Hester | Mar 2012 | B2 |
| 8130917 | Helbling et al. | Mar 2012 | B2 |
| 8139730 | Da Palma et al. | Mar 2012 | B2 |
| 8145212 | Lopresti et al. | Mar 2012 | B2 |
| 8149716 | Ramanathan et al. | Apr 2012 | B2 |
| 8150918 | Edelman et al. | Apr 2012 | B1 |
| 8156213 | Deng et al. | Apr 2012 | B1 |
| 8165116 | Ku et al. | Apr 2012 | B2 |
| 8166185 | Samuel et al. | Apr 2012 | B2 |
| 8169936 | Koren et al. | May 2012 | B2 |
| 8175007 | Jain et al. | May 2012 | B2 |
| 8185619 | Maiocco et al. | May 2012 | B1 |
| 8196133 | Kakumani et al. | Jun 2012 | B2 |
| 8204479 | Vendrow et al. | Jun 2012 | B2 |
| 8214868 | Hamilton et al. | Jul 2012 | B2 |
| 8218457 | Malhotra et al. | Jul 2012 | B2 |
| 8233611 | Zettner | Jul 2012 | B1 |
| 8238533 | Blackwell et al. | Aug 2012 | B2 |
| 8243889 | Taylor et al. | Aug 2012 | B2 |
| 8249552 | Gailloux et al. | Aug 2012 | B1 |
| 8266327 | Kumar et al. | Sep 2012 | B2 |
| 8295272 | Boni et al. | Oct 2012 | B2 |
| 8301117 | Keast et al. | Oct 2012 | B2 |
| 8306021 | Lawson et al. | Nov 2012 | B2 |
| 8315198 | Corneille et al. | Nov 2012 | B2 |
| 8315369 | Lawson et al. | Nov 2012 | B2 |
| 8315620 | Williamson et al. | Nov 2012 | B1 |
| 8319816 | Swanson et al. | Nov 2012 | B1 |
| 8326805 | Arous et al. | Dec 2012 | B1 |
| 8335852 | Hokimoto | Dec 2012 | B2 |
| 8346630 | Mckeown | Jan 2013 | B1 |
| 8355394 | Taylor et al. | Jan 2013 | B2 |
| 8411669 | Chen et al. | Apr 2013 | B2 |
| 8413247 | Hudis et al. | Apr 2013 | B2 |
| 8417817 | Jacobs | Apr 2013 | B1 |
| 8429827 | Wetzel | Apr 2013 | B1 |
| 8438315 | Tao et al. | May 2013 | B1 |
| 8462670 | Chien | Jun 2013 | B2 |
| 8467502 | Sureka et al. | Jun 2013 | B2 |
| 8477926 | Jasper et al. | Jul 2013 | B2 |
| 8503639 | Reding et al. | Aug 2013 | B2 |
| 8503650 | Reding et al. | Aug 2013 | B2 |
| 8504818 | Rao et al. | Aug 2013 | B2 |
| 8509068 | Begall et al. | Aug 2013 | B2 |
| 8532686 | Schmidt et al. | Sep 2013 | B2 |
| 8533857 | Tuchman et al. | Sep 2013 | B2 |
| 8542805 | Agranovsky et al. | Sep 2013 | B2 |
| 8543665 | Ansari et al. | Sep 2013 | B2 |
| 8547962 | Ramachandran et al. | Oct 2013 | B2 |
| 8549047 | Beechuk et al. | Oct 2013 | B2 |
| 8565117 | Hilt et al. | Oct 2013 | B2 |
| 8572391 | Golan et al. | Oct 2013 | B2 |
| 8576712 | Sabat et al. | Nov 2013 | B2 |
| 8577803 | Chatterjee et al. | Nov 2013 | B2 |
| 8582450 | Robesky | Nov 2013 | B1 |
| 8582737 | Lawson et al. | Nov 2013 | B2 |
| 8594626 | Woodson et al. | Nov 2013 | B1 |
| 8601136 | Fahlgren et al. | Dec 2013 | B1 |
| 8611338 | Lawson et al. | Dec 2013 | B2 |
| 8613102 | Nath | Dec 2013 | B2 |
| 8621598 | Lai et al. | Dec 2013 | B2 |
| 8649268 | Lawson et al. | Feb 2014 | B2 |
| 8656452 | Li et al. | Feb 2014 | B2 |
| 8667056 | Proulx et al. | Mar 2014 | B1 |
| 8675493 | Buddhikot et al. | Mar 2014 | B2 |
| 8688147 | Nguyen et al. | Apr 2014 | B2 |
| 8695077 | Gerhard et al. | Apr 2014 | B1 |
| 8713693 | Shanabrook et al. | Apr 2014 | B2 |
| 8728656 | Takahashi et al. | May 2014 | B2 |
| 8751801 | Harris et al. | Jun 2014 | B2 |
| 8755376 | Lawson et al. | Jun 2014 | B2 |
| 8767925 | Sureka et al. | Jul 2014 | B2 |
| 8781975 | Bennett et al. | Jul 2014 | B2 |
| 8797920 | Parreira | Aug 2014 | B2 |
| 8806024 | Toba Francis et al. | Aug 2014 | B1 |
| 8819133 | Wang | Aug 2014 | B2 |
| 8825746 | Ravichandran et al. | Sep 2014 | B2 |
| 8837465 | Lawson et al. | Sep 2014 | B2 |
| 8838707 | Lawson et al. | Sep 2014 | B2 |
| 8843596 | Goel et al. | Sep 2014 | B2 |
| 8855271 | Brock et al. | Oct 2014 | B2 |
| 8861510 | Fritz | Oct 2014 | B1 |
| 8879547 | Maes | Nov 2014 | B2 |
| 8903938 | Vermeulen et al. | Dec 2014 | B2 |
| 8918848 | Sharma et al. | Dec 2014 | B2 |
| 8924489 | Bleau et al. | Dec 2014 | B2 |
| 8938053 | Cooke et al. | Jan 2015 | B2 |
| 8948356 | Nowack et al. | Feb 2015 | B2 |
| 8954591 | Ganesan et al. | Feb 2015 | B2 |
| 8964726 | Lawson et al. | Feb 2015 | B2 |
| 8990610 | Bostick et al. | Mar 2015 | B2 |
| 9014664 | Kim et al. | Apr 2015 | B2 |
| 9015702 | Bhat | Apr 2015 | B2 |
| 9031223 | Smith et al. | May 2015 | B2 |
| 9032204 | Byrd et al. | May 2015 | B2 |
| 9071677 | Aggarwal et al. | Jun 2015 | B2 |
| 9137127 | Nowack et al. | Sep 2015 | B2 |
| 9141682 | Adoc, Jr. et al. | Sep 2015 | B1 |
| 9161296 | Parsons et al. | Oct 2015 | B2 |
| 9177007 | Winters et al. | Nov 2015 | B2 |
| 9204281 | Ramprasad et al. | Dec 2015 | B2 |
| 9210275 | Lawson et al. | Dec 2015 | B2 |
| 9274858 | Milliron et al. | Mar 2016 | B2 |
| 9306982 | Lawson et al. | Apr 2016 | B2 |
| 9307094 | Nowack et al. | Apr 2016 | B2 |
| 9325624 | Malatack et al. | Apr 2016 | B2 |
| 9338190 | Eng et al. | May 2016 | B2 |
| 9344573 | Wolthuis et al. | May 2016 | B2 |
| 9356916 | Kravitz et al. | May 2016 | B2 |
| 9378337 | Kuhr | Jun 2016 | B2 |
| 9398622 | Lawson et al. | Jul 2016 | B2 |
| 9456008 | Lawson et al. | Sep 2016 | B2 |
| 9456339 | Hildner et al. | Sep 2016 | B1 |
| 9460169 | Hinton et al. | Oct 2016 | B2 |
| 9596274 | Lawson et al. | Mar 2017 | B2 |
| 9628624 | Wolthuis et al. | Apr 2017 | B2 |
| 9632875 | Raichstein et al. | Apr 2017 | B2 |
| 9634995 | Binder | Apr 2017 | B2 |
| 9959151 | Milliron et al. | May 2018 | B2 |
| 10176026 | Milliron et al. | Jan 2019 | B2 |
| 20010038624 | Greenberg et al. | Nov 2001 | A1 |
| 20010043684 | Guedalia et al. | Nov 2001 | A1 |
| 20010051996 | Cooper et al. | Dec 2001 | A1 |
| 20020006124 | Jimenez et al. | Jan 2002 | A1 |
| 20020006125 | Josse et al. | Jan 2002 | A1 |
| 20020006193 | Rodenbusch et al. | Jan 2002 | A1 |
| 20020025819 | Cetusic et al. | Feb 2002 | A1 |
| 20020057777 | Saito et al. | May 2002 | A1 |
| 20020064267 | Martin et al. | May 2002 | A1 |
| 20020067823 | Walker et al. | Jun 2002 | A1 |
| 20020077833 | Arons et al. | Jun 2002 | A1 |
| 20020126813 | Partovi et al. | Sep 2002 | A1 |
| 20020133587 | Ensel et al. | Sep 2002 | A1 |
| 20020136391 | Armstrong et al. | Sep 2002 | A1 |
| 20020165957 | Devoe et al. | Nov 2002 | A1 |
| 20020176378 | Hamilton et al. | Nov 2002 | A1 |
| 20020176404 | Girard | Nov 2002 | A1 |
| 20020184361 | Eden | Dec 2002 | A1 |
| 20020198941 | Gavrilescu et al. | Dec 2002 | A1 |
| 20030006137 | Wei et al. | Jan 2003 | A1 |
| 20030012356 | Zino et al. | Jan 2003 | A1 |
| 20030014665 | Anderson et al. | Jan 2003 | A1 |
| 20030018830 | Chen et al. | Jan 2003 | A1 |
| 20030023672 | Vaysman | Jan 2003 | A1 |
| 20030026426 | Wright et al. | Feb 2003 | A1 |
| 20030046366 | Pardikar et al. | Mar 2003 | A1 |
| 20030051037 | Sundaram et al. | Mar 2003 | A1 |
| 20030058884 | Kallner et al. | Mar 2003 | A1 |
| 20030059020 | Meyerson et al. | Mar 2003 | A1 |
| 20030060188 | Gidron et al. | Mar 2003 | A1 |
| 20030061317 | Brown et al. | Mar 2003 | A1 |
| 20030061404 | Atwal et al. | Mar 2003 | A1 |
| 20030088421 | Maes et al. | May 2003 | A1 |
| 20030097330 | Hillmer et al. | May 2003 | A1 |
| 20030097447 | Johnston | May 2003 | A1 |
| 20030097639 | Niyogi et al. | May 2003 | A1 |
| 20030103620 | Brown et al. | Jun 2003 | A1 |
| 20030123640 | Roelle et al. | Jul 2003 | A1 |
| 20030149721 | Alfonso-nogueiro et al. | Aug 2003 | A1 |
| 20030162506 | Toshimitsu et al. | Aug 2003 | A1 |
| 20030195950 | Huang et al. | Oct 2003 | A1 |
| 20030195990 | Greenblat et al. | Oct 2003 | A1 |
| 20030196076 | Zabarski et al. | Oct 2003 | A1 |
| 20030204616 | Billhartz et al. | Oct 2003 | A1 |
| 20030211842 | Kempf et al. | Nov 2003 | A1 |
| 20030231647 | Petrovykh | Dec 2003 | A1 |
| 20030233276 | Pearlman et al. | Dec 2003 | A1 |
| 20040008635 | Nelson et al. | Jan 2004 | A1 |
| 20040011690 | Marfino et al. | Jan 2004 | A1 |
| 20040044953 | Watkins et al. | Mar 2004 | A1 |
| 20040052349 | Creamer et al. | Mar 2004 | A1 |
| 20040071275 | Bowater et al. | Apr 2004 | A1 |
| 20040101122 | Da Palma et al. | May 2004 | A1 |
| 20040102182 | Reith et al. | May 2004 | A1 |
| 20040117788 | Karaoguz et al. | Jun 2004 | A1 |
| 20040136324 | Steinberg et al. | Jul 2004 | A1 |
| 20040165569 | Sweatman et al. | Aug 2004 | A1 |
| 20040172482 | Weissman et al. | Sep 2004 | A1 |
| 20040199572 | Hunt et al. | Oct 2004 | A1 |
| 20040205101 | Radhakrishnan | Oct 2004 | A1 |
| 20040205689 | Ellens et al. | Oct 2004 | A1 |
| 20040213400 | Golitsin et al. | Oct 2004 | A1 |
| 20040216058 | Chavers et al. | Oct 2004 | A1 |
| 20040218748 | Fisher | Nov 2004 | A1 |
| 20040228469 | Andrews et al. | Nov 2004 | A1 |
| 20040236696 | Aoki et al. | Nov 2004 | A1 |
| 20040240649 | Goel | Dec 2004 | A1 |
| 20050005109 | Castaldi et al. | Jan 2005 | A1 |
| 20050005200 | Matena et al. | Jan 2005 | A1 |
| 20050010483 | Ling | Jan 2005 | A1 |
| 20050015505 | Kruis et al. | Jan 2005 | A1 |
| 20050021626 | Prajapat et al. | Jan 2005 | A1 |
| 20050025303 | Hostetler, Jr. | Feb 2005 | A1 |
| 20050038772 | Colrain | Feb 2005 | A1 |
| 20050043952 | Sharma et al. | Feb 2005 | A1 |
| 20050047579 | Salame | Mar 2005 | A1 |
| 20050060411 | Coulombe et al. | Mar 2005 | A1 |
| 20050083907 | Fishler | Apr 2005 | A1 |
| 20050091336 | Dehamer et al. | Apr 2005 | A1 |
| 20050091572 | Gavrilescu et al. | Apr 2005 | A1 |
| 20050108770 | Karaoguz et al. | May 2005 | A1 |
| 20050125251 | Berger et al. | Jun 2005 | A1 |
| 20050125739 | Thompson et al. | Jun 2005 | A1 |
| 20050128961 | Miloslavsky et al. | Jun 2005 | A1 |
| 20050135578 | Ress et al. | Jun 2005 | A1 |
| 20050138111 | Aton | Jun 2005 | A1 |
| 20050141500 | Bhandari et al. | Jun 2005 | A1 |
| 20050147088 | Bao et al. | Jul 2005 | A1 |
| 20050177635 | Schmidt et al. | Aug 2005 | A1 |
| 20050181835 | Lau et al. | Aug 2005 | A1 |
| 20050198292 | Duursma et al. | Sep 2005 | A1 |
| 20050228680 | Malik | Oct 2005 | A1 |
| 20050238153 | Chevalier | Oct 2005 | A1 |
| 20050240659 | Taylor | Oct 2005 | A1 |
| 20050243977 | Creamer et al. | Nov 2005 | A1 |
| 20050246176 | Creamer et al. | Nov 2005 | A1 |
| 20050286496 | Malhotra et al. | Dec 2005 | A1 |
| 20050289222 | Sahim | Dec 2005 | A1 |
| 20060008065 | Longman et al. | Jan 2006 | A1 |
| 20060008073 | Yoshizawa et al. | Jan 2006 | A1 |
| 20060008256 | Khedouri et al. | Jan 2006 | A1 |
| 20060015467 | Morken et al. | Jan 2006 | A1 |
| 20060021004 | Moran et al. | Jan 2006 | A1 |
| 20060023676 | Whitmore et al. | Feb 2006 | A1 |
| 20060047666 | Bedi et al. | Mar 2006 | A1 |
| 20060067506 | Flockhart et al. | Mar 2006 | A1 |
| 20060080415 | Tu | Apr 2006 | A1 |
| 20060098624 | Morgan et al. | May 2006 | A1 |
| 20060129638 | Deakin | Jun 2006 | A1 |
| 20060143007 | Koh et al. | Jun 2006 | A1 |
| 20060146792 | Ramachandran et al. | Jul 2006 | A1 |
| 20060146802 | Baldwin et al. | Jul 2006 | A1 |
| 20060168334 | Potti et al. | Jul 2006 | A1 |
| 20060203979 | Jennings | Sep 2006 | A1 |
| 20060209695 | Archer, Jr. et al. | Sep 2006 | A1 |
| 20060212865 | Vincent et al. | Sep 2006 | A1 |
| 20060215824 | Mitby et al. | Sep 2006 | A1 |
| 20060217823 | Hussey | Sep 2006 | A1 |
| 20060217978 | Mitby et al. | Sep 2006 | A1 |
| 20060222166 | Ramakrishna et al. | Oct 2006 | A1 |
| 20060235715 | Abrams et al. | Oct 2006 | A1 |
| 20060256816 | Yarlagadda et al. | Nov 2006 | A1 |
| 20060262915 | Marascio et al. | Nov 2006 | A1 |
| 20060270386 | Yu et al. | Nov 2006 | A1 |
| 20060285489 | Francisco et al. | Dec 2006 | A1 |
| 20070002744 | Mewhinney et al. | Jan 2007 | A1 |
| 20070036143 | Alt et al. | Feb 2007 | A1 |
| 20070038499 | Margulies et al. | Feb 2007 | A1 |
| 20070043681 | Morgan et al. | Feb 2007 | A1 |
| 20070050306 | McQueen | Mar 2007 | A1 |
| 20070064672 | Raghav et al. | Mar 2007 | A1 |
| 20070070906 | Thakur | Mar 2007 | A1 |
| 20070070980 | Phelps et al. | Mar 2007 | A1 |
| 20070071223 | Lee et al. | Mar 2007 | A1 |
| 20070074174 | Thornton | Mar 2007 | A1 |
| 20070088836 | Tai et al. | Apr 2007 | A1 |
| 20070091907 | Seshadri et al. | Apr 2007 | A1 |
| 20070107048 | Halls et al. | May 2007 | A1 |
| 20070112574 | Greene | May 2007 | A1 |
| 20070116191 | Bermudez et al. | May 2007 | A1 |
| 20070121651 | Casey et al. | May 2007 | A1 |
| 20070127691 | Lert | Jun 2007 | A1 |
| 20070127703 | Siminoff | Jun 2007 | A1 |
| 20070130260 | Weintraub et al. | Jun 2007 | A1 |
| 20070133771 | Stifelman et al. | Jun 2007 | A1 |
| 20070147351 | Dietrich et al. | Jun 2007 | A1 |
| 20070149166 | Turcotte et al. | Jun 2007 | A1 |
| 20070153711 | Dykas et al. | Jul 2007 | A1 |
| 20070167170 | Fitchett et al. | Jul 2007 | A1 |
| 20070192629 | Saito | Aug 2007 | A1 |
| 20070201448 | Baird et al. | Aug 2007 | A1 |
| 20070208862 | Fox et al. | Sep 2007 | A1 |
| 20070232284 | Mason et al. | Oct 2007 | A1 |
| 20070239761 | Baio et al. | Oct 2007 | A1 |
| 20070242626 | Altberg et al. | Oct 2007 | A1 |
| 20070255828 | Paradise | Nov 2007 | A1 |
| 20070265073 | Novi et al. | Nov 2007 | A1 |
| 20070286180 | Marquette et al. | Dec 2007 | A1 |
| 20070291734 | Bhatia et al. | Dec 2007 | A1 |
| 20070291905 | Halliday et al. | Dec 2007 | A1 |
| 20070293200 | Roundtree et al. | Dec 2007 | A1 |
| 20070295803 | Levine et al. | Dec 2007 | A1 |
| 20080005275 | Overton et al. | Jan 2008 | A1 |
| 20080025320 | Bangalore et al. | Jan 2008 | A1 |
| 20080037715 | Prozeniuk et al. | Feb 2008 | A1 |
| 20080037746 | Dufrene et al. | Feb 2008 | A1 |
| 20080040484 | Yardley | Feb 2008 | A1 |
| 20080049617 | Grice et al. | Feb 2008 | A1 |
| 20080052395 | Wright et al. | Feb 2008 | A1 |
| 20080091843 | Kulkarni | Apr 2008 | A1 |
| 20080101571 | Harlow et al. | May 2008 | A1 |
| 20080104348 | Kabzinski et al. | May 2008 | A1 |
| 20080120702 | Hokimoto | May 2008 | A1 |
| 20080123559 | Haviv et al. | May 2008 | A1 |
| 20080134049 | Gupta et al. | Jun 2008 | A1 |
| 20080139166 | Agarwal et al. | Jun 2008 | A1 |
| 20080146268 | Gandhi et al. | Jun 2008 | A1 |
| 20080152101 | Griggs | Jun 2008 | A1 |
| 20080154601 | Stifelman et al. | Jun 2008 | A1 |
| 20080155029 | Helbling et al. | Jun 2008 | A1 |
| 20080162482 | Ahern et al. | Jul 2008 | A1 |
| 20080165708 | Moore et al. | Jul 2008 | A1 |
| 20080172404 | Cohen | Jul 2008 | A1 |
| 20080177883 | Hanai et al. | Jul 2008 | A1 |
| 20080192736 | Jabri et al. | Aug 2008 | A1 |
| 20080201426 | Darcie | Aug 2008 | A1 |
| 20080209050 | Li | Aug 2008 | A1 |
| 20080212945 | Khedouri et al. | Sep 2008 | A1 |
| 20080222656 | Lyman | Sep 2008 | A1 |
| 20080229421 | Hudis et al. | Sep 2008 | A1 |
| 20080232574 | Baluja et al. | Sep 2008 | A1 |
| 20080235230 | Maes | Sep 2008 | A1 |
| 20080256224 | Kaji et al. | Oct 2008 | A1 |
| 20080275741 | Loeffen | Nov 2008 | A1 |
| 20080307436 | Hamilton | Dec 2008 | A1 |
| 20080310599 | Purnadi et al. | Dec 2008 | A1 |
| 20080313318 | Vermeulen et al. | Dec 2008 | A1 |
| 20080316931 | Qiu et al. | Dec 2008 | A1 |
| 20080317222 | Griggs et al. | Dec 2008 | A1 |
| 20080317232 | Couse et al. | Dec 2008 | A1 |
| 20080317233 | Rey et al. | Dec 2008 | A1 |
| 20090046838 | Andreasson | Feb 2009 | A1 |
| 20090052437 | Taylor et al. | Feb 2009 | A1 |
| 20090052641 | Taylor et al. | Feb 2009 | A1 |
| 20090059894 | Jackson et al. | Mar 2009 | A1 |
| 20090063502 | Coimbatore et al. | Mar 2009 | A1 |
| 20090074159 | Goldfarb et al. | Mar 2009 | A1 |
| 20090075684 | Cheng et al. | Mar 2009 | A1 |
| 20090083155 | Tudor et al. | Mar 2009 | A1 |
| 20090089165 | Sweeney | Apr 2009 | A1 |
| 20090089352 | Davis et al. | Apr 2009 | A1 |
| 20090089699 | Saha et al. | Apr 2009 | A1 |
| 20090092674 | Ingram et al. | Apr 2009 | A1 |
| 20090093250 | Jackson et al. | Apr 2009 | A1 |
| 20090094674 | Schwartz et al. | Apr 2009 | A1 |
| 20090125608 | Werth et al. | May 2009 | A1 |
| 20090129573 | Gavan et al. | May 2009 | A1 |
| 20090136011 | Goel | May 2009 | A1 |
| 20090170496 | Bourque | Jul 2009 | A1 |
| 20090171659 | Pearce et al. | Jul 2009 | A1 |
| 20090171669 | Engelsma et al. | Jul 2009 | A1 |
| 20090171752 | Galvin et al. | Jul 2009 | A1 |
| 20090182896 | Patterson et al. | Jul 2009 | A1 |
| 20090193433 | Maes | Jul 2009 | A1 |
| 20090216835 | Jain et al. | Aug 2009 | A1 |
| 20090217293 | Wolber et al. | Aug 2009 | A1 |
| 20090220057 | Waters | Sep 2009 | A1 |
| 20090221310 | Chen et al. | Sep 2009 | A1 |
| 20090222341 | Belwadi et al. | Sep 2009 | A1 |
| 20090225748 | Taylor | Sep 2009 | A1 |
| 20090225763 | Forsberg et al. | Sep 2009 | A1 |
| 20090228868 | Drukman et al. | Sep 2009 | A1 |
| 20090232289 | Drucker et al. | Sep 2009 | A1 |
| 20090234965 | Viveganandhan et al. | Sep 2009 | A1 |
| 20090235349 | Lai et al. | Sep 2009 | A1 |
| 20090241135 | Wong et al. | Sep 2009 | A1 |
| 20090252159 | Lawson et al. | Oct 2009 | A1 |
| 20090262725 | Chen et al. | Oct 2009 | A1 |
| 20090276771 | Nickolov et al. | Nov 2009 | A1 |
| 20090288012 | Hertel et al. | Nov 2009 | A1 |
| 20090288165 | Qiu et al. | Nov 2009 | A1 |
| 20090300194 | Ogasawara | Dec 2009 | A1 |
| 20090316687 | Kruppa | Dec 2009 | A1 |
| 20090318112 | Vasten | Dec 2009 | A1 |
| 20100027531 | Kurashima | Feb 2010 | A1 |
| 20100037204 | Lin et al. | Feb 2010 | A1 |
| 20100054142 | Moiso et al. | Mar 2010 | A1 |
| 20100070424 | Monk | Mar 2010 | A1 |
| 20100071053 | Ansari et al. | Mar 2010 | A1 |
| 20100082513 | Liu | Apr 2010 | A1 |
| 20100087215 | Gu et al. | Apr 2010 | A1 |
| 20100088187 | Courtney et al. | Apr 2010 | A1 |
| 20100088698 | Krishnamurthy | Apr 2010 | A1 |
| 20100094758 | Chamberlain et al. | Apr 2010 | A1 |
| 20100103845 | Ulupinar et al. | Apr 2010 | A1 |
| 20100107222 | Glasser | Apr 2010 | A1 |
| 20100115041 | Hawkins et al. | May 2010 | A1 |
| 20100138501 | Clinton et al. | Jun 2010 | A1 |
| 20100142516 | Lawson et al. | Jun 2010 | A1 |
| 20100150139 | Lawson et al. | Jun 2010 | A1 |
| 20100167689 | Sepehri-Nik et al. | Jul 2010 | A1 |
| 20100188979 | Thubert et al. | Jul 2010 | A1 |
| 20100191915 | Spencer | Jul 2010 | A1 |
| 20100208881 | Kawamura | Aug 2010 | A1 |
| 20100217837 | Ansari et al. | Aug 2010 | A1 |
| 20100217982 | Brown et al. | Aug 2010 | A1 |
| 20100232594 | Lawson et al. | Sep 2010 | A1 |
| 20100235539 | Carter et al. | Sep 2010 | A1 |
| 20100250946 | Korte et al. | Sep 2010 | A1 |
| 20100251329 | Wei | Sep 2010 | A1 |
| 20100251340 | Martin et al. | Sep 2010 | A1 |
| 20100265825 | Blair et al. | Oct 2010 | A1 |
| 20100281108 | Cohen | Nov 2010 | A1 |
| 20100291910 | Sanding et al. | Nov 2010 | A1 |
| 20100299437 | Moore | Nov 2010 | A1 |
| 20100312919 | Lee et al. | Dec 2010 | A1 |
| 20100332852 | Vembu et al. | Dec 2010 | A1 |
| 20110026516 | Roberts et al. | Feb 2011 | A1 |
| 20110029882 | Jaisinghani | Feb 2011 | A1 |
| 20110029981 | Jaisinghani | Feb 2011 | A1 |
| 20110053555 | Cai et al. | Mar 2011 | A1 |
| 20110078278 | Cui et al. | Mar 2011 | A1 |
| 20110081008 | Lawson et al. | Apr 2011 | A1 |
| 20110083069 | Paul et al. | Apr 2011 | A1 |
| 20110083179 | Lawson et al. | Apr 2011 | A1 |
| 20110093516 | Geng et al. | Apr 2011 | A1 |
| 20110096673 | Stevenson et al. | Apr 2011 | A1 |
| 20110110366 | Moore et al. | May 2011 | A1 |
| 20110131293 | Mori | Jun 2011 | A1 |
| 20110138453 | Verma et al. | Jun 2011 | A1 |
| 20110143714 | Keast et al. | Jun 2011 | A1 |
| 20110145049 | Hertel et al. | Jun 2011 | A1 |
| 20110149810 | Koren et al. | Jun 2011 | A1 |
| 20110149950 | Petit-Huguenin et al. | Jun 2011 | A1 |
| 20110151884 | Zhao | Jun 2011 | A1 |
| 20110158235 | Senga | Jun 2011 | A1 |
| 20110167172 | Roach et al. | Jul 2011 | A1 |
| 20110170505 | Rajasekar et al. | Jul 2011 | A1 |
| 20110176537 | Lawson et al. | Jul 2011 | A1 |
| 20110179126 | Wetherell et al. | Jul 2011 | A1 |
| 20110211679 | Mezhibovsky et al. | Sep 2011 | A1 |
| 20110251921 | Kassaei et al. | Oct 2011 | A1 |
| 20110253693 | Lyons et al. | Oct 2011 | A1 |
| 20110255675 | Jasper et al. | Oct 2011 | A1 |
| 20110258432 | Rao et al. | Oct 2011 | A1 |
| 20110265168 | Lucovsky et al. | Oct 2011 | A1 |
| 20110265172 | Sharma | Oct 2011 | A1 |
| 20110267985 | Wilkinson et al. | Nov 2011 | A1 |
| 20110274111 | Narasappa et al. | Nov 2011 | A1 |
| 20110276892 | Jensen-Horne et al. | Nov 2011 | A1 |
| 20110276951 | Jain | Nov 2011 | A1 |
| 20110280390 | Lawson et al. | Nov 2011 | A1 |
| 20110283259 | Lawson et al. | Nov 2011 | A1 |
| 20110289126 | Aikas et al. | Nov 2011 | A1 |
| 20110289162 | Furlong et al. | Nov 2011 | A1 |
| 20110299672 | Chiu et al. | Dec 2011 | A1 |
| 20110310902 | Xu | Dec 2011 | A1 |
| 20110313950 | Nuggehalli et al. | Dec 2011 | A1 |
| 20110320449 | Gudlavenkatasiva | Dec 2011 | A1 |
| 20110320550 | Lawson et al. | Dec 2011 | A1 |
| 20120000903 | Baarman et al. | Jan 2012 | A1 |
| 20120011274 | Moreman | Jan 2012 | A1 |
| 20120017222 | May | Jan 2012 | A1 |
| 20120023531 | Meuninck et al. | Jan 2012 | A1 |
| 20120023544 | Li et al. | Jan 2012 | A1 |
| 20120027228 | Rijken et al. | Feb 2012 | A1 |
| 20120028602 | Lisi et al. | Feb 2012 | A1 |
| 20120036574 | Heithcock et al. | Feb 2012 | A1 |
| 20120039202 | Song | Feb 2012 | A1 |
| 20120059709 | Lieberman et al. | Mar 2012 | A1 |
| 20120079066 | Li et al. | Mar 2012 | A1 |
| 20120083266 | Vanswol et al. | Apr 2012 | A1 |
| 20120089572 | Raichstein et al. | Apr 2012 | A1 |
| 20120094637 | Jeyaseelan et al. | Apr 2012 | A1 |
| 20120101952 | Raleigh et al. | Apr 2012 | A1 |
| 20120110564 | Ran et al. | May 2012 | A1 |
| 20120114112 | Rauschenberger et al. | May 2012 | A1 |
| 20120149404 | Beattie et al. | Jun 2012 | A1 |
| 20120166488 | Kaushik et al. | Jun 2012 | A1 |
| 20120170726 | Schwartz | Jul 2012 | A1 |
| 20120173610 | Bleau et al. | Jul 2012 | A1 |
| 20120174095 | Natchadalingam et al. | Jul 2012 | A1 |
| 20120179646 | Hinton et al. | Jul 2012 | A1 |
| 20120179907 | Byrd et al. | Jul 2012 | A1 |
| 20120180021 | Byrd et al. | Jul 2012 | A1 |
| 20120180029 | Hill et al. | Jul 2012 | A1 |
| 20120185561 | Klein et al. | Jul 2012 | A1 |
| 20120198004 | Watte | Aug 2012 | A1 |
| 20120201238 | Lawson et al. | Aug 2012 | A1 |
| 20120208495 | Lawson et al. | Aug 2012 | A1 |
| 20120221603 | Kothule et al. | Aug 2012 | A1 |
| 20120226579 | Ha et al. | Sep 2012 | A1 |
| 20120239757 | Firstenberg et al. | Sep 2012 | A1 |
| 20120240226 | Li | Sep 2012 | A1 |
| 20120246273 | Bornstein et al. | Sep 2012 | A1 |
| 20120254828 | Aiylam et al. | Oct 2012 | A1 |
| 20120266258 | Tuchman et al. | Oct 2012 | A1 |
| 20120281536 | Gell et al. | Nov 2012 | A1 |
| 20120288082 | Segall | Nov 2012 | A1 |
| 20120290706 | Lin et al. | Nov 2012 | A1 |
| 20120304245 | Lawson et al. | Nov 2012 | A1 |
| 20120304275 | Ji et al. | Nov 2012 | A1 |
| 20120316809 | Egolf et al. | Dec 2012 | A1 |
| 20120321058 | Eng et al. | Dec 2012 | A1 |
| 20120321070 | Smith et al. | Dec 2012 | A1 |
| 20130029629 | Lindholm et al. | Jan 2013 | A1 |
| 20130031158 | Salsburg | Jan 2013 | A1 |
| 20130031613 | Shanabrook et al. | Jan 2013 | A1 |
| 20130036476 | Roever et al. | Feb 2013 | A1 |
| 20130047232 | Tuchman et al. | Feb 2013 | A1 |
| 20130054517 | Beechuk et al. | Feb 2013 | A1 |
| 20130054684 | Brazier et al. | Feb 2013 | A1 |
| 20130058262 | Parreira | Mar 2013 | A1 |
| 20130067232 | Cheung et al. | Mar 2013 | A1 |
| 20130067448 | Sannidhanam et al. | Mar 2013 | A1 |
| 20130097298 | Ting et al. | Apr 2013 | A1 |
| 20130110658 | Lyman | May 2013 | A1 |
| 20130132573 | Lindblom | May 2013 | A1 |
| 20130139148 | Berg et al. | May 2013 | A1 |
| 20130156024 | Burg | Jun 2013 | A1 |
| 20130166580 | Maharajh et al. | Jun 2013 | A1 |
| 20130179942 | Caplis et al. | Jul 2013 | A1 |
| 20130201909 | Bosch et al. | Aug 2013 | A1 |
| 20130204786 | Mattes et al. | Aug 2013 | A1 |
| 20130212603 | Cooke et al. | Aug 2013 | A1 |
| 20130244632 | Spence et al. | Sep 2013 | A1 |
| 20130268676 | Martins et al. | Oct 2013 | A1 |
| 20130325934 | Fausak et al. | Dec 2013 | A1 |
| 20130328997 | Desai | Dec 2013 | A1 |
| 20130336472 | Fahlgren et al. | Dec 2013 | A1 |
| 20140013400 | Warshavsky et al. | Jan 2014 | A1 |
| 20140025503 | Meyer et al. | Jan 2014 | A1 |
| 20140058806 | Guenette et al. | Feb 2014 | A1 |
| 20140064467 | Lawson et al. | Mar 2014 | A1 |
| 20140072115 | Makagon et al. | Mar 2014 | A1 |
| 20140073291 | Hildner et al. | Mar 2014 | A1 |
| 20140095627 | Romagnino | Apr 2014 | A1 |
| 20140101058 | Castel et al. | Apr 2014 | A1 |
| 20140101149 | Winters et al. | Apr 2014 | A1 |
| 20140105372 | Nowack et al. | Apr 2014 | A1 |
| 20140106704 | Cooke et al. | Apr 2014 | A1 |
| 20140122600 | Kim et al. | May 2014 | A1 |
| 20140123187 | Reisman | May 2014 | A1 |
| 20140126715 | Lum et al. | May 2014 | A1 |
| 20140129363 | Lorah et al. | May 2014 | A1 |
| 20140153565 | Lawson et al. | Jun 2014 | A1 |
| 20140185490 | Holm et al. | Jul 2014 | A1 |
| 20140254600 | Shibata et al. | Sep 2014 | A1 |
| 20140258481 | Lundell | Sep 2014 | A1 |
| 20140269333 | Boerjesson | Sep 2014 | A1 |
| 20140274086 | Boerjesson et al. | Sep 2014 | A1 |
| 20140282473 | Saraf et al. | Sep 2014 | A1 |
| 20140289391 | Balaji et al. | Sep 2014 | A1 |
| 20140304054 | Orun et al. | Oct 2014 | A1 |
| 20140317640 | Harm et al. | Oct 2014 | A1 |
| 20140355600 | Lawson et al. | Dec 2014 | A1 |
| 20140372508 | Fausak et al. | Dec 2014 | A1 |
| 20140372509 | Fausak et al. | Dec 2014 | A1 |
| 20140372510 | Fausak et al. | Dec 2014 | A1 |
| 20140373098 | Fausak et al. | Dec 2014 | A1 |
| 20140379670 | Kuhr | Dec 2014 | A1 |
| 20150004932 | Kim et al. | Jan 2015 | A1 |
| 20150004933 | Kim et al. | Jan 2015 | A1 |
| 20150023251 | Giakoumelis et al. | Jan 2015 | A1 |
| 20150026477 | Malatack et al. | Jan 2015 | A1 |
| 20150066865 | Yara et al. | Mar 2015 | A1 |
| 20150081918 | Nowack et al. | Mar 2015 | A1 |
| 20150082326 | Milliron et al. | Mar 2015 | A1 |
| 20150082378 | Collison | Mar 2015 | A1 |
| 20150100634 | He et al. | Apr 2015 | A1 |
| 20150119050 | Liao et al. | Apr 2015 | A1 |
| 20150181631 | Lee et al. | Jun 2015 | A1 |
| 20150236905 | Bellan et al. | Aug 2015 | A1 |
| 20150281294 | Nur et al. | Oct 2015 | A1 |
| 20150365480 | Soto et al. | Dec 2015 | A1 |
| 20150370788 | Bareket et al. | Dec 2015 | A1 |
| 20150381580 | Graham, III et al. | Dec 2015 | A1 |
| 20160011758 | Dornbush et al. | Jan 2016 | A1 |
| 20160028695 | Binder | Jan 2016 | A1 |
| 20160077693 | Meyer et al. | Mar 2016 | A1 |
| 20160112475 | Lawson et al. | Apr 2016 | A1 |
| 20160112521 | Lawson et al. | Apr 2016 | A1 |
| 20160119291 | Zollinger et al. | Apr 2016 | A1 |
| 20160127254 | Kumar et al. | May 2016 | A1 |
| 20160139971 | Milliron et al. | May 2016 | A1 |
| 20160149956 | Birnbaum et al. | May 2016 | A1 |
| 20160162172 | Rathod | Jun 2016 | A1 |
| 20160205519 | Patel et al. | Jul 2016 | A1 |
| 20160226937 | Patel et al. | Aug 2016 | A1 |
| 20160226979 | Lancaster et al. | Aug 2016 | A1 |
| 20160234391 | Wolthuis et al. | Aug 2016 | A1 |
| 20160239770 | Batabyal et al. | Aug 2016 | A1 |
| 20170339283 | Chaudhary et al. | Nov 2017 | A1 |
| 20180024873 | Milliron et al. | Jan 2018 | A1 |
| 20180210769 | Milliron et al. | Jul 2018 | A1 |
| Number | Date | Country |
|---|---|---|
| 1684587 | Mar 1971 | DE |
| 0282126 | Sep 1988 | EP |
| 1464418 | Oct 2004 | EP |
| 1522922 | Apr 2005 | EP |
| 1770586 | Apr 2007 | EP |
| 2053869 | Apr 2009 | EP |
| 2134107 | Sep 1999 | ES |
| 10294788 | Nov 1998 | JP |
| 2004166000 | Jun 2004 | JP |
| 2004220118 | Aug 2004 | JP |
| 2006319914 | Nov 2006 | JP |
| WO-9732448 | Sep 1997 | WO |
| WO-2002087804 | Nov 2002 | WO |
| WO-2006037492 | Apr 2006 | WO |
| WO-2009018489 | Feb 2009 | WO |
| WO-2009124223 | Oct 2009 | WO |
| WO-2010037064 | Apr 2010 | WO |
| WO-2010040010 | Apr 2010 | WO |
| WO-2010101935 | Sep 2010 | WO |
| WO-2011091085 | Jul 2011 | WO |
| Entry |
|---|
| “Aepona's API Monetization Platform Wins Best of 4G Awards for Mobile Cloud Enabler”, 4G World 2012 Conference & Expo, [Online]. [Accessed Nov. 5, 2015]. Retrieved from the Internet: <URL: https://www.realwire.com/releases/%20Aeponas-API-Monetization>, (Oct. 30, 2012), 4 pgs. |
| “U.S. Appl. No. 14/489,387, Examiner Interview Summary dated May 18, 2015”, 3 pgs. |
| “U.S. Appl. No. 14/489,387, Examiner Interview Summary dated May 22, 2015”, 3 pgs. |
| “U.S. Appl. No. 14/489,387, Final Office Action dated Jun. 11, 2015”, 18 pgs. |
| “U.S. Appl. No. 14/489,387, Non-Final Office Action dated Nov. 26, 2014”, 18 pgs. |
| “U.S. Appl. No. 14/489,387, Notice of Allowance dated Oct. 21, 2015”, 6 pgs. |
| “U.S. Appl. No. 14/489,387, Response filed May 19, 2015 to Non-Final Office Action dated Nov. 26, 2014”, 10 pgs. |
| “U.S. Appl. No. 14/489,387, Response filed Oct. 13, 2015 to Final Office Action dated Jun. 11, 2015”, 11 pgs. |
| “U.S. Appl. No. 15/002,774, Non-Final Office Action dated Dec. 13, 2016”, 15 pgs. |
| “U.S. Appl. No. 15/002,774, Notice of Allowance dated Mar. 27, 2017”, 8 pgs. |
| “U.S. Appl. No. 15/002,774, Notice of Allowance dated Jun. 29, 2017”, 5 pgs. |
| “U.S. Appl. No. 15/002,774, Response filed Mar. 7, 2017 to Non-Final Office Action dated Dec. 13, 2016”, 7 pgs. |
| “U.S. Appl. No. 15/719,860, Notice of Allowance dated Dec. 20, 2017”, 8 pgs. |
| “U.S. Appl. No. 15/926,381, Non-Final Office Action dated Apr. 26, 2018”, 7 pgs. |
| “U.S. Appl. No. 15/926,381, Notice of Allowance dated Aug. 30, 2018”, 7 pgs. |
| “U.S. Appl. No. 15/926,381, Response filed Jun. 21, 2018 to Non-Final Office Action dated Apr. 26, 2018”, 6 pgs. |
| “Archive Microsoft Office 365 Email I Retain Unified Archiving”, GWAVA, Inc., Montreal, Canada, [Online] Retrieved from the internet: <http://www.gwava.com/Retain/Retain for_Office_365.php>, (2015), 4 pgs. |
| “Complaint for Patent Infringement”, Telinit Technologies, LLC v. Twilio Inc 2:12-cv-663, (Oct. 12, 2012), 17 pgs. |
| “Ethernet to Token ring Bridge”, Black Box Corporation, [Online] Retrieved from the internet: <http://blackboxcanada.com/resource/files/productdetails/17044.pdf>, (Oct. 1999), 2 pgs. |
| “Twilio Cloud Communications—APIs for Voice, VoIP, and Text Messaging”, Twilio, [Online]Retrieved from the internet: <http://www.twilio.com/docs/api/rest/call-feedback>, (Jun. 24, 2015), 8 pgs. |
| Abu-Lebdeh, et al., “A 3GPP Evolved Packet Core-Based Architecture for QoS-Enabled Mobile Video Surveillance Applications”, 2012 Third International Conference on the Network of the Future {NOF), (Nov. 21-23, 2012), 1-6. |
| Barakovic, Sabina, et al., “Survey and Challenges of QoE Management Issues in Wireless Networks”, Hindawi Publishing Corporation, (2012), 1-29. |
| Berners-Lee, T., “RFC 3986: Uniform Resource Identifier (URI): Generic Syntax”, The Internet Society, [Online]. Retrieved from the Internet: <URL: http://tools.ietf.org/html/rfc3986>, (Jan. 2005), 57 pgs. |
| Kim, Hwa-Jong, et al., “In-Service Feedback QoE Framework”, 2010 Third International Conference on Communication Theory. Reliability and Quality of Service, (2010), 135-138. |
| Matos, et al., “Quality of Experience-based Routing in Multi-Service Wireless Mesh Networks”, Realizing Advanced Video Optimized Wireless Networks. IEEE, (2012), 7060-7065. |
| Mu, Mu, et al., “Quality Evaluation in Peer-to-Peer IPTV Services”, Data Traffic and Monitoring Analysis, LNCS 7754, 302-319, (2013), 18 pgs. |
| Subramanya, et al., “Digital Signatures”, IEEE Potentials, (Mar./Apr. 2006), 5-8. |
| Tran, et al., “User to User adaptive routing based on QoE”, ICNS 2011: The Seventh International Conference on Networking and Services, (2011), 170-177. |
| Number | Date | Country | |
|---|---|---|---|
| 20190235935 A1 | Aug 2019 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61879035 | Sep 2013 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 15926381 | Mar 2018 | US |
| Child | 16204961 | US | |
| Parent | 15719860 | Sep 2017 | US |
| Child | 15926381 | US | |
| Parent | 15002774 | Jan 2016 | US |
| Child | 15719860 | US | |
| Parent | 14489387 | Sep 2014 | US |
| Child | 15002774 | US |
