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, 1677727... |
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-Real... |
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_RESTR... |
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 ... |
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 ... |
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... |
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... |
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 c... |
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... |
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... |
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 requireme... |
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 ... |
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... |
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 mechan... |
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-... |
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 Capabiliti... |
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... |
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... |
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-Spec... |
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, 1677... |
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> < Se... |
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_E... |
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 } { Orig... |
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 > { Au... |
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 ... |
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... |
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 e... |
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). • PRIORIT... |
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 ... |
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 th... |
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 follow... |
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 ca... |
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 diff... |
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 accept... |
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 con... |
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 Netw... |
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.1o... |
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 Bor... |
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 ISD... |
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. • Me... |
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 auto... |
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 l... |
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 subrac... |
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 sup... |
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 th... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.