1. IEEE International Conference on Multimedia and Expo Workshop (ICME) International Workshop on Multimedia-Aware Networking 2011 (WoMAN’11) ENHANCING LEGACY INFRASTRUCTURES WITH CONTENT-AWARE ENABLERS TOWARDS A NETWORKED-MEDIA PLATFORM P.Anapliotis, E.Pallis, D.Negru, V. Zacharopoulos Barcelona, Spain, 11-15 July 2011

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.

5. ALICANTE architecture 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.

9. Responsible for

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. advertising the CAN services to the upper layers

12. negotiating SLAs with other CAN Mngs in order to establish multi-domain VCAN enabled chains

13. cooperating with Intra-NRM in order to apply the QoS requirements to the network elements

15. Supports network virtualisation and instantiation of overlay VCANs

16. Responsible to identify the content type transferred in an IP flow

17. processing of in-band Content Aware Transport Information (CATI) injected at the service layer when the packet stream is created-ALICANTE feature.

18. deep packet inspection (DPI) detecting higher layer protocol signatures .

19. statistical methods based on the observation of the data flows

20. Performs in-network media flow adaptation (for SVC streams)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.

22. MPLS : logical paths inside the core network

23. Mapping VCANs to LSPs

24. DiffServ traffic handling and QoS assurance.

25. Possible configurations

26. EXP-inferred where the Queue and Drop priority is based solely on the EXP field (8 classes)

27. LABEL-inferred where the Queue priority is based on LABEL and drop is based on EXP field.

28. Two possible types of LSP and consequently VCANs.

29. a single LSP holds different DiffServ Traffic Classes

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. Is the responsible to vertically enforce and apply the technical specifications (SLS) of the CANP-SP contracted SLA.

33. Stores this information(SLA) inside the policy table and sends the appropriate entries of this table to the responsible MANEs.

34. Dictates and monitors the application of the new policy table at each MANE

35. Forwards upwards the dimensioning of the network in order to give the CANMng the capability to configure VCANs. Policy Table based on Content Aware Transport Information Generic Policy table

36. Thank you for your attention! Questions please ? http://www.ict-alicante.eu/