Network Capability Exposure System Decoupling Services
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current network capability exposure methods rely on tight coupling between services and capabilities, making it difficult to meet diverse application requirements and limiting the depth and level of network capability exposure.
Innovation Solution
A network capability exposure system that includes a third-party application layer, network capability exposure layer, network element layer, and computing capability exposure layer, which determines the required network capability type, allocates computing resources, and provides corresponding network capabilities to third-party devices, decoupling services and capabilities.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If network capability exposure is implemented using traditional interfaces (data acquisition exposure interface, parameter configuration exposure interface), then basic network information can be provided to third-party applications, but tight coupling between services and capabilities occurs and diverse application requirements cannot be met
Solution Approach 1:
The patent segments the network capability exposure system into multiple independent layers: the network element layer (providing raw network capabilities), the computing capability exposure layer (providing computational resources), and the third-party application layer (consuming services). This segmentation decouples services from capabilities, allowing each layer to operate independently while maintaining loose coupling through standardized interfaces.
Solution Approach 2:
The patent introduces a computing capability exposure layer as an intermediary between the network element layer and the third-party application layer. This intermediary layer provides computing resources (virtualization resources, container resources, function resources) that enable flexible service deployment without direct coupling to underlying network capabilities. The intermediary translates diverse application requirements into standardized resource requests.
2Ease of operation
If various network management applications maintain their own components (data analysis, algorithm training, service provision, operation environment), then complete service functionality can be achieved, but tight coupling between services and capabilities increases
Solution Approach 1:
The patent creates a universal computing capability exposure layer that provides standardized computing resources (virtualization resources, container resources, function resources) that can be used by any third-party application. This universal layer eliminates the need for each application to maintain its own dedicated components, as all applications can utilize the same standardized resource pool through common interfaces.
Solution Approach 2:
The patent enables third-party applications to self-configure and deploy services using the exposed computing resources and network capabilities. The standardized interfaces allow applications to automatically allocate and manage their required resources without manual intervention or tight coupling to specific implementation details, reducing operational complexity.
3Ease of manufacture
If pure event monitoring and parameter configuration interfaces are used for network capability exposure, then implementation simplicity is maintained, but diverse capability exposure requirements in different scenes cannot be met
Solution Approach 1:
The patent implements a dynamic capability exposure mechanism where the computing capability exposure layer can adaptively allocate virtualization resources, container resources, and function resources based on real-time application requirements. The system dynamically adjusts resource allocation, capability types, and exposure levels without requiring changes to the underlying interface structure, maintaining implementation simplicity while achieving high versatility.
Data Source
AI summary
Disclosed is a network capability exposure method, which includes receiving a service request sent by a third-party device; determining a type of a network capability required according to the service request; determining a computing task matching the type of the network capability required; determining computing resources exposed by at least one physical device; obtaining a computing resource exposure result based on the computing task and the computing resources exposed by the at least one physical device; acquiring a network capability corresponding to the type of the network capability and the computing resource exposure result; and providing the network capability to the third-party device. Further, a network capability exposure device, a network capability exposure system and a non-transitory computer-readable storage medium are also disclosed.