Portal services: An evolution of voice features

Clarisse, Olivier B.; Collet, Pierre; Dunn, James P.; Westergren, Bruce A.; Velazquez, Lizette

doi:10.1002/bltj.2245

Cited by 4 publications

(2 citation statements)

References 5 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The customized Web pages must be provided, but this is much easier than getting protocol changes adopted by standards bodies. A portal can be used to configure user preferences and any other user-provisionable data in a personal database, to initiate transactions that drive access session functions for registration and activation, and to provide agent services [8].…”

Section: Solutionmentioning

confidence: 99%

Documenting architectures with patterns

Hanmer¹,

Kocan

2004

Bell Labs Tech. J.

View full text Add to dashboard Cite

Software patterns have been used for a decade or more to describe solutions to design and architecture problems. This paper illustrates the value of using software patterns to describe and generate specific architectures and discusses the objectives and techniques of documenting architectures using these patterns. It defines the specialized system of software patterns called a pattern language and presents example patterns and an example pattern language. Finally, it introduces a set of software patterns that represents service architectures, including service architectures for offering advanced services. © 2004 Lucent Technologies Inc.

show abstract

Section: Solutionmentioning

confidence: 99%

Documenting architectures with patterns

Hanmer¹,

Kocan

2004

Bell Labs Tech. J.

View full text Add to dashboard Cite

show abstract

“…For the PLUSS project we used the H.323 device server and as H.323 end points we used Microsoft' s netmeeting as and an IP Web phone that is based on a modified IS2630 web phone. The latter was provided to us by the SPEED and FLW department in Naperville, Illinois ( see [3]).…”

Section: The Server Sidementioning

confidence: 99%

Validation of the Parlay API through prototyping

Hellenthal¹,

Panken²,

Wegdam³

IEEE Intelligent Network 2001 Workshop. IN 2001 Conference Record (Cat. No.01TH8566)

View full text Add to dashboard Cite

The desire within the telecommunications world for new and faster business growth has been a major drive towards the development of open network APIs. Over the past 7 years several (semi) standardization groups have announced to work on network APIs, including TINA-C, JAIN, IEEE P1520, INforum, 3GPP, JAIN, Parlay. The Parlay group seems most successful in attracting industry awareness with their API, called the Parlay API. The rational behind the Parlay API is that it attracts innovation from third parties that are outside the network operator's domain to build and deploy new network hosted applications. This also means that the public telecom network is opened for niche and short-lived applications as well as for applications that possibly integrate telephones with other terminals such as PCs. The Parlay group has successfully passed the first two phases of success, namely publishing their API on the right moment in time and attracting a critical mass within the telecom industry with their results. Prototyping the API on a real network execution platform is the only manner to show its technical feasibility. Such an exercise was executed internally within Lucent Technologies and raised a number of questions as well as recommendations on both the technical and the semantical behavior for systems that will be interconnected via the Parlay API. In this paper we share these results, showing drawbacks , advantages of as well as challenges for this API.

show abstract