Operator systems either side of the OSS/BSS line: provisioning a service on a network, and turning its usage into money.
12 published across 6 topics.
Telecom domain fundamentals59 short answers on one page, for revising rather than studying.Subscriber lifecycle, service activation, and order-to-activate orchestration.
An activation half-succeeded and nobody owns the divergence. Detect it by reconciling the network's view against the subscription record, classify which side is wrong, re-drive fulfilment from stored intent rather than patching either side, and treat the unbilled period as a decided commercial policy.
The order is decomposed against the product catalogue into technical tasks on separate systems, each with its own latency and failure mode. Because nothing spans them transactionally, correctness comes from idempotent tasks, compensating actions, a fallout queue and jeopardy monitoring.
Physical and logical inventory, resource assignment, and reconciling discovery with records.
Correlation is a traversal of the inventory graph, and an upgrade changes exactly the part being traversed. Model planned as well as as-built state, carry the set of resources a change touches as data, scope suppression to that set rather than to the time window, and confirm recovery positively.
Model physical equipment, the logical resources riding on it and the services consuming them as separate layers linked by assignment, with an explicit resource lifecycle. Discovery does not overwrite the record: the inventory owns intent, the network owns observed state, and differences are classified faults.
Usage record collection, deduplication, rating and real-time charging.
Every reservation must decrement the shared pool and the member's own counter atomically, granting the smallest of the two remainders. That makes the group rather than the subscriber the serialisation point, and it means a member with headroom can still be refused because the pool is gone.
Mediation normalises and deduplicates records against a persisted key window sized to the worst observed lateness, then rating prices each record by its event time against an effective-dated tariff version. Prepaid is not merely faster postpaid; it reserves quota against a live balance.
Bill cycles, invoicing, disputes, leakage detection and revenue assurance.
Restart rather than rerun. The run is not a transaction but a sequence of per-account commitments, so each account must be either fully billed or untouched, charge assembly must be deterministic from inputs frozen at cut-off, and quarantining the offending accounts beats missing the cycle.
A cycle closes a period, assembles recurring, usage and one-off charges, applies discounts and tax, then issues an invoice that must never be edited afterwards. A mid-cycle change produces a credit for unused advance rental plus a prorated new charge, which is what customers dispute.
The domain split, catalogue-driven design, and decomposing a monolithic stack.
Three separate requests hide in that sentence. Pricing new sales is a new catalogue version; repricing the base is a commercial migration per subscription with notice; changing contents is both. The usual defect is not an edited offering but a shared object one level down that both versions reference.
BSS owns what was sold and what it costs; OSS owns how it is delivered on the network, and the boundary survives because the two change at different rates. Catalogue-driven design only removes code if fulfilment and rating read the same model, and decomposition proceeds by cohort behind a facade.
Service models, slicing and edge, at the level an IT engineer needs.
Mostly the work of identifying who loses service and moving them, which network data alone cannot tell you. Device capability comes from the IMEI, packet voice needs subscription and IMS provisioning in bulk, and the machine-to-machine base is the population that cannot be reached by a campaign.
They turn a service into a parameterised, capacity-constrained thing with a location. The catalogue must model performance characteristics and a site, the order flow gains a serviceability and reservation step that can legitimately say no, and SLA measurement has to feed billing.