Telephony web event system and method

Information

  • Patent Grant
  • 11632471
  • Patent Number
    11,632,471
  • Date Filed
    Wednesday, March 31, 2021
    3 years ago
  • Date Issued
    Tuesday, April 18, 2023
    a year ago
Abstract
An embodiment of the system for publishing events of a telephony application to a client includes a call router that generates events from the telephony application and an event router that manages the publication of events generated by the call router and that manages the subscription to events by clients. The system can be used with a telephony application that interfaces with a telephony device and an application server.
Description
TECHNICAL FIELD

This invention relates generally to the event notification field, and more specifically to an new and useful system and method in the telephony web event field.


BACKGROUND

In recent years, there has been a growing trend of both internet-enabled phones and “websites as software”. These two markets thrive on the transfer of information, instantaneous communication, and interaction between remote devices. However, current systems do not provide a seamless integration of telephony actions with remotely hosted applications, with server-side components, or with front-end websites. For instance, it is currently extremely difficult (if not impossible) to relay events that happen during a telephony call to or from a website securely in real-time during the telephony call. In addition, separation of business logic from telephony components complicates the transfer of realtime events from the call infrastructure to other remote services. Thus, there is a need in the telephony field to create a new and useful telephony web event system and method. This invention provides such a new and useful system and method.





BRIEF DESCRIPTION OF THE FIGURES


FIG. 1 is a schematic diagram of the preferred embodiment of the invention.



FIG. 2 is a detailed schematic diagram of the preferred embodiment of the invention.



FIG. 3 is a flowchart diagram of a preferred method of event subscription for telephony applications.



FIG. 4 is a flowchart diagram of a preferred method of distributing events.



FIG. 5 is a flowchart diagram of a preferred method of subscribing to events.



FIG. 6 is a flowchart diagram of a preferred method of subscribing and publishing events.



FIG. 7 is a flowchart diagram of a preferred method full duplex publishing and subscribing of events.



FIGS. 8A-8C are examples of a HTTP GET request, a HTTP POST request, and a HTTP GET request, respectively.



FIGS. 8D-8F are examples of a HTTP requests.



FIGS. 9A and 9B are examples of XML responses.



FIG. 10 an example of subscription aggregation.





DESCRIPTION OF THE PREFERRED EMBODIMENTS

The following description of the 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. Telephony Web Event System


As shown in FIGS. 1 and 2, the telephony web event system 100 of the preferred embodiment includes a call router 110 and an event router 120. The system functions to enable real-time telephony event interaction. In the preferred system, telephony events (e.g., a dialing sequence, a speech command, and a phone call termination) are sent out by a publisher (a device that prepares and electronically announces the occurrence of an event, preferably a call router) and received by a subscriber. A subscriber is preferably any client 130, such as a web browser 132 or Application Programming Interface (API) server 134 that has permission to receive information concerning a particular event. The system 100 is preferably implemented on a multitennant system where a plurality of applications and users are handled on the same software or hardware system. In particular, the call router can preferably simultaneously manage a plurality of telephony application and the event router can publish a plurality of events and manage a plurality of subscriptions for a plurality of clients. The components of the system are preferably scalable with respect to the number of accounts, in-progress calls, events on those calls, and the number of client subscriptions. Call routers no, event routers 120, or any sub-elements (such as event proxy servers 122 or message brokers 128) may be allocated or deallocated to automatically adjust for capacity requirements. A load balancer 121 may additionally be included to optimize the operation of the system components.


The call router no of the preferred embodiment functions to initiate the publication of events occurring during a telephony application. The telephony application is preferably a program controlling the interaction between a telephony based device 112 and an internet based web application server 114. The call router no preferably controls the call and program logic that enables telephony devices 112 to interface with the application server 114, as discussed in more detail below. The call router no preferably detects events occurring from the telephony application 114 and publishes these events to the event router 120. The call router may additionally include an event distributor 116 that determines to which event router to deliver the event. In one variation, the event router 120 includes a plurality of message brokers 128 that manage the publication of events. The message brokers 128 may be sharded or arranged according to event type or any suitable arrangement. The event distributor 116 preferably has control logic to know the correct message broker 128 to send an event. The control logic is preferably updated or synched with the scaling of hardware or software resources of the event router. As an example, an event may have varying attributes, such as account ID, a call ID, or event type. The message brokers 128 may be sharded based on any of these attributes or any combination of attributes. For example, if there are 3 event routers (shards), then the call router could convert the call ID into an integer and that number modulo 3 to determine which event router to contact. An event proxy server 122 may additionally share this control logic such that the event proxy server 122 knows which message broker(s) 128 to subscribe to. The event proxy server 122 preferably uses a similar technique to determine which event router 120 to contact based on what attributes where subscribed to. Additionally an event may be distributed (published) to multiple message brokers 128, such as in the situation where an event has attributes that are managed by multiple message brokers 128. For example, the event may be published by one message broker 128 that manages publication of events for a particular account and the event may additionally be published by a second message broker 128 that manages publication of events of a particular event type. Additionally, multiple event distributor 116 may be allocated or deallocated. The call router and the event router preferably communicate using HTTP or alternatively HTTPS, though any suitable communication system may be used. The published event preferably includes the account to which the event belongs, the type of event, and optionally a set of event data related to the event.


