INAP API Exposure Function

The IN Application Part (INAP) API Exposure Function is a communication engine that enables the access and control of IN services by external applications. IN (Intelligent Network) is a set of standards that defines how fixed-line network operators can provide value-added services to their subscribers. The microservice acts as an interface between the IN service logic and the external applications, allowing them to invoke INAP operations and receive notifications. The INAP-AEF is commonly used to perform authentication, authorization, charging and policy enforcement for the exposed INAP services.

Features & Benefits

Programmable via a internal scripting

Provides ability to quickly and easily implement zero-code call flows using simple scripting language to shorten time-to-market.

Multi-function

Implements all mobile IN function interfaces, Service Switching Function (SCF), Service Control Function (SCF) & Service Resource Function (SRF)

Optional data store

Enables to keep number lists in a shared memory store for distributed configurations.

Standalone mode

Implements a multi-service SCF based on service key subscriptions

One of the benefits of implementing IN services with INAP is that it allows service providers to create and deploy new services independently of the underlying network infrastructure. INAP enables service logic to be executed on an application server, rather than on the network switches, which reduces the complexity and cost of service development and maintenance. INAP also commonly used in fixed and mobile networks, such as GSM, UMTS, and SIP, by providing a common interface for service invocation and control. INAP can be used to implement various IN services, such as prepaid calling, number portability, call screening, and location-based services.

3rd Party API Exposure mode

Expose SCF API to 3rd pary domain with the CAPIF Core Function

A WNO (Wireline Network Operator) would most typically expose APIs to third-party providers or resellers (who could be thought of as virtual network operators in this context) to enable better integration and interoperability between their services. By exposing APIs, WNO can allow these providers to access its network resources, such as billing, authentication, provisioning, and customer care. This can benefit both parties by reducing operational costs, improving customer satisfaction, and creating new revenue streams. For example, third-party providers can offer customized plans and features to their subscribers using WNO's network infrastructure, while WNO can leverage these providers' market reach and brand loyalty.