P-CSCF Selection by Traffic Type for Network Slicing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing cellular network technologies do not optimally select proxy nodes (such as P-CSCF) based on traffic type, leading to suboptimal resource utilization and performance in cellular networks.
Innovation Solution
A network node, such as a packet gateway, receives a request from a network device for proxy node selection based on traffic type and selects an appropriate proxy node from a list, optimizing the selection based on criteria such as geographic location, latency, and network slicing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If a network device selects a proxy node from a provided list using traditional load balancing (e.g., round-robin), then the selection process is simple and fast, but the network resource utilization is suboptimal and does not account for traffic type-specific requirements
Solution Approach 1:
The patent applies local quality by providing different proxy node lists to network devices based on their specific traffic types. Instead of a single uniform list, the system tailors the proxy node selection to local requirements: emergency calls receive priority handling through specific P-CSCFs, while non-emergency traffic uses standard lists. This resolves the contradiction by optimizing resource utilization for each traffic type without requiring complex device-side selection logic.
Solution Approach 2:
The system changes the parameter of proxy node list composition based on traffic type characteristics. The network node modifies which proxy nodes are included in the list and their prioritization order depending on whether the traffic is emergency or non-emergency. This dynamic parameter adjustment improves overall network resource utilization while keeping the device-side selection process simple.
2Reliability
If the network provides a generic set of proxy nodes to all network devices, then the system is simple to operate, but it cannot optimize performance for specific traffic types such as emergency calls or network slicing requirements
Solution Approach 1:
The patent segments the proxy node list into traffic-type-specific subsets. The network node divides the available P-CSCFs into different lists based on traffic type: one list for emergency calls with priority P-CSCFs, another for non-emergency traffic with standard P-CSCFs. This segmentation improves service quality for specific traffic types while maintaining simple operation at the device level, as each device receives a pre-configured appropriate list.
Solution Approach 2:
The network node acts as an intermediary that filters and prepares appropriate proxy node lists before providing them to network devices. Instead of requiring devices to evaluate and select from all available P-CSCFs, the intermediary (network node) performs the optimization work by providing a tailored list already sorted by suitability for the device's traffic type. This resolves the contradiction by improving service quality through intelligent mediation while keeping the device operation simple.
3Loss of time
If proxy nodes are selected without considering traffic type, then the selection process is fast and simple, but latency is increased and network efficiency is reduced for time-sensitive traffic
Solution Approach 1:
The system performs preliminary action by pre-configuring traffic-type-specific proxy node lists at the network node before devices need to make selections. The network node anticipates different traffic type requirements and prepares appropriate P-CSCF lists in advance, sorted by priority and suitability. When a device requests a proxy list, the pre-prepared appropriate list is provided immediately, reducing latency without requiring complex real-time evaluation at the device level.
Data Source
AI summary
Solutions for providing proxy node (e.g., proxy-call session control function (P-CSCF)) selection by traffic type include: receiving, by a network node (e.g., a packet gateway (PGW)), from a network device (e.g., a user equipment (UE) or internet of things (IoT) device), a first message indicating a request for identification of a proxy node; receiving, by the network node, from the network device, an indication of a first data traffic type; based on at least the indication of the first data traffic type, selecting, by the network node, a first proxy node over a second proxy node to identify to the network device; and transmitting an identification of the first proxy node to the network device. Examples support network slicing and improve wireless priority service (WPS) and enhanced 911 (SECOND DATA TRAFFICE911).