You are on page 1of 18

GSMNA – “RCS over LTE using Diameter-

based Policy Control”

Document Number NAIREG Doc59 _0x


Meeting Date 22 January 2013
Meeting Venue St. Petersburg, FL
For Approval
For Information x
Version 1.0
Security Classification GSMA Full, Associate,
Rapporteur and Parent Group
Members

Confidential Information
© GSMA 2010
All GSMA meetings are conducted in full compliance with the GSMA’s anti-trust compliance policy
RCS over LTE

 RCS
– Offers a set of enriched multimedia services
– Is access network independent
– Interfaces are standardized
– Uses several protocols
– Supports service-based roaming and interconnect

 LTE
– Supports any Internet service or application
– Interworks with 2G/3G and non-3GPP networks
– Interfaces are standardized
– Uses several protocols
– Supports access-based roaming and interconnect

RCS & LTE complement each other perfectly!

Confidential 2
Benefits of RCS over LTE

Factor Benefit
• Higher peak data rates • Higher QoE
• Lower latency
• Higher spectral efficiency
• Service-independent access • Seamless integration of RCS, or any
network other Internet services
• Easy addition to the RCS suite in
future
• Differentiated service offering • Higher QoE
• Subscriber-based • More battery life
• Service-based • Optimized network resource usage
• Address OTT competition
• Centralized Policy & Charging • Ease of service provisioning
Control (PCC) framework • Differentiated service offering

Confidential 3
Reference Network Architecture for PCC
in EPS

Confidential 4
Use Case: PCC in an IMS Voice Call
(An RCS Scenario)

Confidential 5
Summary of PCC Information Flow

* Off-path model
Confidential 6
Message Flow… ‘Before’ the IMS Voice
Call Initiation

AF
UE DRA PCRF
(P-CSCF)

1. SIP REGISTER
2. SIP REGISTER

3. 200 OK
4. 200 OK
5. Diameter AAR

6. Diameter AAR
Session Binding
7. Diameter AAA

8. Diameter AAA

PCC/QoS Rules Provisioning

Bearer-level Event Subscription

Confidential 7
Message Flow… ‘During’ the IMS Voice
Call

AF
UE DRA PCRF
(P-CSCF)

1. SIP INVITE w/ SDP


2. SIP INVITE w/ SDP

3. 200 OK w/ SDP

4. Diameter AAR

5. Diameter AAR
Session Information Storage & Identification of IP-CAN Session

6. Diameter AAA

7. Diameter AAA

8. 200 OK w/ SDP

Confidential 8
Message Flow… ‘During’ the IMS Voice
Call (contd…)

AF
UE PCEF DRA PCRF
(P-CSCF)

Policy Decision

9. Diameter RAR

10. Diameter RAR

11. Diameter RAA

12. Diameter RAA


Bearer Binding

Activation/Modification of Bearer

Uplink IP Flow to
Bearer Mapping

Service Data Flow Detection


Confidential 9
PCC Architecture for Roaming Scenario

Confidential 10
PCRF Session Binding

Diameter Policy Control Interface Messages on Interface


Gx CCR/CCA, RAR/RAA
Gxx CCR/CCA, RAR/RAA
Rx AAR/AAA, RAR/RAA, STR/STA, ASR/ASA
S9 CCR/CCA, RAR/RAA, TER/TEA

Combination of Framed-IP-Address & Called-Station-Id AVPs

Session Binding PCRF Counter Timer Id Gx Session Gxx Session Rx Session S9 Session
Id

172.20.1.22 ims pcrf-a 2 7 1 1 0 0

10.1.4.12 internet pcrf-c 4 13 1 1 1 1

Session-Id AVP

Diameter Session Id Session Binding Id

pcef.diametriq.com;109236754;2300 10.1.4.12 internet

Confidential 11
Example of a QoS Parameter Mapping at the AF (P-CSCF) for the
Diameter Rx interface

