SIST ES 282 003 V3.4.1:2009

• Abstract:

  The present document describes the functional architecture of the Resource and Admission Control Sub-System (RACS), for TISPAN NGN Release 3, in line with the service requirements described in TS 181 005 [1], in line with the QoS Requirements described in TS 181 018 [13] and its role in the TISPAN NGN architecture as defined in ES 282 001 [2]. It specifies as well high level stage 2 requirements that are also considered when describing its functional operation.

• Status: Published
• Publication Date: 08-Oct-2009
• ICS: 33.040.01 - Telecommunication systems in general
• ICS: 33.080 - Integrated Services Digital Network (ISDN)
• Technical Committee: SPN - Services and Protocols for Networks
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 02-Oct-2009
• Due Date: 07-Dec-2009
• Completion Date: 09-Oct-2009
• Ref Project: ETSI ES 282 003 V3.4.1 (2009-09) - Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control Sub-System (RACS): Functional Architecture

SIST ES 282 003 V3.4.1:2009 is the Slovenian standard based on ETSI ES 282 003 Version 3.4.1. It specifies the functional architecture of the Resource and Admission Control Sub-System (RACS) for TISPAN NGN Release 3, including how applications, policy functions and transport functions exchange requests, reservations and traffic policies. It is meant for engineers and operators who need to design, implement or evaluate NGN admission control, QoS handling and policy enforcement.

What does SIST ES 282 003 V3.4.1:2009 specify?

SIST ES 282 003 V3.4.1:2009 describes the functional architecture of RACS and its role in the TISPAN NGN architecture. The scope ties the architecture to service requirements in TS 181 005, QoS requirements in TS 181 018, and the NGN functional architecture in ES 282 001, and it also states that the document includes high-level stage 2 requirements that guide functional operation.

The document is organized into:

• Clause 1 Scope
• Clause 2 References
• Clause 3 Definitions and abbreviations
• Clause 4 General description of RACS
• Clause 5 Derivation basis for the RACS architecture
• Clause 6 Functional architecture definition and interactions
• Annexes B to I, covering policy terminology, examples, scenarios, topology and resource management, multicast support, information flows, session modification and change history

Annex	What it covers
B	Policy terminology and policy types
C	Example of connection oriented network handling in the aggregation segment
D	Network deployment scenarios
E	Topology and resource management use cases, elementary functions and architectural models
F	Architectural scenarios for supporting unicast and multicast
G	Information flows for supporting unicast and multicast
H	Session initiation and session modification examples
I	Change history

What are the key requirements of SIST ES 282 003 V3.4.1:2009?

Service control, authorization and priority

Clause 4.2.1.2 requires RACS to offer services to Application Functions (AFs), even when they are in different administrative domains. It also says RACS shall be able to authenticate and authorize the AF, and set bearer or transport functions with network-level attributes that match the service request, such as bandwidth and QoS.

This matters because RACS is not just a routing aid - it is the decision point that checks whether an application is allowed to use network resources and with what service class. Clause 4.2.1.2 also states that RACS shall support at least eight priority types, which is important when the operator needs to treat calls or media flows differently under congestion.

Resource reservation, release and modification

Clause 4.2.1.3 requires both soft-state and hard-state resource management, with reservation, removal and modification handled at the level of individual service flows. It also requires explicit removal and explicit modification of previously established reservations.

In practice, this means the standard expects RACS to manage resources per flow, not only per subscriber or session. Clause 6.3.1.1 adds that the Rq reference point supports single-stage, two-stage reserve-commit, and authorize-reserve-commit resource management models, so implementations can support immediate use, staged commit, and policy-controlled service invocation.

QoS control modes and policy installation

Clause 4.2.2.3 and clause 6.2.2.6 define both push and pull QoS control. In push mode, RACS sends traffic policies to the transport functions after receiving a request from an AF or an interconnected RACS entity; in pull mode, transport functions request traffic policies from RACS after a QoS request from user equipment or another transport element.

This is practical because different networks place the control trigger in different places. Clause 5.3 also distinguishes guaranteed QoS and relative QoS, and says relative QoS is handled at the IP_Edge using Differentiated Services concepts, so operators can map the architecture to either strict reservation or differentiated traffic treatment.

Functional roles of the main entities

Clause 6.2 defines the key functional entities: the SPDF, the generic Resource Admission Control Function (x-RACF), the BGF, the RCEF and the AF. The SPDF is the single point of contact for the AF, while x-RACF is specialized as A-RACF in the access network and C-RACF in the core network.

This matters because implementers need to know where decisions are made and where policies are enforced. Clause 6.2.3 says the BGF works on micro-flows and acts as a dynamic gate, while clause 6.2.5 says the AF must provide media flow identification, bandwidth needs, class-based service information and whether BGF, x-RACF, or both are requested.

Reference points and what they carry

Clause 6.3 defines the reference points between those entities. The Rq reference point carries resource requests, modifications, confirmations and unsolicited events between SPDF and x-RACF; the Ia reference point carries BGF service requests, confirmations, audits and state synchronization; the Re reference point carries policy enforcement information between x-RACF and RCEF.

These reference points are the practical interface contract of the architecture. Clause 6.3.5 and clause 6.3.6 define inter-domain and intra-domain SPDF-to-SPDF coordination through Ri' and Rd', while clause 6.3.8 defines the Rr reference point for x-RACF-to-x-RACF coordination, including request and delegated models for sharing or delegating admission control responsibility.

Charging, topology and overload control

Clause 5.2 limits charging support to offline charging and lists the charging-related information that SPDF, A-RACF and AF can provide, including Charging Correlation Information (CCI), request type, requestor and subscriber information, service priority, media description, commit ID, time stamp and reason. The transfer mechanism itself is not standardized in this document.

Clause 4.2.2.6 requires RACS to provide a single point of contact for topology and resource information, and to support both push and pull retrieval, including complete data sets and deltas. Clause 4.2.1.6 requires overload control at both RACS and AF sides, so deployments can protect the control functions as well as the requesting applications.

QoS downgrading and session handling

Clause 5.4 allows QoS downgrading for an existing session without ending it, either in push mode or pull mode. This is the mechanism RACS uses when a new session must be admitted and resources are tight, while keeping an existing session alive at reduced quality.

Clause 6.4 turns the architecture into procedures for attach, request, release, commit, modification, access profile retrieval and abnormal events. For operators and vendors, these procedures show how the abstract architecture behaves during real service setup and change.

What terms does SIST ES 282 003 V3.4.1:2009 define?

• Application Function (AF) - a functional entity that gives applications control over IP bearer resources when needed and exchanges dynamic QoS-related service information with RACS.
• Service Policy Decision Function (SPDF) - the function that gives the AF a single point of contact and makes the final service-based policy decision.
• generic Resource Admission Control Function (x-RACF) - the generic admission control function that accepts or rejects resource requests for transport resources under its control.
• Access-Resource and Admission Control Function (A-RACF) - the x-RACF specialization that operates in the access network.
• Border Gateway Function (BGF) - the functional entity that enforces policy on media flows and can open or close a gate for an admitted flow.
• RACS - the Resource and Admission Control Sub-System that coordinates policy, admission control, resource reservation and traffic policy installation.
• QoS "Pull" model - the model where transport processing functions request traffic policies from RACS after a QoS request is triggered in the network.

