Docstoc

Mobility

Document Sample
Mobility Powered By Docstoc
					NSIS Mobility Issues

  Hannes Tschofenig
  Henning Schulzrinne
                Possible requirements
Local signaling only:
  If a local route change happens then the signaling message exchange
  should be kept local.

No strong-coupling:
  No strong-coupling with a macro/micro-mobility protocol
  (I.e. in-band signaling = adding QoS signaling information to a mobility
  protocol)

Flow identifier change:
   Flow identifier adaptations along the path should be possible

Double reservations:
  Double reservations should be avoided

[ Interworking with existing micro-mobility protocols and Seamoby context
    transfer]
          Flow Identifier Handling
• A flow identifier might change along the path because of the
  following reasons:
   – Changing Care-of address
   – Hierarchical mobility schemes
   – Tunneling
   – IPSec
   – NAT
   – IPv4 to IPv6 transition

• Problematic:
  Inappropriately selected flow identifier might require end-to-end
  signaling

• Bad:
  Ineffective QoS reservation (e.g. due to NAT or tunnels)
Mobility – Uplink Reservation
   oCoA
              AR(old)




                                       Crossover
          NSIS Create                                       CN
                                            Router




              AR(new)
  nCoA

                                                     Data
                  ICM N templ-example.ppt                        4
Mobility – Uplink Reservation
               NSIS Delete
   oCoA




              AR(old)

   Movement                              Crossover
                                                            CN
                                          Router




              AR(new)
   nCoA

                                                     Data
               ICM N templ-example.ppt                           5
Mobility – Uplink Reservation
          AR(old)




                                  Crossover
         NSIS Response                                       CN
                                       Router



                                       Also possible:
           AR(new)                     Query along the new paths
  nCoA                                 (cost and resource availability)

                                                      Data
             ICM N templ-example.ppt                                 6
Mobility – Downlink Reservation
                              AR(old)

            Movement
                                                            MAP           CN
                         Registration Request

                         Binding Update




                                                NSIS Signaling
                             AR(new)

       •Protocol interaction is similar to a regular route change.
       •Interactions with micro-mobility software (at MAP) can lead to performance
       improvements
Data
                 Conclusion
• Separation between session and flow identifier
  already provides a number of advantages

• Additional performance improvements can be
  obtained by interacting with mobility protocols
  (via APIs, triggers)

• Some generic limitations (e.g. flow identifier
  update) cannot be avoided.

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:4
posted:12/28/2011
language:
pages:8