SERVICE PROVIDER AND CONTENT AWARE NETWORK PROVIDER CROSS-LAYER  OPTIMISATION OF MULTIMEDIA DISTRIBUTION  ICME  2011 Confe...
Authors ’  affiliation: Eugen Borcoci, Serban Obreja University Politehnica of Bucharest, Romania E [email_address]   Chri...
<ul><li>Introduction </li></ul><ul><li>ALICANTE System Architecture </li></ul><ul><li>CAN Services and Resource Management...
1. Introduction <ul><li>ALICANTE : New challenging concepts (Future Internet – oriented)  </li></ul><ul><ul><li>Content Aw...
2.  ALICANTE System Architecture <ul><li>ALICANTE defines several  environments  containing business actors: </li></ul><ul...
2.  ALICANTE System Architecture <ul><li>ALICANTE high level view </li></ul><ul><li>User Environment </li></ul><ul><li>Ser...
2.  ALICANTE System Architecture <ul><li>Management entities </li></ul><ul><ul><li>User Manager :  UMgr@SP, @HB, @CP, @EU ...
<ul><li>Two main optimisation loops  </li></ul><ul><li>provisioning loop  (OL1)  </li></ul><ul><ul><li>CAN/NAA  </li></ul>...
ICME  2011 Conference, WOMAN Workshop July 11 2011, Barcelona <ul><li>Type of ALICANTE services supported by VCANs </li></...
ICME  2011 Conference, WOMAN Workshop July 11 2011, Barcelona <ul><li>Type of ALICANTE services supported by VCANs </li></...
ICME  2011 Conference, WOMAN Workshop July 11 2011, Barcelona <ul><li>Type of ALICANTE services supported by VCANs </li></...
<ul><li>Resource provisioning: interactions and contracts between business actors </li></ul>3. CAN Services and Resource M...
<ul><li>Optimisation Loop 1: </li></ul><ul><ul><li>Resource provisioning: interactions and contracts between business acto...
<ul><li>Content awareness at CAN Layer </li></ul><ul><li>three ways:  </li></ul><ul><li>by concluding an SLA between SP an...
4. SP-CANP Service Level  Agreements <ul><ul><li>SP-CANP SLS clauses and </li></ul></ul>ICME  2011 Conference, WOMAN Works...
4. SP-CANP Service Level  Agreements <ul><ul><li>SP-CANP SLS clauses (cont ’ d) </li></ul></ul>ICME  2011 Conference, WOMA...
  VCAN types and QoS - examples <ul><ul><li>Topologies: 1-1, 1-Any_n, Any_n-1, nxm, multicast (1-m), combinations </li></u...
6. Conclusions <ul><li>ALICANTE: New architecture media and FI oriented , based on: </li></ul><ul><ul><li>Content aware ne...
<ul><li>THANK YOU </li></ul><ul><ul><ul><li>Questions? </li></ul></ul></ul>ICME  2011 Conference, WOMAN Workshop July 11 2...
<ul><li>Backup slides </li></ul>ICME  2011 Conference, WOMAN Workshop July 11 2011, Barcelona
<ul><li>QoS classes applied  in ALICANTE </li></ul><ul><ul><li>Reuse previous definitions </li></ul></ul><ul><ul><ul><li>L...
  VCAN types and QoS- examples <ul><ul><li>Topologies: 1-1, 1-Any_n, Any_n-1, nxm, multicast (1-m), combinations </li></ul...
Upcoming SlideShare
Loading in …5
×

Service provider and content aware network provider cross layer optimisation of multimedia distribution

