GB2488332A - A social networking website is used as a proxy terminal to allow linked members contact each other via SMS/telephone without exchanging numbers. - Google Patents

A social networking website is used as a proxy terminal to allow linked members contact each other via SMS/telephone without exchanging numbers. Download PDF

Info

Publication number
GB2488332A
GB2488332A GB1103077.2A GB201103077A GB2488332A GB 2488332 A GB2488332 A GB 2488332A GB 201103077 A GB201103077 A GB 201103077A GB 2488332 A GB2488332 A GB 2488332A
Authority
GB
United Kingdom
Prior art keywords
sms
user
mms
requests
requestor
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Withdrawn
Application number
GB1103077.2A
Other versions
GB201103077D0 (en
Inventor
Christopher William Smith
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Individual
Original Assignee
Individual
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Individual filed Critical Individual
Priority to GB1103077.2A priority Critical patent/GB2488332A/en
Publication of GB201103077D0 publication Critical patent/GB201103077D0/en
Publication of GB2488332A publication Critical patent/GB2488332A/en
Withdrawn legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q90/00—Systems or methods specially adapted for administrative, commercial, financial, managerial or supervisory purposes, not involving significant data processing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/52—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail for supporting social networking services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/58—Message adaptation for wireless communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • H04L63/101—Access control lists [ACL]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/2866—Architectures; Arrangements
    • H04L67/30—Profiles
    • H04L67/306—User profiles
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/42008—Systems for anonymous communication between parties, e.g. by use of disposal contact identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/02—Protecting privacy or anonymity, e.g. protecting personally identifiable information [PII]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements
    • H04W4/14—Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Business, Economics & Management (AREA)
  • Computer Security & Cryptography (AREA)
  • Physics & Mathematics (AREA)
  • Economics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Computing Systems (AREA)
  • Computer Hardware Design (AREA)
  • General Engineering & Computer Science (AREA)
  • Telephonic Communication Services (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

A method and system for authenticated communication through website in which the communicating parties do not exchange contact details. Website users create a list of user IDs from whom they agree to accept communications, i.e. a friends list, and also register their telephone number, which acts as a verification of the userâ s identification. Subsequently, communication messages, which may be SMS, MMS, or other electronic communications, are sent to the website which acts as a proxy in relaying the communication only if the sender and receiver are verified and listed as known contacts, associates or friends.

Description

DESCRIPTION:
1 Purpose and field of the invention
It is not uncommon for users of dating websites or gaming sites such as poker rooms' to participate anonymously, forming relationships and conducting friendships through messages and chat exchanged under a strict alias. If two Users wish to talk to one another anonymously they can set up a V0IP account under their respective aliases but, unless at least one of them is prepared to exchange a personal phone number, the opportunity to SMS/MMS will be restricted to when both parties happen to be logged on to the site.
Anecdotal evidence suggests that website users who participate under a bona fide name may be as reluctant to exchange phone numbers as those who use a cognomen. The growth of internet telephony as a usable communication medium is thus inhibited by its remaining tied to the sometimes on' mode of the website; conventional offline' telephony usage on the other hand has reached an unprecedented level of importance in our lives owing to our mobile phones' being always with us, and always on'.
The ability to access our website friends' mobile phones at all times and to grant them access to our own in turn without the need to divulge our phone numbers would be a welcome innovation; and it would be a further advantage, indeed for many website users a sine qua non of adoption, if the status of phone friend' were, in line with other privileges of online friendship', not transferable to third parties but obtainable only by direct invitation.
2 Statement of the invention
Accordingly, a system and method is disclosed for the screening and forwarding of call requests placed between Users of communities' such as dating and social networking sites whereby: * The telephonic identifier for a User's personal telephone is not the associated network termination number but the Unique User ID, ie the name by which the User is known to fellow Users of the website or community' * Requests for to send a SMS/MMS to a fellow User's handset are automatically screened, and only those verified as placed by expressly authorised' users are forwarded for transmission.
* SMS/MMS are not routed by default to or from the device from which a call request is made, eg the User's laptop, but to a telephone number which the User registers with the website -or other such means such as a SMS granting permission * Authorisation' is physically non-transferable and can be granted and withdrawn at any time.
3 System apparatus The invention exploits the infrastructure of the social networking website: the User database, Users' stored personal preferences and settings, their Contact or Friends' Lists, their available/unavailable status, and so on.
The system apparatus is shown in Figure 1. Here the Website's Graphical User Interface (GUT) is shown here as separate from the user's mobile handset; but the GUI might equally well be hosted by the mobile device.
Also shown is the back end infrastructure comprising a networked database where (a) a directory of User IDs and (b) those Users' personal preferences and settings data are stored. Figure 1 shows the two categories of data stored on dedicated databases; there is no intrinsic need to separate them. A parser for interpreting the content of messages sent in alternative formats, is also shown.
We also see the networked Dialler, which communicates with the databases. In practice this would be a multi-functional telephony platform, such as a server running the Asterisk platform, and capable of queuing, logging, sending SMS/MMS, dialling, recording calls, of sending and receiving DTMF tones, and more besides.
Closer attention to detail is unnecessary here: online social networks need no reinventing. With the exception of the Telephony Platform none of this apparatus would need to be expressly acquired by a website owner: for that matter it might for many reasons be desirable to have the Telephony functionality outsourced to a dedicated operation.
4 Setting up a User Account Website users create an ad hoc Contact List' of User IDs from whom they agree to accept SMS/MMS; they also need to register a telephone number to a secure database, for example a mobile CLI.
DESCRIPTION
Registering a personal telephone number serves a dual purpose: 1. The invention requires the User to supply a Contact Number for at least one such device 2. The number is a signature' on SMS Requests and may serve to verify the Requestor's ID It being far beyond the powers of the vast majority of website users to counterfeit or spoof' the Sender ID component of an SMS message the sender's phone number may be taken, for the purposes of an application of this type at any rate, as adequate proof of User identity.
S Requesting a call For the purposes of this description the process of requesting and being granted a SMS/MMS connection according to the system and method disclosed will be known as paging'.
We will now suppose that two Users, with User IDs User A' and User Z', have set up paging' accounts on some common website. How does User A page' User Z? In one embodiment of the invention the website publishes a SMS code, which may be a free, a standard rate-or a premium rate number. When User A wishes to page User Z, User A sends the SMS/MMS message he wishes user Z to receive prefixed by "@UserZ" to this SMS code from the phone number which User A has registered on the website, for example "@userZ great to meet you yesterday". The message received by the website via the telephone network will comprise two elements: 1. The body of the message, the destination identifier "User Z" 2. The SMS sender's implicit CLI or Sender ID: the message signature' 6 Screening the Request The condition of a Request's being submitted for execution by the system is that the Requestor be a registered Phone Friend' of the Requested Party.
The steps required to screen the SMS/MMS request, ie to establish whether the Requestor is listed on the Requested Party's Contact List, are shown in the Flow Chart of Figure 2.
It will be remembered that in our example User A sends the message beginning with "@UserZ" to the website's SI'IS code and that the System is thus in possession of two identifiers: the Requestor's Sender ID or mobile CLI, and the Requested Party's Unique User ID.
If the Sender ID is registered as the Contact Number of a registered User the corresponding Unique User ID will be discoverable by a reverse look-up in the database of registered Contact Numbers.
We will assume that in this case the system successfully retrieves the match User A' for the Sender ID. It must now be established whether User A is authorised to page' User Z. If a search of User Z's Contact List fails to yield the item "User A" the request will be discarded and no further action need be taken: the Request is deemed valid if and only if the User ID "User A" is found to match a name on User Z's Contact List, in which case, and only in which case, User Z's personal Contact Number is looked up and the SMS/MMS forwarded along with User A's identifier for transmission. UserZ will receive the SMS/MMS prefixed with User A's sender ID. Eg @UserA great to meet you yesterday.
7 Requests made via other media There is no need to limit Users to placing paging Requests by the medium of SMS. Any messaging system capable of expressing the identifier "User X" would serve the purpose defined in Section 6, provided the message embodied some readable implicit signature'.
Requests sent direct from the website that hosts the community' would embody a signature known as a cookie' which would serve precisely the same purpose as the Sender ID of the previous example.
Any messaging system that embodies a signature difficult for the non-expert user to conterfeit would be acceptable to the majority of users; and if a User should have any objection to any particular messaging system it would be easy to incorporate an opt-out into the Preferences' menu, and to introduce a further step of checking the Request medium against Users' preferences into the screening process.
DESCRIPTION
8 Sending the SMS/MMS The screening process complete, the Telephony Server may now attempt to transmit the SMS/MMS between the two parties.
1. The receiver forwards two identifiers to a Telephony Platform: the Requestor's (origin identifier') and the Requested Party's (destination identifier').
2. The platform transmits the SMS/MMS to the destination identifier This is by no means the only method envisaged. The necessary step of screening Requestor's telephonic signature' could be performed equally well if the Requestor dialled the Telephony Platform as the initial step and subsequently specified the Requested Party's telephonic identifier by means of DTMF tone input. However, a discussion of the relative benefits of various call connection methods would not be relevant to the description of an invention whose function is not to connect, but rather to deny connections.
9 Request management Any SMS/MMS that for whatever reason were not delivered to the Requested Party sit pending in a sort of In/Outbox', awaiting a convenient time for resubmission.
It is likely that Users would wish to have the option of switching off' from time to time, ie making themselves unavailable for paged' SMS/MMS; also, that Users might wish to be able to delete pending MMS/SMS, particularly if the website makes a charge for fulfilled Requests, or to postpone their execution.
A further option might be to group broadcast a SMS/MMS, the ability to send a SMS/MMS to more than one party, and the ability to add an additional party to a pending message transmission.
Payment for the service For Requests posted by SMS there are three established billing mechanisms: a credit account, whereby credit is purchased to use the service and deducted at the agreed rate per message, a premium rate SMS code, and a premium rate reverse billed' SMS code.
S
KEY TO FIG 1 lOa, lOb Application GUI ha, lib User's personal telephone 12 Stored User IDs 13 Database of Users' Contact List, Settings and Status 14 Telephony Server with SMS/MMS, IVR, dialling and queuing capability Parse *SSI.I * S
S
* es see * S S. Se * S S
S S Sb * SeC

