Network sharing and 5G slicing involve a dense web of acronyms from the GSMA, 3GPP, O-RAN Alliance, ETSI, and TM Forum. This glossary explains each term in plain language, grouped by topic rather than alphabetically, so you can read it end-to-end or jump to the section you need. Where relevant, we note how each concept relates to the TEASOL Exchange Platform.
GSMA Standards and Templates
3 termsThe GSMA publishes industry guidelines that sit above the detailed 3GPP specifications. These templates define how network slices are described at the business level — the shared vocabulary that makes multi-operator exchange possible.
GST — Generic Slice Template
Defined in GSMA NG.116, the GST is a standardized list of 42 attributes that describe a network slice at the business level. It covers everything from latency and throughput to isolation level, coverage area, and supported device density. Think of the GST as the full menu of parameters any party can use to specify what a slice should deliver. TEASOL uses the GST as the foundational data model for all slice exchange operations — every supply listing and demand request is expressed in NG.116-compliant attributes.
NEST — Network Slice Type
A NEST is a specific configuration of GST attributes that describes a concrete slice category based on its service characteristics. Standard NESTs include eMBB (enhanced Mobile Broadband), URLLC (Ultra-Reliable Low-Latency Communications), mIoT (massive IoT), and V2X (Vehicle-to-Everything). Each NEST fills in particular GST fields with defined values or ranges. TEASOL supports both standard NESTs and custom templates for vertical-specific use cases like smart factories or cloud gaming.
SST — Slice/Service Type
An integer identifier (values 1 through 5 and beyond) that maps to NEST categories. SST 1 corresponds to eMBB, SST 2 to URLLC, SST 3 to mIoT, SST 4 to V2X, and SST 5 to HMTC (High-Performance Machine-Type Communications). The SST is the compact, machine-readable label that the network uses to classify slice types at a high level.
3GPP Network Slice Architecture
6 terms3GPP defines the technical architecture for how network slices are instantiated, identified, and selected within a 5G system. These are the building blocks that turn a business-level slice description into a running network service.
- NSI
- Network Slice Instance. A deployed, running network slice with all its required network functions, resources, and configurations active. An NSI is the runtime realization of a slice description — it includes RAN, core, and transport components working together to deliver a specific service. When TEASOL brokers a slice transaction, the end result is an NSI provisioned on the host MNO's infrastructure.
- NSSI
- Network Slice Subnet Instance. A deployed subnet within an NSI. Each NSI is typically composed of multiple NSSIs — one for the RAN domain, one for the core network, and one for transport. NSSIs can be shared across multiple NSIs when resource isolation requirements permit it.
- ServiceProfile
- A 3GPP TS 28.541 Network Resource Model (NRM) object that captures end-to-end slice requirements. The ServiceProfile is what the CSMF hands to the NSMF — it includes parameters like latency, availability, coverage area, and maximum number of UEs. TEASOL's Translation Engine converts GSMA NG.116 GST attributes into 3GPP TS 28.541 ServiceProfile parameters, adapting the mapping per MNO.
- SliceProfile
- A domain-specific decomposition of the ServiceProfile into RAN, Core Network (CN), and Transport requirements. While the ServiceProfile describes the end-to-end service, SliceProfiles break that down into what each network domain needs to deliver. The NSMF generates SliceProfiles and passes them to the appropriate NSSMFs.
- S-NSSAI
- Single Network Slice Selection Assistance Information. The identifier that UEs (user equipment/devices) use to request a specific network slice. S-NSSAI is composed of two parts: the SST (Slice/Service Type) and an optional SD (Slice Differentiator). Together, they tell the 5G core exactly which slice a device wants to connect to. For example, SST=1 with a specific SD might indicate a premium eMBB slice for enterprise customers.
- NSSF
- Network Slice Selection Function. A 5G core network function responsible for selecting the appropriate network slice instance for a UE based on the requested S-NSSAI, the UE's subscription information, and local policies. The NSSF ensures that devices are routed to the correct slice when they connect to the network.
Network Slice Management Functions
4 terms3GPP TS 28.530 defines a layered management architecture for network slicing. Each layer handles a different scope of responsibility, from business-level intent down to individual network domain configuration.
- CSMF
- Communication Service Management Function. The top-level entry point for slice lifecycle management. CSMF receives business-level service requirements from customers or business systems, translates them into a ServiceProfile, and passes that to the NSMF. In the TEASOL architecture, the platform effectively operates at the CSMF layer — receiving demand from CSPs and converting it into standardized slice requests.
- NSMF
- Network Slice Management Function. Manages the full lifecycle of a Network Slice Instance (NSI) end-to-end. The NSMF receives a ServiceProfile from the CSMF, decomposes it into subnet-level SliceProfiles, and coordinates with NSSMFs to provision, monitor, and decommission the slice. It is responsible for ensuring the end-to-end service meets its SLA.
- NSSMF
- Network Slice Subnet Management Function. Manages individual network slice subnets within a specific domain — RAN, Core, or Transport. Each NSSMF receives a SliceProfile from the NSMF and configures the domain-specific network functions and resources needed to fulfill it. A single NSI typically involves three NSSMFs working in parallel.
- NWDAF
- Network Data Analytics Function. A 3GPP-defined analytics service within the 5G core (specified in TS 23.288) that provides demand prediction, anomaly detection, slice load monitoring, and network optimization recommendations. NWDAF ingests data from multiple network functions and produces analytics that can be consumed by the NSMF, PCF, or external systems. TEASOL leverages NWDAF-equivalent analytics for traffic forecasting and proactive SLA management.
Network Sharing Arrangements
4 termsNetwork sharing refers to the various models by which multiple operators can share physical or logical infrastructure. These models differ in what is shared, how spectrum is handled, and how deeply the operators' networks are intertwined.
MOCN
Multi-Operator Core Network
A sharing arrangement where multiple operators share both the RAN infrastructure and radio spectrum, but each maintains its own separate core network. MOCN enables deeper sharing than MORAN because spectrum pooling increases spectral efficiency, but it requires regulatory approval for spectrum sharing. TEASOL supports MOCN configurations through its Network Sharing Exchange module.
MORAN
Multi-Operator RAN
A sharing model where operators share RAN hardware — antennas, base stations, site infrastructure — but each uses its own licensed spectrum. This is the most common form of active RAN sharing deployed today, as it avoids the regulatory complexity of spectrum sharing while still reducing CAPEX and OPEX significantly.
INS
Isolated Network Slice
A dedicated logical network slice deployed on shared physical RAN infrastructure. INS provides strong isolation guarantees — dedicated PRBs, separate QoS policies, and independent lifecycle management — enabling an operator to offer slice-as-a-service on shared infrastructure without compromising tenant separation.
PLMN
Public Land Mobile Network
The unique identifier for a mobile network, composed of a Mobile Country Code (MCC) and a Mobile Network Code (MNC). Every operator has at least one PLMN ID, and it is used across all layers of the network — from SIM registration to inter-operator roaming and sharing agreements — to identify which network a device or service belongs to.
Network Management and Orchestration
4 termsBeyond the slice-specific management functions, the broader network management ecosystem includes orchestration frameworks, operations systems, and virtualization platforms that keep the entire infrastructure running.
- SMO
- Service Management and Orchestration. The O-RAN Alliance's management and orchestration layer. SMO sits above the RAN and provides lifecycle management, performance monitoring, and policy-driven optimization through standardized interfaces (O1, A1, O2). It is where rApps (non-real-time optimization applications) execute. TEASOL integrates with SMO platforms to receive RAN performance data and push slice configuration updates.
- OSS
- Operations Support System. The software platform operators use for network management, service provisioning, fault management, and performance monitoring. OSS is the operational backbone of a telecom network. TEASOL connects to existing OSS platforms via northbound APIs to automate slice provisioning without requiring operators to replace their existing tooling.
- BSS
- Business Support System. The software platform handling billing, customer relationship management (CRM), order management, and commercial operations. BSS is the business side of telecom operations. In network sharing scenarios, BSS integration is critical for automated settlement and revenue sharing between parties.
- NFV MANO
- Network Functions Virtualization Management and Orchestration. The ETSI-defined framework (specified in ETSI GS NFV-MAN 001) for managing virtualized network functions. NFV MANO handles the instantiation, scaling, and termination of virtual network functions (VNFs) on cloud infrastructure. It comprises three components: the NFV Orchestrator (NFVO), VNF Manager (VNFM), and Virtualized Infrastructure Manager (VIM).
Quality of Service
5 termsQuality of Service is the measurable, enforceable backbone of any network sharing agreement. These terms define how performance is specified, measured, and guaranteed.
| Term | Full Name | Description |
|---|---|---|
| 5QI | 5G QoS Identifier | A standardized integer that maps to a predefined set of QoS parameters: priority level, packet delay budget, packet error rate, and maximum data burst volume. 5QI values range from 1 to 86+, each corresponding to a specific traffic treatment. For example, 5QI 1 is for conversational voice, 5QI 9 is for video streaming, and 5QI 85 is for non-GBR low-latency traffic. TEASOL maps GST QoS attributes to the appropriate 5QI values during slice configuration. |
| QoS | Quality of Service | The overall performance of a network service as experienced by users, typically measured in terms of latency, throughput, jitter, packet loss, and availability. In 5G, QoS is enforced per-flow through the QoS framework, allowing different traffic types within the same slice to receive different treatment. |
| QoD | Quality on Demand | A GSMA CAMARA API that allows application developers to programmatically request and activate specific QoS profiles for a session or device. QoD exposes network QoS capabilities to the application layer, enabling use cases like boosting bandwidth for a live video stream or ensuring low latency for a gaming session — on demand, via API. |
| SLA | Service Level Agreement | A contract between a service provider and a customer that defines the expected performance of a service — including uptime, latency thresholds, throughput guarantees, and remediation procedures if targets are missed. In TEASOL's architecture, SLA terms are automatically generated from matched GST parameters and recorded on the consortium blockchain for immutable auditability. |
| KPI | Key Performance Indicator | A measurable metric used to evaluate network performance against defined targets. Common network KPIs include average latency, peak throughput, packet loss ratio, and handover success rate. TEASOL continuously monitors KPIs against SLA thresholds and triggers the QoE Preservation Loop when values approach violation boundaries. |
Radio and Infrastructure
6 termsThe physical and logical components that make up the mobile network — from base stations and radio resources to edge computing and core network functions.
- RAN
- Radio Access Network. The portion of a mobile network that connects end-user devices to the core network via radio transmission. In 5G, the RAN includes gNBs, antennas, and the fronthaul, midhaul, and backhaul transport links connecting them. RAN is the most capital-intensive part of any mobile network and the primary target for sharing arrangements.
- gNB
- gNodeB. The 5G NR (New Radio) base station. A gNB provides the radio interface to UEs and connects to the 5G core network. It can be deployed as a monolithic unit or split into a Central Unit (gNB-CU) and Distributed Unit (gNB-DU) for flexible deployment in O-RAN architectures.
- PRB
- Physical Resource Block. The smallest unit of radio resource allocation in LTE and 5G NR. A PRB consists of 12 subcarriers over one slot in the time domain. PRB allocation is how the RAN scheduler distributes capacity among users and slices — dedicated PRB reservations are a key mechanism for guaranteeing slice-level QoS.
- MEC
- Multi-access Edge Computing. Compute, storage, and networking resources deployed at the edge of the mobile network, close to the radio access. MEC enables ultra-low-latency applications by processing data near the user rather than routing it to a central cloud. Use cases include autonomous driving, augmented reality, and industrial automation.
- UPF
- User Plane Function. The 5G core network function responsible for user data packet forwarding, QoS enforcement, traffic measurement, and lawful interception. UPF is where user traffic enters and exits the core network. In MEC deployments, a local UPF can be placed at the edge to enable low-latency data paths.
- DNN
- Data Network Name. An identifier that specifies which external data network a PDU (Protocol Data Unit) session connects to. DNN is the 5G equivalent of the LTE APN (Access Point Name). Different DNNs can route traffic to different enterprise networks, internet breakouts, or MEC applications within the same slice.
TEASOL-Specific Terms
4 termsThese terms are specific to the TEASOL Exchange Platform and describe the proprietary components that enable automated, multi-operator network sharing.
TEP — TEASOL Exchange Platform
The full product name for TEASOL's network and slice exchange platform. TEP provides three core modules — Network Sharing Exchange, Slice Exchange, and Neutral Host Sharing — that together enable AI-powered matching between service demand and available network capacity across multiple operators.
Translation Engine
The component within TEP that converts GSMA NG.116 GST attributes into 3GPP TS 28.541 ServiceProfile parameters. Because each MNO's network implementation is different, the Translation Engine maintains per-operator mapping profiles that account for vendor-specific capabilities, supported features, and parameter ranges.
QoE Preservation Loop
TEASOL's autonomous remediation system that continuously monitors slice KPIs and takes corrective action when values approach SLA violation thresholds. Rather than waiting for a breach, the loop proactively adjusts resource allocation, triggers scaling, or reroutes traffic to maintain the agreed quality of experience.
Consortium Blockchain
The distributed ledger within TEP that provides an immutable record of SLA obligations, real-time monitoring events, and financial settlements between parties. The consortium blockchain ensures that all participants in a sharing arrangement have a single, tamper-proof source of truth for contractual and operational data.
Industry Actors
5 termsThe organizations and roles involved in network sharing ecosystems. Understanding who does what is essential for navigating commercial and technical discussions.
MNO
Mobile Network Operator
An organization that owns and operates licensed radio spectrum and mobile network infrastructure. MNOs are the primary providers of cellular connectivity and the supply side of most network sharing arrangements. Examples include Deutsche Telekom, Vodafone, and KPN.
MVNO
Mobile Virtual Network Operator
A service provider that resells MNO capacity under its own brand without owning radio spectrum or core infrastructure. MVNOs rely on wholesale agreements with MNOs to deliver connectivity. In the TEASOL ecosystem, MVNOs are typical demand-side participants requesting specific slice types through the platform.
NOP
Network Operator
The entity that instantiates and operates network slices on its infrastructure. In most cases, the NOP is an MNO, but it can also be a neutral host provider or a private network operator. The NOP is the supply side in TEASOL's matching engine — publishing available capacity and fulfilling matched slice requests.
CSP
Communication Service Provider
A broad term for any entity that provides communication services to end users. CSPs include MNOs, MVNOs, fixed-line operators, and OTT communication providers. In 3GPP's management architecture, the CSP is the entity that interfaces with the CSMF to request network slices.
Neutral Host
Neutral Host Provider
An entity that deploys shared venue infrastructure — such as in-building DAS (Distributed Antenna Systems), small cells, or private networks — that multiple operators can use simultaneously. Neutral hosts are common in airports, stadiums, hospitals, and enterprise campuses. TEASOL's Neutral Host Sharing module is designed specifically for this model.
Standards Bodies and APIs
6 termsThe organizations that define the specifications, interfaces, and APIs underpinning mobile networks. Their standards determine what is technically possible and commercially interoperable.
| Term | Full Name | Description |
|---|---|---|
| 3GPP | 3rd Generation Partnership Project | The global standards body that defines mobile network specifications across all generations (3G, 4G, 5G, and beyond). Key 3GPP specs for network slicing include TS 28.530 (management concepts), TS 28.541 (NRM/ServiceProfile), TS 23.501 (system architecture), and TS 23.288 (NWDAF). Nearly every technical term in this glossary traces back to a 3GPP specification. |
| GSMA | GSM Association | The mobile industry association that sets guidelines and commercial frameworks used by operators worldwide. Key GSMA documents for network sharing include NG.116 (GST/NEST), NG.117 (NEST Compliance), NG.120 (Network Slicing Management), and the CAMARA Open Gateway initiative. TEASOL's data model is built on GSMA NG.116. |
| O-RAN | O-RAN Alliance | An industry consortium that defines open, interoperable RAN interface specifications. O-RAN promotes disaggregation and vendor diversity in the RAN through standardized interfaces including O1 (management), A1 (policy), R1 (rApp/SMO), and the Open Fronthaul interface. O-RAN's open architecture is foundational for multi-vendor sharing scenarios. |
| TM Forum | TM Forum | A global industry association focused on telecom management and business process standards. TM Forum publishes the Open API suite used for OSS/BSS integration, including TMF 641 (Service Ordering), TMF 633 (Service Catalog), TMF 628 (Performance Management), TMF 632 (Party Management), TMF 642 (Alarm Management), and TMF 635 (Usage Management). TEASOL uses TM Forum APIs for standardized integration with operator OSS/BSS platforms. |
| CAMARA | GSMA Open Gateway | The GSMA Open Gateway API framework that exposes network capabilities to application developers through standardized, carrier-grade APIs. Key CAMARA APIs include Quality on Demand (QoD), Network Slice Booking, Device Location, and SIM Swap detection. CAMARA represents the industry's push to make network capabilities programmable and accessible beyond traditional telecom boundaries. |
| ETSI | European Telecommunications Standards Institute | The European standards body responsible for key telecom frameworks including ZSM (Zero-touch Service Management) for autonomous network operations, SOL005 (NFV orchestration APIs), and the NFV architectural framework. ETSI's ZSM architecture aligns closely with the autonomous management approach that platforms like TEASOL implement. |
See These Standards in Action
TEASOL Exchange translates these standards into a working platform for automated network sharing. Book a demo to see how GST, NEST, and ServiceProfile mapping work in practice.