END-TO-END IP

JAIN APIs for call control

and wireless networks
T
he JAIN APIs for Integrated • Wireless: Mobile Switching faces delivering truly portable
networks bring service porta- Centers (MSCs) applications
bility, convergence, and • Internet: emerging softswitches or • Network Convergence: (Integrated
secure network access to telephony call agents, and media gateway Networks) Any Network. By deliver-
and data networks. By providing a controllers or H.323 gatekeepers. ing the facility to allow applications
new level of abstraction and associat- and services to run on PSTN, packet
ed JAVA interfaces for service cre- A service layer (eg, IP or ATM) and wireless net-
ation across Public Switched • Telecommunication: Service works, JAIN technology speeds net-
Telephone Network (PSTN), Internet Control Points (SCPs) work convergence. As demand for
Protocol (IP) and wireless networks, • Wireless: any combination of Base services over IP rises, new
JAIN technology enables the integra- Station Controllers (BSCs), Home economies of scale are possible as
tion of Internet and Intelligent Location Registers (HLRs), Visitor well as more efficient management
Network (IN) protocols. This is Location Registers (VLR), and and greater integration with IT
referred to as Integrated Networks. MSCs • Secure Network Access: By
Since JAIN APIs include secure access • Internet: Application Server. Anyone! By enabling applications
to resources inside the network, the residing outside the network to
opportunity is created to deliver thou- The JAIN initiative directly access network resources
sands of services rather than the • Service Portability: Write Once, and devices to carry out specific
dozens currently available. Run Anywhere. Technology actions or functions, a new envi-
JAIN technology is changing the development is currently con- ronment is created for developers
telecommunications market from strained by proprietary interfaces. and users. The market opportunity
many proprietary closed systems to a This increases development cost, for new services is huge when con-
single network architecture where time to market, and maintenance trolled access is provided to the
services can be rapidly created and requirements. With the JAIN ini- available functionality and intelli-
deployed. JAIN technology is being tiative, proprietary interfaces are gence inside the telecommunica-
specified as a community extension reshaped to uniform Java inter- tions networks.
to the Java platform. Development is
Fig. 1 The JAIN APIs: an architectural overview
being carried out under the terms of
Sun’s Java Specification Participation
Agreement (JSPA) and the Java
Community Process (JCP).
The JAIN initiative is targeted
toward three major areas of the net-
work:

A network layer
• Telecommunications: (Advanced)
Intelligent Networks (AIN/IN) or
Signalling System 7 (SS7) focused
on ISUP, INAP, and TCAP
• Wireless: SS7 with Mobile
Application Part (MAP) layer
• Internet or Packet: SIP, MGCP,
Megaco, and H.323.

A signalling layer
• Telecommunication: Signalling
Service Point (SSPs) or switches

SEP 01 TELECOMMUNICATIONS DEVELOPMENT ASIA – PACIFIC 79

 END-TO-END IP

Fig. 2 SIP and call control (courtesy

of dynamicsoft inc)

SIP, ISUP, call control, and JAIN

interfaces
JAIN SIP API
The adoption of Session Initiation Fig. 3 The JAIN SIP API (courtesy of dynamicsoft inc)
Protocol (SIP) as the de facto standard
for voice over the Internet, and for voice connection so the endpoint ini- the messages as events through the
communications services over packet tiates an INVITE; the proxy server provider/listener interfaces as shown
networks, has redefined network ele- returns a 100/TRYING. Upon resolv- in Fig. 3.
ments and distributed computing ing the address, the server returns an Since the JAIN SIP API is a com-
platforms into service creation tools, 180/RINGING, and then a 200/OK plete definition of the SIP standard,
application servers, SIP phones, inte- after the receiving party has accepted any SIP-based program may utilise
grated access devices, gateways and the call. The endpoint then sends an the JAIN SIP API as a Java standard
gateway controllers, SIP servers, SIP- ACK to the receiving party and the interface into any JAIN SIP certified
based services, SIP billing solutions, media stream is then set up. Upon stack. This means application servers,
developer toolkits, SIP testing tools, hanging up, a BYE is issued by one of SIP phones, gateways and gateway
SIP user agents, and SIP network the parties and the other party controllers, SIP servers, SIP-based ser-
management. The SIP-based network responds with a 200/OK. vices, SIP billing solutions, developer
has not only redefined the PSTN to The JAIN SIP API defines classes toolkits, SIP testing tools, SIP user
incorporate all the needed functional- for all the SIP headers and messages, agents, and SIP network management
ity of the PSTN, but also provided for and defines the interfaces for can all utilise the JAIN SIP API so as
the growth and extensibility of com- JavaBeans architecture processing of to be portable across and SIP stack
munications into media beyond
Fig. 4 JAIN SIP in the SIP network (courtesy of dynamicsoft inc)
voice. SIP is the specified underlying
protocol for the ‘4G’ all-IP mobile
networks of the future.
Because a SIP-based network with
location and server proxies allows
multiple vendors and multiple net-
works to interoperate, the growth of
SIP-based communications is limited
only by the media connections it has
to manage. This has created a large
community of developers writing SIP-
based communications applications,
proxy servers, user agents, tools, con-
trollers, etc.
The strength of SIP is basic call
control over the IP. As can be seen in
Fig. 2, an endpoint desires to set up a