Claims (4)

  1. Claims 1 A System comprising (A) a User network, for example a Social Networking website, comprising -at least one memory for storing a plurality of Unique User IDs, along with the associated personal data -at least one GUI for uploading and updating personal data and settings to the memory and managing call requests pending on a Telephony Platform.
    -at least one message receiver/parser if updates and requests are to be received from sources other than the website GUI -at least one update receiver for updating User data wherever in the system it may be stored, whether in a single or a plurality of locations (B) at least one Telephony Platform for setting up SMS/MMS between registered Users, whose capabilities might include, but need not be restricted to, the following: i. simulaneously SMS/MMS a plurality of terminations ii. bridging a plurality of connections into a single conference line' iii. playing voice messages iv. parsing DTMF tones v. speech recognition vi. outbound SMS/MMS queueing vii. receiving SMS/MMS viii. forwarding SMS/MMS logs ix. interfaCing with a billing module x. ignoring duplicate requests xi. interfacing with an online or offline application GUI
  2. 2 A method of screening SMS/MMS requests between Users of the system, the Requestor' and the Requested Party', whereby for each such User there is associated (a) some Unique User ID, which may be a true name or an alias, as well as (b) the contact number of at least one personal device such as a cell phone, as well as (c) a personal Contact List' of fellow Users authorised to initiate voice calls with said User; and whereby the information embodied in a Request' submitted to the system consists of two identifiers: (1) the Requested Party's Unique User ID, this being the explicit content of the message, and (2), an identifiable signature' implicit in the SMS/MMS and uniquely associated with the Requestor such as a website cookie, or a username, or the characteristic sound of the Requestor's voice; and whereby only such Requests as are verified by the system as originating from an authorised User, ie from a User currently listed on the Requested Party's Contact List, being deemed valid, are forwarded to the Telephony Platform for execution.
  3. 3 The system and method according to Claims 1-2 whereby the system screens a Request by executing some sequence of the following steps: (i) the Requestor's signature' or Sender ID is submitted to a database for comparison with those of the system's known Users; (ii) the Requestor's Contact Number is looked up in the database of Users' personal data; (iii) the Requestor's Unique User ID and/or Contact Number are matched against the Requested Party's or Parties' Contact Lists; (iv) the Requested Party or Parties' Contact Number or Numbers are looked up in a database of Users' personal data; and whereby failure to identify a positive match for one or more of these steps results in the Request's being deemed invalid, and its execution withheld; and whereby, if and only if the Request is validated, the Contact numbers of the associated Parties are forwarded to the Telephony Server for the forwarding of the content of the SMS/MMS.
  4. 4 The system and method according to Claims 1-3 whereby Requests as well as data and settings updates may be submitted by one or more of the following means: i. entering the Requested Party's Unique User ID into a website GUI field ii. activating a GUI field such as an icon or an item on a pull-down menu iii. submitting an SMS/MMS with the Requested Party's User ID in the body of the message iv. activating a field on a hand held device application such as an iPhone app v. issuing a spoken voice command or a DTMF tone command to an IVR platform vi. issuing a spoken voice command or a DTMF tone command in the course of a SMS/MMS connection set up by the System, said command being intercepted and executed by the Telephony Platform S The system and method according to Claims 1-4 whereby the User may opt out of Requests submitted by means of one or more of the messaging media the website makes available, eg because the User may not trust the security of allowing Requestors to confirm their identity by means of a DTMF password; and whereby the system performs the additional screening step of matching the Request's messaging medium against Users' stored preferences.6 The system and method according to Claims 1-5 whereby a validated request, for example one placed by a User via the System's website GUI, causes the Telephony Platform to establish a SMS/MMS connection between the SMS/MMS Requestor's and the Requested Party's or Parties' respective registered telephonic devices.7 The system according to claims 1-6 where valid Requests that initiallyfail to result in establishing a connection between the Requestor and at least one Requested Party in person are deemed pending and submitted to the User's Website GUI for management by the User; and where this management functionality might include, but need not be limited to, deleting or rescheduling or deferring of pending SMS/MMS.9 The system according to Claims 1-7 whereby the User may issue an instruction over the website GUI or send a message instructing -subject to authentication in the latter case -the System either to hold until further notice or to re-activate said User's inbound and outbound Requests, whereby held Requests are deemed pending according to the method described in Claim 7 and treated accordingly.The system according to Claims 1-9 whereby payment for SMS/MMS connections is made by means of a Request made to a premium rate SMS code or, regulatory conditions permitting, whereby the Request SMS or SMS (plural) act as an opt-in message for a reverse billing' agreement, this being a payment mechanism familiar to those skilled in the Art.11 The system and method according to Claims 1-10 whereby submitting a Request via a UI such as a mobile application GUI causes the host device to generate, in addition to the characteristic output and subject to the User's implicit or explicit consent, an SMS sent to a pre-defined SMS code, or a SMS/MMS to a pre-defined premium rate telephone number, and thus to incur on the part of the Requestor a charge for the requested transmission, this step being executable before, during or after the Request has been fulfilled; alternatively, regulatory conditions permitting, whereby the SMS message thereby generated is an optin message for a reverse billing agreement.12 The system according to Claims 1-11 whereby the number of SMS/MMS transmitted between Requestor and Requested Party is limited to a maximum of eg 3 SMS/MMS per one hour, or 3 SMS/MMS within any 24 hour period, whereby SMS/MMS are held pending after expiry of the maximum period, and Requests whose fulfilment would exceed said maximum are automatically rescheduled for the next permissible' time.13 The system and method according to Claims 1-6 whereby the Requestor establishes a SMS/MMS connection by SMS/MMS'ing the Requested Party via the System Telephony Platform's published contact number; whereby the Telephony Platform, here in effect a Proxy Telephony Platform for the Requestor, captures the Requestor's Contact Number from the incoming Caller ID and is given the identifier for Requested Party by means of an associated DTMF or spoken command issued by the Requestor; or where a unique telephone number is assigned to each Unique User ID, and where all such numbers are routed to the Telephony Platform's termination, and the Requested Party's User ID indentified from the dialled number; and whereby only such requests as are verified by the system as originating from an authorised User, ie a User currently listed on the Requested Party's Contact List, are deemed valid; and whereby all Requests for a voice connection deemed invalid are denied.14 The system and method according to Claims 1-13 whereby all Requests found to originate from known or registered Users of the network are deemed authorised and forwarded to the Telephony Platform for connection.The system and method according to Claims 1-13 whereby all Requests received, whether from known Users or not, are deemed valid and forwarded to the Telephony Platform for connection.