The call router 110 of the preferred embodiment additionally functions to initiate or receive calls from the telephony device 112 and connect to a web-application server 114. The call router 110 is substantially similar to the call router disclosed in application Ser. No. 12/417,630 filed on 2 Apr. 2009 and entitled “System and Method for Processing Telephony Sessions” which is hereby incorporated in its entirety by this reference. The call router 110 is preferably connected to a PSTN device over the PSTN network, such that it can receive and make calls from PSTN-connected devices 112, such as landlines, cellular phones, satellite phones, or any other suitable PSTN-connected devices, as well as non-PSTN devices, such as Voice-Over-Internet-Protocol (VOIP) phones, SIP devices, Skype, Gtalk, or other Internet addressable voice devices. The call router 110 may alternatively or additionally function as or include a message router for use with message-based networks such as SMS, email, faxes, instant messaging, or micro-blogging networks. The call router 110 can preferably connect to an SMS network, such that it can receive and send messages from SMS network devices 112, cellular phones, computers, smart phones, or any suitable SMS network devices. The call router 110 may also send or receive text messages, multimedia messages, emails, faxes and other suitable PSTN-compatible communication messages. The call router 110 can preferably connect to an instance messaging network, such that the call router 110 can receive and send messages and receive and transmit presence information from different instance messages networks such as those based on protocols like Jabber, AIM, or fax. The call router 110 can preferably connect to micro-blogging networks such as Twitter such that it can receive and send messages to and from micro-blogging networks via APIs exposed by those networks. The call router 110 may alternatively send and receive message from any suitable system with exposed APIs. The call router 110 preferably communicates with the application server 114 using an application layer protocol, more preferably using the HTTP, or secure HTTPS, protocol. The communication between the application server 114 and the call router no is preferably stateless and any state information (e.g., call state) or data is preferably located in a URI or the request parameters, such as HTTP headers, GET URI parameters, POST request body parameters, or HTTP cookies. Available state information is preferably transmitted by call router requests to the application server for stateless processing, and the application server preferably stores no state. Alternatively, the application server preferably stores local state information, such as databases or sessions, as is common in web development. The call router 110 preferably stores state information in call router resources 29. The call router resources are preferably accessible by the application server 114 and other devices through a call router API. The call router 110 preferably associates each incoming phone number with a starting resource address (or more specifically a URI), more preferably the URI is provided by the application server 114, still more preferably the URI is provided by the application developer before a call is received at the call router no by associating the initial URI with the incoming call address (such as DID, SIP address, etc.) or by the application upon initiation of an outgoing call. The call router 110 preferably sends call data such as the caller number (obtained via Caller ID), caller geographic data (country, city, and/or state, zip), the number dialed, the time of the call, or any other suitable information or parameter. The call data is preferably digitally signed with a secret key stored on the call router 110. A cryptographic hash of the information is preferably included along with the information as a digital signature. The call router 110 may also encrypt sensitive information (either before or after the cryptographic hash is computed) using the secret key to allow sensitive information to be sent across the network. The call data is preferably sent as an HTTP POST request to the application server 114. Call data may also be sent in URL (GET) variables, or encapsulated in HTTP headers. An example HTTP request containing the information in the header as shown in FIGS. 8A and 8D. As shown in FIG. 8B, further inputs (such as voice recording or DTMF button pressing) from the PSTN-device may be subsequently submitted to the application server 114 as HTTP requests (GET or POST). As shown in FIG. 8C, the inputs from a phone keypad may be included in an HTTP GET request. As shown in FIG. 8E, the content of an SMS message received by the call router may be sent to the application server 114 as an HTTP request. As shown in FIG. 8F, the inputs from the text message are included in an HTTP GET request. The request data may alternatively be simultaneously sent in the URI (query string), message body (POST) and message headers, or any combination of the above.


Any suitable action or parameter, either initiated by the telephony device 112 or by the application server 114, may constitute an event generated by the call router 110. The call router 110 preferably automatically detects such events through any suitable program logic. Events may relate to call related events such as starting or ending a call, starting or ending dialing a number, or any call based occurrence. The events may additionally or alternatively be related to telephony actions such as starting or stopping recording audio, starting or stopping a Text-To-Speech (TTS) conversion, starting or stopping the playing of an audio file, beginning or stopping the gathering of telephony input, redirecting the call to another phone number, or any telephony based instruction. Events may additionally be adjusted for particular applications such as conference calls. Conference call events might include a participant joining a call, a participant leaving a call, gathering telephony input, participant muted, participant unmated, or any suitable conference based event. Furthermore, events may be generated for actions that occur on the message-based protocols used by the call router 110. For example, an messaging events might include a message sent, message received, and message error for SMS, email, faxes, instant messaging, or micro-blogging messages.


The event router 120 of the preferred embodiment functions to connect published events with subscribers of the event. Preferably, the published event is pushed to subscribers through an open HTTP connection (a single continuous HTTP connection). The open HTTP connection functions to simplify software of a web application using the system. Alternatively, the connection may push data with HTTPS, intermittent HTTP/HTTPS connections, AMF Channel, TCP connection, UDP connection, chat protocols such as jabber, or any suitable messaging framework. The event router is preferably a server, which may be partitioned and scaled for greater capacity. The event router 120 may alternatively be a monolithic system or any suitable software or hardware device(s) for routing events between any number of event publishers and authorized subscribers. In one preferred embodiment, the event router includes an event proxy server 122 and/or a message broker 128. The event proxy server 122 preferably manages the subscriptions from a client (i.e., subscriber) and/or performs more computational intensive processes like filtering events and security. The message broker 128 preferably manages the publications and more preferably manages a subset of event publications from the call router. The event proxy server 122 is preferably part of a cluster of event proxy servers 122 that can be dynamically scaled to satisfy capacity requirements. The message broker 128 is preferably part of a cluster of message brokers 128 that can similarly be dynamically scaled to satisfy capacity requirements. A load balancer may additionally be included within the event router 120 to manage the capacity load of the various components (e.g., the event proxy servers 122 and the message brokers 128). A plurality of load balancers may be individually implemented for each component type, or a single load balancer may manage the event router 120.