Who uses SIST ES 282 003 V3.4.1:2009?

SIST ES 282 003 V3.4.1:2009 is used by NGN architects, access and core network engineers, policy/QoS designers, and vendors of AF, SPDF, x-RACF, RCEF and BGF functions. It is also relevant for operators and integrators planning resource admission control for unicast, multicast, IPTV, or other QoS-sensitive services.

In practice, these users apply it when defining control points, mapping service requests to network resources, selecting push or pull control, and designing policy enforcement and charging interactions.

What changed in SIST ES 282 003 V3.4.1:2009 from the previous edition?

SIST ES 282 003 V3.4.1:2009 is identified as the Slovenian standard identical to ETSI ES 282 003 Version 3.4.1.

Which standards are used with SIST ES 282 003 V3.4.1:2009?

Standard	What it contributes
ETSI TS 181 005	Service and capability requirements that RACS follows
ETSI ES 282 001	NGN functional architecture and the role of RACS
IETF RFC 3312	Segmented resource management model referenced for service-layer support
IETF RFC 2475	Differentiated Services architecture used for relative QoS
IETF RFC 2753	Framework for policy-based admission control
ETSI TS 181 018	QoS requirements for NGN
ETSI TS 187 001	NGN security requirements
ETSI TS 185 005	Service requirements and capabilities for customer networks connected to TISPAN NGN

What does the SIST ES 282 003 V3.4.1:2009 document contain?

Clause 6.3 contains the detailed information elements exchanged on Rq, Ia, Re and Rr, including request, confirmation, modification, release, audit and event notification messages. Clause 6.4 turns those message sets into procedures for push, pull and mixed operation, wholesale and retail cases, commit handling, resource modification, profile retrieval and abnormal events.

The annexes extend the architecture with policy terminology, a connection-oriented example, deployment scenarios, multicast support scenarios and information flows, topology and resource management use cases, and session modification behavior. Annex H is especially practical because it shows how connection status changes between session initiation, acceptance, rejection, modification and release.

Final draft ETSI ES 282 003 V3.4.0 (2009-07)
ETSI Standard
Telecommunications and Internet converged Services and
Protocols for Advanced Networking (TISPAN);
Resource and Admission Control Sub-System (RACS):
Functional Architecture
2 Final draft ETSI ES 282 003 V3.4.0 (2009-07)

