Abstract
Abstract. Future high quality communication services will be offered in an integrated or converged network infrastructure maintaining both fixed wireless and mobile access via multi-mode user terminals. A support of various scenarios of user and/or terminal mobility within a common IP-based infrastructure requires intelligently designed control protocols. A major challenge is to provide seamless (i.e. lossless and low delay) handover between different radio cells and operator domains to enable continuation of unicast and multicast sessions while using network resources most efficiently. IETF (Internet Engineering Task Force) is specifying related IP mobility management protocols to be applicable also to a flat architecture as envisaged by Next Generation (Mobile) Networks (NGNs/NGMNs). The contribution will describe operator requirements towards such an approach. Both single-domain and multi-domain scenarios will be discussed based on federation ideas. Already existing solutions are taken into consideration and application of solution proposals towards a Distributed Mobility Management (DMM) currently under evaluation within IETF will be outlined.
Highlights
Further classification is the amount of entities which have to participate in the mobility process, i.e. whether both session end points (MN and core network (CN)) have to be mobility-aware or the MN only – or even none of them
The amount of nodes which can be handled by a system concurrently puts a limitation which may be caused by e.g. signalling effort per handover and network entity
The results of additional data rate required for messages are separated into portion occurring on the radio link (MNMAG) and within the access network (AN), i.e. on interMAG links, and core network (CN) where the Mobility Access Gateway (MAG)-Local Mobility Anchor (LMA) tunnel is assumed to be located is calculated as product of message amount n and size N for each area
Summary
A heterogeneous access network infrastructure to allow such a flexible service provision will rely on a common IP-based infrastructure This concept allows a future integrated mobile as well as fixed network access as outlined by 3GPP (2011). Further classification is the amount of entities which have to participate in the mobility process, i.e. whether both session end points (MN and CN) have to be mobility-aware or the MN only – or even none of them In the latter case only the network (operator) controls the mobility-related activities whereas in the other approaches the user terminals may be involved. It is called a client-based solution (requiring e.g. software on the terminal). Based on the considerations above from an operator point of view several requirements have to be kept in mind which will be listed
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