GB1103077.2A 2011-02-23 2011-02-23 A social networking website is used as a proxy terminal to allow linked members contact each other via SMS/telephone without exchanging numbers. Withdrawn GB2488332A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
GB1103077.2A GB2488332A (en) 2011-02-23 2011-02-23 A social networking website is used as a proxy terminal to allow linked members contact each other via SMS/telephone without exchanging numbers.

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
GB1103077.2A GB2488332A (en) 2011-02-23 2011-02-23 A social networking website is used as a proxy terminal to allow linked members contact each other via SMS/telephone without exchanging numbers.

Publications (2)

Publication Number Publication Date
GB201103077D0 GB201103077D0 (en) 2011-04-06
GB2488332A true GB2488332A (en) 2012-08-29

Family

ID=43881517

Family Applications (1)

Application Number Title Priority Date Filing Date
GB1103077.2A Withdrawn GB2488332A (en) 2011-02-23 2011-02-23 A social networking website is used as a proxy terminal to allow linked members contact each other via SMS/telephone without exchanging numbers.

Country Status (1)

Country Link
GB (1) GB2488332A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017039799A1 (en) * 2015-08-31 2017-03-09 Linkedin Corporation Proxy email server for routing messages

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
Binary Head, How to send SMS via Facebook [on-line], available 7/10/2008, Binary head website/forum. *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017039799A1 (en) * 2015-08-31 2017-03-09 Linkedin Corporation Proxy email server for routing messages
US10122663B2 (en) 2015-08-31 2018-11-06 Microsoft Technology Licensing, Llc Proxy email server for routing messages
US10645049B2 (en) 2015-08-31 2020-05-05 Microsoft Technology Licensing, Llc Proxy email server for routing messages

