SIST ES 282 003 V3.4.1:2009
(Main)Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN) - Resource and Admission Control Sub-System (RACS) - Functional Architecture
Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN) - Resource and Admission Control Sub-System (RACS) - Functional Architecture
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.
Zlite telekomunikacijske in internetne storitve ter protokoli za napredno omreženje (TISPAN) - Podsistem za krmiljenje vira in pristopa (RACS) - Funkcijska arhitektura
General Information
Buy Standard
Standards Content (Sample)
ETSI ES 282 003 V3.4.1 (2009-09)
ETSI Standard
Telecommunications and Internet converged Services and
Protocols for Advanced Networking (TISPAN);
Resource and Admission Control Sub-System (RACS):
Functional Architecture
---------------------- Page: 1 ----------------------
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.: +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 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
---------------------- Page: 2 ----------------------
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
---------------------- Page: 3 ----------------------
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
---------------------- Page: 4 ----------------------
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
---------------------- Page: 5 ----------------------
6 ETSI ES 282 003 V3.4.1 (2009-09)
6.3.8.1.1 Overall features .
...
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
---------------------- Page: 1 ----------------------
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.: +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 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
---------------------- Page: 2 ----------------------
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
---------------------- Page: 3 ----------------------
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
---------------------- Page: 4 ----------------------
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
---------------------- Page: 5 ----------------------
6 Final draft ETSI ES 282 003 V3.4.0 (2009-07)
6.3.7.3.1.5 Policy Query Confirmation .
...
SLOVENSKI STANDARD
SIST ES 282 003 V3.4.1:2009
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)
SIST ES 282 003 V3.4.1:2009 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
---------------------- Page: 1 ----------------------
SIST ES 282 003 V3.4.1:2009
---------------------- Page: 2 ----------------------
SIST ES 282 003 V3.4.1:2009
ETSI ES 282 003 V3.4.1 (2009-09)
ETSI Standard
Telecommunications and Internet converged Services and
Protocols for Advanced Networking (TISPAN);
Resource and Admission Control Sub-System (RACS):
Functional Architecture
---------------------- Page: 3 ----------------------
SIST ES 282 003 V3.4.1:2009
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.: +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 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
---------------------- Page: 4 ----------------------
SIST ES 282 003 V3.4.1:2009
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
---------------------- Page: 5 ----------------------
SIST ES 282 003 V3.4.1:2009
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
---------------------- Page: 6 ----------------------
SIST ES 282 003 V3.4.1:2009
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 .
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.