Network Overview: Access, Transport & Core
Last updated 13 Oct 2026
At a glance
A telecommunications network connects customers, devices and locations. It is where the services customers order are delivered: BSS manages the commercial side, OSS coordinates the network. It can be read in five areas: the access network, the transport network, the IP core, the mobile core and IMS.
The picture
The path every service takes
- 01Access network
Connecting the customer
The access network provides the connection between a customer’s home, business location or mobile device and the service provider’s network. This may be through mobile coverage, fibre, copper or other access technologies.
- Mobile radio
- Fibre (FTTH)
- Copper
- Cable
- Fixed wireless
- 02Transport network
Carrying the traffic
The transport network connects different parts of the provider’s infrastructure. It carries traffic from access networks towards central network locations and between those locations, allowing information to travel over short and long distances.
- Aggregation
- Metro
- Long-haul
- Fibre and microwave links
- 03IP core
Connecting networks and destinations
The IP core directs traffic across the provider’s network and towards other networks, services and the internet. It supports connectivity for broadband customers, businesses and mobile services.
- Core routers
- Broadband edge (BNG)
- Internet peering
With the IP core, for mobile and voice
- 04Mobile core
Managing mobile connectivity
The mobile core manages how mobile devices connect to and use mobile services. It helps identify subscribers, determine which services they can access and establish their mobile connectivity.
- 4G core (EPC)
- 5G core (5GC)
- Subscriber data
- 05IMS
Enabling voice services
IMS supports modern voice and communication services over mobile and fixed networks, including mobile voice calls and internet-based telephone services.
- VoLTE
- VoNR
- Wi-Fi calling
- Fixed VoIP
Access network
The UE attaches over radio to the gNB (eNB in 4G). Nothing on the RAN changes for a new subscriber — it serves whoever the core admits.
Transport network
Aggregation and metro routers carry the gNB's user plane (N3) and signalling (N2) as backhaul.
IP core
The IP core carries the backhaul on to the core site that hosts the 5GC. It routes the traffic; it knows nothing about the subscriber.
Mobile core
The AMF registers the device against its subscription in UDM, the record activation writes, and the SMF sets up the PDU session and selects a UPF; the UPF forwards packets to the internet (N6). The SMF reports usage to the CHF, which hands it to charging.
Not involved: IMS.
IP networking runs through all of it:IPv4 / IPv6Routing: OSPF · IS-IS · BGPMPLSSegment routingQoSTraffic engineeringL2 / L3 VPNNetwork slicingMonitoring & telemetry
How it works
Five areas, one path
The access network connects the customer's home, business location or mobile device. The transport network carries traffic from access towards central network locations and between them. The IP core directs traffic across the network and towards other networks and the internet; its broadband edge (the BNG) is where fixed subscribers arrive. The mobile core identifies mobile subscribers and sets up their connectivity, and IMS enables voice over mobile and fixed networks. The IP core and the mobile core are the two network cores of 9.2. Each service takes its own path: FTTH ends at the BNG and never touches the mobile core; mobile data and voice ride the IP core to the mobile core and IMS; an L3VPN or SD-WAN never touches a subscriber core at all.
What each area owns
| Access network | Transport network | IP core | Mobile core | IMS | |
|---|---|---|---|---|---|
| Typical elements | gNB / eNB, OLT, ONT, splitter, CPE, access switch | Aggregation and metro routers | Core and regional routers, PEs; BNG and AAA; SD-WAN controller | 5GC (AMF, SMF, UPF), PCF, NEF, NSSF | P-, I- and S-CSCF, TAS, SBC |
| Resource Inventory holds | Physical plant, devices, ports, PON trees; VLANs and ONT IDs | Devices, ports, links, topology | Interfaces, VRFs, IP addresses, MPLS / SR paths; address pools | Network function instances; slice instances | Network function instances; numbers, SIP trunks |
| Touched by a customer order? | Yes for fixed and enterprise access; no for the RAN | Rarely: built capacity | At the edge: PEs for a VPN, AAA for broadband, the controller for SD-WAN | Through subscriber data in UDM / HSS | Through numbers and features in HSS and the TAS |
The last row shapes an OSS design. Activation is concentrated at the edges: the OLT, the CPE, the provider edge router and the subscriber data stores. Most transport and core-router configuration is done when capacity is built. A fulfilment flow that configures every element in a path for every order is solving the wrong problem; one that ignores the subscriber data stores activates nothing.
Three kinds of resource
- Physical: chassis, cards, ports, fibre, splitters. The classic inventory of access and transport.
- Logical: VLANs, IP addresses, VRFs, ONT IDs, telephone numbers. What fulfilment assigns.
- Virtual and cloud-native: mobile core and IMS functions. They scale and move, so their record has to be fed from the orchestrator that runs them.
10.1 and 10.2 cover how each is modelled.
A different activation route per area
| Area | Activated through |
|---|---|
| Fixed and enterprise access | Access EMS / NMS, or NETCONF / YANG |
| Transport network and IP core | Network orchestrators and SDN controllers; broadband profiles in AAA / RADIUS; SD-WAN overlays through the SD-WAN controller |
| Mobile core and IMS | NFV or cloud-native orchestration; per-subscriber data written to UDM / HSS |
Each area has its own EMS, NMS or controller above it, often more than one. Those layers are where ROM’s resource orders land. 10.5 covers the activation patterns, 10.3 the EMS/NMS layer, and 10.4 the controllers and interfaces below ROM.
Who owns what
| Entity | System of Record | System of Engagement | System of Reference | Notes |
|---|---|---|---|---|
| Physical resources (devices, ports, fibre, splitters) | Resource Inventory | — | EMS / NMS (active elements only) | TMF639. Active elements can be reconciled from the network; passive plant only from field updates. |
| Logical resources (VLANs, IP addresses, VRFs, ONT IDs) | Resource Inventory (IP addresses often in IPAM) | ROM (assignment during fulfilment) | — | Assigned per order; the domain where most fulfilment errors show up. |
| Virtual and cloud-native network functions | NFV / cloud-native orchestrator | — | Resource Inventory | Instances scale and move; inventory is fed from the orchestrator rather than designed. |
| Per-subscriber network data | UDM / HSS and AAA | SOM / ROM (provisioning) | — | The core is touched per order mostly through these stores. |
In practice
Real estates run several generations of each domain at once: copper and fibre access, legacy and model-driven transport, 4G and 5G core. Each comes with its own management layer, and often more than one per domain. Fulfilment design starts by finding out which of those layers can be driven by API and which still need a person or a script.
The trade-off
What it solves
A shared map of the network lets architects place each activation step in the right domain, and see that most per-order work happens at the edges and in subscriber data stores.
What it does not solve
- Inventory accuracy. Knowing what a domain holds does not make its records true.
- Passive plant, which no discovery tool can verify.
- The management-layer sprawl above each domain, which differs per estate.
What it adds
- Three resource kinds (physical, logical, virtual) need three different ways of keeping inventory current.
- Each domain has its own activation route, so fulfilment integrates with several controllers.
Architecture decision
How should Resource Inventory be kept true for each kind of resource?
Discover and reconcile from the network
Choose when the resource is active and its EMS or controller exposes reliable state.
Feed from the orchestrator that runs it
Choose when the resource is a virtual or cloud-native function that scales and moves.
Design-led records with field updates
Choose when the resource is passive plant, and the field process can be held to updating records.
Breaks if one method is applied to everything. Hand-designed records for scaling network functions go stale in hours; discovery for passive plant finds nothing.
Takeaways
Key Takeaways
- Five areas: the access network, the transport network, the IP core (with the BNG as its broadband edge), the mobile core and IMS; IP networking runs through all of them.
- Each service takes its own path: FTTH never touches the mobile core, and an L3VPN or SD-WAN never touches a subscriber core.
- Per-order activation is concentrated at the edges and in subscriber data stores; most transport and core configuration is built capacity.
- Resource Inventory holds physical, logical and virtual resources, and passive plant is the part no discovery tool can verify.
Check yourself
A fulfilment design configures every router on the path for each new broadband order. What is wrong with it?Show answerHide
Transport and core are built capacity. Per-order work for broadband sits at the edges (OLT, ONT, CPE, BNG profile) and in AAA and IPAM. Touching the backbone per order adds risk and load for no benefit.
A new mobile customer is activated but cannot attach. No network function configuration was changed. Is that the bug?Show answerHide
No. Mobile activation rarely changes function configuration. Check the subscriber data stores (HSS or UDM) and policy, which is where a mobile order actually lands.
Why does a brownfield inventory clean-up spend most of its effort on access?Show answerHide
Access holds the passive plant, which cannot be discovered, and the oldest customer connections, often made before current models existed. Both need field data or manual reconciliation.