IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Future Project Planning Report Date Submitted: November 4, 2011 Presented at IEEE session #47 in Atlanta Authors or Source(s): Antonio de la Oliva, Daniel Corujo Abstract: Future Project Planning Report as of November 4,

2 IEEE presentation release statements This document has been prepared to assist the IEEE Working Group. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein. The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE The contributor is familiar with IEEE patent policy, as stated in Section 6 of the IEEE-SA Standards Board bylaws and in Understanding Patent Issues During IEEE Standards Development Section 6 of the IEEE-SA Standards Board bylawshttp://standards.ieee.org/guides/bylaws/sect6-7.html#6http://standards.ieee.org/board/pat/faq.pdf

Summary of activities 3 audio-conferences since July Sessions held on last meeting at Bangkok Multiple offline discussions to define scenarios

Summary of ideas Multi-Interface Management L2.5 mesh Multicast signaling support DMM and new mobility paradigms Extending the MIIS with policies QoS Integration of different technologies Extended Capability Discovery Dynamic MIIS

Summary of ideas Multi-Interface Management  possible new PAR L2.5 mesh  possible new PAR Multicast signaling support DMM and new mobility paradigms  Maintenance PAR Extending the MIIS with policies QoS Integration of different technologies  Dead Extended Capability Discovery  Dynamic Information Services Dynamic MIIS

Dynamic Information Services Mechanism to provide information to the network and terminal Characteristics of this service: 3GPP compatible Dynamic information Service oriented/enable service discovery (with service we mean e.g., VoLTE support or emergency service or even something more elaborated) Providing mechanisms for asynchronous network based information retrieving from e.g., PoAs (no need for request)

Use cases Service based network selection: User in an airport desires to connect to WLAN hotspot, it requires the hotspot to support e.g., VPN service. Some mechanism enables the user to obtain this information and connect to the most appropriate network Smart network selection based on dynamic information: A user is viewing a long youtube video while waiting for the bus. In order to free resources in the 3G network, the operator (or the user) decides to move the video flow to a different interface. The nearest AP is serving several users, the network decides to move the user to a different AP due to load conditions

Use cases Aiding load based network optimizations: A plane has just arrived at the terminal of the airport. All users are getting out the plane while activating their cellular, checking , twitter etc.. The operator is able to load balance the avalanche of new users within the same technology and with the help of others by attaching users to PoAs. Energy based optimizations: By selective offloading users and monitoring the load of the different PoAs, the network is able to shutdown/sleep some of its infrastructure

Use case and characteristics 3GPP compatibleDynamic Information Service OrientedAsynchronous Information Service based network selection xx Smart Network Selection based on dynamic information xxx Aiding load based network optimizations xxx Energy based optimization xxx

Implementation Hierarchical Information Services replying to information requests about PoAs do not need to have information about the whole infra-structure of the operator/domain The hierarchical deployment of this information allow it to be deployed into servers by zone, or domain. Queries about detected PoAs, but belonging to another domain/zone, can be forwarded to a information server existing in a higher level of the hierarchy On the cloud? Are we able to do this distributed enough so it can be pushed to the cloud?