PROTECTED SEAMLESS CONTENT DELIVERY IN P2P WIRELESS AND WIRED NETWORKS

1. PROTECTED SEAMLESS CONTENT DELIVERY IN P2P WIRELESS AND WIRED NETWORKS 指導教授：童曉儒 教授組別：第二組報告者：盧玉玲 (M9856038) 沈宗億 (M9756025) 歐宗明 (M9856011) 黃承晧 (M9856021) 買冠億 (M9756020)

2. TECHNOLOGY PILLARS • As mentioned before, the combination of all these technologies provides our system with novelty and appeal. • These technology pillars are: • Multilayered/multiview content coding • Multisource/multinetwork streaming and adaptation architectures • The content protection and lightweight asset • management system

3. MULTILAYERED/MULTIVIEWCONTENT CODING • For the proposed architecture, we have considered H.264/MPEG4-SVC and H.264/MPEG4-MVC as the major content formats to be delivered over heterogeneous networks.

4. MULTISOURCE/MULTINETWORK STREAMING AND ADAPTATION ARCHITECTURES • The second technology pillar used is multisource/multinetwork streaming and adaptation. • Although the system is prepared for mesh P2P logical overlay technologies, it can also be used in broadcasting networks, such as digital video broadcasting-terrestrial (DVB-T), DVB satellite (DVB-S), DVB cable (DVB-C), interactive/on demand bidirectional networks ( WiMAX), and mobile networks such as third/fourth generation (3G/4G) and DVB-H .

5. CONTENT PROTECTION AND LIGHTWEIGHT ASSET MANAGEMENT • By this pillar, new business models for large-scale content distribution will be facilitated side by side with a proper content protection and asset management mechanism. • On one hand, we provide encryption technologies to be embedded in the H.264/MPEG4-SVC/MVC encoder and decoder, extending content protection mechanisms based on ISMACryp for point-to-multipoint and P2P topologies.

6. CONTENT PROTECTION AND LIGHTWEIGHT ASSET MANAGEMENT

7. CONTENT PROTECTION AND LIGHTWEIGHT ASSET MANAGEMENT • We have designed the MANE nodes (sHMG and sNMG) as network-based components for architecture that support intelligent seamless content distribution. • Moreover, as they have knowledge of the underlined networks, they provide information on the network conditions/features, which is utilized by the cross-layer control (CLC) mechanism, and adapt the multimedia streams to the next network in the delivery path.

8. CONTENT PROTECTION AND LIGHTWEIGHT ASSET MANAGEMENT • sHMG is able to offer multimedia content adaptation and caching/storage functions to the service provider and the community. • The storage capabilities of the sHMG are divided in two partitions. • One partition is allocated to the user for his/her personal/private content. This content is distributed on user demand and under user permissions, by means of the P2P communications network.

9. CONTENT PROTECTION AND LIGHTWEIGHT ASSET MANAGEMENT • The second partition is allocated to the service provider and/or the community network, and is utilized as a temporal cache. • As content protection and management are provided, network operators and service providers may offer value-added streaming services with remarkable PQoS.

10. CONTENT PROTECTION • We aim to provide an end-to-end solution for content protection management for IP and P2P networks, I exploiting the full potential of content protection and creator’s rights maintenance. • This ciphering technology is applied to each layer (in SVC) or view (in MVC) of an H.264/MPEG4-SVC/MVC video stream separately.

11. CONTENT PROTECTION (Cont) • Especially for the P2P network architecture, a secure content protection technology is needed because the content passes a number of peer nodes that are not always trusted and can easily keep a copy of the content. • When content encryption is applied at the server (which in the targeted architecture can be the terminal of any user), only entitled users can decryptand view a specific layer or view certain content.

12. CONTENT PROTECTION (Cont) • For the interface between the scrambler and the licensing system, we have followed the DVB SimulCrypt specification , which allows using the encrypting core technology with different conditional access systems either as alternative implementations or even at the same time. • With respect to the envisioned new paradigm of any user being a content creator, it is very important toprovide a standardized interface .

13. CONTENT PROTECTION (Cont) • CA (Conditional Access) 密鑰 加密 密鑰 加密 密鑰

14. CONTENT PROTECTION (Cont) • Real-Time Transport Protocol (RTP) • RTP Header • RTP Features • Sequence number • Timestamp

