Service Rendezvous Point for Network Slice Resource Coordination
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current network slicing technologies lack mechanisms to effectively track and manage resources and services across different domains in communication networks, leading to complexity and inefficiency in managing network slices for various services in 5G networks.
Innovation Solution
Implementing a centralized Service Rendezvous Point (SRP) that receives registration messages from Service Switch Points (SSPs) across different network domains, maintaining a database of resource and service information, and sending report messages to allocate resources dynamically across domains to support network slicing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If network slicing is implemented across multiple domains without centralized management, then network flexibility and service customization are improved, but device complexity and difficulty of managing resources increase
Solution Approach 1:
A centralized Service Rendezvous Point (SRP) is introduced as an intermediary component that coordinates service discovery, resource allocation, and slice management across multiple network domains. The SRP receives service requests, determines appropriate network slices, and manages resource distribution, thereby reducing the complexity burden on individual network elements while preserving overall network flexibility through standardized interfaces
2Ease of operation
If distributed resource management is used across network domains, then autonomy of individual domains is improved, but efficiency of resource allocation and service deployment deteriorates
Solution Approach 1:
The system architecture is segmented into hierarchical layers: individual network domains maintain operational autonomy for local resource management, while the centralized SRP handles cross-domain coordination and optimization. This segmentation allows domains to operate independently within their scope while achieving efficient global resource allocation through the SRP's centralized view and coordination capabilities
3Manufacturing precision
If manual configuration of network slices is performed, then precision of service requirements fulfillment is improved, but time consumption and operational overhead increase
Solution Approach 1:
The system implements automated self-service mechanisms where the SRP automatically discovers available services and resources across domains, dynamically determines appropriate network slice configurations, and provisions slices without manual intervention. Service catalogs and resource databases are automatically maintained, enabling rapid, precise service deployment that fulfills requirements while eliminating manual configuration time
4Loss of information
If comprehensive tracking of network resources across domains is implemented, then visibility and control of network slices are improved, but information processing complexity and storage requirements increase
Solution Approach 1:
The SRP extracts and centralizes the management of resource tracking information from individual network domains. Each domain maintains local resource data, but the SRP consolidates comprehensive visibility by aggregating resource states, service configurations, and slice information into centralized databases. This extraction approach provides complete network-wide visibility while managing information processing complexity at the centralized SRP rather than distributing it across all domains
Data Source
AI summary
A method implemented by a service rendezvous point (SRP) comprises receiving, by a receiver of the SRP, a plurality of register messages from a plurality of service switch points (SSPs), each of the register messages comprising at least one of resource information or service information, each of the SSPs being associated with a different network domain, sending, by a transmitter of the SRP, a plurality of report messages to the plurality of SSPs, each of the report messages comprising resource allocation information for each of the network domains for a service, the resource allocation information including an amount of resources to be allocated at the each of the network domains for the service, and maintaining, at a memory of the SRP, a SSP database storing at least one of the resource allocation information of each of the network domains, the resource information of each of the network domains, and the service information of each of the network domains.