Internet Engineering Task Force (IETF) M. Liebsch
Request for Comments: 7222 NEC
Category: Standards Track P. Seite
ISSN: 2070-1721 Orange
H. Yokota
KDDI Lab
J. Korhonen
Broadcom Communications
S. Gundavelli
Cisco
May 2014
Internet Engineering Task Force (IETF) M. Liebsch
Request for Comments: 7222 NEC
Category: Standards Track P. Seite
ISSN: 2070-1721 Orange
H. Yokota
KDDI Lab
J. Korhonen
Broadcom Communications
S. Gundavelli
Cisco
May 2014
Quality-of-Service Option for Proxy Mobile IPv6
代理移动IPv6的服务质量选项
Abstract
摘要
This specification defines a new mobility option, the Quality-of-Service (QoS) option, for Proxy Mobile IPv6. This option can be used by the local mobility anchor and the mobile access gateway for negotiating Quality-of-Service parameters for a mobile node's IP flows. The negotiated QoS parameters can be used for QoS policing and marking of packets to enforce QoS differentiation on the path between the local mobility anchor and the mobile access gateway. Furthermore, making QoS parameters available on the mobile access gateway enables mapping of these parameters to QoS rules that are specific to the access technology and allows those rules to be enforced on the access network using access-technology-specific approaches.
本规范为代理移动IPv6定义了一个新的移动选项，即服务质量（QoS）选项。本地移动锚和移动接入网关可以使用该选项来协商移动节点的IP流的服务质量参数。协商的QoS参数可用于QoS策略和分组标记，以在本地移动锚和移动接入网关之间的路径上实施QoS区分。此外，使QoS参数在移动接入网关上可用使得能够将这些参数映射到特定于接入技术的QoS规则，并且允许使用接入技术特定的方法在接入网络上实施这些规则。
Status of This Memo
关于下段备忘
This is an Internet Standards Track document.
这是一份互联网标准跟踪文件。
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。有关互联网标准的更多信息，请参见RFC 5741第2节。
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7222.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc7222.
Copyright Notice
版权公告
Copyright (c) 2014 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2014 IETF信托基金和确定为文件作者的人员。版权所有。
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.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
Table of Contents
目录
1. Introduction ....................................................3
2. Conventions and Terminology .....................................4
2.1. Conventions ................................................4
2.2. Terminology ................................................5
3. Overview of QoS Support in Proxy Mobile IPv6 ....................7
3.1. Quality-of-Service Option -- Usage Examples ................9
3.2. Quality-of-Service Attributes -- Usage Examples ...........11
4. Protocol Messaging Extensions ..................................12
4.1. Quality-of-Service Option .................................12
4.2. Quality-of-Service Attributes .............................14
4.2.1. Per-Mobile-Node Aggregate Maximum Downlink
Bit Rate ...........................................16
4.2.2. Per-Mobile-Node Aggregate Maximum Uplink Bit Rate ..17
4.2.3. Per-Mobility-Session Aggregate Maximum
Downlink Bit Rate ..................................18
4.2.4. Per-Mobility-Session Aggregate Maximum
Uplink Bit Rate ....................................20
4.2.5. Allocation and Retention Priority ..................22
4.2.6. Aggregate Maximum Downlink Bit Rate ................23
4.2.7. Aggregate Maximum Uplink Bit Rate ..................25
4.2.8. Guaranteed Downlink Bit Rate .......................26
4.2.9. Guaranteed Uplink Bit Rate .........................27
4.2.10. QoS Traffic Selector ..............................28
4.2.11. QoS Vendor-Specific Attribute .....................29
4.3. New Status Code for Proxy Binding Acknowledgement .........30
4.4. New Notification Reason for Update Notification Message ...30
4.5. New Status Code for Update Notification
Acknowledgement Message ...................................31
5. Protocol Considerations ........................................31
5.1. Local Mobility Anchor Considerations ......................31
5.2. Mobile Access Gateway Considerations ......................35
1. Introduction ....................................................3
2. Conventions and Terminology .....................................4
2.1. Conventions ................................................4
2.2. Terminology ................................................5
3. Overview of QoS Support in Proxy Mobile IPv6 ....................7
3.1. Quality-of-Service Option -- Usage Examples ................9
3.2. Quality-of-Service Attributes -- Usage Examples ...........11
4. Protocol Messaging Extensions ..................................12
4.1. Quality-of-Service Option .................................12
4.2. Quality-of-Service Attributes .............................14
4.2.1. Per-Mobile-Node Aggregate Maximum Downlink
Bit Rate ...........................................16
4.2.2. Per-Mobile-Node Aggregate Maximum Uplink Bit Rate ..17
4.2.3. Per-Mobility-Session Aggregate Maximum
Downlink Bit Rate ..................................18
4.2.4. Per-Mobility-Session Aggregate Maximum
Uplink Bit Rate ....................................20
4.2.5. Allocation and Retention Priority ..................22
4.2.6. Aggregate Maximum Downlink Bit Rate ................23
4.2.7. Aggregate Maximum Uplink Bit Rate ..................25
4.2.8. Guaranteed Downlink Bit Rate .......................26
4.2.9. Guaranteed Uplink Bit Rate .........................27
4.2.10. QoS Traffic Selector ..............................28
4.2.11. QoS Vendor-Specific Attribute .....................29
4.3. New Status Code for Proxy Binding Acknowledgement .........30
4.4. New Notification Reason for Update Notification Message ...30
4.5. New Status Code for Update Notification
Acknowledgement Message ...................................31
5. Protocol Considerations ........................................31
5.1. Local Mobility Anchor Considerations ......................31
5.2. Mobile Access Gateway Considerations ......................35
6. QoS Services in Integrated WLAN-3GPP Networks ..................39
6.1. Technical Scope and Procedure .............................39
6.2. Relevant QoS Attributes ...................................41
7. IANA Considerations ............................................42
8. Security Considerations ........................................44
9. Acknowledgements ...............................................44
10. References ....................................................44
10.1. Normative References .....................................44
10.2. Informative References ...................................45
Appendix A. Information When Implementing 3GPP QoS in IP
Transport Network ....................................47
A.1. Mapping Tables ............................................47
A.2. Use Cases and Protocol Operations .........................48
A.2.1. Handover of Existing QoS Rules ........................48
A.2.2. Establishment of QoS Rules ............................50
A.2.3. Dynamic Update to QoS Policy ..........................52
Appendix B. Information When Implementing PMIP-Based QoS Support
with IEEE 802.11e ....................................53
Appendix C. Information When Implementing with a Broadband
Network Gateway ......................................57
6. QoS Services in Integrated WLAN-3GPP Networks ..................39
6.1. Technical Scope and Procedure .............................39
6.2. Relevant QoS Attributes ...................................41
7. IANA Considerations ............................................42
8. Security Considerations ........................................44
9. Acknowledgements ...............................................44
10. References ....................................................44
10.1. Normative References .....................................44
10.2. Informative References ...................................45
Appendix A. Information When Implementing 3GPP QoS in IP
Transport Network ....................................47
A.1. Mapping Tables ............................................47
A.2. Use Cases and Protocol Operations .........................48
A.2.1. Handover of Existing QoS Rules ........................48
A.2.2. Establishment of QoS Rules ............................50
A.2.3. Dynamic Update to QoS Policy ..........................52
Appendix B. Information When Implementing PMIP-Based QoS Support
with IEEE 802.11e ....................................53
Appendix C. Information When Implementing with a Broadband
Network Gateway ......................................57
Mobile operators deploy Proxy Mobile IPv6 (PMIPv6) [RFC5213] to enable network-based mobility management for mobile nodes (MNs). Users can access IP-based services from their mobile device by using various radio access technologies. The currently supported mobile standards have adequate support for QoS-based service differentiation for subscriber traffic in cellular radio access networks. QoS policies are typically controlled by a policy control function, whereas the policies are enforced by one or more gateways in the infrastructure, such as the local mobility anchor (LMA) and the mobile access gateway (MAG), as well as by access network elements. Policy control and in-band QoS differentiation for access to the mobile operator network through alternative non-cellular access technologies are not supported in the currently specified standards. Although support for IP session handovers and IP flow mobility across access technologies already exists in cellular standards [TS23.402], QoS policy handovers across access technologies has not received much attention so far.
移动运营商部署代理移动IPv6（PMIPv6）[RFC5213]以实现移动节点（MN）基于网络的移动性管理。用户可以使用各种无线接入技术从移动设备访问基于IP的服务。当前支持的移动标准充分支持蜂窝无线接入网络中用户业务的基于QoS的服务区分。QoS策略通常由策略控制功能控制，而策略由基础设施中的一个或多个网关（例如本地移动锚（LMA）和移动接入网关（MAG））以及接入网络元件来实施。当前指定的标准不支持通过替代非蜂窝接入技术接入移动运营商网络的策略控制和带内QoS区分。尽管在蜂窝标准[TS23.402]中已经存在对IP会话切换和跨接入技术的IP流移动性的支持，但是跨接入技术的QoS策略切换到目前为止还没有受到太多的关注。
Based on the deployment trends, Wireless LAN (WLAN) can be considered as the dominant alternative access technology to complement cellular radio access. Since the 802.11e extension [IEEE802.11e-2005] provides QoS extensions to WLAN, it is beneficial to apply QoS policies to WLAN access, which enables QoS classification of downlink as well as uplink traffic between a mobile node and its local
基于部署趋势，无线局域网（WLAN）可被视为补充蜂窝无线接入的主要替代接入技术。由于802.11e扩展[IEEE802.11e-2005]为WLAN提供QoS扩展，因此将QoS策略应用于WLAN接入是有益的，这使得能够对移动节点及其本地节点之间的下行链路和上行链路流量进行QoS分类
mobility anchor. For realizing this capability, this specification identifies three functional operations:
机动性锚。为了实现这一功能，本规范确定了三种功能操作：
(a) Maintaining QoS classification during a handover between cellular radio access and WLAN access by means of establishing QoS policies in the handover target access network,
(a) 通过在切换目标接入网络中建立QoS策略，在蜂窝无线电接入和WLAN接入之间的切换期间维持QoS分类，
(b) mapping of QoS classes and associated policies between different access systems, and
(b) 不同接入系统之间QoS类和相关策略的映射，以及
(c) establishment of QoS policies for new data sessions/flows, which are initiated while using WLAN access.
(c) 为使用WLAN访问时启动的新数据会话/流建立QoS策略。
This document specifies an extension to the PMIPv6 protocol [RFC5213] to establish QoS policies for a mobile node's data traffic on the local mobility anchor and the mobile access gateway. QoS policies are conveyed in-band with PMIPv6 signaling using the specified QoS option and are enforced on the local mobility anchor for downlink traffic and on the mobile access gateway and its access network for the uplink traffic. The specified option allows association between IP session classification characteristics, such as a Differentiated Services Code Point (DSCP) [RFC2474], and the expected QoS class for the IP session. This document specifies fundamental QoS attributes that apply on a per-mobile-node, per-mobility-session, or per-flow basis. The specified attributes are not specific to any access technology but are compatible with the Third Generation Partnership Project (3GPP) and IEEE 802.11 Wireless LAN QoS specifications [IEEE802.11-2012].
本文件规定了PMIPv6协议[RFC5213]的扩展，以建立本地移动锚和移动接入网关上移动节点数据流量的QoS策略。QoS策略通过使用指定的QoS选项的PMIPv6信令在频带内传送，并在用于下行链路业务的本地移动锚上以及用于上行链路业务的移动接入网关及其接入网络上实施。指定的选项允许IP会话分类特征（如区分服务代码点（DSCP）[RFC2474]）与IP会话的预期QoS类别之间存在关联。本文档指定了适用于每个移动节点、每个移动会话或每个流的基本QoS属性。指定的属性不特定于任何接入技术，但与第三代合作伙伴计划（3GPP）和IEEE 802.11无线LAN QoS规范[IEEE802.11-2012]兼容。
Additional QoS attributes can be specified and used with the QoS option, e.g., to represent more specific descriptions of latency constraints or jitter bounds. The specification of such additional QoS attributes as well as the handling of QoS policies between the mobile access gateway and the access network are out of the scope of this specification.
可以指定附加的QoS属性并与QoS选项一起使用，例如，用于表示延迟约束或抖动边界的更具体描述。此类附加QoS属性的规范以及移动接入网关和接入网络之间的QoS策略的处理不在本规范的范围内。
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 RFC 2119 [RFC2119].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照RFC 2119[RFC2119]中所述进行解释。
All the mobility-related terms used in this document are to be interpreted as defined in the Proxy Mobile IPv6 specifications [RFC5213], [RFC5844], and [RFC7077]. Additionally, this document uses the following abbreviations:
本文档中使用的所有移动相关术语应按照代理移动IPv6规范[RFC5213]、[RFC5844]和[RFC7077]中的定义进行解释。此外，本文件使用以下缩写：
Aggregate Maximum Bit Rate (AMBR)
聚合最大比特率（AMBR）
AMBR defines the upper limit on the bit rate that can be provided by the network for a set of IP flows. IP packets within the flows exceeding the AMBR limit may be discarded by the rate-shaping function where the AMBR parameter is enforced. Variants of the "AMBR" term can be defined by restricting the target set of IP flows on which the AMBR is applied to a mobile node, mobility session, or flow direction. For example, Per-Mobile-Node Aggregate Maximum Downlink Bit Rate, Per-Mobile-Node Aggregate Maximum Uplink Bit Rate, Per-Mobility-Session Aggregate Maximum Downlink Bit Rate, and Per-Mobility-Session Aggregate Maximum Uplink Bit Rate are used in this document.
AMBR定义了网络可以为一组IP流提供的比特率上限。超过AMBR限制的流内的IP分组可被速率成形函数丢弃，其中AMBR参数被强制。可以通过限制将AMBR应用于移动节点、移动会话或流方向的IP流的目标集来定义“AMBR”术语的变体。例如，本文档中使用每个移动节点聚合最大下行链路比特率、每个移动节点聚合最大上行链路比特率、每个移动会话聚合最大下行链路比特率和每个移动会话聚合最大上行链路比特率。
Allocation and Retention Priority (AARP)
分配和保留优先级（AARP）
AARP is used in congestion situations when there are insufficient resources for meeting all Service Requests. It is used primarily by the Admission Control function to determine whether a particular Service Request must be rejected due to lack of resources or honored by preempting an existing low-priority service.
当没有足够的资源满足所有服务请求时，AARP用于拥塞情况。它主要由准入控制功能用于确定特定的服务请求是否必须由于资源不足而被拒绝，或者通过抢占现有的低优先级服务来满足。
Differentiated Services Code Point (DSCP)
区分服务代码点（DSCP）
In the Differentiated Services Architecture [RFC2474], packets are classified and marked to receive a particular per-hop forwarding behavior on nodes along their path based on the marking present on the packet. This marking on IPv4 and IPv6 packets that defines a specific per-hop behavior is known as DSCP. Refer to [RFC2474], [RFC2475], [RFC4594], and [RFC2983] for a complete explanation.
在区分服务体系结构[RFC2474]中，分组被分类和标记，以基于分组上存在的标记在其路径上的节点上接收特定的每跳转发行为。IPv4和IPv6数据包上定义特定每跳行为的标记称为DSCP。有关完整的说明，请参阅[RFC2474]、[RFC2475]、[RFC4594]和[RFC2983]。
Downlink (DL) Traffic
下行（DL）业务
The mobile node's IP packets that the mobile access gateway receives from the local mobility anchor are referred to as the Downlink traffic. The "Downlink" term used in the QoS attribute definition is always from the reference point of the mobile node, and it implies traffic heading towards the mobile node.
移动接入网关从本地移动锚接收的移动节点的IP分组称为下行链路业务。QoS属性定义中使用的“下行链路”术语始终来自移动节点的参考点，并且它意味着朝向移动节点的业务。
Guaranteed Bit Rate (GBR)
保证比特率（GBR）
GBR denotes the assured bit rate that will be provided by the network for a set of IP flows. It is assumed that the network reserves the resources for supporting the GBR parameter. Variants of the "GBR" term can be defined by limiting the scope of the target IP flows on which the GBR is applied to a mobile node, mobility session, or flow direction. For example, Guaranteed Downlink Bit Rate and Guaranteed Uplink Bit Rate are used in this document.
GBR表示网络将为一组IP流提供的保证比特率。假设网络保留支持GBR参数的资源。可以通过限制将GBR应用于移动节点、移动会话或流方向的目标IP流的范围来定义“GBR”术语的变体。例如，本文档中使用了保证的下行链路比特率和保证的上行链路比特率。
Mobility Session
流动会议
The term "mobility session" is defined in [RFC5213]. It refers to the creation or existence of state associated with the mobile node's mobility binding on the local mobility anchor and on the mobile access gateway.
术语“移动会话”在[RFC5213]中定义。它是指在本地移动锚和移动接入网关上创建或存在与移动节点的移动绑定相关联的状态。
QoS Service Request
QoS服务请求
A QoS Service Request is a set of QoS parameters that are defined to be enforced on one or more mobile node's IP flows. The parameters at the minimum include a DSCP marking and additionally may include Guaranteed Bit Rate or Aggregate Maximum Bit Rate. The Quality-of-Service option defined in this document represents a QoS Service Request.
QoS服务请求是定义为在一个或多个移动节点的IP流上实施的一组QoS参数。这些参数至少包括DSCP标记，另外还可以包括保证比特率或聚合最大比特率。本文档中定义的服务质量选项表示QoS服务请求。
Service Identifier
服务标识
In some mobility architectures, multiple services within the same mobility service subscription are offered to a mobile node. Each of those services provide a specific service (for example, Internet Service and Voice Over IP Service) and has an identifier called "Service Identifier". 3GPP APN (Access Point Name) is an example of a Service Identifier. Refer to [RFC5149] for the definition of the Service Identifier and the mobility option used for carrying the Service Identifier.
在一些移动架构中，向移动节点提供同一移动服务订阅中的多个服务。这些服务中的每一个都提供一个特定的服务（例如，互联网服务和IP语音服务），并具有一个称为“服务标识符”的标识符。3GPP APN（接入点名称）是服务标识符的示例。参考[RFC5149]了解服务标识符的定义以及用于携带服务标识符的移动选项。
Uplink (UL) Traffic
上行（UL）业务
The mobile node's IP packets that the mobile access gateway forwards to the local mobility anchor are referred to as the Uplink traffic. The "Uplink" term used in the QoS attribute definitions is based on the reference point of the mobile node, and it implies traffic originating from the mobile node.
移动接入网关转发给本地移动锚的移动节点的IP分组称为上行链路业务。在QoS属性定义中使用的“上行链路”术语基于移动节点的参考点，并且它意味着来自移动节点的业务。
The Quality-of-Service support in Proxy Mobile IPv6 specified in this document is based on the Differentiated Services Architecture ([RFC2474] and [RFC2475]). The access and the home network in the Proxy Mobile IPv6 domain are assumed to be DiffServ-enabled, with every network node in the forwarding path for the mobile node's IP traffic being DiffServ-compliant. The per-hop behavior for providing differential treatment based on the DiffServ marking in the packet is assumed to be supported in the Proxy Mobile IPv6 domain.
本文档中指定的代理移动IPv6中的服务质量支持基于区分服务体系结构（[RFC2474]和[RFC2475]）。假设代理移动IPv6域中的接入和家庭网络启用了区分服务，移动节点IP流量转发路径中的每个网络节点都符合区分服务。假设在代理移动IPv6域中支持基于分组中的DiffServ标记提供差分处理的每跳行为。
The local mobility anchor in the home network and the mobile access gateway in the access network define the network boundary between the access and the home network. As the tunnel entry and exit points for the mobile node's IP traffic, these entities are the logical choice for being chosen as the QoS enforcement points. The basic QoS functions such as marking, metering, policing, and rate-shaping on the mobile node's IP flows can be enforced at these nodes.
家庭网络中的本地移动性锚和接入网络中的移动接入网关定义接入和家庭网络之间的网络边界。作为移动节点IP流量的隧道入口和出口点，这些实体是被选为QoS实施点的逻辑选择。移动节点的IP流上的基本QoS功能（如标记、计量、策略和速率成形）可以在这些节点上实施。
The local mobility anchor and the mobile access gateway can negotiate the Quality-of-Service parameters for a mobile node's IP flows based on the signaling extensions defined in this document. The QoS services that can be enabled for a mobile node are for meeting both the quantitative performance requirements (such as Guaranteed Bit Rate) as well as for realizing relative performance treatment by way of class-based differentiation. The subscriber's policy and the charging profile (for example, [TS22.115]) are key considerations for the mobility entities in the QoS service negotiation. The decision on the type of QoS services that are to be enabled for a mobile node is based on the subscriber profile and based on available network resources. The negotiated QoS parameters are used for providing QoS differentiation on the path between the local mobility anchor and the mobile access gateway. The signaling related to QoS services is strictly between the mobility entities and does not result in per-flow state or signaling to any other node in the network.
本地移动性锚和移动接入网关可以基于本文档中定义的信令扩展来协商移动节点的IP流的服务质量参数。可为移动节点启用的QoS服务用于满足定量性能要求（例如保证比特率）以及通过基于类别的区分实现相对性能处理。用户的策略和计费模式（例如，[TS22.115]）是QoS服务协商中移动实体的关键考虑因素。关于要为移动节点启用的QoS服务的类型的决定基于订户配置文件和可用网络资源。协商的QoS参数用于在本地移动锚和移动接入网关之间的路径上提供QoS区分。与QoS服务相关的信令严格地在移动实体之间，并且不会导致每流状态或到网络中任何其他节点的信令。
+=======+
| MN-1 |
+=======+
| | | Flow-6
Flow-1<--(GBR: 64 Kbps) |
| Flow-4 |
Flow-2 | | |
| | Flow-1 | |
| Flow-3 | | |
|_|_| DSCP-X | | |
( )<--(Per-Session-AMBR: 1 Mbps) : | | |
| | | DSCP-Z : | | |
| | : : | | |
| | | +=====+ +==:=v+ | | |
| '- -- - - - --| | | : o|--' | |
| '- - --- - - -| | __ | v o|----' |
'- - - - - - - -| | _--' '--_ | o--|------'
| | ( ) | |
| MAG |=====( IP Network )=====| LMA |
| | ( ) | |
,- - - - - - - - -| | '--__--' | o|-- - -,
,- - -- - -- - -| | | o|--- , |
| | ,- - - - -- -| | | o|--, | |
| | +=====+ +====^+ | | |
|_|_| : | | |
( _ _ )<--(Per-Session-AMBR: 2 Mbps) : | | |
| | | DSCP-Y | | |
| | | | |
| | | | | |
| Flow-6 Flow-2 | |
| | | |
Flow-5 (MBR: 100 Kbps) Flow-3 |
| |
Flow-4 (GBR: 64 Kbps) Flow-5
| | |
+=======+
| MN-2 |
+=======+
+=======+
| MN-1 |
+=======+
| | | Flow-6
Flow-1<--(GBR: 64 Kbps) |
| Flow-4 |
Flow-2 | | |
| | Flow-1 | |
| Flow-3 | | |
|_|_| DSCP-X | | |
( )<--(Per-Session-AMBR: 1 Mbps) : | | |
| | | DSCP-Z : | | |
| | : : | | |
| | | +=====+ +==:=v+ | | |
| '- -- - - - --| | | : o|--' | |
| '- - --- - - -| | __ | v o|----' |
'- - - - - - - -| | _--' '--_ | o--|------'
| | ( ) | |
| MAG |=====( IP Network )=====| LMA |
| | ( ) | |
,- - - - - - - - -| | '--__--' | o|-- - -,
,- - -- - -- - -| | | o|--- , |
| | ,- - - - -- -| | | o|--, | |
| | +=====+ +====^+ | | |
|_|_| : | | |
( _ _ )<--(Per-Session-AMBR: 2 Mbps) : | | |
| | | DSCP-Y | | |
| | | | |
| | | | | |
| Flow-6 Flow-2 | |
| | | |
Flow-5 (MBR: 100 Kbps) Flow-3 |
| |
Flow-4 (GBR: 64 Kbps) Flow-5
| | |
+=======+
| MN-2 |
+=======+
Figure 1: QoS Support
图1:QoS支持
Figure 1 illustrates the support of QoS services in a Proxy Mobile IPv6 domain. The local mobility anchor and the mobile access gateway have negotiated QoS parameters for the mobility sessions belonging to MN-1 and MN-2. The negotiated QoS parameters include a Per-Session-AMBR of 1 Mbps and 2 Mbps for MN-1 and MN-2 respectively. Furthermore, different IP flows from MN-1 and MN-2 are given
图1说明了代理移动IPv6域中QoS服务的支持。本地移动锚和移动接入网关已经为属于MN-1和MN-2的移动会话协商了QoS参数。协商的QoS参数包括MN-1和MN-2的每会话AMBR分别为1mbps和2mbps。此外，给出了MN-1和MN-2的不同IP流
different QoS service treatment, for example, a GBR of 64 Kbps for Flow-1 and Flow-4 is assured, a DSCP marking enforcement of "Z" on Flow-6, and an MBR of 100 Kbps on Flow-5.
不同的QoS服务处理，例如，保证了Flow-1和Flow-4的GBR为64 Kbps，Flow-6上的DSCP标记强制为“Z”，Flow-5上的MBR为100 Kbps。
Use Case 1: Figure 2 illustrates a scenario where a local mobility anchor initiates a QoS Service Request to a mobile access gateway.
用例1：图2说明了本地移动锚向移动接入网关发起QoS服务请求的场景。
+-----+ +-----+ +-----+
| MN | | MAG | | LMA |
+-----+ +-----+ +-----+
| | |
1) |---- MN Attach ----| |
2) | |------ PBU ------->|
3) | |<----- PBA --------|
| | |
4) | |o=================o|
| | PMIPv6 Tunnel |
| | |
| (LMA initiates QoS Service Request) |
5) | |<----- UPN (QoS)---|
| | |
| (MAG proposes a revised QoS Request) |
6) | |------ UPA (QoS')->|
| | |
7) | |<----- UPN (QoS')--|
8) | |------ UPA (QoS')->|
| QoS Rules ---| |
9) | Established <-| | QoS Rules ---|
10) | ---| Established <-| |
| | ---|
11) |<----------------->| |
+-----+ +-----+ +-----+
| MN | | MAG | | LMA |
+-----+ +-----+ +-----+
| | |
1) |---- MN Attach ----| |
2) | |------ PBU ------->|
3) | |<----- PBA --------|
| | |
4) | |o=================o|
| | PMIPv6 Tunnel |
| | |
| (LMA initiates QoS Service Request) |
5) | |<----- UPN (QoS)---|
| | |
| (MAG proposes a revised QoS Request) |
6) | |------ UPA (QoS')->|
| | |
7) | |<----- UPN (QoS')--|
8) | |------ UPA (QoS')->|
| QoS Rules ---| |
9) | Established <-| | QoS Rules ---|
10) | ---| Established <-| |
| | ---|
11) |<----------------->| |
Figure 2: LMA-Initiated QoS Service Request
图2:LMA发起的QoS服务请求
o (1) to (4): MAG detects the mobile node's attachment to the access link and initiates the signaling with the local mobility anchor. Upon completing the signaling, the LMA and MAG establish the mobility session and the forwarding state.
o （1） to（4）：MAG检测移动节点与接入链路的连接，并使用本地移动锚发起信令。在完成信令后，LMA和MAG建立移动会话和转发状态。
o (5) to (8): The LMA initiates a QoS Service Request to the mobile access gateway. The trigger for this service can be based on a trigger from a policy function, and the specific details of that trigger are outside the scope of this document. The LMA sends an Update Notification (UPN) message [RFC7077] to the MAG. The message includes the QoS option (Section 4.1), which includes a set of QoS parameters. On determining that it cannot support the
o （5） to（8）：LMA向移动接入网关发起QoS服务请求。此服务的触发器可以基于策略功能的触发器，该触发器的具体细节不在本文档的范围内。LMA向MAG发送更新通知（UPN）消息[RFC7077]。该消息包括QoS选项（第4.1节），其中包括一组QoS参数。确定其无法支持
requested QoS Service Request for that mobile, the MAG sends an Update Notification Acknowledgement (UPA) message. The message contains a revised QoS option with an updated set of QoS attributes. The LMA accepts the revised QoS Service Request by sending a new Update Notification message including the updated QoS option.
请求该移动设备的QoS服务请求时，MAG发送更新通知确认（UPA）消息。该消息包含一个修订的QoS选项，其中包含一组更新的QoS属性。LMA通过发送包括更新的QoS选项的新更新通知消息来接受修改后的QoS服务请求。
o (9) to (11): Upon successfully negotiating a QoS Service Request, the MAG and the LMA install the QoS rules for that Service Request. Furthermore, the MAG (using access-technology-specific mechanisms) installs the QoS rules on the access network.
o （9） to（11）：在成功协商QoS服务请求后，MAG和LMA为该服务请求安装QoS规则。此外，MAG（使用特定于接入技术的机制）在接入网络上安装QoS规则。
Use Case 2: Figure 3 illustrates a scenario where a mobile access gateway initiates a QoS Service Request to a local mobility anchor.
用例2：图3展示了一个场景，其中移动接入网关向本地移动锚发起QoS服务请求。
+-----+ +-----+ +-----+
| MN | | MAG | | LMA |
+-----+ +-----+ +-----+
| | |
1) |---- MN Attach ----| |
2) | |------ PBU ------->|
3) | |<----- PBA --------|
| | |
4) | |o=================o|
| | PMIPv6 Tunnel |
| | |
| (MAG initiates QoS Service Request) |
5) | |------ PBU (QoS)-->|
6) | |<----- PBA (QoS)---|
| QoS Rules ---| |
7) | Established <-| | QoS Rules ---|
8) | ---| Established <-| |
| | ---|
9) |<----------------->| |
+-----+ +-----+ +-----+
| MN | | MAG | | LMA |
+-----+ +-----+ +-----+
| | |
1) |---- MN Attach ----| |
2) | |------ PBU ------->|
3) | |<----- PBA --------|
| | |
4) | |o=================o|
| | PMIPv6 Tunnel |
| | |
| (MAG initiates QoS Service Request) |
5) | |------ PBU (QoS)-->|
6) | |<----- PBA (QoS)---|
| QoS Rules ---| |
7) | Established <-| | QoS Rules ---|
8) | ---| Established <-| |
| | ---|
9) |<----------------->| |
Figure 3: MAG-Initiated QoS Service Request
图3:MAG发起的QoS服务请求
o (1) to (4): MAG detects the mobile node's attachment to the access link and initiates the signaling with the local mobility anchor. Upon completing the signaling, the LMA and MAG establish the mobility session and the forwarding state.
o （1） to（4）：MAG检测移动节点与接入链路的连接，并使用本地移动锚发起信令。在完成信令后，LMA和MAG建立移动会话和转发状态。
o (5) to (6): The MAG initiates a QoS Service Request to the local mobility anchor. The trigger for this service can be based on a trigger from the mobile node using access-technology-specific mechanisms. The specific details of that trigger are outside the scope of this document. The MAG sends a Proxy Binding Update (PBU) message [RFC5213] to the LMA. The message includes the QoS
o （5） to（6）：MAG向本地移动锚发起QoS服务请求。该服务的触发器可以基于来自使用接入技术特定机制的移动节点的触发器。该触发器的具体细节不在本文档的范围内。MAG向LMA发送代理绑定更新（PBU）消息[RFC5213]。该消息包括QoS
option (Section 4.1), which includes a set of QoS parameters. The LMA agrees to the proposed QoS Service Request by sending a Proxy Binding Acknowledgement (PBA) message.
选项（第4.1节），其中包括一组QoS参数。LMA通过发送代理绑定确认（PBA）消息来同意提议的QoS服务请求。
o (7) to (9): Upon successfully negotiating a QoS Service Request, the MAG and the LMA install the QoS rules for that Service Request. Furthermore, the MAG using access-technology-specific mechanisms installs the QoS rules on the access network.
o （7） to（9）：成功协商QoS服务请求后，MAG和LMA为该服务请求安装QoS规则。此外，使用接入技术特定机制的MAG在接入网络上安装QoS规则。
This section identifies the use cases where the Quality-of-Service option (Section 4.1) and its attributes (Section 4.2) defined in this document are relevant.
本节确定了与本文件中定义的服务质量选项（第4.1节）及其属性（第4.2节）相关的用例。
o The subscription policy offered to a mobile subscriber requires the service provider to enforce Aggregate Maximum Bit Rate (AMBR) limits on the subscriber's IP traffic. The local mobility anchor and the mobile access gateway negotiate the uplink and the downlink AMBR values for the mobility session and enforce them in the access and the home network. The QoS option (Section 4.1) with the QoS attributes Per-Session-Agg-Max-DL-Bit-Rate (Section 4.2.3) and Per-Session-Agg-Max-UL-Bit-Rate (Section 4.2.4) is used for this purpose.
o 提供给移动订户的订阅策略要求服务提供商对订户的IP流量实施聚合最大比特率（AMBR）限制。本地移动锚和移动接入网关协商用于移动会话的上行链路和下行链路AMBR值，并在接入和家庭网络中实施它们。QoS选项（第4.1节）具有每个会话Agg最大DL比特率（第4.2.3节）和每个会话Agg最大UL比特率（第4.2.4节）的QoS属性，用于此目的。
o In Community Wi-Fi deployments, the residential gateway participating in the Wi-Fi service is shared between the home user and the community Wi-Fi users. In order to ensure the home user's Wi-Fi service is not impacted because of the community Wi-Fi service, the service provider enables Guaranteed Bit Rate (GBR) for the home user's traffic. The QoS option (Section 4.1) with the QoS attributes Guaranteed-DL-Bit-Rate (Section 4.2.8) and Guaranteed-UL-Bit-Rate (Section 4.2.9) is used for this purpose.
o 在社区Wi-Fi部署中，家庭用户和社区Wi-Fi用户共享参与Wi-Fi服务的住宅网关。为了确保家庭用户的Wi-Fi服务不会因为社区Wi-Fi服务而受到影响，服务提供商为家庭用户的流量启用了保证比特率（GBR）。具有QoS属性保证DL比特率（第4.2.8节）和保证UL比特率（第4.2.9节）的QoS选项（第4.1节）用于此目的。
o A mobile user using the service provider's Voice over IP infrastructure establishes a VoIP call with some other user in the network. The negotiated call parameters for the VoIP call require a dedicated bandwidth of certain fixed value for the media flows associated with that VoIP session. The application function in the VoIP infrastructure notifies the local mobility anchor to enforce the GBR limits on that IP flow identified by the flow definition. The QoS option (Section 4.1) with the QoS attributes Guaranteed-DL-Bit-Rate (Section 4.2.8), Guaranteed-UL-Bit-Rate (Section 4.2.9), and QoS-Traffic-Selector (Section 4.2.10) is used for this purpose.
o 使用服务提供商的IP语音基础设施的移动用户与网络中的其他用户建立VoIP呼叫。VoIP呼叫的协商呼叫参数要求与该VoIP会话相关联的媒体流具有特定固定值的专用带宽。VoIP基础设施中的应用程序功能通知本地移动锚对由流定义标识的IP流实施GBR限制。QoS选项（第4.1节）具有QoS属性保证DL比特率（第4.2.8节）、保证UL比特率（第4.2.9节）和QoS流量选择器（第4.2.10节）用于此目的。
o An emergency service may require network resources in conditions when the network resources have been fully allocated to other users and the network may be experiencing severe congestion. In such cases, the service provider may want to revoke resources that have been allocated and reassign them to emergency services. The local mobility anchor and the mobile access gateway negotiate Allocation and Retention Priority (AARP) values for the IP sessions associated with the emergency applications. The QoS option (Section 4.1) with the QoS attribute Allocation-Retention-Priority (Section 4.2.5) is used for this purpose.
o 当网络资源已完全分配给其他用户且网络可能正经历严重拥塞时，紧急服务可能需要网络资源。在这种情况下，服务提供商可能希望撤销已分配的资源，并将其重新分配给应急服务。本地移动锚和移动接入网关协商与紧急应用程序相关联的IP会话的分配和保留优先级（AARP）值。具有QoS属性分配保留优先级（第4.2.5节）的QoS选项（第4.1节）用于此目的。
The Quality-of-Service option is a mobility header option used by local mobility anchors and mobile access gateways for negotiating QoS parameters associated with a mobility session. This option can be carried in Proxy Binding Update (PBU) [RFC5213], Proxy Binding Acknowledgement (PBA) [RFC5213], Update Notification (UPN) [RFC7077] and Update Notification Acknowledgement (UPA) [RFC7077] messages. There can be more than one instance of the Quality-of-Service option in a single message. Each instance of the Quality-of-Service option represents a specific QoS Service Request.
服务质量选项是本地移动锚和移动接入网关用于协商与移动会话相关联的QoS参数的移动报头选项。此选项可以在代理绑定更新（PBU）[RFC5213]、代理绑定确认（PBA）[RFC5213]、更新通知（UPN）[RFC7077]和更新通知确认（UPA）[RFC7077]消息中携带。一条消息中可以有多个服务质量选项实例。服务质量选项的每个实例代表一个特定的QoS服务请求。
The alignment requirement for this option is 4n.
该选项的对齐要求为4n。
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | SR-ID | TC |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| OC | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ QoS Attribute(s) ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | SR-ID | TC |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| OC | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ QoS Attribute(s) ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 4: QoS Option
图4:QoS选项
o Type: 58
o 类型：58
o Length: 8-bit unsigned integer indicating the length of the option in octets, excluding the Type and Length fields.
o 长度：8位无符号整数，以八位字节表示选项的长度，不包括类型和长度字段。
o Service Request Identifier (SR-ID): An 8-bit unsigned integer used for identifying the QoS Service Request. Its uniqueness is within the scope of a mobility session. The local mobility anchor always allocates the Service Request Identifier. When a new QoS Service
o 服务请求标识符（SR-ID）：用于标识QoS服务请求的8位无符号整数。它的独特性在移动会话的范围内。本地移动锚始终分配服务请求标识符。当一个新的QoS服务
Request is initiated by a mobile access gateway, the Service Request Identifier in the initial request message is set to a value of (0), and the local mobility anchor allocates a Service Request Identifier and includes it in the response. For any new QoS Service Requests initiated by a local mobility anchor, the Service Request Identifier is set to the allocated value.
请求由移动接入网关发起，初始请求消息中的服务请求标识符设置为值（0），并且本地移动锚分配服务请求标识符并将其包括在响应中。对于由本地移动锚发起的任何新QoS服务请求，服务请求标识符被设置为分配的值。
o Traffic Class (TC): Traffic Class consists of a 6-bit DSCP field followed by a 2-bit reserved field.
o 流量类别（TC）：流量类别由6位DSCP字段和2位保留字段组成。
Differentiated Services Code Point (DSCP)
区分服务代码点（DSCP）
A 6-bit unsigned integer indicating the code point value, as defined in [RFC2475] to be used for the mobile node's IP flows. When this DSCP marking needs to be applied only for a subset of a mobile node's IP flows, there will be a Traffic Selector attribute (Section 4.2.10) in the option, which provides the flow selectors. In the absence of any such Traffic Selector attribute, the DSCP marking applies to all the IP flows associated with the mobility session.
一个6位无符号整数，指示[RFC2475]中定义的用于移动节点IP流的代码点值。当此DSCP标记只需要应用于移动节点IP流的子集时，选项中将有一个流量选择器属性（第4.2.10节），该属性提供流量选择器。在没有任何这样的业务选择器属性的情况下，DSCP标记应用于与移动会话相关联的所有IP流。
Reserved
含蓄的
The last two bits in the Traffic Class field are currently unused. These bits MUST be initialized by the sender to (0) and MUST be ignored by the receiver.
Traffic Class字段中的最后两位当前未使用。发送方必须将这些位初始化为（0），接收方必须忽略这些位。
o Operational Code (OC): 1-octet Operational code indicates the type of QoS request.
o 操作代码（OC）：1-octet操作代码表示QoS请求的类型。
RESPONSE: (0) Response to a QoS request
响应：（0）对QoS请求的响应
ALLOCATE: (1) Request to allocate QoS resources
分配：（1）请求分配QoS资源
DE-ALLOCATE: (2) Request to de-Allocate QoS resources
解分配：（2）请求解分配QoS资源
MODIFY: (3) Request to modify QoS parameters for a previously negotiated QoS Service Request
修改：（3）为先前协商的QoS服务请求修改QoS参数的请求
QUERY: (4) Query to list the previously negotiated QoS Service Requests that are still active
查询：（4）查询以列出之前协商的仍处于活动状态的QoS服务请求
NEGOTIATE: (5) Response to a QoS Service Request with a counter QoS proposal
协商：（5）用反QoS建议响应QoS服务请求
Reserved: (6) to (255) Currently not used. Receiver MUST ignore the option received with any value in this range.
保留：（6）至（255）当前未使用。接收方必须忽略接收到的带有此范围内任何值的选项。
o Reserved: This field is unused for now. The value MUST be initialized to a value of (0) by the sender and MUST be ignored by the receiver.
o 保留：此字段目前未使用。发送方必须将该值初始化为（0）值，接收方必须忽略该值。
o QoS Attribute(s): Zero or more TLV-encoded QoS attributes. The format of the QoS attribute is defined in Section 4.2. The interpretation and usage of the QoS attribute is based on the value in the Type field.
o QoS属性：零个或多个TLV编码的QoS属性。QoS属性的格式在第4.2节中定义。QoS属性的解释和使用基于类型字段中的值。
This section identifies the format of a Quality-of-Service attribute. A QoS attribute can be included in the Quality-of-Service option defined in Section 4.1. This section identifies the QoS attributes defined by this specification.
本节确定服务质量属性的格式。QoS属性可包含在第4.1节中定义的服务质量选项中。本节确定了本规范定义的QoS属性。
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Value ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Value ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 5: Format of a Quality-of-Service Attribute
图5：服务质量属性的格式
o Type: 8-bit unsigned integer indicating the type of the QoS attribute. This specification reserves the following values.
o 类型：8位无符号整数，指示QoS属性的类型。本规范保留以下值。
(0) - Reserved This value is reserved and cannot be used
(0) -保留此值为保留值，无法使用
(1) - Per-MN-Agg-Max-DL-Bit-Rate This QoS attribute, Per-Mobile-Node Aggregate Maximum Downlink Bit Rate, is defined in Section 4.2.1.
(1) -每MN Agg最大DL比特率第4.2.1节定义了该QoS属性，即每移动节点的最大下行链路比特率。
(2) - Per-MN-Agg-Max-UL-Bit-Rate This QoS attribute, Per-Mobile-Node Aggregate Maximum Uplink Bit Rate, is defined in Section 4.2.2.
(2) -每MN Agg最大UL比特率第4.2.2节定义了该QoS属性，即每移动节点聚合最大上行链路比特率。
(3) - Per-Session-Agg-Max-DL-Bit-Rate This QoS attribute, Per-Mobility-Session Aggregate Maximum Downlink Bit Rate, is defined in Section 4.2.3.
(3) -每会话Agg最大DL比特率第4.2.3节定义了该QoS属性，即每移动会话聚合最大下行链路比特率。
(4) - Per-Session-Agg-Max-UL-Bit-Rate This QoS attribute, Per-Mobility-Session Aggregate Maximum Uplink Bit Rate, is defined in Section 4.2.4.
(4) -每会话Agg最大UL比特率第4.2.4节定义了该QoS属性，即每移动会话聚合最大上行链路比特率。
(5) - Allocation-Retention-Priority This QoS attribute, Allocation and Retention Priority, is defined in Section 4.2.5.
(5) -分配保留优先级第4.2.5节定义了此QoS属性，即分配和保留优先级。
(6) - Aggregate-Max-DL-Bit-Rate This QoS attribute, Aggregate Maximum Downlink Bit Rate, is defined in Section 4.2.6.
(6) -聚合最大DL比特率该QoS属性，聚合最大下行链路比特率，在第4.2.6节中定义。
(7) - Aggregate-Max-UL-Bit-Rate This QoS attribute, Aggregate Maximum Uplink Bit Rate, is defined in Section 4.2.7.
(7) -聚合最大UL比特率该QoS属性，聚合最大上行链路比特率，在第4.2.7节中定义。
(8) - Guaranteed-DL-Bit-Rate This QoS attribute, Guaranteed Downlink Bit Rate, is defined in Section 4.2.8.
(8) -保证的DL比特率第4.2.8节定义了该QoS属性，即保证的下行链路比特率。
(9) - Guaranteed-UL-Bit-Rate This QoS attribute, Guaranteed Uplink Bit Rate, is defined in Section 4.2.9.
(9) -保证UL比特率第4.2.9节定义了该QoS属性，即保证上行链路比特率。
(10) - QoS-Traffic-Selector This QoS attribute, QoS Traffic Selector, is defined in Section 4.2.10.
（10） -QoS流量选择器该QoS属性QoS流量选择器在第4.2.10节中定义。
(11) - QoS-Vendor-Specific-Attribute This QoS attribute, QoS Vendor-Specific Attribute, is defined in Section 4.2.11.
（11） -QoS供应商特定属性该QoS属性，即QoS供应商特定属性，在第4.2.11节中定义。
(12) to (254) - Reserved These values are reserved for future allocation.
（12） to（254）-保留这些值保留供将来分配。
(255) - Reserved This value is reserved and cannot be used.
（255）-保留此值为保留值，无法使用。
o Length: 8-bit unsigned integer indicating the number of octets needed to encode the Value, excluding the Type and Length fields.
o 长度：8位无符号整数，表示编码值所需的八位字节数，不包括类型和长度字段。
o Value: The format of this field is based on the Type value.
o 值：此字段的格式基于类型值。
This attribute, Per-MN-Agg-Max-DL-Bit-Rate, represents the maximum downlink bit rate for a mobile node. It is a variant of the "AMBR" term defined in Section 2.2. This value is an aggregate across all mobility sessions associated with that mobile node.
该属性（Per MN Agg Max DL Bit Rate）表示移动节点的最大下行链路比特率。它是第2.2节中定义的“AMBR”术语的变体。该值是与该移动节点关联的所有移动会话的聚合。
This attribute can be included in the Quality-of-Service option defined in Section 4.1, and it is an optional attribute. There can only be a single instance of this attribute present in a QoS option.
该属性可以包含在第4.1节中定义的服务质量选项中，并且是可选属性。QoS选项中只能存在此属性的单个实例。
When this attribute is present in a Proxy Binding Update sent by a mobile access gateway or in an Update Notification message sent by a local mobility anchor, it indicates the maximum aggregate downlink bit rate that is being requested for the mobile node at the peer.
当该属性存在于由移动接入网关发送的代理绑定更新或由本地移动性锚发送的更新通知消息中时，它指示在对等端为移动节点请求的最大聚合下行链路比特率。
When this attribute is present in a Proxy Binding Acknowledgement message or in an Update Notification Acknowledgement message, it indicates the maximum aggregate downlink bit rate that the peer agrees to offer.
当此属性出现在代理绑定确认消息或更新通知确认消息中时，它表示对等方同意提供的最大聚合下行链路比特率。
If multiple mobility sessions are established for a mobile node, through multiple mobile access gateways with sessions anchored either on a single local mobility anchor or spread out across multiple local mobility anchors, then it depends on the operator's policy and the specific deployment as to how the total bandwidth for the mobile node on each MAG-LMA pair is computed.
如果通过多个移动接入网关为移动节点建立了多个移动会话，其中会话锚定在单个本地移动锚上或分布在多个本地移动锚上，然后，如何计算每个MAG-LMA对上移动节点的总带宽取决于运营商的策略和具体部署。
When a QoS option includes both the Per-MN-Agg-Max-DL-Bit-Rate attribute and the QoS-Traffic-Selector attribute (Section 4.2.10), then the QoS-Traffic-Selector attribute does not apply to this attribute.
当QoS选项包括Per MN Agg Max DL比特率属性和QoS流量选择器属性（第4.2.10节）时，QoS流量选择器属性不适用于该属性。
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Per-MN-Agg-Max-DL-Bit-Rate |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Per-MN-Agg-Max-DL-Bit-Rate |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o Type: 1
o 类型：1
o Length: The length in octets of the attribute, excluding the Type and Length fields. This value is set to (6).
o 长度：属性的长度（以八位字节为单位），不包括类型和长度字段。该值设置为（6）。
o Reserved: This field is unused for now. The value MUST be initialized by the sender to 0 and MUST be ignored by the receiver.
o 保留：此字段目前未使用。发送方必须将该值初始化为0，接收方必须忽略该值。
o Per-MN-Agg-Max-DL-Bit-Rate: This is a 32-bit unsigned integer that indicates the aggregate maximum downlink bit rate that is requested/allocated for all the mobile node's IP flows. The measurement units for Per-MN-Agg-Max-DL-Bit-Rate are bits per second.
o Per MN Agg Max DL比特率：这是一个32位无符号整数，表示为所有移动节点的IP流请求/分配的聚合最大下行链路比特率。每MN Agg最大DL比特率的测量单位为每秒比特数。
This attribute, Per-MN-Agg-Max-UL-Bit-Rate, represents the maximum uplink bit rate for the mobile node. It is a variant of the "AMBR" term defined in Section 2.2. This value is an aggregate across all mobility sessions associated with that mobile node.
此属性（Per MN Agg Max UL Bit Rate）表示移动节点的最大上行链路比特率。它是第2.2节中定义的“AMBR”术语的变体。该值是与该移动节点关联的所有移动会话的聚合。
This attribute can be included in the Quality-of-Service option defined in Section 4.1, and it is an optional attribute. There can only be a single instance of this attribute present in a QoS option.
该属性可以包含在第4.1节中定义的服务质量选项中，并且是可选属性。QoS选项中只能存在此属性的单个实例。
When this attribute is present in a Proxy Binding Update sent by a mobile access gateway or in an Update Notification message sent by the local mobility anchor, it indicates the maximum aggregate uplink bit rate that is being requested for the mobile node at the peer.
当该属性出现在由移动接入网关发送的代理绑定更新或由本地移动性锚发送的更新通知消息中时，它指示在对等端为移动节点请求的最大聚合上行链路比特率。
When this attribute is present in a Proxy Binding Acknowledgement message or in an Update Notification Acknowledgement message, it indicates the maximum aggregate uplink bit rate that the peer agrees to offer for that mobile node.
当该属性出现在代理绑定确认消息或更新通知确认消息中时，它指示对等方同意为该移动节点提供的最大聚合上行链路比特率。
If multiple mobility sessions are established for a mobile node, through multiple mobile access gateways with sessions anchored either on a single local mobility anchor or spread out across multiple local mobility anchors, then it depends on the operator's policy and the specific deployment as to how the total bandwidth for the mobile node on each MAG-LMA pair is computed.
如果通过多个移动接入网关为移动节点建立了多个移动会话，其中会话锚定在单个本地移动锚上或分布在多个本地移动锚上，然后，如何计算每个MAG-LMA对上移动节点的总带宽取决于运营商的策略和具体部署。
When a QoS option includes both the Per-MN-Agg-Max-UL-Bit-Rate attribute and the QoS-Traffic-Selector attribute (Section 4.2.10), then the QoS-Traffic-Selector attribute does not apply to this attribute.
当QoS选项包括Per MN Agg Max UL比特率属性和QoS流量选择器属性（第4.2.10节）时，QoS流量选择器属性不适用于该属性。
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Per-MN-Agg-Max-UL-Bit-Rate |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Per-MN-Agg-Max-UL-Bit-Rate |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o Type: 2
o 类型：2
o Length: The length in octets of the attribute, excluding the Type and Length fields. This value is set to (6).
o 长度：属性的长度（以八位字节为单位），不包括类型和长度字段。该值设置为（6）。
o Reserved: This field is unused for now. The value MUST be initialized by the sender to 0 and MUST be ignored by the receiver.
o 保留：此字段目前未使用。发送方必须将该值初始化为0，接收方必须忽略该值。
o Per-MN-Agg-Max-UL-Bit-Rate: This is a 32-bit unsigned integer that indicates the aggregate maximum uplink bit rate that is requested/ allocated for the mobile node's IP flows. The measurement units for Per-MN-Agg-Max-UL-Bit-Rate are bits per second.
o Per MN Agg Max UL比特率：这是一个32位无符号整数，表示为移动节点的IP流请求/分配的最大上行链路比特率。每MN Agg最大UL比特率的测量单位为每秒比特数。
This attribute, Per-Session-Agg-Max-DL-Bit-Rate, represents the maximum downlink bit rate for the mobility session. It is a variant of the "AMBR" term defined in Section 2.2.
此属性（每会话Agg Max DL比特率）表示移动会话的最大下行链路比特率。它是第2.2节中定义的“AMBR”术语的变体。
This attribute can be included in the Quality-of-Service option defined in Section 4.1, and it is an optional attribute. There can only be a single instance of this attribute present in a QoS option.
该属性可以包含在第4.1节中定义的服务质量选项中，并且是可选属性。QoS选项中只能存在此属性的单个实例。
When this attribute is present in a Proxy Binding Update sent by a mobile access gateway or in an Update Notification message sent by the local mobility anchor, it indicates the maximum aggregate downlink bit rate that is being requested for that mobility session.
当该属性出现在由移动接入网关发送的代理绑定更新或由本地移动性锚发送的更新通知消息中时，它指示为该移动性会话请求的最大聚合下行链路比特率。
When this attribute is present in a Proxy Binding Acknowledgement message or in an Update Notification Acknowledgement message, it indicates the maximum aggregate downlink bit rate that the peer agrees to offer for that mobility session.
当该属性出现在代理绑定确认消息或更新通知确认消息中时，它指示对等方同意为该移动会话提供的最大聚合下行链路比特率。
When a QoS option includes both the Per-Session-Agg-Max-DL-Bit-Rate attribute and the QoS-Traffic-Selector attribute (Section 4.2.10), then the QoS-Traffic-Selector attribute does not apply to this attribute.
当QoS选项包括每会话Agg Max DL比特率属性和QoS流量选择器属性（第4.2.10节）时，QoS流量选择器属性不适用于该属性。
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length |S|E| Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Per-Session-Agg-Max-DL-Bit-Rate |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length |S|E| Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Per-Session-Agg-Max-DL-Bit-Rate |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o Type: 3
o 类型：3
o Length: The length of the attribute in octets, excluding the Type and Length fields. This value is set to (6).
o 长度：属性的长度（以八位字节为单位），不包括类型和长度字段。该值设置为（6）。
o Service (S) flag: This flag is used for extending the scope of the target flows for Per-Session-Agg-Max-DL-Bit-Rate to the mobile node's other mobility sessions sharing the same Service Identifier. 3GPP Access Point Name (APN) is an example of a Service Identifier, and that identifier is carried using the Service Selection mobility option [RFC5149].
o 服务（S）标志：该标志用于将每个会话Agg Max DL比特率的目标流范围扩展到共享相同服务标识符的移动节点的其他移动会话。3GPP接入点名称（APN）是服务标识符的示例，并且该标识符使用服务选择移动性选项[RFC5149]携带。
* When the (S) flag is set to a value of (1), then the Per-Session-Agg-Max-DL-Bit-Rate is measured as an aggregate across all the mobile node's other mobility sessions sharing the same Service Identifier associated with this mobility session.
* 当（S）标志被设置为值（1）时，则每会话Agg Max DL比特率被测量为共享与该移动会话相关联的相同服务标识符的所有移动节点的其他移动会话的聚合。
* When the (S) flag is set to a value of (0), then the target flows are limited to the current mobility session.
* 当（S）标志设置为值（0）时，目标流被限制为当前移动会话。
* The (S) flag MUST NOT be set to a value of (1) when there is no Service Identifier associated with the mobility session.
* 当没有与移动会话相关联的服务标识符时，不得将（S）标志设置为（1）值。
o Exclude (E) flag: This flag is used to request that the downlink flows for which the network is providing Guaranteed-Bit-Rate service be excluded from the target IP flows for which Per-Session-Agg-Max-DL-Bit-Rate is measured.
o 排除（E）标志：该标志用于请求将网络为其提供保证比特率服务的下行链路流从测量每会话Agg Max DL比特率的目标IP流中排除。
* When the (E) flag is set to a value of (1), then the request is to exclude the IP flows for which Guaranteed-DL-Bit-Rate (Section 4.2.8) is negotiated from the flows for which Per-Session-Agg-Max-DL-Bit-Rate is measured.
* 当（E）标志设置为（1）的值时，则请求将协商保证DL比特率（第4.2.8节）的IP流从测量每会话Agg Max DL比特率的流中排除。
* When the (E) flag is set to a value of (0), then the request is not to exclude any IP flows from the target IP flows for which Per-Session-Agg-Max-DL-Bit-Rate is measured.
* 当（E）标志设置为值（0）时，请求不从测量每会话Agg Max DL比特率的目标IP流中排除任何IP流。
* When the (S) flag and (E) flag are both set to a value of (1), then the request is to exclude all the IP flows sharing the Service Identifier associated with this mobility session from the target flows for which Per-Session-Agg-Max-DL-Bit-Rate is measured.
* 当（S）标志和（E）标志都设置为（1）值时，请求将从测量每会话Agg Max DL比特率的目标流中排除共享与该移动性会话相关联的服务标识符的所有IP流。
o Reserved: This field is unused for now. The value MUST be initialized by the sender to 0 and MUST be ignored by the receiver.
o 保留：此字段目前未使用。发送方必须将该值初始化为0，接收方必须忽略该值。
o Per-Session-Agg-Max-DL-Bit-Rate: This is a 32-bit unsigned integer that indicates the aggregate maximum downlink bit rate that is requested/allocated for all the IP flows associated with that mobility session. The measurement units for Per-Session-Agg-Max-DL-Bit-Rate are bits per second.
o 每会话Agg Max DL比特率：这是一个32位无符号整数，表示为与该移动会话相关的所有IP流请求/分配的最大下行链路比特率。每会话Agg Max DL比特率的测量单位为每秒比特数。
This attribute, Per-Session-Agg-Max-UL-Bit-Rate, represents the maximum uplink bit rate for the mobility session. It is a variant of the "AMBR" term defined in Section 2.2.
此属性（每会话Agg Max UL比特率）表示移动会话的最大上行链路比特率。它是第2.2节中定义的“AMBR”术语的变体。
This attribute can be included in the Quality-of-Service option defined in Section 4.1, and it is an optional attribute. There can only be a single instance of this attribute present in a QoS option.
该属性可以包含在第4.1节中定义的服务质量选项中，并且是可选属性。QoS选项中只能存在此属性的单个实例。
When this attribute is present in a Proxy Binding Update sent by a mobile access gateway or in an Update Notification message [RFC7077] sent by the local mobility anchor, it indicates the maximum aggregate uplink bit rate that is being requested for that mobility session.
当此属性出现在移动接入网关发送的代理绑定更新中或本地移动性锚发送的更新通知消息[RFC7077]中时，它表示为该移动性会话请求的最大聚合上行链路比特率。
When this attribute is present in a Proxy Binding Acknowledgement message or in an Update Notification Acknowledgement [RFC7077] message, it indicates the maximum aggregate uplink bit rate that the peer agrees to offer for that mobility session.
当此属性出现在代理绑定确认消息或更新通知确认[RFC7077]消息中时，它指示对等方同意为该移动会话提供的最大聚合上行链路比特率。
When a QoS option includes both the Per-Session-Agg-Max-UL-Bit-Rate attribute and the QoS-Traffic-Selector attribute (Section 4.2.10), then the QoS-Traffic-Selector attribute does not apply to this attribute.
当QoS选项包括每会话Agg Max UL比特率属性和QoS流量选择器属性（第4.2.10节）时，QoS流量选择器属性不适用于该属性。
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length |S|E| Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Per-Session-Agg-Max-UL-Bit-Rate |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length |S|E| Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Per-Session-Agg-Max-UL-Bit-Rate |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o Type: 4
o 类型：4
o Length: The length of the attribute in octets, excluding the Type and Length fields. This value is set to (6).
o 长度：属性的长度（以八位字节为单位），不包括类型和长度字段。该值设置为（6）。
o Service (S) flag: This flag is used for extending the scope of the target flows for Per-Session-Agg-Max-UL-Bit-Rate to the mobile node's other mobility sessions sharing the same Service Identifier. 3GPP Access Point Name (APN) is an example of a Service Identifier, and that identifier is carried using the Service Selection mobility option [RFC5149].
o 服务标志：该标志用于将每个会话Agg Max UL比特率的目标流范围扩展到共享相同服务标识符的移动节点的其他移动会话。3GPP接入点名称（APN）是服务标识符的示例，并且该标识符使用服务选择移动性选项[RFC5149]携带。
* When the (S) flag is set to a value of (1), then the Per-Session-Agg-Max-UL-Bit-Rate is measured as an aggregate across all the mobile node's other mobility sessions sharing the same Service Identifier associated with this mobility session.
* 当（S）标志被设置为值（1）时，则每会话Agg Max UL比特率被测量为共享与该移动会话相关联的相同服务标识符的所有移动节点的其他移动会话的聚合。
* When the (S) flag is set to a value of (0), then the target flows are limited to the current mobility session.
* 当（S）标志设置为值（0）时，目标流被限制为当前移动会话。
* The (S) flag MUST NOT be set to a value of (1) when there is no Service Identifier associated with the mobility session.
* 当没有与移动会话相关联的服务标识符时，不得将（S）标志设置为（1）值。
o Exclude (E) flag: This flag is used to request that the uplink flows for which the network is providing Guaranteed-Bit-Rate service be excluded from the target IP flows for which Per-Session-Agg-Max-UL-Bit-Rate is measured.
o 排除（E）标志：该标志用于请求将网络为其提供保证比特率服务的上行链路流从测量每会话Agg Max UL比特率的目标IP流中排除。
* When the (E) flag is set to a value of (1), then the request is to exclude the IP flows for which Guaranteed-UL-Bit-Rate (Section 4.2.9) is negotiated from the flows for which Per-Session-Agg-Max-UL-Bit-Rate is measured.
* 当（E）标志设置为（1）值时，则请求将协商保证UL比特率（第4.2.9节）的IP流从测量每会话Agg最大UL比特率的流中排除。
* When the (E) flag is set to a value of (0), then the request is not to exclude any IP flows from the target IP flows for which Per-Session-Agg-Max-UL-Bit-Rate is measured.
* 当（E）标志设置为值（0）时，请求不从测量每会话Agg Max UL比特率的目标IP流中排除任何IP流。
* When the (S) flag and (E) flag are both set to a value of (1), then the request is to exclude all the IP flows sharing the Service Identifier associated with this mobility session from the target flows for which Per-Session-Agg-Max-UL-Bit-Rate is measured.
* 当（S）标志和（E）标志都设置为（1）的值时，请求将从测量每会话Agg Max UL比特率的目标流中排除共享与该移动性会话相关联的服务标识符的所有IP流。
o Reserved: This field is unused for now. The value MUST be initialized by the sender to 0 and MUST be ignored by the receiver.
o 保留：此字段目前未使用。发送方必须将该值初始化为0，接收方必须忽略该值。
o Per-Session-Agg-Max-UL-Bit-Rate: This is a 32-bit unsigned integer that indicates the aggregate maximum uplink bit rate that is requested/allocated for all the IP flows associated with that mobility session. The measurement units for Per-Session-Agg-Max-UL-Bit-Rate are bits per second.
o 每会话Agg Max UL比特率：这是一个32位无符号整数，表示为与该移动会话相关的所有IP流请求/分配的最大上行链路比特率。每会话Agg Max UL比特率的测量单位为每秒比特数。
This attribute, Allocation-Retention-Priority, represents allocation and retention priority for the mobility session or a set of IP flows. It is defined in Section 2.2.
此属性（分配保留优先级）表示移动会话或一组IP流的分配和保留优先级。其定义见第2.2节。
This attribute can be included in the Quality-of-Service option defined in Section 4.1, and it is an optional attribute. There can only be a single instance of this attribute present in a QoS option.
该属性可以包含在第4.1节中定义的服务质量选项中，并且是可选属性。QoS选项中只能存在此属性的单个实例。
When the QoS option includes both the Allocation-Retention-Priority attribute and the QoS-Traffic-Selector attribute (Section 4.2.10), then the Allocation-Retention-Priority attribute is to be applied at a flow level. The traffic selector in the QoS-Traffic-Selector attribute identifies the target flows.
当QoS选项包括分配保留优先级属性和QoS流量选择器属性（第4.2.10节）时，分配保留优先级属性将在流级别应用。QoS流量选择器属性中的流量选择器标识目标流。
When the QoS option including the Allocation-Retention-Priority attribute does not include the QoS-Traffic-Selector attribute (Section 4.2.10), then the Allocation-Retention-Priority attribute is to be applied to all the IP flows associated with that mobility session.
当包括分配保留优先级属性的QoS选项不包括QoS流量选择器属性（第4.2.10节）时，分配保留优先级属性将应用于与该移动会话相关的所有IP流。
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Reserved | PL |PC |PV |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Reserved | PL |PC |PV |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o Type: 5
o 类型：5
o Length: The length of the attribute in octets, excluding the Type and Length fields. This value is set to (2).
o 长度：属性的长度（以八位字节为单位），不包括类型和长度字段。该值设置为（2）。
o Reserved: This field is unused for now. The value MUST be initialized by the sender to 0 and MUST be ignored by the receiver.
o 保留：此字段目前未使用。发送方必须将该值初始化为0，接收方必须忽略该值。
o Priority-Level (PL): This is a 4-bit unsigned integer value. It is used to decide whether a mobility session establishment or modification request can be accepted; this is typically used for admission control of Guaranteed Bit Rate traffic in case of resource limitations. The priority level can also be used to
o 优先级（PL）：这是一个4位无符号整数值。用于决定是否可以接受移动会话建立或修改请求；这通常用于在资源限制的情况下对保证比特率流量进行准入控制。优先级也可用于
decide which existing mobility session to preempt during resource limitations. The priority level defines the relative timeliness of a resource request.
决定在资源限制期间抢占哪个现有移动会话。优先级定义了资源请求的相对及时性。
Values 1 to 15 are defined, with value 1 as the highest level of priority.
定义值1到15，值1为最高优先级。
Values 1 to 8 should only be assigned for services that are authorized to receive prioritized treatment within an operator domain. Values 9 to 15 may be assigned to resources that are authorized by the home network and thus applicable when a mobile node is roaming.
值1到8仅应分配给授权在操作员域内接受优先处理的服务。值9到15可以被分配给由归属网络授权的资源，从而在移动节点漫游时适用。
o Preemption-Capability (PC): This is a 2-bit unsigned integer value. It defines whether a service data flow can get resources that were already assigned to another service data flow with a lower priority level. The following values are defined:
o 抢占能力（PC）：这是一个2位无符号整数值。它定义了服务数据流是否可以获取已分配给另一个优先级较低的服务数据流的资源。定义了以下值：
Enabled (0): This value indicates that the service data flow is allowed to get resources that were already assigned to another IP data flow with a lower priority level.
Enabled（0）：此值表示允许服务数据流获取已分配给另一个优先级较低的IP数据流的资源。
Disabled (1): This value indicates that the service data flow is not allowed to get resources that were already assigned to another IP data flow with a lower priority level. The values (2) and (3) are reserved.
Disabled（1）：此值表示不允许服务数据流获取已分配给另一个优先级较低的IP数据流的资源。保留值（2）和（3）。
o Preemption-Vulnerability (PV): This is a 2-bit unsigned integer value. It defines whether a service data flow can lose the resources assigned to it in order to admit a service data flow with a higher priority level. The following values are defined:
o 抢占漏洞（PV）：这是一个2位无符号整数值。它定义了服务数据流是否会丢失分配给它的资源，以便允许具有更高优先级的服务数据流。定义了以下值：
Enabled (0): This value indicates that the resources assigned to the IP data flow can be preempted and allocated to a service data flow with a higher priority level.
Enabled（0）：该值表示分配给IP数据流的资源可以被抢占并分配给具有更高优先级的服务数据流。
Disabled (1): This value indicates that the resources assigned to the IP data flow shall not be preempted and allocated to a service data flow with a higher priority level. The values (2) and (3) are reserved.
Disabled（1）：该值表示分配给IP数据流的资源不应被抢占并分配给具有更高优先级的服务数据流。保留值（2）和（3）。
This attribute, Aggregate-Max-DL-Bit-Rate, represents the maximum downlink bit rate for the mobility session. It is a variant of the "AMBR" term defined in Section 2.2.
此属性“聚合最大DL比特率”表示移动会话的最大下行链路比特率。它是第2.2节中定义的“AMBR”术语的变体。
This attribute can be included in the Quality-of-Service option defined in Section 4.1, and it is an optional attribute. There can only be a single instance of this attribute present in a QoS option.
该属性可以包含在第4.1节中定义的服务质量选项中，并且是可选属性。QoS选项中只能存在此属性的单个实例。
When this attribute is present in a Proxy Binding Update sent by a mobile access gateway or in an Update Notification message sent by the local mobility anchor, it indicates the maximum aggregate bit rate for downlink IP flows that is being requested.
当此属性出现在移动接入网关发送的代理绑定更新中或本地移动性锚发送的更新通知消息中时，它指示所请求的下行链路IP流的最大聚合比特率。
When this attribute is present in a Proxy Binding Acknowledgement message or in an Update Notification Acknowledgement message, it indicates the maximum aggregate downlink bit rate that the peer agrees to offer.
当此属性出现在代理绑定确认消息或更新通知确认消息中时，它表示对等方同意提供的最大聚合下行链路比特率。
When a QoS option includes both the Aggregate-Max-DL-Bit-Rate attribute and the QoS-Traffic-Selector attribute (Section 4.2.10), then the Aggregate-Max-DL-Bit-Rate attribute is to be enforced at a flow level, and the traffic selectors present in the QoS-Traffic-Selector attribute identify those target flows.
当QoS选项包括聚合最大DL比特率属性和QoS流量选择器属性（第4.2.10节）时，则在流级别强制执行聚合最大DL比特率属性，并且QoS流量选择器属性中的流量选择器识别这些目标流。
When the QoS option that includes the Aggregate-Max-DL-Bit-Rate attribute does not include the QoS-Traffic-Selector attribute (Section 4.2.10), then the Aggregate-Max-DL-Bit-Rate attribute is to be applied to all the IP flows associated with the mobility session.
如果包含聚合最大DL比特率属性的QoS选项不包含QoS流量选择器属性（第4.2.10节），则聚合最大DL比特率属性将应用于与移动会话相关的所有IP流。
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Aggregate-Max-DL-Bit-Rate |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Aggregate-Max-DL-Bit-Rate |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o Type: 6
o 类型：6
o Length: The length of the attribute in octets, excluding the Type and Length fields. This value is set to (6).
o 长度：属性的长度（以八位字节为单位），不包括类型和长度字段。该值设置为（6）。
o Reserved: This field is unused for now. The value MUST be initialized by the sender to 0 and MUST be ignored by the receiver.
o 保留：此字段目前未使用。发送方必须将该值初始化为0，接收方必须忽略该值。
o Aggregate-Max-DL-Bit-Rate: This is a 32-bit unsigned integer that indicates the aggregate maximum downlink bit rate that is requested/allocated for downlink IP flows. The measurement units for Aggregate-Max-DL-Bit-Rate are bits per second.
o 聚合最大DL比特率：这是一个32位无符号整数，表示为下行链路IP流请求/分配的聚合最大下行链路比特率。聚合最大DL比特率的测量单位为每秒比特数。
This attribute, Aggregate-Max-UL-Bit-Rate, represents the maximum uplink bit rate for the mobility session. It is a variant of the "AMBR" term defined in Section 2.2.
此属性“聚合最大UL比特率”表示移动会话的最大上行链路比特率。它是第2.2节中定义的“AMBR”术语的变体。
This attribute can be included in the Quality-of-Service option defined in Section 4.1, and it is an optional attribute. There can only be a single instance of this attribute present in a QoS option.
该属性可以包含在第4.1节中定义的服务质量选项中，并且是可选属性。QoS选项中只能存在此属性的单个实例。
When this attribute is present in a Proxy Binding Update sent by a mobile access gateway or in an Update Notification message sent by the local mobility anchor, it indicates the maximum aggregate uplink bit rate that is being requested.
当此属性出现在由移动接入网关发送的代理绑定更新或由本地移动锚发送的更新通知消息中时，它指示所请求的最大聚合上行链路比特率。
When this attribute is present in a Proxy Binding Acknowledgement message or in an Update Notification Acknowledgement message, it indicates the maximum aggregate uplink bit rate that the peer agrees to offer.
当此属性出现在代理绑定确认消息或更新通知确认消息中时，它表示对等方同意提供的最大聚合上行链路比特率。
When a QoS option includes both the Aggregate-Max-UL-Bit-Rate attribute and the QoS-Traffic-Selector attribute (Section 4.2.10), then the Aggregate-Max-UL-Bit-Rate attribute is to be enforced at a flow level, and the traffic selectors present in the QoS-Traffic-Selector attribute identify those target flows.
当QoS选项包括聚合最大UL比特率属性和QoS流量选择器属性（第4.2.10节）时，则在流级别强制执行聚合最大UL比特率属性，并且QoS流量选择器属性中存在的流量选择器识别这些目标流。
When the QoS option that includes the Aggregate-Max-UL-Bit-Rate attribute does not include the QoS-Traffic-Selector attribute (Section 4.2.10), then the Aggregate-Max-UL-Bit-Rate attribute is to be applied to all the IP flows associated with the mobility session.
当包含聚合最大UL比特率属性的QoS选项不包含QoS流量选择器属性（第4.2.10节）时，聚合最大UL比特率属性将应用于与移动会话相关的所有IP流。
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Aggregate-Max-UL-Bit-Rate |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Aggregate-Max-UL-Bit-Rate |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o Type: 7
o 类型：7
o Length: The length of the attribute in octets, excluding the Type and Length fields. This value is set to (6).
o 长度：属性的长度（以八位字节为单位），不包括类型和长度字段。该值设置为（6）。
o Reserved: This field is unused for now. The value MUST be initialized by the sender to 0 and MUST be ignored by the receiver.
o 保留：此字段目前未使用。发送方必须将该值初始化为0，接收方必须忽略该值。
o Aggregate-Max-UL-Bit-Rate: This is a 32-bit unsigned integer that indicates the aggregate maximum uplink bit rate that is requested/ allocated for all the IP flows associated with that mobility session. The measurement units for Aggregate-Max-UL-Bit-Rate are bits per second.
o 聚合最大UL比特率：这是一个32位无符号整数，表示为与该移动性会话相关的所有IP流请求/分配的聚合最大上行链路比特率。聚合最大UL比特率的测量单位为每秒比特数。
This attribute, Guaranteed-DL-Bit-Rate, represents the assured bit rate on the downlink path that will be provided for a set of IP flows associated with a mobility session. It is a variant of the "GBR" term defined in Section 2.2.
该属性（保证的DL比特率）表示将为与移动会话相关联的一组IP流提供的下行链路路径上的保证比特率。它是第2.2节中定义的“GBR”术语的变体。
This attribute can be included in the Quality-of-Service option defined in Section 4.1, and it is an optional attribute. There can only be a single instance of this attribute present in a QoS option.
该属性可以包含在第4.1节中定义的服务质量选项中，并且是可选属性。QoS选项中只能存在此属性的单个实例。
When this attribute is present in a Proxy Binding Update sent by a mobile access gateway or in an Update Notification message sent by the local mobility anchor, it indicates the guaranteed downlink bit rate that is being requested.
当该属性出现在由移动接入网关发送的代理绑定更新或由本地移动锚发送的更新通知消息中时，它指示所请求的保证下行链路比特率。
When this attribute is present in a Proxy Binding Acknowledgement message or in an Update Notification Acknowledgement message, it indicates the guaranteed downlink bit rate that the peer agrees to offer.
当此属性出现在代理绑定确认消息或更新通知确认消息中时，它表示对等方同意提供的保证下行链路比特率。
When a QoS option includes both the Guaranteed-DL-Bit-Rate attribute and the QoS-Traffic-Selector attribute (Section 4.2.10), then the Guaranteed-DL-Bit-Rate attribute is to be enforced at a flow level, and the traffic selectors present in the QoS-Traffic-Selector attribute identify those target flows.
当QoS选项包括保证DL比特率属性和QoS流量选择器属性（第4.2.10节）时，保证DL比特率属性将在流级别强制执行，QoS流量选择器属性中的流量选择器识别这些目标流。
When the QoS option that includes the Guaranteed-DL-Bit-Rate attribute does not include the QoS-Traffic-Selector attribute (Section 4.2.10), then the Guaranteed-DL-Bit-Rate attribute is to be applied to all the IP flows associated with the mobility session.
当包括保证DL比特率属性的QoS选项不包括QoS流量选择器属性（第4.2.10节）时，保证DL比特率属性将应用于与移动会话相关的所有IP流。
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Guaranteed-DL-Bit-Rate |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Guaranteed-DL-Bit-Rate |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o Type: 8
o 类型：8
o Length: The length of the attribute in octets, excluding the Type and Length fields. This value is set to (6).
o 长度：属性的长度（以八位字节为单位），不包括类型和长度字段。该值设置为（6）。
o Reserved: This field is unused for now. The value MUST be initialized by the sender to 0 and MUST be ignored by the receiver.
o 保留：此字段目前未使用。发送方必须将该值初始化为0，接收方必须忽略该值。
o Guaranteed-DL-Bit-Rate: This is a 32-bit unsigned integer that indicates the guaranteed bandwidth in bits per second for downlink IP flows. The measurement units for Guaranteed-DL-Bit-Rate are bits per second.
o 保证DL比特率：这是一个32位无符号整数，表示下行链路IP流的保证带宽（以比特/秒为单位）。保证DL比特率的测量单位为每秒比特数。
This attribute, Guaranteed-UL-Bit-Rate, represents the assured bit rate on the uplink path that will be provided for a set of IP flows associated with a mobility session. It is a variant of the "GBR" term defined in Section 2.2.
该属性（保证UL比特率）表示上行链路路径上的保证比特率，该上行链路路径将为与移动会话相关联的一组IP流提供。它是第2.2节中定义的“GBR”术语的变体。
This attribute can be included in the Quality-of-Service option defined in Section 4.1, and it is an optional attribute. There can only be a single instance of this attribute present in a QoS option.
该属性可以包含在第4.1节中定义的服务质量选项中，并且是可选属性。QoS选项中只能存在此属性的单个实例。
When this attribute is present in a Proxy Binding Update sent by a mobile access gateway or in an Update Notification message sent by the local mobility anchor, it indicates the guaranteed uplink bit rate that is being requested.
当该属性出现在由移动接入网关发送的代理绑定更新或由本地移动锚发送的更新通知消息中时，它指示所请求的保证上行链路比特率。
When this attribute is present in a Proxy Binding Acknowledgement message or in an Update Notification Acknowledgement message, it indicates the guaranteed uplink bit rate that the peer agrees to offer.
当此属性出现在代理绑定确认消息或更新通知确认消息中时，它表示对等方同意提供的保证上行链路比特率。
When a QoS option includes both the Guaranteed-UL-Bit-Rate attribute and the QoS-Traffic-Selector attribute (Section 4.2.10), then the Guaranteed-UL-Bit-Rate attribute is to be enforced at a flow level, and the traffic selectors present in the QoS-Traffic-Selector attribute identify those target flows.
当QoS选项包括保证的UL比特率属性和QoS流量选择器属性（第4.2.10节）时，保证的UL比特率属性将在流级别强制执行，并且QoS流量选择器属性中的流量选择器识别这些目标流。
When the QoS option that includes the Guaranteed-UL-Bit-Rate attribute does not include the QoS-Traffic-Selector attribute (Section 4.2.10), then the Guaranteed-UL-Bit-Rate attribute is to be applied to all the IP flows associated with the mobility session.
当包括保证UL比特率属性的QoS选项不包括QoS流量选择器属性（第4.2.10节）时，保证UL比特率属性将应用于与移动会话相关的所有IP流。
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Guaranteed-UL-Bit-Rate |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Guaranteed-UL-Bit-Rate |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o Type: 9
o 类型：9
o Length: The length of the attribute in octets, excluding the Type and Length fields. This value is set to (6).
o 长度：属性的长度（以八位字节为单位），不包括类型和长度字段。该值设置为（6）。
o Reserved: This field is unused for now. The value MUST be initialized by the sender to 0 and MUST be ignored by the receiver.
o 保留：此字段目前未使用。发送方必须将该值初始化为0，接收方必须忽略该值。
o Guaranteed-UL-Bit-Rate: This is a 32-bit unsigned integer that indicates the guaranteed bandwidth in bits per second for uplink IP flows. The measurement units for Guaranteed-UL-Bit-Rate are bits per second.
o 保证UL比特率：这是一个32位无符号整数，表示上行链路IP流的保证带宽（位/秒）。保证UL比特率的测量单位为每秒比特数。
This attribute, QoS-Traffic-Selector, includes the parameters used to match packets for a set of IP flows.
此属性（QoS流量选择器）包括用于匹配一组IP流的数据包的参数。
This attribute can be included in the Quality-of-Service option defined in Section 4.1, and it is an optional attribute.
该属性可以包含在第4.1节中定义的服务质量选项中，并且是可选属性。
When a QoS option that includes the QoS-Traffic-Selector also includes any one or more of the attributes Allocation-Retention-Priority (Section 4.2.5), Aggregate-Max-DL-Bit-Rate (Section 4.2.6), Aggregate-Max-UL-Bit-Rate (Section 4.2.7), Guaranteed-DL-Bit-Rate (Section 4.2.8), and Guaranteed-UL-Bit-Rate (Section 4.2.9), then those included attributes are to be enforced at a flow level, and the traffic selectors present in the QoS-Traffic-Selector attribute identify those target flows. Furthermore, the DSCP marking in the QoS option is to be applied only to a partial set of the mobile node's IP flows, and the traffic selectors present in the QoS-Traffic-Selector attribute identify those target flows.
当包括QoS流量选择器的QoS选项还包括任何一个或多个属性分配保留优先级（第4.2.5节）、聚合最大DL比特率（第4.2.6节）、聚合最大UL比特率（第4.2.7节）、保证DL比特率（第4.2.8节）和保证UL比特率（第4.2.9节）时，然后，这些包含的属性将在流级别强制执行，并且QoS流量选择器属性中存在的流量选择器将标识这些目标流。此外，QoS选项中的DSCP标记将仅应用于移动节点的IP流的部分集合，并且QoS业务选择器属性中存在的业务选择器识别那些目标流。
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Reserved | TS Format |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ Traffic Selector ... ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Reserved | TS Format |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ Traffic Selector ... ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o Type: 10
o 类型：10
o Length: The length of the attribute in octets, excluding the Type and Length fields.
o 长度：属性的长度（以八位字节为单位），不包括类型和长度字段。
o Reserved: This field is unused for now. The value MUST be initialized by the sender to 0 and MUST be ignored by the receiver.
o 保留：此字段目前未使用。发送方必须将该值初始化为0，接收方必须忽略该值。
o TS Format: An 8-bit unsigned integer indicating the Traffic Selector Format. The values are allocated from the "Traffic Selector Format" namespace for the traffic selector sub-option defined in [RFC6089]; those defined in [RFC6089] are repeated here for clarity. Value (0) is reserved and MUST NOT be used. When the value of the TS Format field is set to (1), the format that follows is the IPv4 Binary Traffic Selector specified in Section 3.1 of [RFC6088], and when the value of TS Format field is set to (2), the format that follows is the IPv6 Binary Traffic Selector specified in Section 3.2 of [RFC6088].
o TS格式：表示流量选择器格式的8位无符号整数。这些值是从[RFC6089]中定义的流量选择器子选项的“流量选择器格式”命名空间中分配的；为清楚起见，此处重复[RFC6089]中定义的内容。值（0）是保留的，不能使用。当TS格式字段的值设置为（1）时，随后的格式为[RFC6088]第3.1节中指定的IPv4二进制流量选择器，当TS格式字段的值设置为（2）时，随后的格式为[RFC6088]第3.2节中指定的IPv6二进制流量选择器。
o Traffic Selector: variable-length field for including the traffic specification identified by the TS format field.
o 流量选择器：可变长度字段，用于包含TS格式字段标识的流量规范。
This attribute is used for carrying vendor-specific QoS attributes. The interpretation and the handling of this option are specific to the vendor implementation.
此属性用于承载特定于供应商的QoS属性。此选项的解释和处理特定于供应商实施。
This attribute can be included in the Quality-of-Service option defined in Section 4.1, and it is an optional attribute. There can be multiple instances of this attribute with different sub-type values present in a single QoS option.
该属性可以包含在第4.1节中定义的服务质量选项中，并且是可选属性。此属性可以有多个实例，在单个QoS选项中存在不同的子类型值。
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Vendor ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sub-Type | ... ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Vendor ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sub-Type | ... ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o Type: 11
o 类型：11
o Length: The length of the attribute in octets, excluding the Type and Length fields.
o 长度：属性的长度（以八位字节为单位），不包括类型和长度字段。
o Reserved: This field is unused for now. The value MUST be initialized by the sender to 0 and MUST be ignored by the receiver.
o 保留：此字段目前未使用。发送方必须将该值初始化为0，接收方必须忽略该值。
o Vendor ID: The Vendor ID is the SMI (Structure of Management Information) Network Management Private Enterprise Code of the IANA-maintained "Private Enterprise Numbers" registry [SMI].
o 供应商ID：供应商ID是IANA维护的“私有企业编号”注册表[SMI]的SMI（管理信息结构）网络管理私有企业代码。
o Sub-Type: An 8-bit field indicating the type of vendor-specific information carried in the option. The namespace for this sub-type is managed by the vendor identified by the Vendor ID field.
o 子类型：一个8位字段，指示选项中包含的供应商特定信息的类型。此子类型的命名空间由供应商ID字段标识的供应商管理。
This document defines the following new status code value for use in Proxy Binding Acknowledgement message.
本文档定义了以下用于代理绑定确认消息的新状态代码值。
CANNOT_MEET_QOS_SERVICE_REQUEST (Cannot meet QoS Service Request): 179
无法满足QOS服务请求（无法满足QOS服务请求）：179
This document defines the following new Notification Reason value for use in Update Notification message.
本文档定义了以下用于更新通知消息的新通知原因值。
QOS_SERVICE_REQUEST (QoS Service Requested): 5
QOS\u服务请求（请求的QOS服务）：5
This document defines the following new status code value for use in Update Notification Acknowledgement message.
本文档定义了以下用于更新通知确认消息的新状态代码值。
CANNOT_MEET_QOS_SERVICE_REQUEST (Cannot meet QoS Service Request): 130
无法满足QOS服务请求（无法满足QOS服务请求）：130
o The conceptual Binding Cache entry data structure maintained by the local mobility anchor, described in Section 5.1 of [RFC5213], can be extended to store a list of negotiated Quality-of-Service requests to be enforced. There can be multiple such entries, and each entry must include the Service Request Identifier, DSCP value, and the attributes defined in Section 4.2.
o [RFC5213]第5.1节中描述的由本地移动锚维护的概念性绑定缓存条目数据结构可以扩展，以存储要实施的协商服务质量请求列表。可以有多个这样的条目，每个条目必须包括服务请求标识符、DSCP值和第4.2节中定义的属性。
LMA Receiving a QoS Service Request:
接收QoS服务请求的LMA：
o On receiving a Proxy Binding Update message with an instance of the Quality-of-Service option included in the message and the Operational Code field of the Quality-of-Service option set to QUERY, then the local mobility anchor includes all the Quality-of-Service option(s) reflecting the currently negotiated QoS Service Requests for that mobility session in the response message. The Operational Code field in each of the Quality-of-Service option(s), which is included in the response message, is set to RESPONSE.
o 在接收到代理绑定更新消息时，消息中包含服务质量选项的实例，并且服务质量选项的操作代码字段设置为查询，则本地移动锚包括所有服务质量选项在响应消息中反映该移动会话当前协商的QoS服务请求。响应消息中包含的每个服务质量选项中的操作代码字段设置为响应。
o On receiving a Proxy Binding Update message with one or more instances of the Quality-of-Service option included in the message and the Operational Code field set to ALLOCATE, the local mobility anchor processes the option(s) and determines if the QoS Service Request for the proposed QoS Service Request(s) can be met. Each instance of the Quality-of-Service option represents a specific QoS Service Request. This determination to accept the request(s) can be based on policy configured on the local mobility anchor, available network resources, or other considerations.
o 当接收到具有包括在消息中的服务质量选项的一个或多个实例以及设置为分配的操作代码字段的代理绑定更新消息时，本地移动锚处理该选项并确定是否能够满足针对所提议的QoS服务请求的QoS服务请求。服务质量选项的每个实例代表一个特定的QoS服务请求。接受请求的这一确定可以基于在本地移动锚上配置的策略、可用网络资源或其他考虑因素。
o If the local mobility anchor can support the proposed QoS Service Requests in entirety, then it sends a Proxy Binding Acknowledgement message with a status code value of (0).
o 如果本地移动性锚能够完全支持提议的QoS服务请求，那么它发送状态码值为（0）的代理绑定确认消息。
* The message includes all the Quality-of-Service option instances copied (including all the option content) from the received Proxy Binding Update message. The local mobility
* 该消息包括从收到的代理绑定更新消息复制的所有服务质量选项实例（包括所有选项内容）。地方流动性
anchor assigns a Service Request Identifier to each Service Request and sets the SR-ID field of each included Quality-of-Service option accordingly.
anchor为每个服务请求分配一个服务请求标识符，并相应地设置每个包含的服务质量选项的SR-ID字段。
* The Operational Code field in each of the Quality-of-Service option(s) is set to RESPONSE.
* 每个服务质量选项中的操作代码字段都设置为响应。
* The local mobility anchor should enforce the Quality-of-Service rules for all the negotiated QoS Service Requests on the mobile node's uplink and downlink traffic.
* 本地移动性锚应针对移动节点的上行链路和下行链路业务上的所有协商QoS服务请求强制执行服务质量规则。
o If the local mobility anchor cannot support any of the requested QoS Service Requests in entirety, it rejects the request and sends a Proxy Binding Acknowledgement message with the status code value set to CANNOT_MEET_QOS_SERVICE_REQUEST (Cannot meet QoS Service Request).
o 如果本地移动锚不能完全支持任何请求的QoS服务请求，它将拒绝该请求并发送一条状态码值设置为cannot_Meeting_QoS_Service_request（cannot Meeting QoS Service request）的代理绑定确认消息。
* Since the local mobility anchor cannot support the requested QoS services for that mobile node, the Proxy Binding Acknowledgement message will not include any Quality-of-Service options. This serves as an indication to the mobile access gateway that QoS services are not supported for that mobile node.
* 由于本地移动锚无法支持该移动节点的请求QoS服务，因此代理绑定确认消息将不包括任何服务质量选项。这向移动接入网关指示该移动节点不支持QoS服务。
* The denial of a QoS Service Request MUST NOT result in removal of the mobility session for that mobile node.
* 拒绝QoS服务请求不得导致删除该移动节点的移动会话。
o If the local mobility anchor can support QoS services for the mobile node, but only with lower quality values than indicated in the QoS attributes of a received QoS option or only for some of the received QoS Service Requests, the local mobility anchor includes the QoS option for the supported QoS Service Requests in the Proxy Binding Acknowledgement message with an updated set of QoS attributes.
o 如果本地移动锚可以支持移动节点的QoS服务，但是仅具有比接收到的QoS选项的QoS属性中指示的质量值更低的质量值，或者仅针对一些接收到的QoS服务请求，本地移动锚在具有更新的QoS属性集的代理绑定确认消息中包括用于支持的QoS服务请求的QoS选项。
* If the local mobility anchor cannot support some of the received QoS Service Requests for that mobile node, then the Quality-of-Service option for these QoS Service Requests is not included in the Proxy Binding Acknowledgement message. This serves as an indication to the mobile access gateway that a particular QoS Service Request is not supported for that mobile node. This includes the case where the attributes in a QoS option have conflicting requirements, for example, Per-Session-Agg-Max-UL-Bit-Rate is lower than Guaranteed-UL-Bit-Rate.
* 如果本地移动锚不能支持该移动节点的一些接收到的QoS服务请求，那么这些QoS服务请求的服务质量选项不包括在代理绑定确认消息中。这用作向移动接入网关指示该移动节点不支持特定QoS服务请求。这包括QoS选项中的属性具有冲突要求的情况，例如，每会话Agg Max UL比特率低于保证UL比特率。
* The local mobility anchor includes only QoS options in the Proxy Binding Acknowledgement message for supported QoS attributes. The contents of each option (including the QoS
* 本地移动锚在代理绑定确认消息中仅包括支持的QoS属性的QoS选项。每个选项的内容（包括QoS）
attributes) reflect the QoS service parameters that the local mobility anchor can support for that mobile node. The local mobility anchor sets the values of each supported QoS attribute according to the level of QoS it can support for the mobile node. The Service Request Identifier in each of the included QoS options is set to a value of (0). The Operational Code field in each of the included Quality-of-Service option(s) is set to NEGOTIATE. This serves as an indication for the mobile access gateway to resend the Proxy Binding Update message with the revised QoS parameters.
属性）反映本地移动锚可为该移动节点支持的QoS服务参数。本地移动性锚根据其可支持的移动节点的QoS水平设置每个支持的QoS属性的值。每个包括的QoS选项中的服务请求标识符被设置为值（0）。每个包含的服务质量选项中的操作代码字段设置为协商。这用作指示移动接入网关使用修改后的QoS参数重新发送代理绑定更新消息。
LMA Sending a QoS Service Request:
LMA发送QoS服务请求：
o The local mobility anchor, at any time, can initiate a QoS Service Request for a mobile node by sending an Update Notification message [RFC7077]. The Notification Reason in the Update Notification message is set to a value of QOS_SERVICE_REQUEST, and the Acknowledgement Requested (A) flag is set to a value of (1).
o 本地移动锚可随时通过发送更新通知消息[RFC7077]来发起移动节点的QoS服务请求。更新通知消息中的通知原因被设置为QOS_服务_请求的值，并且确认请求（a）标志被设置为（1）的值。
* New QoS Service Request:
* 新的QoS服务请求：
+ The message includes one or more instances of the Quality-of-Service option. Each instance of the option will include one or more QoS attributes.
+ 该消息包括服务质量选项的一个或多个实例。该选项的每个实例将包括一个或多个QoS属性。
+ The Operational Code field in the Quality-of-Service option is set to ALLOCATE.
+ “服务质量”选项中的“操作代码”字段设置为“分配”。
+ The Service Request Identifier is set to the allocated value.
+ 服务请求标识符设置为已分配的值。
+ The DSCP field in the Traffic Class (TC) field is set to the requested DSCP value.
+ 流量等级（TC）字段中的DSCP字段设置为请求的DSCP值。
* Modification of an existing QoS Service Request:
* 修改现有QoS服务请求：
+ The message includes one or more instances of the Quality-of-Service option with the QoS attributes reflecting the updated values in the attributes and the updated list of attributes.
+ 该消息包括服务质量选项的一个或多个实例，其中QoS属性反映属性中的更新值和更新的属性列表。
+ The Operational Code field in the Quality-of-Service option is set to MODIFY.
+ “服务质量”选项中的“操作代码”字段设置为“修改”。
+ The Service Request Identifier is set to a value that was allocated for that QoS Service Request.
+ 服务请求标识符被设置为为为该QoS服务请求分配的值。
+ The DSCP field in the Traffic Class (TC) field is set to the requested DSCP value.
+ 流量等级（TC）字段中的DSCP字段设置为请求的DSCP值。
* Deletion of an existing QoS Service Request:
* 删除现有QoS服务请求：
+ The message includes the Quality-of-Service option(s) with the relevant QoS attributes.
+ 消息包括具有相关QoS属性的服务质量选项。
+ The Operational Code field in the Quality-of-Service option is set to DE-ALLOCATE.
+ 服务质量选项中的操作代码字段设置为取消分配。
+ The Service Request Identifier is set to a value that was allocated for that QoS Service Request.
+ 服务请求标识符被设置为为为该QoS服务请求分配的值。
+ The DSCP field in the Traffic Class (TC) field is set to the DSCP value associated with that request.
+ 流量类别（TC）字段中的DSCP字段设置为与该请求关联的DSCP值。
* Query for the previously negotiated QoS Service Requests:
* 查询先前协商的QoS服务请求：
+ The message includes a single instance of the Quality-of-Service option without including any QoS attributes.
+ 该消息包括服务质量选项的单个实例，但不包括任何QoS属性。
+ The Operational Code field in the Quality-of-Service option is set to QUERY.
+ “服务质量”选项中的“操作代码”字段设置为“查询”。
+ The Service Request Identifier is set to a value of (0).
+ 服务请求标识符的值设置为（0）。
+ The DSCP field in the Traffic Class (TC) field is set to a value of (0).
+ 流量等级（TC）字段中的DSCP字段设置为值（0）。
o Handling a Response to the QoS Service Request:
o 处理对QoS服务请求的响应：
* If the received Update Notification Acknowledgement [RFC7077] message has the Status Code field set to a value (0), the local mobility anchor should enforce the Quality-of-Service rules for the negotiated QoS parameters on the mobile node's uplink and downlink traffic.
* 如果接收到的更新通知确认[RFC7077]消息的状态代码字段设置为值（0），则本地移动性锚点应针对移动节点的上行链路和下行链路业务上协商的QoS参数强制执行服务质量规则。
* If the received Update Notification Acknowledgement message has the Status Code field set to a value CANNOT_MEET_QOS_SERVICE_REQUEST, the local mobility anchor applies the following considerations:
* 如果接收到的更新通知确认消息的状态代码字段设置为值CANNOT_Meeting_QOS_SERVICE_REQUEST，则本地移动锚应用以下注意事项：
+ The denial of a QoS Service Request results in removal of any QoS state associated with that request.
+ 拒绝QoS服务请求会导致删除与该请求相关联的任何QoS状态。
+ If the message did not include any Quality-of-Service option(s), then it is an indication from the mobile access gateway that QoS services are not enabled for the mobile node.
+ 如果消息不包括任何服务质量选项，则它是来自移动接入网关的指示，表明没有为移动节点启用QoS服务。
+ If the Operational Code field in the Quality-of-Service option is set to a value of NEGOTIATE and the message includes one or more instances of the Quality-of-Service option, but the option contents reflect a downgraded/revised set of QoS parameters, then the local mobility anchor MAY choose to agree to proposed QoS Service Request by resending a new Update Notification message with the updated Quality-of-Service option(s).
+ 如果服务质量选项中的操作代码字段设置为协商值，并且消息包括服务质量选项的一个或多个实例，但选项内容反映了一组降级/修订的QoS参数，然后，本地移动锚可以通过重新发送具有更新的服务质量选项的新的更新通知消息来选择同意提议的QoS服务请求。
General Considerations:
一般考虑：
o Any time the local mobility anchor removes a mobile node's mobility session by removing a Binding Cache entry [RFC5213] for which QoS resources have been previously allocated, those allocated resources are released.
o 任何时候，本地移动锚通过移除绑定缓存项[RFC5213]来移除移动节点的移动会话，对于该绑定缓存项[RFC5213]，先前已经为其分配了QoS资源，这些分配的资源将被释放。
o Any time the local mobility anchor receives a Proxy Binding Update with HI hint = 3 (inter-MAG handover), the local mobility anchor when sending a Proxy Binding Acknowledgement message includes the QoS option(s) for each of the QoS Service Requests that are active for that mobile node. This allows the mobile access gateway to allocate QoS resources on the current path. This is relevant for the scenario where a mobile node performs a handover to a new mobile access gateway that is unaware of the previously negotiated QoS services.
o 当本地移动锚接收到HI-hint＝3的代理绑定更新（MAG间切换）时，本地移动锚在发送代理绑定确认消息时包括针对该移动节点的活动的每个QoS服务请求的QoS选项。这允许移动接入网关在当前路径上分配QoS资源。这与移动节点执行到不知道先前协商的QoS服务的新移动接入网关的切换的场景相关。
o The conceptual Binding Update List entry data structure maintained by the mobile access gateway, described in Section 6.1 of [RFC5213], can be extended to store a list of negotiated Quality-of-Service requests to be enforced. There can be multiple such entries, and each entry must include the Service Request Identifier, DSCP value and the attributes defined in Section 4.2.
o [RFC5213]第6.1节中所述的移动接入网关维护的概念绑定更新列表条目数据结构可以扩展，以存储待执行的协商服务质量请求列表。可以有多个这样的条目，每个条目必须包括服务请求标识符、DSCP值和第4.2节中定义的属性。
MAG Receiving a QoS Service Request:
接收QoS服务请求的MAG：
o On receiving an Update Notification message with one or more instances of the Quality-of-Service option included in the message, the mobile access gateway processes the option(s) and determines if the QoS Service Request for the proposed QoS Service Request(s) can be met. Each instance of the Quality-of-Service option represents a specific QoS Service Request. This
o 在接收到包含在消息中的服务质量选项的一个或多个实例的更新通知消息时，移动接入网关处理该选项并确定是否能够满足针对所提议的QoS服务请求的QoS服务请求。服务质量选项的每个实例代表一个特定的QoS服务请求。这
determination to accept the request(s) can be based on policy configured on the mobile access gateway, available network resources, or other considerations.
接受请求的确定可以基于在移动接入网关上配置的策略、可用网络资源或其他考虑因素。
o If the mobile access gateway can support the proposed QoS Service Requests in entirety, then it sends an Update Notification Acknowledgement message with a status code value of (0).
o 如果移动接入网关能够整体支持提议的QoS服务请求，则其发送状态码值为（0）的更新通知确认消息。
* The message includes all the Quality-of-Service option instances copied (including all the option content) from the received Update Notification message. However, if the Operational Code field in the request is a QUERY, then the message includes all the Quality-of-Service option(s) reflecting the currently negotiated QoS Service Requests for that mobility session.
* 该消息包括从收到的更新通知消息复制的所有服务质量选项实例（包括所有选项内容）。然而，如果请求中的操作代码字段是查询，则消息包括反映该移动会话当前协商的QoS服务请求的所有服务质量选项。
* The Operational Code field in each of the Quality-of-Service option(s) is set to RESPONSE.
* 每个服务质量选项中的操作代码字段都设置为响应。
* The mobile access gateway should enforce the Quality-of-Service rules for all the negotiated QoS Service Requests on the mobile node's uplink and downlink traffic.
* 移动接入网关应对移动节点的上行链路和下行链路业务上的所有协商QoS服务请求实施服务质量规则。
o If the mobile access gateway cannot support any of the requested QoS Service Requests in entirety, then it rejects the request and sends an Update Notification Acknowledgement message with the status code set to CANNOT_MEET_QOS_SERVICE_REQUEST (Cannot meet QoS Service Request).
o 如果移动接入网关不能完全支持任何请求的QoS服务请求，则它拒绝该请求并发送状态代码设置为“不能满足QoS服务请求”（不能满足QoS服务请求）的更新通知确认消息。
* The denial for QoS Service Request MUST NOT result in removal of the mobility session for that mobile node.
* 拒绝QoS服务请求不得导致删除该移动节点的移动会话。
* The Update Notification Acknowledgement message may include the Quality-of-Service option(s) based on the following considerations.
* 基于以下考虑，更新通知确认消息可以包括服务质量选项。
+ If the mobile access gateway cannot support QoS services for that mobile node, then the Quality-of-Service option is not included in the Update Notification Acknowledgement message. This serves as an indication to the local mobility anchor that QoS services are not supported for that mobile node.
+ 如果移动接入网关不能支持该移动节点的QoS服务，则更新通知确认消息中不包括服务质量选项。这用于向本地移动锚指示该移动节点不支持QoS服务。
+ If the mobile access gateway can support QoS services for the mobile node, but only with lower quality values than indicated in the QoS attributes of a received QoS option, the mobile access gateway includes the QoS option in the Update Notification Acknowledgement message with an updated set of QoS attributes. The mobile access gateway sets the
+ 如果移动接入网关可以支持用于移动节点的QoS服务，但是仅具有比在接收到的QoS选项的QoS属性中指示的质量值更低的质量值，则移动接入网关在具有更新的QoS属性集的更新通知确认消息中包括QoS选项。移动接入网关设置
values of each QoS attribute according to the level of QoS it can support for the mobile node. The mobile access gateway includes only QoS options in the Update Notification Acknowledgement message for supported QoS attributes. If the mobile access gateway receives one or multiple QoS options, whose QoS attributes are not supported, it omits these QoS options in the Update Notification Acknowledgement message. This includes the case where the attributes in a QoS option have conflicting requirements, for example, Per-Session-Agg-Max-UL-Bit-Rate is lower than Guaranteed-UL-Bit-Rate. The contents of each option (including the QoS attributes) reflect the QoS service parameters that the mobile access gateway can support for that mobile node. The Operational Code field in each of the Quality-of-Service option(s) is set to NEGOTIATE. This serves as an indication to the local mobility anchor to resend the Update Notification message with the revised QoS parameters.
每个QoS属性的值取决于它可以为移动节点支持的QoS级别。移动接入网关在更新通知确认消息中仅包括支持的QoS属性的QoS选项。如果移动接入网关接收到一个或多个QoS选项（其QoS属性不受支持），则在更新通知确认消息中忽略这些QoS选项。这包括QoS选项中的属性具有冲突要求的情况，例如，每会话Agg Max UL比特率低于保证UL比特率。每个选项的内容（包括QoS属性）反映了移动接入网关可为该移动节点支持的QoS服务参数。每个服务质量选项中的操作代码字段都设置为协商。这用作指示本地移动锚重新发送具有修改的QoS参数的更新通知消息。
MAG Sending a QoS Service Request:
MAG发送QoS服务请求：
o The mobile access gateway, at any time, can initiate a QoS Service Request for a mobile node by sending a Proxy Binding Update message. The QoS Service Request can be initiated as part of the initial Binding registration or during Binding re-registrations.
o 移动接入网关可随时通过发送代理绑定更新消息来发起移动节点的QoS服务请求。QoS服务请求可以作为初始绑定注册的一部分或在绑定重新注册期间启动。
* New QoS Service Request:
* 新的QoS服务请求：
+ The message includes one or more instances of the Quality-of-Service option. Each instance of the option will include one or more QoS attributes.
+ 该消息包括服务质量选项的一个或多个实例。该选项的每个实例将包括一个或多个QoS属性。
+ The Operational Code field in each of the Quality-of-Service option is set to ALLOCATE.
+ 每个“服务质量”选项中的“操作代码”字段都设置为“分配”。
+ The Service Request Identifier is set to a value of (0).
+ 服务请求标识符的值设置为（0）。
+ The DSCP value in the Traffic Class field reflects the requested DSCP value.
+ “流量类别”字段中的DSCP值反映了请求的DSCP值。
* Modification of an existing QoS Service Request:
* 修改现有QoS服务请求：
+ The message includes one or more instances of the Quality-of-Service option with the QoS attributes reflecting the updated values in the attributes and the updated list of attributes.
+ 该消息包括服务质量选项的一个或多个实例，其中QoS属性反映属性中的更新值和更新的属性列表。
+ The Operational Code field in the Quality-of-Service option is set to MODIFY.
+ “服务质量”选项中的“操作代码”字段设置为“修改”。
+ The Service Request Identifier is set to a value that was allocated for that QoS Service Request.
+ 服务请求标识符被设置为为为该QoS服务请求分配的值。
+ The DSCP field in the Traffic Class (TC) field is set to the requested DSCP value.
+ 流量等级（TC）字段中的DSCP字段设置为请求的DSCP值。
* Deletion of an existing QoS Service Request:
* 删除现有QoS服务请求：
+ The message includes the Quality-of-Service option(s) with the relevant QoS attributes.
+ 消息包括具有相关QoS属性的服务质量选项。
+ The Operational Code field in the Quality-of-Service option is set to DE-ALLOCATE.
+ 服务质量选项中的操作代码字段设置为取消分配。
+ The Service Request Identifier is set to a value that was allocated for that QoS Service Request.
+ 服务请求标识符被设置为为为该QoS服务请求分配的值。
+ The DSCP field in the Traffic Class (TC) field is set to the DSCP value associated with that request.
+ 流量类别（TC）字段中的DSCP字段设置为与该请求关联的DSCP值。
* Query for the previously negotiated QoS Service Requests:
* 查询先前协商的QoS服务请求：
+ The message includes a single instance of the Quality-of-Service option without including any QoS attributes.
+ 该消息包括服务质量选项的单个实例，但不包括任何QoS属性。
+ The Operational Code field in the Quality-of-Service option is set to QUERY.
+ “服务质量”选项中的“操作代码”字段设置为“查询”。
+ The Service Request Identifier is set to a value of (0).
+ 服务请求标识符的值设置为（0）。
+ The DSCP field in the Traffic Class (TC) field is set to a value of (0).
+ 流量等级（TC）字段中的DSCP字段设置为值（0）。
o Handling a Response to the QoS Service Request:
o 处理对QoS服务请求的响应：
* If the received Proxy Binding Acknowledgement message has the Status Code field set to a value of (0), the mobile access gateway should enforce the Quality-of-Service rules for the negotiated QoS parameters on the mobile node's uplink and downlink traffic.
* 如果接收到的代理绑定确认消息的状态码字段设置为值（0），则移动接入网关应针对移动节点的上行链路和下行链路业务上的协商QoS参数强制执行服务质量规则。
* If the received Proxy Binding Acknowledgement message has the Status Code field set to a value of CANNOT_MEET_QOS_SERVICE_REQUEST, the mobile access gateway applies the following considerations.
* 如果接收到的代理绑定确认消息的状态代码字段设置为“无法满足QOS服务请求”，则移动接入网关将应用以下注意事项。
+ The denial of a QoS Service Request results in removal of any QoS state associated with that request.
+ 拒绝QoS服务请求会导致删除与该请求相关联的任何QoS状态。
+ If the message did not include any Quality-of-Service option(s), then it is an indication from the local mobility anchor that QoS services are not enabled for the mobile node.
+ 如果消息不包括任何服务质量选项，则它是来自本地移动锚的指示，表明没有为移动节点启用QoS服务。
+ If the Operational Code field in the Quality-of-Service option is set to a value of NEGOTIATE and the message includes one or more instances of the Quality-of-Service option, but the option contents reflect a downgraded/revised set of QoS parameters, then the mobile access gateway MAY choose to agree to proposed QoS Service Request by resending a new Proxy Binding Update message with the updated Quality-of-Service option.
+ 如果服务质量选项中的操作代码字段设置为协商值，并且消息包括服务质量选项的一个或多个实例，但选项内容反映了一组降级/修订的QoS参数，然后，移动接入网关可以通过使用更新的服务质量选项重新发送新的代理绑定更新消息来选择同意提议的QoS服务请求。
* General Considerations:
* 一般考虑：
+ There can be more than one QoS Service Request in a single message. If so, the message includes an instance of a Quality-of-Service option for each of those Service Requests. Furthermore, the DSCP value is different in each of those requests.
+ 一条消息中可以有多个QoS服务请求。如果是，则该消息包括每个服务请求的服务质量选项的实例。此外，每个请求中的DSCP值都不同。
+ Any time the mobile access gateway removes a mobile node's mobility session by removing a Binding Update List entry [RFC5213] for which QoS resources have been previously allocated, those allocated resources are released.
+ 任何时候，移动接入网关通过移除绑定更新列表条目[RFC5213]来移除移动节点的移动会话，之前已经为其分配了QoS资源，这些分配的资源将被释放。
The QoS option specified in this document can provide the equivalent level of QoS information defined in 3GPP, which is used to enforce QoS policies for IP flows that have been established while the mobile node is attached to WLAN access or moved from 3GPP to WLAN access. The QoS classification defined by the 3GPP specification [TS23.207] [TS29.212] is provided by Differentiated Services techniques in the IP transport network. The QoS classification used in the IP transport network is further translated to WLAN QoS-specific techniques in the WLAN access using appropriate WLAN QoS specifications [IEEE802.11aa-2012] [WMM1.2.0]. The details are described in Appendix A and Appendix B.
本文档中指定的QoS选项可以提供3GPP中定义的同等级别的QoS信息，用于对移动节点连接到WLAN接入或从3GPP移动到WLAN接入时建立的IP流实施QoS策略。3GPP规范[TS23.207][TS29.212]定义的QoS分类由IP传输网络中的区分服务技术提供。IP传输网络中使用的QoS分类使用适当的WLAN QoS规范[IEEE802.11aa-2012][WMM1.2.0]进一步转化为WLAN接入中的WLAN QoS特定技术。详情见附录A和附录B。
Figure 6 illustrates a generalized architecture where the QoS option can be used. The QoS policies could be retrieved from a Policy Control Function (PCF), such as defined in current cellular mobile communication standards, which aims to assign an appropriate QoS
图6展示了一个可以使用QoS选项的通用体系结构。QoS策略可以从策略控制功能（PCF）检索，如当前蜂窝移动通信标准中定义的，其目的是分配适当的QoS
class to a mobile node's individual flows. Alternatively, more static and default QoS rules could be made locally available, e.g., on a local mobility anchor, through administration.
类设置为移动节点的各个流。或者，可以通过管理在本地（例如在本地移动锚上）提供更多静态和默认QoS规则。
Non-cellular access | Cellular Core Network Cellular
(e.g., WLAN) | (e.g., EPC) Access
| (e.g.,
| +-----------+ EUTRAN)
| | PCF |
| |(e.g.,PCRF)|
+----+ | +-----+-----+
|WiFi| (I) | |
| AP |---+ +---+---+ | | ((O))
+----+ | |WiFi AR| | PMIPv6 +-----+ +---+ |
+----+ (MAG) +=|============| LMA |=====|MAG+--|
| | WLC | | tunnel +-----+ +---+ |
+----+ | +-------+ | //
|WiFi|---+ | //
| AP | | //
+----+ (II) | //
+-------+ | //
+----+ +------+ |WiFi AR| | //
|WiFi+----+ WLC +------+ (MAG) |=|=======//
| AP | | | | | |
+----+ +------+ +------ + |
^ ^ |
| | |
+------------+
QoS inter-working
Non-cellular access | Cellular Core Network Cellular
(e.g., WLAN) | (e.g., EPC) Access
| (e.g.,
| +-----------+ EUTRAN)
| | PCF |
| |(e.g.,PCRF)|
+----+ | +-----+-----+
|WiFi| (I) | |
| AP |---+ +---+---+ | | ((O))
+----+ | |WiFi AR| | PMIPv6 +-----+ +---+ |
+----+ (MAG) +=|============| LMA |=====|MAG+--|
| | WLC | | tunnel +-----+ +---+ |
+----+ | +-------+ | //
|WiFi|---+ | //
| AP | | //
+----+ (II) | //
+-------+ | //
+----+ +------+ |WiFi AR| | //
|WiFi+----+ WLC +------+ (MAG) |=|=======//
| AP | | | | | |
+----+ +------+ +------ + |
^ ^ |
| | |
+------------+
QoS inter-working
Figure 6: Architecture for QoS Inter-Working between Cellular Access and Non-Cellular Access
图6：蜂窝接入和非蜂窝接入之间QoS互通的体系结构
During a mobile node's handover from cellular access to non-cellular access, e.g., a wireless LAN (WLAN) radio access network, the mobile node's QoS policy rules, as previously established on the local mobility anchor for the mobile node's communication through the cellular access network, are moved to the handover target mobile access gateway serving the non-cellular access network. Such a non-cellular mobile access gateway can have an access-technology-specific controller or function co-located, e.g., a Wireless LAN Controller (WLC), as depicted in option (I) of Figure 6. Alternatively, the access-specific architecture can be distributed, and the access-technology-specific control function is located external to the mobile access gateway, as depicted in option (II). In this case, the mobile access gateway and the access-technology-specific control
在移动节点从蜂窝接入切换到非蜂窝接入（例如，无线LAN（WLAN）无线接入网络）期间，移动节点的QoS策略规则，如先前在本地移动锚上为移动节点通过蜂窝接入网络的通信建立的，移动到服务于非蜂窝接入网络的切换目标移动接入网关。如图6的选项（I）所示，这样的非蜂窝移动接入网关可以具有共同定位的接入技术特定控制器或功能，例如无线LAN控制器（WLC）。或者，接入特定架构可以是分布式的，并且接入技术特定控制功能位于移动接入网关的外部，如选项（II）中所述。在这种情况下，移动接入网关和接入技术是特定的控制
function (e.g., the WLC) must provide some protocol for QoS inter-working. Details of such inter-working are out of the scope of this specification.
功能（如WLC）必须为QoS互通提供一些协议。此类互操作的详细信息不在本规范的范围内。
The QoS Option shall at least contain a DSCP value being associated with IP flows of a mobility session. The DSCP value should correspond to the 3GPP QoS Class Index (QCI), which identifies the type of service in terms of QoS characteristics (e.g., conversational voice, streaming video, signaling, and best effort); more details on DSCP and QCI mapping are given in Appendix A. Optional QoS information could also be added. For instance, in order to comply with the bearer model defined in 3GPP [TS23.203], the following QoS parameters are conveyed for each PMIPv6 mobility session:
QoS选项应至少包含与移动会话的IP流相关联的DSCP值。DSCP值应对应于3GPP QoS等级索引（QCI），其根据QoS特征（例如，对话语音、流视频、信令和尽力而为）识别服务类型；有关DSCP和QCI映射的更多详细信息，请参见附录A。还可以添加可选的QoS信息。例如，为了符合3GPP[TS23.203]中定义的承载模型，为每个PMIPv6移动性会话传送以下QoS参数：
o Default, non-GBR bearer (QCI=5-9)
o 默认，非GBR承载（QCI=5-9）
* DSCP=(BE, AF11, AF21, AF31, AF32)
* DSCP=（BE、AF11、AF21、AF31、AF32）
* Per-MN AMBR-UL/DL
* 每MN AMBR-UL/DL
* Per-Session AMBR-UL/DL {S=1,E=1}
* 每个会话AMBR-UL/DL{S=1，E=1}
* AARP
* 美国退休人员协会
APN (Access Point Name) is provided via the Service Selection ID defined in [RFC5149]. If APN is not interpreted by Wi-Fi AP, the latter will police only based on Per-MN AMBR-UL/DL (without Per-Session AMBR-UL/DL) on the Wi-Fi link.
APN（接入点名称）通过[RFC5149]中定义的服务选择ID提供。如果Wi-Fi AP不解释APN，则后者将仅根据Wi-Fi链路上的每MN AMBR-UL/DL（不包括每会话AMBR-UL/DL）进行报警。
o Dedicated, GBR bearer (QCI=1-4)
o 专用GBR承载（QCI=1-4）
* DSCP=(EF, AF41)
* DSCP=（EF，AF41）
* GBR-UL/DL
* GBR-UL/DL
* MBR-UL/DL
* MBR-UL/DL
* AARP
* 美国退休人员协会
* TS
* TS
Wi-Fi AP will perform the policy enforcement with the minimum bit rate=GBR and the maximum bit rate=MBR.
Wi-Fi AP将以最小比特率=GBR和最大比特率=MBR执行策略实施。
o Dedicated, non-GBR bearer (QCI=5-9)
o 专用非GBR承载（QCI=5-9）
* DSCP=(BE, AF11, AF21, AF31, AF32)
* DSCP=（BE、AF11、AF21、AF31、AF32）
* Per-MN AMBR-UL/DL
* 每MN AMBR-UL/DL
* Per-Session AMBR-UL/DL {S=1,E=1}
* 每个会话AMBR-UL/DL{S=1，E=1}
* AARP
* 美国退休人员协会
* TS
* TS
If APN is not interpreted by Wi-Fi AP, it will police based only on Per-MN AMBR-UL/DL (without Per-Session AMBR-UL/DL) on the Wi-Fi link.
如果Wi-Fi AP不解释APN，它将仅根据Wi-Fi链路上的每MN AMBR-UL/DL（无每会话AMBR-UL/DL）进行报警。
If DSCP values follow the 3GPP specification and deployment, the code point can carry intrinsically additional attributes according to Figure 7 in Appendix A.
如果DSCP值遵循3GPP规范和部署，则根据附录A中的图7，代码点可以携带本质上附加的属性。
For some optional QoS attributes, the signaling can differentiate enforcement per mobility session and per IP flow. For the latter, as long as the AMBR constraints are met, the rule associated with the identified flow(s) overrules the aggregated rules that apply per mobile node or per mobility session. Additional attributes can be appended to the QoS option, but their definition and specification is out of scope of this document and are left as considerations for actual deployment.
对于一些可选的QoS属性，信令可以区分每个移动会话和每个IP流的实施。对于后者，只要满足AMBR约束，与所识别的流相关联的规则就会否决适用于每个移动节点或每个移动会话的聚合规则。附加属性可以附加到QoS选项中，但它们的定义和规范不在本文档的范围内，仅作为实际部署的考虑事项。
IANA has completed the following actions:
IANA已完成以下操作：
o Action-1: This specification defines a new mobility option, the Quality-of-Service (QoS) option. The format of this option is described in Section 4.1. The type value 58 for this mobility option has been allocated from the "Mobility Options" registry at <http://www.iana.org/assignments/mobility-parameters>.
o 措施1：该规范定义了一个新的移动性选项，即服务质量（QoS）选项。第4.1节描述了该选项的格式。此移动选项的类型值58已从位于的“移动选项”注册表中分配<http://www.iana.org/assignments/mobility-parameters>.
o Action-2: This specification defines a new mobility attribute format, the Quality-of-Service attribute. The format of this attribute is described in Section 4.2. This attribute can be carried in the Quality-of-Service mobility option. The type values for this attribute are managed by IANA in a new registry, the "Quality-of-Service Attribute Registry". This registry is maintained under the "Mobile IPv6 parameters" registry at <http://www.iana.org/assignments/mobility-parameters>. This specification reserves the type values listed below. All other
o 措施2：该规范定义了一种新的移动性属性格式，即服务质量属性。第4.2节描述了该属性的格式。此属性可以在服务质量移动选项中携带。此属性的类型值由IANA在新注册表“服务质量属性注册表”中管理。此注册表位于“移动IPv6参数”注册表下<http://www.iana.org/assignments/mobility-parameters>. 本规范保留下列类型值。所有其他
values (12 - 254) are unassigned and may be assigned by IANA using the Specification Required policy [RFC5226]. The Designated Expert reviewing the value assignment is expected to verify that the protocol extension follows the Proxy Mobile IPv6 architecture and does not raise backward-compatibility issues with existing deployments.
值（12-254）未分配，IANA可使用规范要求的策略[RFC5226]分配。评估值分配的指定专家将验证协议扩展是否遵循代理移动IPv6体系结构，并且不会引起与现有部署的向后兼容性问题。
+=====+=================================+=================+
|Value| Description | Reference |
+=====+=================================+=================+
| 0 | Reserved | RFC 7222 |
+=====+===================================================+
| 1 | Per-MN-Agg-Max-DL-Bit-Rate | RFC 7222 |
+=====+===================================================+
| 2 | Per-MN-Agg-Max-UL-Bit-Rate | RFC 7222 |
+=====+===================================================+
| 3 | Per-Session-Agg-Max-DL-Bit-Rate | RFC 7222 |
+=====+===================================================+
| 4 | Per-Session-Agg-Max-UL-Bit-Rate | RFC 7222 |
+=====+===================================================+
| 5 | Allocation-Retention-Priority | RFC 7222 |
+=====+===================================================+
| 6 | Aggregate-Max-DL-Bit-Rate | RFC 7222 |
+=====+===================================================+
| 7 | Aggregate-Max-UL-Bit-Rate | RFC 7222 |
+=====+===================================================+
| 8 | Guaranteed-DL-Bit-Rate | RFC 7222 |
+=====+===================================================+
| 9 | Guaranteed-UL-Bit-Rate | RFC 7222 |
+=====+===================================================+
| 10 | QoS-Traffic-Selector | RFC 7222 |
+=====+===================================================+
| 11 | QoS-Vendor-Specific-Attribute | RFC 7222 |
+=====+===================================================+
| 255 | Reserved | RFC 7222 |
+=====+===================================================+
+=====+=================================+=================+
|Value| Description | Reference |
+=====+=================================+=================+
| 0 | Reserved | RFC 7222 |
+=====+===================================================+
| 1 | Per-MN-Agg-Max-DL-Bit-Rate | RFC 7222 |
+=====+===================================================+
| 2 | Per-MN-Agg-Max-UL-Bit-Rate | RFC 7222 |
+=====+===================================================+
| 3 | Per-Session-Agg-Max-DL-Bit-Rate | RFC 7222 |
+=====+===================================================+
| 4 | Per-Session-Agg-Max-UL-Bit-Rate | RFC 7222 |
+=====+===================================================+
| 5 | Allocation-Retention-Priority | RFC 7222 |
+=====+===================================================+
| 6 | Aggregate-Max-DL-Bit-Rate | RFC 7222 |
+=====+===================================================+
| 7 | Aggregate-Max-UL-Bit-Rate | RFC 7222 |
+=====+===================================================+
| 8 | Guaranteed-DL-Bit-Rate | RFC 7222 |
+=====+===================================================+
| 9 | Guaranteed-UL-Bit-Rate | RFC 7222 |
+=====+===================================================+
| 10 | QoS-Traffic-Selector | RFC 7222 |
+=====+===================================================+
| 11 | QoS-Vendor-Specific-Attribute | RFC 7222 |
+=====+===================================================+
| 255 | Reserved | RFC 7222 |
+=====+===================================================+
o Action-3: This document defines a new status code, CANNOT_MEET_QOS_SERVICE_REQUEST (179), for use in Proxy Binding Acknowledgement messages, as described in Section 4.3. This value has been assigned from the "Status Codes" registry at <http://www.iana.org/assignments/mobility-parameters>.
o 措施3：如第4.3节所述，本文件定义了一个新的状态代码，不能满足QOS服务请求（179），用于代理绑定确认消息。此值已从位于的“状态代码”注册表中分配<http://www.iana.org/assignments/mobility-parameters>.
o Action-4: This document defines a new Notification Reason, QOS_SERVICE_REQUEST (5), for use in Update Notification messages [RFC7077] as described in Section 4.4. This value has been assigned from the "Update Notification Reasons Registry" at <http://www.iana.org/assignments/mobility-parameters>.
o 措施4：本文件定义了一个新的通知原因QOS_服务_请求（5），用于第4.4节所述的更新通知消息[RFC7077]。此值已从位于的“更新通知原因注册表”中分配<http://www.iana.org/assignments/mobility-parameters>.
o Action-5: This document defines a new status code, CANNOT_MEET_QOS_SERVICE_REQUEST (130), for use in Update Notification Acknowledgement messages [RFC7077] as described in Section 4.5. This value has been assigned from the "Update Notification Acknowledgement Status Registry" at <http://www.iana.org/assignments/mobility-parameters>.
o 措施5：本文件定义了一个新的状态代码，不能满足QOS服务请求（130），用于第4.5节所述的更新通知确认消息[RFC7077]。此值已从位于的“更新通知确认状态注册表”分配<http://www.iana.org/assignments/mobility-parameters>.
The Quality-of-Service option defined in this specification is for use in Proxy Binding Update, Proxy Binding Acknowledgement, Update Notification, and Update Notification Acknowledgement messages. This option is carried in these messages like any other mobility header option. [RFC5213] and [RFC7077] identify the security considerations for these signaling messages. When included in these signaling messages, the Quality-of-Service option does not require additional security considerations.
本规范中定义的服务质量选项用于代理绑定更新、代理绑定确认、更新通知和更新通知确认消息。该选项与任何其他移动报头选项一样在这些消息中携带。[RFC5213]和[RFC7077]确定了这些信令消息的安全注意事项。当包含在这些信令消息中时，服务质量选项不需要额外的安全考虑。
The authors of this document thank the members of NetExt working group for the valuable feedback to different versions of this specification. In particular, the authors want to thank Basavaraj Patil, Behcet Sarikaya, Charles Perkins, Dirk von Hugo, Mark Grayson, Tricci So, Ahmad Muhanna, Pete McCann, Byju Pularikkal, John Kaippallimalil, Rajesh Pazhyannur, Carlos J. Bernardos Cano, Michal Hoeft, Ryuji Wakikawa, Liu Dapeng, Seil Jeon, and Georgios Karagiannis.
本文件的作者感谢NetExt工作组的成员对本规范不同版本的宝贵反馈。特别是，作者要感谢巴萨瓦拉吉·帕蒂尔、贝塞特·萨里卡亚、查尔斯·珀金斯、德克·冯·雨果、马克·格雷森、特里奇·索、艾哈迈德·穆哈纳、皮特·麦肯、比朱·普拉里卡勒、约翰·凯帕利马利尔、拉杰什·帕兹扬努尔、卡洛斯·J·贝尔纳多斯·卡诺、迈克尔·霍夫特、柳大鹏、赛尔·全和乔治·卡拉吉安尼斯。
The authors would like to thank all the IESG reviewers, especially, Ben Campbell, Barry Leiba, Jari Arkko, Alissa Cooper, Stephen Farrell, Ted Lemon, and Alia Atlas for their valuable comments and suggestions to improve this specification.
作者要感谢IESG的所有评审员，特别是Ben Campbell、Barry Leiba、Jari Arkko、Alissa Cooper、Stephen Farrell、Ted Lemon和Alia Atlas，感谢他们对改进本规范提出的宝贵意见和建议。
Finally, the authors would like to express sincere and profound appreciation to our Internet Area Director, Brian Haberman, for his guidance and great support in allowing us to complete this work.
最后，作者谨向我们的互联网领域总监Brian Haberman表示诚挚和深切的感谢，感谢他对我们完成这项工作的指导和大力支持。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC5213] Gundavelli, S., Leung, K., Devarapalli, V., Chowdhury, K., and B. Patil, "Proxy Mobile IPv6", RFC 5213, August 2008.
[RFC5213]Gundavelli，S.，Leung，K.，Devarapalli，V.，Chowdhury，K.，和B.Patil，“代理移动IPv6”，RFC 5213，2008年8月。
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 5226, May 2008.
[RFC5226]Narten，T.和H.Alvestrand，“在RFCs中编写IANA注意事项部分的指南”，BCP 26，RFC 5226，2008年5月。
[RFC5844] Wakikawa, R. and S. Gundavelli, "IPv4 Support for Proxy Mobile IPv6", RFC 5844, May 2010.
[RFC5844]Wakikawa，R.和S.Gundavelli，“代理移动IPv6的IPv4支持”，RFC 5844，2010年5月。
[RFC6088] Tsirtsis, G., Giarreta, G., Soliman, H., and N. Montavont, "Traffic Selectors for Flow Bindings", RFC 6088, January 2011.
[RFC6088]Tsirtsis，G.，Giarreta，G.，Soliman，H.，和N.Montavont，“流绑定的流量选择器”，RFC 6088，2011年1月。
[RFC7077] Krishnan, S., Gundavelli, S., Liebsch, M., Yokota, H., and J. Korhonen, "Update Notifications for Proxy Mobile IPv6", RFC 7077, November 2013.
[RFC7077]Krishnan，S.，Gundavelli，S.，Liebsch，M.，Yokota，H.，和J.Korhonen，“代理移动IPv6的更新通知”，RFC 7077，2013年11月。
[GSMA.IR.34] GSMA, "Guidelines for IPX Provider networks (Previously Inter-Service Provider IP Backbone Guidelines)", Official Document PRD IR.34, May 2013.
[GSMA.IR.34]GSMA，“IPX提供商网络指南（之前为服务提供商IP主干网指南）”，官方文件PRD IR.34，2013年5月。
[IEEE802.11-2012] IEEE, "Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications", 2012.
[IEEE802.11-2012]IEEE，“第11部分：无线局域网介质访问控制（MAC）和物理层（PHY）规范”，2012年。
[IEEE802.11aa-2012] IEEE, "Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications, Amendment 2: MAC Enhancements for Robust Audio Video Streaming", 2012.
[IEEE802.11aa-2012]IEEE，“第11部分：无线局域网媒体访问控制（MAC）和物理层（PHY）规范，修改件2：用于强健音频视频流的MAC增强”，2012年。
[IEEE802.11e-2005] IEEE, "Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications, Amendment 8: Medium Access Control (MAC) Quality of Service (QoS) Enhancements", 2005.
[IEEE802.11e-2005]IEEE，“第11部分：无线局域网介质访问控制（MAC）和物理层（PHY）规范，修改件8：介质访问控制（MAC）服务质量（QoS）增强”，2005年。
[RFC2474] Nichols, K., Blake, S., Baker, F., and D. Black, "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers", RFC 2474, December 1998.
[RFC2474]Nichols，K.，Blake，S.，Baker，F.，和D.Black，“IPv4和IPv6头中区分服务字段（DS字段）的定义”，RFC 2474，1998年12月。
[RFC2475] Blake, S., Black, D., Carlson, M., Davies, E., Wang, Z., and W. Weiss, "An Architecture for Differentiated Services", RFC 2475, December 1998.
[RFC2475]Blake，S.，Black，D.，Carlson，M.，Davies，E.，Wang，Z.，和W.Weiss，“差异化服务架构”，RFC 24751998年12月。
[RFC2983] Black, D., "Differentiated Services and Tunnels", RFC 2983, October 2000.
[RFC2983]Black，D.，“差异化服务和隧道”，RFC 29832000年10月。
[RFC4594] Babiarz, J., Chan, K., and F. Baker, "Configuration Guidelines for DiffServ Service Classes", RFC 4594, August 2006.
[RFC4594]Babiarz，J.，Chan，K.，和F.Baker，“区分服务服务类的配置指南”，RFC 45942006年8月。
[RFC5149] Korhonen, J., Nilsson, U., and V. Devarapalli, "Service Selection for Mobile IPv6", RFC 5149, February 2008.
[RFC5149]Korhonen，J.，Nilsson，U.，和V.Devarapalli，“移动IPv6的服务选择”，RFC 5149，2008年2月。
[RFC6089] Tsirtsis, G., Soliman, H., Montavont, N., Giaretta, G., and K. Kuladinithi, "Flow Bindings in Mobile IPv6 and Network Mobility (NEMO) Basic Support", RFC 6089, January 2011.
[RFC6089]Tsirtsis，G.，Soliman，H.，Montavont，N.，Giaretta，G.，和K.Kuladinhi，“移动IPv6和网络移动（NEMO）基本支持中的流绑定”，RFC 60892011年1月。
[SMI] IANA, "PRIVATE ENTERPRISE NUMBERS", SMI Network Management Private Enterprise Codes, April 2014, <http://www.iana.org/assignments/enterprise-numbers>.
[SMI]IANA，“私营企业编号”，SMI网络管理私营企业代码，2014年4月<http://www.iana.org/assignments/enterprise-numbers>.
[TS22.115] 3GPP, "Technical Specification Group Services and System Aspects; Service aspects; Charging and billing", 3GPP TS 22.115, 2010.
[TS22.115]3GPP，“技术规范组服务和系统方面；服务方面；收费和计费”，3GPP TS 22.115，2010年。
[TS23.203] 3GPP, "Technical Specification Group Services and System Aspects; Policy and charging control architecture", 3GPP TS 23.203, 2013.
[TS23.203]3GPP，“技术规范组服务和系统方面；策略和计费控制体系结构”，3GPP TS 23.203，2013年。
[TS23.207] 3GPP, "End-to-End Quality of Service (QoS) Concept and Architecture, Release 10", 3GPP TS 23.207, 2011.
[TS23.207]3GPP，“端到端服务质量（QoS）概念和体系结构，第10版”，3GPP TS 23.207，2011年。
[TS23.402] 3GPP, "Technical Specification Group Services and System Aspects; Architecture enhancements for non-3GPP accesses", 3GPP TS 23.402, 2012.
[TS23.402]3GPP，“技术规范组服务和系统方面；非3GPP接入的架构增强”，3GPP TS 23.402，2012年。
[TS29.212] 3GPP, "Policy and Charging Control over Gx/Sd Reference Point, Release 11", 3GPP TS 29.212, 2011.
[TS29.212]3GPP，“Gx/Sd参考点的政策和收费控制，第11版”，3GPP TS 29.212，2011年。
[WMM1.2.0] Wi-Fi Alliance, "Wi-Fi Multimedia Technical Specification (with WMM-Power Save and WMM-Admission Control)", Version 1.2.0.
[WMM1.2.0]Wi-Fi联盟，“Wi-Fi多媒体技术规范（具有WMM节能和WMM准入控制）”，版本1.2.0。
Appendix A. Information When Implementing 3GPP QoS in IP Transport Network
附录A.在IP传输网络中实施3GPP QoS时的信息
Mapping between 3GPP QCI values and DSCP is defined in [GSMA.IR.34] as follows.
[GSMA.IR.34]中定义了3GPP QCI值和DSCP之间的映射，如下所示。
+=====+================+===========================+======+
| QCI | Traffic Class | DiffServ Per-Hop-Behavior | DSCP |
+=====+================+===========================+======+
| 1 | Conversational | EF |101110|
+=====+===================================================+
| 2 | Conversational | EF |101110|
+=====+===================================================+
| 3 | Conversational | EF |101110|
+=====+===================================================+
| 4 | Streaming | AF41 |100010|
+=====+===================================================+
| 5 | Interactive | AF31 |011010|
+=====+===================================================+
| 6 | Interactive | AF32 |011100|
+=====+===================================================+
| 7 | Interactive | AF21 |010010|
+=====+===================================================+
| 8 | Interactive | AF11 |001010|
+=====+===================================================+
| 9 | Background | BE |000000|
+=====+===================================================+
+=====+================+===========================+======+
| QCI | Traffic Class | DiffServ Per-Hop-Behavior | DSCP |
+=====+================+===========================+======+
| 1 | Conversational | EF |101110|
+=====+===================================================+
| 2 | Conversational | EF |101110|
+=====+===================================================+
| 3 | Conversational | EF |101110|
+=====+===================================================+
| 4 | Streaming | AF41 |100010|
+=====+===================================================+
| 5 | Interactive | AF31 |011010|
+=====+===================================================+
| 6 | Interactive | AF32 |011100|
+=====+===================================================+
| 7 | Interactive | AF21 |010010|
+=====+===================================================+
| 8 | Interactive | AF11 |001010|
+=====+===================================================+
| 9 | Background | BE |000000|
+=====+===================================================+
Figure 7: QCI/DSCP Mapping Table
图7:QCI/DSCP映射表
Mapping between QoS attributes defined in this document and 3GPP QoS parameters is as follows.
本文档中定义的QoS属性与3GPP QoS参数之间的映射如下。
+=======+===============================+=============+
|Section| PMIPv6 QoS | 3GPP QoS |
| | Attribute | Parameter |
+=======+===============================+=============+
| 4.2.1 | Per-MN-Agg-Max-DL-Bit-Rate | UE AMBR-DL |
+-------+-------------------------------+-------------+
| 4.2.2 | Per-MN-Agg-Max-UL-Bit-Rate | UE AMBR-UL |
+-------+-------------------------------+-------------+
| 4.2.3 |Per-Session-Agg-Max-DL-Bit-Rate| APN AMBR-DL |
| | Flags: (S=1, E=1) | |
+-------+-------------------------------+-------------+
| 4.2.4 |Per-Session-Agg-Max-UL-Bit-Rate| APN AMBR-UL |
| | Flags: (S=1, E=1) | |
+-------+-------------------------------+-------------+
| 4.2.5 | Allocation-Retention-Priority | ARP |
+-------+-------------------------------+-------------+
| 4.2.6 | Aggregate-Max-DL-Bit-Rate | MBR-DL |
+-------+-------------------------------+-------------+
| 4.2.7 | Aggregate-Max-UL-Bit-Rate | MBR-UL |
+-------+-------------------------------+-------------+
| 4.2.8 | Guaranteed-DL-Bit-Rate | GBR-DL |
+-------+-------------------------------+-------------+
| 4.2.9 | Guaranteed-UL-Bit-Rate | GBR-UL |
+-------+-------------------------------+-------------+
| 4.2.10| QoS-Traffic-Selector | TFT |
+-------+-------------------------------+-------------+
+=======+===============================+=============+
|Section| PMIPv6 QoS | 3GPP QoS |
| | Attribute | Parameter |
+=======+===============================+=============+
| 4.2.1 | Per-MN-Agg-Max-DL-Bit-Rate | UE AMBR-DL |
+-------+-------------------------------+-------------+
| 4.2.2 | Per-MN-Agg-Max-UL-Bit-Rate | UE AMBR-UL |
+-------+-------------------------------+-------------+
| 4.2.3 |Per-Session-Agg-Max-DL-Bit-Rate| APN AMBR-DL |
| | Flags: (S=1, E=1) | |
+-------+-------------------------------+-------------+
| 4.2.4 |Per-Session-Agg-Max-UL-Bit-Rate| APN AMBR-UL |
| | Flags: (S=1, E=1) | |
+-------+-------------------------------+-------------+
| 4.2.5 | Allocation-Retention-Priority | ARP |
+-------+-------------------------------+-------------+
| 4.2.6 | Aggregate-Max-DL-Bit-Rate | MBR-DL |
+-------+-------------------------------+-------------+
| 4.2.7 | Aggregate-Max-UL-Bit-Rate | MBR-UL |
+-------+-------------------------------+-------------+
| 4.2.8 | Guaranteed-DL-Bit-Rate | GBR-DL |
+-------+-------------------------------+-------------+
| 4.2.9 | Guaranteed-UL-Bit-Rate | GBR-UL |
+-------+-------------------------------+-------------+
| 4.2.10| QoS-Traffic-Selector | TFT |
+-------+-------------------------------+-------------+
Figure 8: QoS Attributes and 3GPP QoS Parameters Mapping Table
图8:QoS属性和3GPP QoS参数映射表
The following subsections provide example message flow charts for scenarios where the QoS option extensions will apply as described in Section 6.1 to the protocol operation for QoS rules establishment (Appendices A.2.1 and A.2.2) and to modification (Appendix A.2.3).
以下小节提供了QoS选项扩展将按照第6.1节所述应用于QoS规则建立协议操作（附录A.2.1和A.2.2）和修改（附录A.2.3）的场景的示例消息流程图。
In Figure 9, the MN is first connected to the LTE network with a multimedia session, such as a video call, with appropriate QoS parameters set by the Policy Control Function. Then, the MN discovers a Wi-Fi AP (e.g., at home or in a cafe) and switches to it, provided that Wi-Fi access has a higher priority when available. Not only is the session continued, but the QoS is also maintained after moving to the Wi-Fi access. In order for that to happen, the LMA delivers the QoS parameters according to the bearer type on the 3GPP access to the MAG via the PMIPv6 signaling with the QoS option
在图9中，MN首先通过多媒体会话（例如视频呼叫）连接到LTE网络，并通过策略控制功能设置适当的QoS参数。然后，MN发现一个Wi-Fi AP（例如，在家中或咖啡馆中），并切换到该AP，前提是Wi-Fi接入在可用时具有更高的优先级。不仅会话将继续，而且在移动到Wi-Fi接入后，QoS也将保持不变。为了实现这一点，LMA根据3GPP接入到MAG上的承载类型，通过具有QoS选项的PMIPv6信令来交付QoS参数
(OC=ALLOCATE, SR-ID, QoS attributes, etc.). The equivalent QoS treatment is provided by the Wi-Fi AP toward the MN on the Wi-Fi link.
（OC=分配、SR-ID、QoS属性等）。Wi-Fi AP通过Wi-Fi链路向MN提供等效的QoS处理。
+--------+
|Policy |
|Control |
|Function|
+---+----+
|
+----+ +-------+ +---+----+
+--+ |LTE |_______| SGW | | PGW |
|MN|~~|eNB | | |==============| (LMA) |
+--+ +----+ +-------+ //+--------+
: //
: //
V +----+ +-------+ PMIPv6 //
+--+ |WiFi|_______| WLC |=========
|MN|~~| AP | | (MAG) | tunnel
+--+ +----+ +-------+
+--------+
|Policy |
|Control |
|Function|
+---+----+
|
+----+ +-------+ +---+----+
+--+ |LTE |_______| SGW | | PGW |
|MN|~~|eNB | | |==============| (LMA) |
+--+ +----+ +-------+ //+--------+
: //
: //
V +----+ +-------+ PMIPv6 //
+--+ |WiFi|_______| WLC |=========
|MN|~~| AP | | (MAG) | tunnel
+--+ +----+ +-------+
Figure 9: Handover Scenario (from LTE to WLAN)
图9：切换场景（从LTE到WLAN）
Figure 10 shows an example of how the QoS rules can be conveyed and enforced between the LMA and MN in the case of a handover from 3GPP access to WLAN access.
图10显示了在从3GPP接入切换到WLAN接入的情况下，如何在LMA和MN之间传送和实施QoS规则的示例。
+--+ +--+ +---+ +---+
|MN| |AP| |MAG| |LMA|
+--+ +--+ +---+ +---+
|| | | To |data
|+--detach | | cellular<-==data[DSCP]==-|<----
+----attach-----+ | access [QoS rules]
| |-INFO[MNattach]->| |
| | |-------PBU[handover]------>|
| | | |
| | |<--PBA[QoS option(OC=1 )]--|
| |<-INFO[QoSrules]-| |
| | | |
| Apply Establish Update
| mapped MN's uplink MN's downlink
| QoS rules DSCP rules DSCP rules
| | +===========================+
| | | |
| |(B) |(A) |data
|<--data[QC]----|<---data[DSCP]---|<-======data[DSCP]========-|<----
| | | |
| | | |data
|---data[QC]--->|-->data[DSCP]--->|-=======data[DSCP]=======->|--->
| |(C) |(D) |
| | | |
+--+ +--+ +---+ +---+
|MN| |AP| |MAG| |LMA|
+--+ +--+ +---+ +---+
|| | | To |data
|+--detach | | cellular<-==data[DSCP]==-|<----
+----attach-----+ | access [QoS rules]
| |-INFO[MNattach]->| |
| | |-------PBU[handover]------>|
| | | |
| | |<--PBA[QoS option(OC=1 )]--|
| |<-INFO[QoSrules]-| |
| | | |
| Apply Establish Update
| mapped MN's uplink MN's downlink
| QoS rules DSCP rules DSCP rules
| | +===========================+
| | | |
| |(B) |(A) |data
|<--data[QC]----|<---data[DSCP]---|<-======data[DSCP]========-|<----
| | | |
| | | |data
|---data[QC]--->|-->data[DSCP]--->|-=======data[DSCP]=======->|--->
| |(C) |(D) |
| | | |
(A): Apply DSCP at link to AP (B): Enforce mapped QoS rules to access technology (C): Map MN-indicated QoS Class (QC) to DSCP on the AP-MAG link, or validate MN-indicated QC and apply DSCP on the AP-MAG link according to QoS rules (D): Validate received DSCP and apply DSCP according to QoS rules
（A） ：将链路上的DSCP应用于AP（B）：将映射的QoS规则强制应用于接入技术（C）：将AP-MAG链路上的MN指示的QoS等级（QC）映射到DSCP，或验证MN指示的QC并根据QoS规则将DSCP应用于AP-MAG链路（D）：验证收到的DSCP并根据QoS规则应用DSCP
Figure 10: Handover of QoS Rules
图10:QoS规则的切换
A single operator has deployed both a fixed access network and a mobile access network. In this scenario, the operator may wish a harmonized QoS management on both accesses, but the fixed access network does not implement a QoS control framework. So, the operator chooses to rely on the 3GPP policy control function, which is a standard framework to provide a QoS control, and to enforce the 3GPP QoS policy on the Wi-Fi access network. The PMIP interface is used to realize this QoS policy provisioning.
单个运营商同时部署了固定接入网和移动接入网。在这种情况下，运营商可能希望对两个接入进行协调的QoS管理，但固定接入网络不实现QoS控制框架。因此，运营商选择依赖3GPP策略控制功能，这是提供QoS控制的标准框架，并在Wi-Fi接入网络上实施3GPP QoS策略。PMIP接口用于实现此QoS策略供应。
The use case is depicted on Figure 11. The MN first attaches to the Wi-Fi network. During the attachment process, the LMA, which may communicate with Policy Control Function (using procedures outside
用例如图11所示。MN首先连接到Wi-Fi网络。在连接过程中，LMA可能与策略控制功能（使用外部程序）通信
the scope of this document), provides the QoS parameters to the MAG via the QoS option (OC=ALLOCATE) in the PMIP signaling (i.e., PBA). Subsequently, an application on the MN may trigger the request for alternative QoS resources, e.g., by use of the WMM-API (Wi-Fi Multimedia - API). The MN may request that traffic resources be reserved using L2 signaling, e.g., sending an Add Traffic System (ADDTS) message [IEEE802.11-2012]. The request is relayed to the MAG, which includes the QoS parameters in the QoS option (OC=ALLOCATE) on the PMIP signaling (i.e., the PBU initiated upon flow creation). The LMA, in coordination with the PCF, can then authorize the enforcement of such QoS policy. Then, the QoS parameters are provided to the MAG via the QoS option (OC=ALLOCATE, SR-ID, QoS attributes, etc.) in the PMIP signaling, and the equivalent QoS treatment is provided towards the MN on the Wi-Fi link.
本文档的范围），通过PMIP信令（即PBA）中的QoS选项（OC=分配）向MAG提供QoS参数。随后，MN上的应用可触发对替代QoS资源的请求，例如，通过使用WMM-API（Wi-Fi多媒体-API）。MN可以使用L2信令请求保留业务资源，例如，发送添加业务系统（ADDTS）消息[IEEE802.11-2012]。请求被中继到MAG，MAG包括PMIP信令（即，在流创建时启动的PBU）上的QoS选项（OC＝分配）中的QoS参数。然后，LMA与PCF协调，可以授权实施这种QoS策略。然后，通过PMIP信令中的QoS选项（OC＝分配、SR-ID、QoS属性等）向MAG提供QoS参数，并且在Wi-Fi链路上向MN提供等效的QoS处理。
|
|
| +--------+
| |Policy |
| |Control |
| |Function|
| +---+----+
| |
| +---+----+
+----+ +-------+ PMIPv6 | | PGW |
+--+ |WiFi|_______| WLC |========|=| (LMA) |
|MN|~~| AP | | (MAG) | tunnel | +--------+
+--+ +----+ +-------+ |
|
Wi-Fi Access |
Network | Cellular
| Network
|
|
|
| +--------+
| |Policy |
| |Control |
| |Function|
| +---+----+
| |
| +---+----+
+----+ +-------+ PMIPv6 | | PGW |
+--+ |WiFi|_______| WLC |========|=| (LMA) |
|MN|~~| AP | | (MAG) | tunnel | +--------+
+--+ +----+ +-------+ |
|
Wi-Fi Access |
Network | Cellular
| Network
|
Figure 11: QoS Policy Provisioning
图11:QoS策略供应
Figure 12 shows an example of how the QoS rules can be conveyed and enforced between the LMA and MN in the case of initial attachment to WLAN access.
图12显示了在初始连接到WLAN接入的情况下，如何在LMA和MN之间传输和实施QoS规则的示例。
+--+ +--+ +---+ +---+
|MN| |AP|-------------|MAG|-----------------------|LMA|
+--+ +--+ +---+ +---+
| | | |
| | | |
+----attached---+ | [QoS rules]
| | | |
new session |(E) |(F) |data
|----data[QC]-->|---data[DSCPa]-->|-======data[DSCPb]=======->|--->
| | |--PBU[update,QoS option]-->|
| | | (ReReg) (OC=1) Validate and
| | | add QoS rule
| | |<----PBA[QoS option]----|
| |<-INFO[QoSrules]-| (OC=1, SR-ID)[QoS rules']
| | | |
| Apply Establish |
| adapted MN's uplink |
| QoS rules DSCP rules |
| | | |
| | | |
| | | |data
|<--data[QC]----|<---data[DSCP]---|<-======data[DSCP]========-|<----
| | | |
| | | |data
|---data[QC]--->|-->data[DSCP]--->|-=======data[DSCP]=======->|--->
| | | |
| | | |
+--+ +--+ +---+ +---+
|MN| |AP|-------------|MAG|-----------------------|LMA|
+--+ +--+ +---+ +---+
| | | |
| | | |
+----attached---+ | [QoS rules]
| | | |
new session |(E) |(F) |data
|----data[QC]-->|---data[DSCPa]-->|-======data[DSCPb]=======->|--->
| | |--PBU[update,QoS option]-->|
| | | (ReReg) (OC=1) Validate and
| | | add QoS rule
| | |<----PBA[QoS option]----|
| |<-INFO[QoSrules]-| (OC=1, SR-ID)[QoS rules']
| | | |
| Apply Establish |
| adapted MN's uplink |
| QoS rules DSCP rules |
| | | |
| | | |
| | | |data
|<--data[QC]----|<---data[DSCP]---|<-======data[DSCP]========-|<----
| | | |
| | | |data
|---data[QC]--->|-->data[DSCP]--->|-=======data[DSCP]=======->|--->
| | | |
| | | |
(E): AP may enforce uplink QoS rules according to priority class set by the MN (F): MAG can enforce a default QoS class until the local mobility anchor classifies the new flow (notified with PBA) or the mobile access gateway classifies new flow and proposes the associated QoS class to the local mobility anchor for validation (proposed with PBU, notification of validation result with PBA)
（E） ：AP可根据MN（F）设置的优先级等级强制上行链路QoS规则：MAG可强制默认QoS等级，直到本地移动锚对新流进行分类（用PBA通知）或移动接入网关对新流进行分类并向本地移动锚提出相关联的QoS等级以供验证（与PBU一起提议，与PBA一起通知验证结果）
Figure 12: Adding New QoS Service Request for MN-Initiated Flow
图12：为MN发起的流添加新的QoS服务请求
A mobile node is attached to the WLAN access and has obtained QoS parameters from the LMA for that mobility session. Having obtained the QoS parameters, a new application, e.g., IP Multimedia Subsystems (IMS) application, gets launched on the mobile node that requires certain QoS support.
移动节点连接到WLAN接入，并且已经从LMA获得用于该移动会话的QoS参数。在获得QoS参数之后，在需要特定QoS支持的移动节点上启动新的应用程序，例如IP多媒体子系统（IMS）应用程序。
The application on the mobile node initiates the communications via a dedicated network function (e.g., IMS Call Session Control Function). Once the communication is established, the application network function notifies the PCF about the new IP flow. The PCF function in turn notifies the LMA about the needed QoS parameters identifying the IP flow and QoS parameters. LMA sends an Update Notification message [RFC7077] to the MAG with the Notification Reason value set to QOS_SERVICE_REQUEST. On receiving the Update Notification message, the MAG completes the PBU/PBA signaling for obtaining the new QoS parameters via the QoS options (OC=MODIFY, SR-ID, QoS attributes, etc.). The MAG provisions the newly obtained QoS parameters on the access network to ensure the newly established IP flow gets its requested network resources.
移动节点上的应用通过专用网络功能（例如，IMS呼叫会话控制功能）发起通信。一旦建立通信，应用程序网络功能将通知PCF新的IP流。PCF功能反过来通知LMA关于识别IP流和QoS参数的所需QoS参数。LMA向MAG发送更新通知消息[RFC7077]，通知原因值设置为QOS_服务_请求。在接收到更新通知消息时，MAG完成PBU/PBA信令以通过QoS选项（OC＝修改、SR-ID、QoS属性等）获得新的QoS参数。MAG在接入网络上提供新获得的QoS参数，以确保新建立的IP流获得其请求的网络资源。
Upon termination of the established IP flow, the application function again notifies the PCF function to remove the established QoS parameters. The PCF notifies the LMA to withdraw the QoS resources established for that voice flow. The LMA sends an Update Notification message to the MAG with the "Notification Reason" value set to "FORCE-REREGISTRATION". On receiving this Update Notification Acknowledgement message, the MAG completes the PBU/PBA signaling for removing the existing QoS rules (OC=DE-ALLOCATE, SR-ID). The MAG then removes the QoS parameters from the corresponding IP flow and releases the dedicated network resources on the access network.
在已建立的IP流终止时，应用程序功能再次通知PCF功能删除已建立的QoS参数。PCF通知LMA撤回为该语音流建立的QoS资源。LMA向MAG发送更新通知消息，其“通知原因”值设置为“强制重新注册”。在接收到该更新通知确认消息时，MAG完成PBU/PBA信令以移除现有QoS规则（OC＝取消分配，SR-ID）。然后，MAG从相应的IP流中移除QoS参数，并释放接入网络上的专用网络资源。
Appendix B. Information When Implementing PMIP-Based QoS Support with IEEE 802.11e
附录B.使用IEEE 802.11e实现基于PMIP的QoS支持时的信息
This section shows, as an example, the end-to-end QoS management with a 802.11e-capable WLAN access link and a PMIP-based QoS support.
本节以支持802.11e的WLAN接入链路和基于PMIP的QoS支持为例，展示了端到端QoS管理。
The 802.11e, or Wi-Fi Multimedia (WMM), specification provides prioritization of packets for four types of traffic, or access categories (ACs):
802.11e或Wi-Fi多媒体（WMM）规范为四种类型的流量或访问类别（ACs）提供了数据包优先级：
Voice (AC_VO): Very high-priority queue with minimum delay. Time-sensitive data such as VoIP and streaming mode are automatically sent to this queue.
语音（AC_VO）：具有最小延迟的高优先级队列。对时间敏感的数据（如VoIP和流模式）会自动发送到此队列。
Video (AC_VI): High-priority queue with low delay. Time-sensitive video data is automatically sent to this queue.
视频（AC_VI）：具有低延迟的高优先级队列。对时间敏感的视频数据会自动发送到此队列。
Best effort (AC_BE): Medium-priority queue with medium throughput and delay. Most traditional IP data is sent to this queue.
尽力而为（AC_BE）：具有中等吞吐量和延迟的中等优先级队列。大多数传统的IP数据都发送到此队列。
Background (AC_BK): Lowest-priority queue with high throughput. Bulk data that requires maximum throughput but is not time-sensitive (for example, FTP data) is sent to the queue.
后台（AC_BK）：具有高吞吐量的最低优先级队列。需要最大吞吐量但对时间不敏感的大容量数据（例如FTP数据）被发送到队列。
The access point uses the 802.11e indicator to prioritize traffic on the WLAN interface. On the wired side, the access point uses the 802.1p priority tag and DSCP. To allow consistent QoS management on both wireless and wired interfaces, the access point relies on the 802.11e specification, which defines mapping between the 802.11e access categories and the IEEE 802.1D priority (802.1p tag). The end-to-end QoS architecture is depicted in Figure 13, and the 802.11e /802.1D priority mapping is shown in the following table:
接入点使用802.11e指示器对WLAN接口上的流量进行优先级排序。在有线端，接入点使用802.1p优先级标签和DSCP。为了在无线和有线接口上实现一致的QoS管理，接入点依赖于802.11e规范，该规范定义了802.11e接入类别和IEEE 802.1D优先级（802.1p标签）之间的映射。端到端QoS架构如图13所示，802.11e/802.1D优先级映射如下表所示：
+-----------+------------------+
| 802.1e AC | 802.1D priority |
+-----------+------------------+
| AC_VO | 7,6 |
+-----------+------------------+
| AC_VI | 5,4 |
+-----------+------------------+
| AC_BE | 0,3 |
+-----------+------------------+
| AC_BK | 2,1 |
+-----------+------------------+
+-----------+------------------+
| 802.1e AC | 802.1D priority |
+-----------+------------------+
| AC_VO | 7,6 |
+-----------+------------------+
| AC_VI | 5,4 |
+-----------+------------------+
| AC_BE | 0,3 |
+-----------+------------------+
| AC_BK | 2,1 |
+-----------+------------------+
+=============+ +-----+
DSCP/802.1p | PDP |
mapping table +-----+
+=============+ PEP |
`._ +---+---+ |
`._ |WiFi AR| PMIPv6 +-----+
- + (MAG) +===============| LMA |
| WLC | tunnel +-----+
+-------+ PEP
|
==Video== 802.1p/DSCP
==Voice== |
== B.E.== +----+
+----+ |WLAN| PEP
| MN |----802.11e----| AP |
+----+ +----+
+=============+ +-----+
DSCP/802.1p | PDP |
mapping table +-----+
+=============+ PEP |
`._ +---+---+ |
`._ |WiFi AR| PMIPv6 +-----+
- + (MAG) +===============| LMA |
| WLC | tunnel +-----+
+-------+ PEP
|
==Video== 802.1p/DSCP
==Voice== |
== B.E.== +----+
+----+ |WLAN| PEP
| MN |----802.11e----| AP |
+----+ +----+
Figure 13: End-to-End QoS Management with 802.11e
图13:802.11e的端到端QoS管理
When receiving a packet from the MN, the AP checks whether the frame contains 802.11e markings in the L2 header. If not, the AP checks the DSCP field. If the uplink packet contains the 802.11e marking, the access point maps the access categories to the corresponding 802.1D priority as per the table above. If the frame does not contain 802.11e marking, the access point examines the DSCP field.
当从MN接收数据包时，AP检查帧是否在L2报头中包含802.11e标记。如果没有，AP将检查DSCP字段。如果上行链路分组包含802.11e标记，则接入点根据上表将接入类别映射到相应的802.1D优先级。如果帧不包含802.11e标记，则接入点检查DSCP字段。
If DSCP is present, the AP maps DSCP values to a 802.1p value (i.e., 802.1D priority). This mapping is not standardized and may differ between operators; a mapping example is given in the following table.
如果存在DSCP，AP将DSCP值映射到802.1p值（即802.1D优先级）。该映射未标准化，操作员之间可能存在差异；下表给出了映射示例。
+-------------------+--------+------------+
| Type of traffic | 802.1p | DSCP value |
+-------------------+--------+------------+
| Network Control | 7 | 56 |
+-------------------+--------+------------+
| Voice | 6 | 46 (EF) |
+-------------------+--------+------------+
| Video | 5 | 34 (AF 41) |
+-------------------+--------+------------+
| Voice Control | 4 | 26 (AF 31) |
+-------------------+--------+------------+
| Background Gold | 2 | 18 (AF 21) |
+-------------------+--------+------------+
| Background Silver | 1 | 10 (AF 11) |
+-------------------+--------+------------+
| Best Effort | 0,3 | 0 (BE) |
+-------------------+--------+------------+
+-------------------+--------+------------+
| Type of traffic | 802.1p | DSCP value |
+-------------------+--------+------------+
| Network Control | 7 | 56 |
+-------------------+--------+------------+
| Voice | 6 | 46 (EF) |
+-------------------+--------+------------+
| Video | 5 | 34 (AF 41) |
+-------------------+--------+------------+
| Voice Control | 4 | 26 (AF 31) |
+-------------------+--------+------------+
| Background Gold | 2 | 18 (AF 21) |
+-------------------+--------+------------+
| Background Silver | 1 | 10 (AF 11) |
+-------------------+--------+------------+
| Best Effort | 0,3 | 0 (BE) |
+-------------------+--------+------------+
The access point prioritizes ingress traffic on the Ethernet port based on the 802.1p tag or the DSCP value. If the 802.1p priority tag is not present, the access point checks the DSCP/802.1p mapping table. The next step is to map the 802.1p priority to the appropriate egress queue. When 802.11e support is enabled on the wireless link, the access point uses the IEEE standardized 802.1p/ 802.11e correspondence table to map the traffic to the appropriate hardware queues.
接入点根据802.1p标签或DSCP值对以太网端口上的入口流量进行优先级排序。如果802.1p优先级标签不存在，接入点将检查DSCP/802.1p映射表。下一步是将802.1p优先级映射到适当的出口队列。在无线链路上启用802.11e支持时，接入点使用IEEE标准化的802.1p/802.11e对应表将流量映射到适当的硬件队列。
When the 802.11e-capable client sends traffic to the AP, it usually marks packets with a DSCP value. In that case, the MAG/LMA can come into play for QoS renegotiation and call flows depicted in Appendix A apply. Sometimes, when communication is initiated on the WLAN access, the application does not mark upstream packets. If the uplink packet does not contain any QoS marking, the AP/MAG could determine the DSCP field according to traffic selectors received from the LMA. Figure 14 gives the call flow corresponding to that use case and shows where QoS tags mapping does come into play. The main steps are as follows:
当支持802.11e的客户端向AP发送流量时，它通常使用DSCP值标记数据包。在这种情况下，MAG/LMA可用于QoS重新协商，并适用附录A中描述的呼叫流。有时，在WLAN接入上启动通信时，应用程序不会标记上行数据包。如果上行链路分组不包含任何QoS标记，则AP/MAG可以根据从LMA接收的业务选择器来确定DSCP字段。图14给出了与该用例对应的调用流，并显示了QoS标记映射在何处发挥作用。主要步骤如下：
(A): During the MN attachment process, the MAG fetches QoS policies from the LMA. After this step, both the MAG and LMA are provisioned with QoS policies.
（A） ：在MN连接过程中，MAG从LMA获取QoS策略。在该步骤之后，MAG和LMA都被提供QoS策略。
(B): The MN starts a new IP communication without making IP packets with DSCP tags. The MAG uses the traffic selector to determine the DSCP value; it then marks the IP packet and forwards within the PMIP tunnel.
（B） ：MN启动新的IP通信，而不生成带有DSCP标记的IP数据包。MAG使用流量选择器确定DSCP值；然后标记IP数据包并在PMIP隧道内转发。
(C): The LMA checks the DSCP value with respect to the traffic selector. If the QoS policies are valid, the LMA forwards the packet without renegotiating the QoS rules.
（C） ：LMA检查与流量选择器相关的DSCP值。如果QoS策略有效，LMA转发分组而不重新协商QoS规则。
(D): When receiving a marked packet, the MAG, the AP, and the MN use 802.11e (or WMM), 802.1p tags, and DSCP values to prioritize the traffic.
（D） ：当接收到标记的数据包时，MAG、AP和MN使用802.11e（或WMM）、802.1p标记和DSCP值对流量进行优先级排序。
+--+ +--+ +---+ +---+
|MN| |AP| |MAG| |LMA|
+--+ + -+ +---+ +---+
(A)|----attach-----|---------------->|-----------PBU---------->|
|<--------------|---------------- |<----PBA[QoS option]-----|
. . [QoS rules] [QoS rules]
(B). . . |
new session | | |
|----data[]---->|----data[]------>|-======data[DSCP]======->|
| | | |
(C)| | | Validate QoS rule
| | | |--->
| | |<======data[DSCP]========|<----
| | | |
| | mapping |
(D)| | DSCP/802.1p |
| |<----data--------| |
| | [802.1p/DSCP] | |
| | | |
| mapping | |
| 802.1p/802.11e | |
|<--data[WMM]---| | |
| | | |
|---data[WMM]-->|------data------>|=======data[DSCP]=======>|--->
| | [802.1p/DSCP] | |
| | | |
+--+ +--+ +---+ +---+
|MN| |AP| |MAG| |LMA|
+--+ + -+ +---+ +---+
(A)|----attach-----|---------------->|-----------PBU---------->|
|<--------------|---------------- |<----PBA[QoS option]-----|
. . [QoS rules] [QoS rules]
(B). . . |
new session | | |
|----data[]---->|----data[]------>|-======data[DSCP]======->|
| | | |
(C)| | | Validate QoS rule
| | | |--->
| | |<======data[DSCP]========|<----
| | | |
| | mapping |
(D)| | DSCP/802.1p |
| |<----data--------| |
| | [802.1p/DSCP] | |
| | | |
| mapping | |
| 802.1p/802.11e | |
|<--data[WMM]---| | |
| | | |
|---data[WMM]-->|------data------>|=======data[DSCP]=======>|--->
| | [802.1p/DSCP] | |
| | | |
Figure 14: Prioritization of a Flow Created on the WLAN Access
图14：WLAN接入上创建的流的优先级
Appendix C. Information When Implementing with a Broadband Network Gateway
附录C.使用宽带网络网关实施时的信息
This section shows an example of QoS interworking between the PMIPv6 domain and the broadband access. The Broadband Network Gateway (BNG) or Broadband Remote Access Server (BRAS) has the MAG function, and the CPE (Customer Premise Equipment) or Residential Gateway (RG) is connected via the broadband access network. The MN is attached to the RG via, e.g., Wi-Fi AP in the broadband home network. In the segment of the broadband access network, the BNG and RG are the Policy Enforcement Point (PEP) for the downlink and uplink traffic, respectively. The QoS information is downloaded from the LMA to the BNG via the PMIPv6 with the QoS option defined in this document. Based on the received QoS parameters (e.g., DSCP values), the broadband access network and the RG provide appropriate QoS treatment to the downlink and uplink traffic to/from the MN.
本节展示了PMIPv6域和宽带接入之间的QoS互通示例。宽带网络网关（BNG）或宽带远程接入服务器（BRAS）具有MAG功能，CPE（客户现场设备）或住宅网关（RG）通过宽带接入网络连接。MN通过宽带家庭网络中的Wi-Fi AP连接到RG。在宽带接入网段中，BNG和RG分别是下行和上行业务的策略实施点（PEP）。QoS信息通过PMIPv6从LMA下载到BNG，QoS选项在本文件中定义。基于接收到的QoS参数（例如，DSCP值），宽带接入网络和RG向到/来自MN的下行链路和上行链路业务提供适当的QoS处理。
+-----+
| PDP |
+-----+
PEP |
+-------+ |
| BNG/ | PMIPv6 +-----+
| BRAS +===============| LMA |
| (MAG) | tunnel +-----+
+-------+ PEP
Broadband ( | )
Access ( DSCP )
Network ( | )
+-----+
+----+ | CPE | PEP
| MN |-------------| /RG |
+----+ Broadband +-----+
Home Network
+-----+
| PDP |
+-----+
PEP |
+-------+ |
| BNG/ | PMIPv6 +-----+
| BRAS +===============| LMA |
| (MAG) | tunnel +-----+
+-------+ PEP
Broadband ( | )
Access ( DSCP )
Network ( | )
+-----+
+----+ | CPE | PEP
| MN |-------------| /RG |
+----+ Broadband +-----+
Home Network
Figure 15: End-to-End QoS Management with the Broadband Access Network
图15：宽带接入网络的端到端QoS管理
In the segment of the broadband access network, QoS mapping between 3GPP QCI values and DSCP described in Section 6.2 is applied. In the segment of the broadband home network, if the MN is attached to the RG via Wi-Fi, the same QoS mapping as described in Appendix B can be applied.
在宽带接入网络段中，应用第6.2节中描述的3GPP QCI值和DSCP之间的QoS映射。在宽带家庭网络段中，如果MN通过Wi-Fi连接到RG，则可以应用附录B中描述的相同QoS映射。
Authors' Addresses
作者地址
Marco Liebsch NEC Kurfuersten-Anlage 36 Heidelberg D-69115 Germany
Marco Liebsch NEC Kurfuersten Anlage 36德国海德堡D-69115
EMail: liebsch@neclab.eu
EMail: liebsch@neclab.eu
Pierrick Seite Orange 4, rue du Clos Courtel, BP 91226 Cesson-Sevigne 35512 France
Pierrick Seite Orange 4号，英国石油公司，邮编91226，法国塞森塞维涅35512
EMail: pierrick.seite@orange.com
EMail: pierrick.seite@orange.com
Hidetoshi Yokota KDDI Lab 2-1-15 Ohara Saitama, Fujimino 356-8502 Japan
横田英寿KDDI实验室2-1-15日本富士米诺大原斋玉356-8502
EMail: yokota@kddilabs.jp
EMail: yokota@kddilabs.jp
Jouni Korhonen Broadcom Communications Porkkalankatu 24 Helsinki FIN-00180 Finland
Jouni Korhonen Broadcom Communications Porkkalankatu 24赫尔辛基FIN-00180芬兰
EMail: jouni.nospam@gmail.com
EMail: jouni.nospam@gmail.com
Sri Gundavelli Cisco 170 West Tasman Drive San Jose, CA 95134 USA
美国加利福尼亚州圣何塞市西塔斯曼大道170号，邮编95134
EMail: sgundave@cisco.com
EMail: sgundave@cisco.com