System and method for integrating session initiation protocol communication in a telecommunications platform

Description

TECHNICAL FIELD

This invention relates generally to the telecommunications platform field, and more specifically to a new and useful system and method for integrating session initiation protocol communication in a telecommunications platform in the telecommunications platform field.

BACKGROUND

Session Initiation Protocol (SIP) is a signaling protocol often used in establishing communication sessions. Such communication sessions can include voice, video, messaging, and other forms of communication. SIP is meant to be an application layer that is independent of the transport layer. Working with SIP to build applications and provide services may require a specialized skill set, and building applications on top of SIP may be challenging for some developers. In some cases, setting up a SIP endpoint may pose challenges to those hoping to do so quickly and easily. Thus, there is a need in the telecommunications platform field to create a new and useful system and method for integrating a session initiation protocol communication in a telecommunications platform. This invention provides such a new and useful system and method.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 is a schematic representation of a system of a preferred embodiment;

FIG. 2 is a flowchart representation of a method of a preferred embodiment.

FIG. 3 is sequence flow diagram of a method for implementing outbound SIP communications of a preferred embodiment;

FIG. 4 is a schematic representation of a variation of outside communication to a platform endpoint being mapped another endpoint;

FIG. 5 is a schematic representation of an account holder directing outbound communication through the communication platform;

FIGS. 6A and 6B are schematic representations of an exemplary use of establishing a communication session from an application programming interface call;

FIG. 7 is a schematic representation of communication nodes in a terminating use case;

FIG. 8 is a detailed sequence flow diagram of a terminating use case;

FIG. 9 is sequence flow diagram of a method for implementing inbound SIP communications of a preferred embodiment;

FIG. 10 is a schematic representation of communication nodes in an originating use case;

FIG. 11 is a detailed sequence flow diagram of an originating use case;

FIG. 12 is a schematic representation of an exemplary screenshot of a account routing configuration panel;

FIG. 13 is a schematic representation of an exemplary screenshot of a form to create a signaling and media endpoint with embedded parameters for a signaling application module;

FIG. 14 is an exemplary application of a signaling application module;

FIG. 15 is a sequence flow diagram of an exemplary use of a callback for error handling

FIG. 16 is a schematic representation of a method for registering a SIP endpoint of a preferred embodiment;

FIG. 17 is a schematic representation of an implementation of a method for registering a SIP endpoint of a preferred embodiment;

FIGS. 18 and 19 are sequence flow diagrams of methods for transitioning communication modes of a preferred embodiment;

FIGS. 20A-20D are schematic timeline representations of promoting and demoting a communication session;

FIG. 21 is a sequence flow diagram of one variation of a call transfer upgrade;

FIG. 22 is a sequence flow diagram of one variation of upgrading a basic communication through a REFER to a public-SIP-in;

FIG. 23 is a sequence flow diagram of one variation of upgrading a basic communication through a REFER to a public-SIP-out; and

FIG. 24 is a sequence flow diagram of one variation of upgrading a basic communication through a REFER handled through an edge service.

DESCRIPTION OF THE PREFERRED EMBODIMENTS

The following description of preferred embodiments of the invention is not intended to limit the invention to these preferred embodiments, but rather to enable any person skilled in the art to make and use this invention.

1. System for Integrating Session Initiation Protocol in a Platform

As shown in FIG. 1, a system for integrating session initiation protocol communication in a telecommunications platform is preferably a communication platform facilitating at least bridging communication endpoints through a signaling and media protocol in combination with dynamic programmatic responsive mechanisms. The communication platform is preferably a system substantially similar to the telephony platform described in U.S. patent application Ser. No. 12/417,630 filed 2 Apr. 2009, which is incorporated herein in its entirety by this reference. Herein, SIP is used in describing the signaling and media protocol, but any suitable protocol may alternatively be used in place of SIP. The system preferably functions to bridge signaling and media traffic with application layer interactions. Combining SIP-based communication with HTTP callbacks (or other suitable form of application layer callbacks) can enable a HTTP request/response application model in supplementing SIP communications with information and/or logic. The system can provide SIP trunking (e.g., originating and/or terminating variations), and logic can be integrated into the communication flow in a dynamic and customizable manner. Preferably, SIP data and/or other parameters from the communication session can be passed as parameters in the HTTP request transmitted to the callback resources, which can then track, react to, and/or alter the state of the communication session. Other parameters set within an account record, through an API request, embedded in the signaling communication can be used to enable various features and/or responses to the communication.

The system can be distributed across multiple regions. Each region can include carrier edge services, public SIP edge services, client edge services, a proxy core service, a trunking application, and optionally a communication application service. The system is preferably a multitenant platform wherein a plurality of different distinct users/accounts operates within the same infrastructure of the system. The system can include an account system, a billing system, and additionally services or components to facilitate other features and capabilities of the system. For example, the system can include event logging system, analytics system, recording services, conferencing services, communication queues, text-to-speech (TTS) services, transcription services, and/or any suitable component. A carrier edge service preferably functions to route all traffic to and from a carrier. An edge can be defined as a load balancer and a session-border-controller. A public SIP edge service preferably functions to route all traffic to and from a public SIP endpoint (trunking and non-trunking). A client edge service preferably functions to route all traffic to and from client applications of the communication platform (e.g., web applications or applications using SDK to interface through SIP with the communication platform).

The proxy core is preferably a component that manages/touches traffic of the communication platform as a communication router. The proxy core functions to making routing decisions for incoming and outgoing communications. For an incoming PSTN call (from a carrier to the carrier edge service to the proxy core), the proxy core determines if this is a trunking use case or an application use case. If a trunking use case, the proxy core signals to the trunking application. If an application use case, the proxy core signals to a communication application service. The use case is preferably determined based on the mapping of the destination number to a routing configuration identifier (e.g., a SIP address or an application URI). The proxy core additionally includes a callback engine that monitors SIP transaction messages and can initiate request response interactions with a callback resource over an application layer protocol in response to signaling and/or media events. Callback URIs are preferably configured for the communication platform through an API, a control user interface, or any suitable control mechanism. The communication platform may additionally include a registration record database. The registration record database is preferably used in maintaining routing information for devices that register a communication endpoint with the communication platform.

A trunking application functions to implement trunking functionality such as taking care of REFER SIP messages. In some implementations, the system can include communication application service. The communication application service preferably provides a higher level of communication applications such as voice based applications to play recordings, perform TTS, capture input caller, record messages, connect other endpoints, or control any suitable interaction during a communication session. Preferably the communication application service can function substantially similar to a call router that processes a document of telephony instructions such as in U.S. patent application Ser. No. 12/417,630.

The system can be operated to provide variety of different features. The system as one aspect can include registering and triggering callback resources, which function to make SIP trunking sessions reactive to signaling and media events. As another aspect, the system can use a unified registration system so that a phone number (or other suitable endpoint identifier) can be configured to perform trunking or run a communication application; further, fallback/error responses can be defined for either trunking or application execution. For example, the system can enable a SIP-URI to be associated with a phone number as a main mechanism for communication, but if the communication does fail, a failure callback can specify an application resource or another SIP-URI. In the case of a SIP-URI, the call can failover to the secondary SIP domain for trunking. In the case of an application resource (e.g., preferably specified as a URI of an application resource), then that application can be executed. Such a unified communication endpoint registration can similarly be used where an incoming call is initially handled by an application and fails over to a SIP-URI. As an example, a customer may have capacity for a set number of concurrent phone calls, and when the customer hits that limit, the system can automatically handle the overflow in accordance o the fallback resource. In this example, the unified registration for a number +1-415-555-1234 can have an incoming resource set as “sip:pbx.example.com” and a fallback callback as http://example.com/sorry.xml”. Then if the SIP server at sip:pbx.example.com is busy and responds with an error response, the system can access the fallback callback application. That callback application could play an error message or place in a queue until an agent is available or any suitable application logic.

Similarly, select media features such as recording may be enabled during a trunking communication session. An additional aspect can enable a communication session to dynamically transition between operating modes where a communication session may be established in a low-level trunking mode and then elevated to enable application processing or other media features. Operational mode transitioning can provide better use of resources and possibly allow customers to selectively reduce account usage (and consequently lower platform cost). As another element of the system, a signaling application module can function to provide customizable signaling endpoints wherein a signaling application module will extract and use embedded data of the endpoint identifier to alter signaling. The system is preferably configured to perform any suitable combination and/or subset of processes of the methods described above.

2. Session Initiation Protocol Communication in a Platform

As shown in FIG. 2, a method S100 for integrating session initiation protocol communication in a telecommunications platform of a first preferred embodiment can include receiving an outgoing communication request to a resource S110, establishing signaling and media communication in a session S120, registering a callback resource to a signaling event of the session S130, monitoring signaling messages of the session S140, detecting the signaling event in the signaling messages of the session S150, and triggering the callback resource upon detecting the signaling event S160. The method functions to bridge signaling and media traffic with HTTP as shown in FIG. 3. The method is preferably used in communications using SIP as a communication protocol but may alternatively be used in any suitable signaling and media communication protocol. Combining SIP-based communication with HTTP callbacks can enable a HTTP request/response application model in supplementing SIP communications with information and/or logic. Preferably, SIP data and/or other parameters from the communication session can be passed as parameters in the HTTP request transmitted to the callback resources, which can then track, react to, and/or alter the state of the communication session. The method is preferably implemented within a multitenant communication platform. The callback resources configuration is preferably stored and maintained for a plurality of accounts and/or sub-accounts.

The method can be applied to several different signaling and messaging use cases and communication topologies.

The method can be applied to terminating and originating SIP trunking scenarios. In the terminating use case described in more detail below, the call could originate from a PSTN endpoint, an outside SIP endpoint, an internal SIP endpoint, or any suitable type of endpoint. The terminating endpoint preferably depends on mapping of a destination endpoint to a SIP endpoint as shown in FIG. 4. The originating use case can allow account holders to make outbound SIP communication requests through the communication platform in association with their account. Originating outbound communication requests can include a layer of authentication to facilitate interfacing with outside endpoints on behalf of an account as shown in FIG. 5. Furthermore, there can be translation between the specified destination and the actual intended destination endpoint. In yet another variation, the signaling and media communication can be initiated through an API request, and the callback can be triggered during a signaling event between the communication platform and a communication endpoint. In one example, shown in FIG. 6A, an API request could initiate a call to a SIP endpoint (stages 1 and 2 in FIG. 6A); the signaling event of someone answering could result in retrieval and processing of callback resource that instructs the call to connect to another endpoint (e.g., a PSTN endpoint in the example of FIG. 6A). This API variation could similarly be applied in initially calling a PSTN number and connecting a SIP endpoint as shown in FIG. 6B. Such use cases may be applicable in connecting a customer and a customer service agent in response to an interaction on a website or mobile app.