The message broker 128 of the event router 120 functions to manage the publication of events. The message broker 116 (or core message distributor) preferably handles routing of events to be published. A message broker is preferably any message broker as is known in the art such as RabbitMQ or other Advanced Message Queuing Protocol (AMQP) based broker. Preferably, a plurality of message brokers 128 is used to manage the events. More preferably message brokers 128 are sharded (i.e., partitioned) according to dedicated event types (or group of event types). Events are preferably distributed to the appropriate message broker 128 based on the event type. The sharding of message brokers may alternatively be according to any suitable rule. The message brokers 128 (i.e., the shards) may additionally be hosted on different hardware or software platforms, and event type responsibilities may be adjusted when additional message brokers 128 are allocated or deallocated from the cluster of message brokers 128. The message broker 128 may alternatively be a single device for all published events or hosted on a single system. A message broker 128 preferably sends events to an event proxy server 122 that is subscribed to a particular event. A message broker 128 may additionally send an event for any number of subscriptions, where the subscriptions are managed by any suitable number of event proxy servers 122.


The event proxy server 122 of the event router 120 functions to manage the subscriptions of clients. The client preferably connects to the event proxy server 122 for establishing a subscription to an event and to receive notification of events being published through the event router 120. Events published by a message broker 128 are preferably distributed to a subscribed event proxy server 122, and the event proxy server 122 preferably sends the event to a client. The event proxy server 122 is preferably part of a plurality of event proxy servers 122 that can be automatically scaled. Additionally, an event proxy server preferably manages multiple subscriptions, and may subscribe to multiple message brokers 128. Additionally, a plurality (or series) of event proxy servers 122 may be connected to a single message broker 128 or any suitable device publishing the event for the event router 120. The plurality of event proxy servers 122 functions to increase the volume of subscriptions the event router 120 can manage. A plurality of event proxy servers 122 may alternatively be used with a partitioned message broker 128, multiple message brokers 128, or any suitable configuration. As another variation, an event proxy may have multiple subscriptions (e.g., for different clients) to a message broker 128. This multiple subscriptions may have redundancies. The event proxy server 122 may aggregate the subscriptions for improved system efficiency, as shown in FIG. 10. The event distributor 116, the message brokers 128, and the proxy servers 122 cooperate to increase the subscription capabilities of the event router. The event proxy server 122 additionally functions to perform resource intensive processes such as running an event filter or security policy engine. The event proxy server 122 is preferably a dedicated server for handling event filtering, operating the security policy engine, and/or any suitable CPU intensive tasks.


The event router 120 of the preferred embodiment may additionally include an event filter 124 that functions to selectively pass events to a client. The event filter 124 is preferably operated on an event proxy server 122. Event filters 124 selectively filter the number of events published to a particular subscriber based on account security, event type, contents, and/or any suitable parameter of the event. When a subscriber issues a subscription request, the request preferably contains a set of credentials and more preferably a set of event filters. The event router 120, more preferably the event proxy server 122, first verifies the account ownership via the credentials to determine if the subscriber is authorized to view events for the given account. Once a subscriber's identity is determined, the event router only passes events that are associated with authorized accounts. Preferably, this account-level security preferably limits visibility of events to only the relevant account or accounts, and the event filters are preferably applied after the account-level security. The event proxy server 122 preferably applies the event filters 124 to determine if the event router should publish an event to a given subscriber. The event filter 124 is preferably a type filter or a parameter filter. A type filter preferably filters event details by the type of event such as ‘call start’, ‘call end’, ‘call error’, ‘call warning’, ‘record start’, ‘record end’, ‘gather start’, ‘gather end’, ‘dial start’, ‘dial end’ and/or any suitable type of event. A parameter filter preferably filters events based on characteristics of the event such as by caller ID, contents of call, time of call, duration of call, area code of call, and/or any suitable characteristic of a call. A parameter filter may additionally filter based on the event (such as which digit was pressed by the caller, the warning message issued by the call router, or the length of a recording). Event filters 124 may be used in a variety of ways. As one example, filters may be configured to subscribe to a particular call. As another example, the filters may be configured to subscribe to all calls to and/or from a given phone number. As yet another example, the filters may be configured to subscribe to a particular telephony application action such as “call start” across an account (which may involve multiple simultaneous calls for various phone numbers). The event filter 124 may additionally function to provide a level of security. The event filter 124 preferably prevents inspection, observation, receiving, and/or gathering of any useful information concerning a subset of events. A publisher may implement a security event filter 124 for events the publisher does not want a subscriber to see or alternatively, any suitable entity may implement a security event filter 124.


