1 / 20

QoS and Delivery Context in Rule-Based Edge Services

xexilia
Download Presentation

QoS and Delivery Context in Rule-Based Edge Services

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

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

    3. Panasonic Singapore Labs – Network Team In the Core … Various different content formats are emerging …

    4. Panasonic Singapore Labs – Network Team … At the Edge … Various different user agents and platforms are emerging …

    5. Panasonic Singapore Labs – Network Team 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

    6. Panasonic Singapore Labs – Network Team Open Pluggable Edge Services Current effort by the IETF OPES WG Architecture:

    7. Panasonic Singapore Labs – Network Team Example Services of OPES

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

    9. Panasonic Singapore Labs – Network Team 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

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

    11. Panasonic Singapore Labs – Network Team Extending OPES QoS Sub-System Interprets QoS and network conditions Such as: bandwidth-available, bytes-transmitted

    12. Panasonic Singapore Labs – Network Team Extending OPES Delivery Context Sub-System Interprets Delivery Context Such as: User Preferences, Agent and Device Capabilities, and Natural Environment

    13. Panasonic Singapore Labs – Network Team Implementation

    14. Panasonic Singapore Labs – Network Team Implementation

    15. Panasonic Singapore Labs – Network Team Implementation

    16. Panasonic Singapore Labs – Network Team Implementation

    17. Panasonic Singapore Labs – Network Team Implementation

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

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

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

More Related