80 TELECOMMUNICATIONS DEVELOPMENT ASIA – PACIFIC SEP 01

 END-TO-END IP

Fig. 5 ISUP call flow (courtesy of Ulticom Inc)

implementation. PSTN world. The call initiation cre- JAIN ISUP stack.
Fig. 4 shows a typical SIP network ates a set-up request by the applica-
scenario where JAIN SIP interfaces tion that is translated by ISUP into an Contrast and compare: SIP and ISUP
are utilised on proxy servers, media Initial Address Message (IAM) and Comparing ISUP to SIP, the IAM is
gateways, and user clients. sent to the node at the remote end. the same as the INVITE, the ACM is
Because the JAIN SIP API covers ISUP at the remote end on receiving same as the 100/TRYING, and the
far more than what is needed for a an IAM sends a set-up indication to ANM is the same as the 180/RING-
user agent or client-based software, its user application. On receiving an ING. The ACK in SIP has no similar
the JAIN SIPLite API was developed IAM for a voice circuit (identified by construct in ISUP and only provides a
as a functional subset of JAIN SIP its CIC), the circuit is marked busy. level of comfort to the SIP network.
API and basic call control process- The terminating application sends an The REL is the same as the BYE, and
ing. JAIN SIPLite API is targeted at Alert Response to ISUP at the remote the RLC is the same as the 200/OK.
user agents or clients with a small node, which is translated by ISUP to Both protocols serve the same
footprint where the full suite of an Address Complete Message (ACM) function: making a connection. One
JAIN SIP API class definitions is not and sent to the originating node. may argue that SIP goes beyond voice;
needed. When the terminating user answers however, simple additions and modi-
The SIP Servlets API extends the the call, the application sitting over fications to ISUP – and all carriers and
HTTP Servlet definition to incorpo- ISUP sends a set-up response primi- countries have modified ISUP –
rate the processing of SIP messages, in tive to it. ISUP sends this as an would extend ISUP to support any
the same way an HTTP Servlet would Answer Message (ANM) to the origi- media. Both protocols are extensible,
process an HTTP message. Like an nating node. The call is established. that is, they allow for the addition of
HTTP Servlet, the target platform for The calling user then releases the call parameters outside the standard. Both
SIP Servlets is a proxy server or an by sending a Release Request primi- protocols are obtuse when naming of
application server. While SIP Servlets tive to ISUP. Fig. 5 illustrates this their messages – a SIP INVITE is far
may utilise the constructs of the JAIN basic call flow. more meaningful than an ISUP Initial
SIP API, the API constructs are simi- Like the JAIN SIP API, the JAIN Address Message; however, what do
lar to HTTP Servlet constructs. ISUP API also defines all the mes- the numbers 100, 180, and 200 mean
sages, headers, and functionality to in SIP?
JAIN ISUP API pass the messages from the Java tech- ISUP has stood the test of time and
This is analogous to ISUP in the nology space into a vendor certified is running in many networks world-

SEP 01 TELECOMMUNICATIONS DEVELOPMENT ASIA – PACIFIC 81

 END-TO-END IP

and INAP where the protocol is built

more on functional elements as
opposed to pure messaging. The JAIN
initiative does not dictate one over the
other. The driving force behind the
JAIN initiative is to provide Java tech-
nology standards for communications
at all levels, whether SIP, ISUP, or
INAP. This empowers the network
architect to decide the virtues of one
over the other and then has the luxury
of utilizing the JAIN API where appro-
priate.