The event router 120 of the preferred embodiment may additionally include a security policy engine 126 that functions to enforce a security policy governing which subscribers are allowed to subscribe to a particular event. The event proxy server 122 preferably operates the security policy engine 126. Preferably, the security policy engine 126 includes a signed URL. The signed URL is preferably composed of a subscription message and a verification token. The verification token functions to be validation of the authenticity of the subscription request. A private key shared between the client application developer and the event router is preferably used to generate the verification token and is preferably a code, password, or any suitable identifier. The verification token is preferably implemented as an HMAC (Hash Message Authentication Code) hash using the key, but may alternatively be implemented by any suitable cryptographic message authentication technique. The verification token preferably includes the subscription request including a subscription URL, subscription filters, subscription expiration time, and/or any other suitable subscription metadata or parameter. The verification token is preferably attached to the subscription request. In one preferred version, the verification token is appended to the end of a URL of the subscription message to form the signed URL. The signed URL allows the subscription request to be passed to unknown devices, such as a remote web browser, and allowing the browser to issue subscription requests without knowing the key or other information. Alternatively, other security systems such as OAuth URL signing or any suitable security method may be implemented.


The system of the preferred embodiment may also include a connection to the client device 130, which functions to be a channel through which published events that a client subscribes to can be delivered. The connection 130 is preferably any suitable network connection either wired or wireless. The connection 130 is preferably between an event router 120 and the client, and more preferably, the connection 130 is between an event proxy server 122 and the client. The connection to the client is preferably an HTTP connection but may be any suitable signaling protocol. The client device of the preferred embodiment functions to provide interaction with subscribed events. The client device may be a front-end interface of the web application. The client device preferably reacts to events and provides an interface for user interaction. The client device may be a website, a computer program, a web enabled consumer product, a server, or any suitable device. However, the client device may alternatively be a backend system such as a data collection system. A browser 132 is one common type of client. A connection with a browser is preferably implemented via Ajax in javascript (e.g., XMLHttpRequest) or via a flash plugin (e.g., XMLSocket or an AMF or SecureAMF channel). An Application Programming Interface (API) server 134 is a second common type of client. A client preferably initiates the creation of connection 130 to the event router 122. However, in the situation of an API server 134, the event router 120 or, more preferably, an event proxy server 122 may initiate the creation of a connection 130 to the client 130. There may additionally be a control channel and a publication channel. The control channel is a connection through which a client submits a subscription request. The client can manage subscriptions through the control channel. Management of subscription includes modifying an existing subscription (e.g., updating filters or changing expiration time), adding a subscription, deleting a subscription and/or any suitable subscription change. The subscription channel is the connection through which events are sent to the client. In one variation, a client may setup multiple subscriptions and/or modify subscriptions through multiple control channels or alternatively through one control channel at different times. One publication channel is preferably used regardless of the number of subscriptions of a client. This functions to reduce the number of open connection 130 between the client and the event proxy server 122. The connection 130 may be any suitable connection as mentioned above. In the case where the connection is a long poling type connection, a client preferably connects to the event proxy server 122, gets an event, and closes a connection. When the client is not connected, events may be missed by the client. The event proxy server 122 preferably includes a cache to store events (up to an expiration time) and delivers the cached events to the client during the next connection with the client.


The application server 114 of the preferred embodiment functions to provide a web developer with an improved development environment for interfacing and designing interactions for communications applications. The call router 11o preferably manages the interaction between the telephony device(s) 112 and the application server 114. Events are preferably generated by this interaction. The web application (application server) is preferably a website, but may alternatively be a computer program, a web enabled consumer product, or any suitable method or device capable of event subscription tasks. The application server 114 preferably combines telephony actions and a website to form a powerful user experience. In one example of an application server 114, a user may enter a phone number and leave audio comments for individual photos as the photos cycle through a slideshow. In a second example, a conference call can be managed through a web interface. In a third example, a customer service phone call may be managed and annotated using a web interface. In a fourth example, a business or sales phone call may be managed and supported by using a web interface. Any suitable application server utilizing telephony interaction may alternatively be used. The web application is preferably programmed in a manner similar to regular websites, but integration into the system allows for new user experiences relying on telephony actions.


The application server 114 functions to provide data processing logic for requests received from the call router 110. The application server 114 is preferably connected to the call router 110 via a network 24, more preferably via the Internet. The application server 114 is preferably a third party server operated outside of the system, but the system may alternatively include the application server 114. A URI is preferably associated with an application server 114 or an application on an application server 114. The application server 114 preferably communicates with the call router 110 using an application layer protocol, more preferably using the HTTP protocol, or more secure HTTPS protocol. The application server 114 preferably receives HTTP requests from and sends HTTP responses to the call router 110. The application server 114 preferably runs on a standard stack of programming languages, hosting providers, operating systems and databases to handle HTTP requests, as if the caller were a website visitor in a web browser. The application server 114 also preferably verifies the digital signatures of the call data received in the requests using the secret key to compute a cryptographic hash from the received information and the hash received. If the computed hash and the received hash do not match, or no hash is received with the request, then the application server 114 preferably determines the request is fraudulent, and the request is preferably discarded. If the computed hash and received hash match, the application server 114 preferably determines that the request is authentic and proceeds further with the processing of the request. The application server may alternatively choose to ignore the hash if security is not important. The application server preferably uses call state data communicated by the call router request to determine the next call router instructions, without requiring call state stored on the application server. The application server may alternatively use call state data sent by the call router, such as the caller ID of the caller or the unique ID of the call, to reference additional or external state data, such as rows in a database or session data stored on the application server.


