Universal Mobile Telecommunications System (UMTS); LTE; 5G; Telecommunication management; Generic Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions (3GPP TS 28.623 version 19.7.0 Release 19)
1Key Takeaways
This technical specification series defines a generic Network Resource Model (NRM), also referred to as the Management Information Model (MIM), which includes definitions for Information Object Classes (IOCs) and Managed Object Classes (MOCs). This document specifies the Solution Set (SS) definitions for the generic NR…
2Expert Interpretation
This in-depth analysis of the 3GPP TS 28.623 V19.7.0 standard focuses on the solution set definition of the integrated reference point for the Common Network Resource Model. It covers two implementation schemes: RESTful HTTP and YANG/NetConf, analyzes OpenAPI and YANG data modeling technologies in 5G network management, and provides implementation guidelines and a standardized evolution path under the SBMA architecture.
Standard Overview and Technical Positioning
ETSI TS 128 623 V19.7.0 (2026-04), as an important component of 3GPP Release 19, defines a solution set specification for the **General Network Resource Model** integration reference point. This standard is the core modeling specification in the 3GPP telecommunications management architecture, providing a unified management information model implementation scheme for UMTS, LTE, and 5G networks.
Compared to earlier versions, the biggest change in Release 19 is the **full shift to a service-based architecture**, explicitly stating that this standard is applicable to service-based management architecture deployment scenarios. For scenarios still using the traditional IRP framework, the latest version of Release 14 should be referred to.
Solution Set Architecture Evolution Analysis
The 3GPP TS 28.623 standard family constitutes a complete network resource modeling system:
| Standard Number | Standard Name | Functional Positioning | Release 19 Features |
|---|---|---|---|
| TS 28.621 | General NRM IRP Requirements Specification | Define Model Requirements | SBMA Architecture Requirements |
| TS 28.622 | General NRM IRP Information Services | Define Information Object Classes | Enhanced Information Model |
| TS 28.623 | General NRM IRP Solution Set | Implementation Technical Specifications | Dual-Stack Implementation Scheme |
From a technological evolution perspective, Release 19 realizes the transformation from the traditional CORBA/XML solution to a modern API-driven architecture. The standard text has explicitly removed the CORBA and XML solution sets, focusing on OpenAPI and YANG implementations that conform to modern cloud-native architectures.
OpenAPI Solution Set Technical Implementation
The RESTful HTTP-based solution set uses the OpenAPI 3.0 specification to define the interface contract of the network resource model.
The standard provides complete YAML definition files in the 3GPP Forge repository:Core Model File Architecture
The OpenAPI definition adopts a modular design, mainly including the following key files:
- TS28623_GenericNrm.yaml - Generic NRM root model definition
- TS28623_ComDefs.yaml - Common data type definition
- TS28623_PmControlNrm.yaml - Performance management control model
- TS28623_ThresholdMonitorNrm.yaml - Threshold monitoring model
- TS28623_TraceControlNrm.yaml - Trace control model (separate file)
| Data Type | OpenAPI Mapping | Format Specification | Application Scenarios |
|---|---|---|---|
| Float | Number (format: float) | IEEE 754 Single Precision | Performance Measurement Value |
| DN | DistinguishedName Type | RFC 4514 Format | Object Identifier |
| Real | Decimal64 (fraction-digits 8-18) | High Precision Decimal | Geographic Coordinates |
YANG/NetConf Solution Suite Technical Implementation
The YANG-based data modeling solution provides a standardized data definition language for network configuration management.
The standard provides complete YANG module definitions in the yang-models directory:YANG Module Mounting Mechanism
The standard adopts the YANG Schema Mount mechanism defined by IETF RFC 8528, realizing flexible schema combination:
- ManagedElement and its hierarchy can be mounted under SubNetwork or MeContext
- Dynamic schema extension is achieved through mountpoint "children-of-SubNetwork"
- Supports multi-level SubNetwork nesting, forming a hierarchical management structure
Key features of the YANG solution set include:
- Module Discovery Mechanism: A list of YANG modules supported by the ietf-yang-library module (RFC 8525)
- Schema Acquisition: Supports obtaining module definitions via the get-schema operation of the ietf-netconf-monitoring module (RFC 6022).
- Data Type Mapping: Follows the mapping rules defined in TS 32.160; special types use the predefined YANG type.
| Stage 2 Type | YANG Type | Standard Source | Precision Description |
|---|---|---|---|
| Float | Decimal64 fraction-digits 1-7 | RFC 7950 | 1-7 decimal places precision |
| Real | Decimal64 fraction-digits 8-18 | RFC 7950 | 8-18 decimal places precision |
| Ipv6Addr | inet:ipv6-address | ietf-inet-types | IPv6 address format |
Application of JEX Expressions in Management Operations
Release 19 introduced JSON expressions as a filtering and selection mechanism, replacing the traditional XPath 1.0:
Application Example of NtfSubscriptionControl
Notification Subscription Control uses JEX expressions to define data node selectors and notification filters:
{ "notificationRecipientAddress": "example.org/3gpp-management/alarm-notification-sink", "notificationTypes": ["notifyNewAlarm", "notifyChangedAlarmGeneral", "notifyClearedAlarm"], "scope": { "dataNodeSelector": "/SubNetwork[id=\"SN1\"]/ManagedElement/XyzFunction" }, "notificationFilter": "alarmType=\"QUALITY_OF_SERVICE_ALARM\"" } This configuration monitors quality of service (QS) alerts for XyzFunction objects in all ManagedElements under a specific SubNetwork.
ConditionMonitor Application Example
Condition Monitor uses JEX expressions to define complex monitoring conditions:
"condition": "ManagedElement=X1/GNBCUUPFunction=Y1/DRB.PdcpF1DelayDl_QOS2>15"
The condition is triggered when the average latency of the downlink F1 interface PDCP of QoS2 exceeds 15 milliseconds, which can be associated with starting a performance metric collection task.
Standard Implementation Recommendations and Best Practices
1. Deployment Architecture Selection
Choose a suitable solution set based on network management needs:
- Cloud-native environment: Prioritize OpenAPI solutions for easy microservice integration and automated orchestration
- Traditional network management system: Consider YANG/NetConf solutions and utilize existing network configuration infrastructure
- Hybrid environment: Implement dual-stack support and provide a unified management interface through an adaptation layer
2. Pattern Customization Strategy
Notes when implementing MnS producer-specific patterns:
- Root object simplification: Remove unsupported root class definitions (e.g., retain only SubNetwork or ManagedElement)
- Container pruning: Remove unimplemented name inclusion relationship references
- Attribute Optimization: Remove optional but unimplemented attribute definitions
- URI Specification: Schema files should be accessed via the
/schemas path
3. Data Type Compatibility
Ensure correct mapping and conversion of data types:
- The Float type in OpenAPI corresponds to Decimal64 in YANG (different precisions)
- DN types must comply with the DistinguishedName specification in both OpenAPI and YANG
- Geographic coordinates use the Real type, supporting high-precision geofence definitions
4. Version Management and Evolution
Based on the change history in Appendix F of the standard, the following is recommended:
| Release Version | Key Technical Features | Backward Compatibility | Migration Recommendations |
|---|---|---|---|
| Release 14 | Support for Traditional IRP Framework | Fully Compatible | Traditional System Maintenance |
| Release 16 | Introducing OpenAPI/YANG | Partial Compatibility | Progressive Migration |
| Release 19 | SBMA Architecture, JEX Expressions | Limited Compatibility | New System Implementation |
Technical Challenges and Future Prospects
Current Technical Challenges
3GPP TS 28.623
The main challenges faced during the implementation of V19.7.0 include: Dual-Stack Maintenance Complexity: Both OpenAPI and YANG schemes require synchronized updates and maintenance. JEX Expression Performance: Optimizing the execution efficiency of complex JEX expressions in large networks. Pattern Version Management: Synchronizing versions of MnS producer-specific patterns with standardized patterns. Cross-Vendor Interoperability: Interoperability issues caused by differences in functional subsets implemented by different vendors. Standard Evolution Direction Based on the technology foundation of Release 19, future standard development may focus on: AI/ML Integration: Enhancing support for artificial intelligence and machine learning capabilities in NRM. Intent-Driven Management: Extending Intent NRM to support declarative network management. Edge Computing Enhancement: Optimizing Edge... NRM, supporting distributed edge node management. Network Slicing Deepening: Improving Slice NRM, supporting end-to-end slice lifecycle management. 3GPP TS 28.623, as the core modeling standard for 5G network management, not only provides normative guidance for technical implementation but also lays a solid technical foundation for the evolution of future network management systems. With the development of 5G-Advanced and 6G technologies, this standard system will continue to play a key role, driving network management towards greater intelligence, automation, and service orientation.