ETSI ES 282 003 V2.0.0 (2008-03)

ETSI ES 282 003 V2.0.0 (2008-05)
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 V2.0.0 (2008-05)

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

Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16

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 2008.
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.
ETSI
3 ETSI ES 282 003 V2.0.0 (2008-05)
Contents
Intellectual Property Rights.9
Foreword.9
1 Scope.10
2 References.10
2.1 Normative references.11
2.2 Informative references.11
3 Definitions and abbreviations.12
3.1 Definitions.12
3.2 Abbreviations.13
4 General description of RACS.15
4.1 High Level functional overview.15
4.2 Functional Requirements.16
4.2.1 R1 Requirements.16
4.2.1.1 Overall.16
4.2.1.2 Transport Control Service Requests.16
4.2.1.3 Resource Handling.17
4.2.1.4 QoS Management.18
4.2.1.5 Traffic Handling.18
4.2.1.6 Charging and Overload Control .18
4.2.2 R2 Requirements.18
4.2.2.1 Overall.18
4.2.2.2 Resource Handling.19
4.2.2.3 QoS Management.19
4.2.2.4 e2e QoS Handling .19
4.2.2.5 Multicast/Unicast Handling .19
4.2.2.6 Topology and Resource Information Retrieval .20
4.2.2.7 Network Deployment Scenarios.20
4.2.2.8 Charging and Overload Control .20
5 RACS functional architecture derivation basis .20
5.1 Resource Control for Unicast and Multicast .20
5.1.1 Resource control scenarios .21
5.1.1.1 Identification of Resources.21
5.1.1.2 Multicast Resource Admission Decision Specifics.21
5.1.1.3 Resource Admission Decision Prerequisites.22
5.1.1.4 Resource Admission Control Approaches .22
5.1.1.5 Multicast Resource Admission Control in the Access Network Domain Transport Nodes .22
5.2 Charging.23
5.3 QoS Management Functions in Fixed Access Networks.23
5.4 Resource Control for Service Quality Downgrading.25
6 RACS functional architecture definition.26
6.1 General.26
6.2 Functional elements.28
6.2.1 SPDF.28
6.2.1.1 SPDF main functions.28
6.2.1.2 Summary of SPDF Elementary Functions .28
6.2.1.3 Reference points.29
6.2.1.4 User profile.30
6.2.1.5 Priority.30
6.2.1.6 Service request.30
6.2.1.7 Coordination function.31
6.2.1.8 Charging.31
6.2.1.9 Deployment considerations.31
6.2.1.10 Overload control .32
ETSI
4 ETSI ES 282 003 V2.0.0 (2008-05)
6.2.1.11 Discovery mechanism.32
6.2.2 Generic Resource Admission Control Function .32
6.2.2.1 Main functions.32
6.2.2.1.1 Specializations of x-RACF.33
6.2.2.1.2 Reference points applicable to different specializations of x-RACF.33
6.2.2.1.3 Multiple instantiations of x-RACF .33
6.2.2.2 Summary of generic Resource Admission Control Function Elementary Functions.34
6.2.2.3 A-RACF.36
6.2.2.3.1 A-RACF main functions.36
6.2.2.3.2 Reference points.36
6.2.2.4 C-RACF.36
6.2.2.4.1 C-RACF main functions.36
6.2.2.5 Admission control process .36
6.2.2.5.1 A-RACF .36
6.2.2.5.2 C-RACF.38
6.2.2.6 Installation of policies .38
6.2.2.7 Charging.38
6.2.2.8 Abnormal condition handling.39
6.2.2.9 Deployment considerations.39
6.2.2.10 Overload control .39
6.2.2.11 Discovery Mechanism.39
6.2.3 BGF.39
6.2.3.1 BGF main functions.39
6.2.3.2 BGF parameters.40
6.2.3.3 Reference points.40
6.2.3.4 Addressing latching.40
6.2.3.5 Abnormal conditions handling .40
6.2.3.6 Overload control.40
6.2.4 RCEF.40
6.2.4.1 RCEF main functions.40
6.2.4.2 Reference points.41
6.2.4.3 RCEF parameters.41
6.2.5 Application Function (AF).41
6.2.5.1 AF main functions.41
6.2.5.2 Reference points.42
6.2.5.3 Charging.42
6.2.5.4 Abnormal conditions handling .42
6.3 RACS reference points.42
6.3.1 Rq reference point (SPDF - A-RACF).42
6.3.1.1 Functional requirements.42
6.3.1.1.1 Resource management mechanisms .43
6.3.1.1.2 Service model.43
6.3.1.1.3 Duration semantics.44
6.3.1.1.4 Audit and synchronization support.44
6.3.1.1.5 Report facilities for unsolicited events .44
6.3.1.2 Non-functional requirements.44
6.3.1.2.1 Reliability requirements.44
6.3.1.2.2 Security requirements.44
6.3.1.3 Information exchanged over the Rq Reference Point.45
6.3.1.3.1 Resource Reservation Request.45
6.3.1.3.2 Resource Modification Request.46
6.3.1.3.3 Resource Request/Modification Confirmation.47
6.3.1.3.4 Resource Release Request.47
6.3.1.3.5 Abort Resource Reservation.48
6.3.2 e4 reference point (A-RACF - NASS).48
6.3.3 Ia Reference Point (SPDF - BGF) .48
6.3.3.1 Functional Requirements.48
6.3.3.1.1 Control of NAT, Hosted NAT traversal and Gating.48
6.3.3.1.2 Transport Protocol Type Policing.49
6.3.3.1.3 Bandwidth control .49
6.3.3.1.4 QoS marking.49
6.3.3.1.5 Usage metering and statistics reporting.49
ETSI
5 ETSI ES 282 003 V2.0.0 (2008-05)
6.3.3.1.6 Resource state synchronization .49
6.3.3.2 Non-Functional Requirements.49
6.3.3.2.1 Reliability requirements.49
6.3.3.2.2 Security requirements.49
6.3.3.3 Information exchanged over the Ia Reference Point .49
6.3.4 Gq' Reference Point (AF - SPDF).49
6.3.4.1 Functional Requirements.49
6.3.4.2 Non-Functional Requirements.50
6.3.4.3 Information exchanged over the Gq' Reference Point.50
6.3.5 Ri' Reference Point (SPDF-SPDF inter-domain).50
6.3.5.1 Functional Requirements.50
6.3.5.1.1 Resource management mechanisms .50
6.3.5.1.2 Service model.50
6.3.5.1.3 Duration semantics.51
6.3.5.1.4 Audit and Synchronization support .51
6.3.5.1.5 Report facilities for unsolicited events .51
6.3.5.2 Non-Functional Requirements.51
6.3.5.2.1 Reliability requirements.51
6.3.5.2.2 Security requirements.51
6.3.5.3 Information exchanged over the Ri' Reference Point.51
6.3.6 Rd' Reference Point (SPDF-SPDF intra-domain).51
6.3.7 Re Reference Point (A-RACF - RCEF).52
6.3.7.1 Functional Requirements.52
6.3.7.1.1 Policy Enforcement Management.52
6.3.7.2 Non-functional requirements.53
6.3.7.2.1 Reliability requirements.53
6.3.7.2.2 Security requirements.53
6.3.7.3 Information exchanged over the Re Reference Point.53
6.3.8 Rr Reference Point (x-RACF - x-RACF intra-domain).53
6.3.8.1 Functional Requirements.53
6.3.8.1.1 Overall features.53
6.3.8.1.2 Resource management mechanisms .54
6.3.8.1.3 Service model.54
6.3.8.1.4 Duration semantics.55
6.3.8.1.5 Audit and Synchronization support .55
6.3.8.1.6 Report facilities for unsolicited events .55
6.3.8.2 Non-Functional Requirements.55
6.3.8.2.1 Reliability requirements.55
6.3.8.2.2 Security requirements.55
6.3.8.3 Information exchanged over the Rr Reference Point .56
6.3.8.3.1 Resource Reservation Request.56
6.3.8.3.2 Resource Modification Request.57
6.3.8.3.3 Resource Request/Modification Confirmation.58
6.3.8.3.4 Resource Release Request.59
6.3.8.3.5 Abort Resource Reservation.59
6.3.8.3.6 Resource Allocation Request.60
6.3.8.3.7 Resource Allocation Confirmation.61
6.4 RACS Flows: Interaction Procedures.61
6.4.1 Subscriber Attaches to the Access Network .61
6.4.2 Request Resource.62
6.4.2.1 Request Resource by using the push mode .62
6.4.2.2 Request Resource by using the pull mode.63
6.4.2.2.1 Admission control using pull mode when only one x-RACF is involved in managing the
same resources.63
6.4.2.2.2 Admission control using pull mode when multiple x-RACFs are involved in managing the
same resources.65
6.4.3 Request Resource Wholesale/Retail Scenario .66
6.4.3.1 Request Resource with access to the A-RACF in the retail domain .66
6.4.3.2 Request Resource without access to the A-RACF in the retail domain .67
6.4.4 Release Resource.69
6.4.4.1 Release Resource Request by using the push mode.69
6.4.4.2 Release Resource Request by using the pull mode .70
ETSI
6 ETSI ES 282 003 V2.0.0 (2008-05)
6.4.4.2.1 Resource Release using pull mode when only one x-RACF is involved in managing the same
resources.70
6.4.4.2.2 Resource release using pull mode when multiple x-RACFs are involved in managing the
same resources.71
6.4.5 Commit Resources procedure.72
6.4.6 Resource Modification Request.73
6.4.6.1 Resource Modification Request by using the push mode.73
6.4.6.2 Resource Modification Request by using the pull mode.74
6.4.7 RACS Retrieves Access Profile from NASS.75
6.4.8 Subscriber Detaches from the access network.75
6.4.9 Abnormal event from the RCEF.77
6.4.10 Report of BGF Events.77
6.4.11 Indication of a BGF Service Failure (Autonomous Release of BGF).78
Annex A (informative): Binding Information in RACS, NASS and AF.80
Annex B (informative): Policy nomenclature for RACS .81
B.1 Overview.81
B.2 Policy Terminology.81
B.2.1 Policy.81
B.2.2 Conditions.81
B.2.3 Actions.81
B.2.4 Events.81
B.3 Types of Policy.82
B.3.1 Authorization Policy.82
B.3.2 Obligation Policy.82
B.3.3 Traffic Policy.82
B.3.4 Control Policy.82
Annex C (informative): Admission control scenarios .83
C.1 Example of the handling of Connection Oriented network in the aggregation segment.83
Annex D (informative): Network deployment scenarios.84
D.1 Resource control scenarios according to distribution of Service-based Policy Decision and
Admission Control Functions.84
D.1.1 Single NGN operator performs Service-based Policy Decision and Admission Control Functions .84
D.1.1.1 Scenario Overview.84
D.1.1.2 Business Need.84
D.1.1.3 Mapping to TISPAN Architecture: RACS requirements.85
D.1.1.4 Technical Analysis.85
D.1.1.4.1 Functional Element Analysis.85
D.1.1.4.2 Elementary Functions Analysis.85
D.1.1.4.3 Reference Point Analysis.85
D.1.2 Service-based Policy Decision function handled in two domains .85
D.1.2.1 Scenario Overview.85
D.1.2.2 Business Need.86
D.1.2.3 Mapping to TISPAN Architecture: RACS requirements.86
D.1.2.4 Technical Analysis.86
D.1.2.4.1 Functional Element Analysis.86
D.1.2.4.2 Elementary Functions Analysis.86
D.1.2.4.3 Reference Point Analysis.86
D.1.3 Service-based Policy Decision and Admission Control functions distributed across two domains .87
D.1.3.1 Scenario Overview.87
D.1.3.2 Business Need.87
D.1.3.3 Mapping to TISPAN Architecture: RACS requirements.87
D.1.3.4 Technical Analysis.88
D.1.3.4.1 Functional Element Analysis.88
D.1.3.4.2 Elementary Functions Analysis.88
D.1.3.4.3 Reference Point Analysis.88
ETSI
7 ETSI ES 282 003 V2.0.0 (2008-05)
D.2 Resource control scenarios for Multicast and Unicast .88
D.2.1 Independent scenario - Unicast and Multicast admission control are separated.88
D.2.1.1 Scenario Overview.88
D.2.1.2 Business Need.88
D.2.1.3 Mapping to TISPAN Architecture: RACS requirements.88
D.2.1.4 Technical Analysis.89
D.2.1.4.1 Functional Element Analysis.89
D.2.1.4.2 Elementary Functions Analysis.89
D.2.1.4.3 Reference Point Analysis.89
D.2.2 Synchronized Scenario.89
D.2.2.1 Scenario Overview.89
D.2.2.2 Business Need.89
D.2.2.3 Mapping to TISPAN Architecture: RACS requirements.89
D.2.2.4 Technical Analysis.89
D.2.2.4.1 Functional Element Analysis.89
D.2.2.4.2 Elementary Functions Analysis.89
D.2.2.4.3 Reference Point Analysis.90
D.2.3 Integrated scenario - Integrated Unicast and Multicast Admission Control.90
D.2.3.1 Scenario Overview.90
D.2.3.2 Business Need.90
D.2.3.3 Mapping to TISPAN Architecture: RACS requirements.90
D.2.3.4 Technical Analysis.90
D.2.3.4.1 Functional Element Analysis.90
D.2.3.4.2 Elementary Functions Analysis.90
D.2.3.4.3 Reference Point Analysis.90
D.3 Resource control scenario for Metro Network .90
D.3.1 Scenario Overview.90
D.3.2 Business Need.91
D.3.3 Mapping to TISPAN Architecture: RACS requirements .91
D.3.4 Technical Analysis .91
D.3.4.1 Functional Element Analysis .91
D.3.4.2 Elementary Functions Analysis.91
D.3.4.3 Reference Point Analysis.91
Annex E (informative): Topology and Resource Management Use Cases and Elementary
Functions .92
E.1 Topology and Resource Management Use Cases .92
E.1.1 Initial RACS Startup .92
E.1.2 Network Auto-Discovery.92
E.1.3 Managing Network Elements .93
E.1.4 Managing Network Topology .94
E.1.5 Real-Time Monitoring.94
E.1.5.1 Real-time Monitoring (Network Integration) .94
E.1.5.2 Real-time Monitoring (OSS Integration) .95
E.1.5.3 OSS-based Monitoring.95
E.1.6 Just-In-Time Information Pull.96
E.2 Topology and Resource Management Elementary Functions.97
E.2.1 Provisioning Elementary Function .97
E.2.2 Discovery Elementary Function.97
E.2.3 Partitioning Elementary Function.97
E.2.4 Monitoring Elementary Function.
...

