Enhancing legacy infrastructures with content aware enablers towards a networked-media platform

785 views
710 views

Published on

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

  • Be the first to like this

No Downloads
Views
Total views
785
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
4
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Enhancing legacy infrastructures with content aware enablers towards a networked-media platform

  1. 1. IEEE International Conference on Multimedia and Expo Workshop (ICME)<br />International Workshop on Multimedia-Aware Networking 2011 (WoMAN’11)<br />ENHANCING LEGACY INFRASTRUCTURES WITH CONTENT-AWARE ENABLERS TOWARDS A NETWORKED-MEDIA PLATFORM <br />P.Anapliotis, E.Pallis, D.Negru, V. Zacharopoulos<br />Barcelona, Spain, 11-15 July 2011<br />
  2. 2. Current Internet limitations<br /><ul><li>Service creation and publication: User-generated content is usually provided via centralised content aggregator platforms (such as YouTube, live webcast or social sites)
  3. 3. Service management and adaptation: Media service management takes place mostly at server side. The network is not involved in the media management procedure; adaptation, when applicable, takes place only at service endpoints.
  4. 4. Traffic handling and quality assurance: In best-effort, over-the-top delivery, service quality cannot be assured. Streaming media services have specific transport constraints, which are by default not considered by the network elements involved in the service delivery path</li></li></ul><li>Promising Solutions<br />Content/Service Awareness at the infrastructure level<br />the network’s capability to analyse media-flows and adjust its operation according to the content/service requirements for network available resources and the requested QoS/QoE policies<br />ALICANTE Media Ecosystem<br />Network Awareness at the service level <br />the capability of service/content adaptation according to the underlying network infrastructure and the requested QoS/QoE policies<br />
  5. 5. ALICANTE architecture<br />Building upon these two state-of-the-art approaches/solutions, ALICANTE FP7-ICT project introduces a novel architecture utilising both Service and Network Awareness, besides moving one step beyond by converging them into a common operational system.<br />
  6. 6. Network Environment<br />The Network Environment realises and offers to upper layers a rich and virtualized networked multimedia space, on top of IP, which can be customized and exploited by all business media sectors for delivering networked media content<br />The Network Environment includes:<br /><ul><li>A new Virtual CAN layer, offering virtual connectivity services on top of IP infrastructure, by constructing mono or multi-domain virtual content aware networks (VCANs).
  7. 7. Traditional IP transport layer, supporting MPLS / DiffServ technologies towards instantiating the CANs via its Intra domain Network Resource Managers (Intra-NRM) at request of the CAN manager (CANMng).</li></li></ul><li>The Virtual CAN layer<br />The VCAN layer constitutes an overlay network infrastructure, composed of Virtual Content-Aware Networks (VCAN), spanning single or multiple domains.<br />The CAN layer aims at :<br />a) Improving data delivery by classifying and controlling messages in terms of content, application and individual subscribers.<br />b) Providing QoS assurance, by classifying the packets and associating them to the appropriate virtual path.<br />The CAN layer comprises :<br />The CAN Managers<br />The Media-Aware Network Elements<br />
  8. 8. The CAN Manager @ VCAN layer<br /><ul><li>Main management entity of the VCAN layer
  9. 9. Responsible for
  10. 10. defining/creating the VCANs using the existing IP core infrastructure in order to apply the policies stemming from the interactions (SLA/SLS) of the CANP with the SP
  11. 11. advertising the CAN services to the upper layers
  12. 12. negotiating SLAs with other CAN Mngs in order to establish multi-domain VCAN enabled chains
  13. 13. cooperating with Intra-NRM in order to apply the QoS requirements to the network elements
  14. 14. CANMng’s main responsibility : after concluding the SLA with SP, it forwards policing and QoS classification information for each SLA, to the Intra-NRM (Transport layer) and the Intra-NRM to MANE</li></li></ul><li>The Media-Aware Network Element @ CAN layer<br /><ul><li>Resided at the network edges
  15. 15. Supports network virtualisation and instantiation of overlay VCANs
  16. 16. Responsible to identify the content type transferred in an IP flow
  17. 17. processing of in-band Content Aware Transport Information (CATI) injected at the service layer when the packet stream is created-ALICANTE feature.
  18. 18. deep packet inspection (DPI) detecting higher layer protocol signatures .
  19. 19. statistical methods based on the observation of the data flows
  20. 20. Performs in-network media flow adaptation (for SVC streams)</li></ul>The Content-Aware Transport Information (CATI) is a number of bits declaring specific characteristics of the content (e.g. service type, service sub-type, service priority, VCAN label etc). This information is inserted in the packets at SP level. <br />
  21. 21. The Transport layer<br /><ul><li>Supports the MPLS/DiffServ technologies in the core network domain
  22. 22. MPLS : logical paths inside the core network
  23. 23. Mapping VCANs to LSPs
  24. 24. DiffServ traffic handling and QoS assurance.
  25. 25. Possible configurations
  26. 26. EXP-inferred where the Queue and Drop priority is based solely on the EXP field (8 classes)
  27. 27. LABEL-inferred where the Queue priority is based on LABEL and drop is based on EXP field.
  28. 28. Two possible types of LSP and consequently VCANs.
  29. 29. a single LSP holds different DiffServ Traffic Classes
  30. 30. each single LSP is mapped to one and only traffic class</li></li></ul><li>The Intra-NRM @ Transport Layer<br /><ul><li>The entity to instantiate the connectivity of the two layers.
  31. 31. It has the ultimate authority for configuring/controlling the MANE routers of the CAN network and the MPLS/DiffServ routers of the core network.
  32. 32. Is the responsible to vertically enforce and apply the technical specifications (SLS) of the CANP-SP contracted SLA.
  33. 33. Stores this information(SLA) inside the policy table and sends the appropriate entries of this table to the responsible MANEs.
  34. 34. Dictates and monitors the application of the new policy table at each MANE
  35. 35. Forwards upwards the dimensioning of the network in order to give the CANMng the capability to configure VCANs. </li></ul>Policy Table based on Content Aware Transport Information<br />Generic Policy table<br />
  36. 36. Thank you for your attention!<br />Questions please<br />?<br />http://www.ict-alicante.eu/<br />

×