System and method for automatically transitioning between carrier and IP messaging

US12506701B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-12506701-B2
Application numberUS-202418650048-A
CountryUS
Kind codeB2
Filing dateApr 29, 2024
Priority dateNov 11, 2020
Publication dateDec 23, 2025
Grant dateDec 23, 2025

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

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.

First claim

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.

Assignees

Inventors

Classifications

  • 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

  • H04L51/56Primary

    Unified messaging, e.g. interactions between e-mail, instant messaging or converged IP messaging [CPM] · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US12506701B2 cover?
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 c…
Who is the assignee on this patent?
Twilio Inc
What technology area does this patent fall under?
Primary CPC classification H04L51/56. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue Dec 23 2025 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 4 related publications on this page (citations in our corpus or others sharing the same primary CPC).