Everything worth knowing, nothing that isn't.
What each component does
IN (Intelligent Network) is the architectural concept — invented in the early 1990s — that separates call/session control from service logic. The MSC or SMSC asks an external Service Control Point (SCP) "can this subscriber do this thing?" using the INAP (Intelligent Network Application Protocol). OCS (Online Charging System) is the modern, 3GPP-defined evolution of the SCP role, focused on real-time charging and credit control — it speaks Diameter Gy/Ro for 4G/IMS, and CAMEL/INAP for 2G/3G. Together they enable prepaid SMS, real-time bundle decrement, and per-event policy enforcement.
Why it matters commercially
For prepaid operators (still the majority of the world by subscriber count), OCS is the cash register — every SMS, every minute, every megabyte hits the OCS for credit check and decrement. For A2P SMS senders, the OCS is the system that turns an A2P delivery into a billable event in the operator's revenue stream. The interlock between SMSC, SMS Firewall, and OCS is what makes operator A2P monetisation real — without OCS integration, the operator detects the A2P but can't bill it. BroadNet's SMS Firewall + A2P Monetisation product (/operators/sms-firewall) integrates with operator OCS via Diameter or INAP.
Latency, scale, and compliance angle
OCS credit-check latency budgets are tight — typically 50-150 ms for an SMS, sub-second for a voice call. OCS scale at a tier-1 operator handles 10K-100K events per second. INAP/CAMEL are still in production on 2G/3G overlays; Diameter Gy/Ro dominates on 4G/IMS. Compliance: every OCS event creates a CDR or EDR that flows to billing and revenue assurance; integrity of this data is in scope for revenue-assurance audit and for tax authority review in many markets.
Privacy and compliance considerations
OCS sees full subscriber identity (IMSI, MSISDN) and every event timestamp — it is one of the richest behavioural datasets inside an operator. PDPL and GDPR both reach OCS logs once correlated with subscriber identity. Best practice: pseudonymise OCS export feeds for analytics, retain raw OCS logs in a segregated environment with audit logging, and apply 5-7 year retention only where regulatory or tax requirements demand it.