![](bg6.png)
components and reside in their own container
(CORBA components, CCM). The web service im-
plementation delegates CORBA related tasks to a
proxy component which authenticates the service at
the Parlay Framework and mediates between the
web service and the basic CORBA service (call
setup in this case). In addition, the proxy object can
handle connections to different Frameworks inside
or outside the web services domain.
The Click2Call (C2C) application uses the so-
called 3
rd
Parlay X 3
rd
Party Call Service and takes
advantage of the proposed profiling system.
The Click2Call application could be incorpo-
rated into a real-estate purchase/rent web site. The
end user browses the site, views photos and reads
description of some houses and if he is interested he
pushes the button to activate the C2C application
and connect to an estate broker for discussing further
details.
The service subscription process is expected to
be done offline and is not discussed here. At service
subscription, the user is assigned a service and user
profiles by the WSRTE administration tool. Follow-
ing a request, the service access rights are checked
by the web services platform. Which security
mechanism should be applied for the client-service
communication is a part of the service contract.
The user logs in from the welcome page. For a
call we need two addresses – of the caller and the
callee. In our case, the own address is stored in the
User Profile and is looked up by the service with the
help of WSRTE after the authentication process.
Moreover, the service can perform an authorization
check for the called user by looking up the Service-
User Profile for this user, and for example, deny
international calls in the PSTN. The System Profile
in this example contains the address of the Naming
Service which leads to the address of the underlying
FW Proxy component. Therefore, one could move
the underlying network level service infrastructure,
modify an entry in System Profile for the Parlay X
3
rd
Party Call Service and continue using the latter
without having to restart the web services platform
or re-deploy the Parlay X service.
4 CONCLUSIONS AND FURTHER
RESEARCH
We have shown in this work how one can extend an
existing web service platform to support profiling
for users and services. We discussed as well archi-
tectural considerations for embedding the web ser-
vice layer in a telecom service infrastructure.
When working with the prototype, we found out
that parts of the profiles (System Profiles) are used
simply to find and access other services. In the fu-
ture, service discovery, service inter-working (ag-
gregation, orchestration) and reconfiguration is go-
ing to play a major role and should be done dynami-
cally. One way to do it, is to perform the interaction
between web services via connection proxies, which
would be dynamically configured by a connection
manager. Connection reconfiguration and service
discovery would be transparent to the web service.
REFERENCES
Alonso, G., et al., 2004. Web Services. Concepts, Architec-
tures and Applications. Springer-Verlag Berlin Hei-
delberg.
Apache Software Foundation, 2004. Apache web services
project Axis, http://ws.apache.org/axis/index.html
ETSI ES 202 915-3, 2003. Parlay/OSA Framework API,
http://www.parlay.org
IBM Corp., Microsoft Corp., 2002. Security in a Web
Services World: A proposed Architecture and Road-
map, http://www-
106.ibm.com/developerworks/webservices/library/ws-
secmap/
Manes, A., T., 2003. Web Services. A Manager’s guide.
Addison-Wesley
Newcomer, E., 2004. Context, Coordinators, and Transac-
tions – The Importance of WS-CAF,
http://www.webservices.org/index.php/article/view/12
97/
OASIS Standard 200401, 2004. Web Services Security;
SOAP Message Security 1.0, http://docs.oasis-
open.org/wss/2004/01/oasis-200401-wss-soap-
message-security-1.0
O’Neill, M., et al., 2003. Web Services Security. McGraw-
Hill/Osborne
Parlay X Working Group, 2003. Parlay-X Web Services
Specification, http://www.parlay.org/specs/index.asp
PC Magazine, October 2002. Securing Web Services,
Systinet Corp., 2004. WASP Server for Java,
http://www.systinet.com/doc/wasp_jserver/
3GPP TS 23.240, 2003. Generic User Profile (GUP) re-
quirements; Architecture.
Figure 5: Telecom service collaboration dia
ra
.
F/W
F/W
Client Users
Middleware
Parlay Gateway
WebService:
P/X
3
rd
party
call
SCS
other…
Generic
Call
Control
Service
CCM
F/W
proxy
call
setup
WASP
CORBA
Name service
UDDI
Tomcat/AXIS
click2call.jsp
.NET
click2call.exe
click2call.aspx
WASP client
com-
ponents
click2call.jar
ICETE 2004 - GLOBAL COMMUNICATION INFORMATION SYSTEMS AND SERVICES
256