System and method for a media intelligence platform

Information

  • Patent Grant
  • 10467665
  • Patent Number
    10,467,665
  • Date Filed
    Tuesday, September 19, 2017
    2 years ago
  • Date Issued
    Tuesday, November 5, 2019
    4 months ago
  • Inventors
  • Original Assignees
  • Examiners
    • Eskandarnia; Arvin
    Agents
    • Schwegman Lundberg & Woessner, P.A.
Abstract
A multi-tenant media processing platform system and method. At least a first media analysis service of a plurality of media analysis services is activated for at least a portion of an active communication session of an entity in the platform system. The first activated media analysis service performs a first media analysis on media of the active communication session that is collected by the platform system. The first activated media analysis service performs the first media analysis on the collected media while the communication session is active to generate a first media analysis result. During the active communication session, at least one media analysis result is applied.
Description
TECHNICAL FIELD

This invention relates generally to the communication field, and more specifically to a new and useful system and method for a media intelligence platform in the communication field.


BACKGROUND

There have been many changes in recent years in how people communicate. The rise of mobile devices and VoIP advances have led to numerous services and applications providing news ways for people to communicate. Audio and video processing has similarly seen continued development through the years, bringing several advances as new techniques are discovered and developed. However, it can be challenging from a development standpoint (e.g., technical expertise, time, budget, etc.) to build and maintain a communication service or application that uses advanced media processing techniques. Thus, there is a need in the communication field to create a new and useful system and method for a media intelligence 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 an embodiment;



FIG. 2 is a flow diagram representation of a method of an embodiment;



FIGS. 3A and 3B are schematic representations of a system of an embodiment;



FIG. 4 is a block diagram representation of a method of an embodiment;



FIG. 5 is a block diagram representation of a method of an embodiment;



FIG. 6 is a block diagram representation of a method of an embodiment;



FIG. 7 is a block diagram representation of a method of an embodiment;



FIG. 8 is an architecture diagram of a system of an embodiment; and



FIG. 9 is an architecture diagram of an external system.





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 A MEDIA INTELLIGENCE PLATFORM

As shown in FIG. 1, a system 100 for a media intelligence platform of a preferred embodiment includes a multitenant media intelligence platform 101, communication resources 121-123, an API 183, an account configuration system 130, and media processing resources 141-143. The system 100 functions to enable media processing to be offered as a service to outside applications and services (e.g., of the app servers 151 and 152 of FIG. 1). The media processing is preferably used for communication-based applications. The media processing can be offered as a supplemental or complimentary feature to existing communication services (e.g., telephony call flow, call center service, customer-facing communication application, SIP trunking service, etc.). The media processing can alternatively be a stand-alone service, wherein outside communication systems can integrate with the media intelligence platform. The media intelligence platform preferably provides real-time or time-shifted analysis results, which enable communication control logic to utilize information extracted from the media content. The media intelligence platform can additionally or alternatively expose the extracted media intelligence information through communication records available through an API, a browsable user interface, an analytics portal, or any suitable interface.


The system 100 can include various types of media processing resources, which can function to offer a variety of media processing techniques. The media processing techniques may include sentiment and emotion detection, transcription services, language detection, content detection, intent detection, speaker detection, and/or any suitable type of media analysis. The system can similarly be applied to one or more types of media formats.


The media format of a communication can be text, audio, video, multi-media, or any suitable media format. The media can originate in a synchronous session or in an asynchronous message conversation. The media analysis can be performed on all or part of a communication. A communication session is preferably a synchronous media session such as a voice call, a video call, a screen-sharing call, a multi-media call, or any suitable type of media-based call. The portion of a communication can alternatively be one or more asynchronous messages. The messages can be analyzed individually, as a collection, or a time ordered sequence of messages. A message can be a text message, an image, a video, document, or any suitable media message.


The system can additionally include a set of operational services that facilitate operation of the media analysis platform. The operational services preferably include an account system and a metering and logging service.


The account system 130 of the preferred embodiment functions to map requests of the media intelligence platform to an identity within the system. The system is preferably a multitenant platform wherein multiple outside entities can create an account within the platform. An account preferably provides a set of credentials or an alternative authentication mechanism through which requests can be validated. The account system preferably authenticates requests made by an account. In one variation, an account identifier and an authentication token must be included in a request, and these authentication credentials are validated by the account system before the request is fulfilled. An account may be authenticated when making use of a REST API, when receiving signaling communication, during use of a user interface control panel or at any suitable instance.


Various aspects of an account and usage of the platform can be configured through account management interfaces. An account may be managed through an account portal user interface. An account may alternatively be managed through API requests or through any suitable mechanism. Aspects of an account that can be managed include configuring programmatic mechanisms and settings when using the media intelligence. For example, an account manager could set various callback URIs that are triggered during errors or other events in the system. The account manager can further define various parameters that will determine how a communication is routed.


As a related aspect, the system can include a policy engine. The policy engine may be a supplemental component or a sub-component of the account system. Policy can be set per account. Accordingly, different accounts can have different permissions, capabilities, pricing, capacity, performance, or other aspects, which can be set through an account policy. Policy may alternatively be set for a sub-account, for the entire platform, for a geographic region, or for any suitable context. Policy settings may be set by default by the platform but some or all of the policy settings may be driven by an account.


An account can include a defined policy configuration. A policy configuration may set particular limitations for account usage within the platform. The policy can prevent an application of an outside entity incurring usage that is beyond the scope in which the application is meant to be used. For example, a policy configuration may limit the amount of media analyzed or the analysis operations performed.


The account system can additionally include a sub-account mechanism, which functions to enable a user of the platform to partition account usage to enable multitenancy within a product of the account holder. The sub-account mechanism preferably accounts for usage, and more specifically creditable/billable usage to be monitored according to an identifier for a sub-set of usage by an account. For example, an account holder may build an outside application platform that depends on the system. The outside application platform can similarly be multitenant in that multiple users can have individually metered and accounted usage. The inheritable multitenancy property of the platform (i.e., the capability of one account within a multitenant collection of accounts to further subdivide usage the account between subclass of accounts). Can preferably provide the capabilities of a parent account to a subaccount including: billing; programmatic customization, allocation of identifiers or endpoints; and/or other customization. A billing engine can cooperatively facilitate delivering billing statements and collecting payments from the sub-accounts. Additionally, the sub-account mechanism can establish a hierarchy of policy inheritance. A platform preferably contains policies that are applied to account. In one variation, a usage policy is based on the type of account such as free account, basic account, or enterprise-account. A parent account can similarly at least partially define the policies of sub-accounts. In one variation, an account will create sub-account resources.


The metering and logging system of the preferred embodiment functions to create a monitoring system to the media intelligence platform. The metering and logging system operates in coordination with the provided media intelligence platform resources. In one variation, the metering and logging system is integrated within an media processing resource instance running on a machine. In another variation, the metering and logging system can externally monitor the actions of the media processing resources, wherein the actions of a resource may be reported to the metering and logging system in any suitable manner. The metering and logging system functions to create a record of notable activities. The metering can be used in providing programmatic hooks (e.g., callback URI triggering, application execution, and the like), billing/crediting an associated entity (e.g., charging for services or controlling resource access), creation of an audit trail, and/or other suitable functionality. Metering preferably includes recording who (e.g., which account, sub-account, user, etc.) is associated with the use of media micro-service and the quantity of usage.


In one variation, the metering layer of a media processing resource instance will record individual events such as media analysis initialization requests, configuration of the media analysis, size or data volume of analyzed media, changes to an analyzed media session, when a media analysis session ends, and/or any suitable event. The metering layer may additionally measure the amount of data transfer, the time of communication sessions, and/or any suitable usage metric while facilitating a particular communication session. The records are preferably metered and logged in connection to an associated account.


A billing engine may operate independently of the metering and logging system, but may alternatively be integrated. A billing engine preferably calculates amount owed by a particular account/sub-account. The billing engine can additionally facilitate collecting and distributing of funds as appropriate. Such accounting may be used in billing or crediting an entity/account for metered usage, which functions to allow a sustainable media intelligence platform to be operated. In another variation, usage accountability can be used in limiting and balancing usage of a particular entity. As the platform is preferably multitenant, usage is preferably balanced across multiple entities. Rate limiting and action limits may be imposed at various times. Additionally, as use of a communication infrastructure is often accompanied with significant financial cost, fraudulent behavior by accounts or users of an account can be harmful to users of the platform and to the platform itself. Fraud detection can additionally be accounted for during usage of the platform.


The system may additionally include a resource management system which functions to scale and orchestrate the computing resources that support the media intelligence platform. The set of media processing instances are preferably scaled so as to support the usage requirements across a set of accounts. As a multi-tenant platform, the resources are preferably shared across accounts. In other words, a media processing resource instance used for a first account at one time may be used by a second account at a different time. The variability of usage requirements for distinct account users is preferably normalized across a set of accounts within the platform, such that the platform is scaled to support the varying usage demands of various account holders. The resource management system can preferably instantiate more media processing resources or other services, suspend resources, or terminate service instances. In one variation, a usage model is generated for at least a set of active accounts of the platform. For the users that use the platform, or alternatively that use the media intelligence platform above a particular threshold, a model may be generated that predicts their usage over time. In one instance, an account may have a substantially steady state of usage. In another instance, the amount of usage may be a function of time of day, week, month, or year. In another instance, an account may have varying trends that are predicted in real-time based on past metrics and optionally metrics of similar accounts. As one baseline heuristic for usage prediction, the media type or application use case may be used to generate a usage model. For example, an account may select the type of media processing usage and configuration during activation—selecting a media format such as audio, video, screen sharing, and an analysis process such as sentiment and emotion detection, transcription services, language detection, content detection, intent detection, or speaker detection. A predictive model may be generated using any suitable algorithm or heuristic.


The system may additionally include a queuing system which functions to facilitate rate limiting and/or resource management. The queuing system can preferably queue requests of a defined scope. A queuing scope may include queuing across a platform, within a regional segment of the platform, across an account, across a sub-account, across requests of a telephony endpoint, or across any suitable scope. In the variation of queuing with a platform scope, requests from different accounts to use a particular media processing resource may be initially queued until a resource is available. The requests may be queued according to different entity limits and policy. Requests of an account or sub-account may be associated with a dequeuing rate and limit. A dequeuing limit preferably defines a maximum frequency of a particular action with the media intelligence platform. A dequeuing limit preferably defines a hard limit on the number of particular actions within a time window. For example, an account may be limited to no more than a set data bandwidth of media analysis. Additionally or alternatively, the dequeuing of a request may be dependent at least in part on the resource usage and/or predicted impact of the request on the system.


2. METHOD FOR A MEDIA INTELLIGENCE PLATFORM

As shown in FIG. 2, a method 200 for a media intelligence platform of a preferred embodiment can include activating media analysis for at least a portion of a communication S110, collecting media for analysis S120, performing analysis on the media S130, and applying results of the analysis S140. The method functions to enable developers to extract media intelligence in a communication. The method may be applied to enable a developer to control how a communication application or service integrates with provided media analysis tools. The method can additionally be applied to offer various programmatic mechanisms for using the analysis results.


The method can be used within a communication platform that facilitates communications. The media intelligence platform is preferably multitenant, which involves shared use of the platform from multiple and distinct entities. These entities can be managed within the platform as accounts, sub-accounts, endpoints (e.g., phone numbers, short codes, SIP addresses, or other communication addresses), and/or other entity constructs. The method preferably allows for customized treatment of media intelligence on a per entity basis. For example, a first account can use the analytic feature different from a second account. In one variation, the media analysis service can be used in a communication application platform used in defining communication logic during a call or related to a message, such as in the communication platform described in U.S. Pat. No. 8,306,021, issued 6 Nov. 2012, which is hereby incorporated in its entirety by this reference. The method may alternatively be used in combination with a communication service such as a platform that offers a customer facing communication application or any suitable communication based platform. The method can alternatively be used as a media intelligence micro-service. In a micro-service variation, the media intelligence may be the primary and possibly only service of the platform used in a communication. In one variation, negotiating and managing a communication occurs outside of the platform by a third party, and the third party system routes the communication to the platform to utilize the media intelligence capabilities of the micro-service. Routing the communication can include routing the communication through the media intelligence platform (e.g., the media intelligence platform is an intermediary node in the media path). Routing the communication can alternatively include terminating a media leg of a communication if, for example, a third party service streamed a branch of the media stream to the media intelligence platform.


Block S110, which includes activating media analysis for at least a portion of a communication, functions to initiate or trigger use of the media analysis. Media analysis is preferably not a mandatory feature for every entity. As mentioned above, different accounts, sub-accounts, or endpoints can utilize the media intelligence independently. A portion of a communication to receive media analysis can be a full communication session, a section of a communication session. A communication session is preferably a synchronous media session such as a voice call, a video call, a screen-sharing call, a multi-media call, or any suitable type of media-based call. The portion of a communication can alternatively be one or more asynchronous messages. The messages can be analyzed individually, as a collection, or a time ordered sequence of messages.


Activating media analysis can occur through one of various approaches. Activating media analysis may include activating media analysis in accordance with platform configuration, activating media analysis in response to a programmatic event, and/or activating media analysis in any suitable manner.


Activating media analysis in accordance with platform configuration, functions to trigger media analysis automatically. In one variation, media analysis can be pre-configured for communications (e.g., calls or messages). Media analysis can be configured to automatically activate for communications to or from a particular endpoint, communications associated with an account or sub-account, communications made during a particular time window, communications made in association with a particular location, or any suitable communication condition. During a communication, the media intelligence platform checks if the properties of that communication map to a configuration setting that enables media analysis. The media analysis configuration can include properties of the analysis such as type of media analysis and any customized settings. In one variation, an administrator can manage media analysis configuration in a dashboard. In one variation, the method can include providing a configuration dashboard for some segment of communications and a checkbox can be used to set media analysis. There can be multiple checkboxes for different types of media analysis processes. Other suitable user-interfaces may alternatively be used. Such a configuration dashboard may enable an administrator to enable/disable media analysis for communications based on involved endpoints, sub-account, types of communications, or other categories of communications. Such media analysis configuration settings may alternatively be set through an API or any suitable interface.


Activating media analysis in response to a programmatic event, functions to programmatically initiate and/or configure media analysis on demand. Use of programmatic events can enable the media analysis to be customized for individual communications. The programmatic event can include communication application instructions, a REST API call, a SIP message, or any suitable programmatic mechanism. The communication application instructions are preferably processed in directing state and communication flow of the communication such as with the telephony instructions of the communication platform referenced above. The REST API can alternatively be any suitable type of API call. An API call can enable media analysis to be triggered by an outside party with authentication credentials to act on that communication. The API call can provide or reference media to be analyzed. The API call can additionally configure properties of the media analysis. In a preferred embodiment, analysis can be initiated and/or configured from a cloud-based communications API. The cloud-based communications API can be used in combination with any suitable communication platform such as a telephony developers platform, a communication application platform, a call routing platform, a video chat platform, a conference call platform, a call center platform, or any suitable communications platform.


During live media analysis, the programmatic events can similarly be used to pause, change, and/or end media analysis. Media analysis may be enabled for the full duration of a communication but may alternatively be turned on while a communication session is active. Media analysis may additionally be turned during a session. In a variation, where media analysis is performed on provided media data, the receipt of a media analysis request along with the media can act as the analysis trigger.


Block S120, which includes collecting media for analysis, functions to obtain the media for analysis. In a preferred variation, the media intelligence platform is part of a platform that participates in routing of a media path for a communication. In synchronous communications (e.g., voice calls, video calls, multi-media streams, etc.), at least one media intelligence resource is preferably in the media path. In one variation, the platform of media intelligence may provide additional services, such as communication flow control. Such services may be used in combination with the media analysis. In another variation, a media stream may be streamed to and terminated at the media intelligence platform. For example, a third party communication system may stream a communication to the media intelligence platform, wherein the associated communication is handled through the third party communication system.


In the case where a substantially real-time media stream is available, the method can include streaming the media through synchronous analysis resources, which functions to provide substantially real-time analysis. For example, sentiment analysis could provide a real-time analysis of a user's tone along a happiness dimension (e.g., 0 for happy 10 for angry). The real-time analysis may alternatively provide time-shifted analysis, which may be streamed analysis with a fixed or restrained delay. For example, real-time audio transcription could be provided wherein the text may be output with up to a 10 second delay. The amount of delay may be dependent on the type of analysis, the service plan level of an account, and other factors.


In one variation, the media analysis can additionally or alternatively be performed on static media content. For example, the media content can be recorded, buffered, cached, or uploaded to the platform. Media analysis on static media content may be scheduled, queued, or managed in any suitable manner.


The type of media analyzed in the method may include audio, video, messaging (text, image, audio, video, and/or other media), screen-sharing media, multi-media streams, and/or any suitable type of media. Preferably, the media intelligence platform can support a set of media types. The media type and the media analysis options may be dynamically determined. However, the media intelligence platform may support a single type of media. The media can be from phone calls, SIP calls, conference calls, calls with a call center system, individual text or media messages, text or media message conversations, screen sharing applications, media sharing apps, or any suitable media related application or service.


Block S130, which includes performing analysis on media, functions to process the media and generate at least one media analysis result. At least one media analysis process is performed, but multiple media analysis processes can be used. Those processes can be performed independently, but may alternatively be dependent. Additionally, media analysis results of a first process can be used as input in a second media analysis process. For example, a transcript of an audio or video can be processed using text based sentiment analysis. The media intelligence platform can offer one or more types of media analysis processes. The performed media analysis process can have several parameters that can be defined. Media analysis parameters can be customized through the mechanism used to activate media analysis. They may alternatively be set through any programmatic mechanism.


Additionally, the different types of media analysis processes can be updated over time. The method can include deploying a media analysis process change across multiple accounts, which functions to roll out improvements and other advances across multiple accounts. In one instance, an application using the media intelligence platform can benefit from continuous media analysis processing improvements without altering integration with the media intelligence platform.