SIP SDP  DIAMETER AVP

Confidential 12
Diameter AAR ABNF

<AA-Request> ::= < Diameter Header: 265, REQ, PXY >


< Session-Id >
{ Auth-Application-Id } Let’s pick the
{ Origin-Host }
Max-Requested-Bandwidth-DL AVP
{ Origin-Realm }
{ Destination-Realm } within this AVP
[ Destination-Host ]
[ AF-Application-Identifier ]
*[ Media-Component-Description ]
[ Service-Info-Status ]
[ AF-Charging-Identifier ]
[ SIP-Forking-Indication ]
*[ Specific-Action ]
*[ Subscription-Id ]
*[ Supported-Features ]
[ Reservation-Priority ]
[ Framed-IP-Address ]
[ Framed-IPv6-Prefix ]
[ Called-Station-Id ]
[ Service-URN ]
[ Sponsored-Connectivity-Data ]
[ MPS-Identifier ]
[ Rx-Request-Type ]
[ Origin-State-Id ]
*[ Proxy-Info ]
*[ Route-Record ]
*[ AVP ]

Confidential 13
SIP SDP

Sent by the UE in INVITE

v=0
o=ecsreid 3262464321 3262464325 IN IP6
2001:0646:00F1:0045:02D0:59FF:FE14:F33A
s=MM02
i=One unidirectional audio media consisting of two media IP flows described by one
media component
t=3262377600 3262809600
m=audio 50330/2 RTP/AVP 0
c=IN IP6 2001:0646:00F1:0045:02D0:59FF:FE14:F33A
a=recvonly

Confidential 14
Conversion Algorithm
Max-Requested-Bandwidth-DL IF <SDP direction> = UE originated (NOTE 8) THEN
IF Transport in m-line is "TCP" or " TCP/MSRP" THEN (NOTE 9)
IF a=recvonly or a=sendrecv or no direction attribute THEN
IF b=AS:<bandwidth> is present and b=TIAS:<TIbandwidth> is not
Present or is present but not supported THEN
Max-Requested-Bandwidth-DL:= <bandwidth> * 1000; /* Unit bit/s
IF b=TIAS:<TIbandwidth> is present and supported THEN
Max-Requested-Bandwidth-DL:= <Transport-dependant bandwidth>/*
Unit bit/s (see NOTE 11) OR Operator specific setting ELSE
Max-Requested-Bandwidth-DL:= <Operator specific setting>;
ENDIF;
ELSE
Max-Requested-Bandwidth-DL:= <Operator specific setting>, (NOTE 10)
ENDIF;
ELSE /* UDP or RTP/AVP transport
IF b=AS:<bandwidth> is present and b=TIAS:<TIbandwidth> is not
present THEN
Max-Requested-Bandwidth-DL:= <bandwidth> * 1000; /* Unit is bit/s
ELSE
IF b=TIAS:<TIbandwidth> is present THEN
Max-Requested-Bandwidth-DL:= <Transport-dependent bandwidth>
(NOTE 11) /* Unit bit/s
ELSE
Max-Requested-Bandwidth-DL:= <Operator specific setting>,
or AVP not supplied;
ENDIF;
ENDIF;
ENDIF
ELSE
Consider SDP in opposite direction
ENDIF

Confidential 15
Advantages of DRA/DEA

 Enhanced Routing & Load Balancing


 Application Enablement
 Centralized Diameter Message Flow Monitoring
 Interoperability
 Security

Confidential 16
References

 Diametriq™ Artifacts

 3GPP TS 29.213: "Policy and charging control signalling flows and


Quality of Service (QoS) parameter mapping“

 3GPP TS 29.214: "Policy and Charging Control over Rx reference


point"

Confidential 17
Thank You

Diametriq™

Confidential Information
© GSMA 2010
All GSMA meetings are conducted in full compliance with the GSMA’s anti-trust compliance policy

You might also like