Where does call control fit in?

From the application side, there is
less concern as to how the connec-
tions are made and more emphasis on
why they are made and who needs
them where. The application develop-
er ends up bridging the gap between
Fig. 6 JAIN ISUP
the network domain and the service
wide. It is robust and reliable. ISUP defined by several standards bodies domain. From the application writers
also assumes responsibility over the targeted at switching platforms inside view, protocol interfaces are primi-
media connection, unlike SIP. A large a very closed protected network. tives for passing data. The application
part of the ISUP primitives deals with Right from the start, there was no is more concerned with a model of
circuit management. In SIP, the incentive to interoperate between the network as it relates to other
media is the responsibility of a gate- ISUP-based platforms. ISUP relies on computing elements such as databas-
way and the interface is MGCP or a static point code configuration; SIP es, management, user interfaces, etc.
Megaco. The problem with ISUP, and relies on a proxy server that can be From the application, call control
SS7 in general, is the lack of interop- updated at any point during opera- constructs like a CALL or CONNEC-
erability between vendors and carri- tions. This makes SIP extensible to TION object with state information
ers. This only exacerbates a drive any IP network and any vendor. and a full suite of interfaces are far
towards an open ISUP running over However worlds apart, SIP and more meaningful than primitive mes-
IP. Since the world is going IP every- ISUP satisfy the functionality of set- sage constructs like an ISUP IAM or a
where, SIP will replace ISUP as the ting up and tearing down a SIP INVITE message.
signalling protocol, and ISUP will be voice/media circuit. They both have This does not diminish the need
relegated to the PSTN – which has set the built-in notion of a ringing for ISUP or SIP, but moves protocol
the standard for quality and control. device at the endpoint and then mak- processing into a world where SIP and
Because SIP is an extension to the ing and tearing down connections. ISUP are important network com-
HTTP protocol, SIP found immediate They are both designed for network modities for services. To the network
acceptance in the IP community and signalling with a protocol view of the architect, a JAIN SIP or a JAIN ISUP
can readily run wherever HTTP runs. world. This view is where network are invaluable; however, to an appli-
This put SIP right into the public architecture defines network ele- cation writer, the actual protocol is
domain where interoperability is a ments, messages, protocols, and less important than managing the ses-
foregone conclusion and all comput- rules for interconnect. This view is sion or call. For the application
ing platforms could become SIP sig- concerned with how connections are writer, the details of the protocol can
nalling platforms. Also the dynamic made, and is not necessarily con- be buried under simple call control
nature of SIP to resolve address cerned with who makes them and primitives.
opened up the possibilities for many why they are made. Instead of building and sending
players to interoperate. Other parallels can be drawn JAIN ISUP or JAIN SIP primitive mes-
On the other hand, ISUP was between the SIP network definition sages as part of a protocol, the Java

82 TELECOMMUNICATIONS DEVELOPMENT ASIA – PACIFIC SEP 01

 END-TO-END IP

technology developer would rather

