1 / 7

Service Flow Identifier in Proxy Mobile IPv6

This document presents enhancements to Proxy Mobile IP (PMIP6) that enable better flow identification and binding during flow mobility. By establishing PMIP tunnels based on service flow granularity between Local Mobility Anchors (LMA) and Mobility Access Gateways (MAG), multiple service flows from a mobile node (MN) can be separately managed, allowing for differentiated quality of service (QoS), charging, and traffic control. The proposal addresses the need for distinct service handling, optimizing latency and service quality according to user requirements.

ruth-richardson
Télécharger la présentation

Service Flow Identifier in Proxy Mobile IPv6

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Service Flow Identifier in Proxy Mobile IPv6 draft-hui-netext-service-flow-identifier-03

  2. Abstract • This document proposes extensions to PMIP6 that • Allows flow identification and binding during the flow mobility • Enable PMIP tunnels set up based on the service flow granularity between a pair of LMA/MAG • Therefore, multiple service flows of the MN can be separately controlled, e.g. Qos, charging, traffic control.

  3. Problem Status • What’s the requirement? • For different services, we want to have different charging rate, service quality, and latency. • E.g. User can bear some latency of the streaming TV, but require a high quality of voice service. • What’s the status? • Currently, there is single PMIP tunnel between a pair of LMA/MAG • It’s no difference in the tunnel for multiple services • Service-differ control can not be achieved based on the tunnel

  4. Protocol Operation • When a new service flow of the mobile node is started, it will trigger the service flow proxy binding update • MAG sends the PBU message to LMA including the service flow identifier option and the assigned downlink GRE Key for this SF. • LMA will generate the uplink GRE key and return a PBA message. • The new bi-directional tunnel for this specific service is set up

  5. Message Formats • Service Flow Identifier option • included in the PBU/PBA • Service Flow Identifier • A 16-bit unsigned integer, including the unique identifier within the LMA for the service flow of the mobile node. • However, its length can also be implementation dependent. • Service Flow Description option • The detailed binary encoding of the service flow description field could follow the defined binary traffic selector in draft- ietf-mext-binary-ts • Or the new traffic selector can be defined

  6. Scenario • SFID is used to identify the service flow • SFID can enable the flow binding • Refer to a SFID, there is a unique PMIP tunnle • SFID is unique in one LMA

  7. New Work Item

More Related