@article{1bee8d8695694f2d8588b0f071dcdb98,
title = "Evolutionary trends in intelligent networks",
abstract = "A number of groups are currently developing technologies aimed at evolving and enhancing the capabilities of intelligent networks. In this article we discuss three of these initiatives: PINT, Parlay, and IN/CORBA Interworking. The IETF PINT work addresses how Internet applications can request and enrich telecommunications services. The Parlay consortium is specifying an object-oriented service control API that facilitates the access, control, and configuration of IN services by enterprise IT systems. The OMG's IN/CORBA interworking specification enables CORBA-based systems to interwork with existing IN infrastructure, thereby promoting the adoption of CORBA for the realization of IN functional entities. We address how all three of these technologies could be deployed together in order to provide a basis for a more flexible and open IN architecture. We also identify a number of common trends and potential pitfalls highlighted by current work on the evolution of IN.",
author = "Rob Brennan and Brendan Jennings and Conor McArdle and Thomas Curran",
note = "Funding Information: Our example network operator provides Web-based yellow pages for its enterprise customers{\textquoteright} free-phone (toll-free) numbers and has chosen to subcontract a third-party online directory provider for this work. This is supported by a PINT-based solution to add a click-to-dial capa- bility to the online phone book. One customer has used Parlay to build a free-phone premium support number that routes calls to support personnel based on an internal duty roster database and an internal database of the mobile phone numbers of support personnel. Service deployment and configuration are performed via the Parlay framework interfaces, which in turn trigger a CORBA-based service management system to configure the operator network. Service execution takes the following steps: • A PINT elemental service (click to dial) is initiated by the end user at the online direc-tory provider{\textquoteright}s site. • The PINT server at the network operator{\textquoteright}s site handles the PINT request and supplies the call initiation information to a collocat-ed INAP CS-2 SCF. • From the requested number the SCF deter-mines that additional handling information is required from the CORBA-based SCF and starts an INAP CS-2 SCF–SCF rela-tionship with the controlling SCF. The IN/ CORBA gateway maps between the INAP session (and destination Global Title) and the CORBA TcUser association with the correct service object(s) within the CORBA-based SCF. • The CORBA-based SCF initiates a Parlay session to the enterprise system, which returns a suitable routing address based on current time and the local duty roster and mobile number databases. Additionally, the enterprise accounting system is updated with details of the call. • The controlling SCF then initiates a call between the appropriate support person and the PINT client{\textquoteright}s phone. Our definition of the term service is necessarily loose in this example since multiple traditional and next-generation telecommunications services are combined into one perceived service for the end user. Of course, similar scenarios may be achieved with currently available vendor-specific solutions. These systems are typically inflexible, less integrated, and incapable of deployment in multivendor environments.",
year = "2000",
month = jun,
doi = "10.1109/35.846077",
language = "English",
volume = "38",
pages = "86--93",
journal = "IEEE Communications Magazine",
issn = "0163-6804",
publisher = "Institute of Electrical and Electronics Engineers Inc.",
number = "6",
}