Network Gateway Service Decoupling for 5G SBA Message Handling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing 5G telecommunications core network architecture faces challenges in reconciling Network Functions (NFs) with Service Based Architecture (SBA) models due to non-service based functionality and unnecessary couplings between NFs and external communication entities, complicating updates and service development.
Innovation Solution
Introducing a Network Gateway Service (NGS) that handles operational messages independently, decoupling NFs from external network interfaces, enabling flexible and independent service development and evolution.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If Network Functions implement external network communication interfaces directly, then operational message handling is enabled, but coupling between NFs and external entities increases
Solution Approach 1:
A service-based interface layer is introduced as an intermediary between Network Functions and external communication entities. This service-based interface handles operational message handling while maintaining loose coupling, allowing NFs to communicate through standardized service requests and responses rather than direct point-to-point connections.
Solution Approach 2:
The communication functionality is segmented into separate service-based interfaces that can be independently implemented and managed. Instead of NFs directly implementing external interfaces, the communication handling is divided into service-level abstractions that decouple the NF implementation from external protocol requirements.
2Ease of operation
If Network Functions are coupled to specific external interfaces, then communication with external entities is enabled, but flexibility in service development and evolution is reduced
Solution Approach 1:
Service-based interfaces are designed to be universal and multi-functional, allowing the same interface structure to support multiple communication scenarios and external entities. This enables NFs to interact with different external systems through a common service interface paradigm, improving adaptability while maintaining communication capability.
Solution Approach 2:
The service-based architecture enables dynamic configuration and evolution of communication interfaces. Service definitions can be modified, added, or removed without requiring changes to the underlying NF implementation, allowing flexible service development and evolution while maintaining stable external communications.
3Ease of operation
If point-to-point communication protocols are used for operational message handling, then direct communication is achieved, but compatibility with cloud infrastructures is reduced
Solution Approach 1:
Traditional point-to-point communication protocols are replaced with service-based communication mechanisms that align with cloud infrastructure paradigms. Instead of direct protocol-based connections, the system uses service requests, responses, and notifications that are compatible with cloud-native architectures and HTTP-based communication standards.
4Ease of operation
If Network Functions implement both service functionality and communication interface functionality, then integrated operation is achieved, but independent updates and modifications become difficult
Solution Approach 1:
The Network Function is segmented into separate concerns: service logic functionality and communication interface functionality. The service-based interface acts as an abstraction layer that separates these responsibilities, allowing independent updates and modifications to either the service logic or the communication handling without affecting the other.
Solution Approach 2:
Communication interface functionality is extracted from the core service logic of Network Functions. By taking out the direct implementation of external communication protocols and replacing it with service-based abstractions, the patent enables independent evolution of communication interfaces while preserving service functionality.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A dedicated Network Gateway Service (NGS) (22, 23) in a Service Based Architecture (SBA) domain (21), deployed in a core network of a telecommunications system (20), arranged for operational message handling with communication entities (2, 3, 4) of the telecommunications system external of the SBA domain (21) in accordance with communication interface protocols (N1, N2, N4) of the telecommunications system (20). The NGS (22, 23) is further arranged for service message handling in the SBA domain (21) with at least one of an Access and Mobility Function (AMF) (24) and a Session Management Function (SMF) (25) of the SBA domain (21).