SLOVENSKI STANDARD
01-september-2008
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 2.0.0
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 ES 282 003 V2.0.0 (2008-05)
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 V2.0.0 (2008-05)

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

Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16

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 2008.
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.
ETSI
3 ETSI ES 282 003 V2.0.0 (2008-05)
Contents
Intellectual Property Rights.9
Foreword.9
1 Scope.10
2 References.10
2.1 Normative references.11
2.2 Informative references.11
3 Definitions and abbreviations.12
3.1 Definitions.12
3.2 Abbreviations.13
4 General description of RACS.15
4.1 High Level functional overview.15
4.2 Functional Requirements.16
4.2.1 R1 Requirements.16
4.2.1.1 Overall.16
4.2.1.2 Transport Control Service Requests.16
4.2.1.3 Resource Handling.17
4.2.1.4 QoS Management.18
4.2.1.5 Traffic Handling.18
4.2.1.6 Charging and Overload Control .18
4.2.2 R2 Requirements.18
4.2.2.1 Overall.18
4.2.2.2 Resource Handling.19
4.2.2.3 QoS Management.19
4.2.2.4 e2e QoS Handling .19
4.2.2.5 Multicast/Unicast Handling .19
4.2.2.6 Topology and Resource Information Retrieval .20
4.2.2.7 Network Deployment Scenarios.20
4.2.2.8 Charging and Overload Control .20
5 RACS functional architecture derivation basis .20
5.1 Resource Control for Unicast and Multicast .20
5.1.1 Resource control scenarios .21
5.1.1.1 Identification of Resources.21
5.1.1.2 Multicast Resource Admission Decision Specifics.21
5.1.1.3 Resource Admission Decision Prerequisites.22
5.1.1.4 Resource Admission Control Approaches .22
5.1.1.5 Multicast Resource Admission Control in the Access Network Domain Transport Nodes .22
5.2 Charging.23
5.3 QoS Management Functions in Fixed Access Networks.23
5.4 Resource Control for Service Quality Downgrading.25
6 RACS functional architecture definition.26
6.1 General.26
6.2 Functional elements.28
6.2.1 SPDF.28
6.2.1.1 SPDF main functions.28
6.2.1.2 Summary of SPDF Elementary Functions .28
6.2.1.3 Reference points.29
6.2.1.4 User profile.30
6.2.1.5 Priority.30
6.2.1.6 Service request.30
6.2.1.7 Coordination function.31
6.2.1.8 Charging.31
6.2.1.9 Deployment considerations.31
6.2.1.10 Overload control .32
ETSI
4 ETSI ES 282 003 V2.0.0 (2008-05)
6.2.1.11 Discovery mechanism.32
6.2.2 Generic Resource Admission Control Function .32
6.2.2.1 Main functions.32
6.2.2.1.1 Specializations of x-RACF.33
6.2.2.1.2 Reference points applicable to different specializations of x-RACF.33
6.2.2.1.3 Multiple instantiations of x-RACF .33
6.2.2.2 Summary of generic Resource Admission Control Function Elementary Functions.34
6.2.2.3 A-RACF.36
6.2.2.3.1 A-RACF main functions.36
6.2.2.3.2 Reference points.36
6.2.2.4 C-RACF.36
6.2.2.4.1 C-RACF main functions.36
6.2.2.5 Admission control process .36
6.2.2.5.1 A-RACF .36
6.2.2.5.2 C-RACF.38
6.2.2.6 Installation of policies .38
6.2.2.7 Charging.38
6.2.2.8 Abnormal condition handling.39
6.2.2.9 Deployment considerations.39
6.2.2.10 Overload control .39
6.2.2.11 Discovery Mechanism.39
6.2.3 BGF.39
6.2.3.1 BGF main functions.39
6.2.3.2 BGF parameters.40
6.2.3.3 Reference points.40
6.2.3.4 Addressing latching.40
6.2.3.5 Abnormal conditions handling .40
6.2.3.6 Overload control.40
6.2.4 RCEF.40
6.2.4.1 RCEF main functions.40
6.2.4.2 Reference points.41
6.2.4.3 RCEF parameters.41
6.2.5 Application Function (AF).41
6.2.5.1 AF main functions.41
6.2.5.2 Reference points.42
6.2.5.3 Charging.42
6.2.5.4 Abnormal conditions handling .42
6.3 RACS reference points.42
6.3.1 Rq reference point (SPDF - A-RACF).42
6.3.1.1 Functional requirements.42
6.3.1.1.1 Resource management mechanisms .43
6.3.1.1.2 Service model.43
6.3.1.1.3 Duration semantics.44
6.3.1.1.4 Audit and synchronization support.44
6.3.1.1.5 Report facilities for unsolicited events .44
6.3.1.2 Non-functional requirements.44
6.3.1.2.1 Reliability requirements.44
6.3.1.2.2 Security requirements.44
6.3.1.3 Information exchanged over the Rq Reference Point.45
6.3.1.3.1 Resource Reservation Request.45
6.3.1.3.2 Resource Modification Request.46
6.3.1.3.3 Resource Request/Modification Confirmation.47
6.3.1.3.4 Resource Release Request.47
6.3.1.3.5 Abort Resource Reservation.48
6.3.2 e4 reference point (A-RACF - NASS).48
6.3.3 Ia Reference Point (SPDF - BGF) .48
6.3.3.1 Functional Requirements.48
6.3.3.1.1 Control of NAT, Hosted NAT traversal and Gating.48
6.3.3.1.2 Transport Protocol Type Policing.49
6.3.3.1.3 Bandwidth control .49
6.3.3.1.4 QoS marking.49
6.3.3.1.5 Usage metering and statistics reporting.49
ETSI
5 ETSI ES 282 003 V2.0.0 (2008-05)
6.3.3.1.6 Resource state synchronization .49
6.3.3.2 Non-Functional Requirements.49
6.3.3.2.1 Reliability requirements.49
6.3.3.2.2 Security requirements.49
6.3.3.3 Information exchanged over the Ia Reference Point .49
6.3.4 Gq' Reference Point (AF - SPDF).49
6.3.4.1 Functional Requirements.49
6.3.4.2 Non-Functional Requirements.50
6.3.4.3 Information exchanged over the Gq' Reference Point.50
6.3.5 Ri' Reference Point (SPDF-SPDF inter-domain).50
6.3.5.1 Functional Requirements.50
6.3.5.1.1 Resource management mechanisms .50
6.3.5.1.2 Service model.50
6.3.5.1.3 Duration semantics.51
6.3.5.1.4 Audit and Synchronization support .51
6.3.5.1.5 Report facilities for unsolicited events .51
6.3.5.2 Non-Functional Requirements.51
6.3.5.2.1 Reliability requirements.51
6.3.5.2.2 Security requirements.51
6.3.5.3 Information exchanged over the Ri' Reference Point.51
6.3.6 Rd' Reference Point (SPDF-SPDF intra-domain).51
6.3.7 Re Reference Point (A-RACF - RCEF).52
6.3.7.1 Functional Requirements.52
6.3.7.1.1 Policy Enforcement Management.52
6.3.7.2 Non-functional requirements.53
6.3.7.2.1 Reliability requirements.53
6.3.7.2.2 Security requirements.53
6.3.7.3 Information exchanged over the Re Reference Point.53
6.3.8 Rr Reference Point (x-RACF - x-RACF intra-domain).53
6.3.8.1 Functional Requirements.53
6.3.8.1.1 Overall features.53
6.3.8.1.2 Resource management mechanisms .54
6.3.8.1.3 Service model.54
6.3.8.1.4 Duration semantics.55
6.3.8.1.5 Audit and Synchronization support .55
6.3.8.1.6 Report facilities for unsolicited events .55
6.3.8.2 Non-Functional Requirements.55
6.3.8.2.1 Reliability requirements.55
6.3.8.2.2 Security requirements.55
6.3.8.3 Information exchanged over the Rr Reference Point .56
6.3.8.3.1 Resource Reservation Request.56
6.3.8.3.2 Resource Modification Request.57
6.3.8.3.3 Resource Request/Modification Confirmation.58
6.3.8.3.4 Resource Release Request.59
6.3.8.3.5 Abort Resource Reservation.59
6.3.8.3.6 Resource Allocation Request.60
6.3.8.3.7 Resource Allocation Confirmation.61
6.4 RACS Flows: Interaction Procedures.61
6.4.1 Subscriber Attaches to the Access Network .61
6.4.2 Request Resource.62
6.4.2.1 Request Resource by using the push mode .62
6.4.2.2 Request Resource by using the pull mode.63
6.4.2.2.1 Admission control using pull mode when only one x-RACF is involved in managing the
same resources.63
6.4.2.2.2 Admission control using pull mode when multiple x-RACFs are involved in managing the
same resources.65
6.4.3 Request Resource Wholesale/Retail Scenario .66
6.4.3.1 Request Resource with access to the A-RACF in the retail domain .66
6.4.3.2 Request Resource without access to the A-RACF in the retail domain .67
6.4.4 Release Resource.69
6.4.4.1 Release Resource Request by using the push mode.69
6.4.4.2 Release Resource Request by using the pull mode .70
ETSI
6 ETSI ES 282 003 V2.0.0 (2008-05)
6.4.4.2.1 Resource Release using pull mode when only one x-RACF is involved in managing the same
resources.70
6.4.4.2.2 Resource release using pull mode when multiple x-RACFs are involved in managing the
same resources.71
6.4.5 Commit Resources procedure.72
6.4.6 Resource Modification Request.73
6.4.6.1 Resource Modification Request by using the push mode.73
6.4.6.2 Resource Modification Request by using the pull mode.74
6.4.7 RACS Retrieves Access Profile from NASS.75
6.4.8 Subscriber Detaches from the access network.75
6.4.9 Abnormal event from the RCEF.77
6.4.10 Report of BGF Events.77
6.4.11 Indication of a BGF Service Failure (Autonomous Release of BGF).78
Annex A (informative): Binding Information in RACS, NASS and AF.80
Annex B (informative): Policy nomenclature for RACS .81
B.1 Overview.81
B.2 Policy Terminology.81
B.2.1 Policy.81
B.2.2 Conditions.81
B.2.3 Actions.81
B.2.4 Events.81
B.3 Types of Policy.82
B.3.1 Authorization Policy.82
B.3.2 Obligation Policy.82
B.3.3 Traffic Policy.82
B.3.4 Control Policy.82
Annex C (informative): Admission control scenarios .83
C.1 Example of the handling of Connection Oriented network in the aggregation segment.83
Annex D (informative): Network deployment scenarios.84
D.1 Resource control scenarios according to distribution of Service-based Policy Decision and
Admission Control Functions.84
D.1.1 Single NGN operator performs Service-based Policy Decision and Admission Control Functions .84
D.1.1.1 Scenario Overview.84
D.1.1.2 Business Need.84
D.1.1.3 Mapping to TISPAN Architecture: RACS requirements.85
D.1.1.4 Technical Analysis.85
D.1.1.4.1 Functional Element Analysis.85
D.1.1.4.2 Elementary Functions Analysis.85
D.1.1.4.3 Reference Point Analysis.85
D.1.2 Service-based Policy Decision function handled in two domains .85
D.1.2.1 Scenario Overview.85
D.1.2.2 Business Need.86
D.1.2.3 Mapping to TISPAN Architecture: RACS requirements.86
D.1.2.4 Technical Analysis.86
D.1.2.4.1 Functional Element Analysis.86
D.1.2.4.2 Elementary Functions Analysis.86
D.1.2.4.3 Reference Point Analysis.86
D.1.3 Service-based Policy Decision and Admission Control functions distributed across two domains .87
D.1.3.1 Scenario Overview.87
D.1.3.2 Business Need.87
D.1.3.3 Mapping to TISPAN Architecture: RACS requirements.87
D.1.3.4 Technical Analysis.88
D.1.3.4.1 Functional Element Analysis.88
D.1.3.4.2 Elementary Functions Analysis.88
D.1.3.4.3 Reference Point Analysis.88
ETSI
7 ETSI ES 282 003 V2.0.0 (2008-05)
D.2 Resource control scenarios for Multicast and Unicast .88
D.2.1 Independent scenario - Unicast and Multicast admission control are separated.88
D.2.1.1 Scenario Overview.88
D.2.1.2 Business Need.88
D.2.1.3 Mapping to TISPAN Architecture: RACS requirements.88
D.2.1.4 Technical Analysis.89
D.2.1.4.1 Functional Element Analysis.89
D.2.1.4.2 Elementary Functions Analysis.89
D.2.1.4.3 Reference Point Analysis.89
D.2.2 Synchronized Scenario.89
D.2.2.1 Scenario Overview.89
D.2.2.2 Business Need.89
D.2.2.3 Mapping to TISPAN Architecture: RACS requirements.89
D.2.2.4 Technical Analysis.89
D.2.2.4.1 Functional Element Analysis.89
D.2.2.4.2 Elementary Functions Analysis.89
D.2.2.4.3 Reference Point Analysis.90
D.2.3 Integrated scenario - Integrated Unicast and Multicast Admission Control.90
D.2.3.1 Scenario Overview.90
D.2.3.2 Business Need.90
D.2.3.3 Mapping to TISPAN Architecture: RACS requirements.90
D.2.3.4 Technical Analysis.90
D.2.3.4.1 Functional Element Analysis.90
D.2.3.4.2 Elementary Functions Analysis.90
D.2.3.4.3 Reference Point Analysis.90
D.3 Resource control scenario for Metro Network .90
D.3.1 Scenario Overview.90
D.3.2 Business Need.91
D.3.3 Mapping to TISPAN Architecture: RACS requirements .91
D.3.4 Technical Analysis .91
D.3.4.1 Functional Element Analysis .91
D.3.4.2 Elementary Functions Analysis.91
D.3.4.3 Reference Point Analysis.91
Annex E (informative): Topology and Resource Management Use Cases and Elementary
Functions .92
E.1 Topology and Resource Management Use Cases .92
E.1.1 Initial RACS Startup .92
E.1.2 Network Auto-Discovery.92
E.1.3 Managing Network Elements .93
E.1.4 Managing Network Topology .94
E.1.5 Real-Time Monitoring.94
E.1.5.1 Real-time Monitoring (Network Integration) .94
E.1.5.2 Real-time Monitoring (OSS
...