hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
63ffe60a200b805cb953d0d9093efd05 | 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 Communica... |
63ffe60a200b805cb953d0d9093efd05 | 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 accept... |
63ffe60a200b805cb953d0d9093efd05 | 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] Voi... |
63ffe60a200b805cb953d0d9093efd05 | 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. |
63ffe60a200b805cb953d0d9093efd05 | 183 011 | 3 Definitions and abbreviations | |
63ffe60a200b805cb953d0d9093efd05 | 183 011 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in TS 124 411 [18] apply. |
63ffe60a200b805cb953d0d9093efd05 | 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 In... |
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 accept... |
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] Voi... |
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 accept... |
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] Voi... |
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 (informati... |
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 accept... |
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] Voi... |
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 (informati... |
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 accept... |
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] Voi... |
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... |
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 accept... |
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] Voi... |
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 Publicat... |
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... |
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 accept... |
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 Int... |
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 de... |
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 AV... |
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... |
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 t... |
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 resou... |
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 Sessi... |
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 perf... |
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 a... |
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 ET... |
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... |
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 Me... |
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 release... |
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 t... |
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 netwo... |
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 N... |
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 Dia... |
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-D... |
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 dele... |
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 i... |
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 Pr... |
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... |
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... |
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, Preferre... |
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 ... |
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 ... |
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-Delega... |
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-Da... |
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 flo... |
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 descripti... |
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-Resul... |
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 iden... |
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... |
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-Applicatio... |
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_EXPIR... |
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-Real... |
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 > { Or... |
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-Real... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.