NAC components
The NAC consists of seven primary components that work together with other Tango DRE features and a user management setup (often a SQL database) to deliver a seamless roaming experience for the subscriber.
Multi-tenancy is supported (if needed or desired) through a single NAC instance whereby each tenant has a separately-configured captive portal reflecting their brand and identity. |
1 | Captive Portal |
2 | User Notification Service |
3 | HTTP Resource Generator |
4 | Platform Management Interface |
5 | Orchestrator |
6 | Identity Management Service |
7 | Token Web Service |
Captive Portal overview
The principle component of the NAC is the Captive Portal (CP). The Captive Portal is the landing page where subscribers find themselves upon roaming into your network. They access this via a URL received in an SMS or through being redirected when trying to browse the internet. Subscribers can:
-
opt-in for data roaming
-
view and purchase data plans and offers
-
view and manage their current data plans
Currently, the Captive Portal is available in English, Spanish, and Portuguese. |
HRG overview
The HTTP Resource Generator (HRG) transforms HTTP requests from the Captive Portal into plan purchase requests in the SPCM. It allows the Orchestrator to communicate with the GTP proxy.
Orchestrator overview
The Orchestrator processes service definitions as created in the Service Creation Environment (SCE) through the PMI. Examples of service definitions include the following:
-
Updating the online charging server when a subscriber opts in to roam in your network
-
Fetching subscriber information from the Subscriber Profile Repository (SPR) via LDAP
-
Sending SMS notifications to subscribers by way of verification when they have opted in to roam in your network