| |
- What is the Parlay Group?
- Who were the originators of the Parlay
work and how did the Group come about?
- Is the Parlay Group an open standards body?
- What is the origin of the Parlay name?
- Why did leaders of telecommunications and
high-tech business initiate the creation of the Parlay API?
- Can my company join the Parlay Group?
- Why now?
- What network functionality is accessed
by the Parlay API?
- How does the API find its way to non-Parlay
Group members?
- Doesn't access to telecommunications network
functions, via such an open API, pose a threat to the integrity
of the network?
- Are we talking about re-inventing or replacing
IN?
- What differentiates this API specification
from existing "standards" that have their own
protocols (such as AIN)?
- The API seems to address capabilities
at the edge of the [signaling] network. Will it replace
CTI?
- What are the benefits to the end user
of the Parlay API?
- Are there any geographic limitations to
the adoption of the API?
- Does the Parlay Group produce products?
- Are Parlay products and applications available
now?
- Are the APIs implemented directly on network-equipment
(e.g. switches and routers)?
- Can the Parlay API be implemented on multiple
technologies and platforms (such as Windows NT, JAVA VM,
UNIX and others)?
- What is the relationship of the Parlay
Group to standards emerging from standards bodies and working
groups (e.g. IEEE, OMG, ITU, TINAC, IETF, ETSI, 3GPP, etc.)?
What is the Parlay Group?
The Parlay Group has been formed to create an explosion in
the number of communications applications by specifying and
promoting open Application
Programming Interfaces (APIs) that intimately link IT
applications with the capabilities of the communications world.
Who were the originators of the Parlay work and
how did the Group come about?
Founded in 1998, The Parlay Group focused initial development
of its APIs on functions such as call control, messaging and
security. The Parlay Group was formed by a group of companies
(BT, Microsoft, Nortel Networks, Siemens, and Ulticom - formerly
DGM&S Telecom). The Group first demonstrated a Parlay
service in the UK and USA in December 1998 and since used
industry feedback to refine its specifications. The current
Parlay Specifications
pave the way forward in developing usable, real-world product
implementations of the APIs.
Is the Parlay Group an open standards body?
The Parlay Group, Inc. is not a standards body. It is an
open, multi-vendor consortium organized to develop open, technology-independent
application programming interfaces (APIs) that enable the
development of applications that operate across converged
networks. The Group promotes the use of Parlay APIs and ultimate
standardization.
Back to Top
What is the origin of the Parlay name?
The word parlay originally comes from the French verb
parler, which means "to talk." The term entered
into the English language as a result of the activities of
French traders/explorers in North America. In order to deal
in animal pelts with the Native Americans, a trade pidgin
language developed in which the term grew to mean "negotiate.”
English explorers later encountered and adopted the term,
and from there it entered into English general usage, meaning
"to negotiate a favorable deal” or “to grow
an investment."
The name Parlay was chosen by the Parlay Group because it
encompasses both the technical and commercial objectives of
Parlay:
- To Talk -- Parlay allows the telecom and IT worlds
to talk by providing a mediating interface
- To Negotiate a Favorable Deal -- Parlay negotiates
favorable deals by providing a commercial framework for
profitable participation of all members in the value chain.
The term held additional appeal because its cross-cultural
origin mirrors the diversity of the Parlay
membership. The word Parlay had been trademarked
by Lucent Technologies, a Parlay Group member, that graciously
donated the term to the Parlay Group.
Back to Top
Why did leaders of telecommunications and high-tech
business initiate the creation of the Parlay API?
We wanted to get the job started and to progress rapidly
to meet the needs of the industry and our customers. So we
commenced work with just five companies, all of whom were
already working in the "Open APIs" technology area.
In Parlay Phase 2 (in June 1999), we expanded to eleven companies
so that we could embrace skills in IP network control, mobility,
performance management, audit capabilities, and improved integrity
technology areas. Now, the group has progressed to the point
where a fully open, non-profit organization is the best method
to carry the work forward, and we
seek members with skills for contributions in all areas
of application delivery.
Can my company join the Parlay Group?
Yes. You need only to sign the membership agreement and pay
your dues. No other restrictions exist. Learn
more.
Why now?
In today's network, applications and services are part of
the network operator's domain. This network centric approach
was excellent for simple mass-market applications. But the
network is changing, with the emergence of mobility and IP.
What is now needed is a solution that combines the benefits
of the network-centric approach of economies of scale and
reliability with the creativity and power of the IT industry.
It's possible for applications to be built, tested and operated
by enterprises outside network domain. This is achieved with
a programming interface, which allows applications to access
the functions of the network and generic support functions
in a secure way. This is the role of Parlay
APIs.
What network functionality is accessed by the
Parlay API?
Parlay is an umbrella architecture that provides network
independence and application portability. The Parlay APIs
enable a new generation of off-the-shelf network applications/components
(e.g. messaging, mobility, end-to-end quality of service,
etc.) to be developed by application providers (ISVs/ASPs)
independent of the underlying voice/multimedia network.
How does the API find its way to non-Parlay
Group members?
The Parlay Specifications
are publicly available on this website. In addition, Parlay's
Official Spokespeople travel
internationally, discussing the benefits of Parlay at conferences
an tradeshows. The Parlay Group also hosts Parlay/OSA
Conferences 3 times a year in the Americas, APAC region,
and EMEA region. These events are open to the public and include
product showcases by Parlay Member Companies, live demonstrations
of Parlay applications, an "Intro to Parlay" Educational
Seminar, business-focused presentations in our Business Summitt,
and more. Join the
Parlay Interest Community to receive invitations to international
Parlay/OSA Conferences. Are you an operator? If so, be sure
to join the Parlay
Operator Interest Group, too.
Doesn't access to telecommunications network
functions, via such an open API, pose a threat to the integrity
of the network?
The Parlay API addresses security and load management to
ensure that the integrity of the network is maintained and
has been proven secure by those companies who are using Parlay
today.
Are we talking about re-inventing or replacing
IN?
As networks of the future evolve, there will be a growing
need to harmonize intelligence in the center of the network
with intelligent devices at the network edge. The Parlay APIs
allows services -- which use the wide range of common functions
at the center of the network -- to be developed outside of
the network . The openness of the APIs encourage more utilization
of IN.
What differentiates this API specification from
existing "standards" that have their own protocols
(such as AIN)?
Today's IN solutions have been designed to meet the needs
of telecommunication network operators through protocols (not
open APIs) within the network. The Parlay Group provides specifications
for an external APIs to support a wide range of external applications
(e.g., from service providers) while maintaining the security
and integrity of the network.
The API seems to address capabilities at the
edge of the signaling network. Does it replace CTI?
Not at all. Rather, implementations of the specification
augment CTI by finally breaking down the barriers at the edge
of the networks and allowing creation of services and applications
outside of the network that are less constrained. Parlay allows
applications external to the world's telecommunication networks
to customize the interactions of these networks. This enables
the combined resources of the world's telecommunication networks,
the world's "enterprise" networks, the Internet,
and even personal data networks to be brought to bear to provide
services that use all communications functions, including
voice, video, data, etc.
What are the benefits to the end user of the
Parlay API?
Implementation of the API specification enables more services
and and less-expensive services and creates a more competitive
market for telecoms applications and services. Today end users
are bound to whatever the carrier alone has to offer. Implementation
of the API specifications allows the end user to find services
that are more finely attuned to their specific needs. Service
providers are now easily providing "mass-customization"
of services that meet the specific needs of particular customer
market segments.
Are there any geographic limitations to the
adoption of the API?
No, Parlay was designed to meet the needs of a wide variety
of networks around the world and has been deployed globally.
Does the Parlay Group produce products?
No. Work within the group is confined to the creation of
a specification, which can be used by anyone and everyone
to deliver compliant products and applications. Many Parlay
Members, however, produce Parlay
products and Parlay applications.
Are Parlay products and applications available
now?
Yes! Parlay products and
applications are available now and more are emerging every
day!
Are the APIs implemented directly on network-equipment
(e.g. switches and routers)?
The entities that implement the API specifications produce
a variety of implementations to match the dictates of the
market. The Parlay Group specifies the APIs so as to allow
as much flexibility as possible.
Can the Parlay API be implemented on multiple
technologies and platforms (such as Windows NT, JAVA VM, UNIX
and others)?
Yes, the APIs is platform, vendor- and technology-independent,
allowing it to be implemented on multiple technologies, and
to work easily with other industry initiatives.
What is the relationship of the Parlay Group
to standards emerging from standards bodies and working groups
(e.g. IEEE, OMG, ITU, TINAC, IETF, ETSI, 3GPP, etc.)?
The Parlay Group has an on-going working relationship with
standards fora and consortia. The Parlay Group works with
ETSI, 3GPP, and 3GPP2 to publish the Parlay
Specifications.
|
|