Page 538 - 5G Basics - Core Network Aspects

1 Core network aspects

Appendix I

Use case of application based on MIP
(This appendix does not form an internal part of this Recommendation.)

For the realization of application services with multiple devices, this appendix provides an additional use case
of application with one-to-multiple devices using well known mobility protocols.

I.1 Use case overview

In this case, the sender, content provider in Figure I.1, provides contents like video streaming to user having
multiple devices with the following procedures.

Figure I.1 – Example of application with one-to-multiple devices

1) The user has four devices including a PC and a smart phone at the office, and a TV and a tablet PC
at home, all of which have network connectivity.

2) User first starts to enjoy streaming service like VoD, live TV at his office using device #1 (PC).
3) When user leaves office, he changes his device to device #2 (tablet PC) and moves to home.
4) When user arrives at home, he turns on his device #3 (TV) and continues to watch streaming service.
5) User changes his device to device #4 (smart phone) when he goes out.

I.2 Deployment scenario of application with multiple devices using MIP

Also, applications can be deployed using existing mobility management protocols. Figure I.2 shows a
deployment scenario using Mobile Internet Protocol (MIP). It consists of content provider as correspondence
node, user with multiple devices, mobility binding information management module, IP-in-IP tunnelling
module as transport control function and transport function respectively.
The use of home address (HoA) and care of address (CoA) specified in MIP enable mobile devices to be
assigned IP addresses respectively and upload/update IP binding information (between user IP and active
device) with ease. The content provider (the source) in this example can be regarded as correspondent node
(CN), which is defined in MIPv4. As seen in figure, MIP home agent (HA) is able to play roles in IP binding
information management and conversion, which means, the necessary functions in recommended mobility
management framework can be completely implemented with MIP. To be more specific, two core functions
IP address binding and IP conversion are implemented by registration request/reply functions between HoA
and CoA, and by IP-in-IP tunnelling method respectively.

528