Some exemplary types of media analysis processes that may be performed by the media intelligence platform can include: sentiment and emotion detection, transcription, language detection, content detection, intent detection, context analysis, speaker detection, various computer vision techniques, various natural language techniques, and/or any suitable media analysis process. Some of the media analysis processes may be restricted to particular media formats. For example, there may be a first set of media analysis processes available for audio and second set of media analysis processes available for video. Different sets of media analysis processes may similarly be defined for text messages, messaging conversations, images, screen sharing media, or other types of media. Any suitable media pre-processing operations or data conditioning processes may be performed. The media analysis processes are preferably automatically applied based on the activating trigger or configuration. Media analysis processing can be performed in a remote location or some or at an endpoint device (e.g., performed by client SDK). Additionally, a portion of media analysis processing can be performed in one location and another portion at a second location. In one variation, previously trained machine learning system could be implemented in an endpoint device and media analyzed locally using the trained machine learning system. For example, an emotion detection neural network trained using millions of media streams in the cloud could be used on an endpoint device. In another variation, the analysis system located on an endpoint device could be trained using data on the device or transiting the device. This local data training variation could be used in detection algorithms. For example, a detection algorithm executed on an endpoint device could train using a facial recognition algorithm using photos in an album of the device.


Sentiment and emotion detection functions to classify different aspects of communication. Sentiment and emotion detection can classify the tone of a communication as conveyed through the communicated content (e.g., what is said) or how the content was communicated (e.g., tone of voice). The sentiment and emotion detection can use natural language processing in extracting sentiment or emotion from content (either conveyed in text or transcribed from audio). The sentiment and emotion detection may use various voice analysis techniques for audio and video. Facial expression recognition techniques can be used in graphical media such as images and video. The sentiment emotion detection may provide overall analysis. For example, the sentiment and emotion detection may classify a call based on a measure of aggression detected throughout the call. The sentiment emotion detection may alternatively generate a time-based analysis of sentiment. For example, the measure of aggression may be a function based on time of a call. In this example, the exact moments when one of the callers was angry could be distinguished from when the callers were calm.


Transcription functions to generate a text based machine-readable transcript of what is communicated. Various techniques in speech detection may be used. Audio and video may be transcribed into a text-based format. Transcription may additionally be used with speaker detection to assign an identity to what was said. As mentioned above, the output of a transcription service may be used in other media analysis processes such as sentiment and emotion detection.


Language detection functions to classify the language spoken during a conversation. The language detection process may tag a communication or segments of a communication with language classifiers.


Content detection processes function to classify topics, objects, and other content of a communication. Content detection may be similar to sentiment and emotion detection. However content detection preferably focuses on identifying, classifying, or providing classification probabilities for content in a communication. In image and video based communications, the content detection could include object detection processes. In text communications or communications with a generated transcript, topics of conversation could be classified. Tagging or classification probability assignments could be generated from content detection. The content detection can similarly be applied as an analysis of overall communication or for particular segments of a communication. Context of a communication can similarly be detected. This may be able to classify the environment of a call. For example, the context detection could identify calls made on the street, in an office, in a house, in a store, and the like.


Intent detection functions to detect an objective of a whole communication or a segment of a communication. In one example, intent detection can be used in interpreting a request of a caller. For example, a user could ask a question and this could be parameterized into result parameterizing the question into a normalized query.


Speaker detection functions to identify who is talking at what point in a communication. In one variation, the speaker detection marks points in time when one or more speakers are communicating. Additionally, person or entity recognition can be performed. For example, facial recognition can be used in image and video communications.


In one variation, the method can include offering customized media processing operations. In a first variation, the method can include receiving a customized media analysis process routine. The customized media analysis process routine can be a script, a configuration document, an application, or any suitable mechanism to define media processing. The customized media analysis process routine can be executed during Block S130. The customized media analysis process routine can be statically set for a class of communications (e.g., communications for an account or subaccount, types of calls, for selected communications, etc.). The customized media analysis process routine may alternatively be retrieved from a set media process URI. The media process URI is preferably retrieved using an application layer protocol. The application layer protocol can be an HTTP-based protocol (e.g., HTTP or HTTPS), SPDY, or any suitable application layer protocol. State information of the communication can be embedded into the application layer protocol request to the media process URI. The media process URI preferably refers to a server resource managed by a third party (e.g., such as a server managed by the account holder). In one variation, third parties may be able to offer specialized or custom media analysis modules that can be enabled for use with the media analysis system for a plurality of users. Such third party media analysis modules can be metered and billed individually. Policy could be configured to set permissions of an account or endpoint to use a specific third party analysis module.


Block S140, which includes applying results of the analysis, functions to provide access to analysis results and/or use the results. In a first variation, applying the results of the analysis includes providing access to analysis information. Access to analysis information can enable the results to be queried, accessed, and/or otherwise inspected using an API. The API is preferably a REST API. In one variation, the media analysis results are attached to communication meta-data. The media analysis results can additionally or alternatively be attached to a set of communications, wherein retrieving communication information additionally returns media analysis meta-data. A web interface could additionally provide a user interface portal that can be used to access media analysis results. The web interface could be a portal enabling search or browsing of media analysis information. Additionally or alternatively, the web interface could generate a set of infographics, graphs, tables, highlighted statistics, and other graphics that highlight analytics across a set of communications.


The method can additionally include indexing communication sessions according to analysis results. Indexing can make the communications searchable using media analysis properties. Additionally, the indexing can enable fuzzy search based on classification probabilities. For example, a search for angry communications may return conversations ordered by highest probability of anger to lower probability of anger.


Different types of media analysis can be applied in different ways. Transcription is preferably indexed for searchability. The transcript can additionally be linked or associated with a communication. Language detection, sentiment, content classification, context, speaker detection, and other properties can be tags associated with a communication or a particular segment of a communication.


In some implementations, the media intelligence platform stores communication records (e.g., call records, messaging records, etc.) of a communication system (e.g., a communication system of the media intelligence platform 101, a communication system of the communication resources 121-123 of FIG. 1, or a communication system external to the platform 101). In some implementations, the media intelligence platform (e.g., 101) provides the stored communication records via at least one of an API, a browsable user interface, an analytics portal, or any suitable interface. In some implementations, the media intelligence platform (e.g., 101) provides an external system (e.g., one of the app servers 151, 152) with the stored communication records via at least one of an API, a browsable user interface, an analytics portal, or any suitable interface, the communication records being communication records of an account of the media intelligence platform (e.g., an account managed by the account system 130) that is associated with the external system. In some implementations, the external system provides an API request (e.g., via the API 183) to receive communication records for an account specified in the API request, and the media intelligence platform provides the communication records for the account to the external system via the API of the platform. In some implementations, the communication records include information for at least one communication session, and information for each communication session includes at least one of: endpoint information for each communication endpoint of the communication session, an account or sub-account associated with the communication session, endpoint device information for at least one communication endpoint of the communication session, a time period of the communication session, at least one location associated with the communication session, and media analysis results associated with the communication session. In some implementations, media analysis results included in communication records includes transcription information for a communication session, language detection information for a communication session, sentiment detection information for a communication session, emotion detection information for a communication session, content classification information for a communication session, context information for a communication session, and speaker detection information for a communication session. In some implementations, media analysis results are stored in the communication records as tags associated with a communication session (or a particular segment of a communication session). In some implementations, transcription information for a communication session (that is included in communication records, e.g., communication records for a platform account) is indexed for searchability.


In some implementations, a request by an external system (e.g., one of the app servers 151, 152) for the stored communication records (e.g., provided via at least one of an API, a browsable user interface, an analytics portal, or any suitable interface) (e.g., communication records of a media intelligence platform account of the external system) specifies media analysis results properties, and the media intelligence platform provides the external system with communication records that match the specified media analysis results properties. In some implementations, the provided communication records for each communication session include media analysis results information that matches the media analysis results properties specified in the request provided by the external system. In some implementations, the platform (e.g., 101) indexes the media analysis results information of the communication records such that the media analysis results information can be queried. As an example, an entity can provide a request for communication records of communication sessions in which results of a sentiment and emotion detection media analysis indicates anger, and communication sessions in the communication records can be ordered by highest probability of anger to lower probability of anger. As an example, an entity can provide a request for communication records of communication sessions in which results of a sentiment and emotion detection media analysis indicates anger and results of a transcription media analysis service indicates that overbilling was discussed, and communication sessions in the communication records can be ordered by highest probability of anger to lower probability of anger.


An implementation of the method preferably results in the media intelligence platform observing performing media analysis on a large volume of media. The media processed is preferably used to train and improve analysis algorithms of the media intelligence platform. Analysis feedback mechanisms such as a feedback API can be used in surveying users and providing qualitative input on media analysis.


Additionally or alternatively, applying results of the analysis can include initiating a programmatic event in response to analysis results. The programmatic event can be triggered or initiated in response to particular conditions based at least in part on the analysis results. Alternatively, the programmatic events could be initiated once a media analysis result is available, which functions to regularly act on the media analysis.


In a first variation, the programmatic event is a selected platform event. A platform event is an action performed within the platform. The action of a platform event can include changes to a communication such as changing the media quality setting, calling an endpoint, sending an email, sending a message, activating another media analysis service, activating recording, or performing any suitable action. As one exemplary application of a platform event, all calls associated with a call center application may be monitored with emotion detection. When anger is detected, the programmatic event may turn on recording for that communication. In another exemplary situation, a customer service system could automatically connect a caller to a manager when a caller is getting too upset.


In a second variation, the programmatic event includes transmitting a message to a configured URI, which functions to trigger a webhook or callback URI. A URI is preferably configured in association with at least one condition based on the media analysis results. When the condition is satisfied, an application layer protocol message is transmitted to the URI. The application layer protocol message preferably includes or embeds data relating to the media analysis results. An account manager may use a callback URI for integrating a system of the account manager with events in the media intelligence platform. As opposed to triggering an internal action in the media intelligence platform, the callback URI can be used to initiate any suitable process executed by an external system. In one exemplary application of a callback URI, a callback URI may be configured and then messaged when a caller is detected to be angry. Preferably the callback URI receives a POST HTTP message with information regarding the communication and/or the media analysis. The server that handles the callback URI can process the communication and media analysis information and take any suitable action.


3. MULTI-TENANT MEDIA PROCESSING PLATFORM SYSTEM


FIG. 3A is a schematic representation of a multi-tenant media processing platform system 300 that includes one or more media analysis services (e.g., 322-323).


In some implementations, the system 300 is similar to a system for providing a micro-services communication platform of U.S. patent application Ser. No. 14/919,650, filed 21 Oct. 2015, which is hereby incorporated in its entirety by this reference. In some implementations, the system 300 is similar to the system 100 of U.S. patent application Ser. No. 14/919,650, filed 21 Oct. 2015, which is hereby incorporated in its entirety by this reference. In some implementations, the system 300 is similar to a system for providing a network discovery service (e.g., STUN/TURN service) platform of U.S. patent application Ser. No. 14/919,650, filed 21 Oct. 2015, which is hereby incorporated in its entirety by this reference. In some implementations, the system 300 is similar to the system 1300 of U.S. patent application Ser. No. 14/919,650, filed 21 Oct. 2015, which is hereby incorporated in its entirety by this reference. In some implementations, the system 300 is similar to a multi-tenant media communication platform system of U.S. patent application Ser. No. 14/919,650, filed 21 Oct. 2015, which is hereby incorporated in its entirety by this reference. In some implementations, the system 300 is similar to the multi-tenant media communication platform system 2400 of U.S. patent application Ser. No. 14/919,650, filed 21 Oct. 2015, which is hereby incorporated in its entirety by this reference.


In the implementation of FIG. 3A, the media analysis services of 322 and 323 are implemented as media analysis micro-services having a respective micro-service API (e.g., 392, 393) and at least one media processing resource (e.g., “Entity A Resources”, “Entity C Resources”, “Entity E Resources”). In some implementations, media analysis services are implemented as media processing resources (e.g., the media processing resources of FIG. 1). In some implementations, media analysis services are implemented as media processing resource instances.


In the embodiment of FIG. 3A, the multi-tenant media processing platform system 300 includes at least one communication service (e.g., 321). In the implementation of FIG. 3A, the communication service 321 is implemented as a communication micro-services having a respective micro-service API (e.g., 391) and at least one media processing resource (e.g., “Entity A Resources”, “Entity B Resources”, “Entity C Resources”, “Entity D Resources”). In some implementations, the communication service is implemented as a communication resource (e.g., the communication resources of FIG. 1). In some implementations, the communication service is implemented as a communication resource instance.


The system 300 is a multi-tenant system that includes plural entities (e.g., entities of the systems 351-355 of FIG. 3A). In some embodiments, entities include one or more of accounts, sub-accounts, organizations, users and service instances. In some implementations, each service instance includes platform configuration of the platform system 300 for an application of an account (or sub-account) of the platform system 300. For example, an account holder of a platform account can have multiple applications that use the platform system 300, each application of the account holder having a separate service instance that includes platform configuration. In some embodiments, each entity is independently configurable, and the system 300 manages configuration for each configured entity. In some embodiments, entity configuration at the system 300 includes configuration for one or more micro-services of the system 300. In some embodiments, entity configuration is received from an external system of a corresponding entity via an account management interface (e.g., an account portal user interface, an account management API, and the like). In some implementations, entity configuration includes configuration similar to entity configuration of U.S. patent application Ser. No. 14/919,650, filed 21 Oct. 2015, which is hereby incorporated in its entirety by this reference. In some implementations, entity configuration includes configuration as described herein for FIGS. 1 and 2. In some implementations, entity configuration includes media analysis configuration, as described herein. In some implementations, entity configuration includes platform configuration, as described herein. In some implementations, entity configuration includes policy configuration, as described herein. In some implementations, entity configuration is stored at the system 300. In some implementations, entity configuration is stored at a remote data storage device that is external to the system 300.


In some embodiments, the system 300 generates one or more micro-services resources for a configured entity.


As depicted in FIG. 3A, the media processing platform system 300 includes micro-services 321-323, operational services 399, and a media processing platform API system 383.


Media Processing Platform


In some embodiments, the system 300 is a media processing platform system for multi-tenant peer-to-peer real-time media communication. In some embodiments, the system 300 is a media processing platform system for multi-tenant peer-to-peer asynchronous media communication. In some embodiments, the system 300 is a media processing platform system for multi-tenant peer-to-peer synchronous media communication.


In some embodiments, each media analysis micro-service (e.g., 322, 323) provides at least one media analysis service for a synchronous media stream. In some embodiments, the synchronous media stream is a synchronous media stream between two synchronous media communication endpoints (e.g., media communication endpoints of different endpoint devices). In some embodiments, the two synchronous media communication endpoints communicate via a media communication channel that is established between the two endpoints. In some embodiments, the synchronous media stream is a synchronous media stream that is broadcasted to at least one synchronous media communication endpoint. In some embodiments, a broadcasting media communication endpoint broadcasts the synchronous media stream to each destination media communication endpoint via at least one media communication channel that is established between the broadcasting endpoint and at least one destination endpoint.


The micro-services 322, 323 provide at least one of a sentiment and emotion detection service, a transcription service, a language detection service, a content detection service, an intent detection service, a speaker detection service, a context analysis service, a computer vision service, and a natural language processing service, as described above for FIGS. 1 and 2.


In some implementations, the system 300 includes one or more of signaling micro-services (e.g., network discovery services, such as STUN/TURN services) and media micro-services (e.g., a transcoding micro-service, a recording micro-service, a mixing micro-service, a conferencing micro-service, a media intelligence micro-service, a text-to-speech micro-service, a speech detection micro-service, a notification micro-service, a call-progress micro-service, and the like).


In some implementations, signaling micro-services of the platform system 300 are similar to micro-services of a signaling and control system of U.S. patent application Ser. No. 14/919,650, filed 21 Oct. 2015, which is hereby incorporated in its entirety by this reference. In some implementations, signaling micro-services of the platform system 300 are similar to micro-services of the signaling and control system 120 of U.S. patent application Ser. No. 14/919,650, filed 21 Oct. 2015, which is hereby incorporated in its entirety by this reference.


In some implementations, signaling micro-services of the platform system 300 are similar to a STUN/TURN micro-service (STMS) of U.S. patent application Ser. No. 14/919,650, filed 21 Oct. 2015, which is hereby incorporated in its entirety by this reference. In some implementations, signaling micro-services of the platform system 300 are similar to the STUN/TURN micro-services (STMS) of FIG. 13 of U.S. patent application Ser. No. 14/919,650, filed 21 Oct. 2015, which is hereby incorporated in its entirety by this reference.


In some implementations, media analysis services of the platform system 300 are similar to media micro-services of a media service system of U.S. patent application Ser. No. 14/919,650, filed 21 Oct. 2015, which is hereby incorporated in its entirety by this reference. In some implementations, media analysis services of the platform system 300 are similar to media micro-services of the media service system 110 of U.S. patent application Ser. No. 14/919,650, filed 21 Oct. 2015, which is hereby incorporated in its entirety by this reference. In some implementations, media analysis services of the platform system 300 are similar to the media micro-services 1381 and 1382 of U.S. patent application Ser. No. 14/919,650, filed 21 Oct. 2015, which is hereby incorporated in its entirety by this reference.


In some embodiments, the operational services 399 include a resource management system 390, a Micro-Service (MS) interface 380, an account system 330, a policy engine 331, a metering and logging system 340, a fraud detection system 370, a billing engine 350, and an Event Trigger System 384, as depicted in FIG. 3B.


In some implementations, the account system 330 is similar to the account system described herein for FIG. 1. In some implementations, the metering and logging system 340 is similar to the metering and logging system described herein for FIG. 1. In some implementations, the policy engine 331 is similar to the policy engine described herein for FIG. 1. In some implementations, the billing engine 350 is similar to the billing engine described herein for FIG. 1. In some implementations, the resource management system 390 is similar to the resource management system described herein for FIG. 1.


In some implementations, the system 300 includes a queuing system similar to the queuing system described herein for FIG. 1


