Single number communications accessibility

US12088644B1 · US · B1

Patent metadata
FieldValue
Publication numberUS-12088644-B1
Application numberUS-202318200369-A
CountryUS
Kind codeB1
Filing dateMay 22, 2023
Priority dateMay 22, 2023
Publication dateSep 10, 2024
Grant dateSep 10, 2024

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.

System and methods for routing requests for both assisted communications and non-assisted communications with devices operated by deaf or hard-of-hearing (DHH) users using a single number are described. A network component may determine whether to use routing that directs such requests to an assistance system based on the type of communications requested and one or more identifiers in a request. If a communications request includes a DHH user device's identifier and communications type that are represented in assistance routing data, the network component may forward that request to an assistance system. Otherwise, the network component may route such a request normally. A DHH user may request a suspension of the assistance routing for a period of time and/or until reinstatement of the assistance routing is requested.

First claim

Opening claim text (preview).

What is claimed is: 1. A method comprising: receiving, from a user equipment (UE) at a session border controller (SBC) configured at a wireless communications network, a request to establish a communications session between the UE and a destination device; determining, at the SBC and based at least in part on the request, a requested communications type and a device identifier associated with the UE; determining, at the SBC and based at least on the requested communications type and the device identifier, assistance routing data associated with the UE; generating, based at least in part on determining the assistance routing data associated with the UE and the request, a session initiation protocol (SIP) INVITE message based at least in part on the request; transmitting, by the SBC and based at least in part on the assistance routing data, the SIP INVITE message to a video relay service (VRS) system; and establishing, via the wireless communications network and based at least in part on the SIP INVITE message, the communications session between the UE and the destination device via the VRS system. 2. The method of claim 1 , wherein the SBC is associated with a call session control function (CSCF) configured to determine the assistance routing data associated with the UE. 3. The method of claim 1 , wherein determining the assistance routing data associated with the UE is further based at least in part on initial filter criteria (iFC) data. 4. The method of claim 1 , wherein transmitting the SIP INVITE message to the VRS system comprises transmitting the SIP INVITE message via a SIP trunk communicatively connecting the SBC and the VRS system. 5. The method of claim 1 , wherein the assistance routing data comprises an indication of the VRS system. 6. The method of claim 1 , further comprising accessing, by a call session control function (CSCF) associated with the SBC, the assistance routing data from a home subscriber server (HSS). 7. A session border controller (SBC) comprising: one or more processors; one or more transceivers; and non-transitory computer-readable media storing computer-executable instructions that, when executed by the one or more processors, cause the one or more processors to perform operations comprising: receiving, from a user equipment (UE), a first request to establish a communications session between the UE and a destination device; determining, based at least in part on the first request, a requested communications type and a device identifier associated with the destination device; determining, based at least on the requested communications type and the device identifier, assistance routing data associated with the destination device; transmitting, based at least in part on the first request and the assistance routing data, a second request to establish the communications session to a video relay service (VRS) system; and establishing, based at least in part on the second request, the communications session between the UE and the destination device via the VRS system. 8. The SBC of claim 7 , wherein the operations further comprise: receiving, from the destination device, a third request to suspend use of the assistance routing data; and disabling, based at least on the third request, the assistance routing data. 9. The SBC of claim 8 , wherein the operations further comprise: receiving, from the destination device, a fourth request to resume use of the assistance routing data; and restoring, based at least on the fourth request, the assistance routing data. 10. The SBC of claim 8 , wherein the operations further comprise: determining that a time period has elapsed since disabling the assistance routing data; and restoring, based at least on determining that the time period has elapsed, the assistance routing data. 11. The SBC of claim 10 , wherein the third request comprises an indication of the time period. 12. The SBC of claim 7 , wherein determining, based at least on the requested communications type and the device identifier, the assistance routing data comprises determining that the communications type is associated with voice communications. 13. The SBC of claim 7 , wherein the assistance routing data comprises initial filter criteria (iFC) data. 14. The SBC of claim 7 , wherein the device identifier is one of: a telephone number; a mobile station international subscriber directory number (MSISDN); an international mobile subscriber identity (IMSI); or a network address. 15. A non-transitory computer-readable media storing computer-executable instructions that, when executed by one or more processors, cause the one or more processors to perform operations comprising: receiving, from a user equipment (UE) at a session border controller (SBC) configured at a wireless communications network, a first request to establish a communications session between the UE and a destination device; determining, at the SBC and based at least in part on the first request, a requested communications type and a device identifier associated with the UE; determining, at the SBC and based at least on the requested communications type and the device identifier, assistance routing data associated with the UE; transmitting, by the SBC and based at least in part on the first request and the assistance routing data, a second request to establish the communications session to a video relay service (VRS) system; and establishing, via the wireless communications network and based at least in part on the second request, the communications session between the UE and the destination device via the VRS system. 16. The non-transitory computer-readable media of claim 15 , wherein the operations further comprise: receiving, from a user equipment (UE) at a session border controller (SBC) configured at a wireless communications network, a third request to transmit data from the UE to the destination device; determining, at the SBC and based at least in part on the third request, a communications type associated with the third request and the device identifier associated with the UE; and determining, at the SBC and based at least on the communications type associated with the third request and the device identifier, to route the third request based at least in part on the third request and excluding the assistance routing data. 17. The non-transitory computer-readable media of claim 15 , wherein the requested communications type is a video call. 18. The non-transitory computer-readable media of claim 15 , wherein transmitting the second request to the VRS system causes the VRS system to: generate a session initiation protocol (SIP) INVITE message based at least in part on the second request; and transmit the SIP INVITE message to the destination device. 19. The non-transitory computer-readable media of claim 18 , wherein the SIP INVITE message comprises a source identifier comprising the device identifier associated with the UE and a destination identifier comprising a second device identifier associated with the destination device. 20. The non-transitory computer-readable media of claim 15 , wherein the assistance routing data comprises initial filter criteria (iFC) data.

Assignees

Inventors

Classifications

  • Proxies, e.g. for session initiation protocol [SIP] · CPC title

  • IP multimedia subsystem [IMS] · CPC title

  • Session initiation protocol [SIP] · CPC title

  • Session establishment or de-establishment · CPC title

  • Call controllers; Call servers · 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 US12088644B1 cover?
System and methods for routing requests for both assisted communications and non-assisted communications with devices operated by deaf or hard-of-hearing (DHH) users using a single number are described. A network component may determine whether to use routing that directs such requests to an assistance system based on the type of communications requested and one or more identifiers in a request…
Who is the assignee on this patent?
T Mobile Usa Inc
What technology area does this patent fall under?
Primary CPC classification H04L65/1104. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue Sep 10 2024 00:00:00 GMT+0000 (Coordinated Universal Time) (B1). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 7 related publications on this page (citations in our corpus or others sharing the same primary CPC).