The application server 114 preferably responds to HTTP requests received from the call router 110 by generating telephony instructions for the call router 110. Telephony instructions when executed by the call router preferably cause an event to be detected by the call router 110. The application server preferably replies to the call router in XML, however, any suitable machine-readable message format may be used, including HTML, key/value pair text, delimited text or binary encoding. The XML preferably includes the telephony instructions for the call router 110 such as connecting to another number, playing a recorded greeting, reading text, and/or requesting DTMF digit entry from the caller. The telephony instruction may alternatively be related to SMS messaging, Multimedia Messaging Service (MMS) messaging, faxes, instant messages, email, micro-blogging, or any suitable messaging task. The telephony instruction may additionally be used to send an outgoing SMS message, arrange a phone call from a specific phone number, arranging for a callback, setting up a conference call (connecting multiple numbers), sending an email, interfacing with a calendar or scheduling system, purchasing goods, or services, or any other suitable instruction. The XML instructions are preferably a set of commands to be executed in order, one at a time (i.e., sequentially). An example XML response is shown in FIGS. 9A and 9B. In single telephony session (e.g. one initiated by a PSTN-device or an SMS device), a response from an application server can initiate an outgoing telephony call and/or a SMS message. That is, a single XML response preferably provides the ability to interact with both the SMS network and the voice telephony network (PSTN, SIP/VoIP, etc) sequentially or simultaneously. In addition, audio or video files sent to the call router 110 can be converted to text by an automatic speech-to-text engine, human or other technique, and sent back in text form as an SMS message or an attachment to an MMS. In one variation, an application running on a server may be a simple static XML page and static sound files, deployed on basic web servers where no development or scripting environment is available. This variation preferably uses URI Templates (a current IETF proposal for HTML5), which essentially includes URLs with placeholders for variable data, like this: http://www.twilio.com/audio/{Digit}.mp3 where the call router 110 would substitute the digits pressed for the {Digit} placeholder in the URI Template, GET the file at the resulting URI, and play the static sound file in response. This allows an entire application to be authored offline in a What-You-See-Is-What-You-Get (WYSIWYG) html editor. For example, if the server response specifies the URI Template: http://demo.twilio.com/myapp/{Digits}.mp3, and the caller presses digits 1234, the call router 110 would GET the static mp3 file located at: http://demo.twilio.com/myapp/1234.mp3 and play it to the caller. The variables used for substitution in the URI Templates preferably correspond to the names of variables defined for state submission in HTTP GET, POST and/or header requests from the call router. From the previous example, {Digits} would be associated with a parameter named “Digits” that is preferably generated as a result of a “gather” telephony instruction (collection of DTMF digits). In the preferred embodiment for the second configuration, the call is initiated by the application server 114 (through the call router 110), and the second configuration is substantially similar to the first configuration, such that the call routing is preferably handled identically to an incoming call, namely via URI requests from call router 110 to the server 114 upon call state changes.


As an additional alternative, the system may be implemented to be full duplex where events (client events) may additionally be published from a client and the call router can subscribe to the client events as shown in FIG. 7. In this alternative, the event router additionally manages the publication of client events and manages call router subscriptions to client events. The system is preferably implemented in substantially the same way as above, but with the client additionally generating events and the call router subscribing to events. The client event system is preferably integrated with the eventing system described above.


2. Telephony Web Event Method


As shown in FIGS. 3-6, the method of event subscription for telephony applications includes distributing events S100 and subscribing to events S200. Distributing events preferably includes the sub-steps publishing an event to a router S110, identifying subscribers to an event S120, and sending an event to a subscriber S130. Subscribing to events includes the sub-steps of generating a signed URL for an event subscription S210, sending an event subscription request to an event router S220, verifying an event subscription S230, and allowing an event subscription S240. The method may additionally include allocating new resources to the event router. In particular event proxy servers and message brokers may be allocated or deallocated. Additionally, call routers, event distributors, and/or any suitable part device of the system may be allocated or scaled to accommodate capacity needs. A load balancer may additionally distribute processing across the plurality of components.


As an alternative, the method may additionally include receiving a subscriber generated client event, publishing the client event to the event router and identifying a call router subscribed to a client event, and sending the client event to the call router. This functions to make the eventing method full duplex for two way event publication and subscription. The duplex eventing system is substantially similar to the eventing system described, but where the client generates the events and the call router is subscribed to the events.


2A. Method of Publishing an Event


Step S110, which includes publishing an event to a router, functions to initiate the announcement of an event. Event details are preferably sent to an event router at a URL or other suitable resource or connection identifier. Event details preferably include account identification, event type, any event data associated with the event, and any other suitable parameters relating to the event. Publishing to a router preferably occurs after a new event occurs, but alternatively, a batch of events may be published periodically, a batch of events may be published when an event count is satisfied, an event may be published when an event type is satisfied, or any suitable event publishing rule may be applied. An event is preferably generated from a telephony application operating on a call router. The telephony application is preferably substantially similar in functionality to the one described above. A call router preferably publishes an event to an event router. The event is preferably published over HTTP, but any suitable protocol may be used. An event distributor may additionally select a message broker to send the event. A plurality of message brokers may be sharded according to event types and the event distributor preferably is capable of mapping the event to the appropriate message broker.


Step S120, which includes identifying subscribers to an event, functions to identify all authorized subscribers that should be notified that the event occurred. The subscribers are preferably associated with a subscription URL. Any suitable number of subscribers is preferably identified, and subscribers are preferably identified by inspecting a list of subscribers. The subscribers may alternatively be associated with a group of other subscribers, and a group (or groups) may be identified as a subscriber. Identifying subscribers is preferably performed by an event router, and more preferably an event proxy server in cooperation with a message broker, though any suitable device may be used. Preferably, an event proxy server performs the steps of managing a subscription of a client (subscriber) and subscribing to an event publication of the event router. The event proxy server preferably subscribes on behalf of a client, so that subscription processing can be delegated to the event proxy server. More preferably a message broker performs the steps of publishing the event. So that the event proxy server subscribes to a message broker. Identifying subscribers of an event may include a sub-step of verifying event filters. An account-level security may additionally be enforced by the event router to limit the visibility of events to only relevant accounts. The event is compared to filters of a subscriber to ensure the subscriber should be sent the event. The filters are preferably type filters or parameter filters as discussed above.


