QoS and Delivery Context in Rule-Based Edge Services

1. QoS and Delivery Context in Rule-Based Edge Services Prepared for IWCW2002 By Ng Chan Wah 20020814 Panasonic Singapore Labs – Network Team

2. Agenda • Rule-Based Services in the Edge • Open Pluggable Edge Services • Need for QoS and Delivery Context • Implementations Panasonic Singapore Labs – Network Team

3. In the Core … • Various different content formats are emerging … WML Real Flash PNG GIF DHTML HTML ASP MPEG1 Quicktime Windows Media JPEG PHP MPEG4 Panasonic Singapore Labs – Network Team

4. Embedded Devices WAP Phone Integrated Chip Desktop PDA Palmtop Laptop … At the Edge … • Various different user agents and platforms are emerging … Panasonic Singapore Labs – Network Team

5. Enter: Edge Services • To efficiently deliver contents of various formats to the end users with various agents and platforms • With 3 main types of edge services: • Adapts the requests • Adapts the response • Dynamically assemble the contents Panasonic Singapore Labs – Network Team

6. A caching proxy Caching Proxy • A rule engine that interprets rules written in a highly abstract language known as Intermediary Rule Markup Language (IRML) Rule Engine • Based on rules loaded to the rule engine, adaptation services may be triggered on the request or response Adaptation Services Open Pluggable Edge Services • Current effort by the IETF OPES WG • Architecture: Panasonic Singapore Labs – Network Team

7. Ad Insertion Insert advertisement for access providers Text Translation Convert English HTML into Japanese Intermediary Internet Audio Channel Selection Automatically select the audio channel from different languages for a on-line movie Virus Scanning Scan for virus before downloading program to Palm Pilot Example Services of OPES Panasonic Singapore Labs – Network Team

8. But … • IRML constructs rules based on properties in HTTP headers • Such as: Content-Type, User-Agent • Limited information conveyed • Especially profound for wireless web Panasonic Singapore Labs – Network Team

9. Why? • Wireless Environment • Bandwidth is expensive • QoS is important consideration • Mobile Environment • Wide diversity in devices types, screen sizes • Battery constraints: client-side services is not a good ides Panasonic Singapore Labs – Network Team

10. Caching Proxy Rule Engine Sub-System Adaptation Services Extending OPES • Sub-System mechanism • extend properties that Rule Engine understand beyond HTTP headers Panasonic Singapore Labs – Network Team

11. Caching Proxy Rule Engine QoS Sub-System Adaptation Services Extending OPES • QoS Sub-System • Interprets QoS and network conditions • Such as: bandwidth-available, bytes-transmitted Panasonic Singapore Labs – Network Team

12. Caching Proxy Rule Engine QoS Sub-System Delivery Context Sub-System Adaptation Services Extending OPES • Delivery Context Sub-System • Interprets Delivery Context • Such as: User Preferences, Agent and Device Capabilities, and Natural Environment Panasonic Singapore Labs – Network Team

13. Implementation to other collaborating caches Caching Proxy Adaptation Services Traffic Control Framework Rule Engine to wireless clients to content servers QoS Sub-System Delivery Context Sub-System Remote Adaptation Services Delivery Context Database Panasonic Singapore Labs – Network Team

14. Rule Engine taps the request and response at 2 points: one before the cache, one after the cache Rule Engine taps the request and response at 2 points: one before the cache, one after the cache Implementation to other collaborating caches Caching Proxy Adaptation Services Traffic Control Framework Rule Engine to wireless clients to content servers QoS Sub-System Delivery Context Sub-System Remote Adaptation Services Delivery Context Database Panasonic Singapore Labs – Network Team

15. Implementation to other collaborating caches Caching Proxy Adaptation Services Traffic Control Framework Rule Engine to wireless clients to content servers QoS Sub-System Delivery Context Sub-System Traffic Control Framework monitors and condition packets flowing into the network Remote Adaptation Services Delivery Context Database Panasonic Singapore Labs – Network Team

16. Implementation to other collaborating caches Caching Proxy Adaptation Services Traffic Control Framework Rule Engine to wireless clients to content servers QoS Sub-System Delivery Context Sub-System QoS Sub-System obtain values for QoS properties in IRML by interfacing with the Traffic Control Framework Remote Adaptation Services Delivery Context Database Panasonic Singapore Labs – Network Team

17. Implementation to other collaborating caches Caching Proxy Adaptation Services Traffic Control Framework Rule Engine to wireless clients to content servers QoS Sub-System Delivery Context Sub-System In the actual system, the Delivery Context Sub-System should obtain values for delivery context from an external database, but currently is not implemented. Delivery Context information are now embedded in the HTTP headers. Remote Adaptation Services Delivery Context Database Panasonic Singapore Labs – Network Team

18. Deployment • Conversion of Images to Text • Bandwidth available • Screen capability • User Preference Panasonic Singapore Labs – Network Team

19. Deployment • Conversion of Audio-Visual Streams • Bandwidth available • Screen capability • User Preference Panasonic Singapore Labs – Network Team

20. Summary • OPES as a standardized, rule-based framework for edge services • Extend OPES to understand QoS and Delivery Context • Implementation Examples • Questions? Panasonic Singapore Labs – Network Team