System and method for providing communication platform metadata
US-9137127-B2 · Sep 15, 2015 · US
US11765275B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11765275-B2 |
| Application number | US-202217649113-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jan 27, 2022 |
| Priority date | Apr 2, 2008 |
| Publication date | Sep 19, 2023 |
| Grant date | Sep 19, 2023 |
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.
In one embodiment, the method of processing telephony sessions includes: communicating with an application server using an application layer protocol; processing telephony instructions with a call router; and creating call router resources accessible through a call router Application Programming Interface (API). In another embodiment, the system for processing telephony sessions includes: a call router, a URI for an application server, a telephony instruction executed by the call router, and a call router API resource.
Opening claim text (preview).
We claim: 1. A method comprising: receiving, by one or more processors and via a first application programming interface (API), a message comprising text, the message addressed to a recipient; based on the recipient of the message, identifying a uniform resource locator (URL); and sending a request to an application using a second API and via the identified URL, the request comprising the text of the message and a cryptographic hash computed from parameters of the request. 2. The method of claim 1 , wherein the receiving of the message comprises receiving a Short Message Service (SMS) message. 3. The method of claim 1 , wherein the receiving of the message comprises receiving a Multimedia Messaging Service (MMS) message. 4. The method of claim 1 , wherein the receiving of the message comprises receiving an email. 5. The method of claim 1 , wherein the request further includes an originating phone number of the received message. 6. The method of claim 1 , further comprising: receiving, from the application, a response that includes at least one telephony instruction; and executing, based the at least one telephony instruction, a telephony action. 7. A system comprising: one or more processors; and a memory coupled to the one or more processors and storing instructions that, when executed by the one or more processors, cause the one or more processors to perform operations comprising: receiving, via a first application programming interface (API), a message comprising text, the message addressed to a recipient; based on the recipient of the message, identifying a uniform resource locator (URL); and sending a request to an application using a second API and via the identified URL, the request comprising the text of the message and a cryptographic hash computed from parameters of the request. 8. The system of claim 7 , wherein the receiving of the message comprises receiving a Short Message Service (SMS) message. 9. The system of claim 7 , wherein the receiving of the message comprises receiving a system Messaging Service (MMS) message. 10. The system of claim 7 , wherein the receiving of the message comprises receiving an email. 11. The system of claim 7 , wherein the request further includes an originating phone number of the received message. 12. The system of claim 7 , wherein the operations further comprise: receiving, from the application, a response that includes at least one telephony instruction; and executing, based the at least one telephony instruction, a telephony action. 13. A non-transitory machine-readable medium that stores instructions that, when executed by one or more processors, cause the one or more processors to perform operations comprising: receiving, via a first application programming interface (API), a message comprising text, the message addressed to a recipient; based on the recipient of the message, identifying a uniform resource locator (URL); and sending a request to an application using a second API and via the identified URL, the request comprising the text of the message and a cryptographic hash computed from parameters of the request. 14. The non-transitory machine-readable medium of claim 13 , wherein the receiving of the message comprises receiving a Short Message Service (SMS) message. 15. The non-transitory machine-readable medium of claim 13 , wherein the receiving of the message comprises receiving a system Messaging Service (MMS) message. 16. The non-transitory machine-readable medium of claim 13 , wherein the receiving of the message comprises receiving an email. 17. The non-transitory machine-readable medium of claim 13 , wherein the request further includes an originating phone number of the received message. 18. The non-transitory machine-readable medium of claim 13 , wherein the operations further comprise: receiving, from the application, a response that includes at least one telephony instruction; and executing, based the at least one telephony instruction, a telephony action.
Session protocols · CPC title
Details of addressing, directories or routing tables · CPC title
Click to dial services · CPC title
Session establishment or de-establishment · CPC title
involving digital signatures · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.