System and method for real-time communication by using a client application communication protocol

Description

TECHNICAL FIELD

This invention relates generally to the telephony field, and more specifically to a new and useful system and method for communication with a client application in the telephony field.

BACKGROUND

In recent years, telephony applications and Voice over Internet Protocol (VoIP) have found applications in numerous settings. Such technology has enabled clients to establish communication to outside devices such as phones or applications. However, the nature of most network configurations requires usage of a traditional mobile telephony or landline telephony platform. This seriously limits the type of applications of internet-based telephony. Additionally, real-time communication on the internet has become possible through numerous advancements. Such possibilities have in part been brought about by the browser support of real-time protocols. One such protocol is WebRTC, which provides javascript APIs for real-time communication capabilities in a web browser. One problem with real-time communication is that other real-time communication protocols are available and there is no ubiquitous solution. This limits the functionality available through the WebRTC protocol alone. Thus, there is a need in the telephony field to create a new and useful system and method for real time communication with a client application, such that the client can utilize an Internet browser and/or native application on a computer and/or mobile device for making and/or receiving real time communications. This invention provides such a new and useful system and method.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 is a flowchart depicting a first method for connecting a communication to a client in accordance with a preferred embodiment;

FIG. 2 is schematic representations of preferred method for connecting a communication to a client in accordance with a preferred embodiment;

FIG. 3 is a flowchart depicting a variation of the first preferred method for connecting a communication to a client;

FIG. 4 is a flowchart depicting another variation of the first preferred method for connecting a communication to a client;

FIG. 5 is a flowchart depicting another variation of the first preferred method for connecting a communication to a client;

FIG. 6 is schematic representations of preferred methods for connecting a communication to a client in accordance with a preferred embodiment;

FIG. 7 is a flowchart depicting another variation of the first preferred method for connecting a communication to a client;

FIG. 8 is a flowchart depicting another variation of the first preferred method for connecting a communication to a client;

FIG. 9 is a flowchart depicting a second method for connecting a communication to a client in accordance with a preferred embodiment;

FIG. 10 is a schematic representation depicting a variation of the second preferred method for connecting a communication a communication to a client;

FIG. 11 is a schematic representation depicting another variation of the second preferred method for connecting a communication a communication to a client;

FIG. 12 is a is a flowchart depicting a variation of the second preferred method for connecting a communication to a client;

FIG. 13 is a is a flowchart depicting another variation of the second preferred method for connecting a communication to a client;

FIG. 14 is a schematic block diagram of a system for connecting a communication to a client in accordance with a preferred embodiment;

FIG. 15 is a schematic block diagram of another system for connecting a communication to a client in accordance with a preferred embodiment;

FIG. 16 a schematic block diagram of a system for connecting a call in accordance with a preferred embodiment of the present invention;

FIG. 17 is a schematic block diagram of a mobile architecture operable in the system for connecting a call of the preferred embodiment of the present invention;

FIG. 18 is a schematic diagram of a method for making an outgoing media channel communication from a client application in accordance with a preferred embodiment of the present invention;

FIG. 19 is a schematic diagram of a method for sending an outgoing message from a client application in accordance with a preferred embodiment of the present invention;

FIG. 20 is a schematic diagram of a method for establishing a media channel communication with a client application in accordance with a preferred embodiment of the present invention;

FIG. 21 is a schematic diagram of a method for sending a message communication to a client application in accordance with a preferred embodiment of the present invention;

FIG. 22 is a schematic diagram of a system bridge acting as a gateway between different signaling and media channels;

FIG. 23 is a schematic diagram of signaling and media channels merging between a client application and a communication platform;

FIG. 24 is a schematic diagram of signaling and media channels merging between a client application and a PSTN phone;

FIG. 25 is a schematic diagram of signaling and media channels merging between a client application and a SIP device;

FIG. 26 is a communication flow diagram of a client application making an outgoing call; and

FIG. 27 is a communication flow diagram of a client application receiving an incoming call.

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. Method for Connecting a Client

As shown in FIGS. 1 and 2, a first preferred method for connecting a communication to a client of a preferred embodiment can include: at a system bridge, establishing a client subscription connection with a client device in block S100; receiving an incoming communication request at the system bridge in block S102; publishing an incoming communication notification from the system bridge to the client device in block S104; receiving a client communication at the system bridge in block S106; and merging the incoming communication request into the client communication at the system bridge in block S108. The first method preferably functions to connect incoming communications to a client utilizing a subscription connection that prompts a client to call out. The first method preferably creates a substantially persistent channel of communication such that a client can actively establish a connection when an incoming message arrives, which in turn preferably enables web services, mobile devices, and platforms that want to implement features for incoming communications to circumvent incoming communication issues caused by firewalls and routers. In one alternative implementation of the first preferred method, client communication is preferably initiated by a client as opposed to a client directly responding to a received incoming call. The client application can selectively utilize different real time protocol mechanisms to establish communication. The system bridge can bridge a client application (e.g., a native application or browser application) with a communication platform such as the telephony application platform described in published U.S. Patent Application No. 2009/0252159, titled “SYSTEM AND METHOD FOR PROCESSING TELEPHONY SESSIONS”, which is incorporated in its entirety by this reference.

Preferably, the first preferred method can employ authentication and/or authorization security measures that function to secure the communication channels. An authentication layer preferably prevents malicious parties from posing as a client and/or incoming call. In one embodiment, an application (web or native) may facilitate the use of a token to authenticate a client connecting to an incoming call. The first preferred method is preferably used within internet-telephony platform, but may alternatively be used for any suitable applications such as Internet messaging or real-time applications that may need to establish an incoming communication channel. The method can be configured and/or adapted to function for any suitable type of communication, including telephony-based voice calls, Internet based voice calls, video calls, video streams, video sessions, screen sharing, screen sharing streams, screen sharing sessions, SMS messaging, IP messaging, alternative messaging, or any suitable form of communication. The term call should be understood to include any suitable application communication session, and any suitable form of incoming communication to a client may be received and merged with the client through this method, such as video, screen sharing, chat, or text messaging.

