Patent application EP20169454A (EP), filed 2020-04-14
Publication number: EP3722986A1
Title: SYSTEMS AND METHODS FOR AUTO-TRANSLATING TEXT MESSAGES
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).
IPC codes: G06F  40/    58            A I
H04L  12/    58            A I
H04W   4/    12            A I
Claims: number: 1
text: A computer-implemented method for translating a rich communication services (RCS) message, the method comprising:
number: 2
text: 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.
number: 3
text: The computer-implemented method of either claim 1 or claim 2, 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.
number: 4
text: The computer-implemented method of any one of claims 1 to 3, wherein the language preference configuration parameter is included in the RCS message and wherein identifying the language preference configuration parameter comprises:
determining the language preference configuration parameter associated with a header of the RCS message.
number: 5
text: The computer-implemented method of any one of claims 1 to 4, further comprising:
number: 6
text: The computer-implemented method of any one of claims 1 to 5, further comprising:
number: 7
text: The computer-implemented method of any one of claims 1 to 6, further comprising:
transmitting, by the one or more processors of the RMS, the RCS message in the first language to the second device.
number: 8
text: A system for translating a rich communication services (RCS) message, the system comprising:
number: 9
text: The system of claim 8, 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.
number: 10
text: The system of either of claim 8 or claim 9, 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.
number: 11
text: The system of any one of claims 8 to 10, wherein the language preference configuration parameter is included in the RCS message and wherein the RMS is configured to identify the language preference configuration parameter by determining the language preference configuration parameter associated with a header of the RCS message.
number: 12
text: The system of any one of claims 8 to 11, wherein the RMS is further configured to:
number: 13
text: The system of any one of claims 8 to 12, wherein the RMS is further configured to:
number: 14
text: The system of any one of claims 8 to 13, wherein the RMS is further configured to:
transmit the RCS message in the first language to the second device.
number: 15
text: 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:
Office action: search_report, dated 2020-10-14
Rejection reasons: novelty_epc_54
Prior art cited: ref_id: US2013066624A1
ref_type: patent
severity: background
ref_id: - ANONYMOUS: "Rich Communication Services - Wikipedia", 17 March 2019 (2019-03-17), XP055724643, Retrieved from the Internet <URL:https://en.wikipedia.org/w/index.php?title=Rich_Communication_Services&oldid=888142729> [retrieved on 20200824]
ref_type: npl
severity: background
ref_id: - ANONYMOUS: "Rich Communication Suite 8.0 Advanced Communications Services and Client Specification - Version 9.0", 16 May 2018 (2018-05-16), XP055725027, Retrieved from the Internet <URL:https://dev.maaprcs.com/docs/public/spec/RCC.07-v9.0.pdf> [retrieved on 20200825]
ref_type: npl
severity: background
ref_id: US2006133585A1
ref_type: patent
severity: background
ref_id: - ANONYMOUS: "Messaging in RCS", 14 November 2014 (2014-11-14), XP055915407, Retrieved from the Internet <URL:https://realtimecommunication.wordpress.com/2014/11/14/messaging-in-rcs/> [retrieved on 20220426]
ref_type: npl
severity: background
ref_id: - ANONYMOUS: "Session Description Protocol", WIKIPEDIA, 7 October 2018 (2018-10-07), XP055915411, Retrieved from the Internet <URL:https://en.wikipedia.org/w/index.php?title=Session_Description_Protocol&oldid=862918265> [retrieved on 20220426]
ref_type: npl
severity: background
ref_id: US2013066624
ref_type: patent
severity: novelty_destroying
ref_id: - Anonymous, "Rich Communication Services - Wikipedia", (20190317), URL: https://en.wikipedia.org/w/index.php?title=Rich_Communication_Services&oldid=888142729, (20200824), XP055724643 [T] 1-15 * the whole document *
ref_type: npl
severity: background
ref_id: - Anonymous, "Rich Communication Suite 8.0 Advanced Communications Services and Client Specification - Version 9.0", (20180516), URL: https://dev.maaprcs.com/docs/public/spec/RCC.07-v9.0.pdf, (20200825), XP055725027 [T] 1-15 * pages  1-6; figures 2, 4, 6 *
ref_type: npl
severity: background
Final disposition: pending (2020-10-14)