Analysis of the API interface
Yan Lei
Summary: The API interface between two network controls and application layers, that is, OSA / PARLAY APIS and JAINTM APIS
Keywords: Application Interface (API) PARLY JAIN
I. Introduction
An open business architecture will be one of the important features of the next generation network. One of the key technologies is the application interface (APIS) between network control and application layers. Three applications such as application interfaces, business developers, Independent Software Provider (ISV) can be used to obtain the ability to use existing network resources, so that it is convenient and flexible to provide customers with the required business.
This article introduces two APIs currently in the industry.
Second, the classification of the APIs between network control and application layers
This article describes the following classes in the overall class, as shown in Figure 1:
Figure 1: Classification of APIs between network control and application layers
(1) Third Party APIS: This apis opens and provides authentication and security functions to third parties. Through this API, third parties can use business control APIs and business management APIs.
(2) Business Control APIS: This APIS provides network capabilities for controlling business. Includes call control, billing, mobile, user interaction, etc. Network operators or third parties can develop their applications through this APIS.
(3) Business management APIs: This API provides service management capabilities. For example, the observation, expansion, execution, etc. of the business. Network operators use this API to conduct business management.
(4) Protocol / Resource API: This API provides protocol / resource functionality for network capabilities. Such APIs are not included in this article.
Third, OSA / PARLAY APIS
1 Overview
Parlay organization, ETSI, and 3GPP are defining public APIs for open service access (OSA). The API developed by this joint group will be called OSA / Parlay API.
Parlay organization was established in 1998. The initial members include: BT, Microsoft, Nortel NetWorks, Siemens, and Ulticom (predecessor is DGM & S Telecom). As of today, Parlay organization already has more than 60 members. As the research is in-depth, Parlay has gradually established cooperative relations with other standardized organizations or forums, such as ETSI, 3GPP, JAIN.
OSA / PARLAY API wants to apply providers, such as Independent Software Provider (ISV), and Application Service Providers (ASPs), which can not rely on network application development in the basic voice / multimedia network. Fast commercialization and simplified development cycles will be the interests of Osa / Parlay Apis expectation.
2. Technical introduction
OSA / PARLAY API includes two types of interfaces:
- Business Interface: This type of interface is used to apply access network capabilities.
- Frame interface: Such interfaces are used to provide support for business interfaces to provide the necessary security, manageable.
OSA / PARLAY APIs describe using a Unified Modeling Language (UML). The API provides the corresponding mechanism to ensure that the object transparently sends a request and receives a response from other platform objects.
The location of the OSA / PARLAY API in the network is shown in Figure 2:
Figure 2: Location of OSA / PARLAY API in the network
The architecture of the OSA / PARLAY APIS is shown in Figure 3:
Figure 3: Architecture of OSA / PARLAY APIS
Parlay framework and business capability feature are the main components of OSA / PARLAY APIS:
The framework API mainly includes: the interface between the application server and the framework, the interface between the network service server (SCS) and the framework, the interface between the business operator and the framework. The main features of the completed are: - Business registration, ordering and discovery;
- Authentication and authorization;
Comprehensive Management.
Business Capacity Features (SCFS) mainly include:
Call Control provides basic call control capabilities, and provides multi-call, multimedia call, conference call control, etc. Enhanced function user interaction (user interaction) sends short messages, broadcast notifications, and collect user information, etc. User Location and Status Information Terminal Ability (TERMINAL CAPABILITIES) Gets Data Session Control to Control Basic Messaging (Generic Messaging) to send, store, receive messages, and provides voice mailbox or email. Required Capacity Management (Connectivity Manager) Provides QoS Guaranteed Account Management (Charging) Providing Account Query, Function, POLICY Management, creation, update, deletion, rendering policy information And useful management (Presence and Availability Management) management and presentation related information, such as dynamic information of device / software and its owner
Four, JainTM APIS
1 Overview
JAINTM API is a set of Java technology-based APIs. Through this API, you can quickly develop next-generation communications products and services on the Java platform. Jain's three driving power is:
- Business transplantation: Current technology development is limited by the proprietary interface, which will increase development costs and commercial times. Using Jain technology, the proprietary interface will be transformed into a unified Java interface to make the application have convenient portability.
- Network Fusion (Integrated Network): Jain technology will accelerate network fusion, allowing applications and services to serve PSTN, packets (IP or ATMs) and wireless networks.
- Safe network access: Enables applications outside the network to access network resources and devices, perform specified operations and functions.
Jain technology integrates the Internet (IP) and Intelligence Network (IN) protocol integration by defining a new abstract layer and a Java interface associated with the PSTN network, group (IP or ATM) network, and wireless network establishment. In addition, opportunities have been created for launching rich services because Java applications are allowed to securely use resources in the network. It can be said that Jain technology is changing the telecom market from many proprietary enclosed systems to a single network structure that can be quickly created and deployed.
JAIN consists of two API specifications:
- Protocol API Specification: The interfaces of cable, wireless and IP signaling protocols are specified.
- Applying an API specification: A variety of APIs needed to create a business within the Java framework of all protocols included in the API specification.
Jain's goal is to establish open value chains between third-party business providers, equipment-based business providers, telecommunications providers, network equipment providers and telecommunications, consumers, and computer equipment manufacturers.
2. Architecture
Jain's architecture is shown in Figure 4:
Figure 4: Jain architecture
The Jain system defines the software ingredient library, development tools, business creation environments, and business logic execution environments for establishing next-generation services for integrated PSTN, packets (ATM, and IP) and Wi-Fi.
The basic elements of each layer are as follows:
Business Layer: Business Control Point (SCPS), Base Station Controller (BSCS), Position Home Register (HLRS), Visit Position Register (VLRS), and Mobile Switching Center (MSCS), Application Server.
Signaling layer: ISUP, INAP, TCAP, MAP, SIP, H.323, MGCP, Megaco.
Network Layer: Business Exchange Point (SSP), Switch, Mobile Switch Center (MSCS), Softswitch, Media Gateway, H.323 Net Stay.
The Jain system contains business creation environments (SCE) for trusted business and untrusted third-party applications. The trusted business is located in the center of the public network. Untrusted services written by third parties have functions that access the public network center. The interface is provided through security to ensure the impact of the network reliability and integrity is not affected by third-party applications.
The next-generation network service trusted by the Jain system provides business logic execution environment, business, and JAIN SELE execution will use Enterprise JavaBeansTM (EJB).
The untrusted business is like trusted business, with similar needs to SLEE. Untrusted business will also rely on technologies such as EJB, JES and JINITM. Jain SCE has two types of business creation environments that trust and untrusted business creative environments.
Figure 5 shows the location of the Jain API in the communication platform. The soft exchange system is the topic of the mapping of call control / session to the base protocol API. Because the softswitch platform signaling is based on the IP network, the underlying protocol is mostly SIP, MGCP, Megaco or H.323. There are also some softswitch platforms to support the SS7 protocol in order to support the telephone network.
Figure 5: Location of Jain API in the communication platform
3. Jain App API Specification:
JainTM Call Control
Jain Call Control (JCC) provides applications that provide different networks of different networks in the application. Applications only need to face the JCC interface. The JAIN adapter will enable calls and data to successfully access different networks.
JainTM coordination and transaction processing
JainTM Coordination and Transaction (JCAT) includes functions required to apply, call, call, and return results, processing call parameters, or user information, and further call processing and control.
JainTM business provides API (for PARLAY specifications)
Jain businesses for PARLAY specification provide APIS (Spa) to provide a mechanism for secure access network capabilities. This group of APIs focus on PARLAY implementation, as well as Java technology that allows for the output of network operators and discovers other services such as network operators / users.
JainTM business logic execution environment
Once the business is established, you can test and configure in the JAIN business logic execution environment (SLEE). Jain Slee is a telecommunications and Internet operation definition interface and necessary conditions.
JainTM business creation environment
Jain Business Creation Environment (SCE) is a set of software interfaces, support and simplify the creation of telecom services.
JainTM Public API
The common interfaces and classes are specified, such as data types and exception definitions. Used to keep JAIN consistency. Five, conclude
Although the completion of the next generation network has to wait until the time, with the gradual development of the network, more and more business will be provided by a third party other than network operators and equipment manufacturers through the application interface (APIS). The large-scale application of such services will accelerate the evolution of existing networks to open networks. In this process, various APIs technology will inevitably play an increasingly important role.
