Serverless Core Network Service Invocation for Weak Coupling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing network architectures have strong coupling between network elements, leading to complex logic, difficulty in disaster recovery, and inflexible network deployment and management, with each element needing to maintain user context independently, resulting in frequent transmission of privacy data and reduced security.
Innovation Solution
Implementing a serverless architecture with a new core network design where network elements have weak coupling, allowing a first network element to process service requests and invoke other network elements as needed, with a centralized data storage and network function discovery, reducing direct access to user data and enhancing security.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If each network element independently maintains user context, then network elements can operate autonomously, but network deployment and management become inflexible and complex
Solution Approach 1:
The patent segments network functions into independent network elements (AMF, SMF, PCF, UDM) that operate autonomously while maintaining weak coupling through standardized interfaces. Each element maintains its own context independently, enabling flexible deployment and management while preserving operational autonomy.
2Productivity
If network elements have strong coupling relationships, then coordination between elements is efficient, but disaster recovery becomes difficult and flexibility is reduced
Solution Approach 1:
The patent introduces a service-based architecture where network elements communicate through standardized service interfaces rather than direct strong coupling. The AMF acts as an intermediary that coordinates services from SMF, PCF, and UDM through service discovery and invocation mechanisms, enabling efficient coordination while maintaining independence for disaster recovery.
3Speed
If network elements directly access user data, then data retrieval is fast, but security is reduced due to frequent transmission
Solution Approach 1:
The patent extracts user data storage function from individual network elements and consolidates it in the UDM (Unified Data Management) element. Network elements like AMF and SMF retrieve data from UDM through standardized service interfaces only when needed, reducing frequent direct access and transmission while maintaining fast data retrieval through efficient service-based communication.
4Adaptability or versatility
If network architecture logic becomes complex, then more functions can be integrated, but deployment and management flexibility is reduced
Solution Approach 1:
The patent implements a universal service-based architecture where network elements provide multiple functions through standardized service interfaces. The AMF can invoke services from SMF, PCF, and UDM as needed, allowing flexible deployment and management while integrating multiple functions through a common service framework rather than complex point-to-point connections.
Data Source
AI summary
An example method includes: a first network element obtains service input data or an obtaining credential of the service input data from a second network element based on a received service trigger event, and sends a service request to at least one third network element. The at least one third network element executes a requested service based on the service request, and sends a service feedback to the first network element.