NRF Registration for Legacy Network Elements

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Service provider network elements that do not support the NRF network element registration interface in existing technologies require high-cost upgrades to meet registration requirements.

Innovation Solution

A network element registration method and system where the NRF receives a registration request from an extra-domain service provider network element, allocates a unique instance ID, and supports both automatic and manual registration, allowing for manual configuration without requiring the network element to support the NRF registration interface.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If service provider network elements support the NRF registration interface, then network element management and service discovery are improved, but equipment upgrade cost increases

Engineering Contradiction:
Improvenetwork element managementVSAvoidequipment upgrade cost
Core Design Contradiction:
ReliabilityVSEase of manufacture

Solution Approach 1:

The patent segments network elements into two categories: NRF intra-domain service provider network elements that support the registration interface and NRF extra-domain service provider network elements that do not support it. This segmentation allows the system to manage different types of network elements differently, enabling legacy elements to be included without requiring expensive upgrades while maintaining proper management for elements that do support the interface.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent creates a universal registration mechanism that works for both NRF intra-domain and extra-domain service provider network elements. By allocating different types of network element instance IDs (second instance ID for intra-domain, first instance ID for extra-domain), the system provides universal service discovery and management capabilities across diverse network element types without requiring them all to support the same interface.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If legacy network elements are upgraded to support NRF registration interface, then service discovery capability is improved, but deployment complexity and cost increase

Engineering Contradiction:
Improveservice discovery capabilityVSAvoiddeployment complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent divides the network element population into segments based on their capability to support the NRF registration interface. This segmentation allows legacy network elements to be integrated into the service discovery system without requiring complex upgrade processes, thereby improving service discovery capability while avoiding increased deployment complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The NRF acts as an intermediary that handles registration requests from both intra-domain and extra-domain service provider network elements. For extra-domain elements that cannot support the standard registration interface, the NRF provides alternative registration mechanisms, eliminating the need for complex upgrades at the network element level while maintaining service discovery capability.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS12225490B2Network element registration method and system, and network function repository function
Publication Date: 2025.02.11 ZTE CORP
  • US12225490B2 patent drawing
  • US12225490B2 patent drawing

AI summary

A network element registration method and system, and a Network Function Repository Function (NRF) are disclosed. The network element registration method may include: receiving, by a Network Function Repository Function (NRF), a registration request of a NRF extra-domain service provider network element, the registration request includes service identification information of the NRF extra-domain service provider network element; and allocating, in response to the registration request, a first network element instance ID for the NRF extra-domain service provider network element, the first network element instance ID is different from a second network element instance ID allocated by the NRF for a NRF intra-domain service provider network element.