System and method for providing communication platform metadata
US-9137127-B2 · Sep 15, 2015 · US
US11246013B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11246013-B2 |
| Application number | US-202016892876-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jun 4, 2020 |
| Priority date | Oct 15, 2012 |
| Publication date | Feb 8, 2022 |
| Grant date | Feb 8, 2022 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A system and method for triggering on platform usage can include at a platform, receiving and storing a trigger configuration of an account; operating a platform comprising internally executing a process on behalf of an account and publishing at least one event when executing the process; at the platform, incrementing a counter in response to the at least one event and if the stored trigger configuration species a usage key associated with a category of counted events of the at least one event; monitoring counters in a context of an associated trigger; and processing the trigger upon the counter satisfying condition of an associated trigger.
Opening claim text (preview).
What is claimed is: 1. A method for implementing event based usage triggers in relation to communication services provided by a communication system, the method comprising: determining, by the communication system, a number of occurrences of an event in relation to an account of the communication system, the communication system providing communication services in relation to communication endpoints allocated to the account by the communication system; determining, by the communication system, that the number of occurrences of the event meets a threshold number of occurrences of the event defined by a usage trigger configuration associated with the account of the communication system; identifying a callback Uniform Resource Identifier (URI) defined by the usage trigger configuration, the callback URI referencing an external resource providing a web application associated with the account of the communication system; and transmitting a HyperText Transfer Protocol (HTTP) request directed to the callback URI, the HTTP request including at least one parameter defined by the usage trigger configuration and causing the web application to perform a specified application platform response based on the at least one parameter. 2. The method of claim 1 , further comprising: receiving, from a computing system that is external to the communication system, the usage trigger configuration for the account of the communication system, the usage trigger configuration defining the event, the threshold number and the callback URI; and establishing the usage trigger in relation to the account based on the trigger configuration. 3. The method of claim 2 , wherein the usage trigger configuration is received via an Application Programming Interface (API) request, the API request being based on an API provided for communication with the communication system. 4. The method of claim 1 , wherein the at least one parameter includes a count value indicating the number of occurrences of the event in relation to the account of the communication system. 5. The method of claim 1 , wherein determining that the number of occurrences of the event meets the threshold number of occurrences of the event comprises: comparing the number of occurrences to the threshold number of occurrences defined by the usage trigger, yielding a comparison; and determining, based on the comparison, that the number of occurrences meets or exceeds the threshold number of occurrences. 6. The method of claim 5 , wherein the number of occurrences of the event in relation to the account is determined based on a counter associated with the event trigger, the communication system having incremented the counter in response to each detected occurrence of the event in relation to the account. 7. The method of claim 5 , wherein the number of occurrences of the event in relation to the account is determined based on an event log including records of events associated with the account. 8. A communication system providing event based usage triggers in relation to communication services provided by the communication system, the 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 communication system to perform operations comprising: determining a number of occurrences of an event in relation to an account of the communication system, the communication system providing communication services in relation to communication endpoints allocated to the account by the communication system; determining that the number of occurrences of the event meets a threshold number of occurrences of the event defined by a usage trigger configuration associated with the account of the communication system; identifying a callback Uniform Resource Identifier (URI) defined by the usage trigger configuration, the callback URI referencing an external resource providing a web application associated with the account of the communication system; and transmitting a HyperText Transfer Protocol (HTTP) request directed to the callback URI, the HTTP request including at least one parameter defined by the usage trigger configuration and causing the web application to perform a specified application platform response based on the at least one parameter. 9. The communication system of claim 8 , the operations further comprising: receiving, from a computing system that is external to the communication system, the usage trigger configuration for the account of the communication system, the usage trigger configuration defining the event, the threshold number and the callback URI; and establishing the usage trigger in relation to the account based on the trigger configuration. 10. The communication system of claim 9 , wherein the usage trigger configuration is received via an Application Programming Interface (API) request, the API request being based on an API provided for communication with the communication system. 11. The communication system of claim 8 , wherein the at least one parameter includes a count value indicating the number of occurrences of the event in relation to the account of the communication system. 12. The communication system of claim 8 , wherein determining that the number of occurrences of the event meets the threshold number of occurrences of the event comprises: comparing the number of occurrences to the threshold number of occurrences defined by the usage trigger, yielding a comparison; and determining, based on the comparison, that the number of occurrences meets or exceeds the threshold number of occurrences. 13. The communication system of claim 12 , wherein the number of occurrences of the event in relation to the account is determined based on a counter associated with the event trigger, the communication system having incremented the counter in response to each detected occurrence of the event in relation to the account. 14. The communication system of claim 12 , wherein the number of occurrences of the event in relation to the account is determined based on an event log including records of events associated with the account. 15. A non-transitory computer-readable medium storing instructions that, when executed by one or more computer-processors of a communication system, cause the communication system to perform operations for implementing event based usage triggers in relation to communication services provided by the communication system, the operations comprising: determining a number of occurrences of an event in relation to an account of the communication system, the communication system providing communication services in relation to communication endpoints allocated to the account by the communication system; determining that the number of occurrences of the event meets a threshold number of occurrences of the event defined by a usage trigger configuration associated with the account of the communication system; identifying a callback Uniform Resource Identifier (URI) defined by the usage trigger configuration, the callback URI referencing an external resource providing a web application associated with the account of the communication system; and transmitting a HyperText Transfer Protocol (HTTP) request directed to the callback URI, the HTTP request including at least one parameter defined by the usage trigger configuration and causing the web application to perform a specified application platform response based on the at least one parameter. 16. The non-transitory computer-readable medium of claim 15 , the operation
Communication-related supplementary services, e.g. call-transfer or call-hold · CPC title
Mobile subscriber · CPC title
Message passing systems or structures, e.g. queues · CPC title
Active monitoring, e.g. heartbeat, ping or trace-route · CPC title
based on web technology, e.g. hypertext transfer protocol [HTTP] · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.