Block S110, which includes receiving a communication request to a resource, functions to prompt, start or initiate a communication session. The resource in one variation can be to an endpoint with an account routing configuration (e.g., outside entities make a call into the communication platform). This variation will be discussed in more detail in method S200. The resource may alternatively be directed to an outside endpoint through the communication platform (e.g., PBX of an account holder sending an INVITE to 415-xxx-xxxx@<accountID>.<platform_domain> to make an termination trunking call to 415-xxx-xxxx). The request preferably includes a specified destination. The communication request can be received as a signaling message directed at a domain of the platform, where the signaling message is requesting to establish a media communication session with a communication endpoint. The outgoing communication request can be received as the platform facilitates SIP trunking termination. For example, a customer could be enabled to use a desk phone or a call center workstation behind an IP PBX to make a call to a cell phone or landline as shown in FIG. 7. When using SIP, the signaling message may be an INVITE, a REFER, or other suitable type of signaling message. The signaling message can originate from an IP public branch exchange (PBX) system that can reside off-premise (e.g., on-premise at a customer's infrastructure) as shown in FIG. 8. Alternatively, an IP PBX system can operate within the platform on behalf of one or more accounts. The signaling message can include an authentication token. An authentication token could be account credentials, an HMAC, a signed data package, or any suitable token used in verifying authenticity of the message. In one variation, authentication tokens can be passed through header parameters of the SIP request. Alternatively, receiving an outgoing communication request can include identifying an account of the communication platform that is mapped to a domain identifier of the originating endpoint (e.g., the domain of the SIP address) or the originating IP address. The credentials can be authenticated and verified as a request made on behalf of an account. If the credentials are successfully verified, the platform can establish media communication with the destination of the outgoing communication. The outgoing communication request can additionally include feature headers that specify communication features such as analytics, recording, media processing, transcription, or other suitable media properties. The outgoing communication request can additionally specify a callback resource to register for the session.

An outgoing communication may alternatively be initiated in response to an application programming interface (API) request of a telecommunications platform. The API request is preferably transmitted on behalf of an associated account and received at an API service of the platform. For example, an application or outside entity may make an API request to the communications platform to make an outgoing SIP based call. The outgoing communication may additionally be initiated from a telephony instruction in a communication application. In this use case the communication session is established between the communication platform and the destination endpoint. The callback resource may be used in detecting when the call is answered and beginning application execution or connecting to another endpoint. Though, an API request may be made to connect multiple endpoints.

The communication request is preferably for establishing an audio session between at least two parties. In one variation, the two parties can be the communication platform and a specified signaling and media endpoint. In another variation, the two parties can be the caller/originating endpoint and a destination endpoint. The destination endpoint may be specified in the request. The outgoing communication may alternatively establish a video session, a chat messaging session, an application communication session (e.g., a multi-player gaming session), screen sharing session, multimedia session, presence information session, or any suitable application of a communication session. Once instructions have been processed instructing a communication router to establish an outgoing communication, the communication router will preferably make an outgoing INVITE SIP request to a specified endpoint. Alternatively, the request may be a REFER SIP request or any suitable SIP request. The method may alternatively or additionally be used with other protocols for establishing a session.

Block S120, which includes establishing media communication in a session, functions to initiate, bridge, or connect an originating endpoint with a destination endpoint. The destination is preferably defined by the username identifier of the destination endpoint. The destination endpoint will preferably be another telephony endpoint such as a phone number, which will be connected through PSTN. A carrier can be selected and used to establish a media communication with the phone number. Alternatively, the phone number could be an alternative endpoint identifier wherein the media connection is established with a proxy signaling and media service of that alternative mode of communication. In yet another variation, the phone number of alternative endpoint identifier may be destination registered within the platform, wherein the method below for incoming communications may be used to establish the media communication with another SIP user agent. Once instructions have been processed instructing a communication router to establish an outgoing communication, a communication router will preferably make an outgoing INVITE SIP request to the specified destination endpoint. Alternatively, the request may be a REFER SIP request or any suitable SIP request. The method may alternatively or additionally be used with other protocols for establishing a session. If multiple endpoints are defined and do not have an established signaling and/or media connection, multiple endpoints may be contacted and included in the media communication.

Block S130, which includes registering a callback resource to a signaling event of the session, functions to associate, instantiate, or create a webhook, reactive resource, or event handler that is notified as a result of session messages, signaling patterns, and optionally media events. The registration of a callback resource preferably includes receiving a specified callback URI to associate with communication events. The callback resource may be set for an account, for a sub-account, for an endpoint, for a particular pattern of communication sessions, for a particular instance of communication (e.g., for the specific outgoing communication session) or for any particular categorization of communication sessions. A unique callback resource can be specified for a specific event. The specific event is preferably a type of signaling message, which may be the classification of the signaling message (e.g., INVITE, Ringing, 200 OK, BYE, etc.). The type of signaling message can alternatively be a pattern that can be defined by the parameters of a signaling message. For example, any SIP INVITE to an address with a particular area code in the user field of the ‘to’ field. A signaling event may also be defined by a set of different signaling patterns either generated by the communication platform or received from an endpoint. For example, a signaling event of hang-up could be triggered from the BYE message and/or a timeout in the signaling/media. Multiple callback resources can be registered to handle different types of signaling messages and/or to handle callbacks with different scopes (e.g., one callback scoped for all sessions made in association with an account and a second callback scope for a particular session instance). A multi-purpose callback resource may alternatively be specified, which can be a callback resource to handle callbacks for a variety of callback events. An end user (e.g., an outside developer) can configure the multi-purpose callback resource to parse parameters passed in to the callback resource so as to handle different events. In one exemplary implementation, the callback resource can be used in a SIP-based voice session and be triggered based on call events such as call starting, ringing, pickup, answering machine, hang up, DTMF input, and/or any suitable event of SIP-based voice sessions. Callback resources may alternatively be registered for any event of any suitable type of communication session. The callback resource may additionally be shared between other modalities of communication. For example, a callback URI may be registered for voice session initiation for PSTN voice calls and for SIP-based voice calls. The callback resource is preferably stored in a table mapping the callback resource to an account identifier, an application identifier, and/or an endpoint identifier.

The callback resource may be registered through an administrator control panel interface, through an API, in headers of an outgoing communication request, in the parameters of an outgoing communication instruction, or in any suitable location. In one instance, an outgoing communication request includes a parameter that defines the callback resource. The parameter can specify a callback resource URI or other suitable identifier and optionally a signaling event definition. In another instance, during a session, a signaling message can be received that includes a parameter defining the callback resource, wherein registering a callback resource comprises registering the callback resource according to the parameter in the signaling message. Accordingly, signaling messages can be processed to identify callback resource registration. In another instance, during the session, an API communication can be received that identifies the session and specifies a callback resource to register for a signaling message type. In another instance a callback resource is registered according to account settings associated with the account making the outgoing communication. Account settings can be set through an administrator control panel or through any suitable interface.

Other resources may additionally be configured for an account or an endpoint to promote robust SIP communication. A fallback URI may be configured to use if an application URI and/or a callback URI fails. A lost connection configuration may specify how a call is handled if a call is dropped. A lost connection configuration may direct the call to an error handling application URI (e.g., to read an error message and provide options). A lost connection configuration may alternatively specify actions to be taken to reestablish the connection.

Block S140 and S150, which include monitoring signaling messages of the session and detecting the signaling message type in the signaling messages of the session, function to process signaling and media transactions of the communication session. The communication messages made by a user agent client (e.g., the caller) or a user agent server (e.g., the callee) are preferably monitored. If a communication router detects a communication that has an associated callback resource, the callback resource is preferably triggered. The SIP communication may be monitored for a Trying message, Ringing (e.g., call is ringing), OK (e.g., answered), Bye (e.g., hang-up) and/or any suitable type of message. The transactional messages of SIP are preferably used to bridge SIP communications to HTTP based world.

Step S160, which includes triggering the callback resource upon detecting the signaling message type, functions to notify, message, or signal to a callback resource that an event has occurred. Triggering of a callback resource preferably enables evented web functionality with SIP communication. Preferably, an application layer communication (e.g., an HTTP request) is made to a configured callback resource URI. The callback resource URI is preferably a resource external to the platform and often controlled and/or operated by the account holder (though the callback resource URI can reasonably be a service operated by any suitable entity). The callback resource may alternatively be hosted and triggered using any suitable protocol. Additionally, communication to a callback resource can be annotated with session metadata such as SIP specific data associated with the session. Preferably, SIP data and/or other parameters from the communication session are passed as parameters in the HTTP request transmitted to the callback resource. For example, header fields of SIP transaction messages may be passed as parameters to the callback resource. The response from a callback resource may be used in the processing and handling of the communication session. For example, the callback resource may supply communication instructions to redirect the call, to hang-up, to record a conversation, to transcribe a conversation, or to perform any suitable action. The use of callback resources preferably enables SIP-based communication sessions to follow a HTTP request/response application model that many developers are familiar with from web development experience. In one variation, the callback resource is triggered and takes appropriate action external to the platform. A simple acknowledgment of being triggered may be returned to the platform. In another variation, a callback resource can provide an actionable response. The callback resource response can include communication instructions that are processed and executed in association with the session. For example, a response may be returned with telephony instructions that connect the session to another endpoint, enable media processing features, alter operating mode, execute telephony instructions, or direct any suitable form of action with the session.

As one exemplary use of the method, a SIP based communication session may be established through an implementation of terminating SIP trunking as described above. A client agent connected through a customer's IP PBX can carry on a synchronous media communication session (e.g., voice, video, etc.) with a destination endpoint accessed over a carrier or otherwise. A callback application can be registered for the session such that the callback application is triggered on detection of a BYE signal communicated from the destination endpoint leg of the communication. When the destination endpoint hangs up, the BYE signal message is received. In response to the BYE signal message, the communication platform can transmit a communication to a URI of the callback application. The callback application can take action within its infrastructure (e.g., logging, updating status, etc.) or alternatively respond with some communication directive to alter the media and/or signaling of the session for the leg of communication with the remaining endpoints connected to the session. In one variation, the operating mode can be upgraded to enable telephony instruction processing or other suitable media features.

In addition to using callback application registration to enable signaling and media communication protocols programmable and responsive. The method may additionally include enabling media processing through signaling directives or account configuration. Media processing can include recording, transcription, and/or other suitable media processing processes that can be added on top of basic trunking or communication-bridging services. Media processing services can be enabled similar to registering a callback resource. Media processing features can be enabled through an administrator control panel interface, through an API call, in headers of an outgoing communication request, in the parameters of an outgoing communication instruction, as a parameter passed in a signaling message during a session, or in any suitable manner.

In another variation described more below, the destination SIP endpoints could be a signaling application modules that follow defined application logic in response to data embedded in the destination endpoint. For example, multiple PSTN endpoints could be included in the user field, which may be contacted in parallel or in series until one answers the communication request.

2. Inbound Session Initiation Protocol Communications

As shown in FIG. 2, a method S200 for receiving inbound SIP communication of a second preferred embodiment can include receiving an incoming communication request S210, establishing a media communication in a session according to the incoming communication request S220, registering a callback resource to a signaling event S230, inspecting communication signaling messages of the communication session S240, detecting the signaling event from the communication signaling messages of the communication session S250, and triggering the callback resource upon detecting the signaling event S260. The method of the second preferred embodiment functions to allow inbound calls or communication requests to connect to an endpoint managed by the communication platform. The inbound calls are preferably from an outside entity. In a preferred implementation, the method is used to bridge SIP communication with a HTTP request/response model as with the method of the first preferred embodiment. In alternative implementations of the method, the method may be used in transitioning between basic SIP communications and application level communications. Basic SIP communications are preferably those established through SIP trunking in an originating call flow as shown in FIG. 10. Basic SIP communications preferably provide simple communication connections (e.g., simply bridging a communication session between a SIP device and a PSTN device) with minimal or selective processing or controlling communication interactions. The method preferably provides a way to enable rich media interactions injected into lightweight signaling and media communication flows.

Block S210, which includes receiving an incoming communication request, functions to initiate communication with a destination. The destination is preferably an endpoint managed by the communication platform. The incoming communication request preferably originates from some form of originating endpoint. In one variation, the communication request is a SIP communication request. The SIP communication request preferably specifies a destination endpoint identifier. The incoming SIP request may be initiated by any suitable device or application. DNS is preferably the mechanism in which the SIP communication request is directed to the communication platform. The inbound SIP request is preferably an INVITE request to start a communication session, but the request may be any suitable initiating instruction. The INVITE request may be received from an outside carrier or communication system. A carrier may use SIP or an alterative signaling and media protocol as a mechanism for bridging PSTN initiated call to the communication platform. The carrier may alternatively be another VoIP provider. Alternatively, the INVITE request may be initiated from within the communication platform (e.g., communication between account instances). In a second variation, the communication request can be any suitable incoming communication such as a PSTN based phone call.

Block S220, which includes establishing a media communication in a session according to the incoming communication request, functions to initiate, bridge, or connect an incoming communication with a destination endpoint. Preferably a media communication or stream can be established through the communication platform with the initiating endpoint (i.e., caller leg) and at least one destination endpoint (e.g., callee leg). The callee is preferably a signaling and media endpoint (e.g., SIP endpoint) connected through a public branch exchange or an alternative proxy. The media may additionally be redirected through additional media services, which have been selectively enabled for the session. For example, enabling of media services such as recording, transcription, analytics, API control, and/or other media processing features may be enabled through account configuration and/or session configuration. An account holder on the communication platform can preferably configure their account and optionally an IP PBX to facilitate originating SIP trunking. As shown in FIG. 11, a carrier may direct a SIP INVITE, REFER or other initiating signaling message to the communication platform. The addressing can specify an endpoint address (e.g., phone number, shortcode, endpoint identifier, etc.) in a user field of a SIP address. The domain of the SIP address can be a domain controlled by the communication platform or otherwise redirected to the communication platform. In one implementation of the method, the endpoint address is mapped to an account. For example, an account may have one or more phone numbers registered within the communication platform. Within the account settings, the endpoint address can be mapped to a primary account routing configuration. The account routing configuration can specify a URI, domain name, or other identifier of a resource that can handle the signaling and media communication as shown in FIG. 12. The communication platform then sends an invite addressed to the endpoint address within the resource specified in the account routing configuration. For example, the domain name of the account holder's IP PBX replaces that of the communication platform in the “to” field of the INVITE request. Additionally, the caller endpoint can be used in the username of the “from” field but with a domain of the communication platform, which can function to provide an easy way to call back the caller through the trunking service of the communication platform. Media can be established between the caller and the callee through the communication platform, and subsequent signaling can be routed through the communication platform.

Block S220 can include extracting an endpoint identifier which functions to map a destination endpoint identifier with an endpoint of the communication platform. In one preferred variation, the destination endpoint identifier in a signaled communication request will include a local portion (e.g., a username or phone number) and domain portion. The destination endpoint identifier preferably maps to an endpoint record. The endpoint record is preferably a stored model of the endpoint configurations, which may be stored in association with an account or sub-account. An endpoint record will preferably store a signaling endpoint, an application URI, and/or any callback URIs. Preferably, the communication platform maintains a database table that maps account secure identifiers to signaling endpoints or application secure identifiers. A second database table may maintain a mapping of application secure identifiers to application URIs. Other tables may maintain callback URI's. In one exemplary implementation, the endpoint identifiers of the communication platform use a syntax pattern with an application secure identifier and an account secure identifier as the local portion of the endpoint identifier. An example of an endpoint identifier may be applicationSID@accountSID.example.com, where accountSID is a unique secure account identifier. The endpoint identifier is preferably specified in a header of the SIP invite, but may alternatively be conveyed in any suitable parameter. The secure account identifier may be used in determining an application URI, any callback URIs, and machine address (e.g., IP address). Any suitable pattern may be used in the endpoint identifier such that the communication platform can properly route the request. In another preferred variation, the destination endpoint may be an endpoint associated with the protocol/medium of the incoming communication. For example, an incoming PSTN phone call may be directed at a phone number destination. The communication destination may additionally or alternatively be mapped to a signaling endpoint, an application URI, and/or any callback URIs in an endpoint record.

The incoming communication may additionally be authenticated. Due to the communication platform preferably being a multitenant platform, the method preferably uses the authentication process in identifying and selecting the proper routing and application settings to use in the communication session. The authentication may be performed at the load balancer, prior to being directed to the communication router, at the communication router, or at any suitable point.

In one preferred embodiment, establishing media communication can depend on selectively routing media according to customizable mapping as shown in FIG. 12. The method S200 can include mapping a destination endpoint specified in the incoming com communication signaling request to a primary account routing configuration; if the primary account routing configuration is a signaling endpoint, establishing a media stream communication of the communication session comprises routing an invitation signal to the signaling endpoint and establishing the media stream from a originating endpoint of the incoming communication request and the signaling endpoint; and if the primary account routing configuration is an application resource identifier, establishing a media stream communication of the communication session comprises retrieving and processing an application specified by the application resource identifier to direct the media stream. The customizable mapping functions to enable a communication platform to provide a unified endpoint configuration system where an endpoint can be configured to be routed directly to a communication endpoint or to a communication application with enhanced media processing. In this embodiment a destination endpoint identifier can be selectively invoke different behavior for different accounts. For example, some accounts would want an endpoint to initially route to a SIP phone while other accounts may want a telephony application to handle an inbound call. Additionally, the customizable mapping can include a secondary account routing configuration wherein upon detecting an error or other suitable communication event, establishing media communication according to the secondary account routing configuration. The primary routing configuration and the secondary account routing configuration could be a signaling communication endpoint such as a SIP address or domain name for an IP PBX resource or an application URI. In one account instance, an incoming call may be initially handled by a communication application and if that fails, fallback to connecting a SIP endpoint; while in another account instance, an incoming call can be connected to a SIP endpoint, and if that fails, fallback to a communication application (e.g., instructing a text to speech service to announce an error and instruct the caller to callback later). In other account instances, the primary and secondary routing configurations may both be signaling endpoints or both be communication applications.

In the variation, where the account routing configuration includes a signaling endpoint, establishing media communication can include establishing media communication from the originating endpoint to the destination of the signaling endpoint. For example if the signaling endpoint is “sip:pbx.example.com” and the call was to “sip:<phone_number>@<platform domain>” then the destination connected for media communication can be “<phone number>@pbx.example.com”. In one variation, two endpoints are connected for voice, video, screen-sharing, or other suitable form of a synchronous/real-time communication.

In a related variation, the destination signaling endpoint could be a signaling application module that follows defined logic in response to data embedded in the signaling endpoint stored in the account routing configuration. If the signaling endpoint is a signaling application module, the communication platform preferably routes the message according to the signaling endpoint logic above, but a signaling application module (a signaling and media proxy server) receives the communication request the invite is processed. Accordingly, the method can include routing to a signaling application module; at the signaling application module coordinating signaling with the signaling endpoint in accordance with the metadata. In this variation, the signaling endpoint includes metadata embedded in the endpoint identifier, and the signaling application module is additionally identified.

The signaling application modules are preferably hosted and provided by the communication platform, but outside entities could similarly host and operate the signaling application modules. A signaling application module can preferably be referenced as part of a signaling endpoint identifier. Parameters that define functionality of the signaling application module are additionally a part of the signaling endpoint identifier. A signaling application module preferably functions to provide a defined set of functionality that is commonly implemented for many users. A signaling application module could be defined to set up a conference call of multiple signaling endpoints, to call a set of endpoints in parallel and only connect the first one to pick up, to call a set of endpoints in series one after the other, and/or to serve any suitable use case. A web form or other suitable application can be used by a user to input the parameters of a particular signaling application module instance, and the form outputs a signaling endpoint with the parameters appropriately embedded in the address as shown in FIG. 13. Additionally or alternatively, a library could be provided that includes a function to facilitate generating a signaling endpoint with the parameters appropriately embedded. The library may be used in making outbound calls in method S100. For example, a signaling application module that calls a set of numbers in parallel may be generated to call three numbers in parallel and have a signaling endpoint of the pattern “<phone_number1>+<phone_number2>+<phone_number3>@parallelexample.com”, as shown in FIG. 14. The syntax of the signaling endpoint and embedded parameters can be any suitable syntax. An INVITE or other communication initiation communication is preferably delivered to a resource of the signaling application module. At the resource of the signaling application module, the signaling endpoint is parsed, interpreted, and applied in signaling and media logic. In the above example, the three numbers are extracted and then used as inputs to application logic that calls a set of endpoints in parallel. Signaling application modules can be used in method S100 or in method S200.

In an alternative variation, an incoming SIP communication request may specify communication application instructions within the SIP request. In one preferred implementation, SIP request headers can specify SIP communication instructions. Communication instructions embedded in the SIP request function to enable an application to be defined specifically for an incoming SIP call. The communication instructions may alternatively be specified in the body of the SIP request or in any suitable portion of the request. The request can preferably enable application control without configuring an application, because communication instructions can be configured directly in the SIP request. For example, a SIP request may enable one or more communication features of the communication platform by including the appropriate directives in the header of the SIP request. Using SIP request instructions may function to alleviate the system from providing full application stack support for the communication if the desired features for the communication are limited.

In the variation, where the account routing configuration includes a application resource identifier establishing media communication can include retrieving a communication application specified by the application resource identifier, which functions to send the request to an application server. A proxy core server preferably invites an application processing server (e.g., a call router), which then retrieves and executes communication application instructions. Retrieving a communication application can additionally be in response to the registered callback resource or optionally the secondary routing configuration used in error handling as shown in FIG. 15. The application server preferably hosts or generates application logic that can instruct the communication platform how to process, handle, or route the incoming communication request. A communication application is preferably a remotely hosted resource that can be accessed over HTTP, SPDY, alternative application layer protocol, or any suitable network protocol. Alternatively, a communication application may be hosted locally, within the communication platform, or accessed over any suitable protocol. Preferably, a request is sent to an application URI and, more preferably, the request is sent to a URI mapped to the endpoint identifier. An application server is preferably a third party server and, more preferably, the server is hosting a web application. The request is preferably sent to a server over a network. In one variation, the request is sent to a local server on a local area network. In yet another variation, the request may be sent to multiple servers. The request preferably encapsulates at least a portion of the state information from the communication request, such as the originating endpoint, the destination endpoint, the date and time of the initiating request, geographic location of the caller (e.g., country, city, and/or state, zip), session identifier, and/or the unique call ID, or other state properties of the communication. The request, more preferably, encapsulates all the state information of the call, but may alternatively include no state information or partial state information. The state information from the initiated communication session is preferably sent via HTTP POST in the request body, HTTP GET in the request URI, HTTP header parameters to mimic the data flow of a web browser, or by any combination or suitable alternative way. A communication application is preferably retrieved prior to establishing a communication session between the at least two endpoints. Alternatively, the communication session may, at least initially, be routed to the appropriate destination for a basic communication session, such as providing simple SIP trunking.

The instructions of the communication application can be processed in establishing media communication of the communication session. The communication platform and more preferably a communication router can convert the instructions of a communication application (e.g., server response) into communication actions or executable operations during the communication session. The communication instructions/actions for voice-based communication sessions may include, for example, playing a pre-recorded sound file at a server-specified URI (such as a static mp3 file located at http://demo.example.com/myapp/1234.mp3), reading text to the caller using text-to-speech technology, calling another number (such as creating a new voice connection through the PSTN, SIP/VoIP, or other IP technology system), collecting digits via DTMF input, recording voice response audio, TTY or other inputs, transcribing spoken words to text, sending an SMS/MMS message, putting a call on hold, ending a call, transferring a communication to another endpoint (e.g., other SIP-based devices, PSTN devices, or other suitable destinations), and/or any suitable combination or sequence of these or other suitable actions. The communication instructions may be any suitable instructions customized to the particular medium of communication such as video, text/media messaging, screen-sharing session, multi-user application session, or any suitable medium of communication. In the variations, where at least one feature is specified in the SIP request, the communication platform may configure the communication request to use a subset of communication resources. For example, if the SIP request included a header that specified that the call should be recorded and not processed by an application, then the communication session may flow through a resource that provides recording capabilities. Similarly, if the SIP request is determined to be one for SIP trunking, the SIP communication session may be established using basic resources for the communication session (e.g., not processing with an application stack).

Block S230, which includes registering a callback resource to a signaling event, functions to associate, instantiate, or create a webhook, resource, or event handler reactive to the communication session. Block S230 is preferably substantially similar to block S130 described above. The registration of a callback resource preferably includes receiving a specified callback URI to associate with communication events. The callback resource may be set for an account, for a sub-account, for an endpoint, for a particular pattern of communication sessions, for a particular instance of communication (e.g., for the specific outgoing communication session) or for any particular categorization of communication sessions. A unique callback resource can be specified for a specific event. A callback resource can be registered through an account routing configuration. In this variation, all calls to an endpoint would have the callback resource registered. A callback resource may additionally or alternatively be registered in response to header field or embedded parameter included in a signaling message. Such registration may require authentication parameters to verify that the registration can be authenticated on behalf of the corresponding account. For example, once a call is connected to an account SIP phone through an IP PBX of the account holder, the account holder could inject header parameters in a signaling message (e.g., an INFO signal) that registers a new or updated callback resource and includes signed tokens to verify that the request comes from the account holder. A callback resource can additionally or alternatively be registered through an API request or through any suitable mechanism.

Block S240 and S250, which include inspecting communication signaling messages of the communication session and detecting the signaling message type in the communication signaling messages of the communication session, function to process signaling and media transactions or the communication session. Applied to SIP trunking applications, blocks S240 and S250 can include monitoring SIP transactional messages. SIP transactional messages can be used to interact with evented resources such that SIP initiated communication sessions can be treated as request/response communications. Block S260, which includes triggering the callback resource upon detecting the signaling message type, functions to notify, message, or signal to a callback resource that an event has occurred. Triggering the callback resource preferably includes making an application layer communication to an external resource specified by the callback resource. Blocks S240, S250, and S260 can operate substantially similar to blocks S140, S150, and S160.

3. Registering Session Initiation Protocol Endpoints

As shown in FIG. 16, a method S300 for integrating session initiation protocol in a telecommunications platform of a third preferred embodiment can include receiving a SIP endpoint registration request S310, authenticating the registration request S320, and updating a registration record according to the registration request S330. The method S300 of the third preferred embodiment functions to register SIP endpoints to use the communication platform as a registrar for addresses of SIP communication. The method of registering SIP endpoints may be used in any suitable combination or variation of the methods described herein. A SIP device or application is preferably configured to register as a SIP endpoint of the communication platform. The communication platform preferably receives registration requests from the device or application and updates a maintained registration record so that the device can participate in communication sessions as shown in FIG. 17. The authentication of registration requests can provide a layer of security in the namespace of SIP endpoint registration. Additionally, the authentication of registration requests can be used in expanding the ways endpoints are registered.

Block S310, which includes receiving a SIP endpoint registration request, functions to obtain a notification for a registration update of at least one SIP endpoint on the communication platform. The registration request is preferably to add a new SIP endpoint, update an existing SIP endpoint, or remove an existing SIP endpoint. The registration request may originate from a device requesting to be registered. For example a SIP-based phone may be registered. As another example, a client device may use an application to register. The registration request may alternatively be transmitted over an API, submitted through an administrator user interface, or received from any suitable source.

The registration request preferably specifies a namespace identity and a device identity. The namespace identity preferably includes a communication platform identity (e.g., an account id) and a domain name. The communication platform identity is preferably an account identifier that functions as an account denormalizer. The communication platform identity may alternatively be a username, account secure id, sub-account id, or any suitable identifier for an entity of the communication platform. The communication platform identity may additionally include an application identifier. The domain name preferably conforms to DNS routing. The DNS is preferably configured to route SIP communication to that domain to the communication platform. For example, the namespace identity may be example123@example.com, where example123 refers to a particular account and example.com is used as the domain name in routing SIP requests. In one variation, accounts of the communication platform may be allowed to use a predefined domain name space. In another variation, accounts may be able to use any suitable verified domain. Verifying a domain may include receiving DNS configuration for a domain, accessing a verification signature at specified location of the domain (e.g., retrieving a text document with a verification signature from the root of the domain), using an authentication callback of the domain, completing an authentication process with the domain (e.g., oauth), or completing any suitable authentication process. Additionally, the domain registration techniques may be extended to using outside account systems for registering a namespace identity such as completing oauth authentication to use a social network identity as the namespace identity. The device identity preferably includes the IP address and port to contact the device, but any suitable addressing scheme may alternatively be used. A registered device may additionally be configured with a preferred transport such as TLS, UDP, SCTP, Web Socket, TCP, or any suitable protocol, but the use of DNS may also resolve the preferred transport.

Block S320, which includes authenticating the registration request, functions to add a layer of security prior to changing any records. As mentioned the communication platform is preferably a multitenant platform managing multiple accounts. Authenticating the registration request preferably verifies the identity of the request. The authentication may be used in authenticating that the changes to the registration records of the communication platform are allowed. A received registration request is preferably authenticated prior to updating registration records. In one variation, a device is preferably configured with an authentication token that is passed to the communication platform along with the registration request. The communication platform, upon receipt of the authentication token, preferably verifies the token for the registration request. If the authentication token is deemed valid, the registration request is processed.

Preferably, an outside service may be queried for permission. For example, a callback URI may be expected for at least a subset of domains. The callback URI may be based on the domain name of the namespace identifier in the request. The callback URI may alternatively be preconfigured, registered, or mapped by the communication platform to use a particular authentication technique. An authentication request is preferably transmitted to the callback URI along with at least a subset of information from the registration request. The outside resource will preferably perform any suitable authentication and then respond indicating if the registration request is allowed or denied. A preferred embodiment may employ the use of a callback URI to authenticate any suitable SIP communication (in addition to or in place of authenticating registration).

In one preferred implementation, authentication of the request may use a policy engine that functions to provide authentication for connection requests. The policy engine preferably authenticates a registration request from the client prior to completing the registration. The policy engine is preferably used in the authentication process of a preferred embodiment in a manner substantially similar to the authentication approach described in U.S. patent application Ser. No. 13/478,495 filed 23 May 2012, herein incorporated in its entirety by this reference. The policy engine preferably authenticates the request 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 adds or updates the registration in response to client authentication at the policy engine. 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 registration to complete. 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. Such security measures may additionally or alternatively be used in authentication and/or authorization for other methods and systems of preferred embodiments described herein.

The authentication may additionally or alternatively be in place to authorize that the request has legitimate permissions to use the included credentials. For example, if the registration request specifies a namespace with an outside domain name, the communication platform preferably verifies that the requester has permissions to use that outside domain. Verifying outside permissions may additionally result in updating or requesting updates in outside services such as making DNS changes. Permissions may additionally be authorized. Permissions may determine the actions allowed by the registered device. The numbers that can be called from that number or the numbers that can call in to the registered device may be limited. The modes of communication such as a messaging, voice sessions, video sessions, screen sharing sessions, application sessions, or other modes of communication may be set in the permissions. In one variation, a device may be limited to registration only and receiving calls. Any suitable permissions may be applied to a device.

Block S330, which includes updating a registration record according to the registration request, functions to add, augment, or remove registration records from the communication platform. The registration records are preferably stored in an accessible registration database. Routing tables and/or any suitable routing data or models may additionally be maintained such that inbound and/or outbound communication sessions can be established for the registered devices. In one use case, updating a registration record includes adding a device registration to the registration records. In another use case, updating a registration record includes editing information of an existing device registration. For example, the IP address may need to be updated for a registered device when the device changes to a different wifi network. The device will preferably transmit a new registration request to update the new IP address. In another use case, updating a registration record includes removing, deleting, or deactivating a registered device from the registration records. Any suitable update may alternatively be made. In one variation, multiple devices may be configured for a single endpoint. The multiple devices may be configured for any suitable cooperative use. In one example, multiple devices are prioritized so that if the highest priority device is not answered then the next highest priority device is called.

The method may additionally include routing inbound communication according to the registration record. An inbound communication may be received over any suitable mode of communication. The mode of communication may include messages, voice sessions, video sessions, screen sharing sessions, application sessions, or any suitable mode of communication. The inbound communication is preferably a SIP communication, but the inbound communication may have been initiated from any suitable protocol such as PSTN. Upon receiving an inbound communication, the registration database is queried to find the appropriate registration record. The registration record will preferably map a communication platform identifier (e.g., account identifier) to a device identity (e.g., a current IP address of the device). The inbound may simply specify the communication platform identifier to connect to the proper registered device. Additionally or alternatively, the inbound communication may specify a telephony endpoint such as a telephony number or short code, a username, or any alternative identifier. The communication platform preferably includes a database record mapping the alternative identifier to at least the communication platform identifier. For example, if the inbound communication specifies a phone number, that number is preferably mapped to an account identifier and then subsequently mapped through the registration database to a current IP address of the device.

Additionally, the method for registering SIP endpoints may include providing access to the registration data. Information from the registration database can preferably be accessed through an API. The registration database may be accessed through a REST API, a client interface (e.g., a JavaScript frontend interface), a device SDK interface (e.g., iOS or Android SDK interface), and/or any suitable interface. The interface can preferably be used to programmatically interact with the registration, see who and what devices are registered, see who is online, history of registration, duration of registration, location of registration, the permissions of registered users (e.g., who is registered to call a particular endpoint) and/or any suitable property of registration. The data in the registration database is preferably associated with at least one account, sub-account, or application id. Requests submitted through the interface preferably authenticate so that the permissions to access the requested registration information can be authorized.

4. Method for Transitioning between SIP operational modes

As shown in FIGS. 18 and 19, a method S400 for transitioning between SIP operational modes of a preferred embodiment can include establishing SIP communication session in a first mode S410, receiving a transition signal S420 and altering the operational mode of the communication session S430, which functions to change the resources used in processing the communication session. The variation preferably functions to enable basic SIP communication sessions (e.g., SIP trunking communication sessions) to be elevated to a communication processed by the application stack of the communication platform as shown in FIG. 18. Similarly, the variation may be used to demote a communication session using application/processing resources to use less or basic communication sessions as shown in FIG. 19. The operational modes thus preferably include a basic communication mode and an application stack communication mode, but any alternative operational mode may be used. In one variation, an operational mode may be defined for a particular feature or set of features of the application mode. For example, an operational mode may exist that routes the call through call recording resources. The basic communication mode is preferably used when a call or communication session is established from SIP trunking. The communication platform preferably established the SIP communication session, which is ran through a SIP proxy of the communication platform. The application stack communication mode is preferably used when a communication router uses a retrieved communication application when processing a communication. When in an application stack communication mode, the SIP session preferably has full application capabilities. An application can preferably modify state of the SIP session and perform actions such as redirect the call, hang-up, record a conversation, transcribe a conversation, send an message (e.g., SMS, MMS, application message), merge the call, and/or to perform any suitable action.

Step S410, which includes establishing SIP communication session in a first mode, functions to establish either a communication session in a basic, application, or another alternative communication mode. The method may be used to promote or demote the SIP communication mode. Additionally, modes may be changed any suitable number of times. As shown in FIG. 20A, a basic SIP communication mode may be promoted to use the capabilities of an application communication mode. As shown in FIG. 20B, a SIP session in an application communication mode may be demoted to forgo the application capabilities and operate in the basic SIP communication mode. As illustrated in FIGS. 20C and 20D, the communication mode may switch multiple times. The established SIP communication is preferably established in a manner substantially similar to the methods described above, but the SIP session may alternatively be established in any suitable manner.

Step S420, which includes receiving a transition signal, functions to obtain or identify a trigger to change modes of SIP communication. The transition signal may be received at any suitable point. The transition signal is preferably established and triggered through the programmatic features discussed above in methods S100 and S200. In one variation, the transition signal may be communicated in a SIP message. Either party may be able to trigger the altering of the operational mode of the communication session. Preferably, the SIP signaling may include an application ID, an authentication token, and/or any other credentials to specify how to transition the communication (e.g., which app to give control to and indicate the request is authentic and/or authorized). The transition signal may alternatively be submitted through an API request (preferably a REST API request). The REST API preferably has a resource in which the SIP session may be accessed and acted upon. The REST API preferably specifies the new mode of operation and, in the case of promoting the communication to an application communication mode, the REST API request may specify parameters for what application should initially control state. In yet another variation, a callback URI may be registered for a communication session and/or an endpoint so that the action may be triggered based on the SIP messages. For example, a callback may be registered for a basic SIP communication session so upon one of the endpoints hanging up the other endpoint is changed to an application communication mode with a pre-specified application. When the communication session mode is an application communication mode, an instruction of the application may trigger the change in the operational mode, essentially ending the application control of that application.

Step S430, which includes altering the operational mode of the communication session, functions to update the communication platform to use the appropriate resources to manage the communication session. When in a basic communication mode, the communication session is preferably routed through a SIP proxy. When in an application communication mode, the communication session is preferably routed through at least a communication router where at least a portion of an application is performed. When transitioning to the application communication mode, the steps associated with initiating a communication session with the communication platform are preferably performed in a substantially consistent manner. In one variation, if the communication is returning to the application communication mode for a second time, the communication router may remember at least partial state within the processing of application instructions. For example, if an application transfers the call to a basic mode, and then the call is returned to the application, the instructions after the initial transfer may be performed without having to retrieve new application instructions.

The method S400 is preferably used in combination with the methods S100 and S200 described above. Various signaling and media management approaches can be applied to achieve transitioning between operating modes. Altering the operational mode preferably includes onboarding new media and signaling resources into the session when upgrading an operational mode off boarding signaling and media resources of the session when downgrading, and/or otherwise modifying the set of signaling and media resources when transitioning.

As shown in FIG. 21, a SIP re-INVITE mechanism can be employed to upgrade or alternatively transfer a session. An existing signaling dialog can exist between a transferee (the entity that experiences the transition), the communication platform, an IP PBX and a SIP user agent. As shown in FIG. 21, the user agent can initiate the transfer. Alternatively the transfer may be initiated through an API, triggering of a registered callback, or initiated through any suitable mechanism. A REFER signaling message can be delivered which prompts the invite of the specified referrer, the target. The target could be another carrier or could be a communication application service. By supporting a SIP REFER message, the communication platform may support allowing any endpoint, including carriers, to do various transfer scenarios, which can include upgrading to an application operating mode. As shown in FIG. 22, an alternative signaling and media handling process accepts a REFER message to transition to an application mode. The referrer will preferably specify a referring endpoint. An INVITE to the endpoint is processed through the proxy core. As shown in the example of FIG. 22, the endpoint can be an application identifier such that the media communication will flow from the carrier through the carrier-media-gateway and the communication application service. The signaling and media flow can similarly use REFER to transition to targeting an external domain as shown in FIG. 23. The trunking app can additionally monitor when the transition occurs and meter the associated account appropriately such that an account may be billed at one rate when in SIP trunking mode and a second rate when in application mode. In another variation, the REFER may be handled through an edge service as shown in FIG. 24 where the public media gateway (PMG) facilitates upgrading the operation mode. Similarly, handing the REFER transparently at the edges could enable users to REFER to anything at any time, such that if operating in an application mode, the session could transition to a SIP trunking mode.

In one exemplary implementation, a basic communication mode may be provided by the communication platform at one usage rate and an application communication mode provided at a second usage rate. SIP trunking can use basic communication where communication is preferably channeled between the communicating endpoints. Since facilitating the basic communication session requires fewer/cheaper resources, SIP trunking communication sessions may be offered to users for a lower price. An agent, application, or service can preferably submit a transition signal if an entity decides to dynamically change the basic communication to use features of an application or service of the communication platform. Upon transitioning to the elevated operational mode, the communication session may be charged at a higher price rate for use of the application resources. The transition signal is preferably received through an API request, but may alternatively be received through any suitable channel. The variation of transitioning the operational mode of a communication session may additionally or alternatively be used with the method of the second preferred embodiment or during any established communication session.

The altering of the SIP communication mode may have numerous applications. In one exemplary use-case, an agent may be connected to a customer representative through a SIP session. The account associated with the phone number of the customer representative is preferably charged the basic communication mode rate (e.g., $0.001/min). When the customer representative has finished, a transition signal is preferably received, and the customer is seamlessly transitioned to a SIP communication session in an application communication mode. With the full capabilities of the application stack, a customer survey application may collect feedback from the customer before ending the call. During this survey application portion, the account may be charged an application customer mode rate (e.g., $0.01/min). In this example, the account was able to easily add a survey application without significantly increasing the cost of basic SIP communication. The communication mode changes are preferably transparent to the customer. In another exemplary use-case, a customer may call an endpoint for a calling card service. The call preferably starts the communication session in an application communication mode. The customer enters the code, and specifies the destination they wish to call. The application then transfers them to the desired number. For the portion of the communication session with the desired endpoint, the communication session is preferably demoted to a basic communication session to benefit from a lower rate. The caller may additionally be transferred to an application communication mode at the end of the call for other application related services, such as reading the balance of the calling card and the option to call another number. The altering of the communication mode may be used in any suitable application.

The system and methods of the preferred embodiment and variations thereof can be embodied and/or implemented at least in part as a machine configured to receive a computer-readable medium storing computer-readable instructions. The instructions are preferably executed by computer-executable components preferably integrated with the communication platform. The computer-readable medium can be stored on any suitable computer-readable media such as RAMs, ROMs, flash memory, EEPROMs, optical devices (CD or DVD), hard drives, floppy drives, or any suitable device. The computer-executable component is preferably a general or application specific processor, but any suitable dedicated hardware or hardware/firmware combination device can alternatively or additionally execute the instructions.

As a person skilled in the art will recognize from the previous detailed description and from the figures and claims, modifications and changes can be made to the preferred embodiments of the invention without departing from the scope of this invention defined in the following claims.

Claims

1. A method comprising: establishing, by a multi-tenant communication platform system, a Session Initiation Protocol (SIP) communication session between a first endpoint and a second endpoint;detecting occurrence of a first signaling event in the SIP communication session, the first signaling event being associated with a callback resource identifier that is registered to a first account of the multi-tenant communication platform system; andin response to detecting the occurrence of the first signaling event, transmitting a message to an external system identified by the callback resource identifier registered to the first account, the message including data associated with the SIP communication session.
2. The method of claim 1, further comprising: in response to receiving an Application Programming Interface (API) communication that specifies the callback resource identifier and the first signaling event: registering the callback resource identifier to the first account of the multi-tenant communication platform system, the callback resource identifier identifying the external system associated with the first account; andassociating the callback resource identifier with the first signaling event.
3. The method of claim 1, wherein the first signaling event is the first endpoint ending the communication session.
4. The method of claim 1, wherein the message transmitted to the external system is a HyperText Transfer Protocol (HTTP) message that includes parameters from the SIP communication session as parameters within the HTTP message.
5. The method of claim 4, wherein the parameters from the SIP communication session includes data from a header field of a SIP transaction message from the SIP communication session.
6. The method of claim 1, further comprising: receiving, from the external system, a response message, the response message including instructions to modify an operating mode of the SIP communication session; andmodifying the operating mode of the SIP communication session based on the instructions included in the response message.
7. The method of claim 6, wherein the external system determines the instructions based on the data associated with the SIP communication session that was included in the message transmitted to the external system.
8. The method of claim 6, wherein modifying the operating mode of the SIP communication session comprises redirecting the SIP communication session to a third endpoint.
9. The method of claim 6, wherein modifying the operating mode of the SIP communication session comprises terminating the SIP communication session.
10. The method of claim 6, wherein modifying the operating mode of the SIP communication session comprises initiating a recording service to record the SIP communication session.
11. A multi-tenant communication platform system comprising: one or more computer-processors; andone or more computer-readable mediums storing instructions that, when executed by the one or more computer-processors, cause the multi-tenant communication platform system to perform operations comprising: establishing a Session Initiation Protocol (SIP) communication session between a first endpoint and a second endpoint;detecting occurrence of a first signaling event in the SIP communication session, the first signaling event being associated with a callback resource identifier that is registered to a first account of the multi-tenant communication platform system; andin response to detecting the occurrence of the first signaling event, transmitting a message to an external system identified by the callback resource identifier registered to the first account, the message including data associated with the SIP communication session.
12. The multi-tenant communication platform system of claim 11, the operations further comprising: in response to receiving an Application Programming Interface (API) communication that specifies the callback resource identifier and the first signaling event: registering the callback resource identifier to the first account of the multi-tenant communication platform system, the callback resource identifier identifying the external system associated with the first account; andassociating the callback resource identifier with the first signaling event.
13. The multi-tenant communication platform system of claim 11, wherein the first signaling event is the first endpoint ending the communication session.
14. The multi-tenant communication platform system of claim 11, wherein the message transmitted to the external system is a HyperText Transfer Protocol (HTTP) message that includes parameters from the SIP communication session as parameters within the HTTP message.
15. The multi-tenant communication platform system of claim 14, wherein the parameters from the SIP communication session includes data from a header field of a SIP transaction message from the SIP communication session.
16. The multi-tenant communication platform system of claim 11, the operations further comprising: receiving, from the external system, a response message, the response message including instructions to modify an operating mode of the SIP communication session; andmodifying the operating mode of the SIP communication session based on the instructions included in the response message.
17. The multi-tenant communication platform system of claim 16, wherein the external system determines the instructions based on the data associated with the SIP communication session that was included in the message transmitted to the external system.
18. The multi-tenant communication platform system of claim 16, wherein modifying the operating mode of the SIP communication session comprises redirecting the SIP communication session to a third endpoint.
19. The multi-tenant communication platform system of claim 16, wherein modifying the operating mode of the SIP communication session comprises terminating the SIP communication session.
20. A non-transitory computer-readable medium storing instructions that, when executed by one or more computer-processors of a multi-tenant communication platform system, cause the multi-tenant communication platform system to perform operations comprising: establishing a Session Initiation Protocol (SIP) communication session between a first endpoint and a second endpoint;detecting occurrence of a first signaling event in the SIP communication session, the first signaling event being associated with a callback resource identifier that is registered to a first account of the multi-tenant communication platform system; andin response to detecting the occurrence of the first signaling event, transmitting a message to an external system identified by the callback resource identifier registered to the first account, the message including data associated with the SIP communication session.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of and claims priority to U.S. patent application Ser. No. 16/039,950, filed on Jul. 19, 2018, which is a Continuation of and claims priority to U.S. patent application Ser. No. 15/005,190, filed on Jan. 25, 2016, which is a continuation of U.S. patent application Ser. No. 14/208,920, filed on Mar. 13, 2014, now U.S. Pat. No. 9,282,124, which is a continuation of U.S. Provisional Patent Application Ser. No. 61/783,134, filed Mar. 14, 2013, and each of which are incorporated by reference herein in its entirety.

US Referenced Citations (780)

Number	Name	Date	Kind
5274700	Gechter et al.	Dec 1993	A
5526416	Dezonno et al.	Jun 1996	A
5581608	Jreij et al.	Dec 1996	A
5598457	Foladare et al.	Jan 1997	A
5867495	Elliott et al.	Feb 1999	A
5934181	Adamczewski	Aug 1999	A
5978465	Corduroy et al.	Nov 1999	A
6026440	Shrader et al.	Feb 2000	A
6034946	Roginsky et al.	Mar 2000	A
6094681	Shaffer et al.	Jul 2000	A
6138143	Gigliotti et al.	Oct 2000	A
6185565	Meubus et al.	Feb 2001	B1
6192123	Grunsted et al.	Feb 2001	B1
6206564	Adamczewski	Mar 2001	B1
6223287	Douglas et al.	Apr 2001	B1
6232979	Shochet	May 2001	B1
6269336	Ladd et al.	Jul 2001	B1
6317137	Rosasco	Nov 2001	B1
6363065	Thornton et al.	Mar 2002	B1
6373836	Deryugin et al.	Apr 2002	B1
6425012	Trovato et al.	Jul 2002	B1
6426995	Kim et al.	Jul 2002	B1
6430175	Echols et al.	Aug 2002	B1
6434528	Sanders	Aug 2002	B1
6445694	Swartz	Sep 2002	B1
6445776	Shank et al.	Sep 2002	B1
6459913	Cloutier	Oct 2002	B2
6463414	Su et al.	Oct 2002	B1
6493558	Bernhart et al.	Dec 2002	B1
6496500	Nance et al.	Dec 2002	B2
6501739	Cohen	Dec 2002	B1
6501832	Saylor et al.	Dec 2002	B1
6507875	Mellen-Garnett et al.	Jan 2003	B1
6571245	Huang et al.	May 2003	B2
6574216	Farris et al.	Jun 2003	B1
6577721	Vainio et al.	Jun 2003	B1
6600736	Ball et al.	Jul 2003	B1
6606596	Zirngibl et al.	Aug 2003	B1
6614783	Sonesh et al.	Sep 2003	B1
6625258	Ram et al.	Sep 2003	B1
6625576	Kochanski et al.	Sep 2003	B2
6636504	Albers et al.	Oct 2003	B1
6662231	Drosset et al.	Dec 2003	B1
6704785	Koo et al.	Mar 2004	B1
6707889	Saylor et al.	Mar 2004	B1
6711129	Bauer et al.	Mar 2004	B1
6711249	Weissman et al.	Mar 2004	B2
6738738	Henton	May 2004	B2
6757365	Bogard	Jun 2004	B1
6765997	Zirngibl et al.	Jul 2004	B1
6768788	Langseth et al.	Jul 2004	B1
6771955	Imura et al.	Aug 2004	B2
6778653	Kallas et al.	Aug 2004	B1
6785266	Swartz	Aug 2004	B2
6788768	Saylor et al.	Sep 2004	B1
6792086	Saylor et al.	Sep 2004	B1
6792093	Barak et al.	Sep 2004	B2
6798867	Zirngibl et al.	Sep 2004	B1
6807529	Johnson et al.	Oct 2004	B2
6807574	Partovi et al.	Oct 2004	B1
6819667	Brusilovsky et al.	Nov 2004	B1
6820260	Flockhart et al.	Nov 2004	B1
6829334	Zirngibl et al.	Dec 2004	B1
6831966	Tegan et al.	Dec 2004	B1
6834265	Balasuriya	Dec 2004	B2
6836537	Zirngibl et al.	Dec 2004	B1
6842767	Partovi et al.	Jan 2005	B1
6850603	Eberle et al.	Feb 2005	B1
6870830	Schuster et al.	Mar 2005	B1
6873952	Bailey et al.	Mar 2005	B1
6874084	Dobner et al.	Mar 2005	B1
6885737	Gao et al.	Apr 2005	B1
6888929	Saylor et al.	May 2005	B1
6895084	Saylor et al.	May 2005	B1
6898567	Balasuriya	May 2005	B2
6912581	Johnson et al.	Jun 2005	B2
6922411	Taylor	Jul 2005	B1
6928469	Duursma et al.	Aug 2005	B1
6931405	El-shimi et al.	Aug 2005	B2
6937699	Schuster et al.	Aug 2005	B1
6940953	Eberle et al.	Sep 2005	B1
6941268	Porter et al.	Sep 2005	B2
6947417	Laursen et al.	Sep 2005	B2
6947988	Saleh et al.	Sep 2005	B1
6961330	Cattan et al.	Nov 2005	B1
6964012	Zirngibl et al.	Nov 2005	B1
6970915	Partovi et al.	Nov 2005	B1
6977992	Zirngibl et al.	Dec 2005	B2
6981041	Araujo et al.	Dec 2005	B2
6985862	Strom et al.	Jan 2006	B2
6999576	Sacra	Feb 2006	B2
7003464	Ferrans et al.	Feb 2006	B2
7006606	Cohen et al.	Feb 2006	B1
7010586	Allavarpu et al.	Mar 2006	B1
7020685	Chen et al.	Mar 2006	B1
7039165	Saylor et al.	May 2006	B1
7058042	Bontempi et al.	Jun 2006	B2
7058181	Wright et al.	Jun 2006	B2
7062709	Cheung	Jun 2006	B2
7065637	Nanja	Jun 2006	B1
7076037	Gonen et al.	Jul 2006	B1
7076428	Anastasakos et al.	Jul 2006	B2
7089310	Ellerman et al.	Aug 2006	B1
7099442	Da Palma et al.	Aug 2006	B2
7103003	Brueckheimer et al.	Sep 2006	B2
7103171	Annadata et al.	Sep 2006	B1
7106844	Holland	Sep 2006	B1
7111163	Haney	Sep 2006	B1
7136932	Schneider	Nov 2006	B1
7140004	Kunins et al.	Nov 2006	B1
7143039	Stifelman et al.	Nov 2006	B1
7197331	Anastasakos et al.	Mar 2007	B2
7197461	Eberle et al.	Mar 2007	B1
7197462	Takagi et al.	Mar 2007	B2
7197544	Wang et al.	Mar 2007	B2
D540074	Peters	Apr 2007	S
7225232	Elberse	May 2007	B2
7227849	Rasanen	Jun 2007	B1
7245611	Narasimhan et al.	Jul 2007	B2
7260208	Cavalcanti	Aug 2007	B2
7266181	Zirngibl et al.	Sep 2007	B1
7269557	Bailey et al.	Sep 2007	B1
7272212	Eberle et al.	Sep 2007	B2
7272564	Phillips et al.	Sep 2007	B2
7277851	Henton	Oct 2007	B1
7283515	Fowler	Oct 2007	B2
7283519	Girard	Oct 2007	B2
7286521	Jackson et al.	Oct 2007	B1
7287248	Adeeb	Oct 2007	B1
7289453	Riedel et al.	Oct 2007	B2
7296739	Mo et al.	Nov 2007	B1
7298732	Cho	Nov 2007	B2
7298834	Homeier et al.	Nov 2007	B1
7308085	Weissman	Dec 2007	B2
7308408	Stifelman et al.	Dec 2007	B1
7324633	Gao et al.	Jan 2008	B2
7324942	Mahowald et al.	Jan 2008	B1
7328263	Sadjadi	Feb 2008	B1
7330463	Bradd et al.	Feb 2008	B1
7330890	Partovi et al.	Feb 2008	B1
7340040	Saylor et al.	Mar 2008	B1
7349714	Lee et al.	Mar 2008	B2
7369865	Gabriel et al.	May 2008	B2
7370329	Kumar et al.	May 2008	B2
7373660	Guichard et al.	May 2008	B1
7376223	Taylor et al.	May 2008	B2
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 et al.	Sep 2011	B2
8045689	Provenzale et al.	Oct 2011	B2
8046378	Zhuge et al.	Oct 2011	B1
8046823	Begen et al.	Oct 2011	B1
8069096	Ballaro et al.	Nov 2011	B1
8078483	Hirose et al.	Dec 2011	B1
8081744	Sylvain	Dec 2011	B2
8081958	Soderstrom et al.	Dec 2011	B2
8103725	Gupta et al.	Jan 2012	B2
8126128	Hicks, III et al.	Feb 2012	B1
8126129	Mcguire	Feb 2012	B1
8130750	Hester	Mar 2012	B2
8130917	Helbling et al.	Mar 2012	B2
8139730	Da Palma et al.	Mar 2012	B2
8145212	Lopresti et al.	Mar 2012	B2
8149716	Ramanathan et al.	Apr 2012	B2
8150918	Edelman et al.	Apr 2012	B1
8156213	Deng et al.	Apr 2012	B1
8165116	Ku et al.	Apr 2012	B2
8166185	Samuel et al.	Apr 2012	B2
8169936	Koren et al.	May 2012	B2
8175007	Jain et al.	May 2012	B2
8185619	Maiocco et al.	May 2012	B1
8196133	Kakumani et al.	Jun 2012	B2
8204479	Vendrow et al.	Jun 2012	B2
8214868	Hamilton et al.	Jul 2012	B2
8218457	Malhotra et al.	Jul 2012	B2
8233611	Zettner	Jul 2012	B1
8238533	Blackwell et al.	Aug 2012	B2
8243889	Taylor et al.	Aug 2012	B2
8249552	Gailloux et al.	Aug 2012	B1
8266327	Kumar et al.	Sep 2012	B2
8295272	Boni et al.	Oct 2012	B2
8301117	Keast et al.	Oct 2012	B2
8306021	Lawson et al.	Nov 2012	B2
8315198	Corneille et al.	Nov 2012	B2
8315369	Lawson et al.	Nov 2012	B2
8315620	Williamson et al.	Nov 2012	B1
8319816	Swanson et al.	Nov 2012	B1
8326805	Arous et al.	Dec 2012	B1
8335852	Hokimoto	Dec 2012	B2
8346630	Mckeown	Jan 2013	B1
8355394	Taylor et al.	Jan 2013	B2
8411669	Chen et al.	Apr 2013	B2
8413247	Hudis et al.	Apr 2013	B2
8417817	Jacobs	Apr 2013	B1
8429827	Wetzel	Apr 2013	B1
8438315	Tao et al.	May 2013	B1
8462670	Chien	Jun 2013	B2
8467502	Sureka et al.	Jun 2013	B2
8477926	Jasper et al.	Jul 2013	B2
8503639	Reding et al.	Aug 2013	B2
8503650	Reding et al.	Aug 2013	B2
8504818	Rao et al.	Aug 2013	B2
8509068	Begall et al.	Aug 2013	B2
8532686	Schmidt et al.	Sep 2013	B2
8533857	Tuchman et al.	Sep 2013	B2
8542805	Agranovsky et al.	Sep 2013	B2
8543665	Ansari et al.	Sep 2013	B2
8547962	Ramachandran et al.	Oct 2013	B2
8549047	Beechuk et al.	Oct 2013	B2
8565117	Hilt et al.	Oct 2013	B2
8572391	Golan et al.	Oct 2013	B2
8576712	Sabat et al.	Nov 2013	B2
8577803	Chatterjee et al.	Nov 2013	B2
8582450	Robesky	Nov 2013	B1
8582737	Lawson et al.	Nov 2013	B2
8594626	Woodson et al.	Nov 2013	B1
8601136	Fahlgren et al.	Dec 2013	B1
8611338	Lawson et al.	Dec 2013	B2
8613102	Nath	Dec 2013	B2
8621598	Lai et al.	Dec 2013	B2
8649268	Lawson et al.	Feb 2014	B2
8656452	Li et al.	Feb 2014	B2
8667056	Proulx et al.	Mar 2014	B1
8675493	Buddhikot et al.	Mar 2014	B2
8688147	Nguyen et al.	Apr 2014	B2
8695077	Gerhard et al.	Apr 2014	B1
8713693	Shanabrook et al.	Apr 2014	B2
8728656	Takahashi et al.	May 2014	B2
8751801	Harris et al.	Jun 2014	B2
8755376	Lawson et al.	Jun 2014	B2
8767925	Sureka et al.	Jul 2014	B2
8781975	Bennett et al.	Jul 2014	B2
8797920	Parreira	Aug 2014	B2
8806024	Toba Francis et al.	Aug 2014	B1
8819133	Wang	Aug 2014	B2
8825746	Ravichandran et al.	Sep 2014	B2
8837465	Lawson et al.	Sep 2014	B2
8838707	Lawson et al.	Sep 2014	B2
8843596	Goel et al.	Sep 2014	B2
8855271	Brock et al.	Oct 2014	B2
8861510	Fritz	Oct 2014	B1
8879547	Maes	Nov 2014	B2
8903938	Vermeulen et al.	Dec 2014	B2
8918848	Sharma et al.	Dec 2014	B2
8924489	Bleau et al.	Dec 2014	B2
8938053	Cooke et al.	Jan 2015	B2
8948356	Nowack et al.	Feb 2015	B2
8954591	Ganesan et al.	Feb 2015	B2
8964726	Lawson et al.	Feb 2015	B2
8990610	Bostick et al.	Mar 2015	B2
9014664	Kim et al.	Apr 2015	B2
9015702	Bhat	Apr 2015	B2
9031223	Smith et al.	May 2015	B2
9071677	Aggarwal et al.	Jun 2015	B2
9137127	Nowack et al.	Sep 2015	B2
9141682	Adoc, Jr. et al.	Sep 2015	B1
9161296	Parsons et al.	Oct 2015	B2
9177007	Winters et al.	Nov 2015	B2
9204281	Ramprasad et al.	Dec 2015	B2
9210275	Lawson et al.	Dec 2015	B2
9306982	Lawson et al.	Apr 2016	B2
9307094	Nowack et al.	Apr 2016	B2
9325624	Malatack et al.	Apr 2016	B2
9338190	Eng et al.	May 2016	B2
9344573	Wolthuis et al.	May 2016	B2
9356916	Kravitz et al.	May 2016	B2
9378337	Kuhr	Jun 2016	B2
9398622	Lawson et al.	Jul 2016	B2
9456008	Lawson et al.	Sep 2016	B2
9456339	Hildner et al.	Sep 2016	B1
9460169	Hinton et al.	Oct 2016	B2
9596274	Lawson et al.	Mar 2017	B2
9628624	Wolthuis et al.	Apr 2017	B2
9632875	Raichstein et al.	Apr 2017	B2
9634995	Binder	Apr 2017	B2
9699127	Lennstrom et al.	Jul 2017	B2
10051011	Boerjesson et al.	Aug 2018	B2
10560490	Boerjesson et al.	Feb 2020	B2
20010038624	Greenberg et al.	Nov 2001	A1
20010043684	Guedalia et al.	Nov 2001	A1
20010051996	Cooper et al.	Dec 2001	A1
20020006124	Jimenez et al.	Jan 2002	A1
20020006125	Josse et al.	Jan 2002	A1
20020006193	Rodenbusch et al.	Jan 2002	A1
20020025819	Cetusic et al.	Feb 2002	A1
20020057777	Saito et al.	May 2002	A1
20020064267	Martin et al.	May 2002	A1
20020067823	Walker et al.	Jun 2002	A1
20020077833	Arons et al.	Jun 2002	A1
20020126813	Partovi et al.	Sep 2002	A1
20020133587	Ensel et al.	Sep 2002	A1
20020136391	Armstrong et al.	Sep 2002	A1
20020165957	Devoe et al.	Nov 2002	A1
20020176378	Hamilton et al.	Nov 2002	A1
20020184361	Eden	Dec 2002	A1
20020198941	Gavrilescu et al.	Dec 2002	A1
20030006137	Wei et al.	Jan 2003	A1
20030012356	Zino et al.	Jan 2003	A1
20030014665	Anderson et al.	Jan 2003	A1
20030018830	Chen et al.	Jan 2003	A1
20030023672	Vaysman	Jan 2003	A1
20030026426	Wright et al.	Feb 2003	A1
20030046366	Pardikar et al.	Mar 2003	A1
20030051037	Sundaram et al.	Mar 2003	A1
20030058884	Kallner et al.	Mar 2003	A1
20030059020	Meyerson et al.	Mar 2003	A1
20030060188	Gidron et al.	Mar 2003	A1
20030061317	Brown et al.	Mar 2003	A1
20030061404	Atwal et al.	Mar 2003	A1
20030088421	Maes et al.	May 2003	A1
20030097330	Hillmer et al.	May 2003	A1
20030097447	Johnston	May 2003	A1
20030097639	Niyogi et al.	May 2003	A1
20030103620	Brown et al.	Jun 2003	A1
20030123640	Roelle et al.	Jul 2003	A1
20030149721	Alfonso-nogueiro et al.	Aug 2003	A1
20030162506	Toshimitsu et al.	Aug 2003	A1
20030195950	Huang et al.	Oct 2003	A1
20030195990	Greenblat et al.	Oct 2003	A1
20030196076	Zabarski et al.	Oct 2003	A1
20030204616	Billhartz et al.	Oct 2003	A1
20030211842	Kempf et al.	Nov 2003	A1
20030231647	Petrovykh	Dec 2003	A1
20030233276	Pearlman et al.	Dec 2003	A1
20040008635	Nelson et al.	Jan 2004	A1
20040011690	Marfino et al.	Jan 2004	A1
20040044953	Watkins et al.	Mar 2004	A1
20040052349	Creamer et al.	Mar 2004	A1
20040071275	Bowater et al.	Apr 2004	A1
20040101122	Da Palma et al.	May 2004	A1
20040102182	Reith et al.	May 2004	A1
20040117788	Karaoguz et al.	Jun 2004	A1
20040136324	Steinberg et al.	Jul 2004	A1
20040165569	Sweatman et al.	Aug 2004	A1
20040172482	Weissman et al.	Sep 2004	A1
20040199572	Hunt et al.	Oct 2004	A1
20040205101	Radhakrishnan	Oct 2004	A1
20040205689	Ellens et al.	Oct 2004	A1
20040213400	Golitsin et al.	Oct 2004	A1
20040216058	Chavers et al.	Oct 2004	A1
20040218748	Fisher	Nov 2004	A1
20040228469	Andrews et al.	Nov 2004	A1
20040236696	Aoki et al.	Nov 2004	A1
20040240649	Goel	Dec 2004	A1
20050005109	Castaldi et al.	Jan 2005	A1
20050005200	Matena et al.	Jan 2005	A1
20050010483	Ling	Jan 2005	A1
20050015505	Kruis et al.	Jan 2005	A1
20050021626	Prajapat et al.	Jan 2005	A1
20050025303	Hostetler, Jr.	Feb 2005	A1
20050038772	Colrain	Feb 2005	A1
20050043952	Sharma et al.	Feb 2005	A1
20050047579	Mansour	Mar 2005	A1
20050060411	Coulombe et al.	Mar 2005	A1
20050083907	Fishler	Apr 2005	A1
20050091336	Dehamer et al.	Apr 2005	A1
20050091572	Gavrilescu et al.	Apr 2005	A1
20050108770	Karaoguz et al.	May 2005	A1
20050125251	Berger et al.	Jun 2005	A1
20050125739	Thompson et al.	Jun 2005	A1
20050128961	Miloslavsky et al.	Jun 2005	A1
20050135578	Ress et al.	Jun 2005	A1
20050141500	Bhandari et al.	Jun 2005	A1
20050147088	Bao et al.	Jul 2005	A1
20050177635	Schmidt et al.	Aug 2005	A1
20050181835	Lau et al.	Aug 2005	A1
20050198292	Duursma et al.	Sep 2005	A1
20050228680	Malik	Oct 2005	A1
20050238153	Chevalier	Oct 2005	A1
20050240659	Taylor	Oct 2005	A1
20050243977	Creamer et al.	Nov 2005	A1
20050246176	Creamer et al.	Nov 2005	A1
20050289222	Sahim	Dec 2005	A1
20060008065	Longman et al.	Jan 2006	A1
20060008073	Yoshizawa et al.	Jan 2006	A1
20060008256	Khedouri et al.	Jan 2006	A1
20060015467	Morken et al.	Jan 2006	A1
20060021004	Moran et al.	Jan 2006	A1
20060023676	Whitmore et al.	Feb 2006	A1
20060047666	Bedi et al.	Mar 2006	A1
20060067506	Flockhart et al.	Mar 2006	A1
20060080415	Tu	Apr 2006	A1
20060098624	Morgan et al.	May 2006	A1
20060129638	Deakin	Jun 2006	A1
20060143007	Koh et al.	Jun 2006	A1
20060146792	Ramachandran et al.	Jul 2006	A1
20060146802	Baldwin et al.	Jul 2006	A1
20060168334	Potti et al.	Jul 2006	A1
20060203979	Jennings	Sep 2006	A1
20060209695	Archer, Jr. et al.	Sep 2006	A1
20060212865	Vincent et al.	Sep 2006	A1
20060215824	Mitby et al.	Sep 2006	A1
20060217823	Hussey	Sep 2006	A1
20060217978	Mitby et al.	Sep 2006	A1
20060222166	Ramakrishna et al.	Oct 2006	A1
20060235715	Abrams et al.	Oct 2006	A1
20060256816	Yarlagadda et al.	Nov 2006	A1
20060262915	Marascio et al.	Nov 2006	A1
20060270386	Yu et al.	Nov 2006	A1
20060285489	Francisco et al.	Dec 2006	A1
20070002744	Mewhinney et al.	Jan 2007	A1
20070036143	Alt et al.	Feb 2007	A1
20070038499	Margulies et al.	Feb 2007	A1
20070043681	Morgan et al.	Feb 2007	A1
20070050306	McQueen	Mar 2007	A1
20070064672	Raghav et al.	Mar 2007	A1
20070070906	Thakur	Mar 2007	A1
20070070980	Phelps et al.	Mar 2007	A1
20070071223	Lee et al.	Mar 2007	A1
20070074174	Thornton	Mar 2007	A1
20070088836	Tai et al.	Apr 2007	A1
20070091907	Seshadri et al.	Apr 2007	A1
20070107048	Halls et al.	May 2007	A1
20070112574	Greene	May 2007	A1
20070116191	Bermudez et al.	May 2007	A1
20070121651	Casey et al.	May 2007	A1
20070127691	Lert	Jun 2007	A1
20070127703	Siminoff	Jun 2007	A1
20070130260	Weintraub et al.	Jun 2007	A1
20070133771	Stifelman et al.	Jun 2007	A1
20070147351	Dietrich et al.	Jun 2007	A1
20070149166	Turcotte et al.	Jun 2007	A1
20070153711	Dykas et al.	Jul 2007	A1
20070167170	Fitchett et al.	Jul 2007	A1
20070192629	Saito	Aug 2007	A1
20070201448	Baird et al.	Aug 2007	A1
20070208862	Fox et al.	Sep 2007	A1
20070232284	Mason et al.	Oct 2007	A1
20070239761	Baio et al.	Oct 2007	A1
20070242626	Altberg et al.	Oct 2007	A1
20070255828	Paradise	Nov 2007	A1
20070265073	Novi et al.	Nov 2007	A1
20070286180	Marquette et al.	Dec 2007	A1
20070291734	Bhatia et al.	Dec 2007	A1
20070291905	Halliday et al.	Dec 2007	A1
20070293200	Roundtree et al.	Dec 2007	A1
20070295803	Levine et al.	Dec 2007	A1
20080005275	Overton et al.	Jan 2008	A1
20080008157	Edge et al.	Jan 2008	A1
20080025320	Bangalore et al.	Jan 2008	A1
20080037715	Prozeniuk et al.	Feb 2008	A1
20080037746	Dufrene et al.	Feb 2008	A1
20080040484	Yardley	Feb 2008	A1
20080049617	Grice et al.	Feb 2008	A1
20080052395	Wright et al.	Feb 2008	A1
20080091843	Kulkarni	Apr 2008	A1
20080101571	Harlow et al.	May 2008	A1
20080104348	Kabzinski et al.	May 2008	A1
20080120702	Hokimoto	May 2008	A1
20080123559	Haviv et al.	May 2008	A1
20080134049	Gupta et al.	Jun 2008	A1
20080139166	Agarwal et al.	Jun 2008	A1
20080146268	Gandhi et al.	Jun 2008	A1
20080152101	Griggs	Jun 2008	A1
20080154601	Stifelman et al.	Jun 2008	A1
20080155029	Helbling et al.	Jun 2008	A1
20080162482	Ahern et al.	Jul 2008	A1
20080165708	Moore et al.	Jul 2008	A1
20080172404	Cohen	Jul 2008	A1
20080177883	Hanai et al.	Jul 2008	A1
20080192736	Jabri et al.	Aug 2008	A1
20080201426	Darcie	Aug 2008	A1
20080209050	Li	Aug 2008	A1
20080212945	Khedouri et al.	Sep 2008	A1
20080222656	Lyman	Sep 2008	A1
20080229421	Hudis et al.	Sep 2008	A1
20080232574	Baluja et al.	Sep 2008	A1
20080235230	Maes	Sep 2008	A1
20080256224	Kaji et al.	Oct 2008	A1
20080275741	Loeffen	Nov 2008	A1
20080307436	Hamilton	Dec 2008	A1
20080310599	Purnadi et al.	Dec 2008	A1
20080313318	Vermeulen et al.	Dec 2008	A1
20080316931	Qiu et al.	Dec 2008	A1
20080317222	Griggs et al.	Dec 2008	A1
20080317232	Couse et al.	Dec 2008	A1
20080317233	Rey et al.	Dec 2008	A1
20090046838	Andreasson	Feb 2009	A1
20090052437	Taylor et al.	Feb 2009	A1
20090052641	Taylor et al.	Feb 2009	A1
20090059894	Jackson et al.	Mar 2009	A1
20090063502	Coimbatore et al.	Mar 2009	A1
20090074159	Goldfarb et al.	Mar 2009	A1
20090075684	Cheng et al.	Mar 2009	A1
20090083155	Tudor et al.	Mar 2009	A1
20090089165	Sweeney	Apr 2009	A1
20090089352	Davis et al.	Apr 2009	A1
20090089699	Saha et al.	Apr 2009	A1
20090093250	Jackson et al.	Apr 2009	A1
20090094674	Schwartz et al.	Apr 2009	A1
20090122793	Yang	May 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
20090276771	Nickolov et al.	Nov 2009	A1
20090288012	Hertel et al.	Nov 2009	A1
20090288165	Qiu et al.	Nov 2009	A1
20090300194	Ogasawara	Dec 2009	A1
20090316687	Kruppa	Dec 2009	A1
20090318112	Vasten	Dec 2009	A1
20100027531	Kurashima	Feb 2010	A1
20100037204	Lin et al.	Feb 2010	A1
20100054142	Moiso et al.	Mar 2010	A1
20100070424	Monk	Mar 2010	A1
20100071053	Ansari et al.	Mar 2010	A1
20100082513	Liu	Apr 2010	A1
20100087215	Gu et al.	Apr 2010	A1
20100088187	Courtney et al.	Apr 2010	A1
20100088698	Krishnamurthy	Apr 2010	A1
20100094758	Chamberlain et al.	Apr 2010	A1
20100103845	Ulupinar et al.	Apr 2010	A1
20100107222	Glasser	Apr 2010	A1
20100115041	Hawkins et al.	May 2010	A1
20100138501	Clinton et al.	Jun 2010	A1
20100142516	Lawson et al.	Jun 2010	A1
20100150139	Lawson et al.	Jun 2010	A1
20100167689	Sepehri-Nik et al.	Jul 2010	A1
20100188979	Thubert et al.	Jul 2010	A1
20100191915	Spencer	Jul 2010	A1
20100208881	Kawamura	Aug 2010	A1
20100217837	Ansari et al.	Aug 2010	A1
20100217982	Brown et al.	Aug 2010	A1
20100232594	Lawson	Sep 2010	A1
20100235539	Carter et al.	Sep 2010	A1
20100250946	Korte et al.	Sep 2010	A1
20100251329	Wei	Sep 2010	A1
20100251340	Martin et al.	Sep 2010	A1
20100265825	Blair et al.	Oct 2010	A1
20100281108	Cohen	Nov 2010	A1
20100291910	Sanding et al.	Nov 2010	A1
20100299437	Moore	Nov 2010	A1
20100312919	Lee et al.	Dec 2010	A1
20100332852	Vembu et al.	Dec 2010	A1
20110026516	Roberts et al.	Feb 2011	A1
20110029882	Jaisinghani	Feb 2011	A1
20110029981	Jaisinghani	Feb 2011	A1
20110053555	Cai et al.	Mar 2011	A1
20110078278	Cui et al.	Mar 2011	A1
20110081008	Lawson et al.	Apr 2011	A1
20110083069	Paul et al.	Apr 2011	A1
20110083179	Lawson et al.	Apr 2011	A1
20110093516	Geng et al.	Apr 2011	A1
20110096673	Stevenson et al.	Apr 2011	A1
20110110366	Moore et al.	May 2011	A1
20110131293	Mori	Jun 2011	A1
20110138453	Verma et al.	Jun 2011	A1
20110143714	Keast et al.	Jun 2011	A1
20110145049	Hertel et al.	Jun 2011	A1
20110149810	Koren et al.	Jun 2011	A1
20110149950	Petit-Huguenin et al.	Jun 2011	A1
20110151884	Zhao	Jun 2011	A1
20110158235	Senga	Jun 2011	A1
20110167172	Roach et al.	Jul 2011	A1
20110170505	Rajasekar et al.	Jul 2011	A1
20110176537	Lawson et al.	Jul 2011	A1
20110179126	Wetherell et al.	Jul 2011	A1
20110191778	Shimizu	Aug 2011	A1
20110211679	Mezhibovsky et al.	Sep 2011	A1
20110251921	Kassaei et al.	Oct 2011	A1
20110253693	Lyons et al.	Oct 2011	A1
20110255675	Jasper et al.	Oct 2011	A1
20110258432	Rao et al.	Oct 2011	A1
20110265168	Lucovsky et al.	Oct 2011	A1
20110265172	Sharma	Oct 2011	A1
20110267985	Wilkinson et al.	Nov 2011	A1
20110274111	Narasappa et al.	Nov 2011	A1
20110276892	Jensen-Horne et al.	Nov 2011	A1
20110276951	Jain	Nov 2011	A1
20110280390	Lawson et al.	Nov 2011	A1
20110283259	Lawson et al.	Nov 2011	A1
20110289126	Aikas et al.	Nov 2011	A1
20110289162	Furlong et al.	Nov 2011	A1
20110299672	Chiu et al.	Dec 2011	A1
20110310902	Xu	Dec 2011	A1
20110313950	Nuggehalli et al.	Dec 2011	A1
20110320449	Gudlavenkatasiva	Dec 2011	A1
20110320550	Lawson et al.	Dec 2011	A1
20120000903	Baarman et al.	Jan 2012	A1
20120011274	Moreman	Jan 2012	A1
20120017222	May	Jan 2012	A1
20120023531	Meuninck et al.	Jan 2012	A1
20120023544	Li et al.	Jan 2012	A1
20120027228	Rijken et al.	Feb 2012	A1
20120028602	Lisi et al.	Feb 2012	A1
20120036574	Heithcock et al.	Feb 2012	A1
20120039202	Song	Feb 2012	A1
20120059709	Lieberman et al.	Mar 2012	A1
20120079066	Li et al.	Mar 2012	A1
20120083266	Vanswol et al.	Apr 2012	A1
20120089572	Raichstein et al.	Apr 2012	A1
20120094637	Jeyaseelan et al.	Apr 2012	A1
20120101952	Raleigh et al.	Apr 2012	A1
20120110564	Ran et al.	May 2012	A1
20120114112	Rauschenberger et al.	May 2012	A1
20120149404	Beattie et al.	Jun 2012	A1
20120166488	Kaushik et al.	Jun 2012	A1
20120170726	Schwartz	Jul 2012	A1
20120173610	Bleau et al.	Jul 2012	A1
20120174095	Natchadalingam et al.	Jul 2012	A1
20120179646	Hinton et al.	Jul 2012	A1
20120179907	Byrd et al.	Jul 2012	A1
20120180021	Byrd et al.	Jul 2012	A1
20120180029	Hill et al.	Jul 2012	A1
20120185561	Klein et al.	Jul 2012	A1
20120198004	Watte	Aug 2012	A1
20120201238	Lawson	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
20120281536	Gell et al.	Nov 2012	A1
20120288082	Segall	Nov 2012	A1
20120290706	Lin et al.	Nov 2012	A1
20120304245	Lawson et al.	Nov 2012	A1
20120304275	Ji et al.	Nov 2012	A1
20120316809	Egolf et al.	Dec 2012	A1
20120321058	Eng et al.	Dec 2012	A1
20120321070	Smith et al.	Dec 2012	A1
20130029629	Lindholm et al.	Jan 2013	A1
20130031158	Salsburg	Jan 2013	A1
20130031613	Shanabrook et al.	Jan 2013	A1
20130036476	Roever et al.	Feb 2013	A1
20130047232	Tuchman et al.	Feb 2013	A1
20130054517	Beechuk et al.	Feb 2013	A1
20130054684	Brazier et al.	Feb 2013	A1
20130058262	Parreira	Mar 2013	A1
20130067232	Cheung et al.	Mar 2013	A1
20130067448	Sannidhanam et al.	Mar 2013	A1
20130097298	Ting et al.	Apr 2013	A1
20130110658	Lyman	May 2013	A1
20130132573	Lindblom	May 2013	A1
20130139148	Berg et al.	May 2013	A1
20130156024	Burg	Jun 2013	A1
20130166580	Maharajh et al.	Jun 2013	A1
20130179942	Caplis et al.	Jul 2013	A1
20130201909	Bosch et al.	Aug 2013	A1
20130204786	Mattes et al.	Aug 2013	A1
20130212603	Cooke et al.	Aug 2013	A1
20130244632	Spence et al.	Sep 2013	A1
20130268676	Martins et al.	Oct 2013	A1
20130325934	Fausak et al.	Dec 2013	A1
20130328997	Desai	Dec 2013	A1
20130336472	Fahlgren et al.	Dec 2013	A1
20140013400	Warshavsky et al.	Jan 2014	A1
20140025503	Meyer et al.	Jan 2014	A1
20140058806	Guenette et al.	Feb 2014	A1
20140064467	Lawson et al.	Mar 2014	A1
20140072115	Makagon et al.	Mar 2014	A1
20140073291	Hildner et al.	Mar 2014	A1
20140095627	Romagnino	Apr 2014	A1
20140101058	Castel et al.	Apr 2014	A1
20140105372	Nowack et al.	Apr 2014	A1
20140106704	Cooke et al.	Apr 2014	A1
20140122600	Kim et al.	May 2014	A1
20140123187	Reisman	May 2014	A1
20140126715	Lum et al.	May 2014	A1
20140129363	Lorah et al.	May 2014	A1
20140153565	Lawson et al.	Jun 2014	A1
20140185490	Holm et al.	Jul 2014	A1
20140254600	Shibata et al.	Sep 2014	A1
20140258481	Lundell	Sep 2014	A1
20140269333	Boerjesson	Sep 2014	A1
20140274086	Boerjesson et al.	Sep 2014	A1
20140282473	Saraf et al.	Sep 2014	A1
20140289391	Balaji et al.	Sep 2014	A1
20140304054	Orun et al.	Oct 2014	A1
20140317640	Harm et al.	Oct 2014	A1
20140355600	Lawson et al.	Dec 2014	A1
20140372508	Fausak et al.	Dec 2014	A1
20140372509	Fausak et al.	Dec 2014	A1
20140372510	Fausak et al.	Dec 2014	A1
20140373098	Fausak et al.	Dec 2014	A1
20140379670	Kuhr	Dec 2014	A1
20150004932	Kim et al.	Jan 2015	A1
20150004933	Kim et al.	Jan 2015	A1
20150012864	Goodwin 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
20160011758	Dornbush et al.	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
20160142446	Boerjesson et al.	May 2016	A1
20160149956	Birnbaum et al.	May 2016	A1
20160162172	Rathod	Jun 2016	A1
20160205519	Patel et al.	Jul 2016	A1
20160226937	Patel et al.	Aug 2016	A1
20160226979	Lancaster et al.	Aug 2016	A1
20160234391	Wolthuis et al.	Aug 2016	A1
20160239770	Batabyal et al.	Aug 2016	A1
20170339283	Chaudhary et al.	Nov 2017	A1
20180324223	Boerjesson et al.	Nov 2018	A1

Foreign Referenced Citations (20)

Number	Date	Country
1684587	Mar 1971	DE
0282126	Sep 1988	EP
1464418	Oct 2004	EP
1522922	Apr 2005	EP
1770586	Apr 2007	EP
2053869	Apr 2009	EP
2134107	Sep 1999	ES
10294788	Nov 1998	JP
2004166000	Jun 2004	JP
2004220118	Aug 2004	JP
2006319914	Nov 2006	JP
WO-9732448	Sep 1997	WO
WO-2002087804	Nov 2002	WO
WO-2006037492	Apr 2006	WO
WO-2009018489	Feb 2009	WO
WO-2009124223	Oct 2009	WO
WO-2010037064	Apr 2010	WO
WO-2010040010	Apr 2010	WO
WO-2010101935	Sep 2010	WO
WO-2011091085	Jul 2011	WO

Non-Patent Literature Citations (26)

Entry
“Aepona's API Monetization Platform Wins Best of 4G Awards for Mobile Cloud Enabler”, 4G World 2012 Conference & Expo, [Online]. [Accessed Nov. 5, 2015]. Retrieved from the Internet: <URL: https://www.realwire.com/releases/%20Aeponas-API-Monetization>, (Oct. 30, 2012), 4 pgs.
“U.S. Appl. No. 14/208,920, Advisory Action dated Sep. 11, 2015”, 5 pgs.
“U.S. Appl. No. 14/208,920, Examiner Interview Summary dated Jul. 31, 2015”, 3 pgs.
“U.S. Appl. No. 14/208,920, Examiner Interview Summary dated Oct. 14, 2015”, 3 pgs.
“U.S. Appl. No. 14/208,920, Final Office Action dated May 8, 2015”, 22 pgs.
“U.S. Appl. No. 14/208,920, Non Final Office Action dated Sep. 2, 2014”, 17 pgs.
“U.S. Appl. No. 14/208,920, Notice of Allowance dated Oct. 29, 2015”, 8 pgs.
“U.S. Appl. No. 14/208,920, Response filed Jan. 2, 2015 to Non Final Office Action dated Sep. 2, 2014”, 15 pgs.
“U.S. Appl. No. 14/208,920, Response filed Jul. 28, 2015 to Final Office Action dated May 8, 2015”, 14 pgs.
“U.S. Appl. No. 14/208,920, Response filed Oct. 13, 2015 to Advisory Action dated Sep. 11, 2015”, 16 pgs.
“U.S. Appl. No. 15/005,190, Notice of Allowance dated Apr. 17, 2018”, 11 pgs.
“U.S. Appl. No. 16/039,950, Non Final Office Action dated Jun. 24, 2019”, 11 pgs.
“U.S. Appl. No. 16/039,950, Notice of Allowance dated Oct. 3, 2019”, 8 pgs.
“U.S. Appl. No. 16/039,950, Response filed Sep. 19, 2019 to Non-Final Office Action dated Jun. 24, 2019”, 11 pgs.
“Archive Microsoft Office 365 Email \| Retain Unified Archiving”, GWAVA, Inc., Montreal, Canada, [Online] Retrieved from the internet: <http://www.gwava.com/Retain/Retain for_Office_365.php>, (2015), 4 pgs.
“Complaint for Patent Infringement”, Telinit Technologies, LLC v. Twilio Inc 2:12-cv-663, (Oct. 12, 2012), 17 pgs.
“Ethernet to Token ring Bridge”, Black Box Corporation, [Online] Retrieved from the internet: <http://blackboxcanada.com/resource/files/productdetails/17044.pdf>, (Oct. 1999), 2 pgs.
“Twilio Cloud Communications—APIs for Voice, VoIP, and Text Messaging”, Twilio, [Online] Retrieved from the internet: <http://www.twilio.com/docs/api/rest/call-feedback>, (Jun. 24, 2015), 8 pgs.
Abu-Lebdeh, et al., “A 3GPP Evolved Packet Core-Based Architecture for QoS-Enabled Mobile Video Surveillance Applications”, 2012 Third International Conference on the Network of the Future {NOF), (Nov. 21-23, 2012), 1-6.
Barakovic, Sabina, et al., “Survey and Challenges of QoE Management Issues in Wireless Networks”, Hindawi Publishing Corporation, (2012), 1-29.
Berners-Lee, T., “RFC 3986: Uniform Resource Identifier (URI): Generic Syntax”, The Internet Society, [Online]. Retrieved from the Internet: <URL: http://tools.ietf.org/html/rfc3986>, (Jan. 2005), 57 pgs.
Kim, Hwa-Jong, et al., “In-Service Feedback QoE Framework”, 2010 Third International Conference on Communication Theory. Reliability and Quality of Service, (2010), 135-138.
Matos, et al., “Quality of Experience-based Routing in Multi-Service Wireless Mesh Networks”, Realizing Advanced Video Optimized Wireless Networks. IEEE, (2012), 7060-7065.
Mu, Mu, et al., “Quality Evaluation in Peer-to-Peer IPTV Services”, Data Traffic and Monitoring Analysis, LNCS 7754, 302-319, (2013), 18 pgs.
Subramanya, et al., “Digital Signatures”, IEEE Potentials, (Mar./Apr. 2006), 5-8.
Tran, et al., “User to User adaptive routing based on QoE”, ICNS 2011: The Seventh International Conference on Networking and Services, (2011), 170-177.

Related Publications (1)

	Number	Date	Country
	20200120145 A1	Apr 2020	US

Provisional Applications (1)

	Number	Date	Country
	61783134	Mar 2013	US

Continuations (3)

	Number	Date	Country
Parent	16039950	Jul 2018	US
Child	16716342		US
Parent	15005190	Jan 2016	US
Child	16039950		US
Parent	14208920	Mar 2014	US
Child	15005190		US

System and method for integrating session initiation protocol communication in a telecommunications platform

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

Field of Search

CPC

International Classifications

Disclaimer

Abstract