SOAP API Support

Feature History

Feature Name

Release Information

Description

SOAP API Support for Subscriber CRUD Operations

2025.01

SOAP API Support for cnAAA allows for bulk management of subscriber accounts through a single API request, enabling Create, Read, Update, and Delete operations. This API also supports dynamic policy updates for active user sessions at the Broadband Network Gateway (BNG), optimizing resource management and minimizing operational redundancies.

Overview

Cloud Native Authentication, Authorization, and Accounting (cnAAA) is a system designed to manage network access and enforce security policies. It plays a crucial role in controlling network access and managing resources efficiently. cnAAA supports bulk provisioning of multiple users and allows dynamic policy updates based on real-time inputs from the Online Charging System (OCS). With a single Simple Object Access Protocol (SOAP) API request, users can perform Create, Read, Update, and Delete (CRUD) operations on multiple subscribers, a significant improvement over the previous limitation of handling one subscriber at a time.

Bulk Provisioning

Bulk provisioning refers to the ability to execute CRUD operations on multiple subscriber accounts simultaneously through a single SOAP API request. This capability minimizes redundant tasks and reduces errors in subscriber management.

Procedure

Step 1

The BNG initiates a Subscriber Provisioning SOAP request to manage subscriber data, sent to cnAAA through an HTTPS interface. The UnifiedAPI endpoint on cnAAA handles these requests.

Step 2

Based on the CRUD operation specified, cnAAA interacts with the Subscriber Profile Repository (SPR) to execute the operation.

Step 3

After executing the operation, cnAAA sends a response back to the BNG to confirm success or failure.

Dynamic Policy Push

Dynamic Policy Push updates policies for active subscriber sessions at the Broadband Network Gateway (BNG) using OCS inputs. cnAAA sends a Change of Authorization (CoA) message to the BNG, including details like the NAS-IP-Address, to ensure precise application. This process implements policy changes seamlessly without interrupting user sessions.


Note

In UpdateSubscribersRequest, the dynamic policy push functions only when the session is available.