Also Published As

Publication number Publication date
GB201103077D0 (en) 2011-04-06

Similar Documents

Publication Publication Date Title
US10244105B2 (en) Methods and systems for real time display of caller location, profile, and trust relationship
JP5847579B2 (en) Method and system for a user to access at least one service provided by at least one other user
CN103493465B (en) Authorized user participates in the meeting of carrying out by communication network
US8195137B2 (en) Updating contact information for mobile traffic
US8639225B2 (en) E-mail to phone number resolution for mobile to mobile, mobile to landline, and PC to mobile communications
US20060121880A1 (en) Method and apparatus for enabling authorized and billable message transmission between multiple communications environments
JP2016518662A (en) Method and apparatus for authorization authentication
EP1956817A1 (en) Method and system for establishing a telephone connection
RU2721825C2 (en) System and method of establishing communication over multiple communication platforms
WO2017148146A1 (en) Method and device for preventing nuisance calls
JP2006295673A (en) Call system, proxy dial server device, proxy dial method used therefor, and program thereof
US20200220837A1 (en) System and method to use a mobile number in conjunction with a non-telephony internet connected device
EP2761847B1 (en) Method and system for managing the communication between two users
KR20130082561A (en) Apparatus and method for inviting subscription of contact information
US11196700B1 (en) Single-user non-transferrable communication client for public communication networks
US20070254637A1 (en) Device, Method and Computer Program Product Readable Medium for Establishing a Communication Session
US20100303060A1 (en) Second call mode call set-up between two users
KR101474144B1 (en) Method for Telephony Authentication by using One Time Recipient Number
GB2488332A (en) A social networking website is used as a proxy terminal to allow linked members contact each other via SMS/telephone without exchanging numbers.
CN110933016B (en) Login authentication method and device for call center system
TW201304495A (en) System and method for displaying an identifier of a source on a recipient device
KR20090061432A (en) Service system and method of presentation of a caller
GB2478589A (en) Screening call requests for anonymous communication between members of a community
KR101722414B1 (en) Enriched presence status
RU2626339C2 (en) Method of communication, communication server and communication system with their use

Legal Events

Date Code Title Description
WAP Application withdrawn, taken to be withdrawn or refused ** after publication under section 16(1)