Precision flow counts are the core capabilities of network billing systems in special scenarios, and are part of a common time-to-time calculation that cannot be replaced by cost. The requirements for accuracy are even higher: accurate traffic statistics, how quotas are distributed, and what is done when they are exhausted.
NatShell V7 Authentication & Billing supports precision flow billing: it is distributed through traffic quotas and is matched with the accuracy charge for NAC equipment. Users receive flow value parameters after certification, which are based on actual user consumption.
Why do you need a local NAC bill?
The unique feature of the satellite scenario is that bandwidth costs are extremely high, network links are unstable and delays are great. If the billing depends entirely on clouds, there will be a gap in traffic statistics when the chain breaks. NAC equipment is placed locally as a charge node, and even if cloud billing is not connected for network reasons, NAC can delineate users after the user's flow expires and avoid waste.
Another value of local billing is the cost of offline network separation. Satellite traffic is expensive and local on-line flows are not accrued. V7 supports the off-grid segregation charge through RADIUS interfaces, supports local stream media and local caches, and reduces satellite bandwidth consumption. User access within local area networks is free of charge, except for out-net traffic, which is included in the package.
Flow quotas and due processing
The key to precision flow billing is the accurate implementation of traffic quotas. After the system has a flow value parameter, NAC controls the flow available to users by parameters; when the traffic runs out, access is either banned or used at a slower rate, and rules are defined by the operator in its strategy.
Satellite scenes also require Portal to experience no damage due to high delays. V7 uses a two-storey structure of cloudy Portal plus local NAC caches, downloads Portal pages to local NAC caches and achieves PORTAL seconds, which users can see quickly even with high delay in satellite links.
Satellite scenario operational support
The operating model for satellite billing is different from the home campus flats, with greater emphasis on unmannedity. V7 supports users moving to a counter-registration page via Portal and registering and paying through mobile phone numbers; it can be opened by self-service payments from the self-help system.
Localization is also a mandatory course for satellite projects: support multilingual Portal pages, local mobile payments (e.g. M-Pesa, MTN Mobile Money, etc.) and cash replenishment channels. Access to specific payment modalities depends on the business arrangements of local payment platforms and operators.
Exact validation of flow billing
The flow billing is sensitive to accuracy and requires verification before going online: whether the starting and end of traffic statistics are accurate, whether NAC local billings match cloud accounts and whether quota processing is expected. The precision costing capacity described in the information needs to be field tested in specific projects in conjunction with NAC equipment models, deployment patterns and flow models.
The rules of operation are set before the line is made. Users who charge by traffic are either zero flow or turn down for a month, and when exhausted, access is prohibited or slowed down, often with rigid requirements in the bidding parameters; how the inner network is divided and which domain names go to local caches are confirmed together with field peddling. The more detailed the rules are, the less disputes will be raised after the line has been reached.
The way in which authentication and billing are linked is also well documented on satellite scenes. V7 supports various types of authentication, such as WebPortal, PPPoE, 802.1X, where webPortal is used to coordinate access and billing with NAC; MAC Seamless Authentication supports the first certification of terminals without duplicate passwords; supports IPv4/IPv6 double-tock access, which can be accessed by different end types on board ships. The selection of the authentication method follows the site terminals and bandwidth conditions, and certification page-strained options experience poor experiences on high delay chains, which is also the starting point for PORTAL local cache design.
Security strategies for satellite scenarios are also not safe. V7 supports dual-element authentication, sensitive word management, real name authentication interfaces, cell phone numbers, identity cards, and match names to prevent false identification registration; and security management functions like support for login failure automatic locking. Seaships, ocean platforms, and closed sites such as user identities can be traced back to the bottom line; multi-language Portal pages and localization payments are labeled. Safety and experience need to be designed together, so certification is too easy to be problematic and the process too cumbersome to use.
The satellite scene is delivered in a unmanned mode. At sea, the technical support team is onshore and the system supports cloud remote management; systems are automatically implemented for data backup and account data are regularly archived; user problems are resolved by self-help as much as possible, managers remotely handle emergencies. V7 supports automatic backup to servers, mail backup to manager's assigned mailbox, manual backup data to their own computer, multilevel sub-season teams and shipmasters."Nobody cares."But..."The auto-automatic, the remote, the marks left."。
The traffic statistics are aligned in advance. If the top or bottom lines add up, retransmission is not, how P2P flows are recognized, IPv4 and IPv6 are separated, these calibres are not uniform, and users and operators will speak separately. V7 precision flow billing sends quotas to NAC local execution. If local statistical results are matched with cloud accounts, then it is either a statistical starting point or an equipment difference.
The value of precision flow billing is that"How much to collect, how much to waste, and how much to keep the accounts straight.". This is not a great addition to the high cost of bandwidth, but rather a prerequisite for operational viability.