This article includes a list of references, related reading or external links, but its sources remain unclear because it lacks inline citations .(June 2021) |
Parlay X was a set of standard Web service APIs for the telephone network (fixed and mobile). It is defunct and now replaced by OneAPI, which is the current valid standard from the GSM association for Telecom third party API.
It enables software developers to use the capabilities of an underlying network. The APIs are deliberately high level abstractions and designed to be simple to use. An application developer can, for example, invoke a single Web Service request to get the location of a mobile device or initiate a telephone call.
The Parlay X Web services are defined jointly by ETSI, the Parlay Group, and the Third Generation Partnership Project (3GPP). OMA has done the maintenance of the specifications for 3GPP release 8.
The APIs are defined using Web Service technology: interfaces are defined using WSDL 1.1 and conform with Web Services Interoperability (WS-I Basic Profile).
The APIs are published as a set of specifications.
Parlay X 4.0 Specification | Available functionality |
---|---|
Part 1: "Common" | Definitions re-used across multiple Parlay X specifications |
Part 2: "Third Party Call" | Creating and managing a call initiated by an application |
Part 3: "Call Notification" | Handling calls initiated by a subscriber in the network. One variant (i.e. application interface) allows application to "direct" the handling of the call and the other simply provides a notification. |
Part 4: "Short Messaging" | Receive and send SMS (including delivery receipts) |
Part 5: "Multimedia Messaging" | Receive and send Multimedia Messages |
Part 6: "Payment" | Payment reservations, pre-paid payments, and post-paid payments |
Part 7: "Account Management" | Account querying, direct recharging and recharging through vouchers |
Part 8: "Terminal Status" | Get the status (i.e. reachable, unreachable or busy) of a terminal |
Part 9: "Terminal Location" | Getting location information about a terminal |
Part 10: "Call Handling" | Specify how calls are to be handled for a specific number. There is no 'per-call interaction' with the application unlike in the Call Notification API. |
Part 11: "Audio Call" | Provide multimedia message delivery and the dynamic management of the media involved for the call participants |
Part 12: "Multimedia Conference" | Create a multimedia conference and the dynamic management of the participants involved |
Part 13: "Address List Management" | Manage groups (aliases) of subscribers |
Part 14: "Presence" | Presence information to be obtained about or registered for users used e.g. by Instance Messaging clients |
Part 15: “Message Broadcast” | Send messages to all the fixed or mobile terminals in a specified geographical area |
Part 16: “Geocoding” | Get the location address of a subscriber e.g. country, state, district, city, street, house number, additional information, and zip/postal code |
Part 17: “Application-driven Quality of Service (QoS)” | Dynamically change the quality of service (e.g. bandwidth) available on end user network connection |
Part 18: "Device Capabilities and Configuration" | Get information about device capabilities and push device configuration to a device |
Part 19: “Multimedia Streaming Control” | Control streaming of multimedia to a subscriber e.g. to transfer stream between a user's terminals |
Part 20: “Multimedia Multicast Session Management | Control a multicast session, its members and multimedia stream, and obtain channel presence information |
Part 21: "Content management" | The content management web service enables uploading content into the network (or a third party content provider) and consuming content from the network (or a third party content provider). |
Part 22: "Policy" | The Policy Web Service is defined to offer provisioning and evaluation functions for policies. |
In general Parlay X provides an abstraction of functionality exposed by the more complex, but functionally richer Parlay APIs. ETSI provide a set of (informative not normative) Parlay X to Parlay mapping documents.
Parlay X services have been rolled out by a number of telecom operators, including BT, Korea Telecom, T-Com, Mobilekom and Sprint.
The Global System for Mobile Communications (GSM) is a standard developed by the European Telecommunications Standards Institute (ETSI) to describe the protocols for second-generation (2G) digital cellular networks used by mobile devices such as mobile phones and tablets. It was first deployed in Finland in December 1991. By the mid-2010s, it became a global standard for mobile communications achieving over 90% market share, and operating in over 193 countries and territories.
Scalable Vector Graphics (SVG) is an Extensible Markup Language (XML)-based vector image format for two-dimensional graphics with support for interactivity and animation. The SVG specification is an open standard developed by the World Wide Web Consortium (W3C) since 1999.
SMS is a text messaging service component of most telephone, Internet, and mobile device systems. It uses standardized communication protocols that let mobile devices exchange short text messages. An intermediary service can facilitate a text-to-voice conversion to be sent to landlines.
The Intelligent Network (IN) is the standard network architecture specified in the ITU-T Q.1200 series recommendations. It is intended for fixed as well as mobile telecom networks. It allows operators to differentiate themselves by providing value-added services in addition to the standard telecom services such as PSTN, ISDN on fixed networks, and GSM services on mobile phones or other mobile devices.
An application server is a server that hosts applications.
The Parlay Group was a technical industry consortium that specified APIs for the telephone network. These APIs enable the creation of services by organizations both inside and outside of the traditional carrier environment. In fact, it is hoped that services can be created by IT developers, rather than telephony experts.
A subscriber identity module or subscriber identification module (SIM), widely known as a SIM card, is an integrated circuit running a card operating system (COS) that is intended to securely store the international mobile subscriber identity (IMSI) number and its related key, which are used to identify and authenticate subscribers on mobile telephony devices. It is also possible to store contact information on many SIM cards. SIM cards are always used on GSM phones; for CDMA phones, they are needed only for LTE-capable handsets. SIM cards can also be used in satellite phones, smart watches, computers, or cameras.
The 3rd Generation Partnership Project (3GPP) is an umbrella term for a number of standards organizations which develop protocols for mobile telecommunications. Its best known work is the development and maintenance of:
The Open Service Access or OSA is part of the third generation mobile telecommunications network or UMTS. OSA describes how services are designed in a UMTS network.
Binary Runtime Environment for Wireless is an application development platform created by Qualcomm, originally for code division multiple access (CDMA) mobile phones, featuring third-party applications such as mobile games. It is offered in some feature phones but not in smartphones. Developed in 1999, as a platform for wireless applications on CDMA-based mobile phones, it debuted in September 2001. As a software platform that can download and run small programs for playing games, sending messages, and sharing photos, the main advantage of Brew MP is that the application developers can easily port their applications among all Brew MP devices by providing a standardized set of application programming interfaces. Software for Brew MP enabled handsets can be developed in C or C++ using the freely downloadable Brew MP software development kit (SDK). The Brew runtime library is part of the wireless device on-chip firmware or operating system to allow programmers to develop applications without needing to code for system interface or understand wireless applications. Brew is described as a pseudo operating system, but not a true mobile operating system. Brew is not a virtual machine such as Java ME, but runs native code.
Unstructured Supplementary Service Data (USSD), sometimes referred to as "quick codes" or "feature codes", is a communications protocol used by GSM cellular telephones to communicate with the mobile network operator's computers. USSD can be used for WAP browsing, prepaid callback service, mobile-money services, location-based content services, menu-based information services, and as part of configuring the phone on the network.
The Open Mobile Alliance (OMA) is a standards body which develops open standards for the mobile phone industry. It is not a formal government-sponsored standards organization like the ITU, but a forum for industry stakeholders to agree on common specifications for products and services.
The Telecoms & Internet converged Services & Protocols for Advanced Networks (TISPAN) is a standardization body of ETSI, specializing in fixed networks and Internet convergence. It was formed in 2003 from the amalgamation of the ETSI bodies Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) and Services and Protocols for Advanced Networks (SPAN).
A service delivery platform (SDP) is a set of components that provides a service(s) delivery architecture for a type of service delivered to consumer, whether it be a customer or other system. Although it is commonly used in the context of telecommunications, it can apply to any system that provides a service. Although the TM Forum (TMF) is working on defining specifications in this area, there is no standard definition of SDP in industry and different players define its components, breadth, and depth in slightly different ways.
The JSLEE is a Java programming language API for developing and deploying network services. It was standardized in Java Specification Requests JSR 22 and JSR 240 by Sun Microsystems and OpenCloud with the participation of more than 80 operators and software vendors.
SIM Application Toolkit (STK) is a standard of the GSM system which enables the subscriber identity module to initiate actions which can be used for various value-added services. Similar standards exist for other network and card systems, with the USIM Application Toolkit (USAT) for USIMs used by newer-generation networks being an example. A more general name for this class of Java Card-based applications running on UICC cards is the Card Application Toolkit (CAT).
OpenSocial is a public specification that defines a component hosting environment (container) and a set of common application programming interfaces (APIs) for Web-based applications. Initially, it was designed for social network applications and developed by Google along with MySpace and a number of other social networks. More recently, it has become adopted as a general use runtime environment for allowing untrusted and partially trusted components from third parties to run in an existing web application. The OpenSocial Foundation moved to integrate or support numerous other Open Web technologies. This includes OAuth and OAuth 2.0, Activity Streams, and Portable Contacts, among others.
In intelligent networks (IN) and cellular networks, service layer is a conceptual layer within a network service provider architecture. It aims at providing middleware that serves third-party value-added services and applications at a higher application layer. The service layer provides capability servers owned by a telecommunication network service provider, accessed through open and secure Application Programming Interfaces (APIs) by application layer servers owned by third-party content providers. The service layer also provides an interface to core networks at a lower resource layer. The lower layers may also be named control layer and transport layer.
In computing, an application programming interface (API) is an interface that defines interactions between multiple software applications or mixed hardware-software intermediaries. It defines the kinds of calls or requests that can be made, how to make them, the data formats that should be used, the conventions to follow, etc. It can also provide extension mechanisms so that users can extend existing functionality in various ways and to varying degrees. An API can be entirely custom, specific to a component, or designed based on an industry-standard to ensure interoperability. Through information hiding, APIs enable modular programming, allowing users to use the interface independently of the implementation.
Operations Support Systems (OSS), Operational Support Systems in British usage, or Operation System (OpS) in NTT, are computer systems used by telecommunications service providers to manage their networks. They support management functions such as network inventory, service provisioning, network configuration and fault management.