In some implementations, the resource management system 390, the MS interface 380, the account system 330, the policy engine 331, the metering and logging system 340, the fraud detection system 370, the billing engine 350, the communication platform API system 383, and the Event Trigger System 384 are similar to a resource management system, a MS interface, an account system, a policy engine, a metering and logging system, a fraud detection system, a billing engine, an API service, and an Event Trigger System (respectively) of U.S. patent application Ser. No. 14/919,650, filed 21 Oct. 2015, which is hereby incorporated in its entirety by this reference.


In some implementations, the resource management system 390, the MS interface 380, the account system 330, the policy engine 331, the metering and logging system 340, the fraud detection system 370, the billing engine 350, the communication platform API system 383, and the Event Trigger System 384 are similar to the resource management system 1390, the MS interface 1380, the account system 1330, the policy engine 1331, the metering and logging system 1340, the fraud detection system 1370, the billing engine 1350, the API service 1383, and the Event Trigger System 1384 (respectively) of FIG. 13 of U.S. patent application Ser. No. 14/919,650, filed 21 Oct. 2015, which is hereby incorporated in its entirety by this reference. In some implementations, the system 300 includes a queuing system similar to the queuing system 1360 of FIG. 13 of U.S. patent application Ser. No. 14/919,650, filed 21 Oct. 2015, which is hereby incorporated in its entirety by this reference.


In some implementations, one or more of the micro-services 321-323, are accessible by a system (e.g., Entity A system 351, Entity B system 352, Entity C system 353, Entity D system 354, and Entity E system 355) that is external to the system 300 and that is a system of an entity of the system 300. In some implementations, one or more of the micro-services 321-323, are accessible by an external system of an entity via the API system 383. In some implementations, one or more of the micro-services 321-323, are accessible by an external system of an entity via a micro-service API of the respective micro-service (e.g., micro-service A API 391, micro-service B API 392, micro-service C API 393). In some implementations, an external system of an entity accesses one or more of the micro-services 321-323 by providing at least one signaling request to the system 300 (e.g., via a signaling interface of the system 300, a queuing system, and the like).


In some implementations, one or more of the micro-services 321-323 are accessible by another micro-service of the system 300. In some implementations, one or more of the micro-services 321-323 are accessible by another micro-service of the system 300 via the MS interface 380. In some implementations, one or more of the micro-services 321-323 are accessible by another micro-service of the system 300 via the API service 383. In some implementations, one or more of the micro-services 321-323 are accessible by another micro-service of the system 300 via a respective micro service API (e.g., one of the APIs 391-393). In some implementations, one or more of the micro-services 321-323 are accessible by another micro-service of the system 300 via a signaling request.


In some implementations, one or more of the micro-services 321-323 include RESTful API resources (e.g., Entity A Resources, Entity B Resources, Entity C Resources, Entity D Resources, and Entity E Resources as depicted in FIG. 3A), which act as endpoints that can act as a mechanism for specifying requested information or requesting particular actions. In some implementations, the resources are expressed as URI's or resource paths. In some implementations, the RESTful API resources are responsive to different types of HTTP methods such as GET, Put, POST and/or DELETE. In some implementations, each micro service API (e.g., one of the APIs 391-393) is a RESTful API.


In some implementations, one or more of the micro-services 321-323 include a process manager, an authentication layer, and a metering layer similar to the process managers, the authentication layers, and the metering layers of U.S. patent application Ser. No. 14/919,650, filed 21 Oct. 2015, which is hereby incorporated in its entirety by this reference. In some implementations, one or more of the micro-services 321-323 include a process manager, an authentication layer, and a metering layer similar to the process managers, the authentication layers, and the metering layers (e.g., 1311-1313) of FIG. 13 of U.S. patent application Ser. No. 14/919,650, filed 21 Oct. 2015, which is hereby incorporated in its entirety by this reference.


In some implementations, the platform system 300 includes media analysis service configuration for a plurality of entities (e.g., the entities corresponding to the systems 351-355 of FIG. 3A) configured for use of the platform system (e.g., 300). In some implementations, the media analysis service configuration is managed by operational services of the platform system (e.g., the operational services 399 of FIG. 3A). In some implementations, the media analysis service configuration is managed by an account system of the platform system (e.g., the account system 330 of FIG. 3B). In some implementations, the media analysis service configuration is managed by a policy engine of the platform system (e.g., the policy engine 331 of FIG. 3B). In some implementations, the media analysis service configuration is managed by a respective micro-service of the platform system (e.g., 322-323FIG. 3A).


In some implementations, the platform system 300 includes communication service configuration for a plurality of entities (e.g., the entities corresponding to the systems 351-355 of FIG. 3A) configured for use of the platform system (e.g., 300). In some implementations, the communication service configuration is managed by operational services of the platform system (e.g., the operational services 399 of FIG. 3A). In some implementations, the communication service configuration is managed by an account system of the platform system (e.g., the account system 330 of FIG. 3B). In some implementations, the communication service configuration is managed by a policy engine of the platform system (e.g., the policy engine 331 of FIG. 3B). In some implementations, the communication service configuration is managed by a respective micro-service of the platform system (e.g., 321FIG. 3A).


4. MULTI-TENANT MEDIA PROCESSING PLATFORM METHOD

As shown in FIG. 4, the method 400 is performed at a multi-tenant media processing platform system (e.g., the system 300 of FIG. 3A) that includes a plurality of media analysis services (e.g., implemented as micro-services 322-323 of FIG. 3A).


The method 400 includes: activating at least a first media analysis service (e.g., 322, 323) of the plurality of media analysis services for at least a portion of an active communication session of an entity in the platform system (process S410); the first activated media analysis service performing a first media analysis on media of the active communication session that is collected by the platform system, the first activated media analysis service performing the first media analysis on the collected media while the communication session is active to generate a first media analysis result (process S420); during the active communication session, applying at least one media analysis result (process S430).


In some embodiments, the process S410 is similar to Silo of FIG. 2. In some embodiments, the process S420 is similar to S130 of FIG. 2. In some embodiments, the media of the active communication session is collected as described above for S120 of FIG. 2. In some embodiments, the process S430 is similar to S140 of FIG. 2.


In some embodiments, the platform system 300 activates the first media analysis service responsive to a determination by the platform system 300 that at least one property of media of the active communication session that is collected by the platform system 300 maps to at least one setting of entity platform configuration that enables the first media analysis, the entity platform configuration being platform configuration of the entity (e.g., an entity of one of the systems 351-355) in the platform system.


In some embodiments, the platform system 300 activates the first media analysis service responsive to a communication application instruction. In some embodiments, the communication application instruction is provided by an external system of the entity (e.g., one of the systems 351-355). In some embodiments, the communication application instruction is provided to the communication micro-service 321 by an external system of the entity (e.g., one of the systems 351-355), the communication micro-service 321 executes the communication application instruction, and the platform system 300 activates the first media analysis service responsive to execution of the communication application instruction. In some embodiments, the communication micro-service 321 receives the communication application instruction responsive to an incoming telephony communication request to an communication endpoint that is mapped to an application resource of the external system of the entity, and the communication micro-service receives the communication application instruction responsive to the communication micro-service providing an application layer request to a URI (Uniform Resource Identifier) of the external system. In some embodiments, responsive to the communication micro-service 321 receiving an incoming telephony communication request to a communication endpoint that is mapped to an application resource of an external system (e.g., one of 351-355) of the entity, the communication micro-service receives provides an application layer request to a URI (Uniform Resource Identifier) of the external system (e.g., 351-355) and receives the communication application instruction from the external system in a response to the request, the communication micro-service 321 executes the communication application instruction, and the platform system 300 activates the first media analysis service responsive to execution of the communication application instruction by the communication micro-service 321.


In some embodiments, the platform system 300 activates the first media analysis service responsive to a REST API call. In some embodiments, the REST API call is provided by an external system of the entity. In some embodiments, the platform system 300 activates the first media analysis service responsive to a SIP message. In some embodiments, the SIP message call is provided by an external system of the entity.


In some embodiments, activating at least a first media analysis service (the process S140) includes activating the first media analysis service and a second media analysis service of the plurality of media analysis services for at least a portion of the active communication session of the entity in the platform system.


In some embodiments, the platform system 300 activates the second media analysis service responsive to a determination by the platform system 300 that at least one property of media of the active communication session that is collected by the platform system 300 maps to at least one setting of entity platform configuration that enables the second media analysis, the entity platform configuration being platform configuration of the entity (e.g., an entity of one of the systems 351-355) in the platform system.


In some embodiments, the platform system 300 activates the second media analysis service responsive to a communication application instruction. In some embodiments, the communication application instruction is provided by an external system of the entity (e.g., one of the systems 351-355). In some embodiments, the communication application instruction is provided to the communication micro-service 321 by an external system of the entity (e.g., one of the systems 351-355), the communication micro-service 321 executes the communication application instruction, and the platform system 300 activates the second media analysis service responsive to execution of the communication application instruction. In some embodiments, the communication micro-service 321 receives the communication application instruction responsive to an incoming telephony communication request to an communication endpoint that is mapped to an application resource of the external system of the entity, and the communication micro-service receives the communication application instruction responsive to the communication micro-service providing an application layer request to a URI (Uniform Resource Identifier) of the external system. In some embodiments, responsive to the communication micro-service 321 receiving an incoming telephony communication request to a communication endpoint that is mapped to an application resource of an external system (e.g., one of 351-355) of the entity, the communication micro-service receives provides an application layer request to a URI (Uniform Resource Identifier) of the external system (e.g., 351-355) and receives the communication application instruction from the external system in a response to the request, the communication micro-service 321 executes the communication application instruction, and the platform system 300 activates the second media analysis service responsive to execution of the communication application instruction by the communication micro-service 321.


In some embodiments, the platform system 300 activates the second media analysis service responsive to a REST API call. In some embodiments, the REST API call is provided by an external system of the entity. In some embodiments, the platform system 300 activates the second media analysis service responsive to a SIP message. In some embodiments, the SIP message call is provided by an external system of the entity.


In some embodiments, the platform system 300 activates each media analysis service responsive to at least one of: a determination by the platform system that at least one property of media of the active communication session that is collected by the platform system maps to at least one setting of entity platform configuration that enables media analysis, the entity platform configuration being platform configuration of the entity in the platform system; a communication application instruction; a REST API call; and a SIP message. In some embodiments, the communication application instruction is provided by an external system of the entity (e.g., one of the systems 351-355). In some embodiments, the communication application instruction is provided to the communication micro-service 321 by an external system of the entity (e.g., one of the systems 351-355), the communication micro-service 321 executes the communication application instruction, and the platform system 300 activates a media analysis service responsive to execution of the communication application instruction. In some embodiments, the communication micro-service 321 receives the communication application instruction responsive to an incoming telephony communication request to an communication endpoint that is mapped to an application resource of the external system of the entity, and the communication micro-service receives the communication application instruction responsive to the communication micro-service providing an application layer request to a URI (Uniform Resource Identifier) of the external system. In some embodiments, responsive to the communication micro-service 321 receiving an incoming telephony communication request to a communication endpoint that is mapped to an application resource of an external system (e.g., one of 351-355) of the entity, the communication micro-service receives provides an application layer request to a URI (Uniform Resource Identifier) of the external system (e.g., 351-355) and receives the communication application instruction from the external system in a response to the request, the communication micro-service 321 executes the communication application instruction, and the platform system 300 activates a media analysis service responsive to execution of the communication application instruction by the communication micro-service 321


In some embodiments, the entity platform configuration is provided by at least one external system (e.g., 351-355) via an account management interface (e.g., of the API System 383 of FIG. 3) of the media processing platform system 300, the account management interface including a least one of an account portal user interface and an account management API.


In some embodiments in which the first media analysis service and the second media analysis service are activated, the first media analysis service and the second media analysis service are both active during at least a portion of the active communication session.


In some embodiments, the platform configuration specifies automatic activation of at least one media analysis service for at least one of: a communication of the entity to a particular endpoint; a communication session of the entity from a particular endpoint; a communication session of the entity associated with a particular account; a communication session of the entity made during a particular time window; and a communication session of the entity made in association with a particular location.


In some embodiments, communication application instructions are processed in directing state and communication flow of the communication session.


Performing Media Analysis


In some embodiments, the method 400 includes activating a second media analysis service of the plurality of media analysis services for at least a portion of the active communication session of the entity in the platform system, and the process S420 includes the second activated media analysis service performing a second media analysis on the collected media while the communication session is active to generate a second media analysis result, the second media analysis being different from the first media analysis.


In some embodiments, activating at least a first media analysis service of the plurality of media analysis services for at least a portion of an active communication session of an entity in the platform system (process S410) includes: the platform system 300 selecting at least the first media analysis service from the plurality of media analysis services of the platform system 300, the plurality of media analysis services including at least one of a sentiment and emotion detection service, a transcription service, a language detection service, a content detection service, an intent detection service, a speaker detection service, a context analysis service, a computer vision service, and a natural language processing service; and the platform system 300 activating each selected media analysis service. In some embodiments, activating at least a first media analysis service of the plurality of media analysis services for at least a portion of an active communication session of an entity in the platform system (process S410) includes: the platform system 300 selecting at least the first media analysis service from the plurality of media analysis services of the platform system 300, the plurality of media analysis services including at least one of a sentiment and emotion detection service, a context analysis service, and a computer vision service; and the platform system 300 activating each selected media analysis service. In some implementations, the platform system 300 selects each selected media analysis service responsive to a programmatic event. In some implementations, the programmatic event is provided by an external system (e.g., 351-355 of FIG. 3) of the entity. In some implementations, the programmatic event includes reception at the platform system 300 of a communication application instruction that initiates the activation. In some implementations, the programmatic event includes reception at the platform system 300 of a REST API call that initiates the activation. In some implementations, the platform system 300 selects each selected media analysis service in accordance with entity platform configuration of the entity.


In some embodiments, activating at least a first media analysis service of the plurality of media analysis services for at least a portion of an active communication session of an entity in the platform system (process S410) includes: activating a sentiment and emotion detection service.


In some embodiments, the first media analysis service collects the media of the active communication session. In some embodiments, the second media analysis service collects the media of the active communication session.


In some embodiments, a REST API call that activates a media analysis service is provided by an outside party with authentication credentials to act on the communication session, the API call providing the media of the communication session to be analyzed and configuration of the media analysis service.


In some embodiments, the process S410 includes activating a second media analysis service of the plurality of media analysis services for at least a portion of the active communication session of the entity in the platform system, and the method 400 includes the second media analysis service performing a second media analysis on the first media analysis result while the communication session is active to generate a second media analysis result, the second media analysis being different from the first media analysis. In some implementations, the first media analysis service transmits an application layer protocol message to a Uniform Resource Identifier (URI) of the second media analysis service, the application layer protocol message providing data relating to the first media analysis result. In some embodiments, a callback URI parameter of the first media analysis service is configured to specify the URI of the second media analysis service.


In some implementations, the media is real-time media, and the first media analysis service performs real-time media analysis on the real-time media. In some implementations, the media is stored media, and the first media analysis service performs asynchronous media analysis on the stored media.


In some implementations in which a second media analysis service is activated, the media is real-time media, and the second media analysis service performs real-time media analysis on the real-time media. In some implementations in which a second media analysis service is activated, the media is stored media, and the second media analysis service performs asynchronous media analysis on the stored media.


In some implementations, the first media analysis service is a sentiment and emotion detection service. In some implementations in which a second media analysis service is activated, the second media analysis service is a sentiment and emotion detection service, and the first media analysis service is a different media analysis service. In some implementations in which a second media analysis service is activated, the first media analysis service is a sentiment and emotion detection service, and the second media analysis service is a different media analysis service.


Collecting Media for Analysis


In some implementations, the media processing platform system 300 collects media of the active communication session by using a communication service of the system 300 (e.g., the communication service provided by the micro-service 321 of FIG. 3). In some implementations, the media processing platform system 300 collects media of the active communication session from an external system, such as, for example, a communication system that is external to the media processing platform system 300, a communication endpoint device (e.g., 356, 357 of FIG. 3), a system of the entity (e.g., one of the systems 351-355 of FIG. 3). In some implementations, a communication endpoint device includes at least one of a mobile phone, computer, tablet, portable computing device, and the like.


In some implementations, the first activated media analysis service (e.g., the media analysis service of the micro-service 322) collects media of the active communication session from a communication service of the system 300 (e.g., the communication service of the micro-service 321 of FIG. 3). In some implementations, the first activated media analysis service (e.g., the media analysis service of the micro-service 322) collects media of the active communication session from another media analysis service of the system 300 (e.g., a media analysis service of the micro-service 323 of FIG. 3). In some implementations, the first activated media analysis service collects media of the active communication session from an external system, such as, for example, a communication system that is external to the media processing platform system 300, a communication endpoint device (e.g., 356, 357 of FIG. 3), a system of the entity (e.g., one of the systems 351-355 of FIG. 3). In some implementations, a communication endpoint device includes at least one of a mobile phone, computer, tablet, portable computing device, and the like.


In some implementations, a second activated media analysis service (e.g., the media analysis service of the micro-service 323) collects media of the active communication session from a communication service of the system 300 (e.g., the communication service of the micro-service 321 of FIG. 3). In some implementations, the second activated media analysis service (e.g., the media analysis service of the micro-service 323) collects media of the active communication session from another media analysis service of the system 300 (e.g., a media analysis service of the micro-service 322 of FIG. 3). In some implementations, the second activated media analysis service collects media of the active communication session from an external system, such as, for example, a communication system that is external to the media processing platform system 300, a communication endpoint device (e.g., 356, 357 of FIG. 3), a system of the entity (e.g., one of the systems 351-355 of FIG. 3). In some implementations, a communication endpoint device includes at least one of a mobile phone, computer, tablet, portable computing device, and the like.


Applying Media Analysis Results


In some embodiments, applying at least one media analysis result includes applying the first media analysis result. In some implementations in which the first media analysis service and the second media analysis service are activated, applying at least one media analysis result includes applying the first media analysis result. In some implementations in which the first media analysis service and the second media analysis service are activated, applying at least one media analysis result includes applying the second media analysis result. In some implementations in which the first media analysis service and the second media analysis service are activated, applying at least one media analysis result includes applying the first media analysis result and the second media analysis result.


Applying Media Analysis Results: Changing the Active Communication Session


