end to end bandwidth control and vip qos control frs for ufone v1.0.docx

8/10/2019 End to End bandwidth control and VIP Qos control FRS for Ufone v1.0.docx

1/14

1.1.1 End to End Bandwidth Control

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 tomultiple 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 differentPCEFs based on policy configuration.

Correlate Gx sessions of a subscriber by using the subscriber's IP address or thecombination of the subscriber's IP address and access point name (APN), anddeliver updated policies to other correlated PCEFs based on status changesreported 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 updatessession-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 attributeswith PCRF.

2. Detect and report the event triggerexcept Usage_Report to PCRF.

Support the QoS negotiation andQoS Update.

RNC/NodeB Implement the session QoS control. Configure the mapping shipbetween ARP and subscriber.

Configure the priority of THPClass.

Configure the schedule prority


2/14


mapping ship.

Configure the SPI weight for SPI.

Set the value of switch

URRCTRLSWITCH to 1. Below License should be activedin RNC site:

WRFD-020806 DifferentiatedService Based on SPI Weight

WRFD-01061103 Schedulingbased on EPF and GBR

WRFD-010638 Dynamic CEResource Management

WRFD-050408 Overbooking on IPTransmission

WRFD-010637 HSUPA Iub FlowControl

WRFD-010505 Queuing andPreemption

SCG 1. Implement the service QoS control.

2. Accumulate the quota usage andreport to PCRF.

N/A

PCRF 1. Deliver the session QoS parment toGGSN.

2. Deliver the service policy and quotaslice to SCG.

3. Update the session QoS base on theusage of session bundle.

N/A

Implementation

The following figure describes the end to end service flow that UEinitial PDP connection.

End to End service flow of PDP connection


3/14

UE SCG PCRFGGSN

1.Attach request

7.CCR-I(MSISDN,QoS-Upgrade, QoS-Negotiation,Qos)

12. CCR-I(MSISDN)

9.CCA-I(Session QoS, Predefine rule)

13. CCA-I(Service Qos,PCN)

10.Create PDP context response(Qos)

8. Account startrequest

11. Account startresponse

NODEB HLR RNC SGSN

2.Update location

3. Insert subscriber data(QoS)

4. Attach accept

5. Active PDP context request

6. Create PDP context request(Qos)

14.Radius access bearer assignment

Request(QoS)

17.Radius access bearer assignment

response

15.Radio link reconfiguration prepare(QoS)

16.Radio link reconfigurationready

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 torequest the session setup. In the CCR-I message, the QoS-Negotiation andQoS-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-Initialmessage containing the subscriber's authorized QoS and rules to the GGSN.

10. The GGSN installs the authorized rules and send the PDP attach responsewith 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 Gxsessions of the subscriber by using the subscriber's IP address. Then, thePCRF delivers quota slice and service flow policies to the SCG based on thesubscriber's subscription information.


4/14


5/14

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 newRAT 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) tothe GGSN.

13. The SCG sends CCR-U message to the PCRF with RAT-type-change eventtrigger 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-basedpolicy control when the PCRF connects to the GGSN and SCG .

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

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


6/14

UE SCG PCRFGGSN

1.PDP Connection request

2.CCR-I(MSISDN,QoS-Upgrade, QoS-Negotiation)

7. CCR-I(MSISDN)

3.CCA-I(Sess ion bandwidth, Predefine rule)

8. CCA-I(Service Qos,PCN,Quota slice)

4.PDP Connection reponse

PCRF deliver Qos parametersand predefine rule to GGSN

PCRF correlates the Gx session established for the same subscriber by using the subsc riber s IP and delivers service flow policies

5. Account start request

6. Account start response

1. The user equipment (UE) of a subscriber sends an IP-CAN Establish Requestmessage.

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

3. The PCRF queries the subscriber's subscription information based on thesubscriber 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 EstablishResponse 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


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

The PCRF delivers different policies to the SCG and GGSN basedon the quota information reported by the SCG. Below figure showsthe message flow.


7/14

Delivering different policies to the SCG and GGSN

UE SCG PCRFGGSN

1.CCR-U(Usage_Report)

4.RAA

3.RAR(Session Qos)

2.CCA-U(Service Qos,PCN)

PCRF matches a new Qos rule base on subscription

SCG detects that the quotaslice is used up

5.PDP update request

6.PDP update response

1. After a subscriber runs out of a quota slice, the SCG sends a CCR-Updatemessage 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 updatespolicies based on service configuration and sends a CCA-Update message tothe SCG.

3. The PCRF generates new bandwidth and sends an RAR-Update message tothe GGSN.

4. The GGSN installs the authorized rules and sends an RAA-Update messageto 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, thePCRF sends a CCA-Termination message to the GGSN. Belowfigure shows the message flow.

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

GGSN


8/14

UE SCG PCRFGGSN

1.PDP Termination request

2.CCR-T(SessionID)

5.CCR-T(SessionID)

3.CCA-T

6.CCA-T

4.PDP Termination reponse

Account stop request

Account stop response

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 aCCA-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-Terminationmessage to the SCG.

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

Notifying the SCG and GGSN to update policy

UE SCG PCRFGGSN

2.RAA

6.RAA

1.RAR(Session Bandwidth)

