CUSTOMER JOURNEY → BSS
An order establishes the service.
The selected product defines the destination, validity and charging model. The order connects the customer account to the service being requested.
ORDER · PRODUCT · CUSTOMERTechnology & architectureFollow the connection.
Follow the connection.
All the way through.
See how commercial systems, the service lifecycle and network functions connect an order to a working mobile service.
See the full system directory Commercial & operational events Provisioning & signalling Data sessions & usage
Three connected layersA clear architecture.
A clear architecture.
Down to the network.
Start at the customer-facing experience and follow the systems that turn an order into an active service.
01CommercialSell & operate
Order & service request ↓Lifecycle events & usage ↑
02EnablementProvision & manage
Identity & service configuration ↓Network status & session records ↑
Logical system map. Physical topology and interface selection depend on the network generation, carrier relationships and deployment design.
The end-to-end service lifecycleWhat actually happens
What actually happens
after “buy now”.
Six steps connect the customer journey to the network — and bring usage back into the business.
SIM MANAGEMENT → PROVISIONING
A resource is assigned.
A profile or SIM resource is allocated from the appropriate pool. Digital delivery is coordinated with the relevant eSIM provisioning service.
ICCID · PROFILE ASSIGNMENT · INSTALLATION DETAILSSUBSCRIBER DIRECTORY
The network identity is configured.
The subscriber identity and service template are provisioned. The commercial subscription and network-facing service now refer to the same connection.
IMSI · SERVICE TEMPLATE · SUBSCRIBER STATUSDRA / STP → NETWORK SYSTEMS
Signalling reaches the right destination.
Network messages follow the configured Diameter or SS7 routing rules. The route and message handling reflect the interconnection arrangement.
REALM / HOST / APPID · GT / IMSI · ROUTE POLICYGTP PROXY → PACKET CORE
A data session finds its path.
Session context selects the gateway path. Packet-core functions establish the session, apply the address allocation model and carry the data.
APN · VPLMN · RAT · GATEWAY GROUP · UE IPNETWORK RECORDS → OCS / OPERATIONS
Usage closes the loop.
Usage records return to charging and reporting. Balances or allowances update, while lifecycle events can trigger customer notifications and operational follow-up.
CDR · RATING · BALANCE · WORKFLOW EVENTThe network route, explainedDifferent functions.
Different functions.
Clear responsibilities.
Signalling, session steering and packet forwarding solve different problems. The architecture keeps those responsibilities visible.
Subscriber / visited network
Usage & session records → BSS / OCS & operational workflows
DRA / STP
Route network control messages, apply interconnection rules and handle identity-aware message adaptation.
- Diameter criteria
- Application ID, Host, Realm and IMSI
- SS7 protocols
- M3UA, M2UA, SCCP and MAP
- Addressing & adaptation
- GT / IMSI routing, IMSI mapping and configured AVP handling
HLR / HSS / UDM
Maintain the subscriber-side service configuration used by the relevant network generation.
- Identity model
- Multiple IMSI resource configurations
- Provisioning
- Service templates and repeatable subscriber setup
- Integration
- REST-based provisioning and service-state coordination
GTP Proxy
Put context-aware route selection between the session request and the gateway arrangement.
- Protocol & mode
- GTP v1 / v2; GTP-C-only or full proxy
- Routing inputs
- IMSI, APN, RAT type, VPLMN and MSISDN
- Operations
- Gateway groups, load balancing, redundancy, blacklist and signalling-storm controls
PGW / SMF / UPF
Provide the packet gateway, session-control and user-plane roles required by the deployment.
- Architecture
- NFV-oriented; roles selected for the network generation
- Address resources
- Dynamic and static UE IP pools
- Operations
- Session records, CDR management, high availability and backup
Select the subscriber, signalling and packet-core functions for the network generation and interfaces your deployment uses.
From network function to useful product.
Real-Time Network Switching combines supported identity, signalling and session decisions. App Whitelisting connects application dependencies to traffic policy. IoT brings those controls into a device lifecycle. Each use case is validated against the actual hardware, networks and commercial configuration.
Interfaces & shared recordsThe handoffs matter
The handoffs matter
as much as the modules.
Each system has a job. Shared records and explicit interfaces keep the customer journey intact between them.
| Connection | What moves across it | Why the business needs it |
|---|---|---|
| Sales channel ↔ BSS | Products, orders, customer and subscription context | Sell the right product and retain its commercial context. |
| BSS ↔ SIM management | Resource requests, profile assignments and service status | Turn a purchase into a deliverable service. |
| Provisioning ↔ Subscriber directory | IMSI resources, service templates and provisioning results | Keep the purchased service aligned with its network identity. |
| Network ↔ Signalling layer | Diameter / SS7 messages and routing context | Direct control traffic to the appropriate network systems. |
| Session steering ↔ Packet core | Session context, gateway selection and forwarding state | Put the connection on the intended data path. |
| Network records ↔ OCS / reporting | Usage records, session identifiers and rated outcomes | Account for usage and support reconciliation. |
| Platform ↔ Customer operations | Lifecycle events, balances and workflow outcomes | Give support a clear view of what happened and what to do next. |
KEY RECORDS
ICCID identifies the SIM resource. IMSI identifies the mobile subscriber. APN selects the data-network context. CDR records service or session activity for downstream operations.
From architecture to deliveryA deployment plan.
A deployment plan.
With the details attached.
The technical route starts with your use case and ends with a defined set of systems, interfaces and operational responsibilities.
Define the service.
Set the commercial and customer requirements before choosing the technical scope.
- Markets and network relationships
- Product and charging model
- Digital or physical distribution
Connect the systems.
Map the enabled modules and the records that pass between them.
- Resource and provisioning ownership
- API and protocol boundaries
- Usage and reconciliation flows
Validate the operation.
Test the journey and agree how it will be supported.
- Order-to-activation checks
- Session and charging validation
- Failover and recovery scenarios
Planning a technical evaluation? Bring your network arrangement and integration requirements.
Talk through the architectureLet’s build somethingYour next product
Your next product
could be mobile.
Tell us about your business. We’ll help you find the right way in.
Start a conversation