End to End Bandwidth Control

1.1.1

Definition

Due the SCG cannot deliver the session QoS to GGSN, PCRF should integrate with GGSN via
standard Gx interface to establishment the E2E bandwidth control. If the PCRF connects to
multiple PCEFs of different types, each PCEF may request the PCRF to establish a Gx session
after a subscriber initiates an IP connectivity access network (IP-CAN) session establishment
request. When the PDP session establishes, the PCRF should do as follow description:

Establish Gx sessions with multiple PCEFs, and deliver different policies to different
PCEFs based on policy configuration.

Correlate Gx sessions of a subscriber by using the subscriber's IP address or the

combination of the subscriber's IP address and access point name (APN), and
deliver updated policies to other correlated PCEFs based on status changes
reported by a PCEF.

Multi-PCEF network topology

The PCRF connects to two types of PCEFs: GGSN and DPI(SCG). The GGSN performs quality of
service (QoS) control on sessions. The SCG performs service flow control and report subscriber
quota status to the PCRF. When connecting to the two types of PCEFs, the PCRF delivers
different policies for enforcement:

The PCRF delivers session-level QoS rules to the GGSN, and it updates
session-level QoS rules based on the quota status report from the SCG.

The PCRF delivers service-level QoS rules and quota slices to the SCG.

ME

Function

Dependency

GGSN

1. Exchange the session QoS attributes

with PCRF.

Support the QoS negotiation and

QoS Update.

2. Detect and report the event trigger

except Usage_Report to PCRF.
RNC/NodeB

Implement the session QoS control.

Configure the mapping ship

between ARP and subscriber.
Configure the priority of THP
Class.
Configure the schedule prority

ME

Function

Dependency
mapping ship.
Configure the SPI weight for SPI.
Set the value of switch
URRCTRLSWITCH to 1.
Below License should be actived
in RNC site:
WRFD-020806 Differentiated
Service Based on SPI Weight
WRFD-01061103 Scheduling
based on EPF and GBR
WRFD-010638 Dynamic CE
Resource Management
WRFD-050408 Overbooking on IP
Transmission
WRFD-010637 HSUPA Iub Flow
Control
WRFD-010505 Queuing and
Preemption

SCG

1. Implement the service QoS control.

N/A

2. Accumulate the quota usage and

report to PCRF.
PCRF

1. Deliver the session QoS parment to

GGSN.

N/A

2. Deliver the service policy and quota

slice to SCG.
3. Update the session QoS base on the
usage of session bundle.

Implementation

The following figure describes the end to end service flow that UE
initial PDP connection.
End to End service flow of PDP connection

UE

NODEB

RNC

SGSN

HLR

SCG

GGSN

PCRF

1.Attach request
2.Update location
3. Insert subscriber data
(QoS)
4. Attach accept
5. Active PDP context request
6. Create PDP context request(Qos)
7.CCR-I(MSISDN,QoS-Upgrade,
QoS-Negotiation,Qos)
8. Account start
request
9.CCA-I(Session QoS, Predefine rule)
10.Create PDP context response(Qos)
11. Account start
response
12. CCR-I(MSISDN)
13. CCA-I(Service Qos,
PCN)
14.Radius access
bearer assignment
Request(QoS)
15.Radio link reconfiguration
prepare(QoS)
16.Radio link reconfiguration
ready
17.Radius access
bearer assignment
response
18. Active PDP context response

1.

The user equipment (UE) of a subscriber sends an Attach request to the

SGSN.

2.

The SGSN sends an Update Location message to the HLR.

3.

HLR response SGSN with subscriber Data include QoS parameters, like MBR,
ARP etc.

4.

The SGSN sends Attach response to the UE.

5.

UE sends an Active PDP context request to the SGSN.

6.

The SGSN sends a create PDP context request with QoS parameters to the
GGSN.

7.

The GGSN sends a CCR-Initial message to the PCRF over the Gx interface to
request the session setup. In the CCR-I message, the QoS-Negotiation and
QoS-Upgrade AVPs should be carried.

8.

GGSN sends Account-Start-Request to SCG.

9.

The PCRF queries the subscriber's subscription information based on the

subscriber ID contained in the CCR-Initial message. It sends a CCA-Initial
message containing the subscriber's authorized QoS and rules to the GGSN.

10. The GGSN installs the authorized rules and send the PDP attach response
with QoS to the SGSN.

11. SCG responses GGSN Account-Start-Response to GGSN.

