This invention relates generally to the communication field, and more specifically to a new and useful system and method for a multi-channel notification service in the communication field.
Today's digital services have grown beyond standalone web or mobile applications. Users expect an application or service to be accessible on any device (e.g., in the browser on the desktop or in an app on a smart phone). Increasingly, users expect to have the state on those devices to be synchronized, providing a seamless multi-channel experience. Additionally, with many services being social, actions can occur beyond a user's own actions, and a user may want to be notified of those changes. Various forms of notifications are used to alert a user of new information or events. However, building out useful notifications can be challenging and time consuming. Additionally, as a digital service diversifies its user base, the various user preferences and device variations present substantial challenges. Any digital service that wants to implement a world-class user experience for a multi-platform system, extensive investment is required in notifications. Thus, there is a need in the communication field to create a new and useful system and method for a multi-channel notification service. 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. Overview
The system and method for a multi-channel notification service functions to provide a service enabling a streamlined approach to enabling notification features within a digital service or application. The system and method enable configuration of a notification service for an account such that audience selection, multi-channel notifications, orchestrated notifications rules and execution, and/or other features can be reduced to a programmatic notification request. Preferably, the system and method can enable notifications that can be sent out across different communication channels. Those communication channels could include SMS, MMS, an application push notification channel, a third party communication channel (e.g., a social network messaging service), email, browser or operating notification, a device endpoint, and/or any suitable channel.
Notifications can be any suitable communication used to alert a user. The notification is generally a one-way communication. Though some notifications may allow full or partial two-way communication. For example, a notification may be marked as delivered and/or seen as a form of partial two-way communication. Similarly, some notification communication channels may allow a response action or reply by a user. The system and method can be used as a mechanism for transactional notifications (i.e., notifications targeted at one or a select set of users relating to some individual event like a purchase or login event) and/or bulk notifications (i.e., notifications broadcast to groups of users).
The system and method are preferably implemented through a multitenant service platform. The multitenant service platform can enable multiple distinct accounts, sub-accounts or other entities to utilize the platform to enable notification features for their own distinct application or service offering. The multitenant service platform may operate as a platform as a service or software as a service type operation. The system and method preferably offer a set of mechanisms and processes through which users can more easily enable and control notifications. Additionally, with the engineering work centralized to a focused platform, multiple parties may benefit from improved and updated design of the platform. A developer could avoid developing custom infrastructure for communicating over multiple notification channels as well as avoiding maintaining and updating these channel integrations as they change.
As a first potential benefit, the system and method can offer a unified and normalized interface for using one or more notification channels. An outside service or product that wants to enable notification features can leverage one notification service instead of building out multiple communication channel integrations. For example, a developer could use a notification platform implementing the system and method in enabling notifications across a wide variety of formats, but while also using a simple intuitive programmatic interface for specifying notification content details.
As a second potential benefit, the system and method can enable configurable orchestration, where complex routing and fallback options can be simply configured ahead of time as default behavior for an account or on-demand for a particular notification request. Orchestration rules can be used to deliver to devices preferred by a particular participant, to fallback to secondary notification endpoints during failure, to fan out notifications across all notification channels, to automatically restrict notification delivery to particular time windows, and/or to apply other suitable orchestration rules. These orchestration options can be selectively invoked based on each particular notification and/or configuration of an account or notification service.
As a third potential benefit, the system and method may enable hierarchical notification definitions wherein a single notification request may enable notifications to be sent across multiple channels and be customized for a subset of those channels. Different notification channels will have different capabilities. For example, SMS may only allows for text while another channel may enable structured templates to define a custom interactive notification to be delivered within a notification channel. A notification can be simply delivered to multiple channels while custom features of particular notification channels may be leveraged.
As a fourth potential benefit, the system and method can enable customizing the notification experience for each participant. Participants will have varying preferences for how and when they are notified. In some cases, a participant may be accessible through multiple channels. For example, one user may want to receive SMS messages and not push notifications. And one user may want push notifications. The system and method could facilitate managing participant preferences.
The system and method can be utilized in a variety of use cases. Any application or digital service that needs to alert a user or device of some information may utilize the system and method. As one example, a digital marketplace may want to alert all buyers when a new relevant item becomes available or its price drops. As another example, on-demand dispatching applications may need to alert available “workers” (e.g., call-center agents, drivers, contractors, etc.) of a new “request” (e.g., a support ticket, passenger, job, etc.). Yet another example, news and content apps may want to notify users about new content.
2. Method for a Multi-Channel Notification Service
As shown in
The method functions to provide a service enabling a streamlined approach to enabling notification features within a digital service or application. The method can be used for facilitating notifications through any suitable set of communication channels. Preferably, the communication channels include SMS/MMS and at least a push communication channel (e.g., the Apple push network or the Google cloud messaging). Other potential communication channels can be asynchronous messaging channels such as proprietary messaging services with accessible APIs. A proprietary messaging service may enable notifications to a user within an application or a service. In another variation, the proprietary messaging service directs notifications to a device endpoint such as a wearable computer, an IoT device, a home or office digital assistant, and/or any suitable device. Other notification or communication channels may alternatively or additionally be used.
Block S100, which includes configuring an account for notifications within a multitenant platform for multi-channel notifications, functions to setup how notifications will be managed and executed within the system. A multitenant platform preferably supports configuring a set of different notification scopes. For example, an account that wants to use notifications can configure their account for notifications. An account may additionally setup multiple instances of notification configuration. Herein we describe the configuration and management of the notification being associated with an account. However, notification configuration may alternatively be associated with any suitable entity or scope such as a subaccount.
Configuring the account for notifications can involve configuring the different communication channels and the various participants to be accessed during a notification. This preemptive configuration can make subsequent notification requests simpler to implement. The configuration can preferably be characterized and architected through a set of different resources. The resources can be API resources, data object classes, data model architecture, or any suitable data object. While there may be a variety of ways of receiving and setting configuration, the multitenant platform preferably enables at least one programmatic interface and more preferably a REST API
In particular, configuring the account for notifications can include receiving configuration for at least one notification service resource S110 and receiving configuration for a set of participant binding resources S120.
Block S110, which includes receiving configuration for at least one notification service, functions to define the various communication channels used for notification. A notification service can be referenced when making a notification request, which will cause the configuration of the notification service resource to be utilized in executing the corresponding notification.
Configuring a communication channel can include instantiating channel credentials of a communication channel for a notification service S112 as shown in
With regard to telephony communication channels such as SMS, MMS, and/or PSTN calls, a telephony endpoint (e.g., a phone number, short code, toll free number) can be registered and identified for use with the notification service. Configuring a communication channel can additionally or alternatively include registering and identifying a communication endpoint for use with the notification service. An account may have one or more communication endpoints configured for particular communication channels. For example, an account could have one phone number or a pool of phone numbers, which could be used for SMS messages, MMS messages, or phone calls. As another example, an account could have a SIP address or other credentials setup. A communication endpoint can be a phone number, a short code, toll number, a SIP address, and/or any suitable communication endpoint identifier used for routing communication within a communication network. In one implementation, an account holder can purchase and set up multiple telephony endpoints to be managed and/or used by the account holder within the communication platform. When setting up a notification service, one or multiple telephony endpoints operated by the account holder could be selected for use with the notification service. In an alternative implementation, the communication platform can have a pool of telephony endpoints that may be shared by account holders, in which case there may be no explicit identification of which telephony endpoint is used as that would be automatically selected by the communication platform.
The notification service is scoped to the account, and an account could create and manage a set of different notification services. The set of notification service resources could be queried at any suitable time through the API or an alternative interface. This may be particularly applicable in a multitenant communication platform that enables nested account scopes where one account scope can create a subaccount, wherein each account could build an application that enables a multitenant application or service. Multiple notification services can be operated within an account but individually managed within subaccounts of the parent account. Multiple notification services within an account can additionally be used so that one account can be used to manage different applications, services, or products of the account holder. For example, an account holder with multiple products may instantiate multiple notification services with different configuration, where each notification service is used in servicing each individual product.
Block S120, which includes receiving configuration for a set of participant binding resources, functions to set the addressing information for participants for one or more communication channels. The participant binding resources preferably establishes data/modeling records that can be used in executing a notification request. Preferably, destination endpoints or addressing information is established through the participant binding resources. Generally, speaking the participant binding resources can be updated and maintained by an account holder. For example, existing addressing information can be used in creating a number of participant binding resources, and then add or modify the addressing information as the account holder receives updates. Preferably, the endpoint addressing information such as phone numbers, email addresses, or other communication addresses are explicitly specified in the participant binding resources. Alternatively, the endpoint addresses may be stored and maintained outside the communication platform and are referenced at the time of sending a notification, which may be useful if an account does not want to entrust a third party like the communication platform with addressing information. Both approaches could be used in combination.
Various architectures of participant binding resources may be used where information and information associations can be structured in different ways. The participant binding resources can in some architectures include properties that relate to an account reference, a service reference, communication channel identifying properties, a communication address identifier, a participant identifier, and/or other addressing properties. The various participant binding resources can be directly associated with one notification service resource. Deleting a notification service resource can result in deleting associated binding resources.
In a first variation, receiving configuration for a set of participant binding resources comprises receiving configuration of endpoint addressing resources S122 as shown in
The communication channel identifier can identify the type of communication channel to be used and may additionally include a protocol version number and/or any suitable information. For example, communication channel identifier options can include “SMS”, “PSTN”, “Company X messenger service”, “Company Y push notification service”, and the like. The endpoint addressing resource can additionally include communication channel credentials. The communication channel credentials may be used to override default channel credentials.
Additionally, the participant binding resources and more specifically the endpoint addressing resources can be assigned tag properties to facilitate convenient references to the resource. The tags can be string based labels or other identifiers, which may be used for bulk operations with the bindings. The tags can be account/developer defined. The tags can be specified during creation of the endpoint addressing resource, but could additionally be updated after the creation of the endpoint addressing resource. Additionally, a set of tags may be automatically assigned to a binding based on properties of the participant binding resource. For example, automatic tags can include “all” to reference all bindings), “apn” to reference Apple push network bindings, “gem” to reference Google cloud messaging bindings, “sms” to reference a telephony binding, “facebook-messenger” to reference Facebook messenger channel bindings, and/or any suitable automatic tags. Similarly, analysis of the endpoint address can be used to generate tags. For example, a phone number could be analyzed and geographic associations of that phone number could be used as tags. For example, the associated country from the country code, region from an area code, phone type (land line vs. mobile), and/or other extracted information can be used as tags.
Endpoint addressing resources can additionally include a participant identifier. The participant identifier can be an account defined identifier for a participant such as a unique user identifier string or an email address. The participant identifier functions as a convenience property for optionally specifying notification destinations by participant identifiers instead of endpoint addresses. However, a preferred variation is to include distinct participant resources that can be associated with the endpoint addressing resources to better reflect how a participant may have multiple usable endpoint addresses.
In another variation, receiving configuration for a set of participant binding resources comprises receiving configuration of endpoint addressing resources S122 and receiving configuration for participant resources S124 as shown in
Additionally, an additional grouping construct can be offered so that participants can be associated with participant groups or segments. In one variation, a participant group can be another type of participant binding resource that can have associations with many participant resources and, by extension, multiple communication addresses. In another variation, participant resources can include a tag property. A participant grouping may be used to specify participant classifications. For example, an account holder may create participant group resources for different user tiers (e.g., premium, free, etc.) so that those different groups of users can be notified as a group. The participant groups can be any suitable subsets of the participants. For example, two participant groups can include participant resources that are associated with both participant groups.
Generally, a notification service resource will be initially configured, and participant binding resources will subsequently be created as end users of the account are enrolled as shown in
Block S200, which includes receiving a notification request on behalf of an account, functions to initiate sending of one or more notifications. The notification request can be used to deliver a specific notification to a targeted participant or group of participants. For example, a taxi application may want to notify a customer that their taxi has arrived, and notification can be sent to just that participant by specifying the notification content and the identity of the participant. The configuration of Block S100 can be used to deliver the notification appropriately. The notification request can similarly send notifications to multiple targeted participants. In other scenarios, a digital service may want to fan out a general notification to a wide audience. In this notification, tags can be utilized to specify particular endpoints without explicitly providing a list of each endpoint at the time of the notification.
In different instances, different notification requests can be received and executed through blocks S200 and S300 where each is individually processed. In one instance, a notification request can broadcast notifications to a group of participants. In another instance a different notification request can send a transactional notification to one or a limited set of participants. In another instance, a notification request can be processed so that notifications use a fallback option. The various features implemented in the method can be selectively invoked in different notification requests.
A notification request can be received through an API request. For example, an HTTP-based POST request can be received with a set of request properties defining how a notification should be sent. A notification request may alternatively be specified within a script or application that is processed within the platform. In yet another variation, a user interface or dashboard may be presented to enable an administrator of the account to manually specify and send out notifications through a dashboard or an alternative user interface.
A notification request preferably specifies a notification service, targeting property, and payload definition. The notification request can additionally include delivery options or authenticating or scope identifying information such as an account secure identifier. The notification service identifier is used to map the notification to configuration. In some variations the notification service identifier is not needed as the notification service and its configuration is directly associated with the account.
The targeting property can be specified in a variety of approaches. In a first approach, the targeting property includes a set of endpoints, set of participant identifiers, participant group identifier, and/or tags. An endpoint can be used to send to a particular device instance of a participant as specified by an endpoint addressing resource. A participant identifier may be used to send a notification to one or more endpoints associated with the participant as specified by a participant resource. A participant group identifier may be used to send a notification to one or more endpoints of participants associated with the group. Tags can be used to send to endpoints associated with the tags. In one variation, the targeting property can be conditional so that all their properties must be matched. Different logical rules may be used in processing how multiple targeting properties are handled. In one implementation, the notifications can be sent to the union of endpoints defined by all the targeting properties. For example, targeting properties may specify identifiers for a set of endpoint addressing resources and also a number of tags, and all endpoints that match the set of endpoints or any of the tags may be notified. In another implementation, notifications can be sent to the overlap of endpoints defined by all the targeting properties. In a similar example to above, targeting properties may specify identifiers for a set of endpoint addressing resources and also a number of tags, and then only a subset of the identified endpoints that also share the identified tags are notified. In yet another implementation, notifications can be sent to endpoints based on some prioritized analysis of the targeting properties. However, any suitable logical processing of multiple targeting properties may be used.
In one variation, the targeting property may additionally or alternatively reference an external resource, wherein targeting property can be accessed from a remote server at the time of the processing of the notification request. The external resource can be a specified URI that preferably hosts a resource that can provide endpoint addressing information in place of or to supplement the endpoint addressing resources. For example, one targeting property can be an endpoint callback URI. When processing a notification request with an endpoint callback URI an application layer request (e.g., an HTTP/S request) is transmitted the callback URI. The server responsive to that request can provide a static document or generate a document that will specify addressing endpoints and relevant information like communication channel identifier and credentials as in an endpoint addressing resource. Authentication and/or whitelisting of the IP address used by the communication platform can be used when communicating with the external resource to secure the list of targeting property. This variation can enable an account holder to avoid storing targeting property permanently with the communication platform.
The notification request can additionally include delivery option properties such as a priority property, a time-to-delivery property, a maximum delivery cost, a preferred device option, a fallback option, a fan out option and/or other transmission options. The delivery option properties can be used to specify different notification orchestrations or approaches to managing notifications. In some cases, the delivery option properties will only impact the notification delivery and handling for a subset of communication channels.
The priority property may be recognized by different communication channels to prioritize the delivery of the notification. For example, some push notification channels may have high and low priority options which change how notifications are delivered in consideration of battery consumption of the device. The priority property can additionally be used within the communication platform for how it handles delivery of notifications across the account and/or platform. In one example, low priority may be accompanied with an unspecified delivery time while a high priority may have an expected delivery time window (e.g., immediate, in next 5 minutes, etc.).
The time-to-live property specifies how long the notification request is valid within the platform. The time-to-live property is preferably a specified length of time. A countdown clock will be initialized synchronized to the receipt of the notification request when a time-to-live property is present. After the time specified in the time-to-live property expires, any unsent notifications are canceled. This may be applicable for notifications that are only relevant for a certain amount of time.
A maximum delivery cost will limit the per notification or total amount to be spent fulfilling the notification request. As there may be a cost associated with transmitting the notifications through the multitenant platform, a maximum delivery cost can prevent a notification request from going above expectations. This can be particularly useful when sending notifications across multiple communication channels. The method abstracts away the end communication channel but there will be some financial impact to sending notifications based on the distribution of endpoint addressing resources associated with metered and/or billed communication channels like SMS or MMS. In some variations, the maximum delivery cost can be specified individually for specific communication channels. Processing of a maximum delivery cost property can be used in combination with a fallback option or other orchestration options. In one variation, once the maximum delivery cost limit is met then notifications can proceed for participants that have available free communication channels. For example, a notification may be initially intended to be sent over SMS for one participant but after the price for that notification is surpassed, the notification will be sent over a social media communication channel to that participant.
A preferred device option will facilitate selection of an endpoint addressing resource to be used for a targeted participant when multiple options are available. The preferred device option may be a Boolean value to activate preferred device delivery of notifications. The preferred communication channel and/or device instance (in the case where there may be multiple application instances of the same communication channel) can be indicated through tagging of an endpoint addressing resource. For example, in the creation of an endpoint addressing resource a preference tag (e.g., the tag string “preferred device”) can be added. Then when preferred device option is activated in a notification request that endpoint addressing resource will be selected for sending that notification over other participant associated endpoint addressing resources.
In another variation, the preference or priority of different communication channels can be specified within the notification request or the notification service. These can act as defaults for that notification or account. For example, one account may set their default priority to SMS then voice then a social media messaging channel, but another account may set their default priority to a social media messaging channel, then email, and then SMS.
A fallback option can be a delivery that enables a backup endpoint addressing resource to be used as a delivery target when delivery is unsuccessful for an attempted notification to an initially used endpoint addressing resource. The fallback option can be a Boolean option that can be enabled for notifications over supported communication channels. Supported communication channels preferably have a delivery confirmation mechanism. The delivery confirmation can provide delivery confirmation (e.g., send successfully) and/or read confirmation (e.g., viewed by user). Unsuccessful confirmation can trigger a subsequent notification using a different approach. Success and failure can be defined in different ways. In one implementation this can be a time window where some confirmation must be satisfied. In another implementation it may be the receipt of some error status like delivery failure. The failure condition may be defined or specified in the notification request or within the notification service configuration. In one example, a notification may first be attempted over a push notification network for a participant and then an SMS can be used for notification if delivery is unsuccessful after ten minutes.
A fan out option can be a delivery option that enables notifications to be sent out to all endpoint addresses of a participant. A fan out option may be invoked in a notification request if the account holder wants to increase likelihood that end participants receive the notifications. This may be used in cases, where an important alert is being sent out and the account holder prioritizes participants getting the notification over receiving redundant notifications across different communication channels and/or devices.
The payload properties of the notification request preferably defines the content of the notification to be communicated to the end user of the target endpoint. The payload properties preferably include a body such as a text string. The payload properties can additionally include a title property, a media property, a sound property, an action property (e.g., actions to be displayed for the notification), data property, and/or other suitable properties. The notification request can additionally include a hierarchical definition of the notification and in particular the payload properties. Hierarchical definitions allow general default payload properties to be specified, but for customized notifications to be defined for particular communication channels so as to override corresponding payload defaults. Channel-specific payload properties can be defined for one or more communication channels. The channel specific payload properties may support channel specific features and/or capabilities. Support for channel specific payload properties can enable custom features of a communication channel to be used through the communication platform even when sending notifications across multiple communication channels.
Block S300, which includes executing a notification according to the notification request and the configuration, functions to attempt to transmit notifications. Initially the notification request can be processed and validated. For example, the notification can be validated as being authentically associated with an account. Additionally any required properties can be validated. Executing notifications can include selecting endpoint addressing resources that are accessed from the participant binding resources using the targeting properties of the notification request and transmitting notifications to communication addresses over a set of different communication channels as indicated by the selected endpoint addressing resource. The transmission or attempted sending of notifications is preferably executed by, for each selected endpoint addressing resource, transmitting a notification to the specified communication address of the endpoint addressing resource through a communication channel that is specified by the communication channel identifier of the endpoint addressing resource.
The different communication channels can include different formats and communication mediums. In one variation, transmitting notifications over a set of different communication channels can include transmitting an asynchronous message to a communication address specified by a selected endpoint addressing resource. In another variation, transmitting notifications over a set of different communication channels can include transmitting initializing a synchronous communication stream and playing a message for at least one communication address.
If the notification request is valid, then the referenced participant binding resources and configuration are selected, accessed, and used in executing the notification to one or more destinations. The participant binding resources that are accessed are those referenced in the targeting properties of a notification request. The endpoint identifiers, participant identifiers, participant group identifiers, tags, and/or other properties may be used to specify the destination endpoints. These are used to identify and select endpoint addressing resources. As described above, various approaches may be used in accessing the referenced endpoint addressing resources. In some cases, the delivery options specified for a notification or account can additionally be used in selecting the appropriate endpoint addressing resources. For each of the accessed endpoint addressing resource a notification can be attempted. Preferably, a selected endpoint addressing resource will indicate the communication channel and addressing information within the communication channel, and the notification service can include the channel credentials and general information to deliver a notification.
In the instance variation where a notification request includes a preferred device option, executing the notifications can include selecting an endpoint addressing resource that is associated with a participant resource and indicated as a preferred device. Indication of a preferred device can be through a special tag that can be applied to an endpoint addressing resource. Alternatively preferred device may be an internally applied tag through analysis and usage history of endpoints of a participant.
In the instance variation where a notification request includes a fanout delivery option, the selection of appropriate endpoint addressing resources will involve selecting all endpoint addressing resources associated by the targeted/specified participant resources.
Executing a notification can additionally include generating the notification content, which functions to determine the payload of a transmitted notification. As mentioned above, the payload properties can be defined hierarchically. The payload properties for notification sent over a specific communication channel can include using the default payload properties unless additional or overriding payload properties are specified for that communication channel. A customized notification payload can be generated for each communication channel that will be used for a given notification. Finally, a notification request is submitted or transmitted over the appropriate communication channel. Each communication channel may have varying protocols and/or technology to issue a communication. Additionally, transmission of notifications can be independently managed for different communication channels, which can enable rate limiting, volume limits, and independent metering of notifications over different channels. The multitenant platform can hide these complexities from the account holder (e.g., the developer).
In the instance where the notification request includes a tag identifier, selecting an endpoint addressing resources that are accessed from the participant binding resources using the targeting properties of the notification request can include selecting endpoint addressing resources queried with the tag targeting property of the endpoint addressing resources. The tag identifier is used to access the endpoint addressing resources with that tag property. In some cases, that tag property may have been automatically generated. Multiple tag identifiers could be indicated in the notification request. Using AND Boolean logic/intersection logic, the selected endpoint addressing resources may have tag properties that include each tag identifier. Using OR Boolean logic/union logic, the selected endpoint addressing resources may have at least one tag property matching one of the tag identifiers.
In another instance, the notification request can include a tag identifier and a participant group identifier. In this variation, the participant binding resources includes participant resources associated with a participant group (e.g., as a group resource or having a group label/tag). In this instance, selecting endpoint addressing resources can include selecting endpoint addressing resources according to the participant group identifiers and tag identifiers. Similar with the tags above, the group identifiers and tag identifiers can be used with union or intersection type selection logic.
In the instance variation where a notification request includes a priority option, then notifications can be executed as a prioritized notification when supported by a communication channel. In this instance, at least one endpoint addressing resource includes a tag property identifying the endpoint addressing resource as preferred. Preferably only one endpoint addressing resource can be tagged or indicated as preferred. Alternatively, multiple endpoint addressing resources can be tagged or indicated as preferred in which case multiple preferred devices can be notified. The notification request will include some targeting property such as a participant group identifier, a tag identifier, and/or a participant identifier. During priority option, selecting endpoint addressing resources that are accessed from the participant binding resources using the targeting properties of the notification request will include selecting an endpoint addressing resource that is associated with the participant resource and identified as preferred. In this way a participant's preferred communication address and/or application instance can be notified.
In the instance variation where a notification request includes a delivery cost property, transmitting a notification can include tracking metered cost of transmitted notifications associated with the notification request and alerting notification transmissions when the metered cost satisfies the delivery cost property. Altering notification transmissions can include canceling notification transmissions or altering communication channel. Altering of communication channel preferably includes selecting a fallback or alternative endpoint addressing resource of a participant resource when a communication channel of an initial endpoint addressing resource has surpassed a maximum delivery cost for the notification.
In some variations, executing a notification can include receiving a notification response and parsing the notification response. Some communication channels can support replies or actions that respond to a notification. The communication platform can facilitate receiving and processing those responses. In one variation, the method can include updating notification state in association with a notification record. In another variation, the response can be relayed to an external application service specified by a response callback URI.
In one implementation, a delivery response can be facilitated by providing a notification SDK that can be integrated into an application. At an instance of an application with a notification SDK integration, detecting notification and delivering notification receipt state to the communication platform. This can include updating delivery status, read status, response status, and/or any suitable information. This implementation may be useful when delivery status information is not available. Some communication channels may provide built-in support for delivery status updates.
In the instance variation where a notification request includes a fallback option, executing a notification can include, collecting delivery status of an initially executed notification, and in response to the delivery status, selecting a secondary endpoint addressing resource of a participant and transmitting at least a second notification using the secondary endpoint addressing resource. This can include generating a new notification payload that is appropriate to the updated communication channel. The delivery status can be detection of a delivery or read receipt within a time window, receipt of a delivery error, or any suitable condition.
3. System for a Multi-Channel Notification Service
As shown in
The multitenant communication platform 100 preferably allows multiple accounts to use the communication platform in facilitating various communication tasks that include at least notifications. Additionally, each account within the multitenant communication platform 100 may itself have a subaccount. Accordingly, an account may support multiple communications for different sub-account holders wherein communication, data/analytics, billing, and/or other aspects can be scoped to an account, a sub-account, or any suitable scope. The communication platform can additionally be a cloud-hosted platform. The communication platform can be a server, a server cluster, a collection of components on a distributed computing system, or any suitable network accessible computing infrastructure.
The interface 110 to a set of notification programmatic primitives functions to enable account holders or other entities to configure and execute notifications. The interface preferably includes a programmatic interface, but may alternatively include a user interface. The user interface can be an application or dashboard used in manual execution and configuration of notifications. The programmatic interface functions to enable integration and use of the notification service to be added to a third party service or application. The complexities of managing notifications are delegated to the system. The developers of the third party applications or services can focus on the core aspects of their product rather than implementing features of a notification solution.
A programmable interface can provide one or a number of programmatic interfaces such as an API, an event callback system, or application logic processing system.
An API service is preferably a RESTful API but may alternatively be any suitable API such as SOAP or custom protocol. The RESTful API works according to an application layer request and response model. An application layer request and response model may use an HTTP-based protocol (HTTP or HTTPS), SPDY, or any suitable application layer protocol. Herein, HTTP may be used, but should not be interpreted as being limited to the HTTP protocol. HTTP requests (or any suitable request communication) to the communication platform preferably observe the principles of a RESTful design. RESTful is understood in this document to describe a Representational State Transfer architecture as is known in the art. The RESTful HTTP requests are preferably stateless, thus each message communicated contains all necessary information for processing the request and generating a response. The API service can include various resources, which act as API endpoints that can act as a mechanism for specifying requested information or requesting particular actions. The resources can be expressed as URI's or resource paths. The RESTful API resources can additionally be responsive to different types of HTTP methods such as GET, Put, POST and/or DELETE. Information about a conversation is preferably stored and made accessible through conversation API resources. Additionally participant API resources can be created and made accessible. In addition to obtaining information, actions can be initiated through the API For example, conversations may be initiated or ended, participants can be added or removed, media features enabled or disabled, and/or any suitable action can be triggered. An API is preferably used to remotely interact with notification primitives when setting up or sending a notification.
An event callback system can function to enable event triggers or webhooks to be activated in response to different state changes or events. Event callbacks can be account-customized conditions that result in an event response when the condition is satisfied. An event callback configuration can leverage internal information of the platform but without exposing the used internal information to an outside account entity. When an event callback condition is satisfied, a configured event is executed. The event could be an internal operation, a callback event, or any suitable action. An internal operation can be a closed action that may not be fully exposed to an account holder. A URI callback event preferably includes making an application layer protocol communication to an external resource located at the specified URI. A callback event may alternatively be configured by account for any suitable event such as when a conversation starts, when a conversation ends, when a property of a conversation satisfies some condition or threshold, or any suitable condition.
Application logic processing may enable business logic to be defined through an executable document. Preferably, application logic is specified through a structured document. In one variation, a markup language document can be used in specifying a set of instructions and conditions that can be sequentially executed. The application logic may be retrieved from a remote server. For example, the event callback system may retrieve application logic from a URI, which is then processed in association with a conversation. Application logic may alternatively be stored within the communication platform.
In one variation, an event callback may return application logic for processing. In one implementation, a notification request may be specified within the application logic.
The set of notification primitives preferably include a notification service resource, a participant binding resource, and a notification resource. As described above the notification service resource functions to setup the general configuration related to the enabled communication channels. The participant bindings are established to define how individual endpoints of a communication channel can be reached. In some cases an endpoint is a phone number. In the case of proprietary push notification networks or over-the-top messaging platforms, device identifiers or other suitable addressing tokens may be used. The notification resource can be used m requesting and reviewing notifications send from an account.
Generally, a developer that wants to use the system will create an account on the multitenant communication platform 100. Then the developer can setup a notification service resource for different communication channels the developer plans on using. For SMS and MMS this may involve importing a phone number or buying a phone number to use with the platform. For push notifications or third party communication channels, the developer may need to collect credentials from the various communication channels (where the developer may have distinct accounts for those services/platforms) and add those credentials to the notification service resource. Then the developer can onboard users. In one implementation, the developer may use an SDK, library, or API of the system when building an application or service. The developer can configure their own application logic to update the platform and onboard users as participant binding resources. The developer may customize the way a participant binding is established by detecting or asking a user for preferences in how notifications are received. The user preferences can be reflected in how bindings are setup. Then when a notification needs to be sent, a request can be made to the notification resource to send a notification. The configured information is used in intelligently sending notifications to the targeted endpoints.
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 media intelligence 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 application of co-pending U.S. patent application Ser. No. 16/845,041, filed Apr. 9, 2020, which claims priority to U.S. patent application Ser. No. 15/602,753, filed May 23, 2017, now U.S. Pat. No. 10,686,902, claims the benefit of U.S. Provisional Application No. 62/340,151, filed on May 23, 2016 each of which is incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
5274700 | Gechter et al. | Dec 1993 | 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 |
6192008 | Kim | Feb 2001 | B1 |
6192012 | Kim | 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 |
6487566 | Sundaresan | Nov 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 | 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 |
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 |
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 |
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 |
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 |
7376586 | Partovi et al. | May 2008 | B1 |
7376733 | Connelly 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 |
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 |
8101999 | Takizawa | Jan 2012 | 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 |
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 |
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 |
8306021 | Lawson et al. | Nov 2012 | B2 |
8315198 | Corneille 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 |
8346630 | McKeown | Jan 2013 | B1 |
8355394 | Taylor et al. | Jan 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 et al. | 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 |
8509068 | Begall et al. | Aug 2013 | B2 |
8532686 | Schmidt 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 |
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 |
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 |
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 |
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 |
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 |
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 |
9204281 | Ramprasad et al. | Dec 2015 | 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 |
9378337 | Kuhr | Jun 2016 | B2 |
9456008 | Lawson et al. | Sep 2016 | B2 |
9456339 | Hildner et al. | Sep 2016 | B1 |
9584462 | Chen | Feb 2017 | B1 |
9596274 | Lawson et al. | Mar 2017 | B2 |
9628624 | Wolthuis et al. | Apr 2017 | B2 |
9632875 | Raichstein et al. | Apr 2017 | B2 |
9967319 | Savelieva | May 2018 | 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 | 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 | 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 | Martino 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 | 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 |
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 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 |
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 |
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 |
20110246287 | Wright | Oct 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 |
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 |
20120066175 | Pickering | 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, Jr. 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 | Fuchman 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 et al. | 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 |
20140207877 | Kandaswamy | 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 |
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 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 |
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 | Aug 2016 | A1 |
20160239770 | Batabyal et al. | Aug 2016 | A1 |
20160335074 | Olivier | Nov 2016 | A1 |
20170339240 | Muller et al. | Nov 2017 | A1 |
20170339283 | Chaudhary et al. | Nov 2017 | A1 |
20180227332 | Neystadt | Aug 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 |
9732448 | Sep 1997 | WO |
2002087804 | Nov 2002 | WO |
2006037492 | Apr 2006 | WO |
2009018489 | Feb 2009 | WO |
2009124223 | Oct 2009 | WO |
2010037064 | Apr 2010 | WO |
2010040010 | Apr 2010 | WO |
2010101935 | Sep 2010 | 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. 15/602,753, Examiner Interview Summary dated Feb. 24, 2020”, 3 pgs. |
“U.S. Appl. No. 15/602,753, Final Office Action dated Jan. 16, 2020”, 8 pgs. |
“U.S. Appl. No. 15/602,753, Non Final Office Action dated Jul. 18, 2019”, 25 pgs. |
“U.S. Appl. No. 15/602,753, Notice of Allowance dated Feb. 27, 2020”, 5 pgs. |
“U.S. Appl. No. 15/602,753, Response filed Feb. 19, 2020 to Final Office Action dated Jan. 16, 2020”, 9 pgs. |
“U.S. Appl. No. 15/602,753, Response filed Oct. 16, 2019 to Non-Final Office Action dated Jul. 18, 2019”, 12 pgs. |
“Archive Microsoft Office 365 Email | Retain Unified Archiving”, GWAVA, Inc., Montreal, Canada, [Online] Retrieved from the internet: <http://www.qwava.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 | |
---|---|---|---|
20220191301 A1 | Jun 2022 | US |
Number | Date | Country | |
---|---|---|---|
62340151 | May 2016 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 16845041 | Apr 2020 | US |
Child | 17683252 | US | |
Parent | 15602753 | May 2017 | US |
Child | 16845041 | US |