IP Library Granted Patent US 11,017,183
Granted Patent B2
US 11,017,183 · App. 16/381,107 · Granted May 25, 2021

System and methods for auto-translating text messages

Inventors: Karthik Iyer (Bellevue, WA); Michael Kim (Bellevue, WA)
Assignee: T-MOBILE USA, INC.
G06F40/58G06F40/263H04L65/1006H04W4/12
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,017,183
App. No.
16/381,107
Granted
May 25, 2021
Kind
B2
Abstract

Embodiments described herein relate to a language translation services within a Rich Communication Services (RCS) messaging infrastructure to facilitate translating RCS message sent from an RCS-compatible sender device to an RCS-compatible recipient device or a legacy recipient device. An RCS messaging server (RMS) may detect a language value corresponding to a language preference parameter to translate the RCS message based on the language value. The language value may be passed to the RMS (1) from the sender device via an invite message of the Session Initiation Protocol (SIP), (2) from the recipient device via an accept message of the SIP, (3) from the RCS message itself, or (4) via communication with a home subscription server (HSS).

Claims (73)

1. A computer-implemented method for translating a rich communication services (RCS) message, the method comprising:

receiving, by one or more processors of an RCS Messaging Server (RMS) and from a first device that is RCS-compatible, an invite message to request an RCS session for delivery of the RCS message between the first device and a second device that is RCS-compatible, wherein the invite message is a Session Initiation Protocol (SIP) message to initiate the RCS session;

receiving, by the one or more processors of the RMS and from the second device, an accept message in response to the invite message, wherein the accept message is a SIP response message to establish the RCS session;

receiving, by the one or more processors of the RMS, the RCS message in a first language from the first device;

identifying, by the one or more processors of the RMS, a language preference configuration parameter included in at least one of the invite message or the accept message;

obtaining, by the one or more processors of the RMS, a language preference value of the second device based upon the language preference configuration parameter;

generating, by the one or more processors of the RMS, a translation of the RCS message in a second language from the RCS message in the first language in accordance with the language preference value of the second device; and

transmitting, by the one or more processors of the RMS, the translation of the RCS message in the second language to the second device.

2. The computer-implemented method of claim 1 , wherein the language preference configuration parameter is included in the invite message and wherein identifying the language preference configuration parameter comprises:

determining the language preference configuration parameter associated with a messaging application native to the first device.

3. The computer-implemented method of claim 1 , wherein the language preference configuration parameter is included in the accept message and wherein identifying the language preference configuration parameter comprises:

determining the language preference configuration parameter associated with a messaging application native to the second device.

4. The computer-implemented method of claim 1 , further comprising:

receiving, by the one or more processors of the RMS and from the first device, a request for delivery of a second RCS message from the first device to the second device, wherein the second RCS message is in the first language;

determining, by the one or more processors of the RMS, the RCS session has not expired;

generating, by the one or more processors of the RMS, a translation of the second RCS message in the second language; and

transmitting, by the one or more processors of the RMS, the translation of the second RCS message in the second language to the second device.

5. The computer-implemented method of claim 1 , further comprising:

receiving, by the one or more processors of the RMS and from the first device, a request for delivery of a second RCS message from the first device to the second device, wherein the second RCS message is in the first language;

determining, by the one or more processors of the RMS, the RCS session has expired;

obtaining, by the one or more processors of the RMS, the language preference value of the second device;

generating, by the one or more processors of the RMS, a translation of the RCS message in accordance with the language preference value of the second device; and

transmitting, by the one or more processors of the RMS, the translation of the RCS message to the second device.

6. The computer-implemented method of claim 1 , further comprising:

transmitting, by the one or more processors of the RMS, the RCS message in the first language to the second device.

7. A system for translating a rich communication services (RCS) message, the system comprising:

a first device that is RCS-compatible;

a second device that is RCS-compatible; and

an RCS Messaging Server (RMS) configured to:

receive, from the first device, an invite message to request an RCS session for delivery of the RCS message between the first device and a second device,

wherein the invite message is a Session Initiation Protocol (SIP) message to initiate the RCS session;

receive, from the second device, an accept message in response to the invite message, wherein the accept message is a SIP response message to establish the RCS session;

receive the RCS message in a first language from the first device;

identify a language preference configuration parameter included in at least one of the invite message or the accept message;

obtain a language preference value of the second device based upon the language preference configuration parameter;

generate a translation of the RCS message in a second language from the RCS message in the first language in accordance with the language preference value of the second device; and

transmit the translation of the RCS message in the second language to the second device.

8. The system of claim 7 , wherein the language preference configuration parameter is included in the invite message and wherein the RMS is configured to identify the language preference configuration parameter by determining the language preference configuration parameter associated with a messaging application native to the first device.

9. The system of claim 7 , wherein the language preference configuration parameter is included in the accept message and wherein the RMS is configured to identify the language preference configuration parameter by determining the language preference configuration parameter associated with a messaging application native to the second device.

