Ref. Ares(2015)964509 - 04/03/2015 317959 Mobile Opportunistic Traffic Offloading D4.2 – Protocols for infrastructure offloading control and coordination D4.2 – Protocols for infrastructure offloading control and coordination WP4 –Offloading protocols and algorithms Grant Agreement No. 317959 Project acronym MOTO Project title Mobile Opportunistic Traffic Offloading Advantage Deliverable number D4.2 Deliverable name Protocols for infrastructure offloading control and coordination Version V 1.0 Work package WP4 – Offloading protocols and algorithms Lead beneficiary FON Authors Alaitz García, David Valerdi (FON), Filippo Rebecchi, Farid Benbadis (TCS), Raffaele Bruno, Andrea Passarella, Lorenzo Valerio (CNR) Patricia Ortiz, Daniel Alcaraz and Iván Prada (INNO). Nature R – Report Dissemination level PU – Public Delivery date 31/10/2014 (M24) © MOTO Consortium – 2014 1 D4.2 – Protocols for infrastructure offloading control and coordination WP4 –Offloading protocols and algorithms Table of Contents ACRONYMS ............................................................................................................................................ 4 EXECUTIVE SUMMARY ........................................................................................................................... 5 1. INTRODUCTION .............................................................................................................................. 6 2. OFFLOADING ALGORITHMS: DEFINITION AND PRINCIPLES .............................................................. 8 2.1 PUSH/PULL SCENARIO ........................................................................................................................... 8 2.2 OFFLOADING ALGORITHM AT A GLANCE .................................................................................................... 9 2.3 INFORMATION REQUIRED BY THE MOTO SERVICE FROM EXTERNAL ENTITIES AND TERMINALS ......................... 10 2.4 DISSEMINATION STRATEGIES................................................................................................................. 12 3. COMMUNICATIONS WITH EXTERNAL INFRASTRUCTURE OPERATORS ............................................ 13 3.1 INTERFACE DEFINITION ......................................................................................................................... 13 3.2 PROTOCOL ANALYSIS ........................................................................................................................... 15 3.2.1 Proprietary protocol .................................................................................................................. 15 3.2.2 Web API technologies ................................................................................................................ 15 3.2.2.1 SOAP .................................................................................................................................. 16 3.2.2.2 RESTful .............................................................................................................................. 16 3.3 PROTOCOL SELECTION ......................................................................................................................... 16 4. COMMUNICATIONS WITH TERMINALS .......................................................................................... 18 4.1 INTERFACE DEFINITION ......................................................................................................................... 18 4.2 PROTOCOL ANALYSIS ........................................................................................................................... 19 4.2.1 Proprietary Protocol .................................................................................................................. 19 4.2.2 HTTP Based ................................................................................................................................ 19 4.2.2.1 OMA-DM 2.0 ..................................................................................................................... 19 4.2.2.2 Atom publishing protocols ................................................................................................ 20 4.2.3 Non-Http based ......................................................................................................................... 21 4.2.3.1 MQTT Protocol .................................................................................................................. 21 4.3 PROTOCOL SELECTION ......................................................................................................................... 22 5. COMMUNICATIONS WITH EXTERNAL CONTENT PROVIDERS .......................................................... 23 6. SECURITY ASPECTS ....................................................................................................................... 24 6.1 OFFLOADING ALGORITHMS SECURITY CONSIDERATIONS ............................................................................. 24 6.2 SECURITY CONSIDERATIONS IN THE COMMUNICATIONS WITH EXTERNAL INFRASTRUCTURE OPERATORS .............. 27 6.3 SECURITY CONSIDERATIONS IN THE COMMUNICATIONS WITH TERMINALS ..................................................... 29 7. CONCLUSION ............................................................................................................................... 32 8. APPENDIX .................................................................................................................................... 33 9. REFERENCES ................................................................................................................................. 39 DISCLAIMER ......................................................................................................................................... 40 © MOTO Consortium – 2014 2 D4.2 – Protocols for infrastructure offloading control and coordination WP4 –Offloading protocols and algorithms List of Tables Table 1: Acronyms ............................................................................................................................................. 4 Table 2: Required MOTO Service information. ............................................................................................... 11 Table 3: Communication messages between Infrastructure Operator and Infrastructure API. ..................... 14 Table 4 Comparison between SOAP and RESTful. ........................................................................................... 17 Table 5 Communication messages between Infrastructure Operator and terminals. .................................... 18 Table 6: Communication messages between Infrastructure Operator and Content Provider. ...................... 23 Table 7: Methods needed to implement for the communication between the MOTO Platform and the end users’ terminals....................................................................................................................................... 34 Table 8: Methods needed to implement for the communication between the MOTO Platform and the Infrastructure Operators......................................................................................................................... 36 List of Figures Figure 1. - MOTO specification overview. ......................................................................................................... 6 Figure 2. - MOTO Architecture [3] ..................................................................................................................... 7 Figure 3: Involved mechanisms depending on push or pull scenario. .............................................................. 8 Figure 4: MOTO Content Delivery Manager functioning: Initially a small amount of copies is injected through the LTE data channel to kick start the dissemination process. Content is diffused through opportunistic communications. Upon content reception, users acknowledge the offloading agent using the control channel. MOTO Content Delivery Manager may re-inject additional copies to control the diffusion. 100% delivery ratio is reached through fallback re-injections. .......................................... 9 Figure 5. Effect of a bad seed selection node in the initial phases of propagation ........................................ 24 Figure 6. Rearrangement of user based on trust (1) ....................................................................................... 25 Figure 7. Delivery of trust related information about potential seed users (2) .............................................. 26 Figure 8. Discard of user to be seeds based on trust profile (3) ..................................................................... 26 Figure 9. Combination of the different methods for seed recommendation delivery (4) .............................. 27 Figure 10: HTTP GET Request ......................................................................................................................... 35 Figure 11: POST HTTP Request ........................................................................................................................ 36 Figure 12: HTTP GET request. .......................................................................................................................... 38 Figure 13: HTTP GET request. .......................................................................................................................... 38 © MOTO Consortium – 2014 3 D4.2 – Protocols for infrastructure