Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 29.215  Word version:  16.0.0

Top   Top   None   None   Next
1…   4…   A…

 

1  ScopeWord‑p. 9

The present document provides the Stage 3 specification of the S9 reference point for the present release. The functional requirements of Stage 2 specification for the S9 reference point are contained in TS 23.203. The S9 reference point lies between the PCRF in the home PLMN (also known as H-PCRF) and the PCRF in the visited PLMN (also known as V-PCRF).
Whenever it is possible the present document specifies the requirements for the protocols by reference to specifications produced by the IETF within the scope of Diameter. Where this is not possible extensions to Diameter are defined within the present document.
Up

2  References

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
  • References are either specific (identified by date of publication, edition number, version number, etc.) or non specific.
  • For a specific reference, subsequent revisions do not apply.
  • For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
TS 23.203: "Policy and Charging Control Architecture"
[3]
TS 29.212: "Policy and Charging Control (PCC); Reference points".
[4]
TS 29.213: "Policy and charging control signalling flows and Quality of Service (QoS) parameter mapping"
[5]
TS 29.214: "Policy and charging control over Rx reference point"
[6]  Void.
[7]
TS 29.229: "Cx and Dx interfaces based on the Diameter protocol; Protocol details"
[8]
RFC 4960:  "Stream Control Transmission Protocol".
[9]
3GPP TS23.003: "Numbering, addressing and identification".
[10]
TS 23.261: "IP flow mobility and seamless Wireless Local Area Network (WLAN) offload; Stage 2".
[11]  Void.
[12]  Void.
[13]
TS 23.216: "Single Radio Voice Call Continuity (SRVCC); Stage 2".
[14]
Broadband Forum TR-203: "Interworking between Next Generation Fixed and 3GPP Wireless Access".
[15]
Broadband Forum TR-134: "Policy Control Framework".
[16]
Broadband Forum TR-146: "Subscriber Sessions".
[17]
DSL Forum TR-059: "DSL Evolution - Architecture. Requirements for the Support of QoS-Enabled IP Services", September 2003
[18]
TS 23.402: "Architecture Enhancements for non-3GPP accesses".
[19]
RFC 4006:  "Diameter Credit Control Application".
[20]
TS 23.007: "Restoration Procedures".
[21]  Void.
[22]
TS 29.274: "3GPP Evolved Packet System. Evolved GPRS Tunnelling Protocol for EPS (GTPv2)".
[23]
3GPP2 X.S0057-B: "E-UTRAN - eHRPD Connectivity and Interworking: Core Network Aspects".
[24]
RFC 7683:  "Diameter Overload Indication Conveyance".
[25]
RFC 4005:  "Diameter Network Access Server Application".
[26]
TS 23.161: "Network-based IP flow mobility and Wireless Local Area Network (WLAN) offload; Stage 2".
[27]
RFC 7944:  "Diameter Routing Message Priority".
[28]
RFC 8583:  "Diameter Load Information Conveyance".
[29]
RFC 6733:  "Diameter Base Protocol".
Up

3  Definitions and abbreviationsWord‑p. 10

3.1  Definitions

For the purposes of the present document, the terms and definitions given in TR 21.905 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.
Home Routed Access:
Roaming scenario where the PCEF is located in the HPLMN. In a Home Routed roaming scenario, the UE obtains access to the packet data network from the HPLMN.
IP-CAN session:
association between a UE and an IP network. The association is identified by one or more UE IPv4 addresses/ and/or IPv6 prefix together with a UE identity information, if available, and a PDN represented by a PDN ID (e.g. an APN). An IP-CAN session incorporates one or more IP-CAN bearers. Support for multiple IP-CAN bearers per IP-CAN session is IP-CAN specific. An IP-CAN session exists as long as the related UE IPv4 address and/or IPv6 prefix are assigned and announced to the IP network.
Visited Access (also known as local breakout):
Roaming scenario where the PCEF is located in the VPLMN. In a Visited Access Roaming scenario, the UE obtains access to the packet data network from the VPLMN.
Up

3.2  Abbreviations

For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.
ADC
Application Detection and Control
AF
Application Function
AN-Gateway
Access Network Gateway
AVP
Attribute-Value Pair
BBERF
Bearer Binding and Event Reporting Function
DRMP
Diameter Routing Message Priority
H-AF
Home AF
H-PCRF
Home PCRF
HPLMN
Home PLMN
HR
Home-Routed
HRPD
High Rate Packet Data
HSGW
HRPD Serving Gateway
NBIFOM
Network-based IP flow mobility
OCS
Online charging system
OFCS
Offline charging system
PCC
Policy and Charging Control
PCEF
Policy and Charging Enforcement Function
PCRF
Policy and Charging Rule Function
RCAF
RAN Congestion Awareness Function
S-GW
Serving Gateway
TDF
Traffic Detection Function
TSSF
Traffic Steering Support Function
UDC
User Data Convergence
UDR
User Data Repository
VA
Visited Access
V-AF
Visited AF
V-PCRF
Visited PCRF
VPLMN
Visited PLMN
Up

Up   Top   ToC