Menu
Trending Search
Trending Products
GPON vOLT ZH-vOLT32 GPON vOLT ZH-vOLT32
GPON vOLT ZH-vOLT32
$56.90
GPON vOLT ZH-vOLT16 GPON vOLT ZH-vOLT16
GPON vOLT ZH-vOLT16
$49.60
XG-PON OLT ZH-VOLTXG64 XG-PON OLT ZH-VOLTXG64
XG-PON OLT ZH-VOLTXG64
$161.00
GPON OLT ZH-1GS(LI) GPON OLT ZH-1GS(LI)
GPON OLT ZH-1GS(LI)
$125.00
GPON vOLT ZH-vOLT64 GPON vOLT ZH-vOLT64
GPON vOLT ZH-vOLT64
$95.50

Billing Every Unit on a Shared PON: Authentication, Accounting and Speed Profiles for Apartments and Hotels

Author: AINOPOL Release time: 2026-10-26 06:05:25 View number: 83

Key points: One PON can put every apartment in a building online, but that does not mean you can bill each one. Accurate billing depends on three things being in place at the same time: mapping a specific PON port and ONU to a specific unit number (authentication), pushing a different speed profile to different units (authorization), and recording the start, end and volume of every session so the numbers reconcile with the invoice (accounting). Miss any one of the three and the monthly statement will contradict the network. What follows is the deployment order, the decisions that matter, and where projects usually go wrong.

Authentication, authorization and accounting are three separate jobs

Plenty of projects pass acceptance with "it browses, and the speed test is fine" and consider the network finished. The problem only shows up when someone asks to charge per unit: nobody knows which fibre belongs to which apartment, so the whole building is billed as one; changing a package means going to the equipment room and editing the OLT; a resident cancels service and the system keeps billing them. Those three symptoms are three missing layers, not one.

The full chain looks like this: the ONU comes online, the OLT inserts location information into the subscriber's DHCP or PPPoE traffic, the authentication server decides which account that location belongs to, a policy is pushed for that account's profile, usage is reported throughout the session, and the session is written to a billing record when it ends. Any step filled in by a spreadsheet works at fifty units and collapses at five hundred.

A practical test: unplug one unit and ask operations to say, within five minutes, which apartment that was, what profile it had, and when it last paid. If nobody can answer, the authentication layer does not exist yet, whatever the speed test says.

Three ways to authenticate a unit

There is no single right answer. It depends on whether the building houses long-stay tenants, short-stay guests, or devices that never log in by hand — set-top boxes, door locks, meters, cameras.

ApproachBest fitLocation accuracyMain cost
PPPoELong-stay apartments, corporate housing, anything needing per-account session timeHigh: one account, one session, clean duration and volumeEvery device needs credentials; set-top boxes and locks cannot dial
DHCP with Option 82Set-top boxes, smart locks, CCTV, IoT endpointsHigh: the circuit-id inserted by the OLT identifies the physical portEntirely dependent on OLT capability — verify before purchase
IPoE with a portalShort-stay rentals, guest networks, day passesMedium: first connection is redirected to a login pageTenants changing devices re-authenticate constantly

Hotels and apartments rarely pick one. The usual pattern is two tracks in parallel: human devices on PPPoE or a portal, and set-top boxes, locks and meters on DHCP with Option 82, separated on the authentication side by MAC range or service VLAN. Skip that separation and the billing engine will eventually kick a set-top box offline as an unpaid subscriber.

One question has to be settled before you buy hardware: does the OLT support DHCP Option 82 insertion, and can the circuit-id format be customised? Some entry-level OLTs accept only a fixed string, so every subscriber carries identical location data and the whole point is lost. Do not take a datasheet line for this — ask for a packet capture or a configuration screenshot.

Building a circuit-id that points back to apartment 1203

The circuit-id is the string that turns a physical port into a readable address. Its real value is not sophistication but continuity: when a faulty ONU is swapped, the MAC changes, and the account and the invoice should not change with it.

The common approach is a layered code — building, entrance, floor, unit, service type — written as 03-01-12-1203-I. Fix the field widths and both the billing system and the ticketing system can parse it without a lookup table. The service-type digit matters more than people expect: one unit may hold broadband (I), IPTV (T) and voice (V) at the same time, and collapsing them into one identifier either triple-bills or under-bills that apartment.

The code has to match what is written on the hardware. Splitter ports, joint closure labels and patch cords in the riser all need to follow the same hierarchy. One wrong label during installation costs hours of site verification later.

What RADIUS should hand down

A successful authentication only establishes who the subscriber is. Authorization decides how much they get. The reply attributes should cover four groups at minimum: identity and location (User-Name, Calling-Station-Id, NAS-Port-Id), addressing (Framed-IP-Address or a pool), time control (Session-Timeout, Idle-Timeout), and policy (Filter-Id or a vendor-specific attribute pointing at a named shaping profile).

On the accounting side, watch Acct-Status-Type, Acct-Session-Time, Acct-Input-Octets and Acct-Output-Octets, and keep the interim update interval short. The one-hour default means a power cut or a pulled fibre can lose up to an hour of usage. Five to ten minutes keeps the loss tolerable without loading the server.

