hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
94c82513a2001364c90e5aadbf7f640d | 183 071 | 6.2.7 Abort-Session-Request (ASR) Command | The ASR command, indicated by the Command-Code field set to 274 and the "R" bit set in the Command Flags field, is sent by the lower-tier x-RACF to inform the top-tier x-RACF that all resources for the authorized session have become unavailable. Message Format: <AS-Request> ::= < Diameter Header: 274, REQ, PXY, 16777278 > < Session-Id > { Origin-Host } { Origin-Realm } { Destination-Realm } { Destination-Host } { Auth-Application-ID } { Abort-Cause } *[ Session-Bundle-Id ] [ Origin-State-Id ] *[ Proxy-Info ] *[ Route-Record ] [ AVP ] ETSI ETSI TS 183 071 V3.1.1 (2010-02) 27 |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 6.2.8 Abort-Session-Answer (ASA) Command | The ASA command, indicated by the Command-Code field set to 274 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 ASR command. Message Format: <AS-Answer> ::= < Diameter Header: 274, PXY, 16777278 > < Session-Id > { Origin-Host } { Origin-Realm } [ Result-Code ] [ Experimental-Result ] [ Origin-State-Id ] [ Error-Message ] [ Error-Reporting-Host ] *[ Failed-AVP ] *[ Redirected-Host ] [ Redirected-Host-Usage ] [ Redirected-Max-Cache-Time ] *[ Proxy-Info ] *[ AVP ] |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 6.3 Experimental-Result-Code AVP values | |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 6.3.1 Experimental-Result-Code AVP values imported from TS 129 209 | This clause lists the specific values of the Experimental-Result-Code AVP imported from TS 129 209 [7] (vendor-id is 3GPP): • INVALID_SERVICE_INFORMATION (5061): - The service information provided by the top-tier x-RACF is invalid or insufficient for the lower-tier x-RACF to perform the requested action. • FILTER_RESTRICTIONS (5062): - The Flow-Description AVP(s) cannot be handled by the lower-tier x-RACF because restrictions defined in clause 7.3.7 are not observed. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 6.3.2 Experimental-Result-Code AVP values imported from TS 183 026 | This clause lists the specific values of the Experimental-Result-Code AVP imported from TS 183 026 [10] (vendor-id is ESTI): • INSUFFICIENT_RESOURCES (4041): - The lower-tier x-RACF indicates insufficient resources to perform the requested action. • MODIFICATION_FAILURE (5041): - The lower-tier x-RACF or BGF indicates that the resources reservation could not be modified. This is a permanent failure. • COMMIT_FAILURE (4043): - The lower-tier x-RACF indicates that the resources reservation could not be committed. • REFRESH_FAILURE (4044): - The lower-tier x-RACF indicates that the lifetime of a reservation could not be extended. • QOS_PROFILE_FAILURE (4045): - The lower-tier x-RACF indicates that the request did not match the QoS profile. ETSI ETSI TS 183 071 V3.1.1 (2010-02) 28 • ACCESS_PROFILE_FAILURE (4046): - The lower-tier x-RACF indicates that the request did not match any access profile. • PRIORITY_NOT_GRANTED (4047): - The lower-tier x-RACF indicates that the priority level of the request is not accepted. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 6.4 Use of namespaces | This clause contains the namespaces that have either been created in the present document for the Rr request model, or the values assigned to existing namespaces managed by IANA. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 6.4.1 AVP codes | The present document does not define any new AVPs for the Diameter application for the Rr request model. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 6.4.2 Experimental-Result-Code AVP values | The present document does not define any new Experimental-Result-Code AVP values for the Diameter application for the Rr request model. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 6.4.3 Command Code values | The present document does not assign command code values but uses existing command codes for the Diameter application for the Rr request model. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 6.4.4 Application-ID value | The present document uses value 16777278, allocated by IANA, as application identifier for the Diameter application for the Rr request model. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 6.5 AVPs | This clause summarizes the AVPs used in the present document for the Diameter application for the Rr request model, beyond those defined in the Diameter Base Protocol. The present document does not define any new AVPs for the Diameter application for the Rr request model. ETSI ETSI TS 183 071 V3.1.1 (2010-02) 29 Table 6.1 describes the Diameter AVPs imported from 129 209 [7]. The Vendor-Id header for these AVPs shall be set to 3GPP (10415). Table 6.1: Diameter AVPs imported from TS 129 209 [7] AVP Flag rules (see note 1) Attribute Name AVP Code Clause defined Value Type (see note 2) Must May Should not Must not May encrypt Abort-Cause 500 6.5.1 Enumerated M,V P Y AF-Application-Identifier 504 6.5.2 OctetString M,V P Y AF-Charging-Identifier 505 6.5.3 OctetString M,V P Y Flow-Description 507 6.5.4 IPFilterRule M,V P Y Flow-Number 509 6.5.5 Unsigned32 M,V P Y Flows 510 6.5.6 Grouped M,V P Y Flow-Status 511 6.5.7 Enumerated M,V P Y Flow-Usage 512 6.5.8 Enumerated M,V P Y Specific-Action 513 6.5.9 Enumerated M,V P Y Max-Requested-Bandwidth-DL 515 6.5.10 Unsigned32 M,V P Y Max-Requested-Bandwidth-UL 516 6.5.11 Unsigned32 M,V P Y Media-Component-Description 517 6.5.12 Grouped M,V P Y Media-Component-Number 518 6.5.13 Unsigned32 M,V P Y Media-Sub-Component AVP 519 6.5.14 Grouped M,V P Y Media-Type 520 6.5.15 Enumerated M,V P Y NOTE 1: The AVP header bit denoted as "M", indicates whether support of the AVP is required. The AVP header bit denoted as "V", indicates whether the optional Vendor-ID field is present in the AVP header. For further details, see RFC 3588 [8]. NOTE 2: The value types are defined in RFC 3588 [8]. Table 6.2 describes the Diameter AVPs imported from TS 183 017 [5]. The Vendor-Id header for these AVPs shall be set to ETSI (13019). Table 6.2: Diameter AVPs imported from TS 183 017 [5] AVP Flag rules (see note 1) Attribute Name AVP Code Clause defined Value Type (see note 2) Must May Should not Must not May encrypt Reservation-Class 456 6.5.16 Unsigned32 M,V P Y NOTE 1: The AVP header bit denoted as "M", indicates whether support of the AVP is required. The AVP header bit denoted as "V", indicates whether the optional Vendor-ID field is present in the AVP header. For further details, see RFC 3588 [8]. NOTE 2: The value types are defined in RFC 3588 [8]. Table 6.3 describes the Diameter AVPs imported from ES 283 034 [4]. The Vendor-Id header for these AVPs shall be set to ETSI (13019). Table 6.3: Diameter AVPs imported from [4] AVP Flag rules (see note 1) Attribute Name AVP Code Clause defined Value Type (see note 2) Must May Should not Must not May encrypt Globally-Unique-Address 300 6.5.17 Grouped M, V P Y Address-Realm 301 6.5.18 OctetString M, V P Y Logical-Access-Id 302 6.5.19 OctetString M,V P Y Transport-Class 311 6.5.20 Unsigned32 M,V P Y NOTE 1: The AVP header bit denoted as "M", indicates whether support of the AVP is required. The AVP header bit denoted as "V", indicates whether the optional Vendor-ID field is present in the AVP header. For further details, see RFC 3588 [8]. NOTE 2: The value types are defined in RFC 3588 [8]. ETSI ETSI TS 183 071 V3.1.1 (2010-02) 30 Table 6.4 describes the Diameter AVPs imported from TS 183 026 [10]. The Vendor-Id header for these AVPs shall be set to ETSI (13019). Table 6.4: Diameter AVPs imported from TS 183 026 [10] AVP Flag rules (see note 1) Attribute Name AVP Code Clause defined Value Type (see note 2) Must May Should not Must not May encrypt Session-Bundle-Id 400 6.5.21 Unsigned32 M,V P Y NOTE 1: The AVP header bit denoted as "M", indicates whether support of the AVP is required. The AVP header bit denoted as "V", indicates whether the optional Vendor-ID field is present in the AVP header. For further details, see RFC 3588 [8]. NOTE 2: The value types are defined in RFC 3588 [8]. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 6.5.1 Abort-Cause AVP | The Abort-Cause AVP (AVP code 500) is of type Enumerated, and it determines the cause of an ASR. The following values defined in 129 209 [7] are used: • BEARER_RELEASED (0): - This value is used when the bearer has been deactivated as a result from normal signalling handling. For xDSL, the bearer may refer to an ATM VC. • INSUFFICIENT_SERVER_RESOURCES (1): - This value is used to indicate that the lower-tier x-RACF is overloaded and needs to abort the session. • INSUFFICIENT_BEARER_RESOURCES (2): - This value is used when the bearer has been deactivated due to insufficient bearer resources at a transport gateway (e.g. RCEF policies being removed on an xDSL line). |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 6.5.2 AF-Application-Identifier AVP | The AF-Application-Identifier AVP (AVP code 504) is of type OctetString, and contains information that identifies the RACS client requesting the resources (e.g. name of an ASP or group of ASPs). |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 6.5.3 AF-Charging-Identifier AVP | The AF-Charging-Identifier AVP (AVP code 505) is of type OctetString, contains the AF Charging Identifier that is sent by the AF. This information may be used for charging correlation between AF and RACS functional entities. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 6.5.4 Flow-Description AVP | • 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 IPFilterRule type shall be used with the following restrictions: • Only the Action "permit" shall be used. • No "options" shall be used. • The invert modifier "!" for addresses shall not be used. ETSI ETSI TS 183 071 V3.1.1 (2010-02) 31 • The keyword "assigned" shall not be used. If any of these restrictions is not observed by the top-tier x-RACF, the lower-tier x-RACF shall send an error response to the top-tier x-RACF containing the Experimental-Result-Code AVP with value FILTER_RESTRICTIONS. The Flow description AVP shall be used to describe a single IP flow. The direction "in" refers to IP flows from the subscriber into the access network ("uplink"), and the direction "out" refers to IP flows from the access network to the subscriber ("downlink"). |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 6.5.5 Flow-Number AVP | 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 [13]. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 6.5.6 Flows AVP | 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) are supplied, the Flows AVP refers to all Flows matching the media component number. AVP Format: Flows::= < AVP Header: x > { Media-Component-Number} *[ Flow-Number] |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 6.5.7 Flow-Status AVP | The Flow-Status AVP (AVP code 511) is of type Enumerated, and describes whether the IP flow(s) are enabled or disabled. The Flow-Status AVP may be present in the Media-Description-Component AVP and/or in the Media-Sub-Component AVP. The following values are defined: • ENABLED-UPLINK (0): - This value shall be used to commit the corresponding resource reservation in the uplink direction. • ENABLED-DOWNLINK (1): - This value shall be used to commit the corresponding resource reservation in the downlink direction. • ENABLED (2): - This value shall be used to commit a resource reservation in both directions. • DISABLED (3): - This value shall be used to indicate that the corresponding resource reservation is reserved only and not (yet) committed. • REMOVED (4): - This value shall be used to release all resources associated with the corresponding resource reservation. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 6.5.8 Flow-Usage AVP | The Flow-Usage AVP (AVP code 512) is of type Enumerated, and it provides information about the usage of IP Flows. The following values are defined: • NO_INFORMATION (0): - This value is used to indicate that no information about the usage of the IP flow is being provided. ETSI ETSI TS 183 071 V3.1.1 (2010-02) 32 • RTCP (1): - This value is used to indicate that an IP flow is used to transport RTCP. • NO_INFORMATION is the default value. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 6.5.9 Specific-Action AVP | The Specific-Action AVP (AVP code 513) is of type Enumerated. Within an initial AA-Request the top-tier x-RACF may use the Specific-Action AVP to request from the lower-tier x-RACF notification of specific actions. If the Specific-Action AVP is omitted within the initial AA-Request, no notification of any of the events defined below is requested. The following event from TS 129 209 [7] is supported: • INDICATION_OF_RELEASE_OF_BEARER (4): - Within an AAR, this value shall be used when the lower-tier x-RACF reports to the top-tier x-RACF the release of a bearer (e.g. RCEF policies being removed on an xDSL line). In the AAR, this value indicates that the top-tier x-RACF requests the lower-tier x-RACF to provide a notification at the removal of a bearer. The following events from TS 183 026 [10] are supported: • INDICATION_OF_SUBSCRIBER_DETACHMENT (6): - Within an AAR, this value shall be used when the lower-tier x-RACF reports to the top-tier x-RACF that a subscriber has been detached. In the AAR, this value indicates that the top-tier x-RACF requests the lower-tier x-RACF to provide a notification at the detachment of a subscriber. • INDICATION_OF_RESERVATION_EXPIRATION (7): - Within an AAR, this value shall be used when the lower-tier x-RACF reports to the top-tier x-RACF that a reservation is about to expire. In the AAR, this value indicates that the top-tier x-RACF requests the lower-tier x-RACF to provide a notification when a reservation expires. Other events but the above-listed ones defined by TS 129 209 [7] are not relevant at the Rr interface and are not supported. If specified by the top-tier x-RACF, these values are ignored by the lower-tier x-RACF. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 6.5.10 Max-Requested-Bandwidth-DL AVP | The Max-Requested-Bandwidth-DL AVP (AVP code 515) is type Unsigned32, and it indicates the maximum requested bandwidth in bits per second for a downlink IP flow. The bandwidth includes the bandwidth of the IP payload, including the overhead coming from the IP header. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 6.5.11 Max-Requested-Bandwidth-UL AVP | The Max -Bandwidth-UL AVP (AVP code 516) is of type Unsigned32, and it indicates the maximum requested bandwidth in bits per second for an uplink IP flow. The bandwidth includes the bandwidth of the IP payload, including the overhead coming from the IP header. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 6.5.12 Media-Component-Description AVP | The Media-Component-Description AVP (AVP code 517) is of type Grouped, and it contains service information for a single media component within a session. It may be based on the SDI exchanged between the AF and the AF client in the UE. The information shall be used by the lower-tier x-RACF to determine the QoS requirements. Within one Diameter message, a single IP flow shall not be described by more than one Media-Component-Description AVP. The Media-Component-Description AVP may contain the Flow-Status AVP, which indicates the particular reservation operation to be performed on the media, as described in clauses 5.1 and 5.2. ETSI ETSI TS 183 071 V3.1.1 (2010-02) 33 Bandwidth information provided within the Media-Component-Description AVP applies to all those IP flows within the media component, for which no corresponding information is being provided within Media-Sub-Component AVP(s). If a Media-Component-Description AVP is not supplied, or if optional AVP(s) within a Media-Component-Description AVP are omitted, but corresponding information has been provided in previous Diameter messages, the previous information for the corresponding IP flow(s) remains valid. AVP format: Media-Component-Description ::= < AVP Header: 517> { Media-Component-Number } ; Ordinal number of the media comp. *[ Media-Sub-Component ] ; Set of flows for one flow identifier [ AF-Application-Identifier ] [ Media-Type ] [ Max-Requested-Bandwidth-UL ] [ Max-Requested-Bandwidth-DL ] [ Flow-Status ] [ RS-Bandwidth ] [ RR-Bandwidth ] [ Reservation-Class ] [ Transport-Class ] |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 6.5.13 Media-Component-Number AVP | The Media-Component-Number AVP (AVP code 518) is of type Unsigned32, and it contains the ordinal number of the media component, assigned according to the rules in annex C of TS 129 207 [13]. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 6.5.14 Media-Sub-Component AVP | The Media-Sub-Component AVP (AVP code 519) is of type Grouped, and it contains the requested QoS and filters for the set of IP flows identified by their common Flow-Identifier. The Flow-Identifier is defined in TS 129 207 [13]. The Media-Sub-Component AVP may contain the Flow-Status AVP, which indicates the particular reservation operation to be performed on the flow, as described in clauses 5.1 and 5.2. Possible Bandwidth information provided within the Media-Sub-Component AVP takes precedence over information within the encapsulating Media Component Description AVP. If a Media-Sub-Component AVP is not supplied, or if optional AVP(s) within a Media-Sub-Component AVP are omitted, but corresponding information has been provided in previous Diameter messages, the previous information for the corresponding IP flow(s) remains valid, unless new information is provided within the encapsulating Media-Component-Description AVP. If Flow-Description AVP(s) are supplied, they replace all previous Flow-Description AVP(s), even if a new Flow-Description AVP has the opposite direction as the previous Flow-Description AVP. AVP Format: Media-Sub-Component ::= < AVP Header: 519 > { Flow-Number } ; Ordinal number of the IP flow [ Flow-Status ] 0*2[ Flow-Description ] ; UL and/or DL [ Flow-Usage ] [ Max-Requested-Bandwidth-UL ] [ Max-Requested-Bandwidth-DL ] |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 6.5.15 Media-Type AVP | The Media-Type AVP (AVP code 520) is of type Enumerated, and it determines the media type of a session component. The following values are defined: • AUDIO (0). • VIDEO (1). • DATA (2). • APPLICATION (3). ETSI ETSI TS 183 071 V3.1.1 (2010-02) 34 • CONTROL (4). • TEXT (5). • MESSAGE (6). • OTHER (0xFFFFFFFF). |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 6.5.16 Reservation-Class AVP | The Reservation-Class AVP (AVP code 456) is of type Unsigned32, and it contains an integer used as an index pointing to the traffic characteristics of the flow (e.g. burstiness and packet size). |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 6.5.17 Globally-Unique-Address AVP | The Globally-Unique-Address AVP (AVP code 300) is of type Grouped. AVP Format: Globally-Unique-Address ::= < AVP Header: 300 13019 > [Framed-IP-Address] [Framed-IPv6-Prefix] [Address-Realm] |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 6.5.18 Address-Realm AVP | The Address-Realm AVP (AVP code 301) is of type OctetString. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 6.5.19 Logical-Access-ID AVP | The Logical-Access-ID AVP (AVP code 302 13019) is of type OctetString. It is defined in ES 283 034 [4]. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 6.5.20 Session-Bundle-Id AVP | The Session-Bundle-Id (AVP code 400) is of type Unsigned32. It may be specified by the lower-tier x-RACF in the AA-Answer, when the initial reservation is granted, in order to identify the group of sessions to which the session of the AA-Answer belongs. The value of the Session-Bundle-Id AVP is meaningful for the lower-tier x-RACF only. It may be included by the lower-tier x-RACF in subsequent Abort-Session-Request (ASR) messages sent to the top-tier x-RACF. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 6.5.21 Transport-Class AVP | The Transport-Class AVP (AVP code 311) is of type Unsigned32, and it contains an integer used as an index pointing to a class of transport services to be applied (e.g. forwarding behaviour). |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 7 DIAMETER application for Delegated Model | With the clarifications listed in the following clauses the Diameter base protocol defined by RFC 3588 [8] shall apply. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 7.1 Use of the Diameter base protocol | |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 7.1.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 [14]. ETSI ETSI TS 183 071 V3.1.1 (2010-02) 35 |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 7.1.2 Accounting functionality | Accounting functionality (accounting session state machine, related command codes and AVPs) is not used for the delegated model of the Rr interface. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 7.1.3 Use of sessions | Diameter sessions are implicitly terminated. An implicitly terminated session is one for which the server does not maintain state information. The client does not need to send any re-authorization or session termination requests to the server. The Diameter base protocol includes the Auth-Session-State AVP as the mechanism for the implementation of implicitly terminated sessions. The client (server) shall include in its requests (responses) the Auth-Session-State AVP set to the value NO_STATE_MAINTAINED (1), as described in RFC 3588 [8]. As a consequence, the server does not maintain any state information about this session and the client does not need to send any session termination request. Neither the Authorization-Lifetime AVP nor the Session-Timeout AVP shall be present in requests or responses. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 7.1.4 Transport protocol | Diameter messages over the delegated model of the Rr interface shall make use of SCTP RFC 4960 [12] and shall utilize the new SCTP checksum method specified in RFC 4960 [12]. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 7.1.5 Routing considerations | This clause specifies the use of the Diameter routing AVPs Destination-Realm and Destination-Host. Requests initiated by the delegating x-RACF towards the RACS shall include both Destination-Host and Destination-Realm AVPs. The delegating x-RACF obtains the Destination-Host AVP to use in requests towards a delegated x-RACF, from configuration data and/or the NASS User profile. Consequently, the Destination-Host AVP is declared as mandatory in the ABNF for all requests initiated by the delegating x-RACF. Requests initiated by the delegated x-RACF towards the delegating x-RACF shall include both Destination-Host and Destination-Realm AVPs. The delegated x-RACF obtains the Destination-Host AVP to use in requests towards a delegating x-RACF, from the Origin-Host and Origin-Realm AVPs received in previous commands from the delegating x-RACF. Consequently, the Destination-Host AVP is declared as mandatory in the ABNF for all requests initiated by the delegated x-RACF. Destination-Realm AVP is declared as mandatory in the ABNF for all requests. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 7.1.6 Advertising application support | The delegating x-RACF and the delegated x-RACF shall advertise support of the Rr specific application for delegated model by including the value 16777279 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 Supported-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, support of 3GPP AVPs shall be advertised by adding the vendor identifier value of 3GPP (10415) to the Supported-Vendor-Id AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer 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]. ETSI ETSI TS 183 071 V3.1.1 (2010-02) 36 |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 7.2 Commands | The Rr interface for Rr delegated model re-uses and modifies commands defined in TS 129 329 [15], RFC 3588 [8] or RFC 4006 [6] as follows. Table 7.1: Command-code values Command-Name Abbreviation Code Defined In User-Data-Request UDR 306 TS 129 329 [15] User-Data-Answer UDA 306 TS 129 329 [15] Push-Notification-Request PNR 309 TS 129 329 [15] Push-Notification-Answer PNA 309 TS 129 329 [15] Re-Auth-Request RAR 258 RFC 3588 [8] Re-Auth-Answer RAA 258 RFC 3588 [8] CC-Request CCR 272 RFC 4006 [6] CC-Answer CCA 272 RFC 4006 [6] AVPs defined in TS 129 329 [15], RFC 3588 [8] or RFC 4006 [6] and not used in the Rr interface for Rr delegated model are not shown in the below clauses. If received, these AVPs shall be ignored by the delegating x-RACF and the delegated x-RACF. New AVPs are represented in bold. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 7.2.1 User-Data-Request command | The User-Data-Request (UDR) command, indicated by the Command-Code field set to 306 and the "R" bit set in the Command Flags field, is sent by a delegated x-RACF to a delegating x-RACF to request an operation on delegation. Message Format: < User-Data -Request > ::= < Diameter Header: 306, REQ, PXY, 16777279> < Session-Id > { Vendor-Specific-Application-Id } { Auth-Session-State } { Origin-Host } { Origin-Realm } [ Destination-Host ] { Destination-Realm } [Network-Resource-Id] [Preferred-Delegated-Bandwidth-UL] [Preferred-Delegated-Bandwidth-DL] [Required-Delegated-Bandwidth-UL] [Required-Delegated-Bandwidth-DL] [Reservation-priority] *[ AVP ] *[ Proxy-Info ] *[ Route-Record ] |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 7.2.2 User-Data-Answer command | The User-Data-Answer (UDA) command, indicated by the Command-Code field set to 306 and the "R" bit cleared in the Command Flags field, is sent by a delegating x-RACF in response to the User-Data-Request command. Message Format: < User-Data-Answer > ::= < Diameter Header: 306, PXY, 16777279> < Session-Id > { Vendor-Specific-Application-Id } [ Result-Code ] [ Experimental-Result ] { Auth-Session-State } { Origin-Host } { Origin-Realm } [Granted-Delegated-Bandwidth-UL] [Granted-Delegated-Bandwidth-DL] [Total-Bandwidth-UL] [Total-Bandwidth-DL] *[ AVP ] ETSI ETSI TS 183 071 V3.1.1 (2010-02) 37 *[ Failed-AVP ] *[ Proxy-Info ] *[ Route-Record ] |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 7.2.3 Push-Notification-Request command | The Push-Notification-Request (PNR) command, indicated by the Command-Code field set to 309 and the "R" bit set in the Command Flags field, is sent by a delegating x-RACF to a delegated x-RACF to request an operation on delegation. Message Format: < Push-Notification-Request > ::= < Diameter Header: 309, REQ, PXY, 16777279> < Session-Id > { Vendor-Specific-Application-Id } { Auth-Session-State } { Origin-Host } { Origin-Realm } { Destination-Host } { Destination-Realm } [Network-Resource-Id] [Granted-Delegated-Bandwidth-UL] [Granted-Delegated-Bandwidth-DL] [Preferred-Delegated-Bandwidth-UL] [Preferred-Delegated-Bandwidth-DL] [Required-Delegated-Bandwidth-UL] [Required-Delegated-Bandwidth-DL] [Reservation-priority] [Total-Bandwidth-UL] [Total-Bandwidth-DL] *[ Authorization-Package-Id ] *[ AVP ] *[ Proxy-Info ] *[ Route-Record ] |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 7.2.4 Push-Notification-Answer command | The Push-Notifications-Answer (PNA) command, indicated by the Command-Code field set to 309 and the "R" bit cleared in the Command Flags field, is sent by a delegated x-RACF in response to the Push-Notification-Request command. Message Format: < Push-Notification-Answer > ::= < Diameter Header: 309, PXY, 16777279> < Session-Id > { Vendor-Specific-Application-Id } [ Result-Code ] [ Experimental-Result ] { Auth-Session-State } { Origin-Host } { Origin-Realm } [Granted-Delegated-Bandwidth-UL] [Granted-Delegated-Bandwidth-DL] [Total-Bandwidth-UL] [Total-Bandwidth-DL] *[ AVP ] *[ Failed-AVP ] *[ Proxy-Info ] *[ Route-Record ] ETSI ETSI TS 183 071 V3.1.1 (2010-02) 38 |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 7.2.5 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 delegated x-RACF to the delegating x-RACF in order to indicate a specific action. The values INDICATION_OF_RELEASE_OF_BEARER, INDICATION_OF_SUBSCRIBER_DETACHMENT and 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, 16777279> < Session-Id > { Auth-Session-State } { Origin-Host } { Origin-Realm } { Destination-Host } { Destination-Realm } { Auth-Application-Id } *{ Specific-Action } *[ Flow-Description ] [ Globally-Unique-Address ] [ Logical-Access-Id ] [ Abort-Cause ] [ Origin-State-Id ] *[ Proxy-Info ] *[ Route-Record ] *[ AVP ] |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 7.2.6 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 delegating x-RACF to the delegated x-RACF in response to the RAR command. Message Format: <RA-Answer> ::= < Diameter Header: 258, PXY, 16777279> < Session-Id > { Auth-Session-State } { Origin-Host } { Origin-Realm } [ Result-Code ] [ Experimental-Result ] [ Origin-State-Id ] [ Error-Message ] [ Error-Reporting-Host ] *[ Failed-AVP ] *[ Proxy-Info ] *[ AVP ] |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 7.2.7 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 delegating x-RACF to the delegated x-RACF in order to report the occurrence of particular event. Message Format: <CC-Request> ::= < Diameter Header: 272, REQ, PXY, 16777279> < Session-Id > { Auth-Session-State } { Origin-Host } { Origin-Realm } { Destination-Realm } { Destination-Host } { Auth-Application-Id } *{ Specific-Action } *[ Flow-Description ] [ Globally-Unique-Address ] [ Logical-Access-Id ] [ Abort-Cause ] [ Origin-State-Id ] *[ Proxy-Info ] ETSI ETSI TS 183 071 V3.1.1 (2010-02) 39 *[ Route-Record ] *[ AVP ] |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 7.2.8 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 delegated x-RACF to the delegating x-RACF in answer to the CCR. Message Format: <CC-Answer> ::= < Diameter Header: 272, PXY, 16777279> < Session-Id > { Auth-Session-State } { Origin-Host } { Origin-Realm } { Auth-Application-Id } [ Result-Code ] [ Experimental-Result ] [ Origin-State-Id ] [ Error-Message ] [ Error-Reporting-Host ] *[ Failed-AVP ] *[ Proxy-Info ] *[ AVP ] |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 7.3 Experimental-Result-Code AVP values | |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 7.3.1 Experimental-Result-Code AVP values imported from ES 283 034 | The present document reuses existing Experimental-Result-Code AVP values defined in ES 283 034 [4] as follows: • DIAMETER_SYSTEM_UNAVAILABLE (4001): - This error is returned when a request could not be satisfied at the time that it was received due to a temporary internal failure or congestion. When this result code is used, the ETSI Vendor ID shall be included in the Vendor-Id AVP of the Experimental-Result AVP. 7.3.2 Experimental-Result-Code AVP values defined in the present document This clause defines the specific values of the Experimental-Result-Code AVP (vendor-id is ETSI) for the Diameter application for the Rr delegated model: • NETWORK_RESOURCE_UNAVAILABLE (4061): - The delegating or delegated x-RACF indicates the network resource identified by the Network-Resource- Id AVP is unknown or is not handled in the current entity or is not allowed to be delegated between the delegating x-RACF and the delegated x-RACF. • NETWORK_RESOURCE_INSUFFICIENT (4062): - The delegating or delegated x-RACF indicates there is insufficient network resource to perform the requested action. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 7.4 Use of namespaces | This clause contains the namespaces that have either been created in the present document for the Rr delegated model, or the values assigned to existing namespaces managed by IANA. ETSI ETSI TS 183 071 V3.1.1 (2010-02) 40 |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 7.4.1 AVP codes | The present document assigns the AVP values in the 650 to 699 range from the AVP Code namespace managed by ETSI for the Diameter application for the Rr delegated model. See clause 7.5 for the assigned values. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 7.4.2 Experimental-Result-Code AVP values | The present document assigns the Experimental-Result-Code AVP values from the AVP Code namespace managed by ETSI for the Diameter application for the Rr delegated model. See clause 7.3 for the assigned values. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 7.4.3 Command Code values | The present document does not assign command code values but uses existing command codes for the Diameter application for the Rr delegated model. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 7.4.4 Application-ID value | The present document uses value 16777279, allocated by IANA, as application identifier for the Diameter application for the Rr delegated model. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 7.5 AVPs | This clause summarizes the AVPs used in the present document for the Diameter application for the Rr delegated model, beyond those defined in the Diameter Base Protocol. Table 7.2 describes the Diameter AVPs defined in the present document, their AVP Code values, types, possible flag values and whether the AVP may be encrypted. The vendor-Id header of all AVPs defined in the present document shall be set to ETSI (13019). Table 7.2: Diameter AVPs defined in the present document AVP Flag rules (see note 1) Attribute Name AVP Code Clause defined Value Type (see note 2) Must May Should not Must not May encrypt Network-Resource-Id 650 7.5.1 OctetString M,V P Y Preferred-Delegated- Bandwidth-UL 651 7.5.2 Unsigned32 M,V P Y Preferred-Delegated- Bandwidth-DL 652 7.5.3 Unsigned32 M,V P Y Required-Delegated- Bandwidth-UL 653 7.5.4 Unsigned32 M,V P Y Required-Delegated- Bandwidth-DL 654 7.5.5 Unsigned32 M,V P Y Granted-Delegated- Bandwidth-UL 655 7.5.6 Unsigned32 M,V P Y Granted-Delegated- Bandwidth-DL 656 7.5.7 Unsigned32 M,V P Y Total-Bandwidth-UL 657 7.5.8 Unsigned32 M,V P Y Total-Bandwidth-DL 658 7.5.9 Unsigned32 M,V P Y NOTE 1: The AVP header bit denoted as "M", indicates whether support of the AVP is required. The AVP header bit denoted as "V", indicates whether the optional Vendor-ID field is present in the AVP header. For further details, see RFC 3588 [8]. NOTE 2: The value types are defined in RFC 3588 [8]. Table 7.3 describes the Diameter AVPs imported from TS 183 017 [5]. The Vendor-Id header of these AVPs shall be set to ETSI (13019). ETSI ETSI TS 183 071 V3.1.1 (2010-02) 41 Table 7.3: Diameter AVPs imported from TS 183 017 [5] AVP Flag rules (see note 1) Attribute Name AVP Code Clause defined Value Type (see note 2) Must May Should not Must not May encrypt Reservation-Priority 458 7.5.10 Enumerated V M Y Authorization-Package-Id 461 7.5.11 UTF8String V M Y NOTE 1: The AVP header bit denoted as "M", indicates whether support of the AVP is required. The AVP header bit denoted as "V", indicates whether the optional Vendor-ID field is present in the AVP header. For further details, see RFC 3588 [8]. NOTE 2: The value types are defined in RFC 3588 [8]. Table 7.4 describes the Diameter AVPs imported from TS 129 209 [7]. The Vendor-Id header for these AVPs shall be set to 3GPP (10415). Table 7.4: Diameter AVPs imported from TS 129 209 [7] AVP Flag rules (see note 1) Attribute Name AVP Code Clause defined Value Type (see note 2) Must May Should not Must not May encrypt Abort-Cause 500 7.5.12 Enumerated M,V P Y Flow-Description 507 7.5.13 IPFilterRule M,V P Y Specific-Action 513 7.5.14 Enumerated M,V P Y NOTE 1: The AVP header bit denoted as "M", indicates whether support of the AVP is required. The AVP header bit denoted as "V", indicates whether the optional Vendor-ID field is present in the AVP header. For further details, see RFC 3588 [8]. NOTE 2: The value types are defined in RFC 3588 [8]. Table 7.5 describes the Diameter AVPs imported from ES 283 034 [4]. The Vendor-Id header of these AVPs shall be set to ETSI (13019). Table 7.5: Diameter AVPs imported from e4 interface ES 283 034 [4] AVP Flag rules Attribute Name AVP Code Clause defined Value Type Must May Should not Must not May Encrypt Globally-Unique-Address 300 7.5.15 Grouped V M Y Address-Realm 301 7.5.16 OctetString V M Y Logical-Access-Id 302 7.5.17 OctetString V M Yes NOTE: The AVP header bit denoted as "M", indicates whether support of the AVP is required. The AVP header bit denoted as "V", indicates whether the optional Vendor-ID field is present in the AVP header. For further details, see TS 133 210 [11]. Table 7.6 describes the Diameter AVPs imported from RFC 4005 [9]. No Vendor-Id header shall be included in these AVPs. Table 7.6: Diameter AVPs imported from RFC 4005 [9] AVP Flag rules Attribute Name AVP Code Section defined Value Type Must May Should not Must not May Encrypt Framed-IP-Address 8 7.5.18 OctetString V,M Y Framed-IPv6-Prefix 97 7.5.19 OctetString V,M Y |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 7.5.1 Network-Resource-Id AVP | The Network-Resource-Id AVP (AVP code 650) is of type OctetString, it contains the identifier of the network resource. ETSI ETSI TS 183 071 V3.1.1 (2010-02) 42 |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 7.5.2 Preferred-Delegated-Bandwidth-UL AVP | The Preferred-Delegated-Bandwidth-UL AVP (AVP code 651) is type Unsigned32, and it indicates the preferred delegated bandwidth requested in kbits per second in the uplink direction. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 7.5.3 Preferred-Delegated-Bandwidth-DL AVP | The Preferred-Delegated-Bandwidth-DL AVP (AVP code 652) is type Unsigned32, and it indicates the preferred delegated bandwidth requested in kbits per second in the downlink direction. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 7.5.4 Required-Delegated-Bandwidth-UL AVP | The Required-Delegated-Bandwidth-UL AVP (AVP code 653) is type Unsigned32, and it indicates the required delegated bandwidth requested in kbits per second in the uplink direction. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 7.5.5 Required-Delegated-Bandwidth-DL AVP | The Required-Delegated-Bandwidth-DL AVP (AVP code 654) is type Unsigned32, and it indicates the required delegated bandwidth requested in kbits per second in the downlink direction. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 7.5.6 Granted-Delegated-Bandwidth-UL AVP | The Granted-Delegated-Bandwidth-UL AVP (AVP code 655) is type Unsigned32, and it indicates the granted delegated bandwidth in kbits per second in the uplink direction. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 7.5.7 Granted-Delegated-Bandwidth-DL AVP | The Granted-Delegated-Bandwidth-DL AVP (AVP code 656) is type Unsigned32, and it indicates the granted delegated bandwidth in kbits per second in the downlink direction. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 7.5.8 Total-Bandwidth-UL AVP | The Total-Bandwidth-UL AVP (AVP code 657) is type Unsigned32, and it indicates the total bandwidth in kbits per second in the uplink direction. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 7.5.9 Total-Bandwidth-DL AVP | The Total-Bandwidth-DL AVP (AVP code 658) is type Unsigned32, and it indicates the total bandwidth in kbits per second in the downlink direction. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 7.5.10 Reservation-priority AVP | The Reservation-Priority AVP (AVP code 458) is of type Enumerated. The following values are specified. DEFAULT (0): This is the lowest level of priority. If no Reservation-Priority AVP is specified in the AA-Request, this is the priority associated with the reservation. • PRIORITY-ONE (1). • PRIORITY-TWO (2). • PRIORITY-THREE (3). • PRIORITY-FOUR (4). • PRIORITY-FIVE (5). • PRIORITY-SIX (6). ETSI ETSI TS 183 071 V3.1.1 (2010-02) 43 • PRIORITY-SEVEN (7). • PRIORITY-EIGHT (8). • PRIORITY-NINE (9). • PRIORITY-TEN (10). • PRIORITY-ELEVEN (11). • PRIORITY-TWELVE (12). • PRIORITY-THIRTEEN (13). • PRIORITY-FOURTEEN (14). • PRIORITY-FIFTEEN (15). |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 7.5.11 Authorization-Package-Id AVP | The Authorization-Package-Id AVP (AVP code 461) is of type UTF8String, and it identifies an authorization context requested by the AF for the session and passed transparently through Rq. This information is used by the delegated x-RACF to derive the policy to be passed to an RCEF through the Re reference point for the session. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 7.5.12 Abort-Cause AVP | The Abort-Cause AVP (AVP code 500) is of type Enumerated, and it determines the cause of an ASR. The following values defined in TS 129 209 [7] are used: • INSUFFICIENT_SERVER_RESOURCES (1): - This value is used to indicate that the x-RACF is overloaded. • INSUFFICIENT_BEARER_RESOURCES (2): - This value is used when the bearer has been deactivated due to insufficient bearer resources at a transport gateway (e.g. RCEF for xDSL). |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 7.5.13 Flow-Description AVP | 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 b type shall be used with the following restrictions: • Only the Action "permit" shall be used. • No "options" shall be used. • The invert modifier "!" for addresses shall not be used. • The keyword "assigned" shall not be used. The direction "in" refers to uplink IP flows, and the direction "out" refers to downlink IP flows. ETSI ETSI TS 183 071 V3.1.1 (2010-02) 44 |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 7.5.14 Specific-Action AVP | The Specific-Action AVP (AVP code 513) is of type Enumerated. The following event from TS 129 209 [7] is supported: • INDICATION_OF_RELEASE_OF_BEARER (4): - Within a RAR, this value shall be used when the delegated x-RACF reports to the delegating x-RACF the release of a bearer (e.g. RCEF policies being removed). In case of failure of a multicast request, the RAR message includes the address of the UE that requested the multicast flow and the flow description of the flow. - Within a CCR, this value shall be used when the delegating x-RACF reports to the delegated x-RACF the release of a bearer (e.g. RCEF policies being removed). In case of failure of a multicast request, the CCR message includes the address of the UE that requested the multicast flow and the flow description of the flow. In addition, the present document defines two new events: • INDICATION_OF_SUBSCRIBER_DETACHMENT (6): - Within a RAR, this value shall be used when the delegated x-RACF reports to the delegating x-RACF that a subscriber has been detached. - Within a CCR, this value shall be used when the delegating x-RACF reports to the delegated x-RACF that a subscriber has been detached. • INDICATION_OF_RESERVATION_EXPIRATION (7): - Within a RAR, this value shall be used when the delegated x-RACF reports to the delegating x-RACF that a reservation is about to expire. - Within a CCR, this value shall be used when the delegating x-RACF reports to the delegated x-RACF that a reservation is about to expire. Other events but the above-listed ones defined by TS 129 209 [7] are not relevant at the Rr interface and are not supported. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 7.5.15 Globally-Unique-Address AVP | The Globally-Unique-Address AVP (AVP code 300) is of type Grouped. AVP Format: Globally-Unique-Address ::= < AVP Header: 300 13019 > [Framed-IP-Address] [Framed-IPv6-Prefix] [Address-Realm] |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 7.5.16 Address-Realm AVP | The Address-Realm AVP (AVP code 301) is of type OctetString and contains an address realm in the form of a FQDN. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 7.5.17 Logical-Access-ID AVP | The Logical-Access-ID AVP (AVP code 302 13019) is of type OctetString. It is defined in ES 283 034 [4]. |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 7.5.18 Framed-IP-Address AVP | The Framed-IP-Address AVP (AVP Code 8) is of type OctetString and contains an IPv4 address of the type specified in the attribute value to be configured for the user. ETSI ETSI TS 183 071 V3.1.1 (2010-02) 45 |
94c82513a2001364c90e5aadbf7f640d | 183 071 | 7.5.19 Framed-IPv6-Prefix AVP | The Framed-IPv6-Prefix AVP (AVP Code 97) is of type OctetString and contains the IPv6 prefix to be configured for the user. ETSI ETSI TS 183 071 V3.1.1 (2010-02) 46 History Document history V3.1.1 February 2010 Publication |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 1 Scope | The present document defines a profile of the Gateway Control Protocol (H.248.1 [15]), for controlling access and residential gateways connecting analog lines and ISDN primary and basic accesses, in order to emulate PSTN/ISDN services over IP. 1.1 Differences between H.248 ARGW Profiles Version 1 and Version 2 The differences between both H.248 profile versions are detailed in annex A. Summary list of differences: 1) Package usage details (see clause 5.14.2). 2) IUA/SCTP encapsulation for Q.921 p-/f-type frames in IP domain (see clause 7.3.2). 3) Additional V5 support (see clause 7.4). 4) Adaptive-rate based MGC overload control (see clause 8.1.2). 5) Real time statistics reporting (see clause 8.4). 1.2 Differences between H.248 ARGW Profiles Version 2 and Version 3 The differences between both H.248 profile versions are detailed in annex A. Summary list of differences: 1) traffic volume related statistics on application data level (see clause 8.5); 2) V.152 compliant VBDoIP service (see clause 6.2); 3) addition of Digit Dialling Method Information for Extended Digit Maps Package; and 4) a keep pinhole open method for NAT traversal support (see clause 6.9). |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 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. ETSI ETSI TS 183 002 V3.3.1 (2009-08) 8 |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 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: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Functional Architecture Release 1". [2] ETSI ES 282 002: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN Emulation Sub-system (PES); Functional architecture". [3] ETSI ES 201 970: "Access and Terminals (AT); Public Switched Telephone Network (PSTN); Harmonized specification of physical and electrical characteristics at a 2-wire analogue presented Network Termination Point (NTP)". [4] ETSI EN 300 659-1: "Access and Terminals (AT); Analogue access to the Public Switched Telephone Network (PSTN); Subscriber line protocol over the local loop for display (and related) services; Part 1: On-hook data transmission". [5] ETSI EN 300 659-2: "Access and Terminals (AT); Analogue access to the Public Switched Telephone Network (PSTN); Subscriber line protocol over the local loop for display (and related) services; Part 2: Off-hook data transmission". [6] ETSI ETS 300 099: "Integrated Services Digital Network (ISDN); Specification of the Packet Handler access point Interface (PHI)". [7] ETSI EN 301 141-1: "Integrated Services Digital Network (ISDN); Narrowband Multi-service Delivery System (NMDS); Part 1: NMDS interface specification". [8] ETSI ETS 300 402-2: "Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS1) protocol; Data link layer; Part 2: General protocol specification [ITU-T Recommendation Q.921 (1993), modified]". [9] ETSI EN 300 367: "Integrated Services Digital Network (ISDN); Explicit Call Transfer (ECT) supplementary service; Service description". [10] ETSI TS 102 333: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Gate control protocol". [11] ITU-T Recommendation H.248.45: "Gateway control protocol: MGC information package". [12] IETF RFC 4233 (2006-01): "Integrated Services Digital Network (ISDN) Q.921-User Adaptation Layer". [13] ETSI TBR 003: "Integrated Services Digital Network (ISDN); Attachment requirements for terminal equipment to connect to an ISDN using ISDN basic access". [14] ETSI TBR 004: "Integrated Services Digital Network (ISDN); Attachment requirements for terminal equipment to connect to an ISDN using ISDN primary rate access". [15] ITU-T Recommendation H.248.1 + Corrigendum 1: "Gateway control protocol: Version 2". [16] ITU-T Recommendation H.248.2: "Gateway control protocol: Facsimile, text conversation and call discrimination packages". [17] ITU-T Recommendation H.248.4 + Corrigendum 1: "Gateway control protocol: Transport over Stream Control Transmission Protocol (SCTP)". [18] ITU-T Recommendation H.248.7: "Gateway control protocol: Generic Announcement package". [19] ITU-T Recommendation H.248.11: "Gateway control protocol: Media gateway overload control package". [20] ITU-T Recommendation H.248.13: "Gateway control protocol: Quality Alert Ceasing package". ETSI ETSI TS 183 002 V3.3.1 (2009-08) 9 [21] ITU-T Recommendation H.248.14: "Gateway control protocol: Inactivity timer package". [22] ITU-T Recommendation H.248.16 + Corrigendum 1: "Gateway control protocol: Enhanced digit collection packages and procedures". [23] ITU-T Recommendation H.248.23: "Gateway control protocol: Enhanced Alerting packages". [24] ITU-T Recommendation H.248.26 + Amendment 1: "Gateway control protocol: Enhanced analog lines packages". [25] ITU-T Recommendation H.248.34: "Gateway control protocol: Stimulus analogue lines package". [26] ITU-T Recommendation Q.1950: "Bearer independent call bearer control protocol". [27] ITU-T Recommendation G.711: "Pulse code modulation (PCM) of voice frequencies". [28] ITU-T Recommendation G.711 Appendix I: "A high quality low-complexity algorithm for packet loss concealment with G.711". [29] ITU-T Recommendation G.711 Appendix II: "A comfort noise payload definition for ITU-T G.711 use in packet-based multimedia communication systems". [30] ITU-T Recommendation T.38: "Procedures for real-time Group 3 facsimile communication over IP networks". [31] ITU-T Recommendation V.150.1: "Modem-over-IP networks: Procedures for the end-to-end connection of V-series DCEs". [32] ITU-T Recommendation V.152 + Corrigendum 1 + Corrigendum 2: "Procedures for supporting voice-band data over IP networks". [33] ITU-T Recommendation E.180: "Technical characteristics of tones for the telephone service". [34] IETF RFC 2327: "SDP: Session Description Protocol". [35] IETF RFC 3551: "RTP Profile for Audio and Video Conferences with Minimal Control". [36] IETF RFC 4301: "Security Architecture for the Internet Protocol". [37] IETF RFC 4733: "RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals". [38] IETF RFC 2784: "Generic Routing Encapsulation (GRE)". [39] IETF RFC 4040: "RTP Payload Format for a 64 kbit/s Transparent Call". [40] IETF RFC 4855: "Media Type Registration of RTP Payload Formats". [41] ITU-T Recommendation G.168: "Digital network echo cancellers". [42] IETF RFC 2733: "An RTP Payload Format for Generic Forward Error Correction". [43] IETF RFC 2198: "RTP Payload for Redundant Audio Data". [44] ITU-T Recommendation Q.115.0: "Protocols for the control of signal processing network elements and functions". [45] ITU-T Recommendation Q.115.1: "Logic for the control of echo control devices and functions". [46] ITU-T Recommendation Q.921: "ISDN user-network interface - Data link layer specification". [47] ETSI ETS 300 297: "Integrated Services Digital Network (ISDN); Access digital section for ISDN basic access". [48] ETSI ETS 300 233: "Integrated Services Digital Network (ISDN); Access digital section for ISDN primary rate". [49] ITU-T Recommendation H.248.17: "Gateway control protocol: Line test packages". ETSI ETSI TS 183 002 V3.3.1 (2009-08) 10 [50] ETSI ES 201 235-3: "Access and Terminals (AT); Specification of Dual-Tone Multi-Frequency (DTMF) Transmitters and Receivers; Part 3: Receivers". [51] IETF RFC 3389: "Real-time Transport Protocol (RTP) Payload for Comfort Noise (CN)". [52] ETSI ES 283 002 (V1.1.3): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Release 1 H.248 Profile for controlling Access and Residential Gateways". [53] IETF RFC 3807 (2004): "V5.2-User Adaptation Layer (V5UA)". [54] ETSI EN 300 324-1: "V interfaces at the digital Local Exchange (LE); V5.1 interface for the support of Access Network (AN); Part 1: V5.1 interface specification". [55] ETSI EN 300 347-1: "V interfaces at the digital Local Exchange (LE); V5.2 interface for the support of Access Network (AN); Part 1: V5.2 interface specification". [56] ITU-T Recommendation H.248.47+Revision 1 (2008-07): "Gateway control protocol: Statistic conditional reporting package". [57] ETSI ES 283 039-4 (V2.1.1): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Overload Control Architecture; Part 4: Adaptative Control for the MGC". [58] IETF RFC 2960: "Stream Control Transmission Protocol". [59] ETSI TS 102 144: "Services and Protocols for Advanced Networks (SPAN); MTP/SCCP/SSCOP and SIGTRAN (Transport of SS7 over IP); Stream Control Transmission Protocol (SCTP) [Endorsement of RFC 2960 and RFC 3309, modified]". [60] ITU-T Recommendation H.248.58 (06/2008): "Gateway Control Protocol: Packages for application level H.248 Statistics". [61] ITU-T Recommendation H.248.52 (2008): "Gateway control protocol: QoS Support Packages". [62] ETSI ES 283 002 (V2.1.0): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); H.248 Profile for controlling Access and Residential Gateways". [63] Void. [64] ITU-T Recommendation H.248.70 (2009): "Gateway control protocol: Dialling method information packages". [65] IETF RFC 5109: "RTP Payload Format for Generic Forward Error Correction". [66] IETF RFC 4734: "Definition of Events for Modem, Fax, and Text Telephony Signals". |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 2.2 Informative references | [i.1] ETSI TR 183 025 (Release 2): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); H.248 Non-call related procedures and management system interaction". [i.2] ETSI TR 183 040 (V1.1.1): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); H.248 POTS Message Flows based on the H.248 Profile for controlling Access and Residential Gateways". [i.3] ITU-T Recommendation H.248.1 (Version 3) Amendment 1: "Gateway control protocol". [i.4] Draft ITU-T Recommendation H.248.50: "Gateway control protocol: NAT Traversal Toolkit Packages". ETSI ETSI TS 183 002 V3.3.1 (2009-08) 11 |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 3 Definitions and abbreviations | |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 3.1 Definitions | For the purposes of the present document the terms and definitions given in ITU-T Recommendation H.248.1 [15] and the following apply: Access GateWay (AGW): Media GateWay (MGW) that interworks a significant number of analogue lines to a packet network and is located at the operator's premises NOTE: See also clause 3.1of ITU-T Recommendation H.248.1 [15]. IP Port: source and destination port numbers for UDP, SCTP and TCP traffic Media GateWay (MGW): refers both to Access Media GateWays (AMGs) and to Residential Media Gateways (RMGs) NOTE: See ITU-T Recommendation H.248.1 [15]. MG Port: single physical access interface at a Media GateWay. This is always a circuit oriented interface in the scope of this H.248 Profile NOTE: There are therefore three port types: analog port, ISDN Basic Rate Access port and Primary Rate Access Port. originating Media GateWay (MGW): Media GateWay (MGW) to which the calling party's physical termination is connected Residential GateWay (RGW): Media GateWay MGW) that interworks a small number of analogue lines NOTE: A Residential Media Gateway (RMG) typically contains one or two analogue lines and is located at the customer premises. See also clause 3.6 of ITU-T Recommendation H.248.1 [15]. terminating Media GateWay (MGW): Media GateWay (MGW) to which the called party's physical termination is connected |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ACO Address COmplete message AGCF Access Gateway Control Function AGW Access GateWay ALN Analog Line AMG Access Media Gateway A-MGF Access-MGF AN Access Network AOC Advice of Charge ARGW Access Residential media GateWay BA Basic Access BGF Border Gatweay Function CDR Call Detail Record CN Comfort Noise CRC Cyclic Redundancy Check DLCI Data Link Connection endpoint Identifier DNS Domain Name System DTMF Dual Tone Multi Frequency ECD Echo Control Device FEC Forward Error Correction FECD Full ECD FH Frame Handler ETSI ETSI TS 183 002 V3.3.1 (2009-08) 12 GRE Generic Routing Encapsulation HECD Half-way ECD IECD Incoming ECD IID IUA Interface Identifier IP Internet Protocol IPsec IP security ISDN Integrated Services Digital Network ISUP ISDN User Part IUA ISDN Q.921-User Adaptation LD Local Descriptor MGC Media Gateway Controller MGF Media Gateway Function MGW Media GateWay MID Message Identifier MRFP Media Resource Function Processor NAT Network Address Translation NMDS Narrowband Multi-service Delivery System NT1 Network Termination (type 1) NTN Network Terminating Node NTP Network Termination Point OAM Operation, Administration and Maintenance OECD Outgoing ECD PBX Private Branch eXchange PES PSTN/ISDN Emulation Subsystem PH Packet Handler PLC Packet Loss Concealment PLP Packet Layer Procedures PRA Primary Rate Access PT Payload Type QoS Quality of Service RD Remote Descriptor RFC Request For Comments (IETF) RGW Residential GateWay RMG Residential Media Gateway RMGC Resdiential Media Gateway Controller R-MGF Residential-MGF RTP Real-time Transport Protocol SAPI Service Access Point Identifier SCTP Stream Control Transmission Protocol SDP Session Description Protocol SPNE Signal Processing Network Equipment SRV SeRVer SSRC Synchronization SouRCe TAS Terminal Alerting Signal TCP Transmission Control Protocol TDW Time Division Multiplexing TE Terminal Equipment TEI TE Identifier TLS Transport Layer Security TMGW Trunking Media GateWay TTL Time To Live UDP User Datagram Protocol V5UA V5.2 - User Adaptation Layer VBD VoiceBand Data VoIP Voice over IP ETSI ETSI TS 183 002 V3.3.1 (2009-08) 13 |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 4 Applicability | |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 4.1 Architecture | Figure 1 illustrates the architecture assumed in the present document. The Media Gateway Controller (MGC) resides in a control subsystem and may be implemented as a stand-alone piece of equipment or as a component of a call server. Access to the IP network is provided to analog terminals, ISDN terminals, analog and ISDN Private Branch Exchanges (PBX), V5.1 and V5.2 Access Networks (AN) through Residential GateWays (RGWs) or Access GateWays (AGWs), which support one or more of the following reference points: • The Z reference point for analogue terminations. • The T reference point for Primary Rate Access. • The S/T reference point for Basic Rate Access. • The T* reference point for NMDS Access, as defined in EN 301 141-1 [7]. • The V5.1 reference point for V5.1 Access, as defined in EN 300 324-1 [54]. • The V5.2 reference point for V5.2 Access, as defined in EN 300 347-1 [55]. AGW IP Transport (Access and Core Network) Legacy User Equipment (terminals, PBXs) RGW Customer’s Premises Operator’s Premises Control Subsystem Scope of this specification NOTE: V5 interfaces are supported by this profile, but not indicated in this drawing. The V5 access networks would be located in the operator's premises, in front of the AGW. Figure 1: Reference architecture The present document does not make any assumption on the structure of the control subsystem hosting the MGC functionality. In the context of the TISPAN NGN Architecture (see ES 282 001 [1]), the control subsystem is the PSTN/ISDN Emulation Subsystem (PES) (see ES 282 002 [2]). Within this subsystem, the AGCF plays the MGC role. The RGW and the AGW implement the R-MGF and A-MGF functional entities (respectively). The area shown within the dashed lines, including part of the equipment placed on customer premises as a RGW, is considered to be under the control of a single operator. The use of IPSec (see RFC 4301 [36] or other security measures to create such a control area is outside the scope of the present document. ETSI ETSI TS 183 002 V3.3.1 (2009-08) 14 |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 4.2 Functional requirements | Support of the packages identified in the profile definition implies support of the underlying functionalities. This clause identifies additional functional requirements that Media GateWays (MGWs) conforming to the present document shall comply with: • Media GateWays (MGWs) shall support IPv4 and may support IPv6. • Media GateWays (MGWs) shall support for ITU-T Recommendation G.711 [27] A-law voice codec and may support other codecs. NOTE: Other mandatory codecs may also be required depending on the architecture in which Media GateWays (MGWs) are used. • Media GateWays (MGWs) shall support autonomous transition from Audio Mode to ITU-T Recommendation G.711 [27]-based VBD Mode (according to ITU-T Recommendation V.152 [32]) upon detection of fax modem, text modem or data modem traffic. • Media GateWays (MGWs) supporting other codecs than ITU-T Recommendation G.711 [27] shall also support the procedures defined in RFC 4733 [37] to generate, detect and forward DTMF digits. DTMF shall be identified by name (see mode "Named Telephone Events" in clause 3/RFC 4733 [37]), as opposed to their waveform properties. • All properties of tones requested by the MGC shall be provisioned in the Media GateWay (MG). The MGC is not required to send the physical characteristics of tones to Media GateWays (MGWs). • Where a RGW also provides customer access via a Network Address Translation (NAT) device, the design of the NAT function shall be such that it does not interfere with, and explicitly takes account of, the operation of the H.248 gateway function in the RGW. |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 5 Profile description | |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 5.1 Profile identification | Table 1 provides the name and version of the profile that is sent in the service change command. Table 1 Profile name: ETSI_ARGW Version: 3 |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 5.2 Summary | The profile defined in the present document enables the control of residential and access media gateways connecting analog and ISDN lines to an IP transport domain, in order to emulate PSTN/ISDN services. |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 5.3 Gateway control protocol version | Version 2 shall be the minimum version supported. Support of this version implies conformance to ITU-T Recommendation H.248.1 Version 2 and Corrigendum 1 [15] to this Recommendation, and implementation of the corrections available in the latest version of the H.248 Implementors' Guide. Version 3 may be required if automatic metering requires iteration notification and/or if the "one way external" topology configuration is supported. Support of this version implies conformance to ITU-T Recommendation H.248.1 Version 3 [i.3]. However, only "onIteration" in the NotifyComplete flag, "oneWayExternal" in the Topology Descriptor and "neverNotify" of the NotifyBehaviour parameter are required from this Recommendation. ETSI ETSI TS 183 002 V3.3.1 (2009-08) 15 |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 5.4 Connection model | Media GateWays (MGWs) shall support ephemeral terminations that sink and source RTP traffic. This type of H.248 termination is denoted RTP in the following clauses. Media GateWays (MGWs) shall also support at least one of the following types of physical terminations: • ANALOG: H.248 terminations representing analogue lines where the Network Termination Point (NTP) at the customer premises conform to ES 201 970 [3]. • ISDN: H.248 terminations representing ISDN B-Channels of ISDN Primary and Basic Access (BA) that conform to TBR 003 [13] and TBR 004 [14]. • V5: Support of V5.1 and V5.2 is according to EN 300 324-1 [54] and EN 300 347-1 [55]. Support of NMDS is achieved using ISDN terminations, according to EN 301 141-1 [7]. Table 2 Maximum number of contexts: Provisioned (see note 1) Maximum number of terminations per context: 2 (see note 2), 3 (see note 3), (see note 4), more than 3 (see note 4) (see note 5) Allowed terminations type combinations in a context: Media GateWays (MGWs) shall provide support for creating contexts containing two terminations of the same or different types, i.e. Context[a](ANALOG, ANALOG), Context[b](ANALOG, ISDN), Context[c](ISDN, ISDN), Context[d](ANALOG, RTP), Context[e](ISDN, RTP), Context[f](RTP, RTP). (See note 6) Support for more than two terminations of the same or different types may also be provided for 3-party calls, lawful intercept or both. NOTE 1: The actual number of supported contexts can be audited by the MGC using the MaxNrOfContexts property defined in the Base Root Package. NOTE 2: Support of 2 terminations in a context is the basic requirement in the MG. There are two levels of compliance to this basic requirement: a "basic support" and an "advanced support" of the connection model. Basic Support: This combination only allows Context [d] and Context [e]. It should be noted that in this case an ephemeral termination is never added to a context without the presence of a physical termination within this context. Advanced Support: Any combination of two termination types in contexts is allowed. There is no restriction as to whether an ephemeral termination can be added to a context other than NULL prior a physical termination also being present in this context. The distinction between basic and advanced support is configurable in the MGC on a per MG basis. NOTE 3: Support of 3 terminations in a context is required if the MG supports 3-party conference calls. The combination of terminations types may differ for a basic or advanced support of the connection model. Basic Support: This level of support allows for one physical termination of type ANALOG or ISDN and two ephemeral terminations. Advanced Support: Any combination of terminations is allowed of type ANALOG, ISDN and RTP. NOTE 4: Support of more than 2 terminations in a context is required if the MG supports lawful intercept. NOTE 5: The actual number of supported terminations can be audited by the MGC using the maxTerminationsPerContext property defined in the Base Root Package. NOTE 6: Certain actions performed by the MGC may result in a context having one or more ephemeral terminations without any associated physical termination. This occurs for example while an ISDN subscriber has two active calls, each of which associated with two different contexts in the media gateway. Based on a subscriber's decision, the MGC may subtract the physical terminations from their respective contexts and reconnect the ephemeral terminations into a single context, thereby creating a context with two ephemeral terminations (RTP-to-RTP interworking). There are several services that can invoke a similar procedure, one of which is the Explicit Call Transfer service (see EN 300 367 [9]). ETSI ETSI TS 183 002 V3.3.1 (2009-08) 16 |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 5.5 Context attributes | Table 3 Context attribute Supported Values supported Topology Yes See clause 5.7.8 Priority Indicator Yes 1 to 15 Emergency Indicator Yes Not Applicable |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 5.6 Terminations | |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 5.6.1 Termination names | The termination ID structure is provisioned in the MGC and MG and is known by the MG and the MGC at or before start up. A hierarchical naming structure is recommended for physical and ephemeral terminations. |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 5.6.1.1 Physical terminations | For example, the naming convention for physical terminations representing analog lines could be defined as follows: al/<subrack>/<card>/<port> Where, "al/" is a fixed prefix, <subrack>, <card> and <port> are non-zero integer values. According to this naming scheme, an analog line connected on port 2 of card 1 in subrack 22 would be referred to as al/22/1/2. A similar structure may also be used for ISDN Basic Access (BA)and Primary Rate Access (PRA), using different prefixes: "ba/" for Basic Access and "pra/" for Primary Rate Access. In such cases, the naming structure shall end with a component identifying a B channel. For example the naming convention for physical terminations representing ISDN Basic Accesses may be defined as follows: ba/<subrack>/<card>/<port>/<channel> Where, "ba/" is a fixed prefix, <subrack>, <card> and <port> are non-zero integer values and <channel> shall uniquely identify each of the 2 B channels. According to this naming scheme, an ISDN Basic Access B channel number 1 connected on port 7 of card 3 in subrack 15 would be referred to as ba/15/3/7/1. Similarly the naming convention for physical terminations representing ISDN Primary Rate Accesses and V5 access may be defined as follows: pra/<subrack>/<card>/<port>/<channel> Where, "pra/" is a fixed prefix, <subrack>, <card> and <port> are non-zero integer values and <channel> shall uniquely identify each of the ISDN-PRA B channels. The channel number shall be in the range 1 to 15 or 17 to 31 which identifies the time slot on the E1 used for transporting the "B" channel. According to this naming scheme, an ISDN Primary Rate Access B channel carried in Time Slot 20 connected on port 3 of card 9 in subrack 5 would be referred to as pra/5/9/3/20. |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 5.6.1.2 Ephemeral terminations | For example the naming convention for ephemeral terminations may be defined as follows: ephemeral/<string of alphanumeric characters or "/"> e.g. Ephemeral/1/0/40000. ETSI ETSI TS 183 002 V3.3.1 (2009-08) 17 |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 5.6.2 Multiplexed terminations | Table 4 Multiplex terminations supported? NO NOTE: The MG is not required to support bonding of multiple ISDN B-channels, e.g. for support of ISDN multimedia conferencing. If there are such applications and ISDN teleservices, the MG will handle each B-channel individually. Therefore, this profile is not required to support the multiplex descriptor. |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 5.7 Descriptors | |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 5.7.1 Stream descriptor | Table 5 Maximum number of streams per termination type RTP, ANALOG, ISDN 1 |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 5.7.1.1 LocalControl Descriptor | The following tables specify the level of support required with regard to the properties in the local control descriptor. Table 6 Termination type Stream type Reserve group used: Yes RTP Not Applicable Reserve value used: Yes RTP Not Applicable ReserveGroup: The MGC shall set the "ReserveGroup" property to "true" in the case multiple session descriptor blocks are used for specifying multiple "m=" lines and resources are required to be reserved in the MG for the multiple session descriptor blocks. This situation can occur for example where the first session block descriptor contains a "m=" line indicating audio, while the second session descriptor contains a "m=" line indicating T.38 (fax/modem relay). Alternatively, if the MGC when it specifies multiple session descriptor blocks requires the MG to select one of the session descriptor blocks, then it shall set the "ReserveGroup" property to "false". Another example of where multiple "m=" lines may be specified is where different packetization periods are required for the different audio codecs. In the situation where the MGC specifies a single session descriptor block, then the "ReserveGroup" property may be omitted or set to "false". ReserveValue: The MGC shall set the "ReserveValue" property to "true" when multiple codecs are specified within a single "m=" line of a session descriptor block and resources are required to be reserved in the MG for the multiple codecs. This situation occurs for example for audio calls where a low bit rate codec is specified for transporting voice and a G.711 codec (see ITU-T Recommendation G.711 [27]) is used for fallback (see ITU-T Recommendation V.152 [32]) in case a fax/modem is detected. Alternatively, if the MGC when it specifies multiple codecs requires the MG to select one of the codecs, then it shall set the "ReserveValue" property to "false". In the situation where the MGC species a single codec within a "m line", then the ReserveValue property shall be omitted or set to "false". ETSI ETSI TS 183 002 V3.3.1 (2009-08) 18 StreamMode: Table 7 Termination type Stream type Allowed StreamMode values ALL except ROOT Not Applicable Send, Receive, Send and Receive, Loopback, Inactive Table 8 Properties associated with Local Control Descriptor supported: Yes If yes Property IDs reported Termination type Stream type nt/jit RTP Not Applicable tdmc/ec tdmc/gain ANALOG, ISDN ANALOG Not Applicable mgcinfo/db ALL Not Applicable dscp/* RTP Not Applicable |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.