Step S130, which includes publishing an event to a subscriber, functions to notify a subscriber of the occurrence of an event. The event is preferably published by an event router over an open HTTP connection, but alternatively, a periodic HTTP connection, messaging framework such as Jabber, or any suitable communication protocol may be used. In the situation where a client has previously broken a connection with the event router (i.e., is not connected to the event router at the time an event occurs), the event proxy server preferably establishes a connection to the subscriber. The event proxy server preferably establishes the connection by accessing the stored address of the client and connecting through any suitable protocol. In the case the subscriber is an API server, an API command may be used to connect or notify the API server of the event.


2B. A Method of Subscribing to an Event


Step S210, which includes generating a signed URL for an event subscription, functions to generate a URL encoding any subscription URL, filter, and/or identification information. An unsigned URL is preferably generated including account identification, subscription URL, subscription filters, subscription expiration time, and/or any other suitable subscription metadata or parameter. Preferably, a key is looked up based on the account identification. The key is used to create a verification token. The verification token is preferably implemented as an HMAC-SHA1 (Hash Message Authentication Code) hash using the key or any suitable another cryptographic message authentication technique may be used. The verification token additionally includes the subscription request including a subscription URL, subscription filters, subscription expiration time, and/or any other suitable subscription metadata or parameter. The verification token is preferably appended to the unsigned URL to form a signed URL. The signed URL is preferably integrated into a subscription request. The subscription request is preferably a request to receive particular events of a telephony application.


Step S220 includes sending a subscription request to an event router. The subscription request is preferably sent to an event router by HTTP protocol, but any suitable protocol may alternatively be used. The subscription request is preferably received by an event router, and more preferably is received by an event proxy server. The event proxy server preferably manages subscriptions.


Step S230, which includes verifying an event subscription, functions to verify the identity of a subscriber. The signed URL of the event is preferably deconstructed to identify account identification, subscription URL, subscription filters, subscription expiration time, and/or any other suitable subscription metadata or parameter. The event router preferably verifies that the account identification is included in the signed URL or other authentication credentials. If no account identification is found, the subscription request is discarded and an error is returned. If the identification information is included a key for the account is looked up (i.e. found in a database). The key is preferably a shared key that is identical to the key of Step S210. The key is then used to form a verification token. The verification token is preferably a HMAC hash, or alternatively any suitable cryptographic message or identifier. The verification token is compared to the verification token from the signed URL to verify the match.


Step S240, which includes allowing an event subscription, functions to allow a client to subscribe to an event. A subscription preferably allows a client to receive events in real time (approximately a few milliseconds to a few seconds). An event subscription also only allows events that are authorized to be viewed by the account, such as events generated by calls on that account. More preferably, the events preferably pass any filters of a subscriber. As an additional alternative, subscriptions may expire after a given time. As part of Step S240, the method includes the event proxy server (or event router) configuring filters for the subscription. This step functions to setup processing operations of the subscription. Additionally, any suitable subscription setup that must be performed is additionally performed. In the variation where the subscriber previously has a subscription, the previous subscription may be modified to include the new subscription details. Events from multiple subscriptions of one subscriber are preferably sent to the subscriber through a single connection as described above. In the situation where a subscriber is not connected to the event router when an event occurs the event proxy server or any suitable device may queue or cache the events for delivery when the subscriber next establishes a connection.


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.

