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