IP-CAN Cache Server Data Delivery via PCC Architecture
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current content delivery and caching solutions in IP Connectivity Access Networks are expensive and difficult to implement, with high transmission costs for telecommunication operators due to reliance on explicit agreements between content providers and CDN operators, and inefficient data retrieval processes.
Innovation Solution
Implementing a caching mechanism within an IP-CAN using the Policy and Charging Control architecture, where a Policy and Charging Rules Function (PCRF) decides on caching based on Deep Packet Inspection results, and the Policy and Charging Enforcement Function (PCEF) monitors data requests to deliver cached data directly from an IP-CAN cache server to user terminals.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If current content delivery and caching solutions are implemented using explicit agreements between CP and CDN, then data can be distributed across CDN servers, but the setup and maintenance of caching scheme becomes expensive and difficult to implement
Solution Approach 1:
The network elements automatically perform caching decisions and data delivery without requiring external CDN infrastructure or explicit agreements. The PCEF monitors data requests and the PCRF makes caching decisions based on network policies, enabling the system to serve itself rather than relying on external services
Solution Approach 2:
The PCC architecture elements (PCRF and PCEF) are made multi-functional by adding caching capabilities to them. These existing network elements now perform both their original policy/charging functions and additional caching functions, eliminating the need for separate CDN infrastructure
2Productivity
If CDN servers store and maintain cached content from multiple CPs, then content can be delivered to users, but the cost and difficulty of implementing caching policies increases
Solution Approach 1:
The network automatically manages caching operations through existing PCC architecture elements. The PCRF determines what content to cache based on network policies and the PCEF automatically delivers cached content, eliminating the need for manual CDN configuration and maintenance
Solution Approach 2:
The caching function is merged with the existing PCC architecture elements (PCRF and PCEF) rather than being implemented as a separate CDN system. This consolidation leverages existing infrastructure to provide caching capabilities without the complexity of maintaining separate CDN systems
3Ease of operation
If telecommunication operators fetch content from external CDNs, then users can access data networks, but high transmission costs (peer costs) are incurred
Solution Approach 1:
Content is cached in advance within the operator's network domain based on predicted user demand and network policies. By pre-caching content before it is requested, the system avoids costly external data transmissions when users access the content
Solution Approach 2:
The operator's own network elements (PCRF and PCEF) act as intermediaries between users and external content sources. Instead of directly fetching content from external CDNs, the system uses its own caching infrastructure as an intermediary layer to serve content locally when available
Data Source
AI summary
A method of delivering data to user terminals connected to an Internet Protocol Connectivity Access Network, IP-CAN, wherein the IP-CAN implements a Policy and Charging Control, PCC, architecture. The method comprises caching data within an IP-CAN cache server upon a decision made by a Policy and Charging Rules Function, PCRF, of the PCC architecture. The cached data is then identified to a Policy and Charging Enforcement Function, PCEF, of the PCC architecture. At the PCEF, data requests made by user terminals are monitored and a determination made as to whether or not a request relates to cached data. If a request does relate to cached data, then that cached data is delivered from the IP-CAN cache server to the requesting user terminal.