Browse Prior Art Database

Social relationship based caller/sender information shown on Mobile/VoIP or Messaging Terminals

IP.com Disclosure Number: IPCOM000233959D
Publication Date: 2014-Jan-06
Document File: 8 page(s) / 186K

Publishing Venue

The IP.com Prior Art Database

Abstract

This article introduces a trust relay based social relationship usage to identify incoming calls or messages; Using community membership or direct social content relationship to identify incoming calls or messages are also introduced in this article.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 53% of the total text.

Page 01 of 8

Social relationship based caller

Social relationship based caller/

//sender information shown on Mobile

sender information shown on Mobile

sender information shown on Mobile/

//VoIP or Messaging Terminals VoIP or Messaging Terminals

When people receives a call/message from someone whose name and number are not in the callee/receiver's contact list, then only the caller/sender's phone number or ID
will be shown to the callee/receiver, and some times, these kind of calls/messages are advertisements, and it's very time consuming and wasting of money for the callee. There are inventions like

US 20120196581 A1

that mentions using social graph to identify the caller;

There are also inventions like

EP 2426900 A1

                                 talking about searches
for the social media page of the caller based on the callerID and display it to the recipient of the call on the mobile station screen .

This article introduces 3 enhanced approaches to use social relationship or social contents for caller/sender identification.


1. Trust relay based social relationship to identify the caller/sender
As show in below diagram, the callee/receiver can define the depth of the trusts that she/he believes in, everyone in the social path call also configures to enable
or disable trust relay for others. e.g, If the callee/receiver defines the trusted relationship depth to be 3, then all callers/senders with more than 3 relays to
reach the callee/receiver will be regarded as anonymous; If a user in the social path doesn't want to relay trust for the user in front of him/her in the
social path, then this found social path is broken and can not be used to identify the caller/sender.

1



Page 02 of 8

2



Page 03 of 8

A sample implementation of the social relationship trust relay system as below:

3



Page 04 of 8

4



Page 05 of 8

On the social server


(1) The DB stores the users' social relationship (friends or buddies list) including name, phone number(or VoIP/IM ID) and so on.


(2) the server call also query the social path on behave of the user via 3rd party social severs.


(3) Every person can configure to enable the trust-Relay for other or not, e.g, even if person 2 is buddy of both person 1 and person 3, but if person 2 doesn't enable the trust-relay for others, then person 3 can not reach person 1 via person 2, the trust-relay can be configured as per-person or group based.


(4) The social path service on the social server or3rd party servers can return the shortest one or several social paths that no deeper than n;

On the mobile(or any Message/VoIP Terminal)


(1) When the mobile receives a call/message, If the caller/sender is not in the callee/receiver's contact list or local social path cache, the caller/sender and...