Download Content Adaptation in heterogeneous Environment

Content adaptation for gradual Quality of Service
I T &S
A e r o s p a c e
D e f e n c e
Vania Conan, Arnaud Pierre
Thales
[email protected]
[email protected]
Example problem: video over heterogeneous networks
User with Mobile
phone
User with
laptop PC
Group of users
User with
PDA
Problem:
How to manage QoS in heterogeneous networks characterised by
various types of radio links (UMTS, WLAN, …) , load variations
and typology.
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
Conditions
Input
information
Content
Content
adaptation
Examples of needs for content adaptation
1. HTML content adaptation
2. VRML
3. Video
Séminaire QoS, 25 juin 2004
adapted
information
Content
Progressive Transmission by quality
Compressed Image bitstream
0.125bpp
Séminaire QoS, 25 juin 2004
0.25bpp
1bpp
lossless
Progressive Transmission by resolution
Compressed Image bitstream
Séminaire QoS, 25 juin 2004
Content adaptation
adapt information Nature or/and Structure
to a set of constraints
Content
adaptation
Wireless
Network
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
End user
Equipment
User
Profile
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
Information
Content
Header
Cell:: (Header, Content)>
Header:: (Parameter +)
Content:: (Properties, Data)
Properties:: (Property *)
Information structure: a “cell”
Rules
CAM
Incoming cell
Séminaire QoS, 25 juin 2004
Output cell
Information Flow
Content adaptation Service
information level
cell level
00101101…
transport level
text...
Cell Parsers
Séminaire QoS, 25 juin 2004
A system of rules
If [setOfProperties] Then [...] Else […]
Content properties
Context
(System state)
Type
Of Content
Set of Rules
Content
Séminaire QoS, 25 juin 2004
Loaded Service
Adapted
Content
Rule design DTD Description
<?xml version='1.0' encoding='utf-8'?>
<!-- DTD: RULE STRUCTURE --><!ELEMENT rule (ruleID, instruction)>
<!ELEMENT ruleID (#PCDATA)>
<!ELEMENT instruction (condition, thenExpression, elseExpression)>
<!ELEMENT condition (booleanExpression)>
<!ELEMENT booleanExpression (operator, operandList)>
<!ELEMENT operator (and|or|not)>
<!ELEMENT and EMPTY>
<!ELEMENT or EMPTY>
<!ELEMENT not EMPTY>
<!ELEMENT operandList (operand+)>
<!ELEMENT operand (booleanExpression|property)>
<!ELEMENT property EMPTY>
<!ATTLIST property name CDATA #REQUIRED>
<!ELEMENT thenExpression (instruction|statement)>
<!ELEMENT elseExpression (instruction|statement)>
<!ELEMENT statement (serviceID)>
<!ELEMENT serviceID (#PCDATA)>
Séminaire QoS, 25 juin 2004
Module Architecture
Libraries of Resources
External Communication
Serv.
Events
generation
Module
Rules
Info
Process Management
Processor
Factory
Statistics &
evaluation
Information Capture
Cell
capture
Content
extraction
Messages
Management
Module
CAM State Management
Process
Profile
Management
CAM
State
Information Delivery
Cell
generation
Content
formatting
Cell parser Library
Séminaire QoS, 25 juin 2004
Where to find content adaptation?
•Client-based integration
Entity A
PDA content Adaptation

Entity B
HTML, images
•Server-based integration
Adaptation Module
Module implemented by server
routines

VRML objects
•Network based integration
Séminaire QoS, 25 juin 2004
LAN
Relay
WLAN
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

Entity A
builds a virtual network
Entity B
 makes new services available to applications

Resource discovery
 Enhanced features (multicast, security, reliability)
It is an alternative to
 changing the global operational infrastructure
Séminaire QoS, 25 juin 2004
Overlay nodes
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
Negotiated contract (SLA)
Decision point
QoS policy (SLS)
JPEG2000 server
Proxy
Client
Filtering service
eg. JPEG2000
Client
Séminaire QoS, 25 juin 2004
Network Deployment
PDP
JRM
PS
Router
Router+ PEP
AR
AR
Video
server
user
Two steps procedure:
- at call set up: opening a session and launching adaptation set up : PDP
- during the session: filtering of content : PEP
Séminaire QoS, 25 juin 2004
Video adaptation concept demonstrator
The system is composed of three distinct modules:
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 proxy
It 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 client
the client module
After 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.
PDA client
PC client
Flow of JPEG images
Video broadcasting server
proxy
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 !
Séminaire QoS, 25 juin 2004