Claims
  • 1. A method comprising: establishing a subscription by a subscriber for events associated with an action type;receiving, at a system, an application instruction of an application server that is external to the system, the application instruction received using an application programming interface (API) via a network, the application instruction being an instruction of an account of a plurality of accounts of the system;in response to receiving the application instruction, performing an action;publishing an event corresponding to the action to an event router of the system, the published comprising an identification of the account; andbased on a type of the action, sending the published event from the event router to the subscriber.
  • 2. The method of claim 1, wherein: the subscriber has permission to receive information for the type of the action.
  • 3. The method of claim 1, wherein: the published event comprises an identification of the type of the action.
  • 4. The method of claim 3, wherein: the sending of the published event from the event router to the subscriber is based on the published event comprising the identification of the type and the identification of the account.
  • 5. The method of claim 1, wherein: the subscription includes a parameter filter that comprises an identification of a characteristic of the published event.
  • 6. The method of claim 1, further comprising: sending the published event from the event router to the application server.
  • 7. The method of claim 1, wherein the event router comprises a plurality of message brokers arranged according to one or more event types.
  • 8. The method of claim 1, wherein the sending of the published event from the event router to the subscriber comprises sending the published event through an open Hypertext Transport Protocol (HTTP) or HTTP Secure (HTTPS) connection.
  • 9. The method of claim 1, further comprising: receiving a request from a second subscriber for events associated with the type of action; andbased on a security policy, rejecting the request.
  • 10. The method of claim 1, wherein the sending of the published event from the event router to the subscriber is further based on the action type.
  • 11. A system comprising: a memory that stores instructions; andone or more processors configured by the instructions to perform operations comprising: establishing a subscription by a subscriber for events associated with an action type;receiving an application instruction of an application server that is external to the system, the application instruction received using an application programming interface (API) via a network, the application instruction being an instruction of an account of a plurality of accounts of the system;in response to receiving the application instruction, performing an action;publishing an event corresponding to the action to an event router of the system, the published event comprising an identification of the account; andbased on a type of the action, sending the published event from the event router to the subscriber.
  • 12. The system of claim 11, wherein: the subscriber has permission to receive information for the type of the action.
  • 13. The system of claim 11, wherein: the published event comprises an identification of the type of the action.
  • 14. The system of claim 13, wherein: the sending of the published event from the event router to the subscriber is based on the published event comprising the identification of the type and the identification of the account.
  • 15. The system of claim 11, wherein: the subscription includes a parameter filter that comprises an identification of a characteristic of the published event.
  • 16. The system of claim 11, wherein the operations further comprise: sending the published event from the event router to the application server.
  • 17. The system of claim 11, wherein the event router comprises a plurality of message brokers arranged according to one or more event types.
  • 18. A non-transitory machine-readable medium that stores instructions that, when executed by one or more processors of a system, cause the system to perform operations comprising: establishing a subscription by a subscriber for events associated with an action type;receiving an application instruction of an application server that is external to the system, the application instruction received using an application programming interface (API) via a network, the application instruction being an instruction of an account of a plurality of accounts of the system;in response to receiving the application instruction, performing an action;publishing an event corresponding to the action to an event router of the system, the published event comprising an identification of the account; andbased on a type of the action, sending the published event from the event router to the subscriber.
  • 19. The machine-readable medium of claim 18, wherein: the subscriber has permission to receive information for the type of the action.
  • 20. The machine-readable medium of claim 18, wherein: the published event comprises an identification of the type of the action.
CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 16/557,001, filed on 30 Aug. 2019, which is a continuation of U.S. patent application Ser. No. 16/241,746, filed 7 Jan. 2019, which is a continuation of U.S. patent application Ser. No. 15/709,905, filed 20 Sep. 2017, which is a continuation of U.S. patent application Ser. No. 15/193,416, filed 27 Jun. 2016, which is a continuation of U.S. patent application Ser. No. 14/591,279, filed 7 Jan. 2015, which is a continuation of U.S. patent application Ser. No. 12/572,258, filed 1 Oct. 2009, which claims the benefit of U.S. Provisional Application No. 61/102,007 filed on 1 Oct. 2008, all of which are hereby incorporated in their entirety by this reference.