In some embodiments, applying the at least one media analysis result (process S430) includes changing the active communication session in response to the first media analysis result.


In some embodiments, applying the at least one media analysis result (process S430) includes transmitting at least one application layer protocol message to at least one callback URI of a communication service of the platform system (e.g., a callback URI of the communication micro-service 321, such as, for example, a callback URI corresponding to the communication micro-service API 391) of the entity, the at least one application layer protocol message providing the at least one media analysis result.


In some embodiments in which the first media analysis service and the second media analysis service are activated, applying the at least one media analysis result (process S430) includes changing the active communication session in response to the first media analysis result and the second media analysis result. In some embodiments in which the first media analysis service and the second media analysis service are activated, applying the at least one media analysis result (process S430) includes changing the active communication session in response to the second media analysis result. In some embodiments in which the first media analysis service and the second media analysis service are activated, applying the at least one media analysis result (process S430) includes changing the active communication session in response to the first media analysis result.


In some implementations, changing the active communication session includes changing media of the communication session.


In some implementations, changing the active communication session includes at least one of: changing a media quality of the active communication session; calling an endpoint, sending an e-mail, sending a message, activating another media analysis service, and activating recording. In some implementations, the communication service (e.g., of 321) changes the active communication session.


Applying Media Analysis Results: Providing Analysis Results Using a Callback URI


In some embodiments, applying the at least one media analysis result (process S430) includes transmitting at least one application layer protocol message to at least one callback URI of an external system (e.g., 351-355) of the entity, the at least one callback URI being specified by entity platform configuration. In some implementations, the at least one application layer protocol message provides the first media analysis result.


In some implementations in which the first media analysis service and the second media analysis service are activated, the at least one application layer protocol message provides the first media analysis result. In some implementations in which the first media analysis service and the second media analysis service are activated, the at least one application layer protocol message provides the second media analysis result. In some implementations in which the first media analysis service and the second media analysis service are activated, the at least one application layer protocol message provides the first media analysis result and the second media analysis result.


In some embodiments, applying the at least one media analysis result (process S430) includes applying the first media analysis result by transmitting at least one application layer protocol message to at least one callback URI of an external system (e.g., 351-355) of the entity, the at least one callback URI being specified by a REST API call that activates the first media analysis service, the at least one application layer protocol message providing the first media analysis result.


Applying Media Analysis Results: Providing Access


In some embodiments, applying the at least one media analysis result (process S430) includes: providing access to the at least one media analysis result as described above for S140. In some embodiments, applying the at least one media analysis result (process S430) includes providing access to the at least one media analysis result via a REST API (e.g., the an API of the API system 383). In some embodiments, applying the at least one media analysis result (process S430) includes: providing access to the at least one media analysis result by attaching the at least one media analysis result to communication meta-data (e.g., communication metadata provided by the communication service 321 of FIG. 3). In some embodiments, applying the at least one media analysis result (process S430) includes providing access to the at least one media analysis result via a user interface portal provided by the system 300. In some embodiments, the system 300 indexes communication sessions (e.g., communication sessions of the communication micro-service of 321) according to the at least one media analysis results.


In some implementations, providing access to the at least one media analysis result includes: indexing communication sessions according to analysis results. Indexing can make the communications searchable using media analysis properties. Additionally, the indexing can enable fuzzy search based on classification probabilities. For example, a search for angry communications may return conversations ordered by highest probability of anger to lower probability of anger. Different types of media analysis can be applied in different ways. Transcription is preferably indexed for searchability. The transcript can additionally be linked or associated with a communication. Language detection, sentiment, content classification, context, speaker detection, and other properties can be tags associated with a communication or a particular segment of a communication.


In some implementations, providing access to the at least one media analysis result includes: the platform system 300 providing stored communication records via at least one of an API (e.g., 383 of FIG. 3), a browsable user interface, an analytics portal, or any suitable interface. In some implementations, the platform system 300 stores communication records (e.g., call records, messaging records, etc.) of a communication system (e.g., a communication system of the platform system 300, a communication system of the micro-service 321, a communication system external to the system 300). In some implementations, the system 300 provides an external system (e.g., 351-355) with the stored communication records via at least one of an API, a browsable user interface, an analytics portal, or any suitable interface, the communication records being communication records of an account of the platform system (e.g., an account managed by the account system 330) that is associated with the external system. In some implementations, the external system provides an API request (e.g., via the API 383) to receive communication records for an account specified in the API request, and the platform system provides the communication records for the account to the external system via the API of the platform.


In some implementations, the communication records include information for at least one communication session, and information for each communication session includes at least one of: endpoint information for each communication endpoint of the communication session, an account or sub-account associated with the communication session, endpoint device information (e.g., of a device 356, 357 of FIG. 3) for at least one communication endpoint of the communication session, a time period of the communication session, at least one location associated with the communication session, and media analysis results associated with the communication session. In some implementations, media analysis results included in communication records includes the at least one media analysis result. In some implementations, media analysis results included in communication records includes transcription information for a communication session, language detection information for a communication session, sentiment detection information for a communication session, emotion detection information for a communication session, content classification information for a communication session, context information for a communication session, and speaker detection information for a communication session. In some implementations, media analysis results are stored in the communication records as tags associated with a communication session (or a particular segment of a communication session). In some implementations, transcription information for a communication session (that is included in communication records, e.g., communication records for a platform account) is indexed for searchability.


In some implementations, a request by an external system (e.g., one of the app servers 351-355) for the stored communication records (e.g., provided via at least one of an API, a browsable user interface, an analytics portal, or any suitable interface) (e.g., communication records of a platform system account of the external system) specifies media analysis results properties, and the platform system provides the external system with communication records that match the specified media analysis results properties. In some implementations, the provided communication records for each communication session include media analysis results information that matches the media analysis results properties specified in the request provided by the external system. In some implementations, the platform system (e.g., 300) indexes the media analysis results information of the communication records such that the media analysis results information can be queried. As an example, an entity can provide a request for communication records of communication sessions in which results of a sentiment and emotion detection media analysis indicates anger, and communication sessions in the communication records can be ordered by highest probability of anger to lower probability of anger. As an example, an entity can provide a request for communication records of communication sessions in which results of a sentiment and emotion detection media analysis indicates anger and results of a transcription media analysis service indicates that overbilling was discussed, and communication sessions in the communication records can be ordered by highest probability of anger to lower probability of anger.


Accounting and Billing


In some embodiments, the method 400 includes: accounting for the use of the first activated media analysis service on behalf of the entity (process S440); and generating billing information for the entity based on the accounting for the use of the first activated media analysis service (process S450).


In some embodiments in which the first media analysis service and the second media analysis service are activated, the method 400 includes: accounting for the use of the first activated media analysis service on behalf of the entity (process S440); accounting for the use of the second activated media analysis service on behalf of the entity, the platform system accounting for the use of the second activated media analysis service independently from the accounting for the use of the first activated media analysis service (process S440); and generating billing information for the entity based on the accounting for the use of the first activated media analysis service and the accounting for the use of the second activated media analysis service (process S450).


Additional Embodiments

In some embodiments, the plurality of media analysis services includes at least one of a sentiment and emotion detection service, a transcription service, a language detection service, a content detection service, an intent detection service, a speaker detection service, a context analysis service, a computer vision service, and a natural language processing service.


In some embodiments, the active communication session is a communication session between at least a first communication endpoint device (e.g., 356) and a second communication endpoint device (e.g., 357 of FIG. 3), the first communication endpoint device and the second communication endpoint device each being external to the platform system 300, and each media analysis service (e.g., each service of the media analysis micro-services 322-323) is constructed to perform media analysis on media of the communication session between at least the first communication endpoint device and the second communication endpoint device.


In some embodiments, plurality of media analysis services includes at least one of a sentiment and emotion detection service, a language detection service, an intent detection service, a speaker detection service, a context analysis service, and a computer vision service.


In some embodiments, the active communication session is a peer-to-peer communication session.


In some embodiments, the active communication session is a real-time communication session.


In some embodiments, the media is a real-time media stream.


In some embodiments, at least one REST API call is provided by an external system of the entity.


In some embodiments, the first media analysis service includes a customized media analysis process routine, as described above for block S130.


In some embodiments, the method 400 includes: the system 300 training at least one media analysis service by using the first media analysis result. In some embodiments, the method 400 includes: the system 300 training at least one media analysis service by using the first media analysis result and user feedback provided by an external system (e.g., 351-357) via a feedback API of the system 300 (e.g., a feedback API of the API system 383). In some implementations, the system 300 receives user feedback via the feedback API, the feedback indicating a quality of media analysis provided by the first media analysis service, and the system 300 trains the first media analysis service based on the received feedback. In some implementations, the system maintains a history data that includes media analysis results and corresponding media and user feedback of the first media analysis service, and the system trains the first media analysis service by using the history data.


Method Operation


In some implementations, the process S410 is performed by the API system 383. In some implementations, the process S410 is performed by at least one micro-service (e.g., 321, 322, 323). In some implementations, the process S410 is performed by the API system 383 and at least one micro-service. In some implementations, the process S410 is performed by the API system 383, at least one micro-service, and the operations services 399. In some implementations, the process S410 is performed by the operational services 399. In some implementations, the process S410 is performed by the account system 330. In some implementations, the process S410 is performed by the account system 330 and the policy engine 331. In some implementations, the process S410 is performed by two or more of the account system 330, the policy engine 331, and the MS interface 380.


In some implementations, the process S420 is performed by at least one media analysis micro-service (e.g., 322, 323). In some implementations, the process S420 is performed by the API system 383 and at least one media analysis micro-service. In some implementations, the process S420 is performed by the API system 383, at least one media analysis micro-service, and the operations services 399.


In some implementations, the process S430 is performed by the API system 383. In some implementations, the process S430 is performed by at least one micro-service (e.g., 321, 322, 323). In some implementations, the process S430 is performed by the API system 383 and at least one micro-service. In some implementations, the process S430 is performed by the API system 383, at least one micro-service, and the operations services 399. In some implementations, the process S430 is performed by the operational services 399. In some implementations, the process S430 is performed by the account system 330. In some implementations, the process S430 is performed by the account system 330 and the policy engine 331. In some implementations, the process S430 is performed by two or more of the account system 330, the policy engine 331, and the MS interface 380.


In some implementations, the process S440 is performed by the API system 383. In some implementations, the process S440 is performed by at least one micro-service (e.g., 321, 322, 323). In some implementations, the process S440 is performed by the API system 383 and at least one micro-service. In some implementations, the process S440 is performed by the API system 383, at least one micro-service, and the operations services 399. In some implementations, the process S440 is performed by the operational services 399. In some implementations, the process S440 is performed by the account system 330. In some implementations, the process S440 is performed by the account system 330 and the policy engine 331. In some implementations, the process S440 is performed by two or more of the account system 330, the policy engine 331, and the MS interface 380.


In some implementations, the process S450 is performed by the API system 383. In some implementations, the process S450 is performed by at least one micro-service (e.g., 321, 322, 323). In some implementations, the process S450 is performed by the API system 383 and at least one micro-service. In some implementations, the process S450 is performed by the API system 383, at least one micro-service, and the operations services 399. In some implementations, the process S450 is performed by the operational services 399. In some implementations, the process S450 is performed by the account system 330. In some implementations, the process S450 is performed by the account system 330 and the policy engine 331. In some implementations, the process S450 is performed by two or more of the account system 330, the policy engine 331, and the MS interface 380.


5. MULTI-TENANT MEDIA PROCESSING PLATFORM METHOD 500

As shown in FIG. 5, the method 500 is performed at a multi-tenant media processing platform system (e.g., the system 300 of FIG. 3A) that includes a plurality of media analysis services (e.g., implemented as micro-services 322-323 of FIG. 3A).


The method 500 includes: activating a first media analysis service (e.g., of the micro-services 322, 323 of FIG. 3) of the plurality of media analysis services for at least a portion of an active communication session of an entity (e.g., an entity of one of systems 351-355) in the platform system, the platform system activating the first media analysis service responsive to a REST API call provided by an external system (e.g., 351-355) of the entity (process S510); the first activated media analysis service performing a first media analysis on media of the active communication session that is collected by the first activated media analysis service, while the communication session is active, to generate a first media analysis result (process S520); during the active communication session, applying the first media analysis result by transmitting at least one application layer protocol message to at least one callback URI of an external system (e.g., 351-355) of the entity, the at least one callback URI being specified by the REST API call, the at least one application layer protocol message providing the first media analysis result (process S530); accounting for the use of the first activated media analysis service on behalf of the entity (process S540); generating billing information for the entity based on the accounting for the use of the first activated media analysis service (process S550). Each external system (e.g., 351-355) of the entity is a system of an account holder of a platform account of the multi-tenant media processing platform system, each external system being external to the platform system 300.


Selection of at Least One Media Analysis Service


In some embodiments, activating a first media analysis service of the plurality of media analysis services for at least a portion of an active communication session of an entity in the platform system (the process S510) includes: the platform system 300 selecting at least the first media analysis service from the plurality of media analysis services of the platform system 300, the plurality of media analysis services including at least one of a sentiment and emotion detection service, a transcription service, a language detection service, a content detection service, an intent detection service, a speaker detection service, a context analysis service, a computer vision service, and a natural language processing service; and the platform system 300 activating each selected media analysis service. In some embodiments, activating a first media analysis service of the plurality of media analysis services for at least a portion of an active communication session of an entity in the platform system (the process S510) includes: the platform system 300 selecting at least the first media analysis service from the plurality of media analysis services of the platform system 300, the plurality of media analysis services including at least one of a sentiment and emotion detection service, a context analysis service, and a computer vision service; and the platform system 300 activating each selected media analysis service. In some implementations, the platform system 300 selects each selected media analysis service responsive to a programmatic event. In some implementations, the programmatic event is provided by an external system (e.g., 351-355 of FIG. 3) of the entity. In some implementations, the programmatic event includes reception at the platform system 300 of a communication application instruction that initiates the activation. In some implementations, the programmatic event includes reception at the platform system 300 of a REST API call that initiates the activation. In some implementations, the platform system 300 selects each selected media analysis service in accordance with entity platform configuration of the entity.


In some embodiments, activating at least a first media analysis service of the plurality of media analysis services for at least a portion of an active communication session of an entity in the platform system (process S410) includes: activating a sentiment and emotion detection service.


Activation REST API Call and Callback URI


In some implementations, the first media analysis service is activated for a specified active communication session, such as for example, a pre-established communication session that is active prior to activation of the first media analysis service. In some implementations, the first media analysis service is activated for all active communication sessions of the entity.


In some implementations, the activation REST API call to activate the first media analysis service specifies at least the communication session and at least the first activated media analysis service. In some implementations, the REST API call to activate the first media analysis service specifies at least the communication session, at least the first activated media analysis service, and at least the callback URI for the first media analysis service. In some implementations, the REST API call to activate the first media analysis service specifies at least the communication session, at least the first activated media analysis service, and at least media analysis service configuration for the first media analysis service. In some implementations, the activation REST API call specifies the communication session by using a session ID of a communication session of the communication micro-service (e.g., 321) of the platform 300.


In some implementations, the activation REST API call to activate the first media analysis service includes (or references) the media of the communication session, and specifies at least the first activated media analysis service. In some implementations, the REST API call to activate the first media analysis service includes (or references) the media of the communication session, and specifies at least the first activated media analysis service, and at least the callback URI for the first media analysis service. In some implementations, the REST API call to activate the first media analysis service includes (or references) the media of the communication session, and specifies at least the first activated media analysis service, and at least media analysis service configuration for the first media analysis service.


In some implementations, the callback URI is specified by a callback URI parameter of the media analysis service configuration of the activation REST API call. In some implementations, the callback URI is specified by a callback URI parameter of the media analysis service configuration of the first media analysis micro-service (e.g., 322, 323). In some implementations, the callback URI is specified by a callback URI parameter of the media analysis service configuration of the account system 330.


In some implementations, the callback URI is specified by a callback URI parameter included in entity platform configuration of the entity (e.g., entity platform configuration of the account system 330 of FIG. 3).


In some implementations, the callback URI for the first media analysis service is provided by at least one external system (e.g., 351-355) of the entity via an account management interface (e.g., of the API System 383 of FIG. 3) of the media processing platform system 300, the account management interface including a least one of an account portal user interface and an account management API.


Activation REST API Call and Callback URI: Two Media Analysis Services


In some implementations, the REST API specifies: the first activated media analysis service, a second media analysis service, the callback URI for the first media analysis result, and a callback URI for a second media analysis result generated by the second media analysis service. In some implementations, the REST API specifies the first activated media analysis service, a second media analysis service, and the callback URI, and the specified callback URI is for the first media analysis result and a second media analysis result generated by the second media analysis service.


In some implementations, the REST API specifies: the first activated media analysis service, a second media analysis service, the callback URI for the first media analysis result, and a platform event to be performed based on the second media analysis result generated by the second media analysis service.


In some implantations, the platform event is an action performed within the platform 300. In some implementations, the platform event is an action performed by a communication micro-service (e.g., 321) of the platform 300. In some implementations, action of a platform event can include changes to a communication such as changing the media quality setting, calling an endpoint, sending an email, sending a message, activating another media analysis service, activating recording, or performing any suitable action. In some implementations, an exemplary application of a platform event includes monitoring all calls associated with a call center application with emotion detection. In some implementations, an exemplary application of a platform event includes monitoring all calls associated with a call center application with emotion detection; when anger is detected, the programmatic event turns on recording for that communication. In some implementations, an exemplary application of a platform event includes a customer service system automatically connecting a caller to a manager when a caller is getting too upset.


In some embodiments in which the second media analysis service is activated, the method 500 includes: activating the second media analysis service (e.g., of the micro-services 322, 323 of FIG. 3) of the plurality of media analysis services for at least a portion of an active communication session of an entity (e.g., an entity of one of systems 351-355) in the platform system, the platform system activating the second media analysis service responsive to a REST API call provided by an external system (e.g., 351-355) of the entity.


In some embodiments in which the second media analysis service is activated, the method 500 includes: the second activated media analysis service performing a second media analysis on media of the active communication session that is collected by the second activated media analysis service, while the communication session is active, to generate a second media analysis result.