1,155 views
1,004 views

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,155
On SlideShare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
8
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Service provider and content aware network provider cross layer optimisation of multimedia distribution

  1. 1. SERVICE PROVIDER AND CONTENT AWARE NETWORK PROVIDER CROSS-LAYER OPTIMISATION OF MULTIMEDIA DISTRIBUTION ICME 2011 Conference, WOMAN Workshop July 11 2011, Barcelona Eugen Borcoci, Serban Obreja, Christian Timmerer, George Xilouris Presentation: George Xilouris
  2. 2. Authors ’ affiliation: Eugen Borcoci, Serban Obreja University Politehnica of Bucharest, Romania E [email_address] Christian Timmerer Department of Information Technology (ITEC) Alpen-Adria-Universität Klagenfurt, Austria e-mail: christian.timmerer@itec.uni-klu.ac.at George Xilouris, NCSR Demokritos Institute of Informatics and Telecommunications, Athens, Greece, [email_address] ICME 2011 Conference, WOMAN Workshop July 11 2011, Barcelona Acknowledgment: This work has been supported by the European Research Project FP7 “ MediA Ecosystem Deployment Through Ubiquitous Content-Aware Network Environments ” ALICANTE project No. 2010-2013.
  3. 3. <ul><li>Introduction </li></ul><ul><li>ALICANTE System Architecture </li></ul><ul><li>CAN Services and Resource Management </li></ul><ul><li>SP-CANP Service Level Agreements </li></ul><ul><li>Use case examples </li></ul><ul><li>Conclusions </li></ul>CONTENTS ICME 2011 Conference, WOMAN Workshop July 11 2011, Barcelona
  4. 4. 1. Introduction <ul><li>ALICANTE : New challenging concepts (Future Internet – oriented) </li></ul><ul><ul><li>Content Aware Networking (CAN) </li></ul></ul><ul><ul><li>Network Aware Application (NAA) </li></ul></ul><ul><li>Novel virtual CAN layer </li></ul><ul><ul><li>as a part of a full layered architecture </li></ul></ul><ul><ul><li>focused, but not limited to, on multimedia distribution with Quality of Services (QoS) assurance </li></ul></ul><ul><li>The paper focus: </li></ul><ul><ul><li>Service Provider and Content Aware Network Provider Cross-layer optimisation </li></ul></ul>ICME 2011 Conference, WOMAN Workshop July 11 2011, Barcelona
  5. 5. 2. ALICANTE System Architecture <ul><li>ALICANTE defines several environments containing business actors: </li></ul><ul><ul><li>User Environment (UE) </li></ul></ul><ul><ul><ul><li>End-Users (EU) </li></ul></ul></ul><ul><ul><li>Service Environment (SE) </li></ul></ul><ul><ul><ul><li>Service Providers (SP) </li></ul></ul></ul><ul><ul><ul><li>Content Providers (CP) </li></ul></ul></ul><ul><ul><li>Network Environment (NE) </li></ul></ul><ul><ul><ul><li>CAN Providers (CANP) - new </li></ul></ul></ul><ul><ul><ul><li>Network Providers (NP) </li></ul></ul></ul><ul><ul><li>Home Box – new entity located at EU premises </li></ul></ul><ul><ul><ul><li>Media flow processing, management, adaptation, routing, caching functions </li></ul></ul></ul><ul><ul><ul><li>HBs- form together a virtual layer included in SE </li></ul></ul></ul><ul><li>Environment : </li></ul><ul><li> - grouping of functions defined around the same goal and possibly spanning, vertically, one or more several architectural (sub-) layers; it has a broader scope, than “ layer” </li></ul>ICME 2011 Conference, WOMAN Workshop July 11 2011, Barcelona
  6. 6. 2. ALICANTE System Architecture <ul><li>ALICANTE high level view </li></ul><ul><li>User Environment </li></ul><ul><li>Service Environment </li></ul><ul><ul><li>SP/CP layer </li></ul></ul><ul><ul><li>HB Layer </li></ul></ul><ul><li>Network Environment </li></ul><ul><ul><li>CAN layer </li></ul></ul><ul><ul><li>Network layer </li></ul></ul>ICME 2011 Conference, WOMAN Workshop July 11 2011, Barcelona
  7. 7. 2. ALICANTE System Architecture <ul><li>Management entities </li></ul><ul><ul><li>User Manager : UMgr@SP, @HB, @CP, @EU </li></ul></ul><ul><ul><li>Service Manager : SMgr@CP, @SP, @HB </li></ul></ul><ul><ul><li>CAN Manager: CANMgr@CANP </li></ul></ul><ul><ul><ul><li>Manages Virtual CANs (unicast, multicast, broadcast) </li></ul></ul></ul><ul><ul><ul><li>Current solution: each network domain (AS) has a CAN Manager </li></ul></ul></ul><ul><ul><li>Intra-domain Network resource Manager IntraNRM@NP </li></ul></ul><ul><ul><ul><li>Manages Media Aware Network Elements (MANE) – routers </li></ul></ul></ul><ul><ul><ul><ul><li>content-aware intelligent routing and forwarding </li></ul></ul></ul></ul><ul><ul><ul><ul><li>QoS </li></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>resource provisioning and allocation ( aggregated level) </li></ul></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>flow adaptation (per flow or aggregated level) </li></ul></ul></ul></ul></ul><ul><ul><ul><ul><li>filtering and specific security functions, data caching </li></ul></ul></ul></ul><ul><ul><ul><ul><li>located at the edges of the domains </li></ul></ul></ul></ul><ul><ul><li>Resource Manager at Access Network : RM@ANP </li></ul></ul><ul><ul><ul><li>Manages the resources of the AN </li></ul></ul></ul><ul><ul><ul><li>Out of ALICANTE scope </li></ul></ul></ul><ul><li>End users can consume and/or generate content and exploit services delivered by components of the SE and supported by CAN transport services </li></ul><ul><li>SLAs between SP- CANP – to setup VCANs at SP request </li></ul>ICME 2011 Conference, WOMAN Workshop July 11 2011, Barcelona
  8. 8. <ul><li>Two main optimisation loops </li></ul><ul><li>provisioning loop (OL1) </li></ul><ul><ul><li>CAN/NAA </li></ul></ul><ul><ul><ul><li>SP, CANP, (NP) </li></ul></ul></ul><ul><li>adaptation loop (OL2) </li></ul><ul><ul><li>Network </li></ul></ul><ul><ul><li>HB, terminals </li></ul></ul><ul><ul><li>monitoring system </li></ul></ul><ul><ul><ul><li>QoS, QoE probes </li></ul></ul></ul><ul><ul><li>ADTF </li></ul></ul>2. ALICANTE System Architecture ICME 2011 Conference, WOMAN Workshop July 11 2011, Barcelona <ul><li>Content and context aware architecture at network layer </li></ul>
  9. 9. ICME 2011 Conference, WOMAN Workshop July 11 2011, Barcelona <ul><li>Type of ALICANTE services supported by VCANs </li></ul><ul><ul><li>Fully Managed Services (FM) </li></ul></ul><ul><ul><li>Partially managed Services (PM) </li></ul></ul><ul><ul><li>Unmanaged Services (UM) </li></ul></ul><ul><ul><li>This split captures two point of views </li></ul></ul><ul><ul><ul><li>Services: (degree) how strict the QoS requirements are </li></ul></ul></ul><ul><ul><ul><li>CANP: shows the degree of the CAN layer freedom to perform autonomic actions </li></ul></ul></ul><ul><li>Fully Managed Services </li></ul><ul><ul><li>High priority services in ALICANTE: delivered by the SP and the in some cases EU ’s HB </li></ul></ul><ul><ul><li>SLAs exists agreed between SP and CANP </li></ul></ul><ul><ul><ul><li>Services requirements: Guaranteed: (low) packet delay; bandwidth; (low) packet loss; possible secure, private connectivity </li></ul></ul></ul><ul><ul><ul><li>VCANs provisioned by the CANP to answer the requirements </li></ul></ul></ul><ul><ul><ul><ul><li>Different levels of guarantees are possible </li></ul></ul></ul></ul><ul><ul><li>Services adaptation may be performed - if necessary- at HB and MANE level- but in the limits of the SLA </li></ul></ul>3. CAN Services and Network Resource Management
  10. 10. ICME 2011 Conference, WOMAN Workshop July 11 2011, Barcelona <ul><li>Type of ALICANTE services supported by VCANs </li></ul><ul><ul><li>Partially managed Services (PM) </li></ul></ul><ul><ul><ul><li>The CAN layer has more freedom (to act upon flows) than in FM case </li></ul></ul></ul><ul><ul><ul><li>Still one may have a contract SP-CANP specifying: </li></ul></ul></ul><ul><ul><ul><ul><li>PM1: some minimum QoS guarantees (quantitative) – plus some extra, or </li></ul></ul></ul></ul><ul><ul><ul><ul><li>PM2: only statistical/qualitative (weak) guarantees </li></ul></ul></ul></ul><ul><ul><ul><li>CAN layer may apply adaptation if necessary: </li></ul></ul></ul><ul><ul><ul><ul><li>PM1 case: not to violate the contract (in normal network operation cases) </li></ul></ul></ul></ul><ul><ul><ul><ul><li>PM2 case: any adaptation operation in the network is allowed to CAN layer in order to do &quot;its best ” </li></ul></ul></ul></ul><ul><ul><li>Unmanaged Services: </li></ul></ul><ul><ul><ul><li>No contract SP – CANP </li></ul></ul></ul><ul><ul><ul><li>CAN layer </li></ul></ul></ul><ul><ul><ul><ul><li>Still may offer some QoS </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Is totally free to treat the traffic conforming the NP policy </li></ul></ul></ul></ul>3. CAN Services and Network Resource Management
  11. 11. ICME 2011 Conference, WOMAN Workshop July 11 2011, Barcelona <ul><li>Type of ALICANTE services supported by VCANs </li></ul><ul><ul><li>Hard Guarantees – HG </li></ul></ul><ul><ul><li>Statistical Quantitative Guarantees- SQnG </li></ul></ul><ul><ul><li>Statistical Qualititative Guarantees – SQlG </li></ul></ul><ul><ul><li>No guarantees (Best Effort) – BE </li></ul></ul><ul><li>Notations: </li></ul><ul><li>BQ1, BQ2, .. Different sets of Bandwidth reqs. </li></ul><ul><li>(decreasing QoS order) </li></ul><ul><li>DLJ-Q1, 2, ..- different sets of DJL reqs (decreasing QoS order) </li></ul><ul><li>QoS classes </li></ul><ul><ul><li>Well known- int ’l (Meta QC) </li></ul></ul><ul><ul><li>Local (LQC) composition </li></ul></ul>3. CAN Services and Network Resource Management
  12. 12. <ul><li>Resource provisioning: interactions and contracts between business actors </li></ul>3. CAN Services and Resource Management ICME 2011 Conference, WOMAN Workshop July 11 2011, Barcelona
  13. 13. <ul><li>Optimisation Loop 1: </li></ul><ul><ul><li>Resource provisioning: interactions and contracts between business actors </li></ul></ul><ul><li>contracts/interactions of SLA/SLS types performed in the Management and Control Plane and the appropriate I/Fs exist: </li></ul><ul><li>SP-CANP(1) : the SP requests to CANP to provision/ modify/ terminate new VCANs and the CANP to inform SP about its capabilities </li></ul><ul><li>CANP-NP(2) - the NP offers or commits to offer resources to CANP (this data are topological, QoS and capacity-related) </li></ul><ul><li>CANP-CANP(3) - to extend a VCAN upon several NP domains; </li></ul><ul><li>- Network Interconnection Agreements (NIA) (4) between the NPs or between NPs and ANPs </li></ul><ul><ul><li>these are not innovative ALICANTE functionalities but are necessary for NP cooperation. </li></ul></ul><ul><li>After the SP negotiates a desired VCAN with CANP, </li></ul><ul><ul><li>it will issue the installation commands to CANP </li></ul></ul><ul><ul><li>which in turn configures via IntraNRM (5) the MANE functional blocks (input and output). </li></ul></ul>3. CAN Services and Resource Management ICME 2011 Conference, WOMAN Workshop July 11 2011, Barcelona
  14. 14. <ul><li>Content awareness at CAN Layer </li></ul><ul><li>three ways: </li></ul><ul><li>by concluding an SLA between SP and CANP, concerning different VCAN(s) construction. </li></ul><ul><ul><ul><li>The content servers are instructed by the SP to insert some special Content Aware Transport Information (CATI). </li></ul></ul></ul><ul><ul><ul><li>This simplifies the media flow classification and treatment by the MANE. </li></ul></ul></ul><ul><li>the SLA is concluded, but no CATI information is inserted in the data packets. </li></ul><ul><ul><li>The MANE applies Deep Packet Inspection for data flow classification and assignment to VCANs. </li></ul></ul><ul><ul><li>The treatment of the flows is based on VCANs characteristics defined in the SLA. </li></ul></ul><ul><li>no SLA exists between SP and CANP </li></ul><ul><ul><li>No CATI is inserted in the data packets </li></ul></ul><ul><ul><li>The treatment of the data flows can still be CA-style, but conforming to the local policy established at CANP and IntraNRM. </li></ul></ul>3. CAN Services and Resource Management ICME 2011 Conference, WOMAN Workshop July 11 2011, Barcelona
  15. 15. 4. SP-CANP Service Level Agreements <ul><ul><li>SP-CANP SLS clauses and </li></ul></ul>ICME 2011 Conference, WOMAN Workshop July 11 2011, Barcelona SLS Element/Clause SLS Identification VCAN Associated CATI VCAN Connectivity Services Req . Topology & scope: (pipe, hose, funnel, multicast tree, etc.) and scope (ingress, egress points) Connectivity class (guarantees): quantitative/qualitative: delay, jitter, loss, availability Bandwidth (capacity) VCAN Traffic Processing Req. Access and transfer rules: Ingress flow Id, Egress flow Id, Ingress point, Egress point Access and transfer rules: QoS Guarantees: Class, (dropping, re-marking, shaping) Access and transfer rules: QoS guarantees: Conformance algorithm Access and transfer rules: QoS Guarantees: Excess traffic treatment Routing and Forwarding rules Security requirements Adaptation requirements Reliability
  16. 16. 4. SP-CANP Service Level Agreements <ul><ul><li>SP-CANP SLS clauses (cont ’ d) </li></ul></ul>ICME 2011 Conference, WOMAN Workshop July 11 2011, Barcelona VCAN Services Assessment Req. Monitoring methodology Monitoring tasks Notification and Reports VCAN Allowed actions Availability and VCAN service schedule Invocation methods Modification permission (of): Connectivity services; Traffic Processing; Service Assessment
  17. 17. VCAN types and QoS - examples <ul><ul><li>Topologies: 1-1, 1-Any_n, Any_n-1, nxm, multicast (1-m), combinations </li></ul></ul><ul><ul><li>Example: Multicast + SVC based adaptation </li></ul></ul>ICME 2011 Conference, WOMAN Workshop July 11 2011, Barcelona <ul><ul><li>Multi-domain peering and QoS classes </li></ul></ul><ul><ul><ul><li>VCAN based on well known QCs ( Meta QC) </li></ul></ul></ul><ul><ul><ul><li>VCAN as a composition of Local QC </li></ul></ul></ul><ul><ul><ul><li>Hierarchical VCAN + local QC </li></ul></ul></ul>5. Use case examples
  18. 18. 6. Conclusions <ul><li>ALICANTE: New architecture media and FI oriented , based on: </li></ul><ul><ul><li>Content aware networking </li></ul></ul><ul><ul><li>Network aware applications </li></ul></ul><ul><ul><li>QoS capable </li></ul></ul><ul><ul><ul><li>Different classes of services, Level of guarantees </li></ul></ul></ul><ul><ul><ul><li>Use traditional network layer QoS technologies: MPLS, Diffserv </li></ul></ul></ul><ul><li>Two main cross- layer optimisation loops </li></ul><ul><ul><li>Resource provisioning ( SP-CANP-NRM cooperation) </li></ul></ul><ul><ul><li>Media flow adaptation (see slide 8) </li></ul></ul><ul><li>Future work </li></ul><ul><ul><li>Specification refinements, Design, Implementation, Integration , Use case experiments </li></ul></ul><ul><ul><li>Performances analysis or different solutions </li></ul></ul>ICME 2011 Conference, WOMAN Workshop July 11 2011, Barcelona
  19. 19. <ul><li>THANK YOU </li></ul><ul><ul><ul><li>Questions? </li></ul></ul></ul>ICME 2011 Conference, WOMAN Workshop July 11 2011, Barcelona
  20. 20. <ul><li>Backup slides </li></ul>ICME 2011 Conference, WOMAN Workshop July 11 2011, Barcelona
  21. 21. <ul><li>QoS classes applied in ALICANTE </li></ul><ul><ul><li>Reuse previous definitions </li></ul></ul><ul><ul><ul><li>Local QoS classes l-QC( related to Per Domain Behaviour –PDB) </li></ul></ul></ul><ul><ul><ul><li>Extended QoS Classes (E-QC) = composition of l-QCs </li></ul></ul></ul><ul><ul><ul><li>Meta-QoS-Class , (MQC) ( Tequila, Mescal FP5, FP6 EU projects) </li></ul></ul></ul><ul><ul><ul><ul><li>common set of QoS ranges of parameters spanning several domains </li></ul></ul></ul></ul><ul><li>Mapping VCANs to QoS Classes </li></ul><ul><ul><li>Multi-domain VCANs based on </li></ul></ul><ul><ul><ul><li>1-to-1 mapping VCAN- MQC ( well known by CAN Managers of different domains </li></ul></ul></ul><ul><ul><ul><li>local QC composition </li></ul></ul></ul><ul><ul><li>Multi-domain hierarchical CANs based on local QC composition </li></ul></ul><ul><ul><ul><li>most rich granularity </li></ul></ul></ul>ICME 2011 Conference, WOMAN Workshop July 11 2011, Barcelona 3. CAN Services and Resource Management
  22. 22. VCAN types and QoS- examples <ul><ul><li>Topologies: 1-1, 1-Any_n, Any_n-1, nxm, multicast (1-m), combinations </li></ul></ul>ICME 2011 Conference, WOMAN Workshop July 11 2011, Barcelona <ul><ul><li>Multi-domain peering and QoS classes) </li></ul></ul><ul><ul><ul><li>VCAN based on well known QCs ( Meta QC) </li></ul></ul></ul><ul><ul><ul><li>VCAN as a composition of Local QC </li></ul></ul></ul><ul><ul><ul><li>Hierarchical VCAN + local QC </li></ul></ul></ul>5. Use case examples

×