System and method for enabling communication between a rich communication service system and a non-rich communication service system

Patent metadata

Field	Value
Publication number	US-9678950-B2
Application number	US-201113697958-A
Country	US
Kind code	B2
Filing date	May 16, 2011
Priority date	May 14, 2010
Publication date	Jun 13, 2017
Grant date	Jun 13, 2017

Abstract

System and method for enabling communication between a Rich Communication Service System and a non-Rich Communication Service system. Embodiments of the present invention disclose a translation feature to enhance the communication experience between users of RCS and non-RCS systems by enabling users to communicate in their preferred language with the RCS taking care of language translation.

First claim

The invention claimed is:

1. A method for translating a message sent from a first user in a rich communication service (RCS) to a second user in a non-RCS, the method comprising the steps of:
identifying a language of the message received from the first user at a server in the RCS;
storing the identified language into a language history table with an entry of the first user;
identifying whether a preferred language of the second user is present in the language history table;
obtaining the preferred language from the language history table, when the preferred language is present in the language history table;
obtaining the preferred language from a language history of the second user and storing the preferred language in the language history table with an entry of the second user, when the preferred language is not present in the language history table; and
translating the message into the preferred language at a translator,
wherein the language history of the second user is obtained by using at least one of an application programming interface (API) and a network to network interface (NNI).

2. The method, as claimed in claim 1 , wherein the message is at least one of:
an email;
a social networking message;
an instant messaging (IM) message;
a voice message; and
a video message.

3. The method, as claimed in claim 1 , wherein the language history table comprises fields for:
an identity of the first user;
a language used by the first user;
an identity of the second user; and
a preferred language of the second user.

4. The method, as claimed in claim 1 , wherein the second user is a group of users.

5. The method, as claimed in claim 4 , wherein the language history table comprises fields for:
an identity of the first user;
a language used by the first user;
an identity of the group of users; and
a preferred language of the group of users.

6. The method, as claimed in claim 1 , wherein identifying whether the preferred language of the second user is present in the language history table comprises:
determining whether instructions for translation are present in the message;
extracting the preferred language from the message.

7. The method, as claimed in claim 1 , wherein the server determines whether the identified language and the preferred language match, sends the message from the server to the second user when the identified language and the preferred language match, sends the message from the server to the translator when the identified language and the preferred language do not match and sends the message, the identified language and the preferred language to the translator.

8. The method, as claimed in claim 1 , wherein the server sends details of translation as metadata with the message to the second user.

9. A method for translating a message sent from a first user in a non-rich communication service (RCS) to a second user in an RCS, the method comprising the steps of:
identifying a language of the message received from the first user at a server of the RCS;
storing the identified language into a language history table with an entry of the first user;
identifying whether a preferred language of the second user is present in the language history table;
obtaining the preferred language from the language history table, when the preferred language is present in the language history table;
obtaining the preferred language from a language history of the second user and storing the preferred language into the language history table with an entry of the second user, when the preferred language is not present in the language history table; and
translating the message into the preferred language at a translator,
wherein the language history of the second user is obtained by using at least one of an application programming interface (API) and a network to network interface (NNI).

10. The method, as claimed in claim 9 , wherein the message is at least one of:
an email;
a social networking message;
an instant messaging (IM) message;
a voice message; and
a video message.

11. The method, as claimed in claim 9 , wherein the language history table comprises fields for:
an identity of the first user;
a language used by the first user;
an identity of the second user; and
a preferred language of the second user.

12. The method, as claimed in claim 9 , wherein the second user is a group of users.

13. The method, as claimed in claim 12 , wherein the language history table comprises fields for:
an identity of the first user;
a language used by the first user;
an identity of the group of users; and
a preferred language of the group of users.

14. The method, as claimed in claim 9 , wherein the server determines whether the identified language and the preferred language match, sends the message from the server to the second user when the identified language and the preferred language match, sends the message from the server to the translator when the identified language and the preferred language do not match and sends the message, the identified language and the preferred language to the translator.

15. The method, as claimed in claim 9 , wherein the server sends details of translation as metadata with the message to the second user.

16. A system for translating a message sent users in a rich communication service (RCS) and a non-RCS, the system comprising:
a server in the RCS for identifying a language of the message received from a first user, storing the identified language into a language history table with an entry of the first user, identifying whether a preferred language of a second user is present in the language history table, obtaining the preferred language from the language history table when the preferred language is present in the language history table, and obtaining the preferred language from a language history of the second user and storing the preferred language in the language history table with an entry of the second user when the preferred language is not present in the language history table; and
a translator for translating the message into the preferred language,
wherein the language history of the second user is obtained by using at least one of an application programming interface (API) and a network to network interface (NNI).

Assignees

• Pattan Basavaraj Jayawant
• Jeedigunta Venkateswar
• Samsung Electronics Co Ltd

Inventors

• Pattan Basavaraj Jayawant
• Jeedigunta Venkateswar

Classifications

• G06F40/58 Primary

  Use of machine translation, e.g. for multi-lingual retrieval, for server-side translation for client devices or for real-time translation · CPC title

• H04L51/063 Primary

  Content adaptation, e.g. replacement of unsuitable content · CPC title

• G06F3/167

  Audio in a user interface, e.g. using voice commands for navigating, audio feedback · CPC title

• H04W4/18

  Information format or content conversion, e.g. adaptation by the network of the transmitted or received information for the purpose of wireless delivery to users or terminals · CPC title

• H04W4/12

  Messaging; Mailboxes; Announcements · CPC title