In some embodiments in which the second media analysis service is activated, the method 500 includes: the second activated media analysis service performing a second media analysis on the first analysis result to generate a second media analysis result.


In some embodiments in which the second media analysis service is activated, the method 500 includes: during the active communication session, applying the second media analysis result by transmitting at least one application layer protocol message to at least one callback URI of an external system (e.g., 351-355) of the entity, the at least one callback URI being specified by the REST API call to activate the second media analysis service, the at least one application layer protocol message providing the second media analysis result.


In some embodiments in which the second media analysis service is activated, the method 500 includes: during the active communication session, applying the second media analysis result by performing a platform event, as described herein for S140 of FIG. 1.


In some embodiments in which the second media analysis service is activated, the method 500 includes: accounting for the use of the second activated media analysis service on behalf of the entity; and generating billing information for the entity based on the accounting for the use of the second activated media analysis service.


In some embodiments in which the second media analysis service is activated, the first media analysis service and the second media analysis service are both active during at least a portion of the active communication session.


In some embodiments in which the second media analysis service is activated, use of the second activated media analysis service is accounted for independently from use of the first activated media analysis service.


In some embodiments in which the second media analysis service is activated, media analysis of the second media analysis service is different from media analysis of the first media analysis service.


In some embodiments in which the second media analysis service is activated, a callback URI parameter of the first media analysis service specifies a URI of the second media analysis service, the first media analysis service transmits an application layer protocol message to the URI of the second media analysis service, the message providing data relating to the first media analysis result, the second media analysis service performing a second media analysis on the first media analysis result while the communication session is active to generate a second media analysis result, the second media analysis result being different from the first media analysis result.


In some implementations, the media is real-time media, and the first media analysis service performs real-time media analysis on the real-time media. In some implementations, the media is stored media, and the first media analysis service performs asynchronous media analysis on the stored media.


In some embodiments in which the second media analysis service is activated, the media is real-time media, and the first media analysis service performs real-time media analysis on the real-time media. In some embodiments in which the second media analysis service is activated, the media is stored media, and the first media analysis service performs asynchronous media analysis on the stored media.


In some embodiments in which the second media analysis service is activated, the media is real-time media, and the second media analysis service performs real-time media analysis on the real-time media. In some embodiments in which the second media analysis service is activated, the media is stored media, and the second media analysis service performs asynchronous media analysis on the stored media.


In some implementations, the first media analysis service is a sentiment and emotion detection service. In some implementations in which a second media analysis service is activated, the second media analysis service is a sentiment and emotion detection service, and the first media analysis service is a different media analysis service. In some implementations in which a second media analysis service is activated, the first media analysis service is a sentiment and emotion detection service, and the second media analysis service is a different media analysis service.


Deactivating Media Analysis


In some embodiments, the method 500 includes: de-activating the first media analysis service (e.g., of the micro-services 322, 323 of FIG. 3) of the plurality of media analysis services for at least a portion of an active communication session of an entity (e.g., an entity of one of systems 351-355) in the platform system, the platform system de-activating the first media analysis service responsive to a de-activation REST API call provided by the external system. In some implementations, the REST API call to de-activate the first media analysis service specifies at least the communication session and at least the first activated media analysis service. In some implementations, the de-activation REST API call specifies the communication session by using a session ID of a communication session of the communication micro-service (e.g., 321) of the platform 300. In some implementations, the REST API call to de-activate the first media analysis service specifies at least the first activated media analysis service. In some implementations, the REST API call to de-activate the first media analysis service specifies at least the first activated media analysis service and a media identifier.


In some implementations, the first media analysis service is de-activated for a specified active communication session. In some implementations, the first media analysis service is de-activated for all active communication sessions of the entity.


Configuring Media Analysis


In some embodiments, the method 500 includes: configuring the first media analysis service (e.g., of the micro-services 322, 323 of FIG. 3) of the plurality of media analysis services for at least a portion of an active communication session of an entity (e.g., an entity of one of systems 351-355) in the platform system, the platform system configuring the first media analysis service responsive to a configuration REST API call provided by the external system. In some implementations, the REST API call to configure the first media analysis service specifies at least the first activated media analysis service, and specifies configuration for at least the first activated media analysis service. In some implementations, the REST API call to configure the first media analysis service specifies the active communication session, specifies at least the first activated media analysis service, and specifies configuration for at least the first activated media analysis service. In some implementations, configuration of the configuration REST API call includes the callback URI of the first media analysis service.


In some implementations, the activation REST API call specifies the communication session by using a session ID of a communication session of the communication micro-service (e.g., 321) of the platform 300.


In some implementations, the REST API call to configure the first media analysis service specifies at least the first activated media analysis service and specifies configuration for at least the first activated media analysis service. In some implementations, the REST API call to configure the first media analysis service specifies at least the first activated media analysis service, and specifies configuration for at least the first activated media analysis service, and a media identifier.


In some implementations, the first media analysis service is configured for a specified active communication session, such as for example, a pre-established communication session that is active prior to configuration of the first media analysis service. In some implementations, the first media analysis service is configured for all active communication sessions of the entity.


Customized Media Analysis


In some embodiments, the activation REST API specifies a customized media analysis service (that includes a customized media analysis process routine) as the first media analysis service, as described above for block S130. In some embodiments, the activation REST API includes program instructions (or a link to program instructions) for the customized media analysis service, and responsive to the activation REST API request, the platform system 300 generates a customized media analysis micro-service (e.g., 322, 323) that provides a media analysis service according to the received program instructions.


In some embodiments, the activation REST API includes program instructions (or a link to program instructions) for the customized media analysis service, and responsive to the activation REST API request, the platform system 300 controls a communication micro-service (e.g., 321) to provide a media analysis service according to the received program instructions.


APIs


In some implementations, the REST API call is an API call of the Platform API System 383. In some implementations, the REST API call is an API call of the first media analysis service (e.g., an API call of one of the media analysis micro-service APIs 392, 393). In some implementations, the REST API call is an API call of a communication service of the platform (e.g., an API call of the communication micro-service API 391).


In some implementations, an activation REST API call is an API call of the Platform API System 383. In some implementations, an activation REST API call is an API call of a respective media analysis service (e.g., an API call of one of the media analysis micro-service APIs 392, 393). In some implementations, an activation REST API call is an API call of a communication service of the platform (e.g., an API call of the communication micro-service API 391).


In some implementations, a de-activation REST API call is an API call of the Platform API System 383. In some implementations, a de-activation REST API call is an API call of a respective media analysis service (e.g., an API call of one of the media analysis micro-service APIs 392, 393). In some implementations, a de-activation REST API call is an API call of a communication service of the platform (e.g., an API call of the communication micro-service API 391).


In some implementations, a configuration REST API call is an API call of the Platform API System 383. In some implementations, a configuration REST API call is an API call of a respective media analysis service (e.g., an API call of one of the media analysis micro-service APIs 392, 393). In some implementations, a configuration REST API call is an API call of a communication service of the platform (e.g., an API call of the communication micro-service API 391).


Stand-Alone Media Analysis


In some implementations, the activation REST API call to activate the first media analysis service includes (or references) the media of the communication session, specifies at least the first activated media analysis service, and the activation REST API call is an API all of the first media analysis service (e.g., an API call of one of the media analysis micro-service APIs 392, 393). For example, as shown in FIG. 3, in an exemplary API call, the “ENTITY E System” 355 provides an activation REST API call to the media analysis micro-service C 323 via the micro-service's API 393, and the activation REST API call provides the media to be analyzed by the media analysis service of the micro-service 323. In such an example, the media can be media of a communication session that is managed by a communication platform (or service) that is external to the platform system 300. In such an example, the micro-service 323 can be implemented as a sentiment and emotion detection media analysis micro-service.


Feedback


In some embodiments, the method 500 includes: the system 300 training at least one media analysis service by using the first media analysis result. In some embodiments, the method 500 includes: the system 300 training at least one media analysis service by using the first media analysis result and user feedback provided by an external system (e.g., 351-357) via a feedback API of the system 300 (e.g., a feedback API of the API system 383). In some implementations, the system 300 receives user feedback via the feedback API, the feedback indicating a quality of media analysis provided by the first media analysis service, and the system 300 trains the first media analysis service based on the received feedback. In some implementations, the system maintains a history data that includes media analysis results and corresponding media and user feedback of the first media analysis service, and the system trains the first media analysis service by using the history data.


Applying Media Analysis Results to a Communication Service


In some embodiments, the method 500 includes: during the active communication session, applying the first media analysis result by transmitting at least one application layer protocol message to at least one callback URI of a communication service of the platform system (e.g., a callback URI of the communication micro-service 321, such as, for example, a callback URI corresponding to the communication micro-service API 391) of the entity, the at least one application layer protocol message providing the first media analysis result.


Applying Media Analysis: Providing Access to Results


In some embodiments, the method 500 includes: providing access to the first media analysis result as described above for S140.


In some implementations, providing access to the first media analysis result includes: indexing communication sessions according to analysis results. Indexing can make the communications searchable using media analysis properties. Additionally, the indexing can enable fuzzy search based on classification probabilities. For example, a search for angry communications may return conversations ordered by highest probability of anger to lower probability of anger. Different types of media analysis can be applied in different ways. Transcription is preferably indexed for searchability. The transcript can additionally be linked or associated with a communication. Language detection, sentiment, content classification, context, speaker detection, and other properties can be tags associated with a communication or a particular segment of a communication.


In some implementations, providing access to the first media analysis result includes: the platform system 300 providing stored communication records via at least one of an API (e.g., 383 of FIG. 3), a browsable user interface, an analytics portal, or any suitable interface. In some implementations, the platform system 300 stores communication records (e.g., call records, messaging records, etc.) of a communication system (e.g., a communication system of the platform system 300, a communication system of the micro-service 321, a communication system external to the system 300). In some implementations, the system 300 provides an external system (e.g., 351-355) with the stored communication records via at least one of an API, a browsable user interface, an analytics portal, or any suitable interface, the communication records being communication records of an account of the platform system (e.g., an account managed by the account system 330) that is associated with the external system. In some implementations, the external system provides an API request (e.g., via the API 383) to receive communication records for an account specified in the API request, and the platform system provides the communication records for the account to the external system via the API of the platform.


In some implementations, the communication records include information for at least one communication session, and information for each communication session includes at least one of: endpoint information for each communication endpoint of the communication session, an account or sub-account associated with the communication session, endpoint device information (e.g., of a device 356, 357 of FIG. 3) for at least one communication endpoint of the communication session, a time period of the communication session, at least one location associated with the communication session, and media analysis results associated with the communication session. In some implementations, media analysis results included in communication records includes the first media analysis result. In some implementations, media analysis results included in communication records includes transcription information for a communication session, language detection information for a communication session, sentiment detection information for a communication session, emotion detection information for a communication session, content classification information for a communication session, context information for a communication session, and speaker detection information for a communication session. In some implementations, media analysis results are stored in the communication records as tags associated with a communication session (or a particular segment of a communication session). In some implementations, transcription information for a communication session (that is included in communication records, e.g., communication records for a platform account) is indexed for searchability.


In some implementations, a request by an external system (e.g., one of the app servers 351-355) for the stored communication records (e.g., provided via at least one of an API, a browsable user interface, an analytics portal, or any suitable interface) (e.g., communication records of a platform system account of the external system) specifies media analysis results properties, and the platform system provides the external system with communication records that match the specified media analysis results properties. In some implementations, the provided communication records for each communication session include media analysis results information that matches the media analysis results properties specified in the request provided by the external system. In some implementations, the platform system (e.g., 300) indexes the media analysis results information of the communication records such that the media analysis results information can be queried. As an example, an entity can provide a request for communication records of communication sessions in which results of a sentiment and emotion detection media analysis indicates anger, and communication sessions in the communication records can be ordered by highest probability of anger to lower probability of anger. As an example, an entity can provide a request for communication records of communication sessions in which results of a sentiment and emotion detection media analysis indicates anger and results of a transcription media analysis service indicates that overbilling was discussed, and communication sessions in the communication records can be ordered by highest probability of anger to lower probability of anger.


Additional Embodiments

In some embodiments, the process S510 is similar to Silo of FIG. 2. In some embodiments, the process S520 is similar to S530 of FIG. 2. In some embodiments, the media of the active communication session is collected as described above for S120 of FIG. 2. In some embodiments, the process S530 is similar to S140 of FIG. 2. In some embodiments, the process S510 is similar to S410 of FIG. 4. In some embodiments, the process S520 is similar to S520 of FIG. 4. In some embodiments, the process S530 is similar to S430 of FIG. 4. In some embodiments, the process S550 is similar to S450 of FIG. 4.


In some embodiments, the first media analysis service is a sentiment and emotion detection service. The active communication session is a communication session between at least a first communication endpoint device (e.g., 356 of FIG. 3) and a second communication endpoint device (e.g., 357 of FIG. 3), the first communication endpoint device and the second communication endpoint device each being external to the platform system (e.g., 300 of FIG. 3). The first media analysis service is constructed to perform media analysis on media of the communication session between at least the first communication endpoint device and the second communication endpoint device. The active communication session is at least one of: a peer-to-peer communication session; and a real-time communication session, and the media is a real-time media stream.


In some embodiments, the platform system activates a second media analysis service of the plurality of media analysis services. The platform system activates the second media analysis service responsive to a REST API call provided by an external system (e.g., 351-355) of the entity. The second activated media analysis service performs a second media analysis to generate a second media analysis result.


In some embodiment, the media is real-time media, and the first media analysis service performs real-time media analysis on the real-time media; and the second activated media analysis service performs real-time media analysis on at least one of the real-time media and the first media analysis result.


In some embodiments, during the active communication session, the platform system (e.g., 300) applies the second media analysis result by transmitting at least one application layer protocol message to a communication service (e.g., of the micro-service 321 of FIG. 3) of the platform system, the at least one application layer protocol message providing the second media analysis result.


In some embodiments, the second media analysis is different from the first media analysis.


In some embodiments, the media is real-time media, and the first media analysis service performs real-time media analysis on the real-time media; and the second activated media analysis service performs asynchronous media analysis on stored media.


In some embodiments, activating the first media analysis service includes: the platform system selecting at least the sentiment and emotion detection service as the first media analysis service from the plurality of media analysis services of the platform system, the plurality of media analysis services including the sentiment and emotion detection service and at least one of a context analysis service, and a computer vision service; and the platform system activating each selected media analysis service.


In some embodiments, the REST API specifies at least the communication session and at least the first activated media analysis service.


In some embodiments, the method 500 includes at least one of: at the multi-tenant media processing platform system, de-activating the first media analysis service responsive to a de-activation REST API call provided by an external system of the entity, the de-activation REST API call specifying the communication session; and at the multi-tenant media processing platform system, configuring the first media analysis service responsive to a configuration REST API call provided by an external system of the entity, the configuration REST API call specifying the communication session.


In some embodiment, the platform system 300 trains at least one media analysis service by using the first media analysis result and user feedback provided by an external system (e.g., 351-355) via a feedback API of the platform system. The platform system receives user feedback via the feedback API, the feedback indicating a quality of media analysis provided by the first media analysis service, and the platform system trains the first media analysis service based on the received feedback.


In some embodiments, the platform system maintains history data that includes media analysis results and corresponding media and user feedback of the first media analysis service, and the platform system trains the first media analysis service by using the history data.


In some embodiments, the REST API specifies program instructions for a customized media analysis service, and responsive to the REST API request, the platform system performs at least one of: generation of a customized media analysis service according to the received program instructions; and control of a communication service of the platform system to provide a media analysis service according to the received program instructions.


Method Operation


In some implementations, the process S510 is performed by the API system 383. In some implementations, the process S510 is performed by at least one micro-service (e.g., 321, 322, 323). In some implementations, the process S510 is performed by the API system 383 and at least one micro-service. In some implementations, the process S510 is performed by the API system 383, at least one micro-service, and the operations services 399. In some implementations, the process S510 is performed by the operational services 399. In some implementations, the process S510 is performed by the account system 330. In some implementations, the process S510 is performed by the account system 330 and the policy engine 331. In some implementations, the process S510 is performed by two or more of the account system 330, the policy engine 331, and the MS interface 380.


In some implementations, the process S520 is performed by at least one media analysis micro-service (e.g., 322, 323). In some implementations, the process S520 is performed by the API system 383 and at least one media analysis micro-service. In some implementations, the process S520 is performed by the API system 383, at least one media analysis micro-service, and the operations services 399.


In some implementations, the process S530 is performed by the API system 383. In some implementations, the process S530 is performed by at least one micro-service (e.g., 321, 322, 323). In some implementations, the process S530 is performed by the API system 383 and at least one micro-service. In some implementations, the process S530 is performed by the API system 383, at least one micro-service, and the operations services 399. In some implementations, the process S530 is performed by the operational services 399. In some implementations, the process S530 is performed by the account system 330. In some implementations, the process S530 is performed by the account system 330 and the policy engine 331. In some implementations, the process S530 is performed by two or more of the account system 330, the policy engine 331, and the MS interface 380.


In some implementations, the process S540 is performed by the API system 383. In some implementations, the process S540 is performed by at least one micro-service (e.g., 321, 322, 323). In some implementations, the process S540 is performed by the API system 383 and at least one micro-service. In some implementations, the process S540 is performed by the API system 383, at least one micro-service, and the operations services 399. In some implementations, the process S540 is performed by the operational services 399. In some implementations, the process S540 is performed by the account system 330. In some implementations, the process S540 is performed by the account system 330 and the policy engine 331. In some implementations, the process S540 is performed by two or more of the account system 330, the policy engine 331, and the MS interface 380.


In some implementations, the process S550 is performed by the API system 383. In some implementations, the process S550 is performed by at least one micro-service (e.g., 321, 322, 323). In some implementations, the process S550 is performed by the API system 383 and at least one micro-service. In some implementations, the process S550 is performed by the API system 383, at least one micro-service, and the operations services 399. In some implementations, the process S550 is performed by the operational services 399. In some implementations, the process S550 is performed by the account system 330. In some implementations, the process S550 is performed by the account system 330 and the policy engine 331. In some implementations, the process S550 is performed by two or more of the account system 330, the policy engine 331, and the MS interface 380.


