hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.4.2.1.4 Activation Status Notification Diversion | Mapping of this procedure requires further study. |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.4.2.2 Message Waiting Indication (MWI) | |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.4.2.2.1 Activation of Message Waiting Indication (MWI) | On receipt of a DSS1 FACILITY message containing the MWIActivate invoke component, a SIP SUBSCRIBE request is sent to the Application Server that contains an Event header and the value is set to "message-summary" additionally the Accept header contains the value "application/simple-message-summary". The Expires header ... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.4.2.2.2 Deactivation of Message Waiting Indication (MWI) | On receipt of a DSS1 FACILITY message containing the MWIDeactivate invoke component, a SIP SUBSCRIBE request is sent to the Application Server the Event header I set to "message-summary" and the Expires header is set to zero. The mapping of the Facility I.E is described below. Table 5.4.2.2.2-1: Mapping of MWIDeactivat... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 1 Scope | The present document defines a specification based on DIAMETER for use at the Re Reference Point between the TISPAN NGN Access-Resource Admission Control Function (A-RACF) and the Resource Control Enforcement Function (RCEF). Whenever it is possible the present document specifies the requirements for this protocol by r... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 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... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 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 003 (V2.0.0): "Telecommunications and Int... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 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] ITU-T Recommendation Q.3303.3: "Protocol at the ... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 3 Definitions and abbreviations | |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: activation: operation of binding a Policy-Rule to a Transport Resource based on the transport resource classifier Attribute-Value Pair (AVP): corresponds to an Information Element in a DIAMETER message NOTE: See RFC 3588 [3]. deactivat... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ABNF Augmented Backus-Naur Form AF Application Function A-RACF Access-Resource and Admission Control Function AVP Attribute-Value Pair CCA Credit-Control Answer CCR Credit-Control Request CEA Capabilities-Exchange-Answer CER Capabilities-Excha... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 4 Overview | The Resource Control Enforcement Function (RCEF) defined in ES 282 003 [1] performs policy enforcement functions under control of the A-RACF. The RCEF main functions are: • Enforcement of the policies defined by the access provider. • Οpening and closing of gates in order to allow only authorized traffic to flow; marks... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 5 Procedure descriptions | |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 5.1 General | The following clauses describe the realization of the functional procedures of the Re Reference Point (defined in the RACS specification ES 282 003 [1]) using the Diameter commands described in clause 7.1. This involves describing a mapping between the Information Elements defined in the RACS specification (ES 282 003 ... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 5.2 A-RACF initiated procedures | |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 5.2.1 Procedures at the A-RACF | |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 5.2.1.1 High level description | The A-RACF is the DIAMETER Server. The policy operations that the A-RACF may support include the installation, activation, modification, deactivation and removal of Policy Rules on the RCEF: • In order to activate one or several Policy Rules, or to Install and Activate one or several Policy Rules, the A-RACF sends an i... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 5.2.1.2 Initial Policy Installation Request | The Initial Policy Installation Request is a PIR command with the PI-Request-Type AVP set to INITIAL_REQUEST. The A-RACF shall include the Auth-Session-State AVP with the value NO_STATE_MAINTAINED (1) [3] to indicate implicitly terminated sessions. The A-RACF may include one or several Event-Trigger AVP(s) in order to ... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 5.2.1.3 Policy modification request | The Policy Modification Request is a PIR Command with the PI-Request-Type AVP with the value UPDATE_REQUEST. The A-RACF shall include the Auth-Session-State AVP with the value NO_STATE_MAINTAINED (1) [3]. The A-RACF may include one or several Event-Trigger AVP(s) in order to subscribe to the notification of particular ... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 5.2.1.4 Policy termination request | In order to deactivate and remove all Policy Rule(s) previously activated on a Transport Resource, the A-RACF sends a PIR Command to the RCEF, with the PI-Request-Type AVP set to TERMINATION_REQUEST. The Policy Termination-Request shall include the Transport Resource Classifier of the corresponding Transport Resource. ... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 5.2.1.5 Event notification | |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 5.2.1.5.1 Events | Depending on the policy installed, the RCEF may initiate communication with A-RACF to notify certain event occurred on the network element, according to the event A-RACF may decide to modify / remove existing policies, install new policies or escalate the event to higher layer. Event type is identified within the CCR m... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 5.2.1.5.2 Event subscription | Two mechanisms are supported on the Re Reference Point: • Explicit Event Subscription: The A-RACF may request to be notified of certain events (e.g. bearer failure) by specifying them in the Event-Trigger AVP of the Initial PIR command or of the subsequent Policy Modification Request(s). • Implicit Event Subscription: ... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 5.2.1.5.3 Event notification | A CCR from the RCEF to the A-RACF indicates the occurrence of particular events (Explicit or Implicit Event Subscription). As soon as one of the expected AVPs is missing, the A-RACF denies the entire CCR and returns a CCA command with the Result-Code AVP with the value DIAMETER_MISSING_MANDATORY_AVP [3]. This is the ca... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 5.2.1.6 Policy Query Request | The Policy Query Request is a PIR command with the PI-Request-Type AVP set to QUERY_REQUEST. Several Query levels are supported: • In order to query the RCEF for the list of Policy Rules supported by the RCEF, the A-RACF shall not include any Transport Resource Classifier, and shall not include any Policy Rule. • In or... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 5.2.2 Procedures at the RCEF | |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 5.2.2.1 High level description | The RCEF is the DIAMETER Client. • A PIR Command with the PI-Request-Type AVP set to INITIAL_REQUEST is interpreted by the RCEF as an Initial Policy Install Request. • A PIR Command with the PI-Request-Type AVP set to UPDATE_REQUEST is interpreted by the RCEF as a Policy Modification Request. • A PIR Command with the P... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 5.2.2.2 Initial policy installation request | The RCEF interprets a PIR command with the PI-Request-Type AVP set to INITIAL_REQUEST as an Initial Policy Installation Request. As soon as one of the expected AVPs is missing, the RCEF denies the entire PIR and returns a PIA command with the Result-Code AVP with the value DIAMETER_MISSING_MANDATORY_AVP [3]. This is th... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 5.2.2.3 Policy modification request | The RCEF interprets a PIR command the PI-Request-Type AVP set to UPDATE_REQUEST as a Policy Modification Request. As soon as one of the expected AVPs is missing, the RCEF denies the entire PIR and returns a PIA command with the Result-Code AVP with the value DIAMETER_MISSING_MANDATORY_AVP [3]. This is the case if: • ei... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 5.2.2.4 Policy termination request | The RCEF interprets a PIR command with the PI-Request-Type AVP set to TERMINATION_REQUEST as a Policy Termination Request. If the RCEF cannot map the specified Transport Resource Classifier(s) to the corresponding Transport Resource, or if several Transport Resource Classifiers are specified but they do not match with ... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 5.2.2.5 Event notification | If one of the events implicitly or explicitly subscribed by the A-RACF occurs, the RCEF shall send an unsolicited CCR message to the A-RACF for Event Notification. • The RCEF shall include the Session-Id AVP of the impacted Policy Session. • The RCEF shall include the Service-Context-Id AVP with the value 461. NOTE: Co... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 5.2.2.6 Policy Query Request | The RCEF interprets a PIR command with the PI-Request-Type AVP set to QUERY_REQUEST as a Policy Query Request. As soon as one of the expected AVPs is missing, the RCEF denies the entire PIR and returns a PIA command with the Result-Code AVP with the value DIAMETER_MISSING_MANDATORY_AVP [3]. This is the case if: • eithe... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 5.3 RCEF initiated procedures | RCEF initiated procedures ("pull mode") apply when RCEF receives a request for transport resources via transport signalling. RCEF will employ a CC-Request to request a policy operation by A-RACF. A-RACF will respond to a CC-Request with a CC-Answer. |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 5.3.1 Procedures at the A-RACF | |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 5.3.1.1 High level description | The A-RACF will receive a CCR command from the RCEF in certain circumstances (e.g. Pull mode) to request a resource reservation. The CCR command will also be received in order to modify or terminate this resource reservation: • A CCR command with the CC-Request-Type AVP set to INITIAL_REQUEST is interpreted as an initi... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 5.3.1.2 Traffic policy activation request | On receipt of a CC-Request from RCEF with CC-Request-type AVP set to "INITIAL_REQUEST", the A-RACF will either create corresponding service control state or associate the request with already existing service control state and initiate the attachment of a traffic policy to the transport resource(s) described by the Tra... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 5.3.1.3 Traffic policy modification request | On receipt of a CC-Request with the CC-Request-Type AVP set to the value "UPDATE_REQUEST", the A-RACF shall identify the corresponding service control state using the Transport Resource Classifier(s). A-RACF decides on the attachment of the appropriate new or updated traffic policies and sends a CC-Answer command to th... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 5.3.1.4 Traffic policy deactivation request | Traffic policy deactivation may be initiated by the RCEF through a CC-Request with CC-Request-Type AVP set to the value "TERMINATION_REQUEST". The A-RACF shall identify the corresponding service control state using the Transport Resource Classifier(s). A-RACF shall respond with a CC-Answer to RCEF including the Policy-... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 5.3.2 Procedures at the RCEF | |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 5.3.2.1 High level description | The RCEF will send a CCR command to request a resource reservation from the A-RACF via the Re reference when the RCEF receives a trigger. The CCR indicates that a change of policies may need to be applied to a particular transport resource identified by the logical access id or the user-name. The RCEF will receive a re... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 5.3.2.2 Traffic policy activation request | In order to activate one or several traffic policies the RCEF sends an initial CC-Request to A-RACF. The CC-Request-type AVP contains the value "INITIAL_REQUEST". The A-RACF is expected to respond with a CC-Answer. Each traffic policy is described in the Policy-Rule-Install AVP. The Policy-Rule-Install AVP shall contai... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 5.3.2.3 Traffic policy modification request | In order to modify traffic policies previously activated on transport resources described by Transport Resource Classifier(s), the RCEF sends a CC-Request Command with the CC-Request-Type AVP set to the value "UPDATE_REQUEST". During the modification procedure, a traffic policy previously activated for a set of Transpo... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 5.3.2.4 Traffic Policy Deactivation Request | In order to deactivate all traffic policies previously activated for given Transport Resource Classifier(s), the RCEF sends a CC-Request Command to the A-RACF, with the CC-Request-Type AVP set to "TERMINATION_REQUEST". On receipt of the CC-Answer, the RCEF will: • deactivate the traffic policy referenced by the Policy-... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 6 Use of the DIAMETER base protocol | The DIAMETER Base Protocol defined by RFC 3588 [3] shall apply, with the clarifications listed in the present document. |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 6.1 Securing DIAMETER messages | For secure transport of DIAMETER messages, IPSec may be used. Guidelines on the use of SCTP with IPSec can be found in RFC 3554 [5]. The RCEF may verify the identity of the A-RACF issuing during the Capabilities Exchange Request procedure. The RCEF may verify if the A-RACF that issues a PIR command is allowed to do so,... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 6.2 Accounting functionality | Accounting functionality (Accounting Session State Machine, related command codes and AVPs) is not used on the Re Reference Point. ETSI ETSI TS 183 060 V2.1.1 (2009-04) 28 |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 6.3 Use of sessions | DIAMETER sessions are implicitly terminated. As such, the Abort-Session-Request (ASR) and Session-Termination-Request (STR) defined in [3] are not used. NOTE: The A-RACF and RCEF obviously maintain state, but this state is not associated with the Session-Id. The A-RACF shall include in its Requests the Auth-Session-Sta... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 6.4 Transport protocol | DIAMETER messages over the Re interface shall make use of SCTP RFC 2960 [2] and shall utilize the new SCTP checksum method specified in RFC 3309 [4]. |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 6.5 Routing considerations | This clause specifies the use of the Destination-Realm and Destination-Host Routing AVPs. Both the Destination-Realm and Destination-Host AVPs shall be present in the Request from the A-RACF to the RCEF. The A-RACF may obtain the Destination-Host AVPs to use in Requests towards the RCEF from NASS user location informat... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 6.6 Advertising Application support | The Capabilities-Exchange-Request (CER) and Capabilities-Exchange-Answer (CEA) are defined in RFC 3588 [3]. The A-RACF and RCEF shall advertise support of the Re specific application by including the following AVPs: • Vendor-Specific-Application-Id grouped AVPs containing the following AVPs: - Auth-Application-Id AVPs ... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7 DIAMETER application | The DIAMETER Base Protocol as specified in RFC 3588 [3] is used to support information transfer on the Re interface. RFC 3588 [3] shall apply except as modified by the defined support of the methods and the defined support of the commands and AVPs, result and event codes specified in clause 5. Unless otherwise specifie... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.1 Commands | The following commands are used: Table 1: Command-Code values Command-Name Abbreviation Code Defined In See clause Policy-Install-Request PIR 315 [6], [13] 7.1.1 Policy-Install-Answer PIA 315 [6], [13] 7.1.2 Credit-Control-Request CCR 272 [8] 7.1.3 Credit-Control-Answer CCA 272 [8] 7.1.4 AVPs defined in [6] and not use... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.1.1 Policy-Install-Request (PIR) command | The Policy-Install-Request (PIR) command, indicated by the Command-Code field set to 315 and the "R" bit set in the Command Flags field, is sent by the A-RACF to the RCEF in order to install policies in the RCEF. This command is defined in [6] and used with additional AVPs defined in the present document. Message Forma... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.1.2 Policy-Install-Answer (PIA) command | The Policy-Install-Answer (PIA) command, indicated by the Command-Code field set to 315 and the "R" bit cleared in the Command Flags field, is sent by a server in response to Policy-Install-Request command. This command is defined in [6] and used with additional AVPs defined in the present document. Message Format: <PI... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.1.3 CC-Request (CCR) command | The CCR command, indicated by the Command-Code field set to 272 and the 'R' bit set in the Command Flags field, is sent by the RCEF to the A-RACF in order to report the occurrence of particular event or to request activation, modification, or deactivation of traffic policies. If the Traffic-Flow AVP is used at the comm... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.1.4 CC-Answer (CCA) Command | The Credit-Control-Answer message (CCA) is indicated by the command-code field being set to 272 and the 'R' bit being cleared in the Command Flags field. It is sent by the A-RACF to the RCEF in answer to the CCR.. Message Format: <CC-Answer> ::= < Diameter Header: 272, PXY > < Session-Id > { Origin-Host } { Origin-Real... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.2 Experimental-Result-Code AVP values | Clause 7.2 defines new Experimental-Result-Code values that shall be supported by all DIAMETER implementations that conform to the present document. When one of the Experimental Result Code defined in clause 7.2 is included in a response, it shall be inside an Experimental-Result AVP and the Result-Code AVP shall be ab... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.2.1 Success | Experimental Result Codes that fall within the Success category are used to inform a peer that a request has been successfully completed. ETSI ETSI TS 183 060 V2.1.1 (2009-04) 32 |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.2.2 Transient failures | Experimental Result Codes that fall within the transient failures category are those used to inform a peer that the request could not be satisfied at the time that it was received. The request may be able to be satisfied in the future. The following values of the Experimental-Result-Code AVP defined in ES 283 026 [12] ... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.2.3 Permanent failures | Experimental Result Codes that fall within the Permanent Failures category are used to inform the peer that the request failed, and should not be attempted again. The present document defines the following new values of the Experimental-Result-Code AVP: • UNKNOWN_POLICY_RULE (5061) - The RCEF indicates that the specifi... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3 AVPs | Clause 7.3 summarizes the AVP used in the present document, beyond those defined in the DIAMETER Base Protocol. |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.1 AVPs Defined in the Present Document | Table 2 describes the new DIAMETER AVPs used in the present document, their AVP Code values, types, possible flag values and whether the AVP may or not be encrypted. The Vendor-Id field in the header for these AVPs shall be set to ETSI (13019). Table 2: New DIAMETER AVPs AVP flag rules Attribute name AVP Code Clause de... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.1.1 Policy-Rule-Install AVP | The Policy-Rule-Install AVP (AVP code 550) is of type Grouped, and it is used to activate, install or modify Policy Rule as instructed from the A-RACF to the RCEF. AVP Format: Policy-Rule-Install ::= < AVP Header: 550 > * [ Policy-Rule-Definition ] * [ Policy-Rule-Name ] * [ Policy-Rule-Base-Name ] * [ AVP ] |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.1.2 Policy-Rule-Remove AVP | The Policy-Rule-Remove AVP (AVP code 551) is of type Grouped, and it is used to deactivate or remove Policy Rules. AVP Format: Policy-Rule-Remove ::= < AVP Header: 551 > * [ Policy-Rule-Name ] * [ Policy-Rule-Base-Name ] * [ AVP ] |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.1.3 Policy-Rule-Definition AVP | The Policy-Rule-Definition AVP (AVP code 552) is of type Grouped, and it describes a Policy Rule. The Policy-Rule-Name AVP uniquely identifies the Policy Rule and it is used to reference to a Policy Rule in communication between the RCEF and the A-RACF. The Flow-Description AVPs determines the traffic flows that belong... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.1.4 Policy-Rule-Base-Name AVP | The Policy-Rule-Base-Name AVP (AVP code 553) is of type UTF8String, and it indicates the name of a pre-defined group of Policy Rules residing at the RCEF. |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.1.5 Policy-Rule-Name AVP | The Policy-Rule-Name AVP (AVP code 554) is of type OctetString, and it defines a name for Policy Rule. For Policy Rules provided by the A-RACF it uniquely identifies a Policy Rule. For Policy Rules pre-defined at the RCEF it uniquely identifies a Policy Rule within the RCEF. |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.1.6 Policy-Rule-Report AVP | The Policy-Rule-Report AVP (AVP code 555) is of types Grouped, and it is used to report the status of a particular Policy Rule. Policy-Rule-Name AVP is a reference for a specific Policy. Policy-Rule-Base-Name AVP is a reference to a group of Policies. The Policy-Rule-Status AVP indicates the action being performed on t... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.1.7 Policy-Rule-Status AVP | The Policy-Rule-Status AVP (AVP code 556) is of type Enumerated, and describes the status of one or a group of Policy Rules. The following values are defined: ACTIVE (0) This value is used to indicate that the Policy rule(s) are successfully installed (for those provisioned from A-RACF) or activated (for those pre-prov... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.1.8 Traffic-Flow AVP | The Traffic-Flow AVP (AVP code 557) is of type Grouped, and it describes the detailed information for a group of flows. AVP Format: Traffic-Flow ::= < AVP Header: 557 > * [ Flow-Description ] [ Flow-Status ] [ QoS-Information ] [ User-Name ] [ Called-Station-ID ] [Framed-IP-Address] [Framed-IPv6-Prefix] [Address-Realm]... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.1.9 Policy-Update-Request AVP | The Policy-Update-Request AVP (AVP code 558) is of types Grouped, and it is used to request the update the QoS of a particular Policy Rule. Policy-Rule-Name AVP is a reference for a specific Policy. Policy-Rule-Base-Name AVP is a reference to a group of Policies. AVP Format: Policy-Update-Request ::= < AVP Header: 558 ... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.2 AVPs imported from ITU-T NGN-GSI/DOC - 127 | The following table describes the DIAMETER AVPs imported from ITU-T NGN-GSI/DOC - 127 [6] and used in the present document, their AVP Code values, types, possible flag values and whether the AVP may or not be encrypted. Flags values are described in the context of the present document rather than in the context of the ... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.2.1 Traffic-Descriptor-UL AVP (ITU-T NGN-GSI/DOC - 127) | The Traffic-Descriptor-UL AVP (AVP code 1012) is of type Grouped, and indicates traffic characteristics complementary to the maximum bandwidth. It is used to control the bandwidth of traffic flows in the uplink direction. AVP Format: Traffic-Descriptor-UL ::= < AVP Header: 1012 > [ Maximum-Burst-Size ] [ Committed-Data... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.2.2 Traffic-Descriptor-DL AVP (ITU-T NGN-GSI/DOC - 127) | The Traffic-Descriptor-DL AVP (AVP code 1013) is of type Grouped, and indicates traffic characteristics complementary to the maximum bandwidth. It is used to control the bandwidth of traffic flows in the downlink direction. AVP Format: Traffic-Descriptor-DL::= < AVP Header: 1013 > [ Maximum-Burst-Size ] [ Committed-Dat... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.2.3 Maximum-Burst-Size AVP (ITU-T NGN-GSI/DOC - 127) | The Maximum-Burst-Size AVP (AVP code 1014) is of type Unsigned32, and indicates the peak burst size in Octets. It is used to provision the peak burst size for the traffic policing. |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.2.4 Committed-Data-Rate AVP (ITU-T NGN-GSI/DOC - 127) | The Committed-Data-Rate AVP (AVP code 1015) is of type Unsigned32, and indicates the average bandwidth in Octets per second. It is used to provision the average bandwidth for the traffic policing. ETSI ETSI TS 183 060 V2.1.1 (2009-04) 37 |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.2.5 Committed-Burst-Size AVP (ITU-T NGN-GSI/DOC - 127) | The Committed-Burst Size AVP (AVP code 1016) is of type Unsigned32, and indicates the committed burst size in Octets. |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.2.6 Excess-Burst-Size AVP (ITU-T NGN-GSI/DOC - 127) | The Excess-Burst Size AVP (AVP code 1017) is of type Unsigned32, and indicates the excess burst size in Octets. |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.2.7 PI-Request-Type AVP (ITU-T NGN-GSI/DOC - 127) | The PI-Request-Type AVP (AVP Code 1010) is of type Enumerated and contains the reason for sending the Policy-Install-Request command. It shall be present in all Policy-Install-Request messages. The following values defined in [6] are reused: INITIAL_REQUEST 1 An Initial Request is used to activate Policy Rule(s) on a p... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.2.8 PI-Request-Number AVP (ITU-T NGN-GSI/DOC - 127) | The PI-Request-Number AVP (AVP Code 1011) is of type Unsigned32 and identifies this request within one session. As Session-Id AVPs are globally unique, the combination of Session-Id and PI-Request-Number AVPs is also globally unique and can be used in matching policy-install messages with confirmations. An easy way to ... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.3 AVPs Imported From TS 129 212 | Table 4 describes the DIAMETER AVPs imported from [7] and used in the present document, their AVP Code values, types, possible flag values and whether the AVP may or not be encrypted. Flags values are described in the context of the present document rather than in the context of the application where they are defined. ... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.3.1 QoS-Information AVP (TS 129 212) | The QoS-Information AVP (AVP code 1016) is of type Grouped, and it defines the maximum QoS that is authorized for the corresponding traffic flow(s): AVP Format: QoS-Information ::= < AVP Header: 1016> [ Max-Requested-Bandwidth-UL ] [ Max-Requested-Bandwidth-DL ] [ Traffic-Descriptor-UL ] [ Traffic-Descriptor-DL ] [ ToS... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.3.2 ToS-Traffic-Class AVP (TS 129 212) | The ToS-Traffic-Class AVP (AVP code 1014) is of type OctetString, and it contains an identifier of the Traffic Class. |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.3.3 Event-Trigger AVP (TS 129 212) | The Event-Trigger AVP (AVP code 1006) is of type Enumerated. When sent from the A-RACF to the RCEF the Event-Trigger AVP indicates that an event that shall trigger a CC-Request from the RCEF to the A-RACF. When sent from the RCEF to the A-RACF the Event-Trigger AVP indicates that the corresponding event has occurred on... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.3.4 Precedence AVP (TS 129 212) | The Precedence AVP (AVP code 1010) is of type Unsigned32, and it defines the precedence of a Policy Rule in case of overlapping Policy Rules. A Policy Rule with the Precedence AVP with lower value shall take precedence over a Policy Rule with the Precedence AVP with higher value. |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.3.5 Reporting-Level AVP (TS 129 212) | The Reporting-Level AVP (AVP code 1011) is of type Enumerated, and it defines on what level the RCEF reports the usage for the related Policy Rule. The following values are defined: • SERVICE_IDENTIFIER_LEVEL (0) - This value shall be used to indicate that the usage shall be reported on service id and rating group comb... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.4 AVPs imported from RFC 4006 | Table 5 describes the DIAMETER AVPs imported from RFC 4006 [8] and used in the present document, their AVP Code values, types, possible flag values and whether the AVP may or not be encrypted. Flags values are described in the context of the present document rather than in the context of the application where they are ... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.5 AVPs imported from TS 129 209 | Table 6 describes the DIAMETER AVPs imported from TS 129 209 [9] and used in the present document, their AVP Code values, types, possible flag values and whether the AVP may or not be encrypted. Flags values are described in the context of the present document rather than in the context of the application where they ar... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.5.1 Flow-Description AVP (TS 129 209) | The Flow-Description AVP (AVP code 507) is of type IPFilterRule, and defines a packet filter for an IP flow with the following information: • Direction (in or out). • Source and destination IP address (possibly masked). • Protocol. • Source and destination port (list or ranges). The following restrictions apply: • Only... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.5.2 Flow-Number AVP (TS 129 209) | The Flow-Number AVP (AVP code 509) is of type Unsigned32, and it contains the ordinal number of the IP flow(s), assigned according to the rules in annex C of TS 129 207 [14] (3GPP TS 29.207). |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.5.3 Flows AVP (TS 129 209) | The Flows AVP (AVP code 510) is of type Grouped, and it indicates IP flows via their flow identifiers. If no Flow-Number AVP(s) is supplied, the Flows AVP refers to all Flows matching the Media-Component-Number. AVP Format: Flows::= < AVP Header: 510 > { Media-Component-Number} * [ Flow-Number] |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.5.4 Flow-Status AVP (TS 129 209) | The Flow-Status AVP (AVP code 511) is of type Enumerated, and describes whether the Policy Rule needs to be activated or not. The following values are defined: • ENABLED-UPLINK (0) - This value shall be used to activate a Policy Rule relative to the outgoing direction on the RCEF. • ENABLED-DOWNLINK (1) - This value sh... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.6 AVPs Imported From RFC 4005 | The following table describes the DIAMETER AVPs imported from RFC 4005 [10] and used in the present document, their AVP Code values, types, possible flag values and whether the AVP may or not be encrypted. Flags values are described in the context of the present document rather than in the context of the application wh... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.6.1 Called-Station-Id AVP (RFC 4005) | The Called-Station-Id AVP (AVP Code 30) is of type UTF8String and contains the ASCII string describing the layer 2 address of the Transport Resource on the RCEF. For use with IEEE 802 access, the Called-Station-Id MAY contain a MAC address. NOTE: Further clarification on the use of Called-Station-Id is required in the ... |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.4 Use of namespaces | Clause 7.4 contains the namespaces that have either been created in the present document, or the values assigned to existing namespaces managed by IANA [11]. |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.4.1 AVP codes | The present document assigns the AVP values in the range 550 to 599 from the AVP Code namespace managed by ETSI for its DIAMETER vendor-specific applications. See clause 7.3 for the list of AVP values assigned in the present document. |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.4.2 Experimental-Result-Code AVP values | This clause defines new Experimental-Result-Code values that shall be supported by all DIAMETER implementations that conform to the present document. When one of the Experimental-Result-Code values defined in this clause is included in a response, it shall be inside an Experimental-Result AVP. |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.4.3 Command Code values | The present document does not assign command code values but uses existing command defined in ITU-T NGN-GSI/DOC-127 [6]. |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.4.4 Application-ID value | The present document uses value 16777253. ETSI ETSI TS 183 060 V2.1.1 (2009-04) 44 Annex A (informative): Differences compared to ITU-T Rw and 3GPP Gx specifications The protocol used over the Re reference point and defined in the present specification has strong similarities with the Diameter applications used over th... |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 1 Scope | The present document is applicable to the a2 interface between the Connectivity Session Location and Repository Function (CLF) and the Network Access Configuration Function (NACF). Whenever it is possible the present document specifies the requirements for this protocol by reference to specifications produced by the IE... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.