US Referenced Citations (805)
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
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 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
6798772 Bergman 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
7133518 Sayko et al. Nov 2006 B2
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
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
7461263 Prince Dec 2008 B2
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
8086650 Milford Dec 2011 B1
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
8204052 Baldwin 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
8549639 Newman 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
8712372 Cesarini Apr 2014 B2
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
9104773 Gandhi Aug 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
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
9390418 Gavan et al. Jul 2016 B2
9398622 Lawson et al. Jul 2016 B2
9407597 Lawson et al. Aug 2016 B2
9456008 Lawson et al. Sep 2016 B2
9456339 Hildner et al. Sep 2016 B1
9460169 Hinton et al. Oct 2016 B2
9553940 Oh et al. Jan 2017 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
9807244 Lawson et al. Oct 2017 B2
10187530 Lawson Jan 2019 B2
10455094 Lawson Oct 2019 B2
11005998 Lawson May 2021 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
20040019676 Iwatsuki 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 Matenda 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 Mansour 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
20050283353 Billingsley et al. Dec 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
20090022131 Chen et al. Sep 2009 A1
20090220057 Waters 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
20090300165 Tuckey et al. Dec 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
20100029191 Sanding et al. Nov 2010 A1
20100281108 Cohen 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
20110014981 Koren et al. Jun 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
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
20120017361 Bleau et al. Jul 2012 A1
20120170726 Schwartz 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
20140037251 Fausak et al. Dec 2014 A1
20140355600 Lawson et al. Dec 2014 A1
20140372508 Fausak et al. Dec 2014 A1
20140372509 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
20150127723 Lawson et al. May 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
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
20160309039 Lawson et al. Oct 2016 A1
20170339283 Chaudhary et al. Nov 2017 A1
20180013895 Lawson et al. Jan 2018 A1
20190215401 Lawson et al. Jul 2019 A1
20200076952 Lawson et al. Mar 2020 A1
20210218847 Lawson et al. Jul 2021 A1
20210218848 Lawson et al. Jul 2021 A1
Foreign Referenced Citations (22)
Number Date Country
102227904 Oct 2011 CN
1684587 Mar 1971 DE
0282126 Sep 1988 EP
1464418 Oct 2004 EP
1522922 Apr 2005 EP
1770586 Apr 2007 EP
2053869 Apr 2009 EP
2335402 Jun 2011 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
Non-Patent Literature Citations (52)
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. 12/572,258, Examiner Interview Summary dated Apr. 17, 2013”, 4 pgs.
“U.S. Appl. No. 12/572,258, Examiner Interview Summary dated Jul. 16, 2014”, 3 pgs.
“U.S. Appl. No. 12/572,258, Final Office Action dated Oct. 17, 2012”, 30 pgs.
“U.S. Appl. No. 12/572,258, Non Final Office Action dated Jan. 20, 2012”, 28 pgs.
“U.S. Appl. No. 12/572,258, Non Final Office Action dated Mar. 13, 2014”, 30 pgs.
“U.S. Appl. No. 12/572,258, Notice of Allowance dated Oct. 7, 2014”, 10 pgs.
“U.S. Appl. No. 12/572,258, Response filed Apr. 17, 2013 to Final Office Action dated Oct. 17, 2012”, 11 pgs.
“U.S. Appl. No. 12/572,258, Response filed Jun. 19, 2012 to Non Final Office Action dated Jan. 20, 2012”, 11 pgs.
“U.S. Appl. No. 12/572,258, Response filed Jul. 14, 2014 to Non Final Office Action dated Mar. 13, 2014”, 9 pgs.
“U.S. Appl. No. 12/572,258, Supplemental Notice of Allowability dated Nov. 21, 2014”, 3 pgs.
“U.S. Appl. No. 14/591,279, Final Office Action dated Feb. 26, 2016”, 19 pgs.
“U.S. Appl. No. 14/591,279, Non Final Office Action dated Oct. 7, 2015”, 20 pgs.
“U.S. Appl. No. 14/591,279, Notice of Allowance dated Apr. 13, 2016”, 5 pgs.
“U.S. Appl. No. 14/591,279, Preliminary Amendment filed May 14, 2015”, 8 pgs.
“U.S. Appl. No. 14/591,279, Response filed Jan. 25, 2016 to Non Final Office Action dated Oct. 7, 2015”, 8 pgs.
“U.S. Appl. No. 14/591,279, Response filed Mar. 28, 2016 to Final Office Action dated Feb. 26, 2016”, 8 pgs.
“U.S. Appl. No. 15/193,416, Final Office Action dated May 22, 2017”, 9 pgs.
“U.S. Appl. No. 15/193,416, Non Final Office Action dated Dec. 29, 2016”, 7 pgs.
“U.S. Appl. No. 15/193,416, Notice of Allowance dated Jun. 20, 2017”, 5 pgs.
“U.S. Appl. No. 15/193,416, Notice of Allowance dated Sep. 27, 2017”, 2 pgs.
“U.S. Appl. No. 15/193,416, Response filed Mar. 29, 2017 to Non Final Office Action dated Dec. 29, 2016”, 6 pgs.
“U.S. Appl. No. 15/193,416, Response filed Jun. 2, 2017 to Final Office Action dated May 22, 2017”, 5 pgs.
“U.S. Appl. No. 15/709,905, Non Final Office Action dated Apr. 11, 2018”, 14 pgs.
“U.S. Appl. No. 15/709,905, Notice of Allowance dated Sep. 10, 2018”, 9 pgs.
“U.S. Appl. No. 15/709,905, Response filed Jul. 23, 2018 to Non Final Office Action dated Apr. 11, 2018”, 9 pgs.
“U.S. Appl. No. 16/241,746, Notice of Allowance dated May 31, 2019”, 10 pgs.
“U.S. Appl. No. 16/241,746, Preliminary Amendment filed Apr. 1, 2019”, 6 pgs.
“U.S. Appl. No. 16/557,001, Non Final Office Action dated Jul. 8, 2020”, 14 pgs.
“U.S. Appl. No. 16/557,001, Notice of Allowance dated Jan. 13, 2021”, 8 pgs.
“U.S. Appl. No. 16/557,001, Response filed Oct. 6, 2020 to Non Final Office Action dated Jul. 8, 2020”, 12 pgs.
“Archive Microsoft Office 365 Email I Retain Unified Archiving”, GWAVA, Inc., Montreal, Canada, [Online] Retrieved from the Internet: <URL: 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: <URL: http://blackboxcanada.com/resource/files/productdetails/17044.pdf>, (Oct. 1999), 2 pgs.
“European Application Serial No. 09818540.8, Extended European Search Report dated Mar. 21, 2013”, 6 pgs.
“International Application Serial No. PCT/US2009/059300, International Preliminary Report on Patentability dated Apr. 14, 2011”, 7 pgs.
“International Application Serial No. PCT/US2009/059300, International Search Report dated Jan. 11, 2010”, 2 pgs.
“International Application Serial No. PCT/US2009/059300, Written Opinion dated Jan. 11, 2010”, 5 pgs.
“Twilio Cloud Communications—APIs for Voice, VoIP, and Text Messaging”, Twilio, [Online] Retrieved from the Internet: <URL: 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.
“U.S. Appl. No. 17/301,330, Non Final Office Action dated Aug. 23, 2022”, 15 pgs.
“U.S. Appl. No. 17/301,335, Non Final Office Action dated Sep. 16, 2022”, 17 pgs.
“U.S. Appl. No. 17/301,330, Response filed Nov. 22, 2022 to Non Final Office Action dated Aug. 23, 2022”, 9 pgs.
“U.S. Appl. No. 17/301,330, Examiner Interview Summary dated Nov. 22, 2022”, 2 pgs.
“U.S. Appl. No. 17/301,335, Examiner Interview Summary dated Nov. 22, 2022”, 2 pgs.
Related Publications (1)
Number Date Country
20210218846 A1 Jul 2021 US
Provisional Applications (1)
Number Date Country
61102007 Oct 2008 US
Continuations (6)
Number Date Country
Parent 16557001 Aug 2019 US
Child 17301323 US
Parent 16241746 Jan 2019 US
Child 16557001 US
Parent 15709905 Sep 2017 US
Child 16241746 US
Parent 15193416 Jun 2016 US
Child 15709905 US
Parent 14591279 Jan 2015 US
Child 15193416 US
Parent 12572258 Oct 2009 US
Child 14591279 US