6. MULTI-TENANT MEDIA PROCESSING PLATFORM METHOD 600

As shown in FIG. 6, the method 600 is performed at a multi-tenant media processing platform system (e.g., the system 300 of FIG. 3A) that includes a plurality of media analysis services (e.g., implemented as micro-services 322-323 of FIG. 3A).


In some embodiments, the method 600 is similar to embodiments of the methods 400 and 500 as described herein.


The method 600 includes: activating a first media analysis service (e.g., of 322 of FIG. 3) and a second media analysis service (e.g., of 323 of FIG. 3) of the plurality of media analysis services for at least a portion of an active communication session (e.g., a communication session of the communication micro-service 321) of an entity (e.g., an entity of one of the systems 351-355) in the platform system 300 (process S610); the first activated media analysis service performing a first media analysis on the collected media while the communication session is active to generate a first media analysis result (process S620); the second activated media analysis service performing a second media analysis on the collected media while the communication session is active to generate a second media analysis result, the second media analysis being different from the first media analysis (process S630); during the active communication session, applying the first media analysis result and the second media analysis result (process S640); accounting for the use of the first activated media analysis service on behalf of the entity (process S650); accounting for the use of the second activated media analysis service on behalf of the entity, the platform system accounting for the use of the second activated media analysis service independently from the accounting for the use of the first activated media analysis service (process S660); generating billing information for the entity based on the accounting for the use of the first activated media analysis service and the accounting for the use of the second activated media analysis service (process S670).


The platform system activates each media analysis service responsive to at least one of: a determination by the platform system 300 that at least one property of media of the active communication session that is collected by the platform system maps to at least one setting of entity platform configuration that enables media analysis, the entity platform configuration being platform configuration of the entity in the platform system 300; a communication application instruction (as described herein); a REST API call (as described herein); and a SIP message (as described herein). In some embodiments, the REST API call is provided by an external system of the entity. In some embodiments, the communication application instruction is provided by an external system of the entity. In some embodiments, the SIP message is provided by an external system of the entity.


The platform system applies the first media analysis result and the second media analysis result by at least one of: changing the active communication session in response to at least one of the first media analysis result and the second media analysis result; and transmitting at least one application layer protocol message to at least one callback URI of an external system (e.g., 351-355) of the entity, the at least one callback URI being specified by the entity platform configuration, the at least one application layer protocol message providing at least one of the first media analysis result and the second media analysis result.


The entity platform configuration is provided by at least one external system (e.g., 351-355) via an account management interface (e.g., of the platform API system 383 of FIG. 3) of the media processing platform system 300, the account management interface including a least one of an account portal user interface and an account management API.


The first media analysis service and the second media analysis service are both active during at least a portion of the active communication session.


In some embodiments, the plurality of media analysis services includes at least one of a sentiment and emotion detection service, a transcription service, a language detection service, a content detection service, an intent detection service, a speaker detection service, a context analysis service, a computer vision service, and a natural language processing service.


In some embodiments, the plurality of media analysis services includes at least one of a sentiment and emotion detection service, a context analysis service, and a computer vision service.


In some embodiments, the plurality of media analysis services includes at least one of a sentiment and emotion detection service.


In some embodiments, the plurality of media analysis services includes at least one of a sentiment and emotion detection service, a language detection service, an intent detection service, a speaker detection service, a context analysis service, and a computer vision service.


In some embodiments, the active communication session is a communication session between at least a first communication endpoint device (e.g., the endpoint device 356 of FIG. 3) and a second communication endpoint device (e.g., the endpoint device 357 of FIG. 3), the first communication endpoint device and the second communication endpoint device each being external to the platform system 300, and each media analysis service is constructed to perform media analysis on media of the communication session between at least the first communication endpoint device and the second communication endpoint device.


In some embodiments, the active communication session is a peer-to-peer communication session.


In some embodiments, the active communication session is a real-time communication session.


In some embodiments, the media is a real-time media stream.


In some embodiments, applying the first media analysis result and the second media analysis result includes transmitting at least one application layer protocol message to at least one callback URI of a communication service of the platform system (e.g., a callback URI of the communication micro-service 321, such as, for example, a callback URI corresponding to the communication micro-service API 391) of the entity, the at least one application layer protocol message providing at least one of the first media analysis result and the second media analysis result.


In some implementations, a media analysis micro-service (e.g., 323, 323) performs at least one of the processes S610-S670. In some implementations, the communication micro-service (e.g., 321) performs at least one of the processes S610-S670. In some implementations, the platform API system 383 performs at least one of the processes S610-S670. In some implementations, the operational services 399 performs at least one of the processes S610-S670.


7. MULTI-TENANT MEDIA PROCESSING PLATFORM METHOD 700

As shown in FIG. 7, the method 700 is performed at a multi-tenant media processing platform system (e.g., the system 300 of FIG. 3A) that includes a plurality of media analysis services (e.g., implemented as micro-services 322-323 of FIG. 3A).


In some embodiments, the method 700 is similar to embodiments of the methods 400 and 500 as described herein.


The method 700 includes: activating at least a first media analysis service (e.g., of the micro-service 322 of FIG. 3) and a second media analysis service (e.g., of the micro-service 323 of FIG. 3) of the plurality of media analysis services for at least a portion of an active communication session of an entity (e.g., of a system 351-355) in the platform system (process S710); the first media analysis service collecting media of the active communication session (process S720); the first media analysis service performing a first media analysis on the collected media while the communication session is active to generate a first media analysis result (process S730); the first media analysis service transmitting an application layer protocol message to a Uniform Resource Identifier (URI) of the second media analysis service, the application layer protocol message providing data relating to the first media analysis result (process S740); the second media analysis service performing a second media analysis on the first media analysis result while the communication session is active to generate a second media analysis result, the second media analysis being different from the first media analysis (process S750); during the active communication session, applying the second media analysis result (process S760). A callback URI parameter of the first media analysis service (e.g., stored as entity platform configuration for the entity) is configured to specify the URI of the second media analysis service. The first media analysis service and the second media analysis service are both active during at least a portion of the active communication session.


In some embodiments, the application layer protocol message is an API call in accordance with an API of a media analysis micro-service (e.g., API 392, 393 of FIG. 3) of the second media analysis service.


In some embodiments, applying the second media analysis result includes transmitting at least one application layer protocol message to at least one callback URI of an external system (e.g., 351-355) of the entity, the at least one callback URI being specified by a REST API call provided by the external system of the entity, the at least one application layer protocol message providing the second media analysis result.


In some embodiments, applying the second media analysis result includes transmitting at least one application layer protocol message to at least one callback URI of a communication service of the platform system (e.g., a callback URI of the communication micro-service 321, such as, for example, a callback URI corresponding to the communication micro-service API 391) of the entity, the at least one application layer protocol message providing the second media analysis result.


In some embodiments, the plurality of media analysis services includes at least one of a sentiment and emotion detection service, a transcription service, a language detection service, a content detection service, an intent detection service, a speaker detection service, a context analysis service, a computer vision service, and a natural language processing service.


In some embodiments, the plurality of media analysis services includes at least one of a sentiment and emotion detection service, a context analysis service, and a computer vision service.


In some embodiments, the plurality of media analysis services includes at least one of a sentiment and emotion detection service.


In some embodiments, the plurality of media analysis services includes at least one of a sentiment and emotion detection service, a language detection service, an intent detection service, a speaker detection service, a context analysis service, and a computer vision service.


In some embodiments, the active communication session is a communication session between at least a first communication endpoint device (e.g., the endpoint device 356 of FIG. 3) and a second communication endpoint device (e.g., the endpoint device 357 of FIG. 3), the first communication endpoint device and the second communication endpoint device each being external to the platform system 300, and the first media analysis service is constructed to perform media analysis on media of the communication session between at least the first communication endpoint device and the second communication endpoint device.


In some embodiments, the active communication session is a peer-to-peer communication session.


In some embodiments, the active communication session is a real-time communication session.


In some embodiments, the media is a real-time media stream.


In some implementations, a media analysis micro-service (e.g., 323, 323) performs at least one of the processes S710-S760. In some implementations, the communication micro-service (e.g., 321) performs at least one of the processes S710-S760. In some implementations, the platform API system 383 performs at least one of the processes S710-S760. In some implementations, the operational services 399 performs at least one of the processes S710-S760.


8. SYSTEM ARCHITECTURE: PLATFORM SYSTEM 300


FIG. 8 is an architecture diagram of a system (e.g., the platform system 300 of FIG. 3A) according to an implementation in which the system is implemented by a server device. In some implementations, the system is implemented by a plurality of devices. In some implementations, the system 300 is similar to the system 100 of FIG. 1.


The bus 801 interfaces with the processors 801A-801N, the main memory (e.g., a random access memory (RAM)) 822, a read only memory (ROM) 804, a processor-readable storage medium 805, and a network device 811. In some implementations, the system 300 includes at least one of a display device and a user input device.


The processors 801A-801N may take many forms, such as ARM processors, X86 processors, and the like.


In some implementations, the system (e.g., 300) includes at least one of a central processing unit (processor) and a multi-processor unit (MPU).


The processors 801A-801N and the main memory 822 form a processing unit 899. In some embodiments, the processing unit includes one or more processors communicatively coupled to one or more of a RAM, ROM, and machine-readable storage medium; the one or more processors of the processing unit receive instructions stored by the one or more of a RAM, ROM, and machine-readable storage medium via a bus; and the one or more processors execute the received instructions. In some embodiments, the processing unit is an ASIC (Application-Specific Integrated Circuit). In some embodiments, the processing unit is a SoC (System-on-Chip). In some embodiments, the processing unit includes one or more of the operational services, the platform API system, and one or more micro-services.


The network adapter device 811 provides one or more wired or wireless interfaces for exchanging data and commands between the system (e.g., 300) and other devices, such as an external system (e.g., 351-355). Such wired and wireless interfaces include, for example, a universal serial bus (USB) interface, Bluetooth interface, Wi-Fi interface, Ethernet interface, near field communication (NFC) interface, and the like.


Machine-executable instructions in software programs (such as an operating system, application programs, and device drivers) are loaded into the memory 822 (of the processing unit 899) from the processor-readable storage medium 805, the ROM 804 or any other storage location. During execution of these software programs, the respective machine-executable instructions are accessed by at least one of processors 801A-801N (of the processing unit 899) via the bus 801, and then executed by at least one of processors 801A-801N. Data used by the software programs are also stored in the memory 822, and such data is accessed by at least one of processors 801A-801N during execution of the machine-executable instructions of the software programs. The processor-readable storage medium 805 is one of (or a combination of two or more of) a hard drive, a flash drive, a DVD, a CD, an optical disk, a floppy disk, a flash storage, a solid state drive, a ROM, an EEPROM, an electronic circuit, a semiconductor memory device, and the like. The processor-readable storage medium 805 includes machine-executable instructions (and related data) for an operating system 812, software programs 813, device drivers 814, and the communication platform 820 of the system 300. The machine-executable instructions (and related data) for the communication platform 820 include machine-executable instructions (and related data) for the operational services 399, the platform API System 383, and the micro-services 321-323.


9. SYSTEM ARCHITECTURE: EXTERNAL SYSTEM


FIG. 9 is an architecture diagram of an external system (e.g., an entity external system, such as, for example, one of the entity systems 351-353 of FIG. 3A) according to an implementation in which the external system is implemented by a server device. In some implementations, the external system is implemented by a plurality of devices.


The bus 901 interfaces with the processors 901A-901N, the main memory (e.g., a random access memory (RAM)) 922, a read only memory (ROM) 904, a processor-readable storage medium 905, and a network device 911. In some implementations, the external system includes a display device and a user input device.


The processors 901A-901N may take many forms, such as ARM processors, X86 processors, and the like.


In some implementations, the server device includes at least one of a central processing unit (processor) and a multi-processor unit (MPU).


The processors 901A-901N and the main memory 922 form a processing unit 999. In some embodiments, the processing unit includes one or more processors communicatively coupled to one or more of a RAM, ROM, and machine-readable storage medium; the one or more processors of the processing unit receive instructions stored by the one or more of a RAM, ROM, and machine-readable storage medium via a bus; and the one or more processors execute the received instructions. In some embodiments, the processing unit is an ASIC (Application-Specific Integrated Circuit). In some embodiments, the processing unit is a SoC (System-on-Chip).


The network adapter device 911 provides one or more wired or wireless interfaces for exchanging data and commands between the external system and other devices, such as the system 300 of FIG. 3A. Such wired and wireless interfaces include, for example, a universal serial bus (USB) interface, Bluetooth interface, Wi-Fi interface, Ethernet interface, near field communication (NFC) interface, and the like.


Machine-executable instructions in software programs (such as an operating system, application programs, and device drivers) are loaded into the memory 922 (of the processing unit 999) from the processor-readable storage medium 905, the ROM 904 or any other storage location. During execution of these software programs, the respective machine-executable instructions are accessed by at least one of processors 901A-901N (of the processing unit 999) via the bus 901, and then executed by at least one of processors 901A-901N. Data used by the software programs are also stored in the memory 922, and such data is accessed by at least one of processors 901A-901N during execution of the machine-executable instructions of the software programs. The processor-readable storage medium 905 is one of (or a combination of two or more of) a hard drive, a flash drive, a DVD, a CD, an optical disk, a floppy disk, a flash storage, a solid state drive, a ROM, an EEPROM, an electronic circuit, a semiconductor memory device, and the like. The processor-readable storage medium 905 includes machine-executable instructions (and related data) for an operating system 912, software programs 913, device drivers 914, and data 920.


10. MACHINES

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


11. CONCLUSION

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: collecting, by a multi-tenant media processing platform system, media transmitted as part of an active asynchronous message conversation facilitated by the multi-tenant media processing platform system, the active asynchronous message conversation being associated with a first account of the multi-tenant media processing platform system;determining, based on the media transmitted as part of the active asynchronous message conversation, that a first configuration setting has been satisfied, the first configuration setting being included in a set of configuration settings associated with the first account of the multi-tenant media processing platform system and the first configuration setting corresponding to a first media analysis service of a plurality of media analysis services provided by the multi-tenant media processing platform system;in response to determining that the first configuration setting has been satisfied, using the first media analysis service to perform a first media analysis on the media while the active asynchronous message conversation is active, yielding a first media analysis result; andduring the active asynchronous message conversation, initiating a programmatic event based on the first media analysis result.
  • 2. The method of claim 1, wherein the active asynchronous message conversation is a time ordered sequence of messages.
  • 3. The method of claim 1, wherein the first media analysis service is a sentiment and emotion detection service.
  • 4. The method of claim 1, wherein the first media analysis service is an intent detection service.
  • 5. The method of claim 1, further comprising: after determining that the first configuration setting has been satisfied, determining that a second configuration setting included in the set of configuration settings associated with the first account of the multi-tenant media processing platform system has been satisfied, the second configuration setting corresponding to disabling the first media analysis service; andin response to determining that the second configuration setting has been satisfied, de-activating the first media analysis service; andgenerating billing information for the first account of the multi-tenant media processing platform system based on use of the first media analysis service.
  • 6. The method of claim 1, further comprising: training the first media analysis service based on the first media analysis result and user feedback provided by an external system via a feedback Application Programming Interface (API) of the multi-tenant media processing platform system.
  • 7. The method of claim 1, further comprising: receiving, from an external system associated with the first user account, a request for communication records;in response to receiving the request, providing the external system with communication records that match media analysis result properties specified in the request, the provided communication records including information for a plurality of asynchronous message conversations associated with the first user account, the plurality for asynchronous message conversations including the active asynchronous message conversation for which the first media analysis was performed, the information including the first media analysis result.
  • 8. A multi-tenant media processing platform system comprising: one or more computer processors; and one or more computer-readable mediums storing instructions that, when executed by the one or more computer processors, cause the multi-tenant media processing platform system to perform operations comprising:collecting media transmitted as part of an active asynchronous message conversation facilitated by the multi-tenant media processing platform system, the active asynchronous message conversation being associated with a first account of the multi-tenant media processing platform system;determining, based on the media transmitted as part of the active asynchronous message conversation; that a first configuration setting has been satisfied, the first configuration setting being included in a set of configuration settings associated with the first account of the multi-tenant media processing platform system and the first configuration setting corresponding to a first media analysis service of a plurality of media analysis services provided by the multi-tenant media processing platform system;in response to determining that the first configuration setting has been satisfied, using the first media analysis service to perform a first media analysis on the media while the active asynchronous message conversation is active, yielding a first media analysis result; andduring the active asynchronous message conversation, initiating a programmatic event based on the first media analysis result.
  • 9. The multi-tenant media processing platform system of claim 8, wherein the active asynchronous message conversation is a time ordered sequence of messages.
  • 10. The multi-tenant media processing platform system of claim 8, wherein the first media analysis service is a sentiment and emotion detection service.
  • 11. The multi-tenant media processing platform system of claim 8, wherein the first media analysis service is an intent detection service.
  • 12. The multi-tenant media processing platform system of claim 8, the operations further comprising: after determining that the first configuration setting has been satisfied, determining that a second configuration setting included in the set of configuration settings associated with the first account of the multi-tenant media processing platform system has been satisfied, the second configuration setting corresponding to disabling the first media analysis service; andin response to determining that the second configuration setting has been satisfied, de-activating the first media analysis service; andgenerating billing information for the first account of the multi-tenant media processing platform system based on use of the first media analysis service.
  • 13. The multi-tenant media processing platform system of claim 8, the operations further comprising: training the first media analysis service based on the first media analysis result and user feedback provided by an external system via a feedback Application Programming Interface (API) of the multi-tenant media processing platform system.
  • 14. The multi-tenant media processing platform system of claim 8, the operations further comprising: receiving, from an external system associated with the first user account, a request for communication records;in response to receiving the request, providing the external system with communication records that match media analysis result properties specified in the request, the provided communication records including information for a plurality of asynchronous message conversations associated with the first user account, the plurality for asynchronous message conversations including the active asynchronous message conversation for which the first media analysis was performed, the information including the first media analysis result.
  • 15. A non-transitory computer-readable medium storing instructions that, when executed by one or more computer processors of a multi-tenant media processing platform system, cause the multi-tenant media processing platform system to perform operations comprising: collecting media transmitted as part of an active asynchronous message conversation facilitated by the multi-tenant media processing platform system, the active asynchronous message conversation being associated with a first account of the multi-tenant media processing platform system;determining, based on the media transmitted as part of the active asynchronous message conversation, that a first configuration setting has been satisfied, the first configuration setting being included in a set of configuration settings associated with the first account of the multitenant media processing platform system and the first configuration setting corresponding to a first media analysis service of a plurality of media analysis services provided by the multi-tenant media processing platform system;in response to determining that the first configuration setting has been satisfied; using the first media analysis service to perform a first media analysis on the media while the active asynchronous message conversation is active, yielding a first media analysis result; andduring the active asynchronous message conversation, initiating a programmatic event based on the first media analysis result.
  • 16. The non-transitory computer-readable medium of claim 15, wherein the active asynchronous message conversation is a time ordered sequence of messages.
  • 17. The non-transitory computer-readable medium of claim 15, wherein the first media analysis service is a sentiment and emotion detection service.
  • 18. The non-transitory computer-readable medium of claim 15, wherein the first media analysis service is an intent detection service.
  • 19. Non-transitory computer-readable medium of claim 15, the operations further comprising: after determining that the first configuration setting has been satisfied, determining that a second configuration setting included in the set of configuration settings associated with the first account of the multi-tenant media processing platform system has been satisfied, the second configuration setting corresponding to disabling the first media analysis service; andin response to determining that the second configuration setting has been satisfied, de-activating the first media analysis service; andgenerating billing information for the first account of the multi-tenant media processing platform system based on use of the first media analysis service.
  • 20. The non-transitory computer-readable medium of claim 15, the operations further comprising: training the first media analysis service based on the first media analysis result and user feedback provided by an external system via a feedback Application Programming Interface (API) of the multi-tenant media processing platform system.
CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 15/262,220, filed 12 Sep. 2017, which is a continuation of U.S. patent application Ser. No. 15/013,292, filed 2 Feb. 2016 which claims the benefit of U.S. Provisional Application Ser. No. 62/111,399, filed on 3 Feb. 2015, which are all incorporated in their entirety by this reference.

US Referenced Citations (784)
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 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 Aug 2005 B1
6931405 El-Shimi et al. Aug 2005 B2
6937699 Schuster et al. Aug 2005 B1
6940953 Eberle et al. Sep 2005 B1
6941268 Porter et al. Sep 2005 B2
6947417 Laursen et al. Sep 2005 B2
6947988 Saleh Sep 2005 B1
6961330 Cattan et al. Nov 2005 B1
6964012 Zirngibl et al. Nov 2005 B1
6970915 Partovi et al. Nov 2005 B1
6977992 Zirngibl et al. Dec 2005 B2
6981041 Araujo et al. Dec 2005 B2
6985862 Stroem et al. Jan 2006 B2
6999576 Sacra Feb 2006 B2
7003464 Ferrans et al. Feb 2006 B2
7006606 Cohen et al. Feb 2006 B1
7010586 Allavarpu et al. Mar 2006 B1
7020685 Chen et al. Mar 2006 B1
7039165 Saylor et al. May 2006 B1
7058042 Bontempi et al. Jun 2006 B2
7058181 Wright et al. Jun 2006 B2
7062709 Cheung Jun 2006 B2
7065637 Nanja Jun 2006 B1
7076037 Gonen et al. Jul 2006 B1
7076428 Anastasakos et al. Jul 2006 B2
7089310 Ellerman et al. Aug 2006 B1
7099442 Da Palma et al. Aug 2006 B2
7103003 Brueckheimer et al. Sep 2006 B2
7103171 Annadata et al. Sep 2006 B1
7106844 Holland Sep 2006 B1
7111163 Haney Sep 2006 B1
7136932 Schneider Nov 2006 B1
7140004 Kunins et al. Nov 2006 B1
7143039 Stifelman et al. Nov 2006 B1
7197331 Anastasakos et al. Mar 2007 B2
7197461 Eberle et al. Mar 2007 B1
7197462 Takagi et al. Mar 2007 B2
7197544 Wang et al. Mar 2007 B2
D540074 Peters 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 Oct 2009 B1
7613287 Stifelman et al. Nov 2009 B1
7623648 Oppenheim et al. Nov 2009 B1
7630900 Strom Dec 2009 B1
7631310 Henzinger Dec 2009 B1
7644000 Strom Jan 2010 B1
7657433 Chang Feb 2010 B1
7657434 Thompson et al. Feb 2010 B2
7668157 Weintraub et al. Feb 2010 B2
7672275 Yajnik et al. Mar 2010 B2
7672295 Andhare et al. Mar 2010 B1
7675857 Chesson Mar 2010 B1
7676221 Roundtree et al. Mar 2010 B2
7685280 Berry et al. Mar 2010 B2
7685298 Day et al. Mar 2010 B2
7715547 Ibbotson et al. May 2010 B2
7716293 Kasuga et al. May 2010 B2
7742499 Erskine et al. Jun 2010 B1
7779065 Gupta et al. Aug 2010 B2
7809125 Brunson et al. Oct 2010 B2
7809791 Schwartz et al. Oct 2010 B2
7875836 Imura et al. Jan 2011 B2
7882253 Pardo-Castellote et al. Feb 2011 B2
7920866 Bosch et al. Apr 2011 B2
7926099 Chakravarty et al. Apr 2011 B1
7929562 Petrovykh Apr 2011 B2
7936867 Hill et al. May 2011 B1
7949111 Harlow et al. May 2011 B2
7962644 Ezerzer et al. Jun 2011 B1
7979555 Rothstein et al. Jul 2011 B2
7992120 Wang et al. Aug 2011 B1
8023425 Raleigh Sep 2011 B2
8024785 Andress Sep 2011 B2
8045689 Provenzale et al. Oct 2011 B2
8046378 Zhuge et al. Oct 2011 B1
8046823 Begen et al. Oct 2011 B1
8069096 Ballaro et al. Nov 2011 B1
8078483 Hirose et al. Dec 2011 B1
8081744 Sylvain Dec 2011 B2
8081958 Soederstroem et al. Dec 2011 B2
8103725 Gupta et al. Jan 2012 B2
8126128 Hicks, III et al. Feb 2012 B1
8126129 McGuire Feb 2012 B1
8130750 Hester Mar 2012 B2
8130917 Helbling et al. Mar 2012 B2
8139730 Palma et al. Mar 2012 B2
8145212 Lopresti et al. Mar 2012 B2
8149716 Ramanathan et al. Apr 2012 B2
8150918 Edelman et al. Apr 2012 B1
8156213 Deng et al. Apr 2012 B1
8165116 Ku et al. Apr 2012 B2
8166185 Samuel et al. Apr 2012 B2
8169936 Koren et al. May 2012 B2
8175007 Jain et al. May 2012 B2
8185619 Maiocco et al. May 2012 B1
8196133 Kakumani et al. Jun 2012 B2
8204479 Vendrow et al. Jun 2012 B2
8214868 Hamilton et al. Jul 2012 B2
8218457 Malhotra et al. Jul 2012 B2
8233611 Zettner Jul 2012 B1
8238533 Blackwell et al. Aug 2012 B2
8243889 Taylor et al. Aug 2012 B2
8249552 Gailloux et al. Aug 2012 B1
8266327 Kumar et al. Sep 2012 B2
8295272 Boni et al. Oct 2012 B2
8301117 Keast et al. Oct 2012 B2
8306021 Lawson et al. Nov 2012 B2
8315198 Corneille et al. Nov 2012 B2
8315369 Lawson et al. Nov 2012 B2
8315620 Williamson et al. Nov 2012 B1
8319816 Swanson et al. Nov 2012 B1
8326805 Arous et al. Dec 2012 B1
8335852 Hokimoto Dec 2012 B2
8346630 McKeown Jan 2013 B1
8355394 Taylor et al. Jan 2013 B2
8411669 Chen et al. Apr 2013 B2
8413247 Hudis et al. Apr 2013 B2
8417817 Jacobs Apr 2013 B1
8429827 Wetzel Apr 2013 B1
8438315 Tao et al. May 2013 B1
8462670 Chien et al. Jun 2013 B2
8467502 Sureka et al. Jun 2013 B2
8477926 Jasper et al. Jul 2013 B2
8503639 Reding et al. Aug 2013 B2
8503650 Reding et al. Aug 2013 B2
8504818 Rao et al. Aug 2013 B2
8509068 Begall et al. Aug 2013 B2
8532686 Schmidt et al. Sep 2013 B2
8533857 Tuchman et al. Sep 2013 B2
8542805 Agranovsky et al. Sep 2013 B2
8543665 Ansari et al. Sep 2013 B2
8547962 Ramachandran et al. Oct 2013 B2
8549047 Beechuk et al. Oct 2013 B2
8565117 Hilt et al. Oct 2013 B2
8572391 Golan et al. Oct 2013 B2
8576712 Sabat et al. Nov 2013 B2
8577803 Chatterjee et al. Nov 2013 B2
8582450 Robesky Nov 2013 B1
8582737 Lawson et al. Nov 2013 B2
8594626 Woodson et al. Nov 2013 B1
8601136 Fahlgren et al. Dec 2013 B1
8611338 Lawson et al. Dec 2013 B2
8613102 Nath Dec 2013 B2
8621598 Lai et al. Dec 2013 B2
8649268 Lawson et al. Feb 2014 B2
8656452 Li et al. Feb 2014 B2
8667056 Proulx et al. Mar 2014 B1
8675493 Buddhikot et al. Mar 2014 B2
8688147 Nguyen et al. Apr 2014 B2
8695077 Gerhard et al. Apr 2014 B1
8713693 Shanabrook et al. Apr 2014 B2
8728656 Takahashi et al. May 2014 B2
8751801 Harris et al. Jun 2014 B2
8755376 Lawson et al. Jun 2014 B2
8767925 Sureka et al. Jul 2014 B2
8781975 Bennett et al. Jul 2014 B2
8797920 Parreira Aug 2014 B2
8806024 Francis et al. Aug 2014 B1
8819133 Wang Aug 2014 B2
8825746 Ravichandran Sep 2014 B2
8837465 Lawson et al. Sep 2014 B2
8838707 Lawson et al. Sep 2014 B2
8843596 Goel et al. Sep 2014 B2
8855271 Brock Oct 2014 B2
8861510 Fritz Oct 2014 B1
8879547 Maes Nov 2014 B2
8903938 Vermeulen et al. Dec 2014 B2
8918848 Sharma et al. Dec 2014 B2
8924489 Bleau et al. Dec 2014 B2
8938053 Cooke et al. Jan 2015 B2
8948356 Nowack et al. Feb 2015 B2
8954591 Ganesan et al. Feb 2015 B2
8964726 Lawson et al. Feb 2015 B2
8990610 Bostick et al. Mar 2015 B2
9014664 Kim et al. Apr 2015 B2
9015702 Bhat Apr 2015 B2
9031223 Smith et al. May 2015 B2
9032204 Byrd et al. May 2015 B2
9071677 Aggarwal et al. Jun 2015 B2
9137127 Nowack Sep 2015 B2
9141682 Adoc, Jr. et al. Sep 2015 B1
9161296 Parsons et al. Oct 2015 B2
9177007 Winters et al. Nov 2015 B2
9204281 Ramprasad et al. Dec 2015 B2
9210275 Lawson et al. Dec 2015 B2
9306982 Lawson et al. Apr 2016 B2
9307094 Nowack et al. Apr 2016 B2
9325624 Malatack et al. Apr 2016 B2
9338190 Eng et al. May 2016 B2
9344573 Wolthuis May 2016 B2
9356916 Kravitz et al. May 2016 B2
9378337 Kuhr Jun 2016 B2
9398622 Lawson et al. Jul 2016 B2
9456008 Lawson et al. Sep 2016 B2
9456339 Hildner et al. Sep 2016 B1
9460169 Hinton et al. Oct 2016 B2
9477975 Lawson 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
9805399 Lawson Oct 2017 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 Sep 2002 A1
20020136391 Armstrong Sep 2002 A1
20020165957 Devoe et al. Nov 2002 A1
20020176378 Hamilton et al. Nov 2002 A1
20020176404 Girard Nov 2002 A1
20020184361 Eden Dec 2002 A1
20020198941 Gavrilescu et al. Dec 2002 A1
20030006137 Wei et al. Jan 2003 A1
20030012356 Zino et al. Jan 2003 A1
20030014665 Anderson et al. Jan 2003 A1
20030018830 Chen et al. Jan 2003 A1
20030023672 Vaysman Jan 2003 A1
20030026426 Wright Feb 2003 A1
20030046366 Pardikar et al. Mar 2003 A1
20030051037 Sundaram et al. Mar 2003 A1
20030058884 Kallner et al. Mar 2003 A1
20030059020 Meyerson et al. Mar 2003 A1
20030060188 Gidron et al. Mar 2003 A1
20030061317 Brown et al. Mar 2003 A1
20030061404 Atwal Mar 2003 A1
20030088421 Maes et al. May 2003 A1
20030097330 Hillmer et al. May 2003 A1
20030097447 Johnston May 2003 A1
20030097639 Niyogi et al. May 2003 A1
20030103620 Brown et al. Jun 2003 A1
20030123640 Roelle et al. Jul 2003 A1
20030149721 Alfonso-Nogueiro et al. Aug 2003 A1
20030162506 Toshimitsu et al. Aug 2003 A1
20030195950 Huang Oct 2003 A1
20030195990 Greenblat Oct 2003 A1
20030196076 Zabarski et al. Oct 2003 A1
20030204616 Billhartz et al. Oct 2003 A1
20030211842 Kempf et al. Nov 2003 A1
20030231647 Petrovykh Dec 2003 A1
20030233276 Pearlman et al. Dec 2003 A1
20040008635 Nelson et al. Jan 2004 A1
20040011690 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 May 2004 A1
20040102182 Reith et al. May 2004 A1
20040117788 Karaoguz 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 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 Jan 2005 A1
20050005200 Matena et al. Jan 2005 A1
20050010483 Ling Jan 2005 A1
20050015505 Kruis et al. Jan 2005 A1
20050021626 Prajapat et al. Jan 2005 A1
20050025303 Hostetler Feb 2005 A1
20050038772 Colrain Feb 2005 A1
20050043952 Sharma et al. Feb 2005 A1
20050047579 Salame Mar 2005 A1
20050060411 Coulombe et al. Mar 2005 A1
20050083907 Fishler Apr 2005 A1
20050091336 DeHamer et al. Apr 2005 A1
20050091572 Gavrilescu et al. Apr 2005 A1
20050108770 Karaoguz May 2005 A1
20050125251 Berger et al. Jun 2005 A1
20050125739 Thompson 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 Sep 2005 A1
20050228680 Malik Oct 2005 A1
20050238153 Chevalier Oct 2005 A1
20050240659 Taylor Oct 2005 A1
20050243977 Creamer et al. Nov 2005 A1
20050246176 Creamer et al. Nov 2005 A1
20050286496 Malhotra Dec 2005 A1
20050289222 Sahim Dec 2005 A1
20060008065 Longman et al. Jan 2006 A1
20060008073 Yoshizawa et al. Jan 2006 A1
20060008256 Khedouri Jan 2006 A1
20060015467 Morken et al. Jan 2006 A1
20060021004 Moran et al. Jan 2006 A1
20060023676 Whitmore et al. Feb 2006 A1
20060047666 Bedi et al. Mar 2006 A1
20060067506 Flockhart et al. Mar 2006 A1
20060080415 Tu Apr 2006 A1
20060098624 Morgan et al. May 2006 A1
20060129638 Deakin Jun 2006 A1
20060143007 Koh et al. Jun 2006 A1
20060146792 Ramachandran et al. Jul 2006 A1
20060146802 Baldwin et al. Jul 2006 A1
20060168334 Potti et al. Jul 2006 A1
20060203979 Jennings Sep 2006 A1
20060209695 Archer et al. Sep 2006 A1
20060212865 Vincent et al. Sep 2006 A1
20060215824 Mitby et al. Sep 2006 A1
20060217823 Hussey Sep 2006 A1
20060217978 Mitby et al. Sep 2006 A1
20060222166 Ramakrishna et al. Oct 2006 A1
20060235715 Abrams 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 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 May 2007 A1
20070112574 Greene May 2007 A1
20070116191 Bermudez et al. May 2007 A1
20070121651 Casey et al. May 2007 A1
20070127691 Lert Jun 2007 A1
20070127703 Siminoff Jun 2007 A1
20070130260 Weintraub et al. Jun 2007 A1
20070133771 Stifelman et al. Jun 2007 A1
20070147351 Dietrich et al. Jun 2007 A1
20070149166 Turcotte et al. Jun 2007 A1
20070153711 Dykas et al. Jul 2007 A1
20070167170 Fitchett et al. Jul 2007 A1
20070192629 Saito Aug 2007 A1
20070201448 Baird et al. Aug 2007 A1
20070208862 Fox et al. Sep 2007 A1
20070232284 Mason et al. Oct 2007 A1
20070239761 Baio et al. Oct 2007 A1
20070242626 Altberg et al. Oct 2007 A1
20070255828 Paradise Nov 2007 A1
20070265073 Novi et al. Nov 2007 A1
20070286180 Marquette et al. Dec 2007 A1
20070291734 Bhatia et al. Dec 2007 A1
20070291905 Halliday et al. Dec 2007 A1
20070293200 Roundtree et al. Dec 2007 A1
20070295803 Levine et al. Dec 2007 A1
20080005275 Overton et al. Jan 2008 A1
20080025320 Bangalore et al. Jan 2008 A1
20080037715 Prozeniuk et al. Feb 2008 A1
20080037746 Dufrene et al. Feb 2008 A1
20080040484 Yardley Feb 2008 A1
20080049617 Grice et al. Feb 2008 A1
20080052395 Wright et al. Feb 2008 A1
20080091843 Kulkarni Apr 2008 A1
20080101571 Harlow et al. May 2008 A1
20080104348 Kabzinski et al. May 2008 A1
20080120702 Holimoto May 2008 A1
20080123559 Haviv et al. May 2008 A1
20080134049 Gupta et al. Jun 2008 A1
20080139166 Agarwal et al. Jun 2008 A1
20080146268 Gandhi et al. Jun 2008 A1
20080152101 Griggs Jun 2008 A1
20080154601 Stifelman et al. Jun 2008 A1
20080155029 Helbling Jun 2008 A1
20080162482 Ahem et al. Jul 2008 A1
20080165708 Moore et al. Jul 2008 A1
20080172404 Cohen Jul 2008 A1
20080177883 Hanai et al. Jul 2008 A1
20080192736 Jabri et al. Aug 2008 A1
20080201426 Darcie Aug 2008 A1
20080209050 Li Aug 2008 A1
20080212945 Khedouri Sep 2008 A1
20080222656 Lyman Sep 2008 A1
20080229421 Hudis et al. Sep 2008 A1
20080232574 Baluja et al. Sep 2008 A1
20080235230 Maes Sep 2008 A1
20080256224 Kaji et al. Oct 2008 A1
20080275741 Loeffen Nov 2008 A1
20080307436 Hamilton Dec 2008 A1
20080310599 Purnadi et al. Dec 2008 A1
20080313318 Vermeulen Dec 2008 A1
20080316931 Qiu et al. Dec 2008 A1
20080317222 Griggs et al. Dec 2008 A1
20080317232 Couse et al. Dec 2008 A1
20080317233 Rey et al. Dec 2008 A1
20090046838 Andreasson Feb 2009 A1
20090052437 Taylor et al. Feb 2009 A1
20090052641 Taylor et al. Feb 2009 A1
20090059894 Jackson et al. Mar 2009 A1
20090063502 Coimbatore et al. Mar 2009 A1
20090074159 Goldfarb et al. Mar 2009 A1
20090075684 Cheng et al. Mar 2009 A1
20090083155 Tudor et al. Mar 2009 A1
20090089165 Sweeney Apr 2009 A1
20090089352 Davis et al. Apr 2009 A1
20090089699 Saha et al. Apr 2009 A1
20090092674 Schwartz et al. Apr 2009 A1
20090093250 Jackson et al. Apr 2009 A1
20090094674 Schwartz et al. Apr 2009 A1
20090125608 Werth et al. May 2009 A1
20090129573 Gavan et al. May 2009 A1
20090136011 Goel May 2009 A1
20090170496 Bourque Jul 2009 A1
20090171659 Pearce et al. Jul 2009 A1
20090171669 Engelsma et al. Jul 2009 A1
20090171752 Galvin et al. Jul 2009 A1
20090182896 Patterson et al. Jul 2009 A1
20090193433 Maes Jul 2009 A1
20090216835 Jain et al. Aug 2009 A1
20090217293 Wolber et al. Aug 2009 A1
20090220057 Waters Sep 2009 A1
20090221310 Chen et al. Sep 2009 A1
20090222341 Belwadi et al. Sep 2009 A1
20090225748 Taylor Sep 2009 A1
20090225763 Forsberg et al. Sep 2009 A1
20090228868 Drukman et al. Sep 2009 A1
20090232289 Drucker et al. Sep 2009 A1
20090234965 Viveganandhan et al. Sep 2009 A1
20090235349 Lai et al. Sep 2009 A1
20090241135 Wong et al. Sep 2009 A1
20090252159 Lawson et al. Oct 2009 A1
20090262725 Chen Oct 2009 A1
20090276771 Nickolov et al. Nov 2009 A1
20090288012 Udo et al. Nov 2009 A1
20090288165 Qiu et al. Nov 2009 A1
20090300194 Ogasawara Dec 2009 A1
20090316687 Kruppa Dec 2009 A1
20090318112 Vasten Dec 2009 A1
20100027531 Kurashima Feb 2010 A1
20100037204 Lin et al. Feb 2010 A1
20100054142 Moiso et al. Mar 2010 A1
20100070424 Monk Mar 2010 A1
20100071053 Ansari et al. Mar 2010 A1
20100082513 Liu Apr 2010 A1
20100087215 Gu et al. Apr 2010 A1
20100088187 Courtney et al. Apr 2010 A1
20100088698 Krishnamurthy Apr 2010 A1
20100094758 Chamberlain et al. Apr 2010 A1
20100103845 Ulupinar et al. Apr 2010 A1
20100107222 Glasser Apr 2010 A1
20100115041 Hawkins et al. May 2010 A1
20100138501 Clinton et al. Jun 2010 A1
20100142516 Lawson et al. Jun 2010 A1
20100150139 Lawson Jun 2010 A1
20100167689 Sepehri-Nik et al. Jul 2010 A1
20100188979 Thubert et al. Jul 2010 A1
20100191915 Spencer Jul 2010 A1
20100208881 Kawamura Aug 2010 A1
20100217837 Ansari Aug 2010 A1
20100217982 Brown et al. Aug 2010 A1
20100232594 Lawson Sep 2010 A1
20100235539 Carter et al. Sep 2010 A1
20100250946 Korte et al. Sep 2010 A1
20100251329 Wei Sep 2010 A1
20100251340 Martin et al. Sep 2010 A1
20100265825 Blair et al. Oct 2010 A1
20100281108 Cohen Nov 2010 A1
20100291910 Sanding et al. Nov 2010 A1
20100299437 Moore Nov 2010 A1
20100312919 Lee et al. Dec 2010 A1
20100332852 Vembu et al. Dec 2010 A1
20110026516 Roberts et al. Feb 2011 A1
20110029882 Jaisinghani Feb 2011 A1
20110029981 Jaisinghani Feb 2011 A1
20110053555 Cai et al. Mar 2011 A1
20110078278 Cui et al. Mar 2011 A1
20110081008 Lawson et al. Apr 2011 A1
20110083069 Paul et al. Apr 2011 A1
20110083179 Lawson et al. Apr 2011 A1
20110093516 Geng et al. Apr 2011 A1
20110096673 Stevenson et al. Apr 2011 A1
20110110366 Moore et al. May 2011 A1
20110131293 Mori Jun 2011 A1
20110138453 Verma Jun 2011 A1
20110143714 Keast Jun 2011 A1
20110145049 Udo et al. Jun 2011 A1
20110149810 Koren et al. Jun 2011 A1
20110149950 Petit-Huguenin et al. Jun 2011 A1
20110151884 Zhao Jun 2011 A1
20110158235 Senga Jun 2011 A1
20110167172 Roach et al. Jul 2011 A1
20110170505 Rajasekar et al. Jul 2011 A1
20110176537 Lawson et al. Jul 2011 A1
20110179126 Wetherell et al. Jul 2011 A1
20110211679 Mezhibovsky et al. Sep 2011 A1
20110251921 Kassaei et al. Oct 2011 A1
20110253693 Lyons et al. Oct 2011 A1
20110255675 Jasper et al. Oct 2011 A1
20110258432 Rao Oct 2011 A1
20110265168 Lucovsky et al. Oct 2011 A1
20110265172 Sharma Oct 2011 A1
20110267985 Wilkinson et al. Nov 2011 A1
20110274111 Narasappa et al. Nov 2011 A1
20110276892 Jensen-Home et al. Nov 2011 A1
20110276951 Jain Nov 2011 A1
20110280390 Lawson et al. Nov 2011 A1
20110283259 Lawson et al. Nov 2011 A1
20110289126 Aikas et al. Nov 2011 A1
20110289162 Furlong et al. Nov 2011 A1
20110299672 Chiu et al. Dec 2011 A1
20110310902 Xu Dec 2011 A1
20110313950 Nuggehalli et al. Dec 2011 A1
20110320449 Gudlavenkatasiva Dec 2011 A1
20110320550 Lawson et al. Dec 2011 A1
20120000903 Baarman et al. Jan 2012 A1
20120011274 Moreman Jan 2012 A1
20120017222 May Jan 2012 A1
20120023531 Meuninck et al. Jan 2012 A1
20120023544 Li et al. Jan 2012 A1
20120027228 Rijken et al. Feb 2012 A1
20120028602 Lisi et al. Feb 2012 A1
20120036574 Heithcock et al. Feb 2012 A1
20120039202 Song Feb 2012 A1
20120059709 Lieberman et al. Mar 2012 A1
20120079066 Li et al. Mar 2012 A1
20120083266 VanSwol et al. Apr 2012 A1
20120089572 Raichstein et al. Apr 2012 A1
20120094637 Jeyaseelan et al. Apr 2012 A1
20120101952 Raleigh et al. Apr 2012 A1
20120110564 Ran et al. May 2012 A1
20120114112 Rauschenberger et al. May 2012 A1
20120149404 Beattie et al. Jun 2012 A1
20120166488 Kaushik et al. Jun 2012 A1
20120170726 Schwartz Jul 2012 A1
20120173610 Bleau Jul 2012 A1
20120174095 Natchadalingam et al. Jul 2012 A1
20120179646 Hinton Jul 2012 A1
20120179907 Byrd et al. Jul 2012 A1
20120180021 Byrd et al. Jul 2012 A1
20120180029 Hill et al. Jul 2012 A1
20120185561 Klein Jul 2012 A1
20120198004 Watte Aug 2012 A1
20120201238 Lawson et al. Aug 2012 A1
20120208495 Lawson et al. Aug 2012 A1
20120221603 Kothule et al. Aug 2012 A1
20120226579 Ha et al. Sep 2012 A1
20120239757 Firstenberg et al. Sep 2012 A1
20120240226 Li Sep 2012 A1
20120246273 Bornstein et al. Sep 2012 A1
20120254828 Aiylam et al. Oct 2012 A1
20120266258 Tuchman Oct 2012 A1
20120281536 Gell et al. Nov 2012 A1
20120288082 Segall Nov 2012 A1
20120290706 Lin et al. Nov 2012 A1
20120304245 Lawson Nov 2012 A1
20120304275 Ji et al. Nov 2012 A1
20120316809 Egolf et al. Dec 2012 A1
20120321058 Eng et al. Dec 2012 A1
20120321070 Smith et al. Dec 2012 A1
20130029629 Lindholm et al. Jan 2013 A1
20130031158 Salsburg Jan 2013 A1
20130031613 Shanabrook Jan 2013 A1
20130036476 Roever et al. Feb 2013 A1
20130047232 Tuchman et al. Feb 2013 A1
20130054517 Beechuk Feb 2013 A1
20130054684 Brazier et al. Feb 2013 A1
20130058262 Parreira Mar 2013 A1
20130067232 Cheung et al. Mar 2013 A1
20130067448 Sannidhanam et al. Mar 2013 A1
20130097298 Ting et al. Apr 2013 A1
20130110658 Lyman et al. May 2013 A1
20130132573 Lindblom May 2013 A1
20130139148 Berg et al. May 2013 A1
20130156024 Burg Jun 2013 A1
20130166580 Maharajh et al. Jun 2013 A1
20130179942 Caplis et al. Jul 2013 A1
20130201909 Bosch et al. Aug 2013 A1
20130204786 Mattes et al. Aug 2013 A1
20130212603 Cooke et al. Aug 2013 A1
20130244632 Spence et al. Sep 2013 A1
20130268676 Martins et al. Oct 2013 A1
20130325934 Fausak et al. Dec 2013 A1
20130328997 Desai Dec 2013 A1
20130336472 Fahlgren et al. Dec 2013 A1
20140013400 Warshavsky Jan 2014 A1
20140025503 Meyer et al. Jan 2014 A1
20140058806 Guenette et al. Feb 2014 A1
20140064467 Lawson Mar 2014 A1
20140072115 Makagon et al. Mar 2014 A1
20140073291 Hildner et al. Mar 2014 A1
20140095627 Romagnino Apr 2014 A1
20140101058 Castel et al. Apr 2014 A1
20140101149 Winters Apr 2014 A1
20140105372 Nowack et al. Apr 2014 A1
20140106704 Cooke et al. Apr 2014 A1
20140122600 Kim et al. May 2014 A1
20140123187 Reisman May 2014 A1
20140126715 Lum et al. May 2014 A1
20140129363 Lorah et al. May 2014 A1
20140153565 Lawson et al. Jun 2014 A1
20140185490 Holm et al. Jul 2014 A1
20140254600 Shibata et al. Sep 2014 A1
20140258481 Lundell Sep 2014 A1
20140269333 Boerjesson Sep 2014 A1
20140274086 Boerjesson et al. Sep 2014 A1
20140282473 Saraf et al. Sep 2014 A1
20140289391 Balaji et al. Sep 2014 A1
20140304054 Orun et al. Oct 2014 A1
20140317640 Harm Oct 2014 A1
20140355600 Lawson Dec 2014 A1
20140372508 Fausak et al. Dec 2014 A1
20140372509 Fausak et al. Dec 2014 A1
20140372510 Fausak et al. Dec 2014 A1
20140373098 Fausak et al. Dec 2014 A1
20140379670 Kuhr Dec 2014 A1
20150004932 Kim et al. Jan 2015 A1
20150004933 Kim et al. Jan 2015 A1
20150023251 Giakoumelis et al. Jan 2015 A1
20150026477 Malatack et al. Jan 2015 A1
20150066865 Yara et al. Mar 2015 A1
20150081918 Nowack et al. Mar 2015 A1
20150082378 Collison Mar 2015 A1
20150100634 He et al. Apr 2015 A1
20150119050 Liao et al. Apr 2015 A1
20150181631 Lee et al. Jun 2015 A1
20150236905 Bellan et al. Aug 2015 A1
20150281294 Nur et al. Oct 2015 A1
20150365480 Soto et al. Dec 2015 A1
20150370788 Bareket et al. Dec 2015 A1
20150381580 Graham, II Dec 2015 A1
20160011758 Dornbush et al. Jan 2016 A1
20160028695 Binder Jan 2016 A1
20160077693 Meyer et al. Mar 2016 A1
20160112475 Lawson et al. Apr 2016 A1
20160112521 Lawson et al. Apr 2016 A1
20160119291 Zollinger et al. Apr 2016 A1
20160127254 Kumar et al. May 2016 A1
20160149956 Birnbaum et al. May 2016 A1
20160162172 Rathod Jun 2016 A1
20160205519 Patel et al. Jul 2016 A1
20160225044 Lawson Aug 2016 A1
20160226937 Patel et al. Aug 2016 A1
20160226979 Lancaster et al. Aug 2016 A1
20160234391 Wolthuis Aug 2016 A1
20160239770 Batabyal et al. Aug 2016 A1
20170032433 Lawson Feb 2017 A1
20170339283 Chaudhary et al. Nov 2017 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 Apr 1998 JP
2004166000 Jun 2004 JP
2004220118 Aug 2004 JP
2006319914 Nov 2006 JP
9732448 Sep 1997 WO
2002087804 Nov 2002 WO
2006037492 Apr 2006 WO
018489 Feb 2009 WO
2009124223 Oct 2009 WO
2010037064 Apr 2010 WO
2010040010 Apr 2010 WO
2010101935 Sep 2010 WO
2011091085 Jul 2011 WO
Non-Patent Literature Citations (18)
Entry
“Ethernet to Token ring Bridge”—Black Box Corporation, Oct. 1999 http://blackboxcanada.com/resource/files/productdetails/17044.pdf.
Abu-Lebdeh et al. “A 3GPP Evolved Packet Core-Based Architecture for QoS-Enabled Mobile Video Surveillance Applications”. 2012 Third International Conference on the Network of the Future (NOF). Nov. 21-23, 2012. pp. 1-6.
Archive Microsoft Office 365 Email | Retain Unified Archiving, 2015, Gwava, Inc., Montreal, Canada.
Complaint for Patent Infringement, Telinit Technologies, LLC v. Twilio Inc., dated Oct. 12, 2012.
Kim et al. “In- service Feedback QoE Framework” 2010 Third International Conference on Communication Theory. Reliability and Quality of Service. pp. 135-138. 2010.
Matos et al. “Quality of Experience-based Routing in Multi-Service Wireless Mesh Networks” Realizing Advanced Video Optimized Wireless Networks. IEEE. pp. 7060-7065. 2012.
NPL, “API Monetization Platform”, 2013.
RFC 3986: Uniform Resource Identifier (URI): Generic Syntax; T. Berners-Lee, R. Fielding, L. Masinter; Jan. 2005; The Internet Society.
S. barakovic and L Skorin-Kapov. “Survey and Challenges of QoE Management Issues in Wireless Networks”. 2012, pp. 1-29.
Subramanya, et al. “Digital Signatures”, IEEE Potentials, Mar./Apr. 2006, pp. 5-8.
Tran et al. “User to User adaptive routing based on QoE” ICNS 2011: The Seventh International Conference on Networking and Services. pp. 170-177. 2011.
Twilio Cloud Communications—APIs for Voice, VoIP, and Text Messaging, Twilio.
Wu et al. “Quality Evaluation in Peer-to-Peer IPTV Services” Data Traffic and Monitoring Analysis, LNCS 7754. pp. 302-319. 2013.
“U.S. Appl. No. 15/013,292, Notice of Allowance dated Jul. 11, 2016”, 13 pgs.
“U.S. Appl. No. 15/262,220, Non Final Office Action dated Dec. 2, 2016”, 8 pgs.
“U.S. Appl. No. 15/262,220, Response filed Feb. 21, 2017 to Non Final Office Action dated Dec. 2, 2016”, 11 pgs.
“U.S. Appl. No. 15/262,220, Notice of Allowance dated Mar. 17, 2017”, 11 pgs.
“U.S. Appl. No. 15/262,220, Notice of Allowance dated Jun. 19, 2017”, 11 pgs.
Related Publications (1)
Number Date Country
20180005283 A1 Jan 2018 US
Provisional Applications (1)
Number Date Country
62111399 Feb 2015 US
Continuations (2)
Number Date Country
Parent 15262220 Sep 2016 US
Child 15708845 US
Parent 15013292 Feb 2016 US
Child 15262220 US