SYSTEM AND METHOD FOR ENABLING COMMUNICATION BETWEEN A RICH COMMUNICATION SERVICE SYSTEM AND A NON-RICH COMMUNICATION SERVICE SYSTEM

• US 20130066624A1
• Filed: 05/16/2011
• Published: 03/14/2013
• Est. Priority Date: 05/14/2010
• Status: Active Grant

• Current Assignee: Samsung Electronics Co. Ltd.
• Original Assignee: Samsung Electronics Co. Ltd.
• Inventors: Pattan, Basavaraj Jayawant, Jeedigunta, Venkateswar
• Granted Patent: US 9,678,950 B2
• Time in Patent Office: Days
• US Class Current: 704/2
• CPC Class Codes: G06F 40/58 Use of machine translation, e.g. for multi-lingual retrieval, for server-side translation for client devices or for real-time translation
• CPC Class Codes: H04L 51/063 Content adaptation, e.g. replacement of unsuitable content
• CPC Class Codes: H04M 2203/2061 Language aspects
• CPC Class Codes: H04M 3/533 Voice mail systems

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.

Claims

1. A method for translating a message sent from a first user in a Rich Communications 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;

entering the identified language into a language history table with an entry of the first user;

identifying a preferred language of the second user;

entering 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;

determining whether the identified language and the preferred language match;

sending the message from the server to the second user, when the identified language and the preferred language match;

sending the message from the server to a translator, when the identified language and the preferred language do not match;

translating the message into the preferred language at the translator;

sending the translated message from the translator to the server; and

sending the translated message to from the server the second user.

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 the preferred language of the second user comprises:

obtaining the preferred language from a one of a plurality of sources, when the preferred language is not present in the language history table.

7. The method, as claimed in claim 6, wherein the plurality of sources comprises:

a profile of the second user;

preferences of the second user;

a history of the second user;

an open Application Programming Interfaces (API); and

a Network to Network Interface (NNI).

8. The method, as claimed in claim 1, wherein identifying the preferred language of the second user comprises:

determining whether instructions for translation are present in the message;

extracting the preferred language from the message.

9. The method, as claimed in claim 1, wherein the server sends the message, the identified language and the preferred language to the translator.

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

11. A method for translating a message sent from a first user in a non-Rich Communications 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;

entering the identified language into a language history table with an entry of the first user;

identifying a preferred language of the second user;

entering 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;

determining whether the identified language and the preferred language match;

sending the message from the server to the second user, when the identified language and the preferred language match;

sending the message from the server to a translator, when the identified language and the preferred language do not match;

translating the message into the preferred language at the translator;

sending the translated message from the translator to the server; and

sending the translated message from the server to the second user.

12. The method, as claimed in claim 11, 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.

13. The method, as claimed in claim 11, 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.

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

15. The method, as claimed in claim 14, 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.

16. The method, as claimed in claim 11, wherein identifying the preferred language of the second user comprises:

obtaining the preferred language from one of a plurality of sources, when the preferred language is not present in the language history table.

17. The method, as claimed in claim 16, wherein the plurality of sources comprises:

a profile of the second user;

preferences of the second user; and

a history of the second user.

18. The method, as claimed in claim 11, wherein the server sends the message, the identified language and the preferred language to the translator.

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

20. A system for translating a message sent users in a Rich Communications 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, entering the identified language into a language history table with an entry of the first user, identifying a preferred language of a second user, entering 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, determining whether the identified language and the preferred language match, sending the message to the second user when the identified language and the preferred language match, and, when the identified language and the preferred language do not match, sending the message to a translator, receiving a translated message from the translator, and sending the translated message to the second user;

the translator for translating the message into the preferred language, and sending the translated message to the server.