12. After the subscriber starts using the data service, the SCG retrieves the IP
address from the data flow and sends a CCR-Initial message to the PCRF.

13. The PCRF establishes a Gx session with the SCG and correlates the Gx
sessions of the subscriber by using the subscriber's IP address. Then, the
PCRF delivers quota slice and service flow policies to the SCG based on the
subscriber's subscription information.

14. The SGSN sends a RAB Assignment Request message to the RNC over the
Iu interface. In the RANAP message, the MBR, ARP messages should be
carried.

15. The RNC sends a Radio Link Reconfiguration Prepare message to the NodeB
over the Iub interface. In the NBAP message, the MBR, SPI weight should be
carried.

16. The NodeB sends a Radio Link Reconfiguration Response message back to
the RNC to respond.

17. The RNC sends a RAB Assignment Response message back to the SGSN to
respond.

18. SGSN sends the Active PDP response to the UE.

UE

The following figure describes the end to end service flow that UE
move from 3G to 2G.

BSC

BTS

RNC

NODEB

SGSN

HLR

SCG

GGSN

PCRF

1a. Cell Change Order

1b. Cell Change Order

2. Radio Link Failure

Indication
3a. Routing Area
Update Request

3b. Routing Area

Update Request

3c. Routing Area Update Request

4. SRNS Context Request
5. SRNS Context Request
6. SRNS Data Forward
Command

7.Update PDP Cotext Request

8.CCR-U(MSISDN,QoS-Upgrade,
QoS-Negotiation,Qos,RAT)
9. Account Update
request
10.CCA-U(Session QoS, Predefine rule)
11. Account Update
response
12.Update PDP Cotext Response
QoS MBR/ARP
15. Iu Release Command

13. CCR-U(MSISDN)

16. Iu Release Complete

14. CCA-U(Service Qos,

PCN)
17. Location Update
Request
18. Location Update
Accept

19. Radio Link Deletion

Request
20. Radio Link Deletion
Response
21. Modify PDP Context Request
22.Modify PDP Context Accept
23. Routing Area Update Accept

1.

The RAN decides to perform an intersystem change which makes the MS

switch to a new cell where A/Gb mode has to be used, and stops transmission
to the network.

2.

The NodeB sends a Radio Link Failure Indication to RNC.

3.