5.RAR(Service Qos,PCN)

3.PDP update request

4.PDP update response


9/14

1. When the time range change, status of subscriber change or the quota reset,The PCRF generates new session bandwidth and sends an RAR-Updatemessage 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 PCRFshould notify GGSN and SCG to release the PDP session. Belowfigure shows the message flow.

Notifying the SCG and GGSN to release session

UE SCG PCRFGGSN

2.RAA(Session release)

1.RAR(Session release)

3.Remove the IPCAN sessionrequest

4.Remove the IPCAN sessionresponse

5.CCR-T

6.CCA-T

7.CCR-T

8.CCA-T

Account stop request

Account stop response

1. When the subscriber is removed or frozen on PCRF, the PCRFshould 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.


10/14

In currently network architecture, PCRF already integrated with SCG forimplementing the policy control. And in next phase, the PCRF shouldintegrate with GGSN in current phase. Since GGSN just only control thesession QoS for the subscriber in the network architecture, PCRF no

need to deliver the FUP policy to GGSN but deliver a default predefinedrule and session QoS to GGSN for the PDP session establishment.Below table shows the main parameters send from PCRF to SCG andGGSN in CCA message when PDP session establishes sort by businesscase:

Business CaseEvent Trigger Session QoS Policy

commentGGSN SCG GGSN SCG GGSN SCG

Chose your own

planUsage_reoport Usage_reoport

Session

QoSN/A

Default

predefine

rule

service

policy/quota

slice

N/A

PAYG Usage_reoport Usage_reoportservicepolicy/quota

slice

N/A

Bundles(Base on

Volume)Usage_reoport Usage_reoport

service

policy/quota

slice

N/A

Service based

PackageUsage_reoport Usage_reoport

service

policy/quota

slice

N/A

Location based


service

policy/quota

slice

N/A

URL based


service

policy/quota

slice

N/A

Parent & Child

with speed

package

Usage_reoport Usage_reoport

service

policy/quota

slice

N/A

Bundles(Base onDuration)

Usage_reoport Usage_reoport

service

policy/quota

slice

N/A

Advanced bill

shock preventionUsage_reoport Usage_reoport

service

policy/quota

slice

N/A

Homezone


service

policy/quota

slice

N/A

Terminal Based

PackageN/A N/A

service

policyN/A


11/14

FUP Usage_reoport Usage_reoport

service

policy/quota

slice

N/A

Add-on Package Usage_reoport Usage_reoport

service

policy/quota

slice

N/A

Roaming

PackagePLMN_CHANGE PLMN_CHANGE

service

policyN/A

BOD Usage_reoport Usage_reoport

service

policy/quota

slice

N/A

Roll Over Usage_reoport Usage_reoport

service

policy/quota

slice

N/A

Multi Devie-A N/A N/Aservice

policyN/A

Multi Device-B Usage_reoport Usage_reoport

service

policy/quota

slice

N/A

Application-Based


service

policy/quota

slice

N/A

Impact

None.

Restriction

1. 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 P CRF 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 donot exist in PCRF.


12/14

1.1.2 VIP QoS control

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 Tariff

VIP Free allowance: N/A

Qos:MBRUL=2Mbps,MBRDL=4Mbps,ARP=1

Validity duration: 1 month

N/A

Below table shows the function and dependency of currently ME.


GGSN 1. Exchange the session QoS attributeswith PCRF.

2. Detect and report the event trigger

except Usage_Report to PCRF.

Support the QoS negotiation andQoS Update.

RNC/NodeB Implement the session QoS control. Configure the mapping shipbetween ARP and subscriber.

Configure the priority of THPClass.

Configure the schedule proritymapping ship.

Configure the SPI weight for SPI.

Set the value of switchURRCTRLSWITCH to 1.

Below License should be activedin RNC site:

WRFD-020806 DifferentiatedService Based on SPI Weight

WRFD-01061103 Schedulingbased on EPF and GBR

WRFD-010638 Dynamic CEResource Management

WRFD-050408 Overbooking on IPTransmission

WRFD-010637 HSUPA Iub FlowControl

WRFD-010505 Queuing and


13/14


Preemption

SCG 1. Implement the service QoS control.

2. Accumulate the quota usage and

report to PCRF.

N/A

PCRF 1. Deliver the session QoS parment toGGSN.

2. Deliver the service policy and quotaslice to SCG.

3. Update the session QoS base on theusage of session bundle.

N/A

Implementation

The following figure shows the service flow when the subscriber purchasea new VIP bundle.

UE SCG PCRFGGSN CRM/Provis

1.Update VIPsubscriber request

2.Update VIPsubscriber response

3.PDP Connection request

4.CCR-I(MSISDN)

9. CCR-I(MSISDN)

5.CCA-I(MBRUL,MBRDL,ARP,Predefine rule)

10. CCA-I(Service Qos,PCN)

6.PDP Connection reponse

PCRF deliver Qos parametersand predefine rule to GGSN

PCRF correlates the Gx session established for the same subscriber by using the subscriber s IP and delivers service flow policies

7. Account start request

8. Account start response

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.


14/14

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 EstablishResponse 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


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.

end to end bandwidth control and vip qos control frs for ufone v1.0.docx

Documents