Post on 27-Dec-2015
transcript
China TelecommPeirong Xie (xiepr@gsta.com)
ZTE CorporationRajesh Bhalla (
rabhalla@zteusa.com)
HuaweiJixing Liu (
liujixing@huawei.com)
Page 1
SubscriberQoSProfile Configuration Procedure Related
Operator Requirements
July 25, 2011
Page 2
Notice
The contributing companies grant a free, irrevocable license to 3GPP2 and its Organizational Partners to incorporate text or other copyrightable material contained in the contribution and any modifications thereof in the creation of 3GPP2 publications; to copyright and sell in Organizational Partner’s name any Organizational Partner’s standards publication even though it may include all or portions of this contribution; and at the Organizational Partner’s sole discretion to permit others to reproduce in whole or in part such contribution or the resulting Organizational Partner’s standards publication. The contributing companies are also willing to grant licenses under such contributor copyrights to third parties on reasonable, non-discriminatory terms and conditions for purpose of practicing an Organizational Partner’s standard which incorporates this contribution.
This document has been prepared by the contributing companies to assist the development of specifications by 3GPP2. It is proposed to the Committee as a basis for discussion and is not to be construed as a binding proposal on the contributors. The contributing companies specifically reserves the right to amend or modify the material contained herein and nothing herein shall be construed as conferring or offering licenses or rights with respect to any intellectual property of the contributors other than provided in the copyright statement above.
AbstractThis contribution presents the following TWO
operator requirements:(1) With Pi*3GPP2 Diameter Application the 3GPP2
AAA shall have the capability to support either or both, the HSGW Relocation and the SubscriberQoSProfile Configuration Procedures
(2) The operator shall have the capability to configure at the eAN/ePCF, the SubscriberQoS Profile parameters that can be derived from the 3GPP EPS related information received at the HSGW from the HSS/PCRF during Authorization/Bearer Activation Procedures
The above stated operator requirements be supported in X.S0057-B release of specifications
Page 3
Background – Requirement #1 X.S0057-A specifies Pi*3GPP2 Diameter Application as an optional
capability at the HSGW and the 3GPP2 AAA Pi*3GPP2 Diameter Application couples two eHRPD related features:
3GPP2 AAA assisted HSGW Relocation Procedure3GPP2 AAA assisted SubscriberQoSProfile Configuration Procedure
HSGW advertises support for Pi*3GPP2 Diameter Application if it supports HSGW Relocation OR SubscriberQoSProfile Configuration Procedure
3GPP2 AAA advertises support for Pi*3GPP2 Diameter Application if it supports HSGW Relocation AND SubscriberQoSProfile Configuration Procedures
The HSGW and the 3GPP2 AAA use Supported-Features AVP to negotiate peer’s support for SubscriberQoSProifle Configuration Procedure
No such capability exchange is used to negotiate peer’s support for HSGW Relocation Procedure
Page 4
Operator Requirements - #1If Pi*3GPP2 Diameter Application is advertized:
The Diameter Capability Exchange procedure specified in X.S0057-A effectively mandates the 3GPP2 AAA to support both, the HSGW Relocation and SubcriberQoSProfile Configuration Procedures
This does not meet operator requirements to have the capability to support either or both of the above mentioned procedures at the 3GPP2 AAA
Pi*3GPP2 Diameter Capability exchange procedure needs to be enhanced to allow the operator to have such a capability
It is recommended that such enhancements be adopted in X.S0057-B release specifications
Page 5
Background – Requirement #2 In case the 3GPP2 AAA does not support
SubscriberQoSProfile Configuration procedure, the HSGW will not receive 3GPP2 Subscriber QoS Profile parameters (specified in Annex-D, X.S0057-A) from the 3GPP2 AAA
It is, however, possible to derive some 3GPP2 Subscriber QoS Profile parameters from the 3GPP EPS related information received at the HSGW from the HSS during Authentication and Authorization proceduresMaximum Authorized Aggregate Bandwidth for Best-Effort
Traffic parameter can be derived from the UE-AMBR parameterInter-User Priority for Best-Effort Traffic parameter can be
derived from the QCI in Subscribed QoS-Profile parameter in APN-Configuration associated with the default bearer for the APN
Page 6
Operator Requirements - # 2If 3GPP2 AAA does not support SubscriberQoSProfile
Configuration Procedure, the HSGW shall have the capability to derive the following 3GPP2 Subscriber QoS Profile parameters from the 3GPP EPS related information received at the HSGW from the HSS during Authentication and Authorization procedure and forward such information to the eAN/ePCF:Inter-User Priority for Best-Effort Traffic parameter from
the QCI in Subscribed QoS-Profile parameter in APN-Configuration associated with the default bearer for the APN
Maximum Authorized Aggregate Bandwidth for Best-Effort Traffic parameter from the UE-AMBR parameter
It is recommended that such enhancements be adopted in X.S0057-B release specifications
Page 7
More on Operator Requirements - # 2Inter-User Priority for Best-Effort Traffic parameter
derived from the QCI in the Subscribed QoS-Profile parameter in APN-Configuration associated with the default bearer for the APN
Maximum Authorized Aggregate Bandwidth for Best-Effort Traffic parameter derived from the UE-AMBR parameter
HSGW then forwards the above stated parameters to the eAN/ePCF via A11-Session Update message
In case there is a multiple set of Subscriber QoS Profile parameters at the HSGW, the HSGW has the capability to combine such multiple parameters into a single set of Subscriber QoS Profile parameter as specified in Section 3.3.4, X.S0011-004 specifications
Page 8
Background Info on QCI Parameter QoS Class Identifier (QCI) is a scalar value which classifies a
set of bearer parameters suitable for a particular class of applications
The bearer parameters associated with QCI are: Packet Delay Budget Packet Delay LossPriority Resource Type (GBR or Non-GBR)
QCI is received at the HSGW in the Subscribed QoS-Profile parameter in the APN-Configuration associated with the default bearer fro the APN during Authentication and Authorization procedure
Inter-User Priority for Best-Effort Traffic parameter can be derived from the Priority parameter associated with the QCI
Page 9
Background Info on UE-AMBR Parameter UE-AMBR is stored as a subscription parameter in the HSS Subscribed UE-AMBR is received at the HSGW during UE
Authentication and Authorization Procedure UE-AMBR limits the aggregate bit rate that can be expected
to be provided across all Non-GBR bearers of a UE For E-UTRAN access, the MME sets the UE-AMBR to the sum
of the APN-AMBR for all active APNs up to the value of the Subscriber UE-AMBR
For eHRPD access, the following two options for setting UE-AMBR have been considered:Option 1: HSGW sets UE-AMBR to the Subscriber UE-AMBR
received from the HSSOption 2: HSGW sets UE-AMBR to the sum of the APN-
AMBR of all active APNs up to the value of the Subscribed UE-AMBR
Page 10
More Info on UE-AMBR ParameterBased on such background information it is
recommended that:HSGW sets UE-AMBR to the sum of the APN-AMBR of all active
APNs up to the value of the Subscribed UE-AMBR (Option2)Maximum Authorized Aggregate Bandwidth for Best-Effort
Traffic parameter be mapped from the DL data rate in the UE-AMBR parameter
Account for the difference in the data rates of E-UTRAN and eHRPD access technologies while mapping the DL data rate in the 3GPP UE-AMBR parameter to the 3GPP2 Maximum Authorized Aggregate Bandwidth for Best-Effort Traffic parameter
Enforcement of the APN-AMBR in the uplink is done in the UE
Enforcement of the UE-AMBR in the uplink is done in the UE
Page 11
Recommendations Operator Requirement # 1 be adopted for
enhancements to X.S0057-B specifications With Pi*3GPP2 Diameter Application the 3GPP2 AAA
shall have the capability to support either or both, the HSGW Relocation and the SubscriberQoSProfile Configuration Procedures
Operator Requirement # 2 be adopted for enhancements to X.S0057-B specifications
The operator shall have the capability to configure at the eAN/ePCF, the SubscriberQoS Profile parameters that can be derived from the 3GPP EPS related information received at the HSGW from the HSS during Authorization and Authorization Procedures
Page 12
Thanks
Page 13