Resource Inventory
Resource Inventory for managing physical and logical network resources β devices, ports, cables, VLANs, IPs, and network topology.
Resource Inventory: The Infrastructure Runtime View
Resource Inventory tracks every physical and logical resource in the operator's network. This is where abstract CFS and RFS concepts connect to concrete hardware and configuration. It serves two audiences: service fulfilment (which resources are available to allocate?) and network operations (what is deployed, where, and in what state?).
Design, Assign, Activate: The End-to-End Flow
The diagram below shows how a service order flows from SOM through inventory layers to network activation. SOM decomposes the order into CFS/RFS, SLM designs the service instances, Resource Inventory assigns (checks, selects, reserves) the physical and logical resources, and the activation engine configures the network elements. The confirmation cascade flows back up through each layer.
Service Order Management (SOM)
Decomposes commercial order into CFS β RFS
Service Order
Broadband 200Mbps
SLM (TMF638)
CFS and RFS instances created β service is βDesignedβ
CFS: Internet Access
200Mbps β state: Designed
GPON Bearer
RFS
VLAN Svc
RFS
IP Profile
RFS
QoS Profile
RFS
Resource Inventory (TMF639)
Resources checked, selected, and reserved β service moves to βReservedβ
OLT Port
Reserved
VLAN ID
Reserved
IP Address
Reserved
QoS Policy
Reserved
Activation Engine
Generates vendor-specific config from templates, pushes to network
Activation Engine
Template rendering β config push
Network Elements
Physical and logical resources configured β service becomes βActiveβ
OLT
Switch
BNG
RADIUS
Resource Categories
Resource Allocation and Pool Management
During service fulfilment, resources must be allocated from available pools and assigned to the new service instance. This is one of the most operationally critical functions of Resource Inventory.
Resource Allocation During Fulfilment
Requirement Identified
SOM / Service CatalogRFS decomposition identifies that the service needs: 1 OLT port, 1 VLAN ID, 1 IP address, 1 QoS profile.
Availability Check & Selection
Resource InventoryResource Inventory is queried for available resources at the serving location. Specific resources are selected based on allocation policies (next available port, nearest IP, specific VLAN range).
Reservation
Resource InventorySelected resources are marked "Reserved" to prevent double-allocation. Other orders cannot use these resources while reserved.
Activation & Confirmation
Resource Inventory / ActivationOnce the activation engine configures the resources on the network, inventory updates their state to "In-Use" and records the service instance reference.
Resource Lifecycle States
Resource Lifecycle States
| State | Physical Resource | Logical Resource |
|---|---|---|
| Planned | Ordered from vendor, not yet installed | Defined but not yet provisioned |
| Available | Physically installed, tested, ready for use | Created in pool, available for allocation |
| Reserved | Earmarked for a specific order | Allocated to an order, not yet activated |
| In Use | Actively carrying traffic | Configured on a device, assigned to a service |
| Decommissioned | Physically removed or marked for disposal | Deleted from device, returned to pool |
IP Address and VLAN Management
IP addresses and VLAN IDs are the most common logical resource types. Both are finite pools that must be carefully managed to avoid exhaustion and conflicts.
- IPAM: Tracks IP pools, subnet allocations, and individual assignments. Pools are defined per region/service/access technology. IPv4 exhaustion makes efficient IPAM critical.
- VLAN Management: VLAN IDs range 1-4094, partitioned by service type (e.g., 100-499 residential, 500-999 business). Scope rules determine where uniqueness must hold. Exhaustion on an access ring blocks new activation.
TMF639 Resource Inventory Management API
Resource Discovery and Reconciliation
Resource Inventory is only useful if it reflects reality. Discovery scans the network to detect what actually exists; reconciliation compares discovered state against inventory records.
- Discovery methods: SNMP polling, NETCONF/YANG, CLI scraping (legacy), SDN controller APIs
- Discrepancy types: Missing in inventory (add), missing on network (investigate), attribute mismatch (determine which is correct), state mismatch (typically network wins for physical presence)
- Design intent vs actual state: Mature operators maintain both views β when they diverge, the operator can enforce intent or accept the change
Source of Record
Resource Inventory SoR Mapping
| Entity | System of Record | System of Engagement | System of Reference | Notes |
|---|---|---|---|---|
| Physical Resource Instance | Resource Inventory / Network Inventory | Field Operations, Logistics | SLM, Network Planning | Authoritative for physical device presence, location, and hardware state. |
| Logical Resource Instance | Resource Inventory | ROM / Activation Engine | SLM, IPAM | Authoritative for logical resource allocation (VLAN, IP, QoS). |
| Network Topology | Resource Inventory / Network Inventory | Network Planning, Field Ops | Service Assurance, Path Computation | Containment, connectivity, and dependency relationships. |
Section 4.4 Key Takeaways
- Resource Inventory tracks every physical, logical, and compound resource instance on the network
- Resource allocation during fulfilment requires availability checks, selection, reservation, and confirmation to prevent double-allocation
- Resources follow a lifecycle from Planned through Available, Reserved, In-Use, to Decommissioned
- IPAM and VLAN management are critical sub-functions β both manage finite pools that can block activation when exhausted
- TMF639 provides standardized CRUD and event notification for resource instances
- Discovery and reconciliation maintain accuracy between inventory records and actual network state