Browse Prior Art Database

Presence-Enabled Directory Assistance

IP.com Disclosure Number: IPCOM000126096D
Published in the IP.com Journal: Volume 5 Issue 7A (2005-07-25)
Included in the Prior Art Database: 2005-Jul-25
Document File: 1 page(s) / 23K

Publishing Venue

Siemens

Related People

Juergen Carstens: CONTACT

Abstract

Today in telecommunication environment a subscriber calls another by directly requesting a communication link (phone call) to the called user equipment (mobile phone). This can be done directly by entering the (mobile) number or in a more comfortable way via the Voice Portal by just saying the name of the person (i.e. “John”). Directory Assistance is one of the most useful services provided by a Voice Portal, it allows a caller to reach a destination by simply pronouncing the name of the person he wants to reach. However, when the called subscriber is not available / reachable with the specific communication mean or at the specific access, the call will be terminated unanswered. Of course, the caller may go back to the Voice Portal and ask for a second call attempt at another communication access "owned" by the same person. This process is though time-consuming - and not particularly - user-friendly especially when the called person "owns" several different phone accesses (fixed / mobile, home / office). It is proposed to use Presence Servers in the Voice Portal Environment to store and retrieve information about the reachability of the subscribers. A new interface, e.g. SIP (Single Inline Package)-based, is proposed that is defined between a Voice Portal and a Presence Server. When a subscriber wants to establish a communication link to another subscriber by means of the Directory Assistance Service of a Voice Portal, the Voice Portal itself checks the presence information (being the "watcher") of the requested subscriber (i.e. "principal") and identify the communication address at which the subscriber is available. Assuming that the Voice Portal entity has the authority to subscribe to the presence information of the requested entity at the Presence Server, the Voice Portal acts as a "fetcher", i.e. it requests the current value of the presence information from the Presence Server, without requiring notification of future changes in it. As soon as the presence information is made available to the Voice Portal, the service VoiceXML page may question the subscriber (caller) if he wants to communicate with the specific means. This may involve content format adaptation, if a voice communication is not possible. The Voice Portal itself may facilitate the content format adaptation, as it is common to hold features such as speech-to-text conversion, etc. Finally, the call is transferred / transformed according to the called subscriber's intents.

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

Page 1 of 1

S

Presence-Enabled Directory Assistance

Idea: Dimitris Papadimitriou, GR-Athens

Today in telecommunication environment a subscriber calls another by directly requesting a communication link (phone call) to the called user equipment (mobile phone). This can be done directly by entering the (mobile) number or in a more comfortable way via the Voice Portal by just saying the name of the person (i.e. "John"). Directory Assistance is one of the most useful services provided by a Voice Portal, it allows a caller to reach a destination by simply pronouncing the name of the person he wants to reach. However, when the called subscriber is not available / reachable with the specific communication mean or at the specific access, the call will be terminated unanswered. Of course, the caller may go back to the Voice Portal and ask for a second call attempt at another communication access "owned" by the same person. This process is though time-consuming - and not particularly - user-friendly especially when the called person "owns" several different phone accesses (fixed / mobile, home / office).

It is proposed to use Presence Servers in the Voice Portal Environment to store and retrieve information about the reachability of the subscribers. A new interface, e.g. SIP (Single Inline Package)- based, is proposed that is defined between a Voice Portal and a Presence Server. When a subscriber wants to establish a communication link to another subscriber by means of the Directory Assistance Service of a Voice Portal, the Voice Portal itself checks the presence information (being the "watcher") of the requested subscriber (i.e. "principal") and identify the communication address at which the subscriber is available. Assuming that the Voice Portal entity has the authority to subscribe to the presence information of the requested entity at the Presence Server, the Voice Portal acts as a "fetcher", i.e. it requests the current value of the presence information from the Presence Server, without requiring notification of future changes in it. As soon as the presence information is made available to the Voice Portal, the service VoiceXML page may question the subscriber (caller) if he wants to communicate with the specific means. This may involve content format adaptation, if a voice communication is not possible. The Voice Portal itself may facilitate the content format adaptation, as it is common to hold features such a...