How users authenticate
Do you have a combination of PPPOE, Portal, RADIUS or WiFi?
• Suitable to the target
Which projects do this program fit?
Even if the scene is the same, it will be necessary to judge the current network conditions and project responsibilities.
- Operators preparing to conduct ISP operations in overseas markets
- Broadband or public network that requires both PPoE and Portal certification
- Third-party fee collection systems, financial platforms or local tax systems already exist and require projects to be docked with NATSHEL_AUTH_BILLING
• Four preliminary questions
Common network issues and priorities
The right construction routes can be determined more quickly, starting with network control points, identification sources, interfaces and operational objectives.
Who manages the set and charges?
Opening accounts, packages, balances, shutdowns, payments, arrears and refunds are the responsibility of the NATSHEL_BRAND platform or a third-party fee system?
How to match the charges and taxes?
What interfaces are open between the third-party fee system and the tax system, and how do user, order, tax, invoice and status fields correspond?
Establishment of local operating conditions
Who is responsible for the ISP's licensing, operator lines, tax rules, data storage, customer services and on-site transport?
:: Establishment conditions
Conditions required for the programme to land
Pre-checking of networks, interfaces and operating conditions helps to reduce duplication in implementation.
- Locally available operator lines, export and certification control points
- Clear PPOE, Portal, RADIUS and user life cycle design
- Head of interface, testing environment and liaison for third-party charge system and tax systems
- Local ISP operations, taxes, data and customer service requirements as identified by project parties
04. NatShell What to do
Platform, gateways and supporting capacities work in tandem
The product mix is determined according to project objectives and current network conditions, and the synergies between third-party systems, network equipment and implementation services are identified.
NATHHELL_AUTH_BILLING_PLATFORM
Manages user, account number, package, balance, permissions, online sessions and back-up processes.
Conditions of application: The main data, orders and financial liabilities with the third-party fee system need to be clearly identified in the interface programme.
PPoE/ RADIUS authentication
Organization of account authentication, attribute distribution and session coordination for fixed broadband or operator access links.
Application conditions: protocols, fields and connecting conditions that rely on BRAS, BNG, NAS or other network equipment.
Portal Authentication
A certification portal, user identification and clearance are provided for WiFi, visitors or public access sites.
Conditions of application: authentication page, identification and release links are combined with gateways, AC and local business process recognition.
Fee-to-tax interface
Exchange of user, order, payment, invoice or status information with third party fee systems, payment processes and tax systems on a conditional basis.
Application conditions: All systems are not automatically compatible; interface fields, currencies, tax rates, notes and unusual handling are subject to third-party documentation and joint testing.
05 Product combinations
Select the right product mix by current network size
Select the right product mix based on current network equipment, network size, interface conditions and construction objectives.
PPPOE Broadband Operation
- NATHHELL_AUTH_BILLING_PLATFORM
- PPPoE / RADIUS
- Bras / BNG / NAS
- Set and stop rules
For fixed broadband or dial-up access, network equipment and RADIUS properties are recognized.
Portal Public Access
- NATHHELL_AUTH_BILLING_PLATFORM
- Portal Authentication
- NATHHEL_AUTH_GATEWAY OR CURRENT AC
- User and Suite Process
For WiFi or public access, identification entrances, permissions and clearances are specified.
Third-party fee and tax synergies
- NATHHELL_AUTH_BILLING Platform
- Third-party fee system interface
- Tax system interface
- Order, payment and invoice status synchronized
It is necessary to identify which systems are the main system and define fields, status, failure re-try and reconciliation responsibilities item by item.
Cases
Practical reference for similar projects
A representative case is first looked at, and more project titles are used to understand the accumulation of services in the relevant scenes.
• Conditions for implementation
Key issues to be identified before the project lands
Pre-defined networks, equipment, interfaces and conditions of service would help to develop an implementable and verifiable construction programme.
Basis of implementation
The final programme is based on field-based pings, equipment models, interface documents and joint testing.
NATSHEL_BRAND provides NATSHEL_AUTH_BILLING and conditional interface capabilities, not to obtain local ISP operating licences instead of the project party.+
The project research phase will identify the scope of implementation, co-responsibility and certification modalities in relation to conditions on the ground.
Tax rates, invoices, notes and tax returns are confirmed by the project party and local professional bodies.+
The project research phase will identify the scope of implementation, co-responsibility and certification modalities in relation to conditions on the ground.
Third-party fee and tax systems must provide accessible interfaces, test environments and matchmaking support.+
The project research phase will identify the scope of implementation, co-responsibility and certification modalities in relation to conditions on the ground.
Local operators are not committed to the quality of their lines, payment success rates or commercial operating gains.+
The project research phase will identify the scope of implementation, co-responsibility and certification modalities in relation to conditions on the ground.
• Frequent problems
The question of whether the project is viable will be answered first.
Could PPoE and Portal be used in the same project?+
While they can be designed for fixed broadband, wireless or visitor access objects, account numbers, packages, online status and network control points require uniform planning.
Can local fees and tax systems be directly connected?+
You need to get interface documents, test environments, fields and permissions first. The system has the same name or interface style and cannot replace actual joint testing.
Does NatShell have responsibility for local tax compliance?+
NATSHEL_BRAND does not replace local tax or legal judgement and can be docked to the system in accordance with recognized interfaces and operating rules.
Quick consultation
Tell us about your scene and get a targeted program.
Submission of network size, current network equipment, key requirements and contact calls will assist in collating product portfolios and implementation pathways.