The MS sends a Routing Area Update Request (old RAI, old P-TMSI
Signature, Update Type, Voice domain preference and UE's usage setting)
message to the 2G+3G-SGSN.

4.

The SGSN sends an SRNS Context Request message to the RNC.

5.

The RNC responds with an SRNS Context Response message to SGSN.

6.

The SGSN sends an SRNS Data Forward Command message to the RNC.

7.

The SGSN sends Update PDP Context Request (SGSN Address and TEID,
QoS Negotiated, RAT type) message to the GGSN.

8.

The GGSN sends CCR-U to PCRF with RAT-Change event trigger and new
RAT type.

9.

The GGSN sends Accounting Update Request to the SCG.

10. The PCRF sends CCA-U message to the GGSN with new Qos (MBR/ARP).
11. The SCG sends Accounting Update Response to the GGSN.
12. The GGSN sends Update PDP Context Response message (MBR/ARP) to
the GGSN.
13. The SCG sends CCR-U message to the PCRF with RAT-type-change event
trigger and new RAT type.
14. The PCRF sends CCA-U message to the SCG with new Qos (MBR/ARP).
15. The SGSN sends an Iu Release Command message to the RNC.
16. The RNC responds with an Iu Release Complete message to the SGSN.
17. The SGSN sends the Update Location Request to the HLR.
18. The HLR responds the Update Location Accept to the SGSN.
19. The RNC sends the Radio Link Deletion Request to NodeB.
20. The NodeB sends the Radio Link Deletion Response to RNC.
21. The SGSN send a Modify PDP Context Request (QoS Negotiated, ARP)
message to the MS.
22. The MS sends Modify PDP Context Accept to the SGSN.
23. The SGSN sends Routing Area Update Accept to the MS.

The following describes how the PCRF performs volume-based

policy control when the PCRF connects to the GGSN and SCG.

The PCRF correlates the Gx sessions between the PCRF and the GGSN and
SCG after a subscriber originates an IP-CAN session from the GGSN. Below
figure shows the message flow.

Correlating the Gx sessions between the PCRF and the GGSN and SCG

UE

GGSN

SCG

PCRF

1.PDP Connection request

2.CCR-I(MSISDN,QoS-Upgrade,
QoS-Negotiation)
PCRF deliver Qos parameters
and predefine rule to GGSN
3.CCA-I(Session bandwidth, Predefine rule)
4.PDP Connection reponse
5. Account start request
6. Account start response
7. CCR-I(MSISDN)
PCRF correlates the Gx session established for the same subscriber
by using the subscribers IP and delivers service flow policies
8. CCA-I(Service Qos,PCN,
Quota slice)

1.

The user equipment (UE) of a subscriber sends an IP-CAN Establish Request

message.

2.

The GGSN sends a CCR-Initial message to the PCRF over the Gx interface to
request the session setup. In the CCR-I message, the QoS-Negotiation and
QoS-Upgrade AVPs should be carried.

3.

The PCRF queries the subscriber's subscription information based on the

subscriber ID contained in the CCR-Initial message. PCRF sends a
CCA-Initial message containing the subscriber's authorized QoS and
predefine rule to the GGSN.

4.

The GGSN installs the authorized rules and sends an IP-CAN Establish
Response message to the UE.

5.

GGSN sends Account-Start-Request to SCG.

6.

SCG responses GGSN Account-Start-Response to GGSN.

7.

After the subscriber starts using the data service, the SCG retrieves the IP
address from the data flow and sends a CCR-Initial message to the PCRF.

8.

The PCRF establishes a Gx session with the SCG and correlates the Gx
sessions of the subscriber by using the subscriber's IP address. Then, the
PCRF delivers quota slice and service flow policies to the SCG based on the
subscriber's subscription information.

The PCRF delivers different policies to the SCG and GGSN based
on the quota information reported by the SCG. Below figure shows
the message flow.

Delivering different policies to the SCG and GGSN

UE

GGSN

SCG

PCRF

SCG detects that the quota

slice is used up
1.CCR-U(Usage_Report)
PCRF matches a new Qos rule
base on subscription
2.CCA-U(Service Qos,PCN)

3.RAR(Session Qos)

4.RAA

5.PDP update request

6.PDP update response

1.

After a subscriber runs out of a quota slice, the SCG sends a CCR-Update
message containing the quota usage to the PCRF.

2.

The PCRF depletes the quota and checks whether the subscriber has
available quota. If the authorized quota is exhausted, the PCRF updates
policies based on service configuration and sends a CCA-Update message to
the SCG.

3.

The PCRF generates new bandwidth and sends an RAR-Update message to

the GGSN.

4.

The GGSN installs the authorized rules and sends an RAA-Update message
to the PCRF.

5.

The GGSN sends PDP update request to UE.

6.

The UE responses PDP update request to GGSN.

After receiving a CCR-Termination message from the GGSN, the

PCRF sends a CCA-Termination message to the GGSN. Below
figure shows the message flow.

Notifying the SCG to terminate a Gx session after receiving a CCR-Termination message from the
GGSN

UE

GGSN

SCG

PCRF

1.PDP Termination request

2.CCR-T(SessionID)

3.CCA-T
4.PDP Termination reponse
Account stop request
Account stop response
5.CCR-T(SessionID)

6.CCA-T

1.

The UE sends an IP-CAN Termination Request message to the GGSN.

2.

The GGSN sends a CCR-Termination message to the PCRF.

3.

The PCRF releases the session with the GGSN and sends a
CCA-Termination message to the GGSN.

4.

The GGSN releases the bearer allocated to the subscriber.

5.

The SCG sends a CCR-Termination message to the PCRF.

6.

The PCRF releases the session with the SCG and sends a CCA-Termination
message to the SCG.

When the time range change or the quota reset, the PCRF sends
RAR message both to the GGSN and SCG. Below figure shows the
message flow.

Notifying the SCG and GGSN to update policy

UE

GGSN

SCG

PCRF

1.RAR(Session Bandwidth)

2.RAA
3.PDP update request
4.PDP update response

5.RAR(Service Qos,PCN)

6.RAA

1.

When the time range change, status of subscriber change or the quota reset,
The PCRF generates new session bandwidth and sends an RAR-Update
message to the GGSN.

2.

The GGSN sends a RAA message to the PCRF.

3.

The GGSN sends a PDP update request to UE.

4.

The UE sends a PDP update response to GGSN.

5.

The PCRF generates new service QoS parameters and rules and sends an
RAR-Update message to the SCG.

6.

The SCG sends a RAA message to the PCRF.

When the subscriber is removed or frozen on PCRF, the PCRF

should notify GGSN and SCG to release the PDP session. Below
figure shows the message flow.

Notifying the SCG and GGSN to release session

UE

GGSN

SCG

PCRF

1.RAR(Session release)

2.RAA(Session release)

3.Remove the IPCAN session

request
4.Remove the IPCAN session
response
5.CCR-T
6.CCA-T
Account stop request
Account stop response
7.CCR-T
8.CCA-T

1.

When the subscriber is removed or frozen on PCRF, the PCRF

should send RAR message to GGSN to release the PDP session.

2.

The GGSN sends a RAA message to the PCRF.

3.

The GGSN releases the bearer allocated to the subscriber.

4.

The UE sends the IPCAN session release response to GGSN.

5.

The GGSN sends a CCR-Termination message to the PCRF.

6.

The PCRF releases the session with the GGSN and sends a
CCA-Termination message to the GGSN.

7.

The SCG sends a CCR-Termination message to the PCRF.

8.

The PCRF releases the session with the SCG and sends a
CCA-Termination message to the SCG.

In currently network architecture, PCRF already integrated with SCG for

implementing the policy control. And in next phase, the PCRF should
integrate with GGSN in current phase. Since GGSN just only control the
session QoS for the subscriber in the network architecture, PCRF no
need to deliver the FUP policy to GGSN but deliver a default predefined
rule and session QoS to GGSN for the PDP session establishment.
Below table shows the main parameters send from PCRF to SCG and
GGSN in CCA message when PDP session establishes sort by business
case:
Event Trigger

Session QoS

Policy

Business Case

comment
GGSN

SCG

GGSN

SCG

GGSN

SCG
service

Chose your own

Usage_reoport

Usage_reoport

policy/quota

N/A

plan
slice
service
PAYG

Usage_reoport

Usage_reoport

policy/quota

N/A

slice
service
Bundles(Base on
Usage_reoport

Usage_reoport

policy/quota

N/A

Volume)
slice
service
Service

based
Usage_reoport

Usage_reoport

policy/quota

N/A

Package
slice
service
Location

based
Usage_reoport

Usage_reoport

policy/quota

N/A

Package
slice
Default
Session
URL

based

service
N/A

Usage_reoport

Usage_reoport

Package

predefine

QoS

policy/quota

N/A

rule
slice

Parent

&

with

Child
speed

service
Usage_reoport

Usage_reoport

package

policy/quota

N/A

slice
service

Bundles(Base on
Usage_reoport

Usage_reoport

policy/quota

N/A

Duration)
slice
service
Advanced

bill
Usage_reoport

Usage_reoport

policy/quota

N/A

shock prevention
slice
service
Homezone
Usage_reoport

Usage_reoport

policy/quota

N/A

Package
slice
Terminal

Based

service
N/A

Package

N/A

N/A
policy

service
FUP

Usage_reoport

Usage_reoport

policy/quota

N/A

slice
service
Add-on Package

Usage_reoport

Usage_reoport

policy/quota

N/A

slice
Roaming

service
PLMN_CHANGE

PLMN_CHANGE

Package

N/A
policy
service

BOD

Usage_reoport

Usage_reoport

policy/quota

N/A

slice
service
Roll Over

Usage_reoport

Usage_reoport

policy/quota

N/A

slice
service
Multi Devie-A

N/A

N/A

N/A
policy
service

Multi Device-B

Usage_reoport

Usage_reoport

policy/quota

N/A

slice
service
Application-Based
Usage_reoport

Usage_reoport

policy/quota

N/A

Package
slice

Impact
None.

1.

Restriction
To fulfill E2E bandwidth control function, RAN/NodeB have to open the feature of QoS
control function and interact with GGSN to execute the QoS control.

2.

Since PCRF will establish Gx session with multiple PCEFs, and deliver different policies
to different PCEFs such as GGSN and SCG based on policy configuration, PCRF will
have to open multi-PCEF feature.

3.

While the subscriber may purchase more than one bundle and each bundle defined its
own session bandwidth, PCRF can only deliver the session bandwidth of the bundle
which has the highest priority. Hence, the priority of bundle should be defined base on
bandwidth on PCRF.

4.

The QoS mode of services defined in PCRF should be Replace.

5.

The QoS deliver from PCRF cannot higher than the HLR.

Dependency
PCRF will not response the error code to GGSN and SCG when the subscribers do
not exist in PCRF.

VIP QoS control

1.1.2

Definition
VIP (Very Important Person) means valuable user of carrier.
QoS is sometimes used as a quality measure, it got many alternative definitions,
and here quality of service refers to the level of quality of data service. In currently
phase, the VIP QoS control will only include the maximum bandwidth and ARP.
VIP QoS control will identify valuable users and provide them better transiting
priority in best-effort GPRS network. In this scenarios, GGSN will play as SCG
function which will transfer QoS Parameter to wireless network(RAN/NodeB) to
execute E2E QoS control.
Data Package example:
Package

Package description

VIP

Free allowance: N/A

Tariff
N/A

Qos:
MBRUL=2Mbps,MBRDL=4Mbps,ARP=1
Validity duration: 1 month

Below table shows the function and dependency of currently ME.

ME

Function

Dependency

GGSN

1. Exchange the session QoS attributes

with PCRF.

Support the QoS negotiation and

QoS Update.

2. Detect and report the event trigger

except Usage_Report to PCRF.
RNC/NodeB

Implement the session QoS control.

Configure the mapping ship

between ARP and subscriber.
Configure the priority of THP
Class.
Configure the schedule prority
mapping ship.
Configure the SPI weight for SPI.
Set the value of switch
URRCTRLSWITCH to 1.
Below License should be actived
in RNC site:
WRFD-020806 Differentiated
Service Based on SPI Weight
WRFD-01061103 Scheduling
based on EPF and GBR
WRFD-010638 Dynamic CE
Resource Management
WRFD-050408 Overbooking on IP
Transmission
WRFD-010637 HSUPA Iub Flow
Control
WRFD-010505 Queuing and

ME

Function

Dependency
Preemption

SCG

1. Implement the service QoS control.

N/A

2. Accumulate the quota usage and

report to PCRF.
PCRF

1. Deliver the session QoS parment to

GGSN.

N/A

2. Deliver the service policy and quota

slice to SCG.
3. Update the session QoS base on the
usage of session bundle.

Implementation
The following figure shows the service flow when the subscriber purchase
a new VIP bundle.

UE

GGSN

SCG

PCRF

CRM/Provis

1.Update VIP
subscriber request
2.Update VIP
subscriber response
3.PDP Connection request
4.CCR-I(MSISDN)
PCRF deliver Qos parameters
and predefine rule to GGSN
5.CCA-I(MBRUL,MBRDL,ARP,
Predefine rule)
6.PDP Connection reponse
7. Account start request
8. Account start response
9. CCR-I(MSISDN)
PCRF correlates the Gx session established for the same subscriber
by using the subscribers IP and delivers service flow policies
10. CCA-I(Service Qos,PCN)

1.

CRM/Provisioning identifies who is the VIP users, and then update the
category of subscriber to VIP in PCRF.

2.

The PCRF response successful to the CRM/Provisioning.

3.

The user equipment (UE) of a subscriber sends an IP-CAN Establish request

message to GGSN.

4.

The GGSN sends a CCR-Initial message to the PCRF over the Gx interface to
request the session setup.

5.

The PCRF queries the subscriber's subscription information based on the

subscriber ID contained in the CCR-Initial message. It sends a CCA-Initial
message containing the subscriber's authorized QoS(include
MBRUL/MBRDL/ARP) and predefine rule to the GGSN.

6.

The GGSN installs the authorized rules and sends an IP-CAN Establish
Response message to the UE.

7.

GGSN sends Account-Start-Request to SCG.

8.

The SCG responses GGSN Account-Start-Response to GGSN.

9.

After the subscriber starts using the data service, the SCG retrieves the IP
address from the data flow and sends a CCR-Initial message to the PCRF.

10. The PCRF establishes a Gx session with the SCG and correlates the Gx
sessions of the subscriber by using the subscriber's IP address. Then, the
PCRF delivers service flow policies to the SCG based on the subscriber's
subscription information.

Impact

VIP will occupy more resource than common subscriber, so the VIP subscriber should be
limited to a certain count according to the network capacity, otherwise, it will cause more users
inaccessible when cell is congested.

Restriction

1. Since the VIP subscribers will have high speed at all traffic, the VIP policy and non-VIP
policy should define in all the currently and future bundles.
2. The CRM should identify the VIP subscribers and update the category of subscriber in
PCRF.
3. Since the limited resource of wire radio network, the bandwidth of the VIP subscribers may
not reach the MBRUL/MBRDL when cell is congested.
.
4. The QoS defined in PCRF cannot higher than the HLR.