Reference
RES/TISPAN-02072-NGN-R3
Keywords
architecture, control, system
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2009.
All rights reserved.
TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
LTE™ is a Trade Mark of ETSI currently being registered
for the benefit of its Members and of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI
3 Final draft ETSI ES 282 003 V3.4.0 (2009-07)
Contents
Intellectual Property Rights . 10
Foreword . 10
1 Scope . 11
2 References . 11
2.1 Normative references . 11
2.2 Informative references . 12
3 Definitions and abbreviations . 12
3.1 Definitions . 12
3.2 Abbreviations . 14
4 General description of RACS . 16
4.1 Functional overview . 16
4.1.1 Global description . 16
4.1.2 Basic functionalitie s . 16
4.1.3 Restrictions applicable to the present document . 17
4.2 Functional Requirements . 17
4.2.1 R1 Requirements . 17
4.2.1.1 Overall . 17
4.2.1.2 Transport Control Service Requests . 17
4.2.1.3 Resource Handling . 18
4.2.1.4 QoS Management . 19
4.2.1.5 Traffic Handling . 19
4.2.1.6 Charging and Overload Control . 20
4.2.2 R2 Requirements . 20
4.2.2.1 Overall . 20
4.2.2.2 Resource Handling . 20
4.2.2.3 QoS Management . 20
4.2.2.4 e2e QoS Handling . 21
4.2.2.5 Multicast/Unicast Handling . 21
4.2.2.6 Topology and Resource Information Retrieval . 21
4.2.2.7 Network Deployment Scenarios . 22
4.2.2.8 Charging and Overload Control . 22
4.2.3 R3 Requirements . 22
4.2.3.1 Interaction with the CPN . 22
4.2.3.1.1 Direct control by RACS . 22
5 RACS functional architecture derivation basis . 22
5.1 Resource Control for Unicast and Multicast . 23
5.1.1 Resource control scenarios . 23
5.1.1.1 Identification of Resources . 23
5.1.1.2 Multicast Resource Admission Decision Specifics . 24
5.1.1.3 Resource Admission Decision Prerequisites . 24
5.1.1.4 Resource Admission Control Approaches . 25
5.1.1.5 Multicast Resource Admission Control in the Access Network Domain Transport Nodes . 25
5.1.1.6 Unicast/Multicast Resource Reuse in the Access Segment . 25
5.2 Charging . 26
5.3 QoS Management Functions in Fixed Access Networks. 26
5.4 Resource Control for QoS Downgrading . 28
6 RACS functional architecture definition . 29
6.1 General . 29
6.2 Functional elements . 31
6.2.1 SPDF . 31
6.2.1.1 SPDF main functions . 31
6.2.1.2 Summary of SPDF Elementary Functions . 31
6.2.1.3 Reference points . 33
ETSI
4 Final draft ETSI ES 282 003 V3.4.0 (2009-07)
6.2.1.4 User profile . 33
6.2.1.5 Priority . 33
6.2.1.6 Service request . 34
6.2.1.7 Coordination function . 34
6.2.1.8 Charging . 35
6.2.1.9 Deployment considerations . 35
6.2.1.10 Overload control . 35
6.2.1.11 Discovery mechanism . 35
6.2.2 Generic Resource Admission Control Function . 35
6.2.2.1 Main functions . 35
6.2.2.1.1 Specializations of x-RACF . 36
6.2.2.1.2 Reference points applicable to different specializations of x-RACF . 36
6.2.2.1.3 Multiple instantiations of x-RACF . 36
6.2.2.2 Summary of generic Resource Admission Control Function Elementary Functions . 37
6.2.2.3 A-RACF . 39
6.2.2.3.1 A-RACF main functions . 39
6.2.2.3.2 Reference points . 39
6.2.2.4 C-RACF . 40
6.2.2.4.1 C-RACF main functions . 40
6.2.2.4.2 Reference points . 40
6.2.2.5 Admission control process . 40
6.2.2.5.1 A-RACF . 40
6.2.2.5.2 C-RACF. 42
6.2.2.6 Installation of policies . 42
6.2.2.7 Charging . 43
6.2.2.8 Abnormal condition handling. 43
6.2.2.9 Deployment considerations . 43
6.2.2.10 Overload control . 43
6.2.2.11 Discovery Mechanism . 43
6.2.3 BGF . 43
6.2.3.1 BGF main functions . 43
6.2.3.2 BGF parameters . 44
6.2.3.3 Reference points . 44
6.2.3.4 Addressing latching . 44
6.2.3.5 Abnormal conditions handling . 44
6.2.3.6 Overload control . 44
6.2.4 RCEF . 45
6.2.4.1 RCEF main functions . 45
6.2.4.2 Reference points . 45
6.2.4.3 RCEF parameters . 45
6.2.5 Application Function (AF) . 45
6.2.5.1 AF main functions . 45
6.2.5.2 Reference points . 46
6.2.5.3 Charging . 47
6.2.5.4 Abnormal conditions handling . 47
6.2.6 BTF . 47
6.3 RACS reference points . 47
6.3.1 Rq reference point (SPDF - x-RACF). 47
6.3.1.1 Functional requirements . 47
6.3.1.1.1 Resource management mechanisms . 47
6.3.1.1.2 Service model . 48
6.3.1.1.3 Duration semantics . 48
6.3.1.1.4 Audit and synchronization support . 49
6.3.1.1.5 Report facilities for unsolicited events . 49
6.3.1.2 Non-functional requirements. 49
6.3.1.2.1 Reliability requirements . 49
6.3.1.2.2 Security requirements . 49
6.3.1.3 Information exchanged over the Rq Reference Point . 49
6.3.1.3.1 Resource Reservation Request . 49
6.3.1.3.2 Resource Modification Request . 51
6.3.1.3.3 Resource Request/Modification Confirmation . 52
6.3.1.3.4 Resource Release Request . 52
ETSI
5 Final draft ETSI ES 282 003 V3.4.0 (2009-07)
6.3.1.3.5 Abort Resource Reservation . 52
6.3.2 e4 reference point (A-RACF - NASS) . 53
6.3.3 Ia Reference Point (SPDF - BGF) . 53
6.3.3.1 Functional Requirements . 53
6.3.3.1.1 Control of NAT, Hosted NAT traversal and Gating . 53
6.3.3.1.2 Transport Protocol Type Policing . 53
6.3.3.1.3 Bandwidth control . 53
6.3.3.1.4 QoS marking . 53
6.3.3.1.5 Usage metering and statistics reporting . 53
6.3.3.1.6 Resource state synchronization . 54
6.3.3.2 Non-Functional Requirements . 54
6.3.3.2.1 Reliability requirements . 54
6.3.3.2.2 Security requirements . 54
6.3.3.3 Information exchanged over the Ia Reference Point . 54
6.3.3.3.1 BGF Service Request . 54
6.3.3.3.2 BGF Service Confirmation . 57
6.3.3.3.3 BGF Service Modify Request . 58
6.3.3.3.4 BGF Service Modify Confirmation . 59
6.3.3.3.5 BGF Service Audit Request . 60
6.3.3.3.6 BGF Service Audit Response . 61
6.3.3.3.7 BGF Service Notify Request . 62
6.3.3.3.8 BGF Service Notify Indication . 63
6.3.3.3.9 BGF Service Release Request . 63
6.3.3.3.10 BGF Service Release Confirmation. 64
6.3.4 Gq' Reference Point (AF - SPDF) . 65
6.3.4.1 Functional Requirements . 65
6.3.4.2 Non-Functional Requirements . 65
6.3.4.3 Information exchanged over the Gq' Reference Point . 65
6.3.5 Ri' Reference Point (SPDF-SPDF inter-domain) . 66
6.3.5.1 Functional Requirements . 66
6.3.5.1.1 Resource management mechanisms . 66
6.3.5.1.2 Service model . 66
6.3.5.1.3 Duration semantics . 66
6.3.5.1.4 Audit and Synchronization support . 67
6.3.5.1.5 Report facilities for unsolicited events . 67
6.3.5.2 Non-Functional Requirements . 67
6.3.5.2.1 Reliability requirements . 67
6.3.5.2.2 Security requirements . 67
6.3.5.3 Information exchanged over the Ri' Reference Point . 67
6.3.6 Rd' Reference Point (SPDF-SPDF intra-domain) . 67
6.3.6.1 Functional Requirements . 67
6.3.6.1.1 Resource management mechanisms . 67
6.3.6.1.2 Service model . 67
6.3.6.1.3 Duration semantics . 68
6.3.6.1.4 Audit and Synchronization support . 68
6.3.6.1.5 Report facilities for unsolicited events . 68
6.3.6.2 Non-Functional Requirements . 68
6.3.6.2.1 Reliability requirements . 68
6.3.6.2.2 Security requirements . 68
6.3.6.3 Information exchanged over the Rd' Reference Point . 68
6.3.7 Re Reference Point (x-RACF - RCEF) . 68
6.3.7.1 Functional Requirements . 68
6.3.7.1.1 Policy Enforcement Management. 68
6.3.7.2 Non-functional requirements. 69
6.3.7.2.1 Reliability requirements . 69
6.3.7.2.2 Security requirements . 69
6.3.7.3 Information exchanged over the Re Reference Point . 70
6.3.7.3.1 Information exchanged by using the push mode . 70
6.3.7.3.1.1 Policy Enforcement Install Request . 70
6.3.7.3.1.2 Policy Enforcement Modification Request . 71
6.3.7.3.1.3 Policy Query Request . 73
6.3.7.3.1.4 Policy Enforcement Installation/Modification Confirmation . 73
ETSI
6 Final draft ETSI ES 282 003 V3.4.0 (2009-07)
6.3.7.3.1.5 Policy Query Confirmation . 74
6.3.7.3.1.6 Policy Enforcement Release Request. 75
6.3.7.3.2 Information exchanged by using the pull mode . 76
6.3.7.3.2.1 Policy Decision Install Request . 76
6.3.7.3.2.2 Policy Decision Modification Request. 77
6.3.7.3.2.3 Policy Decision Deactivation Request . 79
6.3.7.3.2.4 Policy Decision Install Response . 79
6.3.7.3.2.5 Policy Decision Modification Response . 81
6.3.7.3.2.6 Policy Decision Deactivation Response. 82
6.3.7.3.3 Information exchanged by using both QoS mechanisms . 83
6.3.7.3.3.1 Event Subscription Request . 83
6.3.7.3.3.2 Event Notification Indication . 84
6.3.8 Rr Reference Point (x-RACF - x-RACF intra-domain) . 84
6.3.8.1 Functional Requirements . 84
6.3.8.1.1 Overall features . 84
6.3.8.1.2 Resource management mechanisms . 85
6.3.8.1.3 Service model . 86
6.3.8.1.4 Duration semantics . 86
6.3.8.1.5 Audit and Synchronization support . 86
6.3.8.1.6 Report facilities for unsolicited events . 87
6.3.8.2 Non-Functional Requirements . 87
6.3.8.2.1 Reliability requirements . 87
6.3.8.2.2 Security requirements . 87
6.3.8.3 Information exchanged over the Rr Reference Point . 87
6.3.8.3.1 Information exchanged over the Rr Reference Point for request model . 87
6.3.8.3.1.1 Resource Reservation Request . 87
6.3.8.3.1.2 Resource Modification Request . 88
6.3.8.3.1.3 Resource Request/Modification Confirmation . 89
6.3.8.3.1.4 Resource Release Request . 90
6.3.8.3.1.5 Abort Resource Reservation . 90
6.3.8.3.2 Information exchanged over the Rr Reference Point for delegated model . 90
6.3.8.3.2.1 Resource Delegation Request . 90
6.3.8.3.2.2 Resource Delegation Confirmation . 91
6.3.8.3.2.3 Resource Delegation Push . 92
6.3.8.3.2.4 Resource Delegation Push Response . 93
6.3.8.3.2.5 Resource Delegation Query . 93
6.3.8.3.2.6 Resource Delegation Query Response . 94
6.3.9 Rf Reference Point (SPDF-Charging Functions and x-RACF-Charging Functions) . 94
6.4 RACS Flows: Interaction Procedures . 94
6.4.1 Subscriber Attaches to the Access Network . 95
6.4.2 Request Resource . 95
6.4.2.1 Request Resource by using the push mode . 95
6.4.2.1.1 Admission control using push mode when only one x-RACF is involved . 95
6.4.2.1.2 Admission control using push mode when multiple x-RACFs are involved . 97
6.4.2.1.2.1 Use of request bulk resources . 97
6.4.2.1.2.2 Use of Rr request model . 98
6.4.2.2 Request Resource by using the pull mode . 100
6.4.2.2.1 Admission control using pull mode when only one x-RACF is involved . 100
6.4.2.2.2 Admission control using pull mode when multiple x-RACFs are involved . 101
6.4.2.3 Request resource by combining push and pull mode . 102
6.4.3 Request Resource Wholesale/Retail Scenario . 105
6.4.3.1 Request Resource with access to the A-RACF in the retail domain . 105
6.4.3.2 Request Resource without access to the A-RACF in the retail domain . 107
6.4.4 Release Resource . 109
6.4.4.1 Release Resource Request by using the push mode . 109
6.4.4.2 Release Resource Request by using the pull mode . 110
6.4.4.2.1 Resource Release using pull mode when only one x-RACF is involved . 110
6.4.4.2.2 Resource release using pull mode when multiple x-RACFs are involved . 111
6.4.5 Commit Resources procedure . 112
6.4.6 Resource Modification Request . 113
6.4.6.1 Resource Modification Request by using the push mode. 113
6.4.6.2 Resource Modification Request by using the pull mode . 114
ETSI
7 Final draft ETSI ES 282 003 V3.4.0 (2009-07)
6.4.7 RACS Retrieves Access Profile from NASS . 115
6.4.8 Subscriber Detaches from the access network . 115
6.4.9 Abnormal event from the RCEF . 117
6.4.10 Report of BGF Events. 117
6.4.11 Indication of a BGF Service Failure (Autonomous Release of BGF) . 118
Annex A (informative): Binding Information in RACS, NASS and AF . 120
Annex B (informative): Policy nomenclature for RACS . 121
B.1 Overview . . 121
B.2 Policy Terminology . 121
B.2.1 Policy . 121
B.2.2 Conditions . 121
B.2.3 Actions . 121
B.2.4 Events . 121
B.3 Types of Policy . 122
B.3.1 Authorization Policy. 122
B.3.2 Obligation Polic y . 122
B.3.3 Traffic Policy . 122
B.3.4 Control Policy . 122
Annex C (informative): Admission control scenarios . 123
C.1 Example of the handling of Connection Oriented network in the aggregation segment . 123
Annex D (informative): Network deployment scenarios . 124
D.1 Resource control scenarios according to distribution of Service-based Policy Decision and
Admission Control Functions . 124
D.1.1 Single NGN operator performs Service-based Policy Decision and Admission Control Functions . 124
D.1.1.1 Scenario Overview . 124
D.1.1.2 Business Need . 124
D.1.1.3 Mapping to TISPAN Architecture: RACS requirements . 125
D.1.1.4 Technical Analysis . 125
D.1.1.4.1 Functional Element Analysis . 125
D.1.1.4.2 Elementary Functions Analysis . 125
D.1.1.4.3 Reference Point Analysis . 125
D.1.2 Service-based Policy Decision function handled in two domains . 125
D.1.2.1 Scenario Overview . 125
D.1.2.2 Business Need . 126
D.1.2.3 Mapping to TISPAN Architecture: RACS requirements . 126
D.1.2.4 Technical Analysis . 126
D.1.2.4.1 Functional Element Analysis . 126
D.1.2.4.2 Elementary Functions Analysis . 126
D.1.2.4.3 Reference Point Analysis . 126
D.1.3 Service-based Policy Decision and Admission Control functions distributed across two domains . 127
D.1.3.1 Scenario Overview .
...