As shown in FIG. 1, the preferred method can include block S100, which recites at the system bridge, establishing a client subscription connection with a client device. Block S100 preferably functions to create a substantially persistent connection between the client and the system bridge. The client subscription connection is preferably a publication/subscription Internet communication channel that can be used to push incoming call notifications to the client. The client subscription can be used as a signaling channel between the client device and the system bridge. The system bridge can function as a signaling and media gateway that bridges client real time communication with that of a communication system or other endpoint. In one variation, the communication system will use an internal communication scheme with an internal signaling (e.g., SIP) and media (e.g., RTMP with a PCMU codec). The system bridge can manage interface of real time communication with various client applications and the internal communication of a communication platform. The subscription channel can include one or more websockets, an HTTP server push, an Adobe flash socket, ajax long polling, ajax multipart streaming, a forever iframe, jsonp polling, Comet, XMPP, BOSH, or any suitable communication technology to facilitate a client subscription. The subscription connection is preferably persistently maintained. The client preferably establishes a client subscription connection by initially registering a subscription channel and then subscribing to that channel. The channel is preferably subscribed to using a method substantially similar to method for connecting a client to an application described below where the use of a token is used. Alternatively, any suitable technique to subscribe may be used. Once registered, the system bridge will preferably publish a notification to that subscription. The subscription connection is preferably established between a client and a system bridge through a pubsub system, but any suitable subscription connection may be used. A client identifier is preferably created which may be used for the subscription channel but additionally as a handle or mapping for addressing incoming calls. The client identifier is preferably specified by the client, but may alternatively be an automatically assigned client identifier. The client identifier preferably includes a client ID, which may be signed with a shared secret. The client identifier may include various scopes that may take form as subdirectories or hierarchical layers of contexts. For example, one name space of “foo” may have a subdirectory of “foo/mobile” and a second subdirectory of “foo/web”. In this example, “foo/mobile” may be registered for a mobile device client and “foo/web” may be registered for a desktop browser session. Incoming calls can preferably address these devices individually by using “foo/mobile” or “foo/web”. Additionally, an incoming call may be simultaneously directed at both clients by using “foo/*”. Additional attributes can be assigned to the name-spaced endpoint or to different scopes of the name-spaced endpoint. Additionally the client identifiers may be used to broadcast to multiple clients. Clients can preferably subscribe to client identifiers. For example a plurality of clients may subscribe to “foo” and each receive a request sent to “foo”.

Block S102, which recites receiving an incoming communication request at the system bridge, functions to accept a communication from an outside entity (i.e., the caller) directed to a client. The incoming call may have any suitable source. A cloud-based communication router preferably initially receives/initiates the incoming communication. The cloud-based communication router is preferably a call router call router of a telephony platform such as one substantially similar to the one described in published U.S. Patent Application No. 2009/0252159, titled “SYSTEM AND METHOD FOR PROCESSING TELEPHONY SESSIONS”, which is hereby incorporated in its entirety by this reference, but the cloud-based communication router may alternatively be any suitable communication router. Alternatively, the system bridge may be integrated into the cloud-based router or call router architecture or alternatively into any suitable communication framework. The incoming call preferably specifies an identifier, and more preferably, the incoming call specifies a name-spaced client identifier. The identifier preferably corresponds to a client or more preferably a subscription channel. In one variation, the client may vary depending on what user devices are active, and thus the identifier is preferably not specific to a particular client device (e.g., addressing to “foo/*”). The identifier is preferably unique to a user, account, session, or any suitable entity. Preferably using the identifier, a subscription is identified and an incoming communication notification is generated for publishing in block S104. While the client is notified and calls out, the system bridge preferably puts the incoming communication into a holding-state. The holding state is preferably a temporary state where the incoming communication is received by the system bridge but the client (e.g., the callee) has not initiated an outgoing communication to connect to the caller. When the system bridge is ready to merge the incoming communication to a client, the incoming communication is pulled from the holding-state.

In one variation, a service can facilitate identifying the signaling subscription of a client device. The identifier preferably includes an account identifier and a client identifier. The client identifier can be assigned to a device or automatically assigned. For example, if an outside developer designs a client application to establish a client real time communication connection, the developer could assign the connection an identifier that identifies that user within the developer's system (e.g., a username). A client device can maintain multiple signaling subscriptions and thus multiple client identifiers can refer to a single client device. Similarly, multiple client devices can share common client identifiers if multiple client devices want to maintain multiple communication endpoints in parallel. The signaling subscription identification service can accept the identifier and then can specify the appropriate system bridge or alternatively route the request to the appropriate system bridge. Client communication can be limited to within an account or a sub-account of the communication platform, but client communication can alternatively occur across different accounts if the identifier is generalized to enable inter-account client addressing. For example, the name space of client identifiers can be scoped by account/application identifiers. For example, “foo@client.app1.example.com” could be used to specify a client connection ‘foo’ made through app1 on the example.com communication platform.

Block S104, which recites publishing an incoming communication notification from the system bridge to the client device, functions to push a message to the client through the subscription channel. The client subscription channel preferably facilitates simple notification because the connection is substantially persistent and the outside entity is not required to independently establish the connection. There may additionally be a plurality of clients subscribed to the subscription channel, and the incoming communication notification may be published to a plurality of clients. The incoming communication notification is preferably sufficient to initiate a client communication sent to the system bridge by the client. Alternatively, the communication notification may include additional parameters such as keys to authenticate the message is from the system bridge, call URI's to direct a call out, caller metadata, and/or any suitable parameter. The signaling communication from the system bridge can be any suitable form of signaling protocol. In one implementation, the signaling communication is made through a websocket and uses JSON or other data serialization format to approximate SIP or other suitable protocols used to control multimedia communication sessions. The system bridge may additionally pass opaque data (from the perspective of the client) to the client. This data is preferably passed along when the client connects back in. In one variation, block S104 may include pushing a communication token from the system bridge to the client S110 as shown in FIG. 3. The passed communication token may be used to later identify which incoming communication to connect with the client communication. The communication token preferably includes a communication ID and a host (identifier for the instance) that allows the incoming communication to be uniquely identified across multiple bridge nodes. Block Silo preferably includes encrypting the communication token with a key unique to the system bridge in block S112 and as shown in FIG. 4. The variation preferably includes receiving the encrypted communication token at the system bridge from the client and decrypting the encrypted communication token at the system bridge in Block S114 as shown in FIG. 5. The passing of a communication token functions to remove the need for an external state, unnecessary because the state is preferably contained in the system bridge token. As described below, the communication token is preferably passed back to the system bridge from the client, and the communication token is then decrypted with the bridge system secret and the call (or connection) bridged as shown in FIG. 15. When there is a plurality of system bridges used in a scale infrastructure, the token preferably indicates which system bridge to pass the client communication message. If the subscription channel is encrypted and authorized, then the token may additionally function to provide security for incoming connections.

Block S106, which recites receiving a client communication at the system bridge, functions to have the client call out to the system bridge to be merged with the incoming communication. The client, upon receiving the communication notification from block S104, preferably initiates forming connections to the system bridge. The client may be any suitable device with a network connection to the system bridge. The client device may be running a native application or alternatively a web application. The call out message is preferably communicated through HTTP or HTTPS but any suitable application transport layer may alternatively be used. Any additional parameters from the client are preferably included in a message to the system bridge as appropriate, such as an application identifier or application data. The application identifier is preferably a name-spaced endpoint. A name spaced endpoint is preferably a context that embodies various aspects for the endpoint (e.g., a client). Name-spaced endpoints preferably include a plurality of parameters including associated phone numbers, application URI's, status callback URI's (e.g., backup URI's if communication with a client application fails), or any suitable parameter. A name-spaced endpoint may be globally or locally unique for a given user. For example, a name-spaced endpoint may be unique for all communication occurring over a platform or protocol. The name-spaced endpoint may alternatively, be unique for an instance of an application. Allowed users, pricing models, account-application settings, and/or any suitable aspects can be stored as part of the name-spaced endpoint. For example, only particular users may be allowed to call in or use a particular scope of a name-spaced endpoint while a second scope may be publicly accessible.

Additionally or alternatively, security measures are taken to authenticate the message from the client to the system bridge as shown in FIG. 6. Block S108 preferably includes authenticating the client communication at a policy engine S116 as shown in FIG. 7. The policy engine preferably authenticates a client communication from the client prior to merging the incoming communication. The policy engine preferably authenticated the client by using a token associated with the client and analyzing a signed client communication from the client. If the client communication satisfies the authentication, a preferred embodiment preferably includes merging the incoming communication request into the client communication at the system bridge in response to client authentication at the policy engine S118 as shown in FIG. 8. If the client communication fails to satisfy the authentication, an error may be logged and any suitable error response may be taken. Preferably, the token is sent from the client. In one variation, the client has an embedded token from when an application was instantiated. In another variation, a communication can be made to an authentication application to retrieve a token. Alternatively, a client identifier is sent to a policy engine that has an authentication application authenticate the credentials of the client identifier. Similarly a SIP backend authentication may alternatively be used. The authentication may occur for registration and/or outbound communications. The token preferably includes an application ID and any additional parameters. The contents of a token are preferably signed with a secret key. A policy engine preferably completes authentication of the token before allowing a connection to the system bridge. A policy engine preferably mediates the call out requests and authenticates any tokens, and may additionally verify permissions associated with application identifiers. Any suitable alternative forms of authentication may alternatively or additionally be integrated into the method.

Block S108, which recites merging the incoming communication request into the client communication at the system bridge, functions to connect the incoming communication request to the client. Once the client sends a client communication to the system bridge, the system bridge preferably identifies the corresponding incoming communication and establishes the communication channel between the client and the outside entity of the incoming communication. The incoming communication is preferably moved out of the holding-state and added to an active channel of communication with the intended client. Upon establishing the connection, the client and the outside entity can preferably continue to use the established connection for communication. For example, a VoIP call made to the system bridge may be connected to a client device, and then a VoIP session can preferably continue to use the channel established by the preferred method. The connection may be any suitable form of connection including a number of channels that may include audio, video, messaging, screen sharing, or any suitable channel for communication. Merging the incoming communication into the client communication at the system bridge can additionally include merging, bridging, or connecting a first real time media communication channel (i.e., the client device to system bridge leg) and a second real time media communication channel (i.e., system bridge to outside communication system leg), which can function to support multiple real time protocols. The first and second legs can be of different types of media communication channels. In an implementation where the client device is operating through a web browser, the real time media communication may include WebRTC, Flash, and/or any suitable mechanism. The outside communication system could be a communication platform as described above using another media communication approach such as using SIP. Merging the first and second real time media communication channels can include transcoding media between the first and second media communication channels as shown in FIG. 22. Various codecs may be used in different legs of the media channels. The transcoding preferably converts media to a codec appropriate for the destination channel. For example, an opus codec could be used over WebRTC and PCMU used within a communication platform. A transcoding service converts between the opus and PCMU for the two legs of the media communication channel. Additionally, the method can include translating between the client signaling and the destination signaling. The client signaling connection is preferably translated into corresponding signaling instructions in the signaling communication channel between the system bridge and the destination (e.g., telephony device, communication device, other client application instance). In implementation, merging can connect a client application with a communication platform or other communication infrastructure as shown in FIG. 23, with a PSTN device as shown in FIG. 24, a SIP based device as shown in FIG. 25, another client application, or any suitable destination endpoint.

As shown in FIG. 9, a second preferred method for connecting a client to an application of a preferred embodiment includes receiving a connection request at a policy engine from a client, the connection request including an authentication token retrieved by the client in block S200; receiving an authentication token at the policy engine S202; authenticating the client at the policy engine by verifying the authentication token in block S204; and permitting the client to connect to an application in response to verification of the authentication token in block S206. The method functions to enable a possibly untrusted client to securely access application services and resources. A client preferably describes a web browser, application session, or any suitable outside entity. The method is preferably implemented for use with a telephony platform but may alternatively be used for any suitable communication platform. The method may be used to implement browser based telephony application such as click to call features, voice sessions, video calls, video streams, screen sharing, sending of SMS messages, alternative messaging, or any suitable application. In an exemplary application, the client is enabled to initiate and interact with a telephony application by obtaining a token to authenticate access to the application. Additionally, the method of connecting a client to an application may be applied in cooperation with the method above for a client receiving incoming communications.

Block S200, which recites receiving a connection request at a policy engine from a client, functions to receive communication from a client wishing to use an application or make a communication. As described below, an authentication token is preferably directly or indirectly communicated to the policy engine. The policy engine then can preferably allow or deny access to an application by a client based on the verification of the authentication token. The connection request may be accompanied by the token as shown in FIG. 10 or the connection request may come prior to obtaining a token as shown in FIG. 11. The client application preferably uses establishes a signaling communication channel if the connection request is accepted. The signaling communication channel can be used to control a media communication channel over which synchronous communication flows.

Block S202, which recites receiving an authentication token at the policy engine, functions to obtain an authentication token on behalf of a client. The authentication token is preferably a data package that includes application ID and/or additionally parameters. The authentication token is preferably signed. The authentication token is more preferably signed with a secret key shared by the policy engine and an accessing entity (e.g., a web application for use of the telephony application). The application ID and/or the authentication token may be sent to client, which may then use the authentication token to connect to a web application. In another variation, the client may provide an identifier that enables a policy engine to validate with an authentication application. In the first variation, as shown in FIG. 10, a web application preferably sends an authentication token to the client. The client then communicates the authentication token directly when sending a connection request. The authentication token may be embedded in the webpage or application when instantiated. Alternatively, a client may dynamically request the authentication token such as by using AJAX upon a user-triggered event. In a second variation, as shown in FIG. 11, the client may send an identifier when sending a connection request for indirectly obtaining a token for a client. In this variation, block S202 preferably includes sending a client identifier contained in the connection request from the client to an authentication application S208 and receiving the authentication token at the policy engine from the authentication application S210 as shown in FIG. 12. A policy engine preferably connects with an authentication application. The authentication application can preferably use the identifier to authenticate or deny access by the client. The authentication application then sends a response to the policy engine preferably includes an authentication token. The authentication token received at the policy engine from the authentication application preferably enables the client to be indirectly authorized to form a connection. The authentication application is preferably a server run by the web application entity, but may alternatively be a third party authentication application. The identifier may include an account name, code, or any suitable parameters that the authentication application requires to complete authentication.

Block S204, which recites authenticating the client at the policy engine by verifying the authentication token, functions to determine if a client should be allowed or denied access to an application. In the first variation where a token is received from the client, a shared secret between the application and the policy engine may be used to authenticate the token. In the second variation, the authentication application may send the authentication token, which may be authorized in a similar manner, or the authentication application may communicate to the policy engine if the client is allowed or denied.

Block S206, which includes permitting the client to connect to an application in response to verification of the authentication token, functions to allow the client to connect to the application or to deny the client access to the application. The connection request from the client is preferably forwarded on to the application if the verification of the authentication token allows access. If the connection request is denied, a communication may be sent back to the client or any suitable response may be made. The connection in one application is preferably establishing a voice session, video session, click to call feature, starting an outbound call, a video stream, a screen sharing session, SMS/MMS messaging, IP messaging session, and/or any suitable communication application as in block S212 shown in FIG. 13. In one exemplary application, a call router of a telephony platform preferably facilitates execution of the application.

2. System for Connecting a Client

As shown in FIG. 14, a system for connecting a call to a client of a preferred embodiment preferably includes a system bridge 210, a pub/sub system 220, and optionally a policy engine 230. The system preferably functions to facilitate connecting an outside entity to a client 260. The system preferably implements the above method. The system bridge 210 preferably includes an incoming channel to receive incoming calls or video such as from a PSTN device, another client device, or any suitable source. In one embodiment, the system bridge 210 includes a communication link to a call router 250 of a telephony platform. In another embodiment, the system bridge 210 is integrated into a call router 250. In another implementation, a SIP endpoint is used in place of a call router. As shown in FIG. 15, the system bridge 210 may be a cloud environment or system bridge cluster composed of a plurality of system bridges (210a, 210b, 210n). The system bridge 210 preferably additionally includes internet channels to be accessed by a client 260. The system bridge 210 preferably connects to the pub/sub system 220, and the pub/sub system 220 preferably maintains persistent connections to clients. The pub/sub system 220 may use any suitable technology such as websockets, HTTP server push, adobe flash sockets, AJAX long polling, AJAX multipart streaming, forever iframes, jsonp polling, Comet, XMPP, BOSH, or any suitable communication technology to facilitate subscription and publication channels. Any suitable system may be used in place of the pub/sub system such as a queuing system. The client 260 preferably includes native or web application code that cooperates with the system to establish a subscription through the pub/sub system 220 to the system bridge 210 and to send a client communication that is received by the system bridge 210. The client preferably uses HTTP or HTTPS or any suitable communication protocol. Additionally, a policy engine 230 may be an intermediary system for the communication channel between clients and the system bridge 210. The policy engine 230 preferably authenticates signed messages using web tokens, but may alternatively be configured for any suitable form of authentication. An authentication application server 240 preferably facilitates the distribution and/or processing of authentication tokens.

The system preferably implements the above methods in a computer-readable medium storing computer-readable instructions. The instructions are preferably executed by computer-executable components preferably integrated with the system bridge 210, the pub/sub system 220, and the optional policy engine 230. The computer-readable medium may 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 processor but the instructions may alternatively or additionally be executed by any suitable dedicated hardware device.

3. System for Communicating with a Client Application

As shown in FIG. 16, a system 10 for communicating with a client application can include one or more hardware interfaces, including for example a browser 12, a mobile device 14, or a public switched telephone network (PSTN) line 16. In the system 10 of the preferred embodiment, each of the hardware interfaces 12, 14, 16 can be connected and/or interconnected with one another through a communication platform cloud-based service 30 such as that available from the assignee of the present application. Preferably, the cloud service 30 is configured according to an Application Programming Interface (API). As used herein, the term API should be understood to mean any combination of software, firmware, and/or hardware that allows two or more software applications (i.e., machine-readable instructions) to communicate with one another. An example API can be configured as a telephony platform such as one substantially similar to the one described in published U.S. Patent Application No. 2009/0252159, titled “SYSTEM AND METHOD FOR PROCESSING TELEPHONY SESSIONS”, assigned to the assignee of the present application, and hereby incorporated in its entirety by this reference.

As shown in FIG. 16, the cloud system 30 functions to communicate with one or more client HTTP servers 18, 20, 22. The cloud system 30 and HTTP server 18, 20, 22 communications are preferably RESTful in nature in both directions. 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 from the call router to the application server preferably contains all necessary information for operation of the application server and response generation of the application server. Hardware communications elements such as routers and servers preferably do not need to remember or store previous communications to be aware of the state. Documents, media, and application state are preferably viewed as addressable resources, combined with data provide to the resource via request parameter, such as HTTP GET or HTTP POST parameters, or request body contents. Such request data can include an updated representation of the call resource, or other call state data generated as a result of call router operation, such as digits pressed on the keypad or audio recordings generated.

State information included with each request can include a unique call identifier, call status data such as whether the call is in-progress or completed, the caller ID of the caller, the phone number called, geographic data about the callers, and/or any suitable data. Alternatively, a varying level of a RESTful communication (statelessness) can be used, such as by using cookies, session tracking, or any suitable devices to simulate a normal website visitor model. Preferably, data sent with each request can fully enable the application server to determine the next state of the call to execute. RESTfulness preferably does not preclude using an external data source, such as a database, to lookup additional data to log call meta data, or determine application logic.

The hardware interfaces 12, 14, 16 function to interface with the human element of the communication through voice, video, short message service (SMS), multimedia messaging service (MMS), proprietary or alternative IP messaging protocols, or other communication means and/or protocols. As an example, the browser 12 can include any web-enabled browser that is capable of receiving and/or transmitting voice signals such as through real time messaging protocol (RTMP) or other suitable TCP-type communication protocols. Some web browsers can use flash based real time communication channels. Other web browsers can use WebRTC communication channels. A client application can selectively decide which type of real time communication protocol is preferred/available for a given communication. Alternatively, the browser 12 can include any plug-in enabled browser that is configured for session initiated protocol (SIP) or other signaling communications that can be transmitted through TCP, UDP and/or other suitable protocols. Similarly, the mobile device 14 can include a SIP module or other suitable communication protocol. Preferably, each of the browser 12 and the mobile device 14 can be connected and/or connectable to the cloud service 30 through any suitable type of network, including but not limited to, wide area networks, local area networks, mobile telephony networks, or any suitable combination thereof. As an example, many current mobile devices 14, such as tablet computers, are connectable to the Internet through both WiFi and mobile telephony (GSM and CDMA) networks.

The mobile device 14 of the system 10 of the preferred embodiment can include a series of modules relating to its communication function. As shown in FIG. 17, the mobile device 14 of the preferred embodiment can include an operating system module 40, an audio engine 42, and a cloud interface module 46. The operating system module 40 of the mobile device 14 of the preferred embodiment functions to control the general functionality of the mobile device 14, including but not limited to its communication capabilities. The audio engine 42 of the mobile device 14 of the preferred embodiment functions to control a majority of voice communication functions, including interfacing with any device hardware 44 such as speakers and microphones. In particular, the audio engine 42 can function to initiate and control communication sessions including voice communication sessions using Internet protocol (rather than a typical telephony communication protocol typically used in a mobile device).

The mobile device 14 of the preferred embodiment can further include a cloud interface module 46 that functions to cooperate with the audio engine 42 to communicate with the cloud service 30 and communicate with other hardware interfaces 12, 14, 16. The cloud interface module 46 can be configured within a browser function of the mobile device 14, or alternatively as a native application or set of machine executable instructions residing permanently or quasi-permanently in a memory module (not shown) of the mobile device 14. Preferably, the cloud interface module 46 can be designed according to the RESTful principles described above.

In one variation of the mobile device 14 of the preferred embodiment, the cloud interface module 46 can further include one or more security and/or resource management tools described in further detail below. Examples of security and/or resource management tools can include an authorization token, which can be defined as an electronic listing of possible privileges for its bearer. A developer or other suitable account holder preferably obtains an account token from the provider of the cloud service 30 and then signs the account token to generate an authorization token. The authorization token can be used to authorize actions when included in communication requests, client registration, client presence registration, and/or any suitable use. The cloud service or any suitable service can preferably verify the authorization token by validating the signature of the authorization token against the account key. Thus enabling possibly untrusted client applications to prove that they are authorized to perform particular actions. Example privileges conferred by a token can include, but are not limited to, a user's abilities to make and/or receive calls, an identification of the application and/or user, and one or more operational parameters that can further define a scope of functions and/or processes performable by the cloud interface module 46. In one exemplary variation, an authorization token permits a communication request to send one or more communications. In another exemplary variation, an authorization token can permit a communication request to establish a communication session that supports communications selected from audio, video, chat, and/or other suitable communication mediums. In another variation an authorization token can permit presence information to be provided to other devices or to be obtained from other devices or a contact list. In one alternative embodiment, the token can be transmittable in its entirety in the clear. In another alternative embodiment, some or all aspects of the token are encrypted during transmission and are partially or entirely unknown to the user of the mobile device 14. The cloud service 30 may be substantially agnostic relative to the contents of the token insofar as the contents of the token can be directed entirely to the HTTP server or to a authorization server indicating if the authorization token is allowed. Alternatively, the cloud service 30 can function in part as a gatekeeper and perform one or more security and/or authenticity checks prior to, during, and/or following a communication session.

The system preferably implements the methods described herein in a computer-readable medium storing computer-readable instructions. The instructions are preferably executed by computer-executable components preferably integrated with the mobile devices 12, 14, 16, the cloud system 30, and the HTTP servers 18, 20, 22. 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 processor but the instructions can alternatively or additionally be executed by any suitable dedicated hardware device.

4. Method for Connecting a Call to a Client

As shown in FIGS. 18 and 19, a method S1000 of a first preferred embodiment for making outgoing communications from a client application can include receiving a connection request from a first client application S1110; verifying at least one parameter of the communication request S1120; merging the real time communication of the client with real time communication of a communication destination S1100 that can include transmitting a progress signal to the first client application S1130; retrieving communication instructions from a server according to the incoming communication request S1140; identifying an instruction to make a call to a communication destination S1150; and establishing communication with the communication destination S1160. More generally, the method allows a signaling channel and a media channel of a client application to connect to a second type of signaling channel and media channel as shown in FIG. 26. The method of the first preferred embodiment enables a client application to establish communication. The medium of communication is preferably a telephony voice based communication but may alternatively be any suitable communication medium such as video session, screen sharing, text messaging, and/or multimedia messaging. The method preferably establishes a media channel (i.e., communication session) such as an open voice channel between the first client application and at least a second endpoint. The method may alternatively perform one or more communication requests such as transmitting a message from the first client application to at least a second endpoint. As shown in FIG. 18, the method may be used for connecting a USER A that is using a client application to a USER B that is using a PSTN device. As shown in FIG. 19, the method may alternatively, be used for communicating a media message such as an SMS or MMS message from a USER A on a client application to a USER B using a PSTN device. The method as described herein, USER A can include a mobile device 14 of the type described above. USER B may be a PSTN connected device or a mobile device 14 of the type described above.

Step S1110, which includes receiving a connection request from a first client application, functions to connect a USER A of client application to the CLOUD. The CLOUD is preferably a communication platform and can include one or more functions and/or hardware systems described above with reference to cloud service 30. Preferably, the CLOUD can include one or more separate servers and/or services configured for trafficking and connecting communications between the users in accordance with the principles of the API described above. The connection Step S1110 functions to initiate communications over a predetermined protocol, such as SIP, RTMP and the like, between a mobile device and the CLOUD. The predetermined protocol is preferably an internet protocol utilizing an internet protocol such as TCP, UDP, and/or HTTP, but any suitable protocol may be used.

Receiving a connection request can include at a client device, initiating communication through a browser real-time protocol, functions to establish communication between a browser and a system bridge or communication gateway of a communication platform. The real-time communication is preferably initiated by a RTC browser module. As described below, an outside entity may initiate the communication and the browser with the RTC browser module may be the callee entity of a communication. Initiating communication through a browser preferably includes establishing a control communication channel and a real-time media communication channel. Preferably, the control communication channel is a websocket communicatively coupling the browser (e.g., the RTC browser module) and the communication platform (e.g., a RTC load balancer). The real time media communication channel is used to transfer the real-time media such as the audio, video, screen sharing, and/or other real-time media communication. The control and media communication is preferably bi-directional and full-duplex between the browser and the communication platform. The real time media communication channel preferably uses WebRTC to communication with a Secure Real Time Protocol (SRTP).

Initiating communication may additionally include selecting a communication protocol. Selecting a communication protocol preferably includes analyzing properties of the intended communication and capabilities client device. In a first preferred variation, the RTC browser module determines properties of the current client device ands selects a form of real-time communication according to that information. The current client device properties may include using the operating system version, application/browser version, connectivity quality, type of data communication (e.g., wireless internet vs. cellular data), or any suitable property that may factor into determining an optimal real-time communication type. For example, in a first browser, WebRTC may be better supported while in a second browser flash enabled RTMP may be more supported. In another variation, the properties of the other involved endpoints may be queried or determined and used in a similar manner to determine an optimal real-time communication protocol for the current RTC browser module. Endpoints and the associated device properties can preferably be determined by querying a service provided through the communication platform, but may alternatively be determined in any suitable manner. Additionally, properties of a plurality of endpoints involved in the communication may be used to determine a real-time communication protocol. For example, if the destination endpoint does not support WebRTC but the current RTC browser module and the destination support Flash enabled RTMP, it may be optimal to use Flash RTMP for the caller RTC browser module so that both endpoints use the same protocol. In yet another variation, a device may rely on presence information of a destination endpoint in selecting an optimal communication endpoint. The presence information can preferably provide data such as the availability of a user for a particular endpoint, a list of devices at which a user associated with the endpoint may be reached, and/or other information related to the presence/availability of a user at an endpoint. Presence information can preferably be collected and integrated into the communication routing such as in the system and method described in U.S. patent application Ser. No. 13/624,750, filed 21 Sep. 2012, and titled “SYSTEM AND METHOD FOR DETERMINING AND COMMUNICATING PRESENCE INFORMATION”, which is hereby incorporated in its entirety by this reference.

In one variation of the method of the preferred embodiment, the connecting step S1110 can further include transmitting one or more permissions, parameters or tokens with the connection attempt. Preferably, the parameters can include one or more of a cloud system token (or security credential token) that can contain authentication credentials of USER A, a bridge token (which can have a null value in outgoing calls such as that shown in FIG. 18), and/or one or more user-defined parameters. The authentication token is preferably associated with security credentials that can authenticate and/or authorize a communication request to perform particular actions. The authorization token can preferably be used to verify if a bearer can perform a particular action and in some variations which operations to limit/permit. A communication request can be permitted to execute one or more communications. Any suitable restriction on the communications may additionally be associated with the authorization token such as number of communications, timing of communications, communication endpoints, and communication mediums. As described above, the authorization token is preferably created for a client application by a developer signing against their account key or some other suitable identifier. At the communication platform or at a service communicatively coupled to the communication platform, the authorization token can be verified against an account key provided to a developer or provider of a system using the client application. As an example, the user defined parameters can include additional constraints or conditions on the use of the system, such as for example particular users to whom calls can be placed, particular abilities of the token holder, identifiers of any applications or functions in use, or identifiers of any required recipients of communications, e.g., customer service or sales representatives. Preferably, any or all of the permissions can be consolidated into a single entity, such as the cloud system token; and any or all of the permissions can be sealed and kept invisible from USER A and partially or entirely transparent to any intermediary servers useable in the communication process.

Step S1120, which includes verifying at least one parameter of the communication request, functions to check if the connection request should be completed. Preferably, the connection request is sent with a security credential token for a user of the first client application. The security credential token is preferably checked at the CLOUD to ensure the client application is allowed to make a connection request on behalf of the user. Permissions can be stored in association with an authorization token, and the authorization token preferably received in S1110 is used to retrieve the associated permissions. The permissions are then used to determine if the communication request is allowed. Additionally or alternatively, the user defined parameters may be checked to ensure they satisfy any requirements or meet expectations. Additionally, step S1120 can preferably function to check other diagnostic functions of the communication system and identify selected ports and/or communication channels for the impending communications. For example, the CLOUD may check to ensure that the connection request is not being made when the CLOUD is an overloaded state, and that the connection request satisfies an overload policy.

Step S1100, which includes merging real time communication of the client with real time communication of a communication destination, functions to bridge real time media communication from the client application to an outside destination. Establishing the outside communication can include steps S1140, S1150, and S1160 to establish the outside communication channel according to a communication application. Alternative communication platforms may include simple mapping to a destination or use any suitable logic to determine the second leg of a real time communication channel. Merging real time communication of the client with real time communication of a communication destination preferably involves the coordination of signaling as described above with the establishment of real time communication channels between the client application, a gateway (e.g., the system bridge), and a communication destination (e.g., a communication application and/or a communication endpoint). Merging of real time communication preferably accommodates selective use of different real time communication protocols such as WebRTC or flash.

Merging can include receiving communication of the browser real-time protocol, functions to use the communication platform as a proxy for the intended destination. The control communication signaling channel and the real-time media communication channel are both preferably received at a load balancer. Regardless of a specified end destination(s), the RTC browser module preferably directs the real time communication to the communication platform, which proxies communication, directs communication traffic to subsystems with adequate capacity, and/or process communication for communicating with the other endpoint.

At the load balancer, merging can include load balancing communication to a system bridge, which functions to determine a system bridge with adequate capacity. There is preferably a plurality of system bridges, and an optimal/best-available communication router is preferably selected for processing the communication depending on load, quality metrics, regional performance, and/or suitable parameters of the communication routers. The load balancer preferably forwards the real-time communication channel(s) from the RTC browser module on to the system bridge. In particular, the load balancer establishes a control signaling communication channel using a websocket or SDP and a real-time media communication channel using SRTP. In alternative variations, the system bridge is not load balanced, and the control signaling communication channel and the real time media communication channels are directly established with the system bridge.

Prior to merging real time communication, a destination and destination media channel must be established. The method can include determining a destination, which functions to map the destination to an endpoint. Preferably the RTC browser module specifies a destination identifier that is associated with an endpoint or plurality of endpoints. A plurality of destination endpoints may additionally be specified for real-time communications for any suitable number of endpoints. In one variation, the endpoints are specified as namespace identifiers. The identifiers may be namespaced globally, within the communication platform, within an account, within an application, or namespaced in any suitable context. Namespaced destination identifiers function to enable more usable ways of establishing real-time communication between two known endpoints. In another variation, the destination endpoint is not namespaced (e.g., a telephony number or IP address), and there may not be a need to perform any mapping to an endpoint. Determining a destination may additionally include determining a destination according to a presence server at least in part. The presence server preferably allows presence information (e.g., if a user is available, busy, available at one of several possible devices, etc) to be used. In situations where a destination specifying a user has multiple possible device destinations. The type of endpoint may be used in selecting an endpoint. For example, there may be performance improvements if the endpoints do not require expensive transcoding processing, and thus the communication router may be configured to give preference device endpoints that minimize the transcoding.

Step S1130, which includes transmitting a progress signal to the first client application, functions to transmit a ringtone or confirmation message to USER A. The progress signal may take different forms depending on the communication medium. For voice or video calls, the progress signal is preferably a ringtone played for the user of the client application. In an asynchronous messaging application, the progress signal may indicate the delivery status of the message (e.g., sending, delivered, read). In some variations, the progress signal is a confirmation transmission to confirm the connection for the client application. The confirmation transmission is preferably transparent to a user and is only an acknowledgment by the CLOUD for the client application. The progress signal is preferably transmitted in response to an invite transmission within one or more of the CLOUD service. Preferably, the invite can include an application to which connection is sought, the account identification of the recipient, as well as the user defined parameters that were previously received in the CLOUD. Additionally, the invite can include a caller-identification or user identification of USER A. The invite is preferably a SIP invite but may be any suitable invite. In response to a smooth traffic flow of the invite within the one or more CLOUD servers, the CLOUD can preferably transmit the progress signal back to the mobile device via the SIP connection.

As mentioned before, merging can be used to establish media communication flow between the client application and an outside endpoint for a variety of systems. In one variation, a communication application is used to control and direct a connection. The client application can initially have a media flow between the client application and the application. For example, the application can specify audio, video, text-to-speech commands, and other interactions that should occur over the media channel. Additionally, the application can direct the media channel to connect to an outside endpoint. Any suitable number of media bridges can occur on the non-client application leg of the media connection.

In a communication application variation, step S1140, which includes retrieving communication instructions from a server according to the incoming communication request, functions to fetch instruction markup determining communication logic. Step S1140 preferably includes transmitting an HTTP request (such as a GET or POST) to the HTTP Server associated with the user account of the client application. Preferably the user account has a URL configured as a resource location of the communication instructions. Step S1140 can preferably be performed simultaneously or substantially simultaneously with one or more variations of step S1130, described above. In another variation of the method of the preferred embodiment, the HTTP request can include any or all of the permissions described above. Preferably, the HTTP request includes at least the user-defined parameters, which can be transmitted and received in an encrypted format. Alternatively, step S1140 can include verifying one or more of the user defined parameters at or by the HTTP server.

Step S1150, which includes identifying an instruction to make a call to a communication destination, functions to process the communication instructions and determine an outgoing communication destination. The communication instructions retrieved in Step S1140 are preferably transmitted as a markup language format message to the CLOUD from the HTTP Server. In one variation of the method of the preferred embodiment, the markup language format message can include one of an HTML message, an XHTML message, an SGML message, or any other suitable markup language or variation or version thereof. In another variation of the method of the preferred embodiment, the markup language format message can include a TWiML message for use with a cloud system of the assignee of the present application. The communication instructions may include any suitable logic. In making an outgoing call, the communication instructions preferably include an instruction to dial or communicate with a communication destination. Alternatively, the application could direct playing audio files, playing other media files, converting text to speech, or performing any suitable interaction over a media connection.

Step S1160, which includes establishing communication with the communication destination, functions to complete communication with the desired endpoint. Establishing communication can establish communication from the source of the communication request (e.g., USER A) and at least one party/endpoint. A plurality of destination endpoints/parties may alternatively be included in the established communication. In a first variation, the communication is preferably an open media channel (e.g., voice/audio, video, screen sharing or any suitable communication session) between the client application and a device of the communication destination. This variation preferably includes inviting the communication destination; and upon receiving acknowledgement of invite acceptance, opening a media channel between the communication destination and the first client application. The invite is preferably a SIP invite but may alternatively be any suitable invite to a media channel. This may be used to establish communication with a PSTN device and/or a second client application as described more below. In one example, a USER A is attempting to contact a PSTN USER B. Accordingly, the communication instructions can indicate that the recipient is a PSTN user, and therefore the CLOUD will preferably create an appropriate SIP invite and transmit it to an appropriate provider. As used herein, the PSTN network and/or service provider can include both mobile and landline-based telephony networks. A response is preferably received from the provider at the CLOUD service, wherein the response can include an appropriate HTTP status code such as 200 OK. Following confirmation and cross-confirmation between one or more components of the CLOUD service and the service provider, the method can open a media channel between USER A and USER B. As shown in FIG. 18, the media channel bypasses and/or is transparent to the HTTP server, but can be transmitted through one or more components of the CLOUD service. It should be understood that the media channel can also include other types of media, including at least video, screen sharing, SMS, MMS, or any other suitable communication media.

Merging real time communication of the client with real time communication of a communication destination can include processing communication according to the destination, functions to transcode, convert, or otherwise translate the media communication for the destination endpoint. The communication router preferably translates the communication from a form compatible with the RTC browser module (e.g., WebRTC or Flash RTMP) to a form compatible with the destination endpoint. The destination endpoint may be a PSTN device, a SIP/VoIP device, another browser client using WebRTC, Flash RTMP, CU-RTC-Web, proprietary communication protocol, or any suitable destination endpoint. In one variation, the communication router preferably detects if a receiving endpoint is the same type and/or compatible with the encoding used by the calling RTC browser module. If the destination is the same type or compatible then the communication router may maintain the encoding used by the calling RTC browser module to preserve the encoding. For example, when a RTC browser module is using WebRTC to communicate with another device using WebRTC then the communication router preferably maintains the encoding when routing the communication. In one example, processing communication may include transcoding between ISAC (Internet Speech Audio Codec) and G711U. In another example, processing communication may include transcoding between webm and h.264 video encodings. In another example, processing communication includes transcoding media encoded with an opus codec and transmitted over a WebRTC connection to media encoded with a PCMU codec transmitted over a SIP controlled RTMP. The real-time communication is preferably bi-directional and thus the processing of communication is preferably performed in both directions. Thus information from the destination to the RTC browser module is similarly converted to an encoding/format compatible with the RTC browser module. The media streams are transmitted between the destination and the client application. When the destination is a SIP endpoint, the communication router may establish a SIP channel. If the destination is a RTC browser module compatible with WebRTC, the communication router may mirror that of the caller, a websocket control channel and an audio SRTP channel.

In a second variation of Step S1160, establishing a communication with the communication destination can include performing one or more specific communication requests. Performing the communication request preferably includes sending an asynchronous message to the communication destination as shown in FIG. 19. An asynchronous message can be sent using protocols including SMS, MMS, IP-based messaging protocols, proprietary messaging protocols, and/or any suitable messaging protocol.

In another variation of the method of the preferred embodiment, USER A can be communicating on a mobile device having a native application, software program or set of machine executable instructions that functions to perform one or more of the steps outlined above. In one example configuration, the connect, check and invite steps S1110, S1120, S1130 or significant portions thereof can all be performed by such a native application configured with an operating system of the mobile device. As an example, certain invite and authentication procedures, including for example the cloud system token and user defined parameters associated with the application native to the user's mobile device. In such an example configuration, the mobile device can communicate directly with the HTTP server via one or more requests and/or messages of the type described above.

As shown in FIGS. 20 and 21, a method S2000 of a second preferred embodiment for receiving communication at a client application may include at a first server of a communication platform, receiving an executed login of a user of a first client application S1200; at a second server of the communication platform, accepting an incoming communication request S1210; retrieving communication instructions from a server according to the incoming communication request S1240; identifying an instruction to make a call to a communication destination of the user of the first client application S1250; forwarding the communication request to the first server of the communication platform S1260; and at the first server of the communication platform, establishing communication with the first client application S1270. The method functions to receive calls at a client application through the systems described above. The method is preferably employed to enable software applications or machine executable instructions running natively on a mobile device to interface with a telephony or communication platform. The method may be used such that a PSTN device or any suitable communication capable device may contact the client application. The method may be used for voice, video, SMS, MMS, IP based messaging, proprietary messaging, and/or any suitable communication medium. More generally, the method S2000 of making inbound calls directed at the client allows a client application to establish a signaling channel, then for an outside calling entity (e.g., an application, a PSTN device, a SIP device and the like) to initiate a communication request, subsequently a signaling channel and a media channel are established between a system bridge and the calling entity (or a proxy of the calling entity), a media channel is established between the system bridge and the client application, and then the signaling and media channels are merged as shown in FIG. 27. Media may be transcoded such that media formats are compatible for transmitting between the two media channels. Additionally, registration of a client identifier for the client signaling channel can be used by incoming communication requests to specify an intended client application. The method may be used in combination with the method above for making outgoing communications from a client application such that a first client application may contact a client application. The pairs of steps S1110 and S1210, S1120 and S1220, S1140 and S1240, and S1150 and S1250 may in some variations be substantially similar to their corresponding step.

Step S1200, which includes at a first server of a communication platform, receiving an executed login of a user of a first client application, functions to establish a connection of a user to a communication platform/CLOUD system. The user preferably uses a mobile device having a native application (with a client application) of the type described above, but any suitable device with a client application may be used. Preferably, when USER D logs into his account on CLOUD B, a URL subscription <userd_sid>/USERD is established in CLOUD B such that USER D will receive any messages published to that URL. Example messages can include voice, video, SMS, MMS, email or any other suitable type of electronic communication audible or readable on a mobile device.

Step S1210, which includes at a second server of the communication platform, accepting an incoming communication request, functions to initiate a call from a caller (e.g., USER C) to the user of the first client application (e.g., USER D). As shown in FIG. 5, the call initiation can be processed at a service provider, such as for example a PSTN service provider for a mobile telephony or landline telephony network. The service provider can function to receive a telephonic communication (voice, SMS, MMS) and convert that incoming communication into an SIP request transmittable to CLOUD A. Alternatively, the caller may be initiated by device using a second client application, and the outgoing call may be established in manner substantially similar to that of the method for making outgoing communications from a client application. In step S1220 of the method of the preferred embodiment, CLOUD A will perform a check of the received SIP invite, which can include checking a recipient account, a voice URL for the account, an SMS or MMS URL for the account and/or any other account-specific or user specific permissions or preferences associated with the account of USER D. In the variation where a call is initiated from a second client application, the method S2000 may include transmitting a progress signal to the second client application, which is substantially similar to Step S1130.

Steps S1240 and S1250, which include retrieving communication instructions from a server according to the incoming communication request and identifying an instruction to make a call to a communication destination of the user of the first client application, function to process the application logic of a communication platform application. Step S1240 of the method of the preferred embodiment preferably includes transmitting an HTTP request from CLOUD A to the users HTTP Server in response to a successful check of the recipient's credentials. As an example, once CLOUD A identifies a voice URL associated with USER D's account, CLOUD A can transmit an HTTP GET/POST request to USER D's HTTP Server. Step S1250 of the method of the preferred embodiment preferably processes the communication instructions and determine an outgoing communication destination corresponding to the user of the first client application. A markup language format message is preferably received at CLOUD A from the HTTP Server. In one variation of the method of the preferred embodiment, the markup language format message can include one of an HTML message, an XHTML message, an SGML message, or any other suitable markup language or variation or version thereof. In another variation of the method of the preferred embodiment, the markup language format message can include a TWiML message for use with a cloud system of the assignee of the present application.

Step S1260, which includes forwarding the communication request to the first server of the communication platform functions to communicate the incoming communication request to a portion of the CLOUD that manages the logged in user. For media channels communication requests such as voice or video calls, an invite request is transmitted from CLOUD A to CLOUD B in response to the receipt of the markup language format message from USER D's HTTP Server. Preferably, the invite request contains at least an account identification for USER D and a client name (USER D) associated with the account during the login step S1200. The invite request is preferably a SIP invite as is known in the art. In the case of an asynchronous messaging, the text, and/or media message may be contained in the communication message sent to the server of CLOUD B as shown in FIG. 20. The first server of the communication platform may additionally or alternatively include or function as a subscription manager of the communication platform. The communication request may subsequently be forwarded to an appropriate server to manage the subscription or login session of the user of the first client application.

Step S1270, which includes at the first server of the communication platform, establishing communication with the first client application; functions to complete the communication request initiated in Step S1200. Step S1270 preferably completes the communication request between the entity of the incoming communication request (e.g., USER C) and the user of the first client application (e.g., USER D). Establishing communication with the first client application preferably includes publishing a notification to the first client application S1272. In one variation of the method of the preferred embodiment, CLOUD B can publish an invite message to USER D's URL while simultaneously causing the caller, USER C, to hear a ringtone. In Step S1272 CLOUD B can receive the publication of the invite message and broadcast it to all registered listeners, i.e., those users associated with the account established in step S1200. Establishing communication with the first client application may include varying steps depending on if the method is employed for establishing a media channel between two parties or for sending a message from one entity to a user of the first client application.

Establishing communication for a media channel communication request can additionally include receiving a connection acceptance by the first client application S1274; and opening a media channel with the first client application upon connection S1276. If USER D agrees to accept the incoming call, then he will transmit a connection acceptance to CLOUD B as shown in step S1274. The acceptance can include the transmission of one or more permissions with the connection acceptance. Preferably, the permissions can include one or more of a cloud system token containing the security credentials of USER D (which can have a null value since the call is being received in FIG. 20), a bridge token (which might have been copied from the invitation from CLOUD B), and one or more user defined parameters. In another variation of the method of the preferred embodiment, CLOUD B step S1274 can also include checking the one or more permissions at CLOUD B, which can include for example checking if there are a predetermined number of parameters (even though one or more can be null). Alternatively, step S1274 can further include unpacking the bridge token to identify an IP address associated with one or more CLOUD A or CLOUD B servers to ensure that communications are properly routed and merged through the appropriate portion of CLOUD A or CLOUD B, i.e., a bridge portion of one of the respective CLOUD services. In another variation of the method or the preferred embodiment, step S1274 can include bridging the call between USER C and USER D in response to a bridge token associated with the connection request from USER D.

In another variation of the method of the preferred embodiment, step S1274 can recite responding from the provider to the CLOUD service, wherein the response can include an appropriate HTTP status code such as 200 OK. Following confirmation and cross-confirmation between one or more components of the CLOUD service and the service provider, step S1216 of the method of the preferred embodiment recites opening an audio channel between USER C and USER D. As shown in FIG. 20, the audio channel bypasses and/or is transparent to the HTTP server, but can be transmitted through one or more components of the CLOUD A and CLOUD B components.

In another variation of the method of the preferred embodiment, USER D can be communicating on a mobile device having a native application, software program or set of machine executable instructions that functions to perform one or more of the steps outlined above. In one example configuration, the login, pub/notice and connect steps S1200, S1272, S1274 or significant portions thereof can all be performed by such a native application configured with an operating system of the mobile device. As an example, certain invite and authentication procedures, including for example the cloud system token and user defined parameters associated with the application native to the user's mobile device. In such an example configuration, the mobile device can communicate directly with the HTTP server via one or more requests and/or messages of the type described above.

As shown in FIGS. 20 and 21, the cloud services can be broken in to two or more segments, including for example CLOUD A and CLOUD B. Those of skill the art will appreciate that these designations are for illustrative and descriptive ease only, and that CLOUD A and CLOUD B can include a single computer/server having multiple functions or multiple discrete computers/servers having unique functions, depending upon the particular configuration sought by the user. The method of the preferred embodiment can be configured partially or entirely in a computer-readable medium storing computer-readable instructions. The instructions are preferably executed by computer-executable components preferably integrated with a mobile devices, one or more portions of the cloud system and the HTTP servers. 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 processor but the instructions can alternatively or additionally be executed by any suitable dedicated hardware device.

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: at a system bridge of a WebRTC real-time client communication hardware system, establishing a persistent client subscription connection with an external WebRTC client device;receiving from an external system an incoming communication request at the system bridge, the incoming communication request being directed to the external WebRTC client device;publishing an incoming communication notification from the system bridge to the WebRTC client device via the persistent client subscription connection;receiving a client communication at the system bridge from the WebRTC client device; andthe system bridge merging the incoming communication request into the client communication at the system bridge by connecting the incoming communication request to the WebRTC client device by using a WebRTC communication protocol,wherein the system bridge merging the incoming communication request into the client communication at the system bridge comprises: the hardware system: opening a first audio channel between the client device and the system bridge,opening a second audio channel between the system bridge and a server of the hardware system, andopening a third audio channel between the server and the external system.
2. The method of claim 1, the method further comprising: the hardware system providing voice media communication between the external system and the client device via the first audio channel, the second audio channel, and the third audio channel.
3. The method of claim 1, wherein the external system is a PSTN service provider system, and wherein the external PSTN service provider system opens a fourth audio channel between the PSTN service provider system and a PSTN user device.
4. The method of claim 3, wherein voice media communication between the PSTN user device and the client device is provided via the first audio channel, the second audio channel, the third audio channel, and the fourth audio channel.
5. The method of claim 4, wherein the hardware system publishes the incoming communication notification from the system bridge to the client device based on the incoming communication request received from the external system.
6. The method of claim 5, wherein the external system is external to the external client device and external to the real-time client communication hardware system, and wherein the external client device is external to the real-time client communication hardware system.
7. The method of claim 6, wherein the external client device provides the system bridge with the client communication based on the incoming communication notification received by the client device from the system bridge.
8. The method of claim 7, wherein the WebRTC protocol is an application-based real-time communication protocol.
9. The method of claim 2, wherein the external system is a WebRTC client device.
10. The method of claim 2, wherein the first audio channel between the WebRTC client device and the system bridge is a WebRTC audio channel.
11. The method of claim 8, wherein the first audio channel between the WebRTC client device and the system bridge is a WebRTC audio channel.
12. The method of claim 1, wherein the WebRTC protocol is an application-based real-time communication protocol.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 14/054,254, filed 15 Oct. 2013, which is a continuation in part of U.S. patent application Ser. No. 13/624,739, filed 21 Sep. 2012, which claims the benefit of U.S. Provisional Application No. 61/537,217, filed 21 Sep. 2011, and this application is a continuation in part of U.S. patent application Ser. No. 13/478,495, filed 23 May 2012, which claims the benefit of U.S. Provisional Patent Application No. 61/489,189, filed on 23 May 2011 and U.S. Provisional Patent Application No. 61/500,549, filed on 23 Jun. 2011, which are all incorporated in their entirety by this reference.

US Referenced Citations (789)

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
6269252	Hutchings	Jul 2001	B1
6269336	Ladd et al.	Jul 2001	B1
6317137	Rosasco	Nov 2001	B1
6363065	Thornton et al.	Mar 2002	B1
6373836	Deryugin et al.	Apr 2002	B1
6425012	Trovato et al.	Jul 2002	B1
6426995	Kim et al.	Jul 2002	B1
6430175	Echols et al.	Aug 2002	B1
6434528	Sanders	Aug 2002	B1
6445694	Swartz	Sep 2002	B1
6445776	Shank et al.	Sep 2002	B1
6459913	Cloutier	Oct 2002	B2
6463414	Su et al.	Oct 2002	B1
6493558	Bernhart et al.	Dec 2002	B1
6496500	Nance et al.	Dec 2002	B2
6501739	Cohen	Dec 2002	B1
6501832	Saylor et al.	Dec 2002	B1
6507875	Mellen-Garnett et al.	Jan 2003	B1
6571245	Huang et al.	May 2003	B2
6574216	Farris et al.	Jun 2003	B1
6577721	Vainio et al.	Jun 2003	B1
6600736	Ball et al.	Jul 2003	B1
6606596	Zirngibl et al.	Aug 2003	B1
6614783	Sonesh et al.	Sep 2003	B1
6625258	Ram et al.	Sep 2003	B1
6625576	Kochanski et al.	Sep 2003	B2
6636504	Albers et al.	Oct 2003	B1
6662231	Drosset et al.	Dec 2003	B1
6704785	Koo et al.	Mar 2004	B1
6707889	Saylor et al.	Mar 2004	B1
6711129	Bauer et al.	Mar 2004	B1
6711249	Weissman et al.	Mar 2004	B2
6738738	Henton	May 2004	B2
6757365	Bogard	Jun 2004	B1
6765997	Zirngibl et al.	Jul 2004	B1
6768788	Langseth et al.	Jul 2004	B1
6771955	Imura et al.	Aug 2004	B2
6778653	Kallas et al.	Aug 2004	B1
6785266	Swartz	Aug 2004	B2
6788768	Saylor et al.	Sep 2004	B1
6792086	Saylor et al.	Sep 2004	B1
6792093	Barak et al.	Sep 2004	B2
6798867	Zirngibl et al.	Sep 2004	B1
6807529	Johnson et al.	Oct 2004	B2
6807574	Partovi et al.	Oct 2004	B1
6819667	Brusilovsky et al.	Nov 2004	B1
6820260	Flockhart et al.	Nov 2004	B1
6829334	Zirngibl et al.	Dec 2004	B1
6831966	Tegan et al.	Dec 2004	B1
6834265	Balasuriya	Dec 2004	B2
6836537	Zirngibl et al.	Dec 2004	B1
6842767	Partovi et al.	Jan 2005	B1
6850603	Eberle et al.	Feb 2005	B1
6870830	Schuster et al.	Mar 2005	B1
6873952	Bailey et al.	Mar 2005	B1
6885737	Gao et al.	Apr 2005	B1
6874084	Dobner et al.	May 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	Stroem et al.	Jan 2006	B2
6999576	Sacra	Feb 2006	B2
7003464	Ferrans et al.	Feb 2006	B2
7006606	Cohen et al.	Feb 2006	B1
7010586	Allavarpu et al.	Mar 2006	B1
7020685	Chen et al.	Mar 2006	B1
7039165	Saylor et al.	May 2006	B1
7058042	Bontempi et al.	Jun 2006	B2
7058181	Wright et al.	Jun 2006	B2
7062709	Cheung	Jun 2006	B2
7065637	Nanja	Jun 2006	B1
7076037	Gonen et al.	Jul 2006	B1
7076428	Anastasakos et al.	Jul 2006	B2
7089310	Ellerman et al.	Aug 2006	B1
7099442	Da Palma et al.	Aug 2006	B2
7103003	Brueckheimer et al.	Sep 2006	B2
7103171	Annadata et al.	Sep 2006	B1
7106844	Holland	Sep 2006	B1
7111163	Haney	Sep 2006	B1
7136932	Schneider	Nov 2006	B1
7140004	Kunins et al.	Nov 2006	B1
7143039	Stifelman et al.	Nov 2006	B1
7197331	Anastasakos et al.	Mar 2007	B2
7197461	Eberle et al.	Mar 2007	B1
7197462	Takagi et al.	Mar 2007	B2
7197544	Wang et al.	Mar 2007	B2
D540074	Peters Samuel M	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
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	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	Soederstroem et al.	Dec 2011	B2
8082576	Flynn et al.	Dec 2011	B2
8103725	Gupta et al.	Jan 2012	B2
8126128	Hicks, III et al.	Feb 2012	B1
8126129	McGuire	Feb 2012	B1
8130750	Hester	Mar 2012	B2
8130917	Helbling et al.	Mar 2012	B2
8139730	Palma et al.	Mar 2012	B2
8145212	Lopresti et al.	Mar 2012	B2
8149716	Ramanathan et al.	Apr 2012	B2
8150918	Edelman et al.	Apr 2012	B1
8156213	Deng et al.	Apr 2012	B1
8165116	Ku et al.	Apr 2012	B2
8166185	Samuel et al.	Apr 2012	B2
8169936	Koren et al.	May 2012	B2
8175007	Jain et al.	May 2012	B2
8185619	Maiocco et al.	May 2012	B1
8196133	Kakumani et al.	Jun 2012	B2
8204479	Vendrow et al.	Jun 2012	B2
8214868	Hamilton et al.	Jul 2012	B2
8218457	Malhotra et al.	Jul 2012	B2
8233611	Zettner	Jul 2012	B1
8238533	Blackwell et al.	Aug 2012	B2
8243889	Taylor et al.	Aug 2012	B2
8249552	Gailloux et al.	Aug 2012	B1
8266327	Kumar et al.	Sep 2012	B2
8295272	Boni et al.	Oct 2012	B2
8301117	Keast et al.	Oct 2012	B2
8306021	Lawson et al.	Nov 2012	B2
8315198	Corneille et al.	Nov 2012	B2
8315369	Lawson et al.	Nov 2012	B2
8315620	Williamson et al.	Nov 2012	B1
8319816	Swanson et al.	Nov 2012	B1
8326805	Arous et al.	Dec 2012	B1
8335852	Hokimoto	Dec 2012	B2
8346630	McKeown	Jan 2013	B1
8355394	Taylor et al.	Jan 2013	B2
8411669	Chen et al.	Apr 2013	B2
8413247	Hudis et al.	Apr 2013	B2
8417817	Jacobs	Apr 2013	B1
8429827	Wetzel	Apr 2013	B1
8438315	Tao et al.	May 2013	B1
8462670	Chien 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
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, Sr. et al.	Oct 2013	B2
8549047	Beechuk et al.	Oct 2013	B2
8565117	Hilt et al.	Oct 2013	B2
8572391	Golan et al.	Oct 2013	B2
8576712	Sabat et al.	Nov 2013	B2
8577803	Chatterjee et al.	Nov 2013	B2
8582450	Robesky	Nov 2013	B1
8582737	Lawson et al.	Nov 2013	B2
8594626	Woodson et al.	Nov 2013	B1
8601136	Fahlgren et al.	Dec 2013	B1
8611338	Lawson et al.	Dec 2013	B2
8613102	Nath	Dec 2013	B2
8621598	Lai et al.	Dec 2013	B2
8649268	Lawson et al.	Feb 2014	B2
8656452	Li et al.	Feb 2014	B2
8667056	Proulx et al.	Mar 2014	B1
8675493	Buddhikot et al.	Mar 2014	B2
8688147	Nguyen et al.	Apr 2014	B2
8695077	Gerhard et al.	Apr 2014	B1
8713693	Shanabrook et al.	Apr 2014	B2
8728656	Takahashi et al.	May 2014	B2
8751801	Harris et al.	Jun 2014	B2
8755376	Lawson et al.	Jun 2014	B2
8767925	Sureka et al.	Jul 2014	B2
8781975	Bennett et al.	Jul 2014	B2
8797920	Parreira	Aug 2014	B2
8806024	Francis et al.	Aug 2014	B1
8819133	Wang	Aug 2014	B2
8825746	Ravichandran	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	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
9071677	Aggarwal et al.	Jun 2015	B2
9137127	Nowack	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	May 2016	B2
9356916	Kravitz et al.	May 2016	B2
9378337	Kuhr	Jun 2016	B2
9398622	Lawson et al.	Jul 2016	B2
9456008	Lawson et al.	Sep 2016	B2
9456339	Hildner et al.	Sep 2016	B1
9460169	Hinton et al.	Oct 2016	B2
9596274	Lawson et al.	Mar 2017	B2
9628624	Wolthuis et al.	Apr 2017	B2
9632875	Raichstein et al.	Apr 2017	B2
9634995	Binder	Apr 2017	B2
9648006	Lawson et al.	May 2017	B2
20010038624	Greenberg et al.	Nov 2001	A1
20010043684	Guedalia et al.	Nov 2001	A1
20010047406	Araujo	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	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	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	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	Miloslaysky 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	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	Marken 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	Oct 2006	A1
20060256816	Yarlagadda et al.	Nov 2006	A1
20060259307	Sanders	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	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
20070124536	Carper	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
20070250635	Hamilton	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	Jun 2008	A1
20080162482	Ahem 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	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	Schwartz	Apr 2009	A1
20090093250	Jackson et al.	Apr 2009	A1
20090094674	Schwartz et al.	Apr 2009	A1
20090125608	Werth et al.	May 2009	A1
20090129573	Gavan et al.	May 2009	A1
20090136011	Goel	May 2009	A1
20090170496	Bourque	Jul 2009	A1
20090171659	Pearce et al.	Jul 2009	A1
20090171669	Engelsma et al.	Jul 2009	A1
20090171752	Galvin et al.	Jul 2009	A1
20090182896	Patterson et al.	Jul 2009	A1
20090193433	Maes	Jul 2009	A1
20090216835	Jain et al.	Aug 2009	A1
20090217293	Wolber et al.	Aug 2009	A1
20090220057	Waters	Sep 2009	A1
20090221310	Chen et al.	Sep 2009	A1
20090222341	Belwadi et al.	Sep 2009	A1
20090225748	Taylor	Sep 2009	A1
20090225763	Forsberg et al.	Sep 2009	A1
20090228868	Drukman et al.	Sep 2009	A1
20090232289	Drucker et al.	Sep 2009	A1
20090234965	Viveganandhan et al.	Sep 2009	A1
20090235349	Lai et al.	Sep 2009	A1
20090241135	Wong et al.	Sep 2009	A1
20090252159	Lawson et al.	Oct 2009	A1
20090262725	Chen	Oct 2009	A1
20090276771	Nickolov et al.	Nov 2009	A1
20090288012	Udo 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	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	Aug 2010	A1
20100217982	Brown et al.	Aug 2010	A1
20100232594	Lawson	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	Jun 2011	A1
20110143714	Keast	Jun 2011	A1
20110145049	Udo et al.	Jun 2011	A1
20110149810	Koren et al.	Jun 2011	A1
20110149950	Petit-Huguenin et al.	Jun 2011	A1
20110151884	Zhao	Jun 2011	A1
20110158235	Senga	Jun 2011	A1
20110167172	Roach et al.	Jul 2011	A1
20110170505	Rajasekar et al.	Jul 2011	A1
20110176537	Lawson et al.	Jul 2011	A1
20110179126	Wetherell et al.	Jul 2011	A1
20110211679	Mezhibovsky et al.	Sep 2011	A1
20110251921	Kassaei et al.	Oct 2011	A1
20110253693	Lyons et al.	Oct 2011	A1
20110255675	Jasper et al.	Oct 2011	A1
20110258432	Rao	Oct 2011	A1
20110265168	Lucovsky et al.	Oct 2011	A1
20110265172	Sharma	Oct 2011	A1
20110267985	Wilkinson et al.	Nov 2011	A1
20110274111	Narasappa et al.	Nov 2011	A1
20110276892	Jensen-Horne et al.	Nov 2011	A1
20110276951	Jain	Nov 2011	A1
20110280390	Lawson et al.	Nov 2011	A1
20110283259	Lawson et al.	Nov 2011	A1
20110289126	Aikas et al.	Nov 2011	A1
20110289162	Furlong et al.	Nov 2011	A1
20110299672	Chiu et al.	Dec 2011	A1
20110310902	Xu	Dec 2011	A1
20110313950	Nuggehalli et al.	Dec 2011	A1
20110320449	Gudlavenkatasiva	Dec 2011	A1
20110320550	Lawson et al.	Dec 2011	A1
20120000903	Baarman et al.	Jan 2012	A1
20120011274	Moreman	Jan 2012	A1
20120017222	May	Jan 2012	A1
20120023531	Meuninck et al.	Jan 2012	A1
20120023544	Li et al.	Jan 2012	A1
20120027228	Rijken et al.	Feb 2012	A1
20120028602	Lisi et al.	Feb 2012	A1
20120036574	Heithcock et al.	Feb 2012	A1
20120039202	Song	Feb 2012	A1
20120059709	Lieberman et al.	Mar 2012	A1
20120079066	Li et al.	Mar 2012	A1
20120083266	VanSwol et al.	Apr 2012	A1
20120089572	Raichstein et al.	Apr 2012	A1
20120094637	Jeyaseelan et al.	Apr 2012	A1
20120101952	Raleigh et al.	Apr 2012	A1
20120110564	Ran et al.	May 2012	A1
20120114112	Rauschenberger et al.	May 2012	A1
20120149404	Beattie et al.	Jun 2012	A1
20120166488	Kaushik et al.	Jun 2012	A1
20120170726	Schwartz	Jul 2012	A1
20120173610	Bleau	Jul 2012	A1
20120174095	Natchadalingam et al.	Jul 2012	A1
20120179646	Hinton	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	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	Oct 2012	A1
20120281536	Gell et al.	Nov 2012	A1
20120288082	Segall	Nov 2012	A1
20120290706	Lin et al.	Nov 2012	A1
20120304245	Lawson	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
20130019297	Lawson et al.	Jan 2013	A1
20130029629	Lindholm et al.	Jan 2013	A1
20130031158	Salsburg	Jan 2013	A1
20130031613	Shanabrook	Jan 2013	A1
20130036476	Roever et al.	Feb 2013	A1
20130047232	Tuchman et al.	Feb 2013	A1
20130054517	Beechuk	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	Warshaysky Alex	Jan 2014	A1
20140025503	Meyer et al.	Jan 2014	A1
20140044123	Lawson et al.	Feb 2014	A1
20140058806	Guenette et al.	Feb 2014	A1
20140064467	Lawson	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	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	Oct 2014	A1
20140355600	Lawson	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, II	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
20160323320	Lawson et al.	Nov 2016	A1
20170339283	Chaudhary et al.	Nov 2017	A1

Foreign Referenced Citations (23)

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	Apr 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
018489	Feb 2009	WO
WO 2009018489	Feb 2009	WO
2009124223	Oct 2009	WO
2010037064	Apr 2010	WO
2010040010	Apr 2010	WO
WO 2010037064	Apr 2010	WO
2010101935	Sep 2010	WO
2011091085	Jul 2011	WO
WO-2012162397	Nov 2012	WO

Non-Patent Literature Citations (44)

Entry
“Ethernet to Token Ring Bridge”—Black Box Network Services, Oct. 1999 http://www2.blackboxab.se/Datablad/17044.pdf.
“Ethernet to Token ring Bridge”—Black Box Corporation, Oct. 1999 http://blackboxcanada.com/resource/files/productdetails/17044.pdf.
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. pp. 1-6.
Archive Microsoft Office 365 Email \| Retain Unified Archiving, 2015, GWAVA, Inc., Montreal, Canada.
Complaint for Patent Infringement, Telinit Technologies, LLC v. Twilio Inc., dated Oct. 12, 2012.
Kim et al. “In-service Feedback QoE Framework” 2010 Third International Conference on Communication Theory. Reliability and Quality of Service. pp. 135-138. 2010.
Matos et al. “Quality of Experience-based Routing in Multi-Service Wireless Mesh Networks” Realizing Advanced Video Optimized Wireless Networks. IEEE pp. 7060-7065. 2012.
NPL, “API Monetization Platform”, 2013.
RFC 3986: Uniform Resource Identifier (URI): Generic Syntax; T. Berners-Lee, R. Fielding, L. Masinter; Jan. 2005; The Internet Society.
S. barakovic and L. Skorin-Kapov. “Survey and Challenges of QoE Management Issues in Wireless Networks”. 2012, pp. 1-29.
Subramanya, et al. “Digital Signatures”, IEEE Potentials, Mar./Apr. 2006, pp. 5-8.
Tran et al. “User to User adaptive routing based on QoE” ICNS 2011: The Seventh International Conference on Networking and Services. pp. 170-177. 2011.
Twilio Cloud Communications—APIs for Voice, VoIP, and Text Messaging, Twilio.
Wu et al. “Quality Evaluation in Peer-to-Peer IPTV Services” Data Traffic and Monitoring Analysis, LNCS 7754. pp. 302-319. 2013.
“U.S. Appl. No. 13/478,495, Non Final Office Action dated Dec. 9, 2015”, 10 pgs.
“U.S. Appl. No. 13/478,495, Notice of Allowance dated Apr. 6, 2016”, 9 pgs.
“U.S. Appl. No. 13/478,495, Response filed Feb. 29, 2016 to Non Final Office Action dated Dec. 9, 2015”, 6 pgs.
“U.S. Appl. No. 13/478,495, Response filed Jun. 2, 2015 to Restriction Requirement dated May 20, 2015”, 7 pgs.
“U.S. Appl. No. 13/478,495, Restriction Requirement dated May 20, 2015”, 7 pgs.
“U.S. Appl. No. 13/624,739, Examiner Interview Summary dated Sep. 21, 2015”, 3 pgs.
“U.S. Appl. No. 13/624,739, Examiner Interview Summary dated Oct. 19, 2016”, 3 pgs.
“U.S. Appl. No. 13/624,739, Examiner Interview Summary dated Dec. 29, 2014”, 3 pgs.
“U.S. Appl. No. 13/624,739, Final Office Action dated Jul. 14, 2015”, 32 pgs.
“U.S. Appl. No. 13/624,739, Non Final Office Action dated Jul. 12, 2016”, 36 pgs.
“U.S. Appl. No. 13/624,739, Non Final Office Action dated Aug. 27, 2014”, 16 pgs.
“U.S. Appl. No. 13/624,739, Notice of Allowance dated Feb. 3, 2017”, 17 pgs.
“U.S. Appl. No. 13/624,739, Response filed Feb. 20, 2015 to Non Final Office Action dated Aug. 27, 2014”, 18 pgs.
“U.S. Appl. No. 13/624,739, Response filed Oct. 11, 2016 to Non Final Office Action dated Jul. 12, 2016”, 6 pgs.
“U.S. Appl. No. 13/624,739, Response filed Nov. 13, 2015 to Final Office Action dated Jul. 14, 2015”, 19 pgs.
“U.S. Appl. No. 14/054,254, Examiner Interview Summary dated Apr. 4, 2016”, 3 pgs.
“U.S. Appl. No. 14/054,254, Final Office Action dated Aug. 15, 2016”, 11 pgs.
“U.S. Appl. No. 14/054,254, Non Final Office Action dated Dec. 31, 2015”, 26 pgs.
“U.S. Appl. No. 14/054,254, Response filed Mar. 31, 2016 to Non Final Office Action dated Dec. 31, 2015”, 20 pgs.
“U.S. Appl. No. 15/184,621, Examiner Interview Summary dated Dec. 8, 2017”, 3 pgs.
“U.S. Appl. No. 15/184,621, Final Office Action dated Jan. 12, 2018”, 6 pgs.
“U.S. Appl. No. 15/184,621, Non Final Office Action dated Sep. 7, 2017”, 8 pgs.
“U.S. Appl. No. 15/184,621, Notice of Allowance dated Mar. 14, 2018”, 9 pgs.
“U.S. Appl. No. 15/184,621, Response filed Feb. 6, 2018 to Final Office Action dated Jan. 12, 2018”, 5 pgs.
“U.S. Appl. No. 15/184,621, Response filed Dec. 7, 2017 to Non Final Office Action dated Sep. 7, 2017”, 7 pgs.
“International Application Serial No. PCT/US2012/039151, International Preliminary Report Patentability dated Dec. 5, 2013”, 8 pgs.
“International Application Serial No. PCT/US2012/039151, International Search Report dated Jul. 19, 2012”, 2 pgs.
“International Application Serial No. PCT/US2012/039151, Written Opinion dated Jul. 19, 2012”, pgs.
Sadeghi, et al., “Token-Based Cloud Computing”, Horst Gortz Institute for IT-Security, Ruhr-University, [Online]. Retrieved from the Internet: <http://syssec.rub.de/media/trust/veroeffentlichungen/2010/05/26/SSW10.pdf>, (May 26, 2010).
“U.S. Appl. No. 15/184,621, Notice of Allowance dated Jul. 6, 2018”, 5 pgs.

Related Publications (1)

	Number	Date	Country
	20170142166 A1	May 2017	US

Provisional Applications (3)

Number	Date	Country
61537217	Sep 2011	US
61489189	May 2011	US
61500549	Jun 2011	US

Continuations (2)

	Number	Date	Country
Parent	14054254	Oct 2013	US
Child	15404751		US
Parent	14054254	Oct 2013	US
Child	15404751		US

Continuation in Parts (3)

	Number	Date	Country
Parent	13624739	Sep 2012	US
Child	14054254		US
Parent	15404751	Jan 2017	US
Child	14054254		US
Parent	13478495	May 2012	US
Child	14054254		US

System and method for real-time communication by using a client application communication protocol

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

Field of Search

US

CPC

International Classifications

Abstract