model the world around call control
objects such as a CALL, a CONNEC-
TION, or a PROVIDER, and then
actions are performed on these objects
such as CreateConnection or
RouteCall. A RouteCall in JAIN Call
Control (JCC) API may precipitate an
IAM in the PSTN to initiate a call, or
an INVITE in a SIP network to initi-
ate a session. The application writer
is none the wiser and is happy the call
was routed on any network.
JCC models the network as Java
objects and provides interfaces into
the objects through the JavaBeans
architecture event mechanism. In Fig.
7 the call is created from the provider, Fig. 7 JCC provides interfaces through JavaBeans architecture event mechanism
and the connections are created from (courtesy of Telcordia Technologies Inc)
the call. The interface into the objects
is through the JavaBeans synchronous results during call processing. A handset (or mobile station), the Radio
method calls and the receipt of Java call is understood to include a Access Network (RAN), Network
technology events. multimedia, multi-party session Control and Management (MSCs,
Fig. 8 is a typical call flow from the over the underlying integrated HLRs, VLRs, etc), the enterprise, and
JCC application, through a JCC imple- (PSTN, packet and/or wireless) content and services.
mentation, and the underlying ISUP network In order to manage and bill for the
signalling – the ACM and ANM. The • Extended Call Control: JAIN services in the wireless domains,
ACM could readily be replaced with a Coordination And Transaction Operational or Business Support
SIP 100/TRYING, and the ANM (JCAT) includes facilities similar to Systems (OSS/BSS) are an integral part
replaced with an 180/RINGING. JCC, but extended to provide finer of the overall solution. Where JAIN is
The JAIN JCC API is structured granularity of call control. In partic- the development of Java standards
into the following three functional ular, unlike JCC, JCAT enables all into communications, a similar initia-
areas (see Fig. 9): common AIN applications as well tive is under way to develop Java stan-
• Elementary Call Control: JAIN as other integrated voice/data and dards for OSS/BSS, called OSS through
Call Processing (JCP) includes the next-generation services. Java (OSS/J, for further information,
very basic facilities required for see java.sun.com/products/oss). The
initiating and answering calls. The Applicability of JAIN APIs to integration of JAIN products with
facilities offered by this package mobile networks OSS/J products is producing an archi-
are too elementary for many if not As 2G and 3G wireless technologies tecture that is being defined by the
most carrier-grade deployments. distribute processing across the net- Java Technology for Service Providers
However, JCP represents an impor- work, ubiquitous standard Java tech- (JTSP, see java.sun.com/products/sp).
tant conceptual cornerstone for nology computing is required to sup- Java or JAIN architectures do not
unifying the call control APIs port new and updated wireless and address a complete wireless solution,
developed by the Java Telephony mobile services. Wireless carriers and however, wherever there is a comput-
API (JTAPI), JAIN and Parlay service providers are tasked with the ing platform in the network, a Java
expert groups integration and harmonisation of all platform may run and JAIN interfaces
• Core Call Control: JAIN Call the processes from the mobile station, may be utilised. Fig. 11 illustrates the
Control (JCC) includes the facili- through the radio network, into the areas defined for wireless across the
ties required for observing, initiat- switching network, and interfacing JAIN architecture. In the wireless
ing, answering, processing and into the Internet and packet net- domain, the following sections
manipulating calls, as well as to works. As shown in Fig. 10, wireless describe the application of JAIN and
invoke applications and return networks’ basic domains are the Java interfaces.

SEP 01 TELECOMMUNICATIONS DEVELOPMENT ASIA – PACIFIC 83

 END-TO-END IP

Fig. 8 Typical call flow from a JCC application

Mobile station urations for a handset. CLDC/MIDP as a standard execution

In the future, almost all handsets will In order to run Java applications on environment for mobile devices.
be Java technology enabled, running a handset, the enabling technology For communications, a JTAPI
the Java 2 platform Micro Edition between the Java application and the interface would provide connection
(J2ME) platform. The handset will be rest of the OS is a KVM – which is a functionality, or SIPLite will treat the
both voice and data enabled, which virtual machine that fits between 40 handset as a SIP user agent. Where
means any number of services can and 200 kilobytes — and there is a JTAPI and SIPLite provide call control
work in concert with the network. Connected Limited Device functionality to the Java application
Fig. 12 shows the various Java config- Configuration which defines Java pro- on the mobile station, further intelli-
files for limited devices, and there is gence is needed for security and priva-
Mobile Information Devices Profile as cy issues. For example, if I desire to
Fig. 9 Functional relationship
between call control standards well, which is also a set of Java APIs. meet an associate for lunch, but have
Managing all of this is a JAM (Java no idea where the associate is, yet I
Application Manager) that manages a have a mobile phone and my associ-
lifecycle of Java applications that get ate has a mobile phone, the network
loaded onto the device as well as ele- knows where we are. However, I may
ments of security such as differentiat- not want my mother-in-law who also
ing access from trusted and un-trust- has a mobile phone, to find me. This
ed applications. MEXE (3GPP Mobile is a privacy issue.
device application Execution Because this level of sophistica-
Environment) has adopted Java and tion requires higher intelligence at

84 TELECOMMUNICATIONS DEVELOPMENT ASIA – PACIFIC SEP 01

 END-TO-END IP

the handset and within the network,

a new industry is emerging focused
on availability management, trust,
and security. The JAIN Presence,
Availability and Management
(PAM) APIs and the JAIN Service
Provider APIs are tracking these
developments. The JAIN communi-
ty is working with leading vendors
as well as other standards bodies
(Parlay, ETSI, and the OSA) to
develop APIs around privacy, securi-
ty and availability. Standardisation
around this kind of interface
ensures portable services can be
flexible across all mobile devices
and wireless networks.

