Mobility Support for Mobile Router
draft-liu-its-mobility-00

Abstract

This document proposes a ITS mobility solution. The solution is based on extensions to current IP mobility protocol.

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at http://datatracker.ietf.org/drafts/current/.

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

This Internet-Draft will expire on January 16, 2014.

Copyright Notice

Copyright (c) 2013 IETF Trust and the persons identified as the document authors. All rights reserved.

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.

Table of Contents

• 1. Introduction
• 2. Conventions and Terminologies
• 2.1. Conventions used in this document
• 2.2. Terminology
• 3. Scenario of mobile router mobility
• 4. Architecture and work flow of the mobile router mobility solution
• 5. Security Considerations
• 6. IANA Considerations
• 7. References
• 7.1. Normative References
• 7.2. Informative References
• Authors' Addresses

1. Introduction

This document specify a mobility solution for mobile router that located in a vehicle.

2. Conventions and Terminologies

2.1. Conventions used in this document

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL","SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].

2.2. Terminology

TBD

3. Scenario of mobile router mobility

This section discusses the scenario of mobile router mobility. The scenario of mobile router mobility is illustrated in figure 1. The mobile router is located in the vehicle. The mobile router works as the network access point for the mobile router users. The mobile router user include vehicle applications and other on board system. Example of such application may include vehicle security and monitoring system. The users or other vehicle may access the vehicle application from Internet or from other vehicle. The requirement for the mobile router in this architecture is that it should allow the user to access the vehicle application even when the vehicle is moving.

	    
        Vehicle
        +--------------------+                               
        |                    |                               
        | +-------------+    |                               
        | |mobile router|    |                               
        | +-------------+    |                   +-----------+    +---------+
        |       |application |-------------------|  Internet |----|   User  |
        | --------------     |                   +-----------+    +---------+
        |    |       |       |                                           
        |   |_|     |_|      |                                                   
        |  on board system   |                                               
        +--------------------+                                               
                                                                             	    

	      	

Figure 1. Mobile router architecture

4. Architecture and work flow of the mobile router mobility solution

The architecture of the mobile router mobility solution is illustrated in figure 2. The architecture is composed in three component: the mobile router, the home agent and the DNS. The vehicle application runs in the mobile router environment. The users can access to the vehicle application from Internet when the vehicle is moving. The key problem is that how to find the vehicle's identity when the vehicle is moving. The solution discussed in this document uses domain name as the vehicle's application identity.

                        

        Vehicle
        +--------------------+                               +------+
        |                    |                               | DNS  |
        |  +-------------+   |                               +------+
        |  |mobile router|   |                               +---|--+
        |  +-------------+   |                               |      |   +-----------+
        |       |application |-------------------------------|  HA  |---|  Internet |
        | ------------------ |                               |      |   +-----------+
        |    |       |       |                               +------+            |
        |   |_|     |_|      |                                                   |
        |  on board system   |                                               +------+
        +--------------------+                                               | User |
                                                                             +------+


			      	

Figure 2. Architecture of mobile router mobility solution

The flow chart of the mobile router mobility solution is as follows:

                        
             +-------------+        +----------+          +--------+         +--------+
             |Mobile Router|        |    HA    |          |  DNS   |         | Service|
             +-------------+        +----------+          +--------+         +--------+
                    |    Binding Update   |                   |                   |
                    |-------------------->|                   |                   |
                    |                     |                   |                   |
                    |             IP address allocate         |                   |
                    |                     |                   |                   |
                    |                     | Update DNS record |                   |
                    |     Binding Ack     |------------------>|                   |
                    |<--------------------|                   |                   |
                    |   Tunnel establish  |                   |                   |
                    |=====================|                   |                   |
                    |                     |                   |  DNS query        |
                    |                     |                   |<------------------|
                    |                     |                   |  DNS response     |
                    |                     |                   |------------------>|
                    |                     |  service access   |                   |
                    |<--------------------|-------------------|------------------>|
                    |                     |                   |                   |

			      	

Figure 3. Flow chart of mobile router mobility solution

1. Binding update

When the mobile router is powered on, it will send DSMIPv6 binding update to the home agent. The binding update request contains the identification of the mobile router, the home address of the mobile router, the access network allocated car-of address of the mobile router. For the mobile router's first time network attachment, the home address could be set to all zero.

2. Binding cache update and IP address allocation

The home agent receives the binding update, it will register the binding cache entry and allocate IP address for the mobile router. This IP address is the home address of the mobile router that used in the period of communication session.

3. Dome name register

The home agent send the domain name register request to the DNS system. The DNS record optional include both the home address of the mobile router and the tunnel type and port information. See [RFC2136].

4. Binding Ack

After the success register of the mobile router's domain name, the home agent send binding ack message to the mobile router to trigger the mobility tunnel establishment.

5. Mobility tunnel establishment

After the success receiving of binding ack message, the mobile router set up the mobility tunnel between the mobile router and the home agent.

6. DNS query from the user/other vehicle

The user or other vehicles send the DNS query request to the DNS system to get the IP address and port information of the mobile router. The DNS system will response to the DNS query request with the mobile router's IP address and other information(port number and tunnel type)

7. Service connection establish

The user or other vehicles application use the IP address and port information to establish the service level connection to the mobile router. e.g. TCP connection.

5. Security Considerations

TBD

6. IANA Considerations

None

7. References

7.1. Normative References

7.2. Informative References

Authors' Addresses