Systems and methods for a proactive two-way conversation
US-11736430-B2 · Aug 22, 2023 · US
US12506701B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12506701-B2 |
| Application number | US-202418650048-A |
| Country | US |
| Kind code | B2 |
| Filing date | Apr 29, 2024 |
| Priority date | Nov 11, 2020 |
| Publication date | Dec 23, 2025 |
| Grant date | Dec 23, 2025 |
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 automatically transitioning between carrier and IP messaging that can include receiving a messaging request specifying a destination endpoint for a message, retrieving client status of the destination endpoint from a client application registry system, evaluating the client status of the destination endpoint for use of a client application, and depending on whether the client status is being active or inactive, transmitting the message either to the destination endpoint or the client application associated with the destination endpoint.
Opening claim text (preview).
What is claimed is: 1 . A method comprising: receiving a messaging request specifying a destination endpoint for a message; retrieving client status of the destination endpoint from a client application registry system, the client status comprising an identifier of a client application registered for reaching the destination endpoint; evaluating the client status of the destination endpoint for use of the client application; and depending on whether the client status is being active or inactive, transmitting the message either to the destination endpoint or the client application associated with the destination endpoint. 2 . The method of claim 1 , wherein the client status comprises an identifier of the client application. 3 . The method of claim 1 , wherein the client application is registered to receive a plurality of messages from a plurality of senders at the destination endpoint. 4 . The method of claim 3 , further comprising: selecting, from one or more carrier-based communication options and one or more IP-based communication options, a messaging protocol option based on the client application registered to receive the plurality of messages from the plurality of senders at the destination endpoint. 5 . The method of claim 4 , wherein: the client status indicates time-based activity of the client application; and selecting the messaging protocol option comprises detecting client application registration and inspecting the time-based activity of the client application. 6 . The method of claim 1 , wherein transmitting the message comprises: in response to the destination endpoint having an inactive client status, transmitting content of the messaging request to the destination endpoint; or in response to the destination endpoint having an active client status, transmitting the content of the messaging request to the client application associated with the destination endpoint. 7 . The method of claim 1 , wherein retrieving the client status of the destination endpoint from the client application registry system comprises querying multiple client application registries of the client application registry system. 8 . The method of claim 1 , the client application registry system includes an internally maintained client application registry. 9 . The method of claim 1 , further comprising receiving client application registration update and updating the client application registry system. 10 . The method of claim 1 , wherein the messaging request is received via an application programming interface. 11 . A system comprising: a memory; and at least one computer processor coupled to the memory to perform operations comprising: receiving a messaging request specifying a destination endpoint for a message; retrieving client status of the destination endpoint from a client application registry system, the client status comprising an identifier of a client application registered for reaching the destination endpoint; evaluating the client status of the destination endpoint for use of the client application; and depending on whether the client status is being active or inactive, transmitting the message either to the destination endpoint or the client application associated with the destination endpoint. 12 . The system of claim 11 , the operations further comprising: selecting, from one or more carrier-based communication options and one or more IP-based communication options, a messaging protocol option based on the client application registered to receive a plurality of messages from a plurality of senders at the destination endpoint. 13 . The system of claim 12 , wherein: the client status indicates time-based activity of the client application; and selecting the messaging protocol option comprises detecting client application registration and inspecting the time-based activity of the client application. 14 . The system of claim 11 , wherein transmitting the message comprises: in response to the destination endpoint having an inactive client status, transmitting content of the messaging request to the destination endpoint; or in response to the destination endpoint having an active client status, transmitting the content of the messaging request to the client application associated with the destination endpoint. 15 . A non-transitory computer-readable medium storing instructions that, when executed by one or more computer processors of one or more computing devices, cause the one or more computing devices to perform operations comprising: receiving a messaging request specifying a destination endpoint for a message; retrieving client status of the destination endpoint from a client application registry system, the client status comprising an identifier of a client application registered for reaching the destination endpoint; evaluating the client status of the destination endpoint for use of the client application; and depending on whether the client status is being active or inactive, transmitting the message either to the destination endpoint or the client application associated with the destination endpoint. 16 . The non-transitory computer-readable medium of claim 15 , the operations further comprising: selecting, from one or more carrier-based communication options and one or more IP-based communication options, a messaging protocol option based on the client application registered to receive a plurality of messages from a plurality of senders at the destination endpoint. 17 . The non-transitory computer-readable medium of claim 16 , wherein: the client status indicates time-based activity of the client application; and selecting the messaging protocol option comprises detecting client application registration and inspecting the time-based activity of the client application. 18 . The non-transitory computer-readable medium of claim 15 , wherein transmitting the message comprises: in response to the destination endpoint having an inactive client status, transmitting content of the messaging request to the destination endpoint; or in response to the destination endpoint having an active client status, transmitting the content of the messaging request to the client application associated with the destination endpoint. 19 . The non-transitory computer-readable medium of claim 15 , wherein retrieving the client status of the destination endpoint from the client application registry system comprises querying multiple client application registries of the client application registry system. 20 . The non-transitory computer-readable medium of claim 15 , the client application registry system includes an internally maintained client application registry.
Interoperability with other network applications or services · CPC title
Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD] · CPC title
Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication · CPC title
Format adaptation, e.g. format conversion or compression · CPC title
Unified messaging, e.g. interactions between e-mail, instant messaging or converged IP messaging [CPM] · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.