Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
X:User<br />
6.5.1 Accessing Profile<br />
Each user has a profile where he may store all<br />
his set up and preferences. The profile may<br />
incorporate things like bookmarks, address list<br />
and also items that the user uses frequently. At<br />
this stage it has not been analysed what should<br />
be part of the user profile. However, it is important<br />
that the profile contains a list of all components<br />
of the Virtual Terminal, i.e. all the devices<br />
that the user has at his disposal. Such a list<br />
should contain both the device unique ID, e.g.<br />
MSISDN number, IP address, etc., and also the<br />
device type, e.g. GSM phone, SAT (SIM Application<br />
Toolkit) phone, WAP phone, PDA, PC,<br />
TV, etc.<br />
The profile might also contain a list of possible<br />
mailboxes to where incoming messages can be<br />
sent. The user should be able to choose what<br />
kind of mailboxes he wants in this list and which<br />
mailbox to use at any given time. The user’s personal<br />
address book should also be placed in the<br />
Virtual Terminal so that he can reach it from any<br />
device he might be using.<br />
Another important issue is that the profile should<br />
be easily accessible to the user. The user should<br />
have the possibility to access his profile from<br />
any Web browser and any WAP phone and to<br />
change elements in it if desired. It is therefore<br />
necessary to have sufficiently strong authentication<br />
and access control to prevent fraudulent<br />
access to the user profile. This use case and also<br />
the other three use cases will hence use the use<br />
case Authentication & Access Control. The Virtual<br />
Terminal should also have access to a certain<br />
database in order to read and write the user<br />
profile.<br />
Telektronikk 1.2001<br />
1:Device<br />
2:Device<br />
3:Device<br />
PSTN/ISDN<br />
Gateway<br />
Gateway<br />
WAP GW<br />
Mobile Network<br />
User<br />
Profile<br />
IP-based<br />
Network<br />
WAP/Web<br />
server<br />
X:Virtual<br />
Terminal<br />
As shown in Figure 23, the Virtual Terminal<br />
should reside on a Web/WAP server or alternatively<br />
reside on a separate application server but<br />
accessible from the Web/WAP server. There are<br />
several commercial application server products<br />
available such as Bea Weblogic, Cold Fusion,<br />
NetDynamics, Netscape Application Server, etc.<br />
The evaluation and selection of appropriate application<br />
server, however, are out of the scope of<br />
this article.<br />
The Web/WAP can be a standard public domain<br />
Web server such as Apache, a W3C XML (Extended<br />
Markup Language) bean server such as<br />
Bea Logic (Weblogic). Depending on whether<br />
the terminal has a Web browser or a WAP<br />
browser HTML (Hypertext Markup Language)<br />
or WML (<strong>Wireless</strong> Markup Language) will be<br />
generated from XML.<br />
6.5.2 Defining and Deleting Devices<br />
All the devices that the user has at his disposal<br />
and may use in a specific situation must be<br />
defined in his profile so that the Virtual Terminal<br />
knows how to handle them. Such a definition<br />
can be done manually and the user must then<br />
update the list of defined devices contained in<br />
the Virtual Terminal with all necessary information<br />
about the new device to be defined. Deleting<br />
an already defined device manually is naturally<br />
a much easier task. New devices can also<br />
be defined in the Virtual Terminal automatically<br />
when they are discovered by some service discovery<br />
protocols that detect all necessary information,<br />
but to define too many devices automatically<br />
might result in a long list of devices that<br />
are hardly ever used. A better approach could be<br />
to let all necessary information about new devices<br />
be detected automatically, and to simply<br />
Figure 23 Profile access from<br />
WAP/Web<br />
123