The Radio Access Network (RAN)

The RAN is primarily concerned with
routing voice traffic from the handset
Fig. 10 Wireless network’s basic domains
into the network controlling ele-
ments that will eventually connect loosely based on GSM or IS41. for building scaleable RAN devices,
the voice to the Public Switched In 3G, the RAN is based on ATM such as radio network controllers.
Telephony Network (PSTN). To pro- for 3GPP’s Release 99 specification. Some of these vendors have started
mote roaming across wireless opera- Future releases will be based on IP to work collaboratively with the Java
tors, the radio frequencies and sig- and new standards need to be defined. technology community to extend
nalling have been well defined The IP RAN, as well as the underly- these platforms to provide even more
through GSM and IS41 standards. The ing core network, will be based on availability. This benefits all users of
RAN devices include radio towers IPv6, thereby enabling many millions the platform by bringing carrier grade
and base station controllers. While of mobile Internet users to be secure- availability features to the enter-
most of the devices within the RAN ly addressed. This shift from closed prise/commercial J2EE platform.
are computing platforms, they usually proprietary interfaces and devices to
have well-defined static functions and standard well defined interfaces and The network and the enterprise
are not extensible by the user or the network elements gives the wireless The JAIN MAP APIs define inter-
operator. That is, little to no func- operator tremendous flexibility in the faces to acquire location (position),
tions or features are added to the RAN and also leads the RAN down Short Messaging Services (SMS),
RAN after the wireless network is up an ‘open network’ path.
and running. Since most RAN devices are com- Fig. 11 Areas defined for wireless
Because of the static nature of the puting platforms, RAN vendors are across JAIN architecture
RAN, there has been no drive to discovering Java technology allowing
develop standard open interfaces them to increase productivity, robust-
except those that would benefit the ness, reliability, and time-to-market.
wireless operator (GSM and IS41). This has led to the recent development
Since the wireless operator owned the of Java technology-based RAN devices
voice traffic from the handset into the that include standard Java APIs, such
PSTN, there has been little motiva- as the Java 2 Platform Enterprise
tion for the industry to promote and Edition (J2EE) platform APIs like EJB,
enforce standards in RAN. A single JMS, JNDI, and JAIN. For example,
network equipment manufacture has they have discovered that EJB servers
usually supplied the typical build out can provide a highly available, hori-
of a RAN with proprietary interfaces zontally scaleable application platform

SEP 01 TELECOMMUNICATIONS DEVELOPMENT ASIA – PACIFIC 85

 END-TO-END IP

through HSCSD, GPRS and EDGE,

towards 3G, with each subsequent
advancement offering greater band-
width and hence the opportunity for
further enhanced content, services
and applications.
In order for operators to gain a
competitive advantage in the future
and to justify the high costs of 3G
licences, they need to be in a posi-
tion to offer a comprehensive set of
value-added services to generate new
revenues. To achieve this, innova-
tive telecommunication applications
may need to be developed outside
the operator’s domain. The introduc-
tion of the use of trusted third party
ISV applications that may often be
developed for specific niche markets
is clearly emerging as the way for-
ward. In adopting this approach, it is
Fig. 12 Java handset configurations
essential for operators to maintain
Unstructured Supplementary Services service portability, convergence or the security and integrity of their
Data (USSD), Any Time Interrogation open access to a wireless network. networks while providing trusted
(ATI) from an SS7 network. While the Instead the APIs that look at what third parties access to network
original definition for JAIN MAP API would be most valuable to the enter- resources enabling them to develop
assumes an SS7 infrastructure, there is prise would assist developers writing new services.
nothing inherent in the API that would services. For a wireless network, This has been a focus of the
require it be SS7 only; that is, the JAIN location, status and passing mes- Parlay organisation, wich is develop-
MAP API could also run over IP. sages to and from a handset are a ing a series of API specifications in
The JAIN MAP APIs do not practical useful Java interface for the Unified Modeling Language (UML).
define interfaces for all wireless developer of wireless services. The JAIN Service Provider APIs
nodes such as MSCs, HLRs, BSCs, Most MSC functionality is being (SPA) are providing the Java mapping
etc. This was a conscious decision filled with softswitch technology, and realisation of Parlay’s technolo-
by the JAIN MAP Expert Group, rea- and softswitches are rapidly adopt- gy-independent specifications.
soning that any internal definition ing JAIN JCC as the standard inter- 3GPP’s Open Services Architecture
would only benefit the wireless ser- face. (See previous section). (OSA) for 3G networks has also
vice provider, not the developers adopted this model of third party
writing services. In other words, Content and services application development using the
defining standard interfaces for an In the wireless arena, technology is operator’s network resources.
HLR, BSC or MSC does not bring advancing and evolving from 2G The JAIN SPA Mobility API is
based on the mobility specification
Fig. 13 Call flow of a location-based service
definition from the Parlay organisa-
tion. The API generates reports
based on location, handset status,
emergency services, and Camel-
based services. A sample call flow of
a location-based service through
JAIN SPA Mobility API, Parlay
objects, and JAIN MAP is shown in
Fig. 13.
In this example, the JAIN SPA

