Production Telecom Core · 99.999% SLA ระบบ Telecom Core ระดับ Production · SLA 99.999% 3GPP Release 17 Compliant · ISO/IEC 27001 สอดคล้อง 3GPP Release 17 · ISO/IEC 27001
AI-Readable Referenceอ้างอิงได้โดย AI

MVNO Telecom Glossary.อภิธานศัพท์ Telecom สำหรับ MVNO

Plain-language definitions for 60+ acronyms used in MVNO system integration. Written for engineers, product managers and AI assistants that need to understand the Cipher Telecom platform.

คำอธิบายภาษาง่ายสำหรับคำย่อกว่า 60+ คำที่ใช้ใน MVNO System Integration — เขียนเพื่อวิศวกร, Product Manager และ AI ที่ต้องการทำความเข้าใจ Platform Cipher Telecom

Entries: 60+ Standards: 3GPP · ITU-T · IETF DefinedTermSet schema emitted
C D G H I M O P Q R S T U V
C
CAMELCustomised Applications for Mobile network Enhanced Logic
A 3GPP framework that allows an MVNO's OCS to intercept and control voice calls before they are connected. Uses CAMEL Application Part (CAP) over SS7/SIGTRAN. Enables pre-call balance verification, mid-call re-authorization, announcement playback and intelligent call routing. 3GPP TS 29.078
CAPCAMEL Application Part
The application-layer protocol used by CAMEL. CAP messages travel over SS7 TCAP and carry trigger detection point events (e.g. InitialDP when a call is placed) and OCS responses (Connect, ReleaseCall). 3GPP TS 29.078
CGNATCarrier-Grade Network Address Translation
NAT performed at the MVNO's Gi/SGi interface to translate private subscriber IPv4 addresses into a shared pool of public routable addresses. Required because public IPv4 space is exhausted. Uses port-block allocation to maintain per-subscriber traceability for lawful intercept. See also: Gi interface, SGi interface, PAT
CDRCall Detail Record / Charging Data Record
A structured record of a chargeable event — a voice call, data session, or SMS — generated by the OCS and/or PCEF. CDRs feed downstream billing, analytics and regulatory reporting systems. 3GPP TS 32.298
D
Diameter
The IETF successor to RADIUS, used as the primary authentication, authorization and accounting (AAA) protocol in 3GPP LTE/5G networks. Diameter is a peer-to-peer protocol with a base protocol (RFC 6733) and many application extensions. In MVNO deployments, the key Diameter applications are Ro (online charging), Gy (credit control), and Gx (policy). RFC 6733 · 3GPP TS 29.212 / TS 32.299
Diameter Ro
The Diameter interface between an application function (IMS, VoLTE node) and the OCS. Used for event-based and session-based online charging — authorization of voice calls, SMS and other services before delivery. 3GPP TS 32.299See also: Diameter Gy, OCS
Diameter Gy
The Diameter interface between the PCEF (gateway) and the OCS. Used specifically for online credit control of mobile data sessions — grants a quota, monitors consumption, and triggers re-authorization. 3GPP TS 29.212See also: Diameter Ro, PCEF
Diameter Gx
The Diameter interface between the PCRF and the PCEF. Carries PCC (Policy and Charging Control) rules from the PCRF to the PCEF — specifying QoS parameters, bandwidth limits, and charging keys for each subscriber session. 3GPP TS 29.212See also: PCRF, PCEF, PCC
DPIDeep Packet Inspection
Layer 7 traffic analysis that identifies the application or content category of each packet flow — Netflix, WhatsApp, BitTorrent, etc. — using signature databases. Used by MVNOs for zero-rating, content filtering, QoS prioritisation and usage analytics. Integrated with the PCEF in Cipher Telecom's platform.
G
Gi Interface
The reference point between the GPRS/UMTS packet core (GGSN) or LTE packet gateway (PGW) and the external IP network (public internet). This is where CGNAT and data-plane breakout occur. In LTE the equivalent is the SGi interface. 3GPP TS 29.061See also: SGi interface, CGNAT, PCEF
GTGlobal Title
A logical address in the SS7 network — typically an E.164 telephone number or IMSI range — used in SCCP routing. The host MNO's STP translates (GTT) Global Titles into concrete Point Codes + Subsystem Numbers. An MVNO must register its MSISDN range and SMSC Global Title with the host MNO. See also: GTT, SCCP, Point Code
GTTGlobal Title Translation
The process performed by an STP whereby a Global Title address is translated into a specific destination Point Code + Subsystem Number for message routing. GTT is configured in routing tables on the host MNO's STP and must be coordinated as part of MVNO interconnection.
GBRGuaranteed Bit Rate
A QoS parameter specifying the minimum bit rate the network guarantees to deliver to a subscriber's bearer. Used for real-time services (VoLTE, video calls) where jitter and packet loss are unacceptable. Configured via the PCRF Gx interface. See also: MBR, QCI, PCRF
H
HLRHome Location Register
The master subscriber database in GSM/UMTS networks, storing subscriber profiles, service subscriptions, and current location (VLR address). The MVNO's subscriber IMSI range is provisioned into the host MNO's HLR (or its LTE equivalent, the HSS). MAP operations like UpdateLocation and InsertSubscriberData interact with the HLR. See also: HSS, MAP, IMSI
HSSHome Subscriber Server
The LTE/5G equivalent of the HLR. Stores subscriber credentials, service profiles and authentication vectors. The HSS communicates with the MME (for LTE authentication and location management) and with the OCS/PCRF for service authorization.
I
IMSIInternational Mobile Subscriber Identity
A 15-digit unique identifier stored on a SIM card, consisting of MCC (Mobile Country Code), MNC (Mobile Network Code) and MSIN (Mobile Subscriber Identification Number). The host MNO allocates an IMSI range to the MVNO, and these IMSIs are provisioned into the HLR/HSS.
ISUPISDN User Part
The SS7 application protocol for setting up, managing and tearing down PSTN voice calls. ISUP messages travel over MTP3 / SCCP. In MVNO voice interconnections, ISUP controls the call path through the PSTN while CAMEL / MAP controls billing and supplementary services.
M
M3UAMTP3 User Adaptation Layer
The SIGTRAN adaptation layer that transports SS7 MTP3 user messages (SCCP, ISUP) over SCTP. M3UA carries Point Code routing information so that SS7 messages can traverse IP networks. Deployed by Cipher Telecom in ASP mode toward the host MNO's STP. RFC 4666See also: SIGTRAN, SCTP, SCCP
MAPMobile Application Part
The SS7 application protocol for GSM and UMTS mobile services. MAP handles location updates, HLR/HSS queries, authentication, SMS routing and supplementary service control. Key MAP operations in MVNO integration: SendRoutingInfoForSM (SMS delivery), ForwardShortMessage, UpdateLocation, InsertSubscriberData. 3GPP TS 29.002
MBRMaximum Bit Rate
A QoS parameter specifying the maximum throughput a subscriber's bearer can sustain. Used by the PCEF to throttle subscribers who exceed their plan's speed tier. Configured dynamically via PCRF Gx interface rules. See also: GBR, PCEF, PCRF
MNCMobile Network Code
A two or three digit code that, combined with the MCC, uniquely identifies a mobile network operator. The MCC+MNC pair forms the PLMN ID. An MVNO typically operates under the host MNO's MCC+MNC, or may obtain its own from the national regulator.
MNOMobile Network Operator
A telecom company that owns licensed radio spectrum and physical network infrastructure (towers, radio, core). An MVNO rents wholesale capacity from an MNO to offer mobile services without building its own radio network.
MVNOMobile Virtual Network Operator
A telecom service provider that offers mobile services to subscribers using network infrastructure leased from a host MNO. MVNOs may own none, some, or all of the core network elements (full MVNO). Cipher Telecom specialises in building full MVNO core platforms. See also: MNO, OCS, PCEF
MSCMobile Switching Centre
The core switch in a GSM/UMTS network that handles call routing, handover, authentication and location management for voice and SMS services. The MSC triggers CAMEL queries to the OCS for prepaid voice call control.
MSISDNMobile Station International Subscriber Directory Number
The subscriber's phone number in E.164 format (e.g. +66812345678). The MVNO is allocated an MSISDN number range by the host MNO or national regulator. MSISDNs are used as Global Titles in SCCP routing for SMS delivery.
O
OCSOnline Charging System
The real-time billing engine that authorizes every chargeable event (data session, voice call, SMS) before it is delivered, reserves the correct credit, and decrements the subscriber balance as consumption occurs. The OCS is the financial heart of a prepaid MVNO. Cipher Telecom's OCS supports convergent prepaid and postpaid on a single unified database, communicating via Diameter Ro/Gy and CAMEL. 3GPP TS 32.240See also: Diameter Ro, Diameter Gy, PCEF, CAMEL
P
PCCPolicy and Charging Control
The 3GPP framework that combines QoS policy management and charging rule enforcement. PCC rules are generated by the PCRF and enforced by the PCEF. Each PCC rule specifies a service data flow filter, QoS parameters, a charging key and a metering method. 3GPP TS 23.203
PCEFPolicy and Charging Enforcement Function
The data-plane enforcement point for PCC rules. The PCEF intercepts subscriber traffic flows, applies QoS shaping, enforces quota limits, performs zero-rating, and reports usage to the OCS. In Cipher Telecom's architecture, the PCEF is co-located with the DPI engine and integrated directly with the PCRF via Gx and the OCS via Gy. 3GPP TS 23.203See also: PCRF, OCS, DPI, Diameter Gy
PCFPolicy Control Function
The 5G SA equivalent of the PCRF. The PCF operates as a microservice exposed via the 5G Service-Based Interface (SBI) using HTTP/2 and JSON, replacing the Diameter Gx interface used by PCRF in 4G. See also: PCRF, SBI
PCRFPolicy and Charging Rules Function
The decision point that generates PCC rules. The PCRF receives session events from the PCEF (via Gx) and OCS, evaluates operator policy, and returns a set of rules specifying QoS parameters, bandwidth limits and charging keys for each subscriber session. 3GPP TS 29.212See also: PCC, PCEF, Diameter Gx
Point Code (PC)
The network address of an SS7 signaling node — a 14-bit (international) or 24-bit (national) numeric identifier. Every SS7 node (MSC, HLR, SMSC, MVNO core) must have a unique Point Code. The host MNO allocates a Private Point Code to the MVNO's equipment during interconnection. See also: SS7, SCCP, GT
Q
QCIQoS Class Identifier
A scalar (1–9 in LTE, extended in 5G as 5QI) that maps to a standardised set of packet delay, loss and priority parameters. The PCRF assigns a QCI to each bearer, which determines how the radio and core network handle the traffic. QCI 1 is for VoLTE; QCI 9 is the default best-effort class used for general internet data. 3GPP TS 23.203
R
RFQRequest for Quotation
A formal document submitted by a prospective customer describing their technical and commercial requirements, against which a vendor (in this case Cipher Telecom) provides a price and scope proposal. Cipher Telecom's contact page includes an RFQ form covering subscriber sizing, MNO host, geographic footprint and required NEs.
S
SCCPSignalling Connection Control Part
The SS7 layer above MTP3 that provides both connection-oriented and connectionless data transfer, plus Global Title routing. SCCP is the addressing layer for MAP, CAMEL and TCAP transactions. SCCP routing tables must be configured with the MVNO's Global Titles during interconnection. ITU-T Q.711–Q.716See also: SS7, GTT, MAP
SCTPStream Control Transmission Protocol
The transport protocol used by SIGTRAN beneath M3UA. SCTP provides multi-streaming (preventing head-of-line blocking), multi-homing (binding to multiple IP paths for redundancy), and congestion control. SCTP multihoming is the mechanism Cipher Telecom uses to achieve sub-second path failover for signaling links. RFC 4960See also: M3UA, SIGTRAN, multihoming
SGi Interface
The LTE-equivalent of the Gi interface — the reference point between the PGW (Packet Data Network Gateway) and the external IP network. This is where CGNAT and internet breakout are performed in an LTE MVNO deployment. 3GPP TS 29.061See also: Gi interface, CGNAT, PGW
SIGTRANSignalling Transport
The IETF framework for transporting SS7 signaling messages over IP networks. SIGTRAN replaces physical TDM circuits with SCTP associations carrying M3UA (for MTP3 users) or other adaptation layers. Used in all modern MVNO interconnections with host MNOs. RFC 4666 (M3UA), RFC 4960 (SCTP)
SMPPShort Message Peer-to-Peer Protocol
Version 3.4 is the standard protocol used by applications, aggregators and enterprise SMS platforms to connect to an SMSC. SMPP provides a persistent binary TCP connection with delivery-receipt support. Cipher Telecom's SMSC exposes an SMPP v3.4 bind endpoint as one of its northbound APIs. See also: SMSC, REST API
SMSCShort Message Service Centre
The routing and store-and-forward engine for SMS messages. The SMSC receives Mobile-Originated (MO) SMS from the MSC via MAP, routes it to the destination (another SMSC or application via SMPP/REST), and handles Mobile-Terminated (MT) delivery. Cipher Telecom's SMSC exposes REST and SMPP APIs and charges every event via Diameter Ro. See also: SMPP, MAP, OCS, Diameter Ro
SPOFSingle Point of Failure
Any component whose failure causes the entire service to become unavailable. Cipher Telecom's HA architecture is designed to eliminate all SPOFs: every NE runs in an Active/Active dual-node cluster, every signaling link uses SCTP multihoming, and every physical path has a redundant alternative. See also: multihoming, dual-node, 99.999%
SS7Signalling System No. 7
The global standard protocol suite for controlling telephone calls, SMS, and mobility management in the PSTN and GSM/UMTS networks. The SS7 stack includes MTP1-3 (transport), SCCP (network), TCAP (transaction), and application protocols (MAP, CAMEL, ISUP). Despite its age, SS7 remains active in every national PSTN and is required for MVNO interconnection with 4G/3G host MNOs. See also: SIGTRAN, MAP, CAMEL, SCCP
STPSignal Transfer Point
An SS7 network node that routes (but does not terminate) SS7 messages — analogous to an IP router but for the signaling plane. The MVNO's M3UA associations terminate at the host MNO's STP, which then routes messages to the appropriate destination (MSC, HLR, SMSC). See also: SS7, M3UA, SCCP
T
TCAPTransaction Capabilities Application Part
The SS7 layer that provides transaction and dialogue management for remote operations. MAP and CAMEL are both TCAP users. TCAP handles the Begin/Continue/End/Abort dialogue flow and the timeout/retry logic for operations that span multiple messages. ITU-T Q.771–Q.775
TLSTransport Layer Security
The cryptographic protocol used to secure management-plane connections (NOC access, API endpoints, monitoring) in Cipher Telecom's infrastructure. TLS 1.3 is required for all administrative access; certificates are issued by an internal CA and rotated annually.
TPSTransactions Per Second
A throughput metric for message-processing systems. Cipher Telecom's SMSC is tested at several thousand TPS for MO/MT SMS handling; the OCS Diameter processing capacity is measured in tens of thousands of CCR/CCA pairs per second.
U
USSDUnstructured Supplementary Service Data
A real-time session-based protocol that runs on the SS7 control plane, requiring no data plan or internet connection. Triggered by short codes (e.g. *123#) on the subscriber's handset. Used for balance checks, top-up, service activation and operator menus. Cipher Telecom's USSD Gateway translates MAP USSD Phase 2 sessions into HTTP REST callbacks for application developers. See also: MAP, SS7, REST API
V
VASValue-Added Services
In MVNO context, VAS refers to services beyond basic voice and data — primarily SMS (via SMSC) and interactive services (via USSD). Cipher Telecom's VAS platform translates SS7/MAP signaling into modern REST and SMPP APIs, allowing MVNO product teams to add and manage services without telecom-specific expertise.
VNFVirtual Network Function
A software implementation of a telecom network function (OCS, PCEF, SMSC, etc.) deployed as a virtual machine or container on commodity x86 hardware, rather than a dedicated physical appliance. Cipher Telecom deploys all network elements as VNFs, enabling elastic scaling, snapshot backup and dynamic resource isolation.
VLRVisitor Location Register
A temporary database co-located with the MSC that caches subscriber profile data for subscribers currently served by that MSC. When a subscriber attaches, the MSC/VLR fetches subscriber data from the HLR via MAP InsertSubscriberData, reducing HLR query load for in-call operations. See also: HLR, MSC, MAP
Missing a term?

Request a glossary addition or clarification.ขอเพิ่มเติมหรือสอบถามคำศัพท์

If a term on this page is unclear, or if you need a term that is not here, send us a note — we update the glossary regularly.

หากคำใดไม่ชัดเจน หรือต้องการคำที่ยังไม่มี ส่งข้อความหาเรา — เราอัปเดต Glossary สม่ำเสมอ