You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
112<br />
X:User<br />
1:Device<br />
2:Device<br />
3:Device<br />
Figure 9 Initiating service<br />
from an IP-based device<br />
ISUP<br />
PSTN/ISDN<br />
Gateway<br />
ISUP<br />
Gateway<br />
Gateway<br />
Mobile Network<br />
In order to realise the Use Case Initiating Service<br />
the following conditions must be met:<br />
• Every object Virtual Terminal must have an<br />
identity that is visible to all devices, i.e. it<br />
should be possible to address the Virtual Terminal<br />
from any device. Each Virtual Terminal<br />
may have several identifiers:<br />
- An MSISDN number (telephone number);<br />
- An email address;<br />
SIP/H323<br />
IP-based<br />
Network<br />
A:Service<br />
X:Virtual<br />
Terminal<br />
- Some kind of unique identifiers conformed<br />
to OSA/Parlay [7,8].<br />
If the Virtual Terminal has several identifiers,<br />
a mapping between these identifiers is required.<br />
• It should be possible to establish a connection<br />
from any device to the Virtual Terminal and a<br />
connection from the Virtual Terminal to any<br />
service or any other device. The Virtual Terminal<br />
must be capable of acting as a connector<br />
that connects the streams together.<br />
The user may have different devices connected<br />
to different networks. One device can be an IP<br />
phone or a PC directly connected to an IP-based<br />
network, another device can be a fixed phone or<br />
cordless phone connected to the PSTN/ISDN<br />
network, and a third device can be a cellular<br />
phone connected to a mobile network such as<br />
GSM.<br />
The protocols used to establish and terminate a<br />
connection vary for different networks. For IPbased<br />
networks either SIP [9] or H323 [10] protocols<br />
should be used but for PSTN/ISDN and<br />
mobile networks, the protocol is SS7 ISUP.<br />
When the user initiates a service from a chosen<br />
device a connection must be established from<br />
this device to the Virtual Terminal. Different<br />
protocols should therefore be used depending on<br />
the type of device, i.e. IP-based device contra<br />
PSTN/ISDN or mobile device.<br />
Let us consider these two device types successively.<br />
6.1.1 Initiating Services from an<br />
IP-based Device<br />
If the user uses a device that is connected to an<br />
IP-based network, either SIP or H323 protocol<br />
is used for signalling. In addition, information<br />
on the requested service or device must be conveyed<br />
to the Virtual Terminal so that it knows<br />
which service or device to connect to. This case<br />
is illustrated in Figure 9.<br />
Two implementation alternatives are identified:<br />
Alternative 1:<br />
• Use SIP/H323 for establishment of connections.<br />
• Use CORBA/Java RMI for control and information<br />
exchange with the Virtual Terminal<br />
[11,12].<br />
Alternative 2:<br />
• Use OSA/Parlay API for establishment of<br />
connections.<br />
• Use CORBA/Java RMI for control and information<br />
exchange with the Virtual Terminal.<br />
The most straightforward implementation will<br />
be to incorporate either SIP or H323 in the Virtual<br />
Terminal. However, such a solution does<br />
not imply portability since the code of the Virtual<br />
Terminal needs to be changed for each protocol.<br />
A better solution might be to use OSA/Parlay<br />
API since a generic and network independent<br />
Call control API is offered. Portability is hence<br />
ensured and the Virtual Terminal will function<br />
on either SIP or H323.<br />
6.1.2 Initiating Services from PSTN/ISDN<br />
or Mobile Devices<br />
If the user uses either a device connected to the<br />
PSTN/ISDN network or a device connected to a<br />
mobile network such as GSM, the SS7 ISUP is<br />
used to establish connection.<br />
Assume that a user wants to make a telephone<br />
call to another phone. He dials the number of the<br />
addressed phone. The signalling must somehow<br />
be routed to the Virtual Terminal, and there is a<br />
need for an IN service, which sends the signalling<br />
to the Virtual Terminal. This IN service<br />
Telektronikk 1.2001