15. CONTENT PROTECTION (Cont) • Content protection system process 3.使用「即時傳輸協定」傳送「影音壓縮封包」 7.擾碼器 8.傳送 6.CW密鑰，加密影音封包 5.協調不同CA系統， 同時間處理CW密鑰 2.影音壓縮 4.產生CW密鑰 4.傳送ECM 1.更新CW密鑰 3.加密CW密鑰，成ECM 1.從儲存體， 取出MP4檔 案格式的影片 2.加密SK密鑰，成EMM 2.傳送CW密鑰 1.傳送解ECM的SK密鑰

16. CONTENT MANAGEMENT SYSTEM • Due to the fact that distributed P2P architectureclients do not establish a secure connection with a server and download content, the network architecture entails serious security problems. • For this reason, we propose a semi-distributed P2P-based architecture, in which some critical functions exist in a dedicated content management server, while all others lie in peer node .

17. Implemented Solution • As mentioned above, we targeted a secure SVC/MVC content management and media sharing system that can be divided into server side and client side. • We decided to follow the DVB SimulCrypt specification for the implementation in order to make it easier to adapt the content protection system to the content management system, but our target has always been to implement a lightweight and interoperable management system.

18. Implemented Solution(2) • This implementation gives the system the capability to be compatible with other content management system implementations, DRM systems, and so on. • Figure 3 shows an overview of the content protection and key management system.

19. Figure 3. An overview of the content protection and key management system. • The content management system consists of a server agent with several functions.

20. Figure 3. An overview of the content protection and key management system.

21. Implemented Solution(3) • Finally, the server acts as a license management agent, keeping a list of all the available licenses in order to let the clients know which licenses they have purchased and modifying the content of the license accordingly .

22. An example of the functionality of the P2Pcontent management system is shown in Fig. 3

23. An example of the functionality of the P2Pcontent management system is shown in Fig. 3

24. An example of the functionality of the P2Pcontent management system is shown in Fig. 3

25. An example of the functionality of the P2Pcontent management system is shown in Fig. 3

26. An example of the functionality of the P2Pcontent management system is shown in Fig. 3

27. An example of the functionality of the P2Pcontent management system is shown in Fig. 3 • To complete our system, we need to add some plug-ins into the media player included in the device in order to provide the system with all these functionalities.

28. An example of the functionality of the P2Pcontent management system is shown in Fig. 3 • First, an SVC codec plug-into the client’s media player is added. Thus, thecontent is available in several resolutions to satisfydifferent clients’ needs. • Additionally, a plug-in is added to the media player to make it able to create and understand the licenses, and execute the content as the rights object authorizes it to do. • Finally, the ISMACryp decrypting capabilities are included in the client environment, while the ISMACryp proxy is located at the server side.

29. ECMG and EMMG • ECM • The ECM generator creates an ECM message, which includes the CW that has been used to encrypt the content following the ISMACryp standard, and some other parameters needed to establish connection between this particular module and the SCS module. • EMM • the EMM messages are generated by the EMM generator module, also included in the server. An EMM contains the license, which indicates the actions a user can take on specified content and the necessary key to decrypt the encrypted CW of the ECM.

30. Figure 4. Interaction between ECM and EMM messages.

31. Key Management In order to control all the keys that get into the action, the system includes a key management system. In the proposed content management system, two different set of keys are implicated. 1.One of them is needed to encrypt the CW generated by the ISMACryp Proxy, as described earlier. This encryption takes place in the ECMG module. 2.The other set of keys is needed to encrypt the license, which takes place in the license management module.

32. License Management The implemented license management system gives the user the freedom to create and modify its licenses, so we can define it as a personalized license management system. For this reason, it needs to be located at the client side for generating and performing the license, and also at the server side for delivery of the license to the users that request it.

33. License Management(cont.) License management system.

34. Use Cases According to the consumption permission given to the media content, we can distinguish several use cases that should be treated in our model: 1.Content that can be consumed by any user. 2. Encrypted content restricted to a set of users selected by the author. -The creator sends them the key (by email, phone call, etc.), giving them the freedom to consume it whenever they desire. -The creator wants to have control over the content and avoid its consumption by other people.

35. System Testing Architecture General testing architecture

36. 工作分配

37. Thank You !