Note that mapping a profile name to an actual shaping template uses vendor-specific attributes, and the attribute numbers differ between vendors. Copying another vendor's configuration will silently fail. Work through your own OLT manual line by line, then dial three test accounts on three different profiles and confirm each one lands on the right template.

Keep billing policy separate from how shaping is implemented

The most common structural mistake is writing the speed profile directly into each ONU's configuration file. The result is one template per subscriber: five hundred units, five hundred configurations. Upgrading a package means re-provisioning on site or over the air, and one typo becomes one complaint.

The correct split is two layers. RADIUS decides only which profile an account belongs to — 100M, 300M, 500M. The OLT keeps a handful of shaping templates, one per profile, and the template itself defines committed rate, peak rate and burst behaviour. Changing a package then means editing one account attribute; the next dial-in picks it up and nothing on site moves.

How those template values should be set depends on the shared upstream and is a topic of its own. The principles are simple: few templates, names a technician can read at a glance, and no change released to everyone before it has been tested on two or three accounts.

Trial, suspension and non-payment

On an invoice these look like three status values. On the network they are three different procedures, and getting them wrong means either cutting off a paying tenant or billing someone who already cancelled.

  • Trial: short Session-Timeout, a separate address pool, and a trial flag on the accounting record so trial traffic never contaminates a real invoice. When the trial ends, drop to a very low profile rather than cutting the line — it converts better.
  • Suspension: do not delete the account and do not release the IP or VLAN. Cut the profile to the minimum and keep the link up. One dial-in restores service when the tenant pays, with no site visit.
  • Non-payment: return Access-Reject from RADIUS rather than shutting the PON port on the OLT. Rejection is reversible, immediate and leaves a clear audit trail. Shutting a port is manual, slow to restore, and takes every other service on that port down with it.

There is a knock-on effect worth planning for: if the set-top box shares the broadband account, a non-payment cut also blacks out the television. Either authorize by service type, or put the set-top box on its own service VLAN and its own authentication domain so "cut broadband" and "cut TV" remain two separate actions.

Six reasons the bill never matches the network

When month-end figures disagree, the billing software is rarely at fault. The information chain broke somewhere on the network side. In rough order of frequency:

  1. ONU swapped without re-binding. Projects that identify accounts by MAC end up billing the old device while the new one fails authentication.
  2. circuit-id and unit number out of step. A mislabelled patch cord means the system shows 1203 online while 1204 is actually using the service.
  3. Sessions that never close cleanly. Power loss, an unplugged fibre or a broken span sends no stop record — only interim updates cover the gap.
  4. Several accounts on one unit. A tenant adds a router and shares it with a neighbour, or one apartment holds both a broadband and an IPTV account but is settled as a single unit.
  5. Unauthorized sharing. Extending a drop into a common area can only be stopped with port isolation and admission control.
  6. Different cycle start dates. The system runs on calendar months while the contract starts on the activation date, and traffic crossing midnight is where the error hides.

Nine checks before you go live

This stack cannot be accepted on the basis of "it looks fine". Run the list below end to end, and only start charging when all nine pass.

  1. Pick three units at random; each circuit-id is visible in the RADIUS log and matches the unit number.
  2. Simulate an ONU swap: replace the unit, complete the re-binding, and the account comes back online with its history intact.
  3. Test three units on each of the three profiles, with real traffic rather than an idle line, and confirm the rates match.
  4. Pull a fibre mid-session and confirm the break appears in the system within five to ten minutes.
  5. Reject an account for non-payment, then clear it, and confirm service returns in under a minute.
  6. Set-top boxes, locks and cameras are not rejected as unauthenticated users.
  7. Given a unit number, one query returns its session history, current profile and payment status.
  8. Run a sharing test between two adjacent units: VLAN and port isolation hold and neither sees the other.
  9. Run one full billing cycle — activation, mid-cycle suspension, restoration, month-end invoice — and reconcile hours and volume by hand.

Checks three and nine are the ones people skip. The first is often run at three in the morning on an empty line, which produces a beautiful number and no information. The second requires actually crossing a month boundary; plenty of projects have been live for three months without ever completing one full cycle.

Closing

Per-unit billing looks like a software and accounting problem. It is really a binding problem between three things: the PON port, the physical location and the account. Get the binding clean and the billing platform is just arithmetic. Leave it vague and the most expensive platform on the market will still produce an estimate. A shared PON is no obstacle to precise charging — provided the circuit-id, the service type and the profile layers are designed during deployment rather than reconstructed from labels after the first disputed invoice.

Contact us

If you are designing a per-unit billed network for apartments, hotels or a campus and need to confirm Option 82 support, shaping templates and authentication integration on your OLT, send us your current setup.

Related Products
GPON vOLT ZH-vOLT32 GPON vOLT ZH-vOLT32
GPON vOLT ZH-vOLT32
$56.90
XG-PON OLT ZH-VOLTXG64 XG-PON OLT ZH-VOLTXG64
XG-PON OLT ZH-VOLTXG64
$161.00
GPON vOLT ZH-vOLT64 GPON vOLT ZH-vOLT64
GPON vOLT ZH-vOLT64
$95.50
Nginx server needs to configure pseudo-static rules, click View configuration method