i t & s a e r o s p a c ed e f e n c e content adaptation for gradual quality of service vania...
TRANSCRIPT
I T & S A e r o s p a c e D e f e n c e
Content adaptation for gradual Quality of ServiceContent adaptation for gradual Quality of Service
Vania Conan, Arnaud PierreThales
[email protected]@fr.thalesgroup.com
Séminaire QoS, 25 juin 2004
Example problem: video over heterogeneous networks
Problem:
How to manage QoS in heterogeneous networks characterised by various types of radio links (UMTS, WLAN, …) , load variations and typology.
User with laptop PC
User with Mobile phone
Group of users
User with PDA
Séminaire QoS, 25 juin 2004
Presentation plan
1- Content adaptation problem applications
2- Middleware application Layer Concepts architecture
3- Overlay networks principles current work
4- Overlay management PDP/PEP approach
5- Conclusions
Séminaire QoS, 25 juin 2004
The concept of Content Adaptation Module
Examples of needs for content adaptationExamples of needs for content adaptation
1.1. HTML content adaptationHTML content adaptation
2.2. VRMLVRML
3.3. VideoVideo
ConditionsConditions
Input Input information information
ContentContent
adaptedinformation information
ContentContent
Content adaptation
Séminaire QoS, 25 juin 2004
Compressed Image bitstream
Progressive Transmission by quality
0.125bpp 0.25bpp 1bpp lossless
Séminaire QoS, 25 juin 2004
Compressed Image bitstream
Progressive Transmission by resolution
Séminaire QoS, 25 juin 2004
Content adaptation
WirelessNetwork
User Profile
Content adaptation
adapt information Nature or/and Structureto a set of constraints
End userEquipment
Wireless network constraints
low bandwidth (low signal power)
connection cut hazards
End user equipment (heterogeneous)
laptop PC
PDA environment
mobile phone environment
user profile
user role in the organisation
access control
Séminaire QoS, 25 juin 2004
Presentation plan
1- Content adaptation problem applications
2- Middleware application Layer Concepts architecture
3- Overlay networks principles current work
4- Overlay management PDP/PEP approach
5- Conclusions
Séminaire QoS, 25 juin 2004
unified information format
Header
Information Content
CAM
Rules
Incoming Incoming cellcell
Output Output cellcell
Information structure: a “cell”Information structure: a “cell”
Cell:: (Header, Content)>Header:: (Parameter +)Content:: (Properties, Data)Properties:: (Property *)
Séminaire QoS, 25 juin 2004
Information Flow
transport leveltransport level
cell levelcell level
information levelinformation level
Cell ParsersCell Parsers
Content adaptation ServiceContent adaptation Service
00101101…00101101…
text...text...
Séminaire QoS, 25 juin 2004
A system of rulesA system of rules
Content propertiesContent properties
Loaded ServiceLoaded ServiceContentContentAdapted Adapted ContentContent
Set of RulesSet of Rules
ContextContext(System state)(System state)
Type Type Of ContentOf Content
If [setOfProperties] Then [...] Else […]setOfProperties] Then [...] Else […]
Séminaire QoS, 25 juin 2004
Rule design DTD Description
<?xml version='1.0' encoding='utf-8'?><!-- DTD: RULE STRUCTURE --><!ELEMENT rule (ruleID, instruction)><!ELEMENT ruleIDruleID (#PCDATA)><!ELEMENT instructioninstruction (condition, thenExpression, elseExpression)><!ELEMENT conditioncondition (booleanExpression)> <!ELEMENT booleanExpressionbooleanExpression (operator, operandList)><!ELEMENT operatoroperator (and|or|not)><!ELEMENT andand EMPTY><!ELEMENT oror EMPTY><!ELEMENT notnot EMPTY><!ELEMENT operandListoperandList (operand+)><!ELEMENT operandoperand (booleanExpression|property)><!ELEMENT propertyproperty EMPTY><!ATTLIST propertyproperty name CDATA #REQUIRED><!ELEMENT thenExpressionthenExpression (instruction|statement)><!ELEMENT elseExpressionelseExpression (instruction|statement)><!ELEMENT statementstatement (serviceID)><!ELEMENT serviceIDserviceID (#PCDATA)>
Séminaire QoS, 25 juin 2004
Module Architecture
Libraries of Resources
Serv. Rules Info
Process
Process Management
ProcessorFactory
Statistics & evaluation
External Communication
MessagesManagement
Module
Events generation
Module
Information Capture
Cellcapture
Content extraction
CAM State Management
CAMState
ProfileManagement
Information Delivery
Cellgeneration
Content formatting
Cell parser Library
Séminaire QoS, 25 juin 2004
Where to find content adaptation?
•Client-based integration
PDA content Adaptation HTML, images
•Server-based integration
Module implemented by server routines
VRML objects
•Network based integration
Entity A
Entity B
Adaptation Module
LANLAN WLANWLANRelayRelay
Séminaire QoS, 25 juin 2004
Presentation plan
1- Content adaptation problem applications
2- Middleware application Layer Concepts Architecture
3- Overlay networks principles current work
4- Overlay management PDP/PEP approach
5- Conclusions
Séminaire QoS, 25 juin 2004
Definition
An overlay network is a network built on top of existing networks
replaces some of the functionality of underlying network e.g. addressing, routing, service model
adds an additional layer of indirection builds a virtual network
makes new services available to applications Resource discovery Enhanced features (multicast, security, reliability)
It is an alternative to changing the global operational infrastructure
Entity A
Entity B
Overlay nodes
Séminaire QoS, 25 juin 2004
Pros: Reuse
Reuse of existing infrastructure (hardware, software, providers)
No modification of existing network layer software/protocols
But Deploy new software on top of existing software
P2P software, ...
Possibly deploy new hardware cache servers, ...
Support evolving network services expensive to develop entirely new networking hardware/software all networks after the telephone have begun as overlay networks
Séminaire QoS, 25 juin 2004
Pros: Reuse !
Not every node needs/wants overlay network service all the time e.g., QoS guarantees for best-effort traffic
Overlay network may be too heavyweight for some nodes e.g., consumes too much memory, cycles, or bandwidth
Overlay network may have unclear security properties e.g., may be used for service denial attack
Overlay network may scale poorly e.g. may require n2 state or communication
Séminaire QoS, 25 juin 2004
Cons
Adds overhead Adds a layer in networking stack
Additional packet headers, processing load at the nodes
Sometimes, additional work is redundant E.g. addressing
Adds complexity Layering does not eliminate complexity, it only manages it
Another layer ! more possible unintended interaction between layers E.g., corruption drops on wireless interpreted as congestion drops by TCP
Séminaire QoS, 25 juin 2004
Presentation plan
1- Content adaptation problem applications
2- Middleware application Layer Concepts architecture
3- Overlay networks principles current work
4- Overlay management PDP/PEP approach
5- Conclusions
Séminaire QoS, 25 juin 2004
QoS policy management
ProxyProxyFiltering
service eg. JPEG2000
JPEG2000 JPEG2000 serverserver
ClienClientt
ClientClient
QoS policy (SLS)QoS policy (SLS)
Decision pointDecision point
Negotiated contract (SLA)Negotiated contract (SLA)
Séminaire QoS, 25 juin 2004
Network Deployment
Two steps procedure:
- at call set up: opening a session and launching adaptation set up : PDP
- during the session: filtering of content : PEP
user
AR
AR
Video server
Router+ PEP
Router
PSJRMPDP
Séminaire QoS, 25 juin 2004
Video adaptation concept demonstrator
The system is composed of three distinct modules:A broadcasting video server A broadcasting video server acts as a source of JPEG images.Its main role is to generate a video flow of images which are sent to a specific proxy. A filter proxyA filter proxyIt receives the image flow from the source and transmits it to the client. The “video” flow is truncated according to the QoS parameters required by each client.Input: flow of JPEG images issued by the source, client transmit/QoS requests Output: personalized “Video” flow for each clientthe client modulethe client moduleAfter sending to the proxy connection and QoS parameters, its role is to receive decompress and display the “video” flow.Input: flow of JPEG images issued by the proxy, Output: client/QoS requests for configuring the proxy.
Flow of JPEG images Video broadcasting server
proxy
PDA client
PC client
Lite PC client
Séminaire QoS, 25 juin 2004
Presentation plan
1- Content adaptation problem applications
2- Middleware application Layer Concepts architecture
3- Overlay networks principles current work
4- Overlay management PDP/PEP approach
5- Conclusions
Séminaire QoS, 25 juin 2004
Conclusions
Overlay network built on top of the Internet for content adaptation
Middleware supports processing of structured data dynamic upload of new processing features rules-based external supervision
On going work Link with overlay management Application to multicast video delivery
Séminaire QoS, 25 juin 2004
End
Thank you !