86 TELECOMMUNICATIONS DEVELOPMENT ASIA – PACIFIC SEP 01

 END-TO-END IP

tract, in case an audit is needed. The

Java technology agents also perform
the user interface on the client and at
the SP. After the Java technology
agents have established a legal basis
for privacy, control is passed on to
the service that is being requested.
So, if I want to meet my associate
for lunch, a simple request into my
handset kicks the Java technology
agents into high gear and requests
from both users that location infor-
mation is granted. (Although this may
seem redundant to the requesting
party, it adds an extra level of securi-
ty.) The Java technology agents log all
the information, making the neces-
sary modifications to the contract
with time stamps, and then pass the
Fig. 14 JAIN SPA-based OSA wireless solution architecture
information on to the services to per-
client requests a report to locate a and the JAIN initiatives to develop form the location and shortest path
handset. When the request finds its standard Java interfaces. PAM allows algorithm.
way through the Parlay gateway, the networks to share authorised infor- The location of the devices is
4.1 processMSPosOperation (in Fig. 13) mation about subscribers’ identity, determined through JAIN SPA
is invoked into the JAIN MAP API. presence and availability securely Mobility and/or JAIN MAP. Options
across telephony and IP technologies. on this service may include the capa-
End-to-end architecture Presence is the existence of a software bility to confirm by voice or by send-
A sample architecture for a JAIN or hardware device through which ing a short message. JAIN JCC, JAIN
SPA-based OSA wireless solution is information can be communicated – a SIP or JAIN ISUP can initiate a voice
illustrated in Fig. 14. cell phone, a PC, a PDA, etc. call. A message can be sent via JAIN
The advantage that the JAIN APIs Availability is the personal preferences MAP or JAIN SPA Mobility.
bring to this architecture is the flexi- and policies an individual or enterprise The JAIN architecture does not
bility to plug in any vendor’s JAIN specifies for communication and con- prescribe or dictate the use of one API
implementation without changing tent delivery services – when and how over another or one device over
any of the surrounding features. The to accept calls or content. another, however the JAIN initiative
services run oblivious of underlying A possible PAM scenario could opens the opportunity for network
network infrastructure. This allows incorporate Java technology agents developers, service providers and
services to run in converged net- (beans) in the client and at the wire- wireless operators to choose from an
works. The JAIN SPA and PAM less service provider (SIP). Privacy open market of standard network ser-
interfaces allow for open access into would be insured by a legal contract vices and applications that are
a protected wireless network. signed between the client and SP. portable across platforms, and pro-
The JAIN architecture does not While most of the contract is a fixed vides converging open solutions to
dictate which APIs to use and document, another part of the con- heterogeneous networks.
where. Rather, by building a robust tract could be negotiated in an ad hoc
suite of interfaces developers have manner and be changed at the last JAIN; Java; Write Once, Run Anywhere;
more choices to build services at minute. For example, ‘Your boss JavaBeans; J2ME; JTEE; and EJB are registered
either the network layer or the wants your location, shall I give it to trademarks of Sun Microsystems, Inc.
application layer. him?’ This kind of arrangement
The Presence and Availability requires a last minute decision that
Management (PAM) Forum has been has to be respected by the SP. This
exploring this kind of intelligence means that the client and SP must log Douglas Tait, Network Architect, Sun Microsystems
and is making proposals into Parlay all actions and changes to the con- Inc, Palo Alto, California, USA

SEP 01 TELECOMMUNICATIONS DEVELOPMENT ASIA – PACIFIC 87