10. The system of claim 7 , wherein the RMS is further configured to:

receive, from the first device, a request for delivery of a second RCS message from the first device to the second device, wherein the second RCS message is in the first language;

determine the RCS session has not expired;

generate a translation of the second RCS message in the second language; and

transmit the translation of the second RCS message in the second language to the second device.

11. The system of claim 7 , wherein the RMS is further configured to:

receive, from the first device, a request for delivery of a second RCS message from the first device to the second device, wherein the second RCS message is in the first language;

determine the RCS session has expired;

obtain the language preference value of the second device;

generate a translation of the RCS message in accordance with the language preference value of the second device; and

transmit the translation of the RCS message to the second device.

12. The system of claim 7 , wherein the RMS is further configured to:

transmit the RCS message in the first language to the second device.

13. A non-transitory, tangible computer-readable medium storing machine readable instructions for translating a rich communication services (RCS) message, when executed by one or more processors of an RCS Messaging Server (RMS), cause the one or more processors to:

receive, from a first device that is RCS-compatible, an invite message to request an RCS session for delivery of the RCS message between the first device and a second device that is RCS-compatible, wherein the invite message is a Session Initiation Protocol (SIP) message to initiate the RCS session;

receive, from the second device, an accept message in response to the invite message, wherein the accept message is a SIP response message to establish the RCS session;

receive the RCS message in a first language from the first device;

identify a language preference configuration parameter included in at least one of the invite message or the accept message;

obtain a language preference value of the second device based upon the language preference configuration parameter;

generate a translation of the RCS message in a second language from the RCS message in the first language in accordance with the language preference value of the second device; and

transmit the translation of the RCS message in the second language to the second device.

14. The non-transitory, tangible computer-readable medium of claim 13 , wherein the language preference configuration parameter is included in the invite message and wherein the machine readable instructions cause the one or more processors to identify the language preference configuration parameter by determining the language preference configuration parameter associated with a messaging application native to the first device.

15. The non-transitory, tangible computer-readable medium of claim 13 , wherein the language preference configuration parameter is included in the accept message and wherein the machine readable instructions cause the one or more processors to identify the language preference configuration parameter by determining the language preference configuration parameter associated with a messaging application native to the second device.

16. The non-transitory, tangible computer-readable medium of claim 13 , wherein the machine readable instructions, when executed by the one or more processors of the RMS, further cause the one or more processors to:

receive, from the first device, a request for delivery of a second RCS message from the first device to the second device, wherein the second RCS message is in the first language;

determine the RCS session has not expired;

generate a translation of the second RCS message in the second language; and

transmit the translation of the second RCS message in the second language to the second device.

17. The non-transitory, tangible computer-readable medium of claim 13 , wherein the machine readable instructions, when executed by the one or more processors of the RMS, further cause the one or more processors to:

receive, from the first device, a request for delivery of a second RCS message from the first device to the second device, wherein the second RCS message is in the first language;

determine the RCS session has expired;

obtain the language preference value of the second device;

generate a translation of the RCS message in accordance with the language preference value of the second device; and

transmit the translation of the RCS message to the second device.

Assignments (3)
RELEASE OF SECURITY INTEREST Recorded Aug 23, 2022
From: DEUTSCHE BANK TRUST COMPANY AMERICAS
To: IBSV LLC; LAYER3 TV, LLC; PUSHSPRING, LLC; T-MOBILE CENTRAL LLC; T-MOBILE USA, INC.; ASSURANCE WIRELESS USA, L.P.; BOOST WORLDWIDE, LLC; CLEARWIRE COMMUNICATIONS LLC; CLEARWIRE IP HOLDINGS LLC; SPRINTCOM LLC; SPRINT COMMUNICATIONS COMPANY L.P.; SPRINT INTERNATIONAL INCORPORATED; SPRINT SPECTRUM LLC
Reel/Frame 062595/0001 →
SECURITY AGREEMENT Recorded Apr 2, 2020
From: T-MOBILE USA, INC.; ISBV LLC; T-MOBILE CENTRAL LLC; LAYER3 TV, INC.; PUSHSPRING, INC.; BOOST WORLDWIDE, LLC; CLEARWIRE COMMUNICATIONS LLC; CLEARWIRE IP HOLDINGS LLC; CLEARWIRE LEGACY LLC; SPRINT COMMUNICATIONS COMPANY L.P.; SPRINT INTERNATIONAL INCORPORATED; SPRINT SPECTRUM L.P.; ASSURANCE WIRELESS USA, L.P.
To: DEUTSCHE BANK TRUST COMPANY AMERICAS
Reel/Frame 053182/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 15, 2019
From: IYER, KARTHIK; KIM, MICHAEL
To: T-MOBILE USA, INC.
Reel/Frame 049181/0528 →
Continuity (1)
Related Publication 20200327199A1 · Oct 15, 2020
Cited By (2)
US 12,470,612 US 12,495,081