ETSI Standard
Telecommunications and Internet converged Services and
Protocols for Advanced Networking (TISPAN);
Resource and Admission Control Sub-System (RACS):
Functional Architecture
2 ETSI ES 282 003 V3.4.1 (2009-09)

Reference
RES/TISPAN-02072-NGN-R3
Keywords
architecture, control, system
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2009.
All rights reserved.
TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
LTE™ is a Trade Mark of ETSI currently being registered
for the benefit of its Members and of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI
3 ETSI ES 282 003 V3.4.1 (2009-09)
Contents
Intellectual Property Rights . 10
Foreword . 10
1 Scope . 11
2 References . 11
2.1 Normative references . 11
2.2 Informative references . 12
3 Definitions and abbreviations . 12
3.1 Definitions . 12
3.2 Abbreviations . 14
4 General description of RACS . 16
4.1 Functional overview . 16
4.1.1 Global description . 16
4.1.2 Basic functionalitie s . 16
4.1.3 Restrictions applicable to the present document . 17
4.2 Functional Requirements . 17
4.2.1 R1 Requirements . 17
4.2.1.1 Overall . 17
4.2.1.2 Transport Control Service Requests . 17
4.2.1.3 Resource Handling . 18
4.2.1.4 QoS Management . 19
4.2.1.5 Traffic Handling . 19
4.2.1.6 Charging and Overload Control . 20
4.2.2 R2 Requirements . 20
4.2.2.1 Overall . 20
4.2.2.2 Resource Handling . 20
4.2.2.3 QoS Management . 20
4.2.2.4 e2e QoS Handling . 21
4.2.2.5 Multicast/Unicast Handling . 21
4.2.2.6 Topology and Resource Information Retrieval . 21
4.2.2.7 Network Deployment Scenarios . 22
4.2.2.8 Charging and Overload Control . 22
4.2.3 R3 Requirements . 22
4.2.3.1 Interaction with the CPN . 22
4.2.3.1.1 Direct control by RACS . 22
5 RACS functional architecture derivation basis . 22
5.1 Resource Control for Unicast and Multicast . 23
5.1.1 Resource control scenarios . 23
5.1.1.1 Identification of Resources . 23
5.1.1.2 Multicast Resource Admission Decision Specifics . 24
5.1.1.3 Resource Admission Decision Prerequisites . 24
5.1.1.4 Resource Admission Control Approaches . 25
5.1.1.5 Multicast Resource Admission Control in the Access Network Domain Transport Nodes . 25
5.1.1.6 Unicast/Multicast Resource Reuse in the Access Segment . 25
5.2 Charging . 26
5.3 QoS Management Functions in Fixed Access Networks. 26
5.4 Resource Control for QoS Downgrading . 28
6 RACS functional architecture definition . 29
6.1 General . 29
6.2 Functional elements . 31
6.2.1 SPDF . 31
6.2.1.1 SPDF main functions . 31
6.2.1.2 Summary of SPDF Elementary Functions . 31
6.2.1.3 Reference points . 33
ETSI
4 ETSI ES 282 003 V3.4.1 (2009-09)
6.2.1.4 User profile . 33
6.2.1.5 Priority . 33
6.2.1.6 Service request . 34
6.2.1.7 Coordination function . 34
6.2.1.8 Charging . 35
6.2.1.9 Deployment considerations . 35
6.2.1.10 Overload control . 35
6.2.1.11 Discovery mechanism . 35
6.2.2 Generic Resource Admission Control Function . 35
6.2.2.1 Main functions . 35
6.2.2.1.1 Specializations of x-RACF . 36
6.2.2.1.2 Reference points applicable to different specializations of x-RACF . 36
6.2.2.1.3 Multiple instantiations of x-RACF . 36
6.2.2.2 Summary of generic Resource Admission Control Function Elementary Functions . 37
6.2.2.3 A-RACF . 39
6.2.2.3.1 A-RACF main functions . 39
6.2.2.3.2 Reference points . 39
6.2.2.4 C-RACF . 40
6.2.2.4.1 C-RACF main functions . 40
6.2.2.4.2 Reference points . 40
6.2.2.5 Admission control process . 40
6.2.2.5.1 A-RACF . 40
6.2.2.5.2 C-RACF. 42
6.2.2.6 Installation of policies . 42
6.2.2.7 Charging . 43
6.2.2.8 Abnormal condition handling. 43
6.2.2.9 Deployment considerations . 43
6.2.2.10 Overload control . 43
6.2.2.11 Discovery Mechanism . 43
6.2.3 BGF . 43
6.2.3.1 BGF main functions . 43
6.2.3.2 BGF parameters . 44
6.2.3.3 Reference points . 44
6.2.3.4 Addressing latching . 44
6.2.3.5 Abnormal conditions handling . 44
6.2.3.6 Overload control . 44
6.2.4 RCEF . 45
6.2.4.1 RCEF main functions . 45
6.2.4.2 Reference points . 45
6.2.4.3 RCEF parameters . 45
6.2.5 Application Function (AF) . 45
6.2.5.1 AF main functions . 45
6.2.5.2 Reference points . 46
6.2.5.3 Charging . 47
6.2.5.4 Abnormal conditions handling . 47
6.2.6 BTF . 47
6.3 RACS reference points . 47
6.3.1 Rq reference point (SPDF - x-RACF). 47
6.3.1.1 Functional requirements . 47
6.3.1.1.1 Resource management mechanisms . 47
6.3.1.1.2 Service model . 48
6.3.1.1.3 Duration semantics . 48
6.3.1.1.4 Audit and synchronization support . 49
6.3.1.1.5 Report facilities for unsolicited events . 49
6.3.1.2 Non-functional requirements. 49
6.3.1.2.1 Reliability requirements . 49
6.3.1.2.2 Security requirements . 49
6.3.1.3 Information exchanged over the Rq Reference Point . 49
6.3.1.3.1 Resource Reservation Request . 49
6.3.1.3.2 Resource Modification Request . 51
6.3.1.3.3 Resource Request/Modification Confirmation . 52
6.3.1.3.4 Resource Release Request . 52
ETSI
5 ETSI ES 282 003 V3.4.1 (2009-09)
6.3.1.3.5 Abort Resource Reservation . 52
6.3.2 e4 reference point (A-RACF - NASS) . 53
6.3.3 Ia Reference Point (SPDF - BGF) . 53
6.3.3.1 Functional Requirements . 53
6.3.3.1.1 Control of NAT, Hosted NAT traversal and Gating . 53
6.3.3.1.2 Transport Protocol Type Policing . 53
6.3.3.1.3 Bandwidth control . 53
6.3.3.1.4 QoS marking . 53
6.3.3.1.5 Usage metering and statistics reporting . 53
6.3.3.1.6 Resource state synchronization . 54
6.3.3.2 Non-Functional Requirements . 54
6.3.3.2.1 Reliability requirements . 54
6.3.3.2.2 Security requirements . 54
6.3.3.3 Information exchanged over the Ia Reference Point . 54
6.3.3.3.1 BGF Service Request . 54
6.3.3.3.2 BGF Service Confirmation . 57
6.3.3.3.3 BGF Service Modify Request . 58
6.3.3.3.4 BGF Service Modify Confirmation . 59
6.3.3.3.5 BGF Service Audit Request . 60
6.3.3.3.6 BGF Service Audit Response . 61
6.3.3.3.7 BGF Service Notify Request . 62
6.3.3.3.8 BGF Service Notify Indication . 63
6.3.3.3.9 BGF Service Release Request . 63
6.3.3.3.10 BGF Service Release Confirmation. 64
6.3.4 Gq' Reference Point (AF - SPDF) . 65
6.3.4.1 Functional Requirements . 65
6.3.4.2 Non-Functional Requirements . 65
6.3.4.3 Information exchanged over the Gq' Reference Point . 65
6.3.5 Ri' Reference Point (SPDF-SPDF inter-domain) . 66
6.3.5.1 Functional Requirements . 66
6.3.5.1.1 Resource management mechanisms . 66
6.3.5.1.2 Service model . 66
6.3.5.1.3 Duration semantics . 66
6.3.5.1.4 Audit and Synchronization support . 67
6.3.5.1.5 Report facilities for unsolicited events . 67
6.3.5.2 Non-Functional Requirements . 67
6.3.5.2.1 Reliability requirements . 67
6.3.5.2.2 Security requirements . 67
6.3.5.3 Information exchanged over the Ri' Reference Point . 67
6.3.6 Rd' Reference Point (SPDF-SPDF intra-domain) . 67
6.3.6.1 Functional Requirements . 67
6.3.6.1.1 Resource management mechanisms . 67
6.3.6.1.2 Service model . 67
6.3.6.1.3 Duration semantics . 68
6.3.6.1.4 Audit and Synchronization support . 68
6.3.6.1.5 Report facilities for unsolicited events . 68
6.3.6.2 Non-Functional Requirements . 68
6.3.6.2.1 Reliability requirements . 68
6.3.6.2.2 Security requirements . 68
6.3.6.3 Information exchanged over the Rd' Reference Point . 68
6.3.7 Re Reference Point (x-RACF - RCEF) . 68
6.3.7.1 Functional Requirements . 68
6.3.7.1.1 Policy Enforcement Management. 68
6.3.7.2 Non-functional requirements. 69
6.3.7.2.1 Reliability requirements . 69
6.3.7.2.2 Security requirements . 69
6.3.7.3 Information exchanged over the Re Reference Point . 70
6.3.7.3.1 Information exchanged by using the push mode . 70
6.3.7.3.2 Information exchanged by using the pull mode . 76
6.3.7.3.3 Information exchanged by using both QoS mechanisms . 83
6.3.8 Rr Reference Point (x-RACF - x-RACF intra-domain) . 84
6.3.8.1 Functional Requirements . 84
ETSI
6 ETSI ES 282 003 V3.4.1 (2009-09)
6.3.8.1.1 Overall features . 84
6.3.8.1.2 Resource management mechanisms . 85
6.3.8.1.3 Service model . 86
6.3.8.1.4 Duration semantics . 86
6.3.8.1.5 Audit and Synchronization support . 86
6.3.8.1.6 Report facilities for unsolicited events . 87
6.3.8.2 Non-Functional Requirements . 87
6.3.8.2.1 Reliability requirements . 87
6.3.8.2.2 Security requirements . 87
6.3.8.3 Information exchanged over the Rr Reference Point . 87
6.3.8.3.1 Information exchanged over the Rr Reference Point for request model . 87
6.3.8.3.2 Information exchanged over the Rr Reference Point for delegated model . 90
6.3.9 Rf Reference Point (SPDF-Charging Functions and x-RACF-Charging Functions) . 94
6.4 RACS Flows: Interaction Procedures . 94
6.4.1 Subscriber Attaches to the Access Network . 95
6.4.2 Request Resource . 95
6.4.2.1 Request Resource by using the push mode . 95
6.4.2.1.1 Admission control using push mode when only one x-RACF is involved . 95
6.4.2.1.2 Admission control using push mode when multiple x-RACFs are involved . 97
6.4.2.2 Request Resource by using the pull mode . 100
6.4.2.2.1 Admission control using pull mode when only one x-RACF is involved . 100
6.4.2.2.2 Admission control using pull mode when multiple x-RACFs are involved . 101
6.4.2.3 Request resource by combining push and pull mode . 102
6.4.3 Request Resource Wholesale/Retail Scenario . 105
6.4.3.1 Request Resource with access to the A-RACF in the retail domain . 105
6.4.3.2 Request Resource without access to the A-RACF in the retail domain . 107
6.4.4 Release Resource . 109
6.4.4.1 Release Resource Request by using the push mode . 109
6.4.4.2 Release Resource Request by using the pull mode . 110
6.4.4.2.1 Resource Release using pull mode when only one x-RACF is involved . 110
6.4.4.2.2 Resource release using pull mode when multiple x-RACFs are involved . 111
6.4.5 Commit Resources procedure . 112
6.4.6 Resource Modification Request . 113
6.4.6.1 Resource Modification Request by using the push mode. 113
6.4.6.2 Resource Modification Request by using the pull mode . 115
6.4.7 RACS Retrieves Access Profile from NASS . 115
6.4.8 Subscriber Detaches from the access network . 116
6.4.9 Abnormal event from the RCEF . 118
6.4.10 Report of BGF Events. 118
6.4.11 Indication of a BGF Service Failure (Autonomous Release of BGF) . 119
Annex A (informative): Binding Information in RACS, NASS and AF . 121
Annex B (informative): Policy nomenclature for RACS . 122
B.1 Overview . . 122
B.2 Policy Terminology . 122
B.2.1 Policy . 122
B.2.2 Conditions . 122
B.2.3 Actions . 122
B.2.4 Events . 122
B.3 Types of Policy . 123
B.3.1 Authorization Policy. 123
B.3.2 Obligation Polic y . 123
B.3.3 Traffic Policy . 123
B.3.4 Control Policy . 123
Annex C (informative): Admission control scenarios . 124
C.1 Example of the handling of Connection Oriented network in the aggregation segment . 124
Annex D (informative): Network deployment scenarios . 125
ETSI
7 ETSI ES 282 003 V3.4.1 (2009-09)
D.1 Resource control scenarios according to distribution of Service-based Policy Decision and
Admission Control Functions . 125
D.1.1 Single NGN operator performs Service-based Policy Decision and Admission Control Functions . 125
D.1.1.1 Scenario Overview . 125
D.1.1.2 Business Need . 125
D.1.1.3 Mapping to TISPAN Architecture: RACS requirements . 126
D.1.1.4 Technical Analysis . 126
D.1.1.4.1 Functional Element Analysis . 126
D.1.1.4.2 Elementary Functions Analysis . 126
D.1.1.4.3 Reference Point Analysis . 126
D.1.2 Service-based Policy Decision function handled in two domains . 126
D.1.2.1 Scenario Overview . 126
D.1.2.2 Business Need . 127
D.1.2.3 Mapping to TISPAN Architecture: RACS requirements . 127
D.1.2.4 Technical Analysis . 127
D.1.2.4.1 Functional Element Analysis . 127
D.1.2.4.2 Elementary Functions Analysis . 127
D.1.2.4.3 Reference Point Analysis . 127
D.1.3 Service-based Policy Decision and Admission Control functions distributed across two domains . 128
D.1.3.1 Scenario Overview . 128
D.1.3.2 Business Need . 128
D.1.3.3 Mapping to TISPAN Architecture: RACS requirements . 128
D.1.3.4 Technical Analysis . 129
D.1.3.4.1 Functional Element Analysis . 129
D.1.3.4.2 Elementary Functions Analysis . 129
D.1.3.4.3 Reference Point Analysis . 129
D.2 Resource control scenarios for Multicast and Unicast . 129
D.2.1 Independent scenario - Unicast and Multicast admission control are separated . 129
D.2.1.1 Scenario Overview . 129
D.2.1.2 Business Need . 129
D.2.1.3 Mapping to TISPAN Architecture: RACS requirements . 129
D.2.1.4 Technical Analysis . 130
D.2.1.4.1 Functional Element Analysis . 130
D.2.1.4.2 Elementary Functions Analysis . 130
D.2.1.4.3 Reference Point Analysis . 130
D.2.2 Synchronized Scenario . 130
D.2.2.1 Scenario Overview . 130
D.2.2.2 Business Need . 130
D.2.2.3 Mapping to TISPAN Architecture: RACS requirements . 130
D.2.2.4 Technical Analysis . 130
D.2.2.4.1 Functional Element Analysis . 130
D.2.2.4.2 Elementary Functions Analysis . 130
D.2.2.4.3 Reference Point Analysis . 131
D.2.3 Integrated scenario - Integrated Unicast and Multicast Admission Control . 131
D.2.3.1 Scenario Overview . 131
D.2.3.2 Business Need .
...

