hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
c1529897291b412e882d6d9bf84f7a00 | 183 011 | 1 Scope | The present document specifies the, stage three, Protocol Description of the Anonymous Communication Rejection (ACR) and Communication Barring (CB) simulation service, based on stage one and two of the ISDN supplementary service Anonymous Call Rejection (ACR), Incoming Communication Barring (ICB) and Outgoing Communication Barring (OCB). |
c1529897291b412e882d6d9bf84f7a00 | 183 011 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably, the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the method of access to the referenced document and the full network address, with the same punctuation and use of upper case and lower case letters. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity. |
c1529897291b412e882d6d9bf84f7a00 | 183 011 | 2.1 Normative references | The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] Void. [2] Void. [3] Void. [4] Void. [5] Void. [6] Void. [7] Void. [8] Void. [9] Void. [10] Void. [11] Void. ETSI ETSI TS 183 011 V1.4.0 (2008-06) 6 [12] Void. [13] Void. [14] Void. [15] Void. [16] Void. [17] Void. [18] ETSI TS 124 411: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); TISPAN; PSTN/ISDN simulation services: Anonymous Communication Rejection (ACR) and Communication Barring (CB); Protocol specification (Release 7)". |
c1529897291b412e882d6d9bf84f7a00 | 183 011 | 2.2 Informative references | The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. [i.1] Void. |
c1529897291b412e882d6d9bf84f7a00 | 183 011 | 3 Definitions and abbreviations | |
c1529897291b412e882d6d9bf84f7a00 | 183 011 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in TS 124 411 [18] apply. |
c1529897291b412e882d6d9bf84f7a00 | 183 011 | 3.2 Symbols | For the purposes of the present document, the abbreviations given in TS 124 411 [18] apply. 4 Anonymous Communication Rejection (ACR) and Communication Barring (CB) The provisions of the present document are contained in TS 124 411 [18]. ETSI ETSI TS 183 011 V1.4.0 (2008-06) 7 Annex A (informative): Signalling flows Information is contained in TS 124 411 [18]. ETSI ETSI TS 183 011 V1.4.0 (2008-06) 8 Annex B (informative): Example of filter criteria Information is contained in TS 124 411 [18]. ETSI ETSI TS 183 011 V1.4.0 (2008-06) 9 Annex C (informative): Change history Information is contained in TS 124 411 [18]. ETSI ETSI TS 183 011 V1.4.0 (2008-06) 10 History Document history V1.1.1 March 2006 Publication V1.2.1 March 2007 Publication V1.3.0 January 2008 Publication V1.4.0 June 2008 Publication |
45813f4893d229a0f50bab8d0dc65195 | 183 010 | 1 Scope | The present document specifies the, stage three, Protocol Description of the Communication Hold (HOLD) services, based on stages one and two of the ISDN Hold (HOLD) supplementary services. |
45813f4893d229a0f50bab8d0dc65195 | 183 010 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably, the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the method of access to the referenced document and the full network address, with the same punctuation and use of upper case and lower case letters. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity. |
45813f4893d229a0f50bab8d0dc65195 | 183 010 | 2.1 Normative references | The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] Void. [2] Void. [3] Void. [4] Void. [5] Void. [6] Void. [7] ETSI TS 124 410: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); TISPAN; NGN Signalling Control Protocol; Communication HOLD (HOLD) PSTN/ISDN simulation services; Protocol specification (3GPP TS 24.410 Release 8)". ETSI ETSI TS 183 010 V2.0.0 (2008-06) 6 |
45813f4893d229a0f50bab8d0dc65195 | 183 010 | 2.2 Informative references | The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. Not applicable. |
45813f4893d229a0f50bab8d0dc65195 | 183 010 | 3 Definitions and abbreviations | |
45813f4893d229a0f50bab8d0dc65195 | 183 010 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in TS 124 410 [7] apply. |
45813f4893d229a0f50bab8d0dc65195 | 183 010 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in TS 124 410 [7] apply. |
45813f4893d229a0f50bab8d0dc65195 | 183 010 | 4 Communication Hold (HOLD) | The provisions of the present document are contained in TS 124 410 [7]. ETSI ETSI TS 183 010 V2.0.0 (2008-06) 7 Annex A (informative): Signalling Flows Information is contained in TS 124 410 [7]. ETSI ETSI TS 183 010 V2.0.0 (2008-06) 8 History Document history V2.0.0 June 2008 Publication |
cf3dd9d16685a624f3065e75d79a3934 | 183 008 | 1 Scope | The present document specifies the stage three protocol description of the Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR) services. |
cf3dd9d16685a624f3065e75d79a3934 | 183 008 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably, the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the method of access to the referenced document and the full network address, with the same punctuation and use of upper case and lower case letters. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity. |
cf3dd9d16685a624f3065e75d79a3934 | 183 008 | 2.1 Normative references | The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] Void. [2] Void. [3] Void. [4] Void. [5] Void. [6] Void. [7] Void. [8] Void. [9] Void. [10] Void. [11] Void. [12] Void. ETSI ETSI TS 183 008 V2.8.0 (2008-06) 6 [13] Void. [14] Void. [15] Void. [16] Void. [17] Void. [18] ETSI TS 124 508: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); PSTN/ISDN simulation services Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR); Protocol specification (3GPP TS 24.508 Release 8)". |
cf3dd9d16685a624f3065e75d79a3934 | 183 008 | 2.2 Informative references | The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. Not applicable. |
cf3dd9d16685a624f3065e75d79a3934 | 183 008 | 3 Definitions and abbreviations | |
cf3dd9d16685a624f3065e75d79a3934 | 183 008 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in TS 124 508 [18] apply. |
cf3dd9d16685a624f3065e75d79a3934 | 183 008 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in TS 124 508 [18] apply. 4 Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR) The provisions of the present document are contained in TS 124 508 [18]. ETSI ETSI TS 183 008 V2.8.0 (2008-06) 7 Annex A (informative): Signalling flows Information is contained in TS 124 508 [18]. ETSI ETSI TS 183 008 V2.8.0 (2008-06) 8 Annex B (informative): Example of filter criteria Information is contained in TS 124 508 [18]. ETSI ETSI TS 183 008 V2.8.0 (2008-06) 9 Annex C (informative): Bibliography Information is contained in TS 124 508 [18]. ETSI ETSI TS 183 008 V2.8.0 (2008-06) 10 History Document history V2.4.1 August 2007 Publication V2.7.0 January 2008 Publication V2.8.0 June 2008 Publication |
b36a88927c23ee6dcefdad931f1db82d | 183 007 | 1 Scope | The present document specifies the stage three (protocol description) of the Originating Identification Presentation (OIP) simulation service and the Originating Identification Restriction (OIR) simulation services. |
b36a88927c23ee6dcefdad931f1db82d | 183 007 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably, the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the method of access to the referenced document and the full network address, with the same punctuation and use of upper case and lower case letters. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity. |
b36a88927c23ee6dcefdad931f1db82d | 183 007 | 2.1 Normative references | The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] Void. [2] Void. [3] Void. [4] Void. [5] Void. [6] Void. [7] Void. [8] Void. [9] Void. [10] Void. [11] Void. [12] Void. ETSI ETSI TS 183 007 V2.0.0 (2008-06) 6 [13] Void. [14] ETSI TS 124 407 : "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services: Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR); Protocol specification" (3GPP TS 24.407 Release 8). |
b36a88927c23ee6dcefdad931f1db82d | 183 007 | 2.2 Informative references | The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. Not applicable. |
b36a88927c23ee6dcefdad931f1db82d | 183 007 | 3 Definitions and abbreviations | |
b36a88927c23ee6dcefdad931f1db82d | 183 007 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in TS 124 407 [14] apply. |
b36a88927c23ee6dcefdad931f1db82d | 183 007 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in TS 124 407 [14] apply. 4 Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR) The provisions of the present document are contained in TS 124 407 [14]. ETSI ETSI TS 183 007 V2.0.0 (2008-06) 7 Annex A (informative): Signalling flows Information is contained in TS 124 407 [14]. ETSI ETSI TS 183 007 V2.0.0 (2008-06) 8 Annex B (informative): Example of filter criteria Information is contained in TS 124 407 [14]. ETSI ETSI TS 183 007 V2.0.0 (2008-06) 9 History Document history V2.0.0 June 2008 Publication |
0932a73014cee3bb138c11baa917f008 | 183 006 | 1 Scope | The present document specifies the stage three Protocol Description of the Message Waiting Indication (MWI) service, based on stage one and two of the ISDN MWI supplementary services. |
0932a73014cee3bb138c11baa917f008 | 183 006 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably, the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the method of access to the referenced document and the full network address, with the same punctuation and use of upper case and lower case letters. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity. |
0932a73014cee3bb138c11baa917f008 | 183 006 | 2.1 Normative references | The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] Void. [2] Void. [3] Void. [4] Void. [5] Void. [6] Void. [7] Void. [8] Void. [9] Void. [10] Void. [11] Void. [12] Void. ETSI ETSI TS 183 006 V2.0.0 (2008-06) 6 [13] Void. [14] ETSI TS 124 406: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); TISPAN; PSTN/ISDN simulation services; Message Waiting Indication (MWI): Protocol specification (Release 8)". |
0932a73014cee3bb138c11baa917f008 | 183 006 | 2.2 Informative references | The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. Not applicable. |
0932a73014cee3bb138c11baa917f008 | 183 006 | 3 Definitions and abbreviations | |
0932a73014cee3bb138c11baa917f008 | 183 006 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in TS 124 406 [14] apply. |
0932a73014cee3bb138c11baa917f008 | 183 006 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in TS 124 406 [14] apply. |
0932a73014cee3bb138c11baa917f008 | 183 006 | 4 Message Waiting Indication (MWI) | The provisions of the present document are contained in TS 124 406 [14]. ETSI ETSI TS 183 006 V2.0.0 (2008-06) 7 Annex A (informative): Example signalling flows of Message Waiting Indication (MWI) service operation Information is contained in TS 124 406 [14]. ETSI ETSI TS 183 006 V2.0.0 (2008-06) 8 Annex B (informative): Example of a filter criteria Information is contained in TS 124 406 [14]. ETSI ETSI TS 183 006 V2.0.0 (2008-06) 9 Annex C (informative): Bibliography Information is contained in TS 124 406 [14]. ETSI ETSI TS 183 006 V2.0.0 (2008-06) 10 Annex D (informative): Change history Information is contained in TS 124 406 [14]. ETSI ETSI TS 183 006 V2.0.0 (2008-06) 11 History Document history V2.0.0 June 2008 Publication |
175afaf5bce693d8f68e5589b88b7b21 | 183 005 | 1 Scope | The present document specifies the, stage three, Protocol Description of the Conference (CONF) service based on stage one and two of the ISDN CONF supplementary service. |
175afaf5bce693d8f68e5589b88b7b21 | 183 005 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably, the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the method of access to the referenced document and the full network address, with the same punctuation and use of upper case and lower case letters. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity. |
175afaf5bce693d8f68e5589b88b7b21 | 183 005 | 2.1 Normative references | The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] Void. [2] Void. [3] Void. [4] Void. [5] Void. [6] Void. [7] Void. [8] Void. [9] Void. [10] Void. [11] Void. ETSI ETSI TS 183 005 V2.6.0 (2008-06) 6 [12] ETSI TS 124 505: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); TISPAN; PSTN/ISDN simulation services: Conference (CONF); Protocol specification (3GPP TS 24.505 Release 8)". |
175afaf5bce693d8f68e5589b88b7b21 | 183 005 | 2.2 Informative references | The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. Not applicable. |
175afaf5bce693d8f68e5589b88b7b21 | 183 005 | 3 Definitions and abbreviations | |
175afaf5bce693d8f68e5589b88b7b21 | 183 005 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in TS 124 505 [12] apply. |
175afaf5bce693d8f68e5589b88b7b21 | 183 005 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in TS 124 505 [12] apply. |
175afaf5bce693d8f68e5589b88b7b21 | 183 005 | 4 CONFerence (CONF) | The provisions of the present document are contained in TS 124 505 [12]. ETSI ETSI TS 183 005 V2.6.0 (2008-06) 7 Annex A (informative): Signalling flows Information is contained in TS 124 505 [12]. ETSI ETSI TS 183 005 V2.6.0 (2008-06) 8 History Document history V2.5.0 January 2008 Publication V2.6.0 June 2008 Publication |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 1 Scope | The present document defines a specification applicable to the Rr interface between Generic Resource Admission Control Function (x-RACF) instances, based on the Diameter protocol. Other alternative protocols which may also be used for this interface such as ANCP are not specified in the present document. Whenever it is possible the present document specifies the requirements for this protocol by reference to specifications produced by the IETF within the scope of Diameter. Where this is not possible, extensions to Diameter are defined within the present document. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 2.1 Normative references | The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] ETSI ES 282 001 (V3.y.z): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Functional Architecture". [2] ETSI ES 282 003 (V3.y.z): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control Sub-System (RACS): Functional Architecture". [3] ETSI ES 282 004 (V3.y.z): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Functional Architecture; Network Attachment Sub- System (NASS)". [4] ETSI ES 283 034 (V2.y.z): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Network Attachment Sub-System (NASS); e4 interface based on the DIAMETER protocol". [5] ETSI TS 183 017 (V3.y.z): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN);Resource and Admission Control: DIAMETER protocol for session based policy set-up information exchange between the Application Function (AF) and the Service Policy Decision Function (SPDF); Protocol specification". [6] IETF RFC 4006: "Diameter Credit-Control Application". ETSI ETSI TS 183 071 V3.1.1 (2010-02) 8 [7] ETSI TS 129 209: "Universal Mobile Telecommunications System (UMTS); Policy control over Gq interface (3GPP TS 29.209)". [8] IETF RFC 3588: "Diameter Base Protocol". [9] IETF RFC 4005: "Diameter Network Access Server Application". [10] ETSI TS 183 026 (V3.y.z): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control; Protocol for QoS reservation information exchange between the Service Policy Decision Function (SPDF) and the Access Resource and Admission Control Function (A-RACF) In the Resource and Protocol specification". [11] ETSI TS 133 210: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; 3G security; Network Domain Security (NDS); IP network layer security (3GPP TS 33.210 )". [12] IETF RFC 4960: "Stream Control Transmission Protocol". [13] ETSI TS 129 207: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Policy control over Go interface (3GPP TS 29.207)". [14] IETF RFC 3554: "On the Use of Stream Control Transmission Protocol (SCTP) with IPSec". [15] ETSI TS 129 329: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Sh interface based on the Diameter protocol; Protocol details (3GPP TS 29.329)". |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 2.2 Informative references | The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. Not applicable. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 3 Definitions and abbreviations | |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: delegated x-RACF: x-RACF instance which works in the Rr delegated Model and performs admission control for the resources delegated by the delegating x-RACF delegating x-RACF: x-RACF instance which works in the Rr delegated Model and delegates a bulk of resources to another x-RACF instance for admission control |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: AAA AA-Answer AAR AA-Request ABNF Augmented Backus–Naur Form AF Application Function ANCP Access Node Control Protocol ASA Abort-Session-Answer ASR Abort-Session-Request ETSI ETSI TS 183 071 V3.1.1 (2010-02) 9 ATM Asynchronous Transfer Mode AVP Attribute-Value Pair CCA CC-Answer CCR CC-Request CEA Capabilities-Exchange-Answer CER Capabilities-Exchange-Request DHCP Dynamic Host Configuration Protocol FQDN Fully Qualified Domain Name IANA Internet Assigned Numbers Authority ID IDentifier IETF Internet Engineering Task Force IP Internet Protocol IPSec IP Security NASREQ Network Access Server Application NASS Network Attachment Sub-System PNA Push-Notification-Answer PNR Push-Notification-Request QoS Quality of Service RAA Re-Auth-Answer RACS Resource and Admission Control Sub-System RAR Re-Auth-Request RCEF Resource Control Enforcement Function RFC Request For Comments Rr reference point Rr RTCP Realtime Transport Control Protocol SCTP Stream Control Transport Protocol SDI Session Description Information SPDF Service-based Policy Decision Function STA Session-Termination-Answer STR Session-Termination-Request TISPAN Telecommunications and Internet converged Services and Protocols for Advanced Networking UDA User-Data-Answer UDR User-Data-Request UE User Equipment VC Virtual Channel VP Virtual Path x-RACF Generic Resource Admission Control Function ETSI ETSI TS 183 071 V3.1.1 (2010-02) 10 |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 4 Overview | The present document specifies the Diameter protocol for the RACS Rr interface. The Rr interface is used for QoS resource reservation between x-RACF instances of RACS within a single administrative domain. The functional requirements and the stage 2 specifications of the Rr interface are contained in ES 282 001 [1] and ES 282 003 [2]. Figure 4.1: Rr interface |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 5 Procedure descriptions | |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 5.1 General | |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 5.1.1 Information elements | The following clauses describe the realization of the functional procedures defined in the RACS (ES 282 003 [2]) using Diameter commands described in clauses 6 and 7. This involves describing a mapping between the Information Elements defined in the RACS specification (ES 282 003 [2]) and Diameter AVPs. In the tables that describe this mapping, each Information Element is marked as (M) Mandatory, (C) Conditional or (O) Optional: • A mandatory Information Element (marked as (M) in the table) shall always be present in the command. If this Information Element is absent, an application error occurs at the receiver and an answer message shall be sent back to the originator of the request with the Result-Code set to DIAMETER_MISSING_AVP. This message shall also include a Failed-AVP AVP containing the missing Information Element i.e. the corresponding Diameter AVP defined by the AVP Code and the other fields set as expected for this Information Element. • A conditional Information Element (marked as (C) in the table) shall be present in the command if certain conditions are fulfilled: - If the receiver detects that those conditions are fulfilled and the Information Element is absent, an application error occurs and an answer message shall be sent back to the originator of the request with the Result-Code set to DIAMETER_MISSING_AVP. This message shall also include a Failed-AVP AVP containing the missing Information Element i.e. the corresponding Diameter AVP defined by the AVP Code and the other fields set as expected for this Information Element. If multiple Information Elements are missing, all corresponding AVP codes shall be included in the Failed-AVP AVP. Rr x - RACF AF SPDF BGF RCEF NASS Re Ia Gq ’ Rd’, Ri ’ Rq e4 Transport Processing Functions RACS BTF Rf Rr x - RACF AF SPDF BGF RCEF NASS Re Ia Gq ’ Rd’, Ri ’ Rq e4 Transport Processing Functions RACS BTF Rf ETSI ETSI TS 183 071 V3.1.1 (2010-02) 11 - If those conditions are not fulfilled, the Information Element shall be absent. If however this Information Element appears in the message, it shall not cause an application error and it may be ignored by the receiver if this is not explicitly defined as an error case. Otherwise, an application error occurs at the receiver and an answer message with the Result-Code set to DIAMETER_AVP_NOT_ALLOWED shall be sent back to the originator of the request. A Failed-AVP AVP containing a copy of the corresponding Diameter AVP shall be included in this message. • An optional Information Element (marked as (O) in the table) may be present or absent in the command, at the discretion of the application at the sending entity. Absence or presence of this Information Element shall not cause an application error and may be ignored by the receiver. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 5.2 Procedures on the Rr interface | |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 5.2.1 Resource control procedures for Request Model | The resource control process supports the following operations: 1) Resource Reservation: the resources are admitted by the requested entity (e.g. lower-tier x-RACF). In relation to the enforcement operations performed in the co-located RCEF, it can be divided into the following categories: - Reservation only: the resources are reserved but not allocated. - Commit only: the pre-reserved resources are allocated. - Reservation and commit: the resources are reserved and allocated. 2) Resource Modification: the pre-reserved/committed resources are updated upon the request of the originating entity (e.g. top-tier x-RACF). 3) Resource Release: the pre-reserved/committed resources are terminated upon the request of the originating entity. 4) Event notification: a specific action is requested when a pre-defined event occurs (e.g. reservation expiration). The Flow-Status AVP is used to define the action to be taken for each AA-Request made by the top-tier x-RACF to the lower-tier x-RACF. The rules for interpreting the Flow-Status AVP are the following: • Resource Reservation: can be invoked by any of the following status: - Reservation only: New Media-Description-Component AVP(s) and optionally Media-Sub-Component AVP(s) with Flow-Status AVP(s) set to DISABLED (3). - Commit only: Media-Description-Component AVP(s) and optionally Media-Sub-Component AVP(s) of existing reservations with Flow-Status AVP(s) set to ENABLED-UPLINK (0), ENABLED-DOWNLINK (1) or ENABLED (2). - ReservationAndCommit: New Media-Component-Description AVP(s) and optionally Media-Sub-Component AVP(s). Flow-Status AVP(s) set to ENABLED-UPLINK (0), ENABLED-DOWNLINK (1) or ENABLED (2). NOTE: For the purpose of the resource admission and reservation, any of above status triggers the procedure. The distinction of above flow status is only meaningful in the case the lower-tier x-RACF needs to control the enforcement operations (e.g. Opening the gate) in the co-located RCEF. • Resource Modification: Updated Media-Description-Component AVP(s) and Media-Sub-Component AVP(s). Flow-Status AVP not modified, unless the state needs to be modified (e.g. for committing a resource reservation, or for releasing a resource reservation). • Resource Release: Media-Description-Component AVP(s) and optionally Media-Sub-Component AVP(s) of existing reservations with Flow-Status AVP(s) set to REMOVED (4). ETSI ETSI TS 183 071 V3.1.1 (2010-02) 12 These resource control operations are described in the following clauses. During the operations Diameter AVPs are passed between the top-tier x-RACF and the lower-tier x-RACF. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 5.2.1.1 Procedures at the Top-tier x-RACF | |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 5.2.1.1.1 Resource Reservation Session Establishment and Initial Resource Reservation | Upon the receipt of a new request from the SPDF, the top-tier x-RACF sends an initial request to the lower-tier x-RACF for initiating a resource reservation session. The AA-Request issued to request an initial reservation contains a new Session-Id assigned by the top-tier x-RACF. As specified in RFC 3588 [8], the Session-Id is globally unique and is meant to uniquely identify a resource session without reference to any other information. The Session-Id begins with the sender's identity encoded in the DiameterIdentity type. This AA-Request message contains one or more Media-Component-Description Attribute-Value Pair(s) (AVP(s)). Each Media-Component-Description AVP describes the set of flows of a particular media type (i.e. it may contain one or more Media-Sub-Component AVP(s) and requirements for the flows). The top-tier x-RACF may forward an AF-Charging-Identifier AVP from the SPDF in the message for charging correlation purposes between AF and RACS. The resource admission and reservation operation that shall be performed by the lower-tier x-RACF for each individual media and flow is triggered by the following value of the Flow-Status AVP, as indicated in table 5.1: • Reservation; the value of the Flow-Status AVP shall be set to DISABLED (3). • ReservationAndCommit; the value of the Flow-Status AVP shall be set to ENABLED-UPLINK (0), ENABLED-DOWNLINK (1) or ENABLED (2). • The Flow-Status AVP shall be specified in the Media-Component-Description AVP and in the Media-Sub-Component AVP(s). The Flow-Status AVP shall be set to the same value in both these AVPs. Table 5.1: Initial Reservation operations Message Type Flow-Status AVP at the level of Meaning Media Sub-Media AAR New Media, DISABLED New flow, DISABLED Reserve Resources for all the flows in the request. The media(s) and flow(s) descriptions MUST be new ones. AAR [New Media, ENABLE*] New flow, ENABLE* Reserve Resources. In addition, instruct the co-located RCEF to commit resources for some of the flows. The media(s) and flow(s) descriptions MUST be new ones (see note). NOTE: The control of committing resources in the co-located RCEF is an implementation choice and out of scope in the present document. As specified in clause 8.9 of RFC 3588 [8], the top-tier x-RACF may specify the Authorization-Lifetime AVP in the AA-Request to request a maximum lifetime for a session. To request a hard-state session the top-tier x-RACF shall omit the Authorization-Lifetime AVP in the AA-Request. To request a soft-state session the top-tier x-RACF shall specify this AVP in the AA-Request. The AA-Answer may contain the Authorization-Lifetime AVP. The AA-Answer may contain the Auth-Grace-Period AVP in addition to the Authorization-Lifetime AVP. The Authorization-Lifetime AVP specifies the maximum number of seconds before the Session must be refreshed by the top-tier x-RACF. The Auth-Grace-Period AVP contains the number of seconds the lower-tier x-RACF will wait for a Refresh following the expiration of the Authorization- Lifetime AVP. Whether the Authorization-Lifetime AVP and Auth-Grace-Period need to be included in the AA-Answer is a local decision of the lower-tier x-RACF. This means that the top-tier x-RACF may be offered a soft-state reservation although it asked for hard-state or a hard-state reservation although it asked for soft-state. Should the top-tier x-RACF not accept what is offered by the lower-tier x-RACF it must explicitly release the resources through issuing another AAR command. The top-tier x-RACF may specify, in the Specific-Action AVP of the AA-Request through which the initial reservation request is made, the events of which it wants to be informed. The supported events are listed in clause 6.5.9. ETSI ETSI TS 183 071 V3.1.1 (2010-02) 13 The behaviour when the top-tier x-RACF does not receive an AA-Answer, or when it arrives after the internal timer waiting for it has expired, or when it arrives with an indication different than DIAMETER_SUCCESS, is outside the scope of the present document. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 5.2.1.1.2 Resource Modification and Release for Media Flows | The top-tier x-RACF may modify an existing session by sending an AA-Request to the lower-tier x-RACF with zero or more updated Media-Component-Description AVP(s) and optional Media-Sub-Component AVP(s). The Session-Id shall be an existing one and refer to the session that is to be modified. The top-tier x-RACF may perform the following operations: • Add a new flow within a media component by providing a new Media-Sub-Component AVP within the corresponding Media-Component-Description AVP. • Add a new flow within a new media component by providing a new Media-Component-Description AVP. • Modify a media component by updating the corresponding Media-Component-Description AVP (e.g. increase or decrease the allocated bandwidth). • Modify a flow within a media component by updating the corresponding Media-Sub-Component AVP. • Modify a media flow state from Reserved to Committed by providing a Flow-Status AVP of the corresponding Media-Component-Description AVP and/or Media-Sub-Component AVP(s). The Flow-Status AVP shall be set to one of the values ENABLED-UPLINK, ENABLED-DOWNLINK or ENABLED, according to the direction in which the resources are to be committed. This operation requires that the media and flows are in the Reserved state prior to the AA-Request. • Release a media component by providing the corresponding Media-Component-Description AVP with the Flow-Status AVP set to the value REMOVED. • Release a flow within a media by providing the corresponding Media-Sub-Component AVP with the Flow-Status AVP set to the value REMOVED. • Refresh a soft-state session by providing an AA-Request message containing the Session-Id of the session that is to be refreshed. The AA-Request may contain the Authorization-Lifetime AVP to request a maximum lifetime of the refreshed session. If this AVP is not included, the refresh message requests the lifetime to be extended by a default value. The AA-Request may contain Media-Component-Description AVP(s) and Media-Sub-Component AVP(s) (e.g. to modify media, flows and/or commit status). The Flow-Status AVP in the Media-Sub-Component AVP shall always be the same as the Flow-Status AVP in the Media-Component-Description AVP containing the Media-Sub-Component AVP. The top-tier x-RACF SHALL NOT use the RAA to modify the session service information. As an option, the top-tier x-RACF MAY send an AAR command following an RAA to update the session service information after the local RACF responds with the RAR. ETSI ETSI TS 183 071 V3.1.1 (2010-02) 14 Table 5.2: Modification operations Message Type Flow-Status AVP at the level of Meaning Media Sub-Media AAR Existing Media Existing Flow, Unchanged Flow-Status Modify a media. In addition, modify a flow according to the new parameters specified in the Media-Sub-Component AVP. The Media and Flow must exist (see notes 1, 2 and 5). AAR Existing Media New flow. Same Flow-Status AVP as in the media. (see note 3) Modify a media. In addition, add a new flow in a media. The Flow must be new (see notes 3 and 5). AAR Existing Media (see note 4) REMOVED Modify a media. In addition, release an existing flow within an existing media. If the flow does not exist, the request shall be ignored by the lower-tier x-RACF (see notes 2 and 5). AAR Existing Media, Modified Flow-Status AVP = REMOVED Existing Flow, Flow-Status AVP = REMOVED Release the resources of the media. AAR Existing Media Existing Flow (see note 5). NOTE 1: If the media is not an existing one, the AAR is interpreted as a reservation for a new media (clause 5.2.1.1). NOTE 2: The parameters specified at flow-level (in the Media-Sub-Component AVP(s)) take precedence over the parameters specified at media-level (in the updated Media-Component-Description AVP). NOTE 3: The Flow-Status AVP of a new flow within a media shall be the same as the Flow-Status of the media. NOTE 4: As the Modification operation is also used for the Commit operation, the Flow-Status AVP of the Media-Component-Description AVP may actually be modified. NOTE 5: In the case of a soft-state reservation, extend its lifetime. The behaviour when the top-tier x-RACF does not receive an AA-Answer, or when it arrives after the internal timer waiting for it has expired, or when it arrives with an indication different than DIAMETER_SUCCESS, is outside the scope of the present document. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 5.2.1.1.3 Termination and Release of the Resources for a Resource Reservation Session | The top-tier x-RACF may issue a Session-Termination-Request (STR) command to the lower-tier x-RACF when it decides to terminate a resource reservation session and release all the resources. The session termination may be triggered by the explicit request from the SPDF or the expiry of the session or the inactivity of applications based on network policy. This command releases all the resources associated with the session identified by the provided Session-Id AVP. Table 5.3: Resource release operations Message Type Flow-Status AVP at the level of Meaning Media Sub-Media STR Release a session: all the media(s) and flow(s) within that session are released. When receiving an Abort-Session-Request (ASR) message from the lower-tier x-RACF, the top-tier x-RACF shall – if the session involves the resources in other network segments – release those resources and inform the SPDF of that the resources identified by the Session-Id AVP have been released. If the ASR message contains one or more Session-Bundle-Id AVPs the top-tier x-RACF shall perform these procedures for all sessions associated with the Session-Bundle-Id AVP(s). |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 5.2.1.1.4 Event notification | Notifications for specific events may be implicitly requested through policies established in the lower-tier x-RACF. The top-tier x-RACF may further specify, in the Specific-Action AVP of an initial AA-Request command, the events of which it wants to be informed. The supported events are listed in clause 6.5.9. ETSI ETSI TS 183 071 V3.1.1 (2010-02) 15 |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 5.2.1.2 Procedures at the lower-tier x-RACF | |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 5.2.1.2.1 Initial Resource Reservation | When the lower-tier x-RACF receives a reservation request in which the Session-Id is new, it is interpreted by the lower-tier x-RACF as a new resource reservation session. An initial AA-Request may contain one or more Media-Component-Description AVP(s) optionally including one or more Media-Sub-Component AVP(s). If the initial AA-Request does not contain any Media-Component-Description AVP(s), the lower-tier x-RACF will establish the Diameter session as the idle state without further operations. Upon reception of an AF-Application-Identifier AVP in an initial AA-Request from the top-tier x-RACF, the lower-tier x-RACF shall store this identifier together with the states created and maintained for the new session for the purpose of charging correlation between AF and RACS. The identifier is opaque to the lower-tier x-RACF. As defined in ES 282 003 [2], the top-tier x-RACF identifies a QoS profile based on the Subscriber ID and/or the Globally Unique IP Address. The QoS profile includes the Physical Access ID, Logical Access ID and Access Network Type. The lower-tier x-RACF does not interact with the NASS directly. Instead, the top-tier x-RACF maintains the QoS profiles, selects the right one and pushes the relevant information (e.g. QoS info) down to the lower-tier x-RACF. To identify a specific customer on the lower-tier x-RACF, the top-tier x-RACF shall convey the Logical Access ID, and optionally the Globally Unique IP Address. The mapping of these parameters to the Diameter AVPs is described in table 5.4. If the lower-tier x-RACF does not receive one of these parameters at least the Logical-Access-Id AVP, it shall return an AA-Answer that include a Result-Code AVP set to the value DIAMETER_MISSING_AVP. The Failed-AVP AVP should be included in the message. The Failed-AVP AVP must contain an example of the missing AVP. The value field of the missing AVP example should be of correct minimum length and contain zeroes. Table 5.4: Mapping of information element names to Diameter AVPs Information element name Mapping to Diameter AVP Categorie Logical Access ID (The identity of the logical access to which the user equipment is connected. See note) Logical-Access-Id M Subscriber ID in RACS [2] and in NASS [3] User-Name O Globally Unique IP Address in RACS [2] and in NASS [3] Globally-Unique-Address O Requestor Name in RACS [2] AF-Application-Identifier O Media Type in NASS [3] and in RACS [2] Media-Type O Reservation Class in RACS [2] Reservation-Class O Transport Service Class in RACS [2] and in NASS [3] Transport-Class O Service Class in RACS [2] Service-Class O NOTE: The Logical Access ID identifies the logical access used by the attached user equipment. In the xDSL case, the Logical Access ID may explicitly contain the identifier of VP and/or VC carrying the traffic. Can be used as the agent circuit ID present in DHCP option 82, including <Access-Node-Identifier> atm <rack>/<shelf>/<slot>/<DSL-Line>:<VPI.<VCI>. Any value of the Flow-Status AVP received in an initial AA-Request (in which the Session-Id is new) different from ENABLED-UPLINK, ENABLED-DOWNLINK, ENABLED or DISABLED shall result in an error. If the Flow-Status AVP has the value REMOVED the lower-tier x-RACF shall return an AA-Answer containing a Failed-AVP AVP and a Result-Code AVP with the value DIAMETER_INVALID_AVP_VALUE. In case the operation fails due to lack of resources, the lower-tier x-RACF shall include the Experimental-Result-Code AVP set to the value INSUFFICIENT_RESOURCES. An initial reservation request can be admitted by the lower-tier x-RACF if for all media streams in the session, the resource requirements fit within the constraints of remaining envelopes of unused resources. The lower-tier x-RACF is presumed to exhibit "atomic" reservation semantics (i.e. either all reservations are admitted, or none of them). Once a reservation is admitted, the corresponding amount of resources is removed from the pool of available resources. ETSI ETSI TS 183 071 V3.1.1 (2010-02) 16 If the request is admitted the lower-tier x-RACF must send an AA-Answer back to the top-tier x-RACF and include the Result-Code AVP set to the value DIAMETER_SUCCESS. Upon successful reservation, the lower-tier x-RACF shall store the Diameter base protocol Session-Id received in the AA-Request through which the initial reservation request was made, and the Media-Component-Number(s) and Flow-Number(s). The AA-Request may contain the Authorization-Lifetime AVP. The lower-tier x-RACF shall interpret the presence of the Authorization-Lifetime AVP as a request for a soft-state reservation and the absence of this AVP as a request for a hard-state reservation. The lower-tier x-RACF may however return the Authorization-Lifetime AVP or the pair of Authorization-Lifetime AVP and Auth-Grace-Period AVP although the AA-Request did not contain the Authorization-Lifetime AVP. The lower-tier x-RACF thereby offers a soft-state reservation although the request was for hard-state. The lower-tier x-RACF may also choose not to return the Authorization-Lifetime AVP and the Auth-Grace-Period AVP although the AA-Request contained the Authorization-Lifetime AVP. The lower-tier x-RACF thereby offers a hard-state reservation although the request was for soft-state reservation. The Authorization-Lifetime indicates when the lower-tier x-RACF expects a Refresh from the top-tier x-RACF. The Auth-Grace-Period AVP can only be specified in addition to the Authorization-Lifetime AVP. As specified in clause 8.9 of RFC 3588 [8] the Diameter server (i.e. the lower-tier x-RACF) may return the Authorization-Lifetime AVP set to a value equal to, or smaller than the value of the Authorization-Lifetime AVP provided by the top-tier x-RACF. The lower-tier x-RACF may include one or more Session-Bundle-Id AVPs in the AA-Answer. The Session-Bundle-Id AVP identifies a group of sessions to which the session belongs. The value of this AVP and the sessions that belong to a certain such value are chosen by the lower-tier x-RACF. The value of the Session-Bundle-Id AVP is meaningful only for the lower-tier x-RACF. If the Specific-Action AVP is included in the initial AA-Request, notification for the given event(s) shall be activated by the lower-tier x-RACF. The supported events are listed in clause 6.5.8. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 5.2.1.2.2 Resource Modification and Release for Media Flows | When the lower-tier x-RACF receives requests in which both the Session-Id and the Media-Component-Number(s) and Flow-Number(s) of existing reservations are existing ones, it performs the resource admission and reservation for modified flows. An AA-Request issued to modify an existing session may contain zero or more Media-Component-Description AVP(s) optionally including one or more Media-Sub-Component AVP(s). Media-Component-Number(s) and Flow-Number(s) of new Media-Component-Description AVP(s) and Media-Sub-Component AVP(s) are interpreted by the lower-tier x-RACF as new ones. For an AA-Request issuing a session modification operation the Flow-Status AVP must be set to a value representing a state to which the session is allowed to enter from its current state. Should the Flow-Status AVP be set to a disallowed value the lower-tier x-RACF shall return an AA-Answer containing a Failed-AVP AVP and a Result-Code AVP with the value DIAMETER_INVALID_AVP_VALUE. In the case the lower-tier x-RACF also needs to control the enforcement of the resources, if the lower-tier x-RACF is unable to modify the status of a reservation to ENABLED-UPLINK, ENABLED-DOWNLINK or ENABLED, the lower-tier x-RACF shall issue an error message to the top-tier x-RACF with an Experimental-Result-Code AVP set to the value COMMIT_FAILURE. If the status of a reservation is one of the values ENABLED-UPLINK, ENABLED-DOWNLINK or ENABLED, the AA-Request should not contain a Flow-Status AVP set to DISABLED. If it does, the lower-tier x-RACF shall return an AA-Answer to the top-tier x-RACF with an Experimental-Result-Code AVP set to the value MODIFICATION_FAILURE. If the lower-tier x-RACF is not able to re-initialize the lifetime of the reservation, it shall return an AA-Answer to the top-tier x-RACF with an Experimental-Result-Code AVP set to the value REFRESH_FAILURE. If a flow-level operation fails, the entire Resource Modification operation fails. In the case the lower-tier x-RACF determines that the request cannot be admitted due to insufficient resources, it shall return an Experimental-Result-Code AVP to the top-tier x-RACF set to the value INSUFFICIENT_RESOURCES. In case the Specific-Action AVP, the AF-Charging-Identifier AVP, the User-Name AVP or the Globally-Unique- Address AVP was provided in an initial AA-Request with a value different from the value of the AVP(s) in a modifying AA-Request, the lower-tier x-RACF shall return an AA-Answer containing a Failed-AVP AVP and a Result-Code AVP with the value DIAMETER_INVALID_AVP_VALUE. Upon successful session modification, the lower-tier x-RACF must send an AA-Answer back to the top-tier x-RACF with the Result-Code AVP set to DIAMETER_SUCCESS. ETSI ETSI TS 183 071 V3.1.1 (2010-02) 17 Upon a successful refresh operation, the lower-tier x-RACF shall in the AA-Answer return the Authorization-Lifetime AVP with a value equal or smaller than the Authorization-Lifetime AVP of the AA-Request (if any). The Auth-Grace-Period AVP can only be specified in addition to the Authorization-Lifetime AVP. Whether Authorization-Lifetime AVP and Auth-Grace-Period AVP need to be specified in the AA-Answer is a local decision for the lower-tier x-RACF. If a reference to a previously negotiated Media-Component-Description AVP and/or Media-Sub-Component AVP for the session in question is omitted in the AA-Request, the corresponding flow is not impacted by the Modification operation. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 5.2.1.2.3 Termination and Release of the Resources for a Resource Reservation Session | If all resources within an established resource reservation session need to be terminated, the lower-tier x-RACF shall inform the top-tier x-RACF about this event by sending an Abort-Session-Request (ASR) message with the appropriate Abort-Cause AVP value, and all resources within the authorized session will be released. The lower-tier x-RACF may include one or more Session-Bundle-Id AVPs in order to inform the top-tier x-RACF of that several sessions identified by the provided Session-Bundle-Id AVP(s) are terminated. Upon receipt of a Session-Termination-Request (STR) message from the top-tier x-RACF the lower-tier x-RACF shall release all the resources associated with the session identified through the provided Session-Id AVP. If an unknown Session-Id is provided in the STR the lower-tier x-RACF shall return a Session-Termination-Answer (STA) message to the top-tier x-RACF with the Result-Code AVP set to DIAMETER_UNKNOWN_SESSION_ID. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 5.2.1.2.4 Event Notification | If an event for which notification is required occurs, the lower-tier x-RACF shall send an unsolicited Re-Auth-Request (RAR) message to the top-tier x-RACF containing: • The value of the Specific-Action AVP, indicating the event that occurred. • Optionally, the appropriate Abort-Cause AVP value. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 5.2.2 Procedures for Delegated Model | 5.2.2.1 Delegation Push triggered by the delegating x-RACF This procedure is used for the delegating x-RACF to push the delegation information to the delegated x-RACF. This information flow occurs at the initial provisioning stage or when the delegating x-RACF decides to synchronize the delegation information between the delegating x-RACF and the delegated x-RACF. This procedure is mapped to the commands Push-Notification-Request/Answer in the Diameter application specified in clause 7. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 5.2.2.1.1 Procedures at the delegating x-RACF | The delegating x-RACF shall obtain the address of the delegated x-RACF entity where the information should be pushed (e.g. from configuration data). The delegating x-RACF shall populate the Push-Notification-Request as follows: • The Network-Resource-Id AVP shall be present and shall contain the identifier of the network resource to be delegated. • At least one of Granted-Delegated-Bandwidth-UL and Granted-Delegated-Bandwidth-DL AVP shall be present. • The presence of Total-Bandwidth-UL and Total-Bandwidth-DL AVP depends on the network resource and local policy rules. The Preferred-Delegated-Bandwidth-UL, Preferred-Delegated-Bandwidth-DL, Required-Delegated-Bandwidth-UL, Required-Delegated-Bandwidth-DL and Reservation-priority AVPs shall not be present. ETSI ETSI TS 183 071 V3.1.1 (2010-02) 18 |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 5.2.2.1.2 Procedures at the delegated x-RACF | On receipt of the Push-Notification-Request with at least either of the Granted-Delegated-Bandwidth-UL and Granted-Delegated-Bandwidth-DL AVPs, the delegated x-RACF take the Push-Notification-Request as the delegation push request. If there is no delegation record with the network resource identifier contained in the Network-Resource-Id AVP as a key, the delegated x-RACF shall create an internal record to store the received information for future use. If there is a delegation record with the network resource identifier contained in the Network-Resource-Id AVP as a key, the delegated x-RACF shall replace the entire content of the internal record with the received information for future use. Such an update shall not have any impact on ongoing application sessions for which an authorization has already been provided by the delegating x-RACF. If the contents of the request are invalid the delegated x-RACF shall return a Push-Notification-Answer with a Result-Code AVP value set to the appropriate value as described in clause 5.1. If the delegated x-RACF cannot fulfil the received request for reasons not stated in the above steps, e.g. due to database error, it shall stop processing the request and return a Push-Notification-Answer with a Result-Code AVP value set to DIAMETER_UNABLE_TO_COMPLY or an Experimental-Result-Code AVP set to DIAMETER_SYSTEM_UNAVAILABLE. In the later case, the delegating x-RACF is expected to retry after a provisioned time period. Otherwise, the requested operation shall take place and the delegated x-RACF shall return the Result-Code AVP set to DIAMETER_SUCCESS in the Push-Notification-Answer. The Granted-Delegated-Bandwidth-UL and Granted-Delegated-Bandwidth-DL should not be present in the Push-Notification-Answer. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 5.2.2.2 Delegation Negotiation triggered by the delegated x-RACF | This procedure is used for the delegated x-RACF to negotiate the delegation with the delegating x-RACF. This information flow occurs normally when there is insufficient delegated bandwidth for a new application session on the delegated x-RACF. This procedure is mapped to the commands User-Data-Request/Answer in the Diameter application specified in clause 7. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 5.2.2.2.1 Procedures at the delegated x-RACF | The delegated x-RACF shall populate the User-Data-Request as follows: • The Network-Resource-Id AVP shall be present and shall contain the identifier of the network resource to be delegated. • At least one of the Required-Delegated-Bandwidth-UL and Required-Delegated-Bandwidth-DL AVP shall be present. • The Preferred-Delegated-Bandwidth-UL, Preferred-Delegated-Bandwidth-DL and Reservation-priority AVPs may be present optionally. If the Required-Delegated-Bandwidth-UL AVP is not present, the Preferred- Delegated-Bandwidth-UL AVP shall not be present. If the Required-Delegated-Bandwidth-DL AVP is not present, the Preferred-Delegated-Bandwidth-DL AVP shall not be present. On receipt of the corresponding User-Data-Answer with the Result-Code AVP set to DIAMETER_SUCCESS and at least either of the Granted-Delegated-Bandwidth-UL and Granted-Delegated-Bandwidth-DL AVPs, the delegated x-RACF updates the corresponding content of the internal record with the received information for future use (e.g. allocating the resource for pending application sessions). |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 5.2.2.2.2 Procedures at the delegating x-RACF | On receipt of the User-Data-Request with at least either of the Required-Delegated-Bandwidth-UL and Required- Delegated-Bandwidth-DL AVPs, the delegating x-RACF takes the User-Data-Request as the delegation negotiation request. ETSI ETSI TS 183 071 V3.1.1 (2010-02) 19 If the contents of the request are invalid the delegating x-RACF shall return a User-Data-Answer with a Result-Code AVP value set to the appropriate value as described in clause 5.1. The delegating x-RACF shall, in the following order: 1) If the network resource identified by the Network-Resource-Id AVP is unknown or is not handled in the delegating x-RACF or is not allowed to be delegated to the delegated x-RACF, return a User-Data-Answer with the Experimental-Result-Code AVP set to NETWORK_RESOURCE_UNAVAILABLE. 2) If the network resource identified by the Network-Resource-Id AVP is handled in the delegating x-RACF and is allowed to be delegated to the delegated x-RACF, decide if the delegated bandwidth can be changed to the value indicated by the messages for each requested direction. a) If Preferred-Delegated-Bandwidth-UL (Preferred-Delegated-Bandwidth-DL) AVP is present and the uplink (downlink) delegated bandwidth to be delegated can be changed to the amount carried in this AVP without affecting the ongoing application sessions admitted by the delegating x-RACF and violating any policy rules in the delegating x-RACF, the delegating x-RACF changes the uplink (downlink) delegated bandwidth to the amount carried in the Preferred-Delegated-Bandwidth-UL (Preferred-Delegated-Bandwidth-DL) AVP. b) If Preferred-Delegated-Bandwidth-UL (Preferred-Delegated-Bandwidth-DL) AVP is not present or the uplink (downlink) delegated bandwidth can not be changed to the value carried in the Preferred-Delegated-Bandwidth-UL (Preferred-Delegated-Bandwidth-DL) AVP without affecting the ongoing application sessions admitted by the delegating x-RACF and violating any policy rules in the delegating x-RACF, the delegating x-RACF decides if the uplink (downlink) delegated bandwidth can be changed to the value indicated by the Required-Delegated-Bandwidth-UL (Required-Delegated-Bandwidth-DL) AVP: i) If the uplink (downlink) delegated bandwidth can be changed to the value carried in the Required-Delegated-Bandwidth-UL (Required-Delegated-Bandwidth-DL) AVP without affecting the ongoing application sessions admitted by the delegating x-RACF and violating any policy rules in the delegating x-RACF, the delegating x-RACF changes the uplink (downlink) delegated bandwidth to the amount carried in the Required-Delegated-Bandwidth-UL (Required-Delegated-Bandwidth-DL) AVP. ii) If the uplink (downlink) delegated bandwidth can not be changed to the value carried in the Required-Delegated-Bandwidth-UL (Required-Delegated-Bandwidth-DL) AVP without affecting the ongoing application sessions admitted by the delegating x-RACF and violating any policy rules in the delegating x-RACF, and if the Reservation-priority AVP is present, the delegating x-RACF evaluates if the uplink (downlink) delegated bandwidth can reach the value carried in the Required-Delegated-Bandwidth-UL (Required-Delegated-Bandwidth-DL) AVP by releasing sufficient ongoing application sessions with lower reservation priority than the value carried in the Reservation-priority AVP. If it can, then the delegating x-RACF releases sufficient ongoing application sessions with lower reservation priority, and changes the uplink (downlink) delegated bandwidth to the amount carried in the Required-Delegated-Bandwidth-UL (Required-Delegated-Bandwidth-DL) AVP. c) If either direction of the delegated bandwidth can not be changed as requested in the above steps, the delegating x-RACF shall return a User-Data-Answer with the Experimental-Result-Code AVP set to NETWORK_RESOURCE_INSUFFICIENT. Otherwise, the delegating x-RACF shall return a User-Data-Answer with the Result-Code AVP set to DIAMETER_SUCCESS and with the delegated bandwidth(s) in both or either of the Granted-Delegated-Bandwidth-UL and Granted-Delegated-Bandwidth-DL AVP. If the uplink delegated bandwidth is requested, the Granted-Delegated-Bandwidth-UL AVP must be included in the successful answer. If the downlink delegated bandwidth is requested, the Granted-Delegated-Bandwidth-DL AVP must be included in the successful answer. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 5.2.2.3 Delegation Negotiation triggered by the delegating x-RACF | This procedure is used for the delegating x-RACF to negotiate the delegation with the delegated x-RACF. This information flow occurs normally when there is insufficient delegated bandwidth for a new application session on the delegating x-RACF. This procedure is mapped to the commands Push-Notification-Request/Answer in the Diameter application specified in clause 7. ETSI ETSI TS 183 071 V3.1.1 (2010-02) 20 |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 5.2.2.3.1 Procedures at the delegating x-RACF | The delegating x-RACF shall populate the Push-Notification-Request as follows: • The Network-Resource-Id AVP shall be present and shall contain the identifier of the network resource to be delegated. • At least one of the Required-Delegated-Bandwidth-UL and Required-Delegated-Bandwidth-DL AVP shall be present. • The Preferred-Delegated-Bandwidth-UL, Preferred-Delegated-Bandwidth-DL and Reservation-priority AVPs may be present optionally. If the Required-Delegated-Bandwidth-UL AVP is not present, the Preferred- Delegated-Bandwidth-UL AVP shall not be present. If the Required-Delegated-Bandwidth-DL AVP is not present, the Preferred-Delegated-Bandwidth-DL AVP shall not be present. On receipt of the corresponding Push-Notification-Answer with the Result-Code AVP set to DIAMETER_SUCCESS and at least either of the Granted-Delegated-Bandwidth-UL and Granted-Delegated-Bandwidth-DL AVPs, the delegating x-RACF updates the corresponding content of the internal record with the received information for future use (e.g. allocating the resource for the pending application sessions). |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 5.2.2.3.2 Procedures at the delegated x-RACF | On receipt of the Push-Notification-Request with at least either of the Required-Delegated-Bandwidth-UL and Required-Delegated-Bandwidth-DL AVPs, the delegated x-RACF takes the Push-Notification-Request as the delegation negotiation request. If the contents of the request are invalid the delegated x-RACF shall return a Push-Notification-Answer with a Result-Code AVP value set to the appropriate value as described in clause 5.1. The delegated x-RACF shall, in the following order: 1) If there is no delegation record with the network resource identifier contained in the Network-Resource-Id AVP as a key, return a Push-Notification-Answer with the Experimental-Result-Code AVP set to NETWORK_RESOURCE_UNAVAILABLE. 2) If there is a delegation record with the network resource identifier contained in the Network-Resource-Id AVP as a key, decide if the delegated bandwidth can be changed to the value indicated by the messages for each requested direction. a) If Preferred-Delegated-Bandwidth-UL (Preferred-Delegated-Bandwidth-DL) AVP is present and the uplink (downlink) delegated bandwidth to be delegated can be changed to the amount carried in this AVP without affecting the ongoing application sessions admitted by the delegated x-RACF, the delegated x-RACF changes the uplink (downlink) delegated bandwidth to the amount carried in the Preferred-Delegated-Bandwidth-UL (Preferred-Delegated-Bandwidth-DL) AVP. b) If Preferred-Delegated-Bandwidth-UL (Preferred-Delegated-Bandwidth-DL) AVP is not present or the uplink (downlink) delegated bandwidth can not be changed to the value carried in the Preferred-Delegated-Bandwidth-UL (Preferred-Delegated-Bandwidth-DL) AVP without affecting the ongoing application sessions admitted by the delegated x-RACF, the delegated x-RACF decides if the uplink (downlink) delegated bandwidth can be changed to the value indicated by the Required-Delegated-Bandwidth-UL (Required-Delegated-Bandwidth-DL) AVP: i) If the uplink (downlink) delegated bandwidth can be changed to the value carried in the Required-Delegated-Bandwidth-UL (Required-Delegated-Bandwidth-DL) AVP without affecting the ongoing application sessions admitted by the delegated x-RACF, the delegated x-RACF changes the uplink (downlink) delegated bandwidth to the amount carried in the Required-Delegated-Bandwidth-UL (Required-Delegated-Bandwidth-DL) AVP. ETSI ETSI TS 183 071 V3.1.1 (2010-02) 21 ii) If the uplink (downlink) delegated bandwidth can not be changed to the value carried in the Required-Delegated-Bandwidth-UL (Required-Delegated-Bandwidth-DL) AVP without affecting the ongoing application sessions admitted by the delegated x-RACF, and if the Reservation-priority AVP is present, the delegated x-RACF evaluates if the uplink (downlink) delegated bandwidth can reach the value carried in the Required-Delegated-Bandwidth-UL (Required-Delegated-Bandwidth- DL) AVP by releasing sufficient ongoing application sessions with lower reservation priority than the value carried in the Reservation-priority AVP. If it can, then the delegated x-RACF releases sufficient ongoing application sessions with lower reservation priority, and changes the uplink (downlink) delegated bandwidth to the amount carried in the Required-Delegated-Bandwidth-UL (Required-Delegated-Bandwidth-DL) AVP. c) If either direction of the delegated bandwidth can not be changed as requested in the above steps, the delegated x-RACF shall return a Push-Notification-Answer with the Experimental-Result-Code AVP set to NETWORK_RESOURCE_INSUFFICIENT. Otherwise, the delegated x-RACF shall return a Push-Notification-Answer with the Result-Code AVP set to DIAMETER_SUCCESS and with the delegated bandwidth(s) in both or either of the Granted-Delegated-Bandwidth-UL and Granted-Delegated-Bandwidth-DL AVP. If the uplink delegated bandwidth is requested, the Granted-Delegated-Bandwidth-UL AVP must be included in the successful answer. If the downlink delegated bandwidth is requested, the Granted-Delegated-Bandwidth-DL AVP must be included in the successful answer. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 5.2.2.4 Delegation Query triggered by the delegating x-RACF | This procedure is used for the delegating x-RACF to query the delegation from the delegated x-RACF. This information flow occurs normally when the delegating x-RACF discovers there is a possibility of inconsistency of the delegation between the delegating x-RACF and the delegated x-RACF. This procedure is mapped to the commands Push-Notification-Request/Answer in the Diameter application specified in clause 7. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 5.2.2.4.1 Procedures at the delegating x-RACF | The delegating x-RACF shall populate the Push-Notification-Request as follows: • The Network-Resource-Id AVP shall be present and shall contain the identifier of the network resource to be delegated. • None of the Granted-Delegated-Bandwidth-UL, Granted-Delegated-Bandwidth-DL, Preferred-Delegated-Bandwidth-UL, Preferred-Delegated-Bandwidth-DL, Required-Delegated- Bandwidth-UL, Required-Delegated-Bandwidth-DL and Reservation-priority AVPs shall be present. On receipt of the corresponding Push-Notification-Answer with the Result-Code AVP set to DIAMETER_SUCCESS and at least either of the Granted-Delegated-Bandwidth-UL and Granted-Delegated-Bandwidth-DL AVPs, the delegating x-RACF may take the result of the query into account in deciding whether synchronization is needed and how much bandwidth should be delegated. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 5.2.2.4.2 Procedures at the delegated x-RACF | On receipt of the Push-Notification-Request with none of the Granted-Delegated-Bandwidth-UL, Granted-Delegated-Bandwidth-DL, Preferred-Delegated-Bandwidth-UL, Preferred-Delegated-Bandwidth-DL, Required-Delegated-Bandwidth-UL, Required-Delegated-Bandwidth-DL and Reservation-priority AVPs, the delegated x-RACF takes the Push-Notification-Request as the delegation query request. If the contents of the request are invalid the delegated x-RACF shall return a Push-Notification-Answer with a Result-Code AVP value set to the appropriate value as described in clause 5.1. The delegated x-RACF shall, in the following order: 1) If there is no delegation record with the network resource identifier contained in the Network-Resource-Id AVP as a key, return a Push-Notification-Answer with the Experimental-Result-Code AVP set to NETWORK_RESOURCE_UNAVAILABLE. ETSI ETSI TS 183 071 V3.1.1 (2010-02) 22 2) If there is a delegation record with the network resource identifier contained in the Network-Resource-Id AVP as a key, return a Push-Notification-Answer with the Result-Code AVP set to DIAMETER_SUCCESS and populate the Push-Notification-Request as follows: a) The Granted-Delegated-Bandwidth-UL shall be present if the uplink bandwidth has been delegated to the delegated x-RACF. b) The Granted-Delegated-Bandwidth-DL shall be present if the downlink bandwidth has been delegated to the delegated x-RACF. c) The Total-Bandwidth-UL shall be present if the total uplink bandwidth has been provisioned by the delegating x-RACF. d) The Total-Bandwidth-DL shall be present if the total downlink bandwidth has been provisioned by the delegating x-RACF. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 5.2.2.5 Delegation Query triggered by the delegated x-RACF | This procedure is used for the delegated x-RACF to query the delegation from the delegating x-RACF. This information flow occurs normally when the delegated x-RACF discovers there is a possibility of inconsistency of the delegation between the delegated x-RACF and the delegating x-RACF. This procedure is mapped to the commands User-Data-Request/Answer in the Diameter application specified in clause 7. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 5.2.2.5.1 Procedures at the delegated x-RACF | The delegated x-RACF shall populate the User-Data-Request as follows: • The Network-Resource-Id AVP shall be present and shall contain the identifier of the network resource to be delegated. • None of the Granted-Delegated-Bandwidth-UL, Granted-Delegated-Bandwidth-DL, Preferred-Delegated- Bandwidth-UL, Preferred-Delegated-Bandwidth-DL, Required-Delegated-Bandwidth-UL, Required- Delegated-Bandwidth-DL and Reservation-priority AVPs shall be present. On receipt of the corresponding User-Data-Answer with the Result-Code AVP set to DIAMETER_SUCCESS and at least either of the Granted-Delegated-Bandwidth-UL and Granted-Delegated-Bandwidth-DL AVPs, the delegated x-RACF updates the corresponding content of the internal record with the received information for future use (e.g. allocating the resource for new application sessions). |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 5.2.2.5.2 Procedures at the delegating x-RACF | On receipt of the User-Data-Request with none of the Granted-Delegated-Bandwidth-UL, Granted-Delegated-Bandwidth-DL, Preferred-Delegated-Bandwidth-UL, Preferred-Delegated-Bandwidth-DL, Required-Delegated-Bandwidth-UL, Required-Delegated-Bandwidth-DL and Reservation-priority AVPs, the delegating x-RACF takes the User-Data-Request as the delegation query request. If the contents of the request are invalid the delegating x-RACF shall return a User-Data-Answer with a Result-Code AVP value set to the appropriate value as described in clause 5.1. The delegating x-RACF shall, in the following order: 1) If the network resource identified by the Network-Resource-Id AVP is unknown or is not handled in the delegating x-RACF or is not allowed to be delegated to the delegated x-RACF, return a User-Data-Answer with the Experimental-Result-Code AVP set to NETWORK_RESOURCE_UNAVAILABLE. 2) If the network resource identified by the Network-Resource-Id AVP is handled in the delegating x-RACF and is allowed to be delegated to the delegated x-RACF, return a User-Data-Answer with the Result-Code AVP set to DIAMETER_SUCCESS and populate the Push-Notification-Request as follows: a) The Granted-Delegated-Bandwidth-UL shall be present if the uplink bandwidth has been delegated to the delegated x-RACF. b) The Granted-Delegated-Bandwidth-DL shall be present if the downlink bandwidth has been delegated to the delegated x-RACF. ETSI ETSI TS 183 071 V3.1.1 (2010-02) 23 |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 5.2.2.6 Event Notification triggered the delegating x-RACF | If an event for which notification is requested occurs, the delegating x-RACF shall send a CCR message to the delegated x-RACF containing: • The value of the Specific-Action AVP, indicating the event that occurred. • Optionally, the address of the UE that requested the multicast flow and the flow description of the flow. • Optionally, the appropriate Abort-Cause AVP value. The delegating x-RACF shall send a CCA message to the delegated x-RACF in response to the CCR message. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 5.2.2.7 Event Notification at the delegated x-RACF | If an event for which notification is requested occurs, the delegated x-RACF shall send an unsolicited RAR message to the delegating x-RACF containing: • The value of the Specific-Action AVP, indicating the event that occurred. • Optionally, the address of the UE that requested the multicast flow and the flow description of the flow. • Optionally, the appropriate Abort-Cause AVP value. The delegated x-RACF shall send a RAA message to the delegating x-RACF in response to the RAR message. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 6 DIAMETER application for Request Model | |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 6.1 Use of the Diameter base protocol | The Rr protocol is based on Diameter (RFC 3588 [8]). The Diameter Base Protocol as specified in RFC 3588 [8] used to support information transfer on the Rr interface. RFC 3588 [8] shall apply except as modified by the defined Rr application specific procedures, Attribute-Value Pairs (AVPs) as well as Experimental-Result-Code AVP and Specific-Action AVP values defined in the present document. Unless otherwise specified, the procedures of RFC 3588 [8] (including error handling and unrecognized information handling) are unmodified. In addition to the AVPs defined in clause 7.3, the Diameter AVPs from the Diameter base application (RFC 3588 [8]) are reused within the Diameter messages sent over the Rr reference point. The support of AVPs from the Diameter Network Access Server Application (NASREQ) (RFC 4005 [9]) is not required for Diameter implementations that conform to the present document. Accounting functionality (Accounting Session State Machine, related command codes and AVPs) is not used in the Rr specification. With regard to the Diameter protocol defined over the Rr reference point for request model, the lower-tier x-RACF acts as a Diameter server, in the sense that it is the network element that handles authorization requests for a particular realm. The top-tier x-RACF acts as the Diameter Client, in the sense that is the network element requesting authorization to use bearer path network resources. The support of Diameter agents between the lower-tier x-RACF and the top-tier x-RACF, is optional where the Rr is intra operator i.e. lower-tier x-RACF and top-tier x-RACF are all in the same domain. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 6.1.1 Securing Diameter Messages | For secure transport of Diameter messages, see TS 133 210 [11]. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 6.1.2 Accounting functionality | Accounting functionality (Accounting Session State Machine, related command codes and AVPs) is not used on the Rr interface for the Diameter application for the Rr request model. ETSI ETSI TS 183 071 V3.1.1 (2010-02) 24 |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 6.1.3 Use of sessions | The Session-Termination-Request (STR) and Session-Termination-Answer (STA) commands defined in RFC 3588 [8] shall be used in order to terminate the sessions. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 6.1.4 Transport protocol | Diameter messages over the Rr reference point shall make use of SCTP RFC 4960 [12] and shall utilize the new SCTP checksum method specified in RFC 4960 [12]. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 6.1.5 Routing considerations | Both the Destination-Realm and Destination-Host AVPs shall be present in the request. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 6.1.6 Advertising Application Support | The Capabilities-Exchange-Request (CER) and Capabilities-Exchange-Answer (CEA) commands are specified in the Diameter Base Protocol RFC 3588 [8]. The top-tier x-RACF and lower-tier x-RACF shall advertise the support of the Rr specific application for request model by including the value 16777278 of the application identifier in the Auth-Application-Id AVP within the Vendor-Specific-Application-Id grouped AVP of the Capabilities-Exchange-Request and Capabilities- Exchange-Answer commands. The vendor identifier value of ETSI (13019) shall be included in the Vendor-Id AVP of the Capabilities-Exchange- Request and Capabilities-Exchange-Answer commands, and in the Vendor-Id AVP within the Vendor-Specific- Application-Id grouped AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands. Additionally, the top-tier x-RACF and the lower-tier x-RACF shall advertise the support of additional Vendor-ID AVPs by including the values 10415 (3GPP) in different Supported-Vendor-Id AVP of the CER and CEA commands. NOTE: The Vendor-Id AVP included in Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands that is not included in the Vendor-Specific-Application-Id AVPs as described above indicates the manufacturer of the Diameter node as per RFC 3588 [8]. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 6.2 Commands | Existing Diameter command codes from the Diameter base protocol RFC 3588 [8] and RFC 4005 [9] are used at the Rr interface. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 6.2.1 AA-Request (AAR) Command | The AA-Request command (AAR), indicated by the Command-Code field set to 265 and the "R" bit set in the Command Flags field, is sent by the top-tier x-RACF to the lower-tier x-RACF for reserve, commit, modify and refresh operations. Message Format: <AA-Request> ::= < Diameter Header: 265, REQ, PXY, 16777278 > < Session-Id > { Auth-Application-ID } { Origin-Host } { Origin-Realm } { Destination-Realm } [ Destination-Host ] *[ Specific-Action ] [ AF-Charging-Identifier ] *[ Media-Component-Description ] [ User-Name ] [Logical-Access-Id] [ Globally-Unique-Address ] [ Service-Class ] [ Authorization-Lifetime ] *[ Proxy-Info ] ETSI ETSI TS 183 071 V3.1.1 (2010-02) 25 *[ Route-Record ] *[ AVP ] |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 6.2.2 AA-Answer (AAA) Command | The AA-Answer command (AAA), indicated by the Command-Code field set to 265 and the "R" bit cleared in the Command Flags field, is sent by the lower-tier x-RACF to the top-tier x-RACF in response to the AAR command. Message Format: <AA-Answer> ::= < Diameter Header: 265, PXY, 16777278 > < Session-Id > { Auth-Application-ID } { Origin-Host } { Origin-Realm } [ Result-Code ] [ Experimental-Result ] [ Error-Message ] [ Error-Reporting-Host ] [ Auth-Grace-Period ] *[ Session-Bundle-Id ] [ Authorization-Lifetime ] *[ Failed-AVP ] *[ Proxy-Info ] *[ AVP ] |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 6.2.3 Re-Auth-Request (RAR) Command | The RAR command, indicated by the Command-Code field set to 258 and the "R" bit set in the Command Flags field, is sent by the lower-tier x-RACF to the top-tier x-RACF in order to indicate a specific action. The values INDICATION_OF_RELEASE_OF_BEARER, INDICATION_OF_SUBSCRIBER_DETACHMENT, INDICATION_OF_RESERVATION_EXPIRATION of the Specific-Action AVP shall not be combined with each other in a Re-Auth-Request. Message Format: <RA-Request> ::= < Diameter Header: 258, REQ, PXY, 16777278 > < Session-Id > { Origin-Host } { Origin-Realm } { Destination-Realm } { Destination-Host } { Auth-Application-Id } *{ Specific-Action } *[ Flows ] [ Abort-Cause ] [ Origin-State-Id ] *[ Proxy-Info ] *[ Route-Record ] *[ AVP ] |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 6.2.4 Re-Auth-Answer (RAA) Command | The RAA command, indicated by the Command-Code field set to 258 and the "R" bit cleared in the Command Flags field, is sent by the top-tier x-RACF to the lower-tier x-RACF in response to the RAR command. Message Format: <RA-Answer> ::= < Diameter Header: 258, PXY, 16777278 > < Session-Id > { Origin-Host } { Origin-Realm } [ Result-Code ] [ Experimental-Result ] * [ Media-Component-Description ] [ Origin-State-Id ] [ Error-Message ] [ Error-Reporting-Host ] * [ Failed-AVP ] * [ Proxy-Info ] ETSI ETSI TS 183 071 V3.1.1 (2010-02) 26 * [ AVP ] |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 6.2.5 Session-Termination-Request (STR) Command | The STR command, indicated by the Command-Code field set to 275 and the "R" bit set in the Command Flags field, is sent by the top-tier x-RACF to inform the lower-tier x-RACF that an authorized session shall be terminated. Message Format: <ST-Request> ::= < Diameter Header: 275, REQ, PXY, 16777278 > < Session-Id > { Origin-Host } { Origin-Realm } { Destination-Realm } { Auth-Application-ID } { Termination-Cause } [ Destination-Host ] *[ Class ] [ Origin-State-Id ] *[ Proxy-Info ] *[ Route-Record ] *[ AVP ] |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 6.2.6 Session-Termination-Answer (STA) Command | The STA command, indicated by the Command-Code field set to 275 and the "R" bit cleared in the Command Flags field, is sent by the lower-tier x-RACF to the top-tier x-RACF in response to the STR command. Message Format: <ST-Answer> ::= < Diameter Header: 275, PXY, 16777278 > < Session-Id > { Origin-Host } { Origin-Realm } [ Result-Code ] [ Experimental-Result ] [ Error-Message ] [ Error-Reporting-Host ] *[ Failed-AVP ] [ Origin-State-Id ] *[ Redirect-Host ] [ Redirect-Host-Usage ] [ Redirect-Max-Cache-Time ] *[ Proxy-Info ] [ AVP ] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.