Open Telecom Platform
Developer(s) | Ericsson |
---|---|
Initial release | 1998 |
Stable release | 18.3 / March 16, 2016 |
Written in | Erlang |
Operating system | Cross-platform |
Platform | Cross-platform |
Type | Programming Framework (middleware, libraries, tools, database) |
License |
Apache License 2.0 (since OTP 18.0) Erlang Public License 1.1 (earlier releases) |
Website |
www |
OTP is a collection of useful middleware, libraries and tools written in Erlang programming language. It is an integral part of the open source distribution of Erlang. The name OTP was originally an acronym for Open Telecom Platform, which was a branding attempt before Ericsson released Erlang/OTP as open source. However neither Erlang nor OTP is specific to telecom applications.[1][2]
The OTP distribution is supported and maintained by the OTP product unit at Ericsson, who released Erlang/OTP as open source in the late 90s, to ensure its independence from a single vendor and to increase awareness of the language.
It contains:
- an Erlang interpreter;
- an Erlang compiler;
- a protocol for communication between servers (nodes);
- a Corba Object Request Broker;
- a static analysis tool called Dialyzer;
- a distributed database server (Mnesia); and
- many other libraries.
History
Early days
Originally named Open System, it was started by Ericsson in late 1995 as a prototype system that aimed to select from a range of appropriate programming technologies and system components, including computers, languages, databases and management systems, to support a remote access system being developed at Ericsson.[3] In the same year, following the collapse of another gigantic C++-based project, Open System was ordered to provide support when it restarted from scratch using Erlang.[4] The result was the highly successful AXD301 system, a new ATM switch, announced in 1998. Open System system was later named Open Telecom Platform (OTP) when the first prototype was delivered in May 1996. OTP has also become a specific product unit within Ericsson since then, providing management, support and further development.
The early OTP system components in 1998:[5]
- Distributed application management
- SASL - error logging, release handling
- OS resource monitoring
- EVA - protocol independent event/alarm handling
- Mnesia - real-time active data replication
- SNMP - operations and maintenance interface
- INETS - simple HTTP support
A key subsystem in OTP is the System Architecture Support Libraries (SASL), which gave a framework for writing applications. The early version of SASL provided:[6]
- Start-up scripts
- An application concept
- Behaviours (design patterns)
- Error handling
- Debugging
- High-level software upgrade in runtime without shutdown
The behaviours provide programmers with yet higher abstractions for efficient program design. The early version included:[7]
- Supervision
- Servers
- Event handling
- Finite State Machines
OTP applications
As of OTP 18.2, the following applications are included in the Erlang/OTP distribution:[8]
- asn1
- common_test
- compiler
- cosEvent
- cosEventDomain
- cosFileTransfer
- cosNotification
- cosProperty
- cosTime
- cosTransactions
- crypto
- debugger
- dialyzer
- diameter
- edoc
- eldap
- erl_docgen
- erl_interface
- erts
- et
- eunit
- gs
- hipe
- ic
- inets
See also
References
- ↑ M. Logan, E. Merritt, and R. Carlsson (2010) Erlang and OTP in Action
- ↑ OTP, the Middleware for Concurrent Distributed Scalable Architectures - Youtube
- ↑ B. Däcker (2000) Concurrent Functional Programming for Telecommunications: A Case Study of Technology Introduction
- ↑ M. Logan, E. Merritt, and R. Carlsson (2010) Erlang and OTP in Action
- ↑ B. Däcker (2000) Concurrent Functional Programming for Telecommunications: A Case Study of Technology Introduction
- ↑ B. Däcker (2000) Concurrent Functional Programming for Telecommunications: A Case Study of Technology Introduction
- ↑ B. Däcker (2000) Concurrent Functional Programming for Telecommunications: A Case Study of Technology Introduction
- ↑ http://www.erlang.org/download.html