SLOVENSKI STANDARD
01-november-2009
Zlite telekomunikacijske in internetne storitve ter protokoli za napredno omreženje
(TISPAN) - Podsistem za krmiljenje vira in pristopa (RACS) - Funkcijska arhitektura
Telecommunications and Internet converged Services and Protocols for Advanced
Networking (TISPAN) - Resource and Admission Control Sub-System (RACS) -
Functional Architecture
Ta slovenski standard je istoveten z: ES 282 003 Version 3.4.1
ICS:
33.040.01 Telekomunikacijski sistemi Telecommunication systems
na splošno in general
33.080 Digitalno omrežje z Integrated Services Digital
integriranimi storitvami Network (ISDN)
(ISDN)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

ETSI Standard
Telecommunications and Internet converged Services and
Protocols for Advanced Networking (TISPAN);
Resource and Admission Control Sub-System (RACS):
Functional Architecture
2 ETSI ES 282 003 V3.4.1 (2009-09)

Reference
RES/TISPAN-02072-NGN-R3
Keywords
architecture, control, system
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2009.
All rights reserved.
TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
LTE™ is a Trade Mark of ETSI currently being registered
for the benefit of its Members and of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI
3 ETSI ES 282 003 V3.4.1 (2009-09)
Contents
Intellectual Property Rights . 10
Foreword . 10
1 Scope . 11
2 References . 11
2.1 Normative references . 11
2.2 Informative references . 12
3 Definitions and abbreviations . 12
3.1 Definitions . 12
3.2 Abbreviations . 14
4 General description of RACS . 16
4.1 Functional overview . 16
4.1.1 Global description . 16
4.1.2 Basic functionalitie s . 16
4.1.3 Restrictions applicable to the present document . 17
4.2 Functional Requirements . 17
4.2.1 R1 Requirements . 17
4.2.1.1 Overall . 17
4.2.1.2 Transport Control Service Requests . 17
4.2.1.3 Resource Handling . 18
4.2.1.4 QoS Management . 19
4.2.1.5 Traffic Handling . 19
4.2.1.6 Charging and Overload Control . 20
4.2.2 R2 Requirements . 20
4.2.2.1 Overall . 20
4.2.2.2 Resource Handling . 20
4.2.2.3 QoS Management . 20
4.2.2.4 e2e QoS Handling . 21
4.2.2.5 Multicast/Unicast Handling . 21
4.2.2.6 Topology and Resource Information Retrieval . 21
4.2.2.7 Network Deployment Scenarios . 22
4.2.2.8 Charging and Overload Control . 22
4.2.3 R3 Requirements . 22
4.2.3.1 Interaction with the CPN . 22
4.2.3.1.1 Direct control by RACS . 22
5 RACS functional architecture derivation basis . 22
5.1 Resource Control for Unicast and Multicast . 23
5.1.1 Resource control scenarios . 23
5.1.1.1 Identification of Resources . 23
5.1.1.2 Multicast Resource Admission Decision Specifics . 24
5.1.1.3 Resource Admission Decision Prerequisites . 24
5.1.1.4 Resource Admission Control Approaches . 25
5.1.1.5 Multicast Resource Admission Control in the Access Network Domain Transport Nodes . 25
5.1.1.6 Unicast/Multicast Resource Reuse in the Access Segment . 25
5.2 Charging . 26
5.3 QoS Management Functions in Fixed Access Networks. 26
5.4 Resource Control for QoS Downgrading . 28
6 RACS functional architecture definition . 29
6.1 General . 29
6.2 Functional elements . 31
6.2.1 SPDF . 31
6.2.1.1 SPDF main functions . 31
6.2.1.2 Summary of SPDF Elementary Functions . 31
6.2.1.3 Reference points . 33
ETSI
4 ETSI ES 282 003 V3.4.1 (2009-09)
6.2.1.4 User profile . 33
6.2.1.5 Priority . 33
6.2.1.6 Service request . 34
6.2.1.7 Coordination function . 34
6.2.1.8 Charging . 35
6.2.1.9 Deployment considerations . 35
6.2.1.10 Overload control . 35
6.2.1.11 Discovery mechanism . 35
6.2.2 Generic Resource Admission Control Function . 35
6.2.2.1 Main functions . 35
6.2.2.1.1 Specializations of x-RACF . 36
6.2.2.1.2 Reference points applicable to different specializations of x-RACF . 36
6.2.2.1.3 Multiple instantiations of x-RACF . 36
6.2.2.2 Summary of generic Resource Admission Control Function Elementary Functions . 37
6.2.2.3 A-RACF . 39
6.2.2.3.1 A-RACF main functions . 39
6.2.2.3.2 Reference points . 39
6.2.2.4 C-RACF . 40
6.2.2.4.1 C-RACF main functions . 40
6.2.2.4.2 Reference points . 40
6.2.2.5 Admission control process . 40
6.2.2.5.1 A-RACF . 40
6.2.2.5.2 C-RACF. 42
6.2.2.6 Installation of policies . 42
6.2.2.7 Charging . 43
6.2.2.8 Abnormal condition handling. 43
6.2.2.9 Deployment considerations . 43
6.2.2.10 Overload control . 43
6.2.2.11 Discovery Mechanism . 43
6.2.3 BGF . 43
6.2.3.1 BGF main functions . 43
6.2.3.2 BGF parameters . 44
6.2.3.3 Reference points . 44
6.2.3.4 Addressing latching . 44
6.2.3.5 Abnormal conditions handling . 44
6.2.3.6 Overload control . 44
6.2.4 RCEF . 45
6.2.4.1 RCEF main functions . 45
6.2.4.2 Reference points . 45
6.2.4.3 RCEF parameters . 45
6.2.5 Application Function (AF) . 45
6.2.5.1 AF main functions . 45
6.2.5.2 Reference points . 46
6.2.5.3 Charging . 47
6.2.5.4 Abnormal conditions handling . 47
6.2.6 BTF . 47
6.3 RACS reference points . 47
6.3.1 Rq reference point (SPDF - x-RACF). 47
6.3.1.1 Functional requirements . 47
6.3.1.1.1 Resource management mechanisms . 47
6.3.1.1.2 Service model . 48
6.3.1.1.3 Duration semantics . 48
6.3.1.1.4 Audit and synchronization support . 49
6.3.1.1.5 Report facilities for unsolicited events . 49
6.3.1.2 Non-functional requirements. 49
6.3.1.2.1 Reliability requirements . 49
6.3.1.2.2 Security requirements . 49
6.3.1.3 Information exchanged over the Rq Reference Point . 49
6.3.1.3.1 Resource Reservation Request . 49
6.3.1.3.2 Resource Modification Request . 51
6.3.1.3.3 Resource Request/Modification Confirmation . 52
6.3.1.3.4 Resource Release Request . 52
ETSI
5 ETSI ES 282 003 V3.4.1 (2009-09)
6.3.1.3.5 Abort Resource Reservation . 52
6.3.2 e4 reference point (A-RACF - NASS) . 53
6.3.3 Ia Reference Point (SPDF - BGF) . 53
6.3.3.1 Functional Requirements . 53
6.3.3.1.1 Control of NAT, Hosted NAT traversal and Gating . 53
6.3.3.1.2 Transport Protocol Type Policing . 53
6.3.3.1.3 Bandwidth control . 53
6.3.3.1.4 QoS marking . 53
6.3.3.1.5 Usage metering and statistics reporting . 53
6.3.3.1.6 Resource state synchronization . 54
6.3.3.2 Non-Functional Requirements . 54
6.3.3.2.1 Reliability requirements . 54
6.3.3.2.2 Security requirements . 54
6.3.3.3 Information exchanged over the Ia Reference Point . 54
6.3.3.3.1 BGF Service Request . 54
6.3.3.3.2 BGF Service Confirmation . 57
6.3.3.3.3 BGF Service Modify Request . 58
6.3.3.3.4 BGF Service Modify Confirmation . 59
6.3.3.3.5 BGF Service Audit Request . 60
6.3.3.3.6 BGF Service Audit Response . 61
6.3.3.3.7 BGF Service Notify Request . 62
6.3.3.3.8 BGF Service Notify Indication . 63
6.3.3.3.9 BGF Service Release Request . 63
6.3.3.3.10 BGF Service Release Confirmation. 64
6.3.4 Gq' Reference Point (AF - SPDF) . 65
6.3.4.1 Functional Requirements . 65
6.3.4.2 Non-Functional Requirements . 65
6.3.4.3 Information exchanged over the Gq' Reference Point . 65
6.3.5 Ri' Reference Point (SPDF-SPDF inter-domain) . 66
6.3.5.1 Functional Requirements . 66
6.3.5.1.1 Resource management mechanisms . 66
6.3.5.1.2 Service model . 66
6.3.5.1.3 Duration semantics . 66
6.3.5.1.4 Audit and Synchronization support . 67
6.3.5.1.5 Report facilities for unsolicited events . 67
6.3.5.2 Non-Functional Requirements . 67
6.3.5.2.1 Reliability requirements . 67
6.3.5.2.2 Security requirements . 67
6.3.5.3 Information exchanged over the Ri' Reference Point . 67
6.3.6 Rd' Reference Point (SPDF-SPDF intra-domain) . 67
6.3.6.1 Functional Requirements . 67
6.3.6.1.1 Resource management mechanisms . 67
6.3.6.1.2 Service model . 67
6.3.6.1.3 Duration semantics . 68
6.3.6.1.4 Audit and Synchronization support . 68
6.3.6.1.5 Report facilities for unsolicited events . 68
6.3.6.2 Non-Functional Requirements . 68
6.3.6.2.1 Reliability requirements . 68
6.3.6.2.2 Security requirements . 68
6.3.6.3 Information exchanged over the Rd' Reference Point . 68
6.3.7 Re Reference Point (x-RACF - RCEF) . 68
6.3.7.1 Functional Requirements . 68
6.3.7.1.1 Policy Enforcement Management. 68
6.3.7.2 Non-functional requirements. 69
6.3.7.2.1 Reliability requirements . 69
6.3.7.2.2 Security requirements . 69
6.3.7.3 Information exchanged over the Re Reference Point . 70
6.3.7.3.1 Information exchanged by using the push mode . 70
6.3.7.3.2 Information exchanged by using the pull mode . 76
6.3.7.3.3 Information exchanged by using both QoS mechanisms . 83
6.3.8 Rr Reference Point (x-RACF - x-RACF intra-domain) . 84
6.3.8.1 Functional Requirements . 84
ETSI
6 ETSI ES 282 003 V3.4.1 (2009-09)
6.3.8.1.1 Overall features . 84
6.3.8.1.2 Resource management mechanisms . 85
6.3.8.1.3 Service model . 86
6.3.8.1.4 Duration semantics . 86
6.3.8.1.5 Audit and Synchronization support . 86
6.3.8.1.6 Report facilities for unsolicited events . 87
6.3.8.2 Non-Functional Requirements . 87
6.3.8.2.1 Reliability requirements . 87
6.3.8.2.2 Security requirements . 87
6.3.8.3 Information exchanged over the Rr Reference Point . 87
6.3.8.3.1 Information exchanged over the Rr Reference Point for request model . 87
6.3.8.3.2 Information exchanged over the Rr Reference Point for delegated model . 90
6.3.9 Rf Reference Point (SPDF-Charging Functions and x-RACF-Charging Functions) . 94
6.4 RACS Flows: Interaction Procedures . 94
6.4.1 Subscriber Attaches to the Access Network . 95
6.4.2 Request Resource . 95
6.4.2.1 Request Resource by using the push mode . 95
6.4.2.1.1 Admission control using push mode when only one x-RACF is involved . 95
6.4.2.1.2 Admission control using push mode when multiple x-RACFs are involved . 97
6.4.2.2 Request Resource by using the pull mode . 100
6.4.2.2.1 Admission control using pull mode when only one x-RACF is involved . 100
6.4.2.2.2 Admission control using pull mode when multiple x-RACFs are involved . 101
6.4.2.3 Request resource by combining push and pull mode . 102
6.4.3 Request Resource Wholesale/Retail Scenario . 105
6.4.3.1 Request Resource with access to the A-RACF in the retail domain . 105
6.4.3.2 Request Resource without access to the A-RACF in the retail domain . 107
6.4.4 Release Resource . 109
6.4.4.1 Release Resource Request by using the push mode . 109
6.4.4.2 Release Resource Request by using the pull mode . 110
6.4.4.2.1 Resource Release using pull mode when only one x-RACF is involved . 110
6.4.4.2.2 Resource release using pull mode when multiple x-RACFs are involved . 111
6.4.5 Commit Resources procedure . 112
6.4.6 Resource Modification Request . 113
6.4.6.1 Resource Modification Request by using the push mode. 113
6.4.6.2 Resource Modification Request by using the pull mode . 115
6.4.7 RACS Retrieves Access Profile from NASS . 115
6.4.8 Subscriber Detaches from the access network . 116
6.4.9 Abnormal event from the RCEF . 118
6.4.10 Report of BGF Events. 118
6.4.11 Indication of a BGF Service Failure (Autonomous Release of BGF) . 119
Annex A (informative): Binding Information in RACS, NASS and AF . 121
Annex B (informative): Policy nomenclature for RACS . 122
B.1 Overview . . 122
B.2 Policy Terminology . 122
B.2.1 Policy . 122
B.2.2 Conditions . 122
B.2.3 Actions . 122
B.2.4 Events . 122
B.3 Types of Policy . 123
B.3.1 Authorization Policy. 123
B.3.2 Obligation Polic y . 123
B.3.3 Traffic Policy . 123
B.3.4 Control Policy . 123
Annex C (informative): Admission control scenarios . 124
C.1 Example of the handling of Connection Oriented network in the aggregation segment . 124
Annex D (informative): Network deployment scenarios . 125
ETSI
7 ETSI ES 282 003 V3.4.1 (2009-09)
D.1 Resource control scenarios according to distribution of Service-based Policy Decision and
Admission Control Functions . 125
D.1.1 Single NGN operator performs Service-based Policy Decision and Admission Control Functions . 125
D.1.1.1 Scenario Overview . 125
D.1.1.2 Business Need . 125
D.1.1.3 Mapping to TISPAN Architecture: RACS requirements . 126
D.1.1.4 Technical Analysis . 126
D.1.1.4.1 Functional Element Analysis . 126
D.1.1.4.2 Elementary Functions Analysis . 126
D.1.1.4.3 Reference Point Analysis . 126
D.1.2 Service-based Policy Decision function handled in two domains . 126
D.1.2.1 Scenario Overview . 126
D.1.2.2 Business Need . 127
D.1.2.3 Mapping to TISPAN Architecture: RACS requirements . 127
D.1.2.4 Technical Analysis . 127
D.1.2.4.1 Functional Element Analysis . 127
D.1.2.4.2 Elementary Functions Analysis . 127
D.1.2.4.3 Reference Point Analysis . 127
D.1.3 Service-based Policy Decision and Admission Control functions distributed across two domains . 128
D.1.3.1 Scenario Overview . 128
D.1.3.2 Business Need . 128
D.1.3.3 Mapping to TISPAN Architecture: RACS requirements . 128
D.1.3.4 Technical Analysis . 129
D.1.3.4.1 Functional Element Analysis . 129
D.1.3.4.2 Elementary Functions Analysis . 129
D.1.3.4.3 Reference Point Analysis . 129
D.2 Resource control scenarios for Multicast and Unicast . 129
D.2.1 Independent scenario - Unicast and Multicast admission control are separated . 129
D.2.1.1 Scenario Overview . 129
D.2.1.2 Business Need . 129
D.2.1.3 Mapping to TISPAN Architecture: RACS requirements . 129
D.2.1.4 Technical Analysis . 130
D.2.1.4.1 Functional Element Analysis . 130
D.2.1.4.2 Elementary Functions Analysis . 130
D.2.1.4.3 Reference Point Analysis . 130
D.2.2 Synchronized Scenario . 130
D.2.2.1 Scenario Overview . 130
D.2.2.2 Business Need .
...