hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
9c251a86380319ca5f337310fb41e781 | 183 017 | 3 Definitions and abbreviations | |
9c251a86380319ca5f337310fb41e781 | 183 017 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: Application Function (AF): element offering applications that require the control of IP bearer resources NOTE: The AF is capable of communicating with the SPDF to transfer dynamic QoS-related application information. One example of an ... |
9c251a86380319ca5f337310fb41e781 | 183 017 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: AAA AA-Answer AAR AA-Request AF Application Function A-RACF Access-RACF ASA Abort-Session-Answer ASR Abort-Session-Request AVP Attribute-Value Pair BGF Border Gateway Function CEA Capabilities-Exchange-Answer CER Capabilities-Exchange-Request ... |
9c251a86380319ca5f337310fb41e781 | 183 017 | 4 Gq' interface | |
9c251a86380319ca5f337310fb41e781 | 183 017 | 4.1 Overview | The Gq' interface is used for the service-based policy set-up information exchange between the SPDF and the AF, e.g. the P-CSCF. As defined in the stage 2 specification (ES 282 003 [2]), this information is used by the SPDF for the Service Based Policy decisions. The Gq' interface may be an intra- or inter-domain inter... |
9c251a86380319ca5f337310fb41e781 | 183 017 | 4.2 Gq' reference model | The Gq' interface is defined between the AF and the SPDF. Within the present release, the Gq' interface is used for requesting transport plane resources and admission control for fixed broadband access networks (e.g. xDSL). NOTE: When supporting a GPRS IP-CAN, the AF will apply the procedures specified in TS 129 209 [4... |
9c251a86380319ca5f337310fb41e781 | 183 017 | 4.3 Functional elements and capabilities | |
9c251a86380319ca5f337310fb41e781 | 183 017 | 4.3.1 Service-based Policy Decision Function (SPDF) | The SPDF is a functional element that coordinates the resource reservation requests received from the AF. The SPDF makes policy decisions using policy rules and forwards the session and media related information obtained from the AF to the A-RACF for admission control purposes. Additionally, based on information receiv... |
9c251a86380319ca5f337310fb41e781 | 183 017 | 4.3.2 Application Function (AF) | The AF is a functional element offering applications that request and use IP bearer resources. The AF shall use the Gq' interface to exchange session and media related information with the SPDF. One example of an application function is the P-CSCF of the IMS. |
9c251a86380319ca5f337310fb41e781 | 183 017 | 5 Procedures descriptions | |
9c251a86380319ca5f337310fb41e781 | 183 017 | 5.1 Procedures at the AF | |
9c251a86380319ca5f337310fb41e781 | 183 017 | 5.1.1 Initial reservation for a session | Upon receipt of an AF session signalling message initiating a new AF session, the AF shall request an authorization for the session from the SPDF by sending the AA-Request message. This AA-Request message shall contain a new Session-Id. NOTE: As specified in RFC 3588 [3], the Session-Id is globally unique and is meant ... |
9c251a86380319ca5f337310fb41e781 | 183 017 | 5.1.2 Session modification | During the AF session modification, the AF shall send an update for the session description information to the SPDF based on the new SDI exchanged within the AF session signalling. The AF does this by sending the AA-Request message with an existing Session-Id and Media-Component-Description AVP(s) containing the update... |
9c251a86380319ca5f337310fb41e781 | 183 017 | 5.1.3 Session termination | When the AF session is terminated, the AF shall terminate the Diameter session by sending a Session-Termination-Request message to the SPDF. |
9c251a86380319ca5f337310fb41e781 | 183 017 | 5.2 Procedures at the SPDF | |
9c251a86380319ca5f337310fb41e781 | 183 017 | 5.2.1 Initial reservation for a session | Upon receipt of an initial AA-Request, the SPDF determines based on local policy whether a BGF and/or an A-RACF need to be involved in the AF session. If this is the case, the SPDF determines the address of the BGF and A-RACF using local policy. If the AA-Request contains the Media-Component-Description AVP(s), the SPD... |
9c251a86380319ca5f337310fb41e781 | 183 017 | 5.2.2 Session modification | The SPDF may receive the AA-Request message from the AF with modified service information. Based on the contents of the AA-Request, the SPDF shall coordinate any required modifications to existing resource reservation over the Rq interface and/or to existing BGF settings instantiated via the Ia interface. As described ... |
9c251a86380319ca5f337310fb41e781 | 183 017 | 5.2.3 Session termination | Upon receipt of a Session-Termination-Request message from the AF, the SPDF shall trigger the session termination procedure over the Rq interface and revoke any transport plane functions enforced over the Ia interface as a result of this session. |
9c251a86380319ca5f337310fb41e781 | 183 017 | 5.2.4 SPDF notifications | The Gq' interface supports facilities for indicating, on request basis, relevant events like revocation of established resource reservations. The SPDF shall send unsolicited RA-Request messages to the AF. Such messages are implicitly requested through policies established in the AF via the Specific-Action AVP (see clau... |
9c251a86380319ca5f337310fb41e781 | 183 017 | 5.3 IMS related P-CSCF procedures | |
9c251a86380319ca5f337310fb41e781 | 183 017 | 5.3.1 Provisioning of service information at the P-CSCF | The P-CSCF shall send service information to the SPDF upon every SIP message that includes an SDP answer payload. NOTE: The present clause assumes that the SDP payload is not encrypted when received in a SIP message. The service information shall be derived both from the SDP offer and the SDP answer. This ensures that ... |
9c251a86380319ca5f337310fb41e781 | 183 017 | 5.3.2 Enabling IP flows at the P-CSCF | Prior to the completion of the SIP session set-up, i.e. until the 200 OK(INVITE) is received, the P-CSCF may enable or disable media IP flows depending on operator policy, thus allowing or forbidding early media in forward and/or backward directions. If early media is to be disabled, the P-CSCF may modify the values of... |
9c251a86380319ca5f337310fb41e781 | 183 017 | 6 Use of the Diameter base protocol | With the clarifications listed in the following clauses the Diameter Base Protocol defined by RFC 3588 [3] shall apply. |
9c251a86380319ca5f337310fb41e781 | 183 017 | 6.1 Securing Diameter messages | For secure transport of Diameter messages, see TS 133 210 [6]. |
9c251a86380319ca5f337310fb41e781 | 183 017 | 6.2 Accounting functionality | Accounting functionality (Accounting Session State Machine, related command codes and AVPs) is not used on the Gq' interface. |
9c251a86380319ca5f337310fb41e781 | 183 017 | 6.3 Use of sessions | The Session-Termination-Request (STR) and Session-Termination-Answer (STA) commands defined in RFC 3588 [3] shall be used in order to terminate the sessions which are established via the AAR and AAA commands. If an RAR command is specifically corresponding to an established Gq' session, the RAR shall contain the sessio... |
9c251a86380319ca5f337310fb41e781 | 183 017 | 6.4 Transport protocol | Diameter messages over the Gq' interface shall make use of SCTP RFC 2960 [10] and shall utilize the new SCTP checksum method specified in RFC 3309 [11]. |
9c251a86380319ca5f337310fb41e781 | 183 017 | 6.5 Routing considerations | This clause specifies the use of the Diameter routing AVPs Destination-Realm and Destination-Host. The AF obtains the contact address of the SPDF for a given user via the e2 interface (ES 283 035 [13]). Both the Destination-Realm and Destination-Host AVPs shall be present in the request. |
9c251a86380319ca5f337310fb41e781 | 183 017 | 6.6 Advertising application support | The Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands are specified in the Diameter Base Protocol (RFC 3588 [3]). The AF and the SPDF shall advertise the support of the Gq specific Application by including the value 16777222 of the application identifier in the Auth-Application-Id AVP within the V... |
9c251a86380319ca5f337310fb41e781 | 183 017 | 7 DIAMETER application | The Diameter Base Protocol as specified in RFC 3588 [3] is used to support information transfer on the Gq' interface. RFC 3588 [3] shall apply except as modified by the additional support of the methods and the additional support of the commands and Attribute-Value-Pairs (AVPs), and result and event codes specified in ... |
9c251a86380319ca5f337310fb41e781 | 183 017 | 7.1 Commands | Existing Diameter command codes from the Diameter base protocol RFC 3588 [3] and the NASREQ Diameter application (RFC 4005 [5]), are used. The Gq specific Auth-Application id is used together with the command code within those messages. NOTE: The notion of NAS (Network Access Server) is not used here, NASREQ is just us... |
9c251a86380319ca5f337310fb41e781 | 183 017 | 7.1.1 AA-Request (AAR) command | The AAR command, indicated by the Command-Code field set to 265 and the "R" bit set in the Command Flags field, is sent by an AF to the SPDF in order to request the authorization for the bearer usage for the AF session. Message Format: <AA-Request> ::= < Diameter Header: 265, REQ, PXY > < Session-Id > { Auth-Applicatio... |
9c251a86380319ca5f337310fb41e781 | 183 017 | 7.1.2 AA-Answer (AAA) command | The AAA command, indicated by the Command-Code field set to 265 and the "R" bit cleared in the Command Flags field, is sent by the SPDF to the AF in response to the AAR command. Message Format: <AA-Answer> ::= < Diameter Header: 265, PXY > < Session-Id > { Auth-Application-Id } { Origin-Host } { Origin-Realm } [ Result... |
9c251a86380319ca5f337310fb41e781 | 183 017 | 7.1.3 Re-Auth-Request (RAR) command | The RAR command, indicated by the Command-Code field set to 258 and the 'R' bit set in the Command Flags field, is sent by the SPDF to the AF in order to indicate a specific action. However, application-specific authentication and/or authorization messages are not mandated for the Gq application in response to an RAR c... |
9c251a86380319ca5f337310fb41e781 | 183 017 | 7.1.4 Re-Auth-Answer (RAA) command | The RAA command, indicated by the Command-Code field set to 258 and the 'R' bit cleared in the Command Flags field, is sent by the AF to the SPDF in response to the RAR command. Message Format: <RA-Answer> ::= < Diameter Header: 258, PXY > < Session-Id > { Origin-Host } { Origin-Realm } [ Result-Code ] [ Experimental-R... |
9c251a86380319ca5f337310fb41e781 | 183 017 | 7.1.5 Session-Termination-Request (STR) command | The STR command, indicated by the Command-Code field set to 275 and the 'R' bit set in the Command Flags field, is sent by the AF to inform the SPDF that an authorized session shall be terminated. Message Format: <ST-Request> ::= < Diameter Header: 275, REQ, PXY > < Session-Id > { Origin-Host } { Origin-Realm } { Desti... |
9c251a86380319ca5f337310fb41e781 | 183 017 | 7.1.6 Session-Termination-Answer (STA) command | The STA command, indicated by the Command-Code field set to 275 and the 'R' bit cleared in the Command Flags field, is sent by the SPDF to the AF in response to the STR command. Message Format: <ST-Answer> ::= < Diameter Header: 275, PXY > < Session-Id > { Origin-Host } { Origin-Realm } [ Result-Code ] [ Experimental-R... |
9c251a86380319ca5f337310fb41e781 | 183 017 | 7.1.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 SPDF to inform the AF that all bearer resources for the authorized session have become unavailable. Message Format: <AS-Request> ::= < Diameter Header: 274, REQ, PXY > < Session-Id > { Origin-H... |
9c251a86380319ca5f337310fb41e781 | 183 017 | 7.1.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 AF to the SPDF in response to the ASR command. Message Format: <AS-Answer> ::= < Diameter Header: 274, PXY > < Session-Id > { Origin-Host } { Origin-Realm } [ Result-Code ] [ Experimental-R... |
9c251a86380319ca5f337310fb41e781 | 183 017 | 7.2 Experimental-Result-Code AVP values | |
9c251a86380319ca5f337310fb41e781 | 183 017 | 7.2.1 Experimental-Result-Code AVP values imported from TS 129 209 | This clause list the specific values of the Experimental-Result-Code AVP imported from [4] (vendor-id is 3GPP): • INVALID_SERVICE_INFORMATION (5061): - The service information provided by the AF is invalid or insufficient for the server to perform the requested action. • FILTER_RESTRICTIONS (5062): - The Flow_Descripti... |
9c251a86380319ca5f337310fb41e781 | 183 017 | 7.2.2 Experimental-Result-Code AVP values imported from ES 283 026 | This clause defines the specific values of the Experimental-Result-Code AVP imported from [14] (vendor-id is ETSI): • INSUFFICIENT_RESOURCES (4041): - The A-RACF or BGF indicates insufficient resources to perform the requested action. • COMMIT_FAILURE (4043): - The A-RACF or BGF indicates that the resources reservation... |
9c251a86380319ca5f337310fb41e781 | 183 017 | 7.3 AVPs | The following tables summarize the AVPs used in the present document, beyond those defined in the Diameter Base Protocol RFC 3588 [3]. ETSI ETSI TS 183 017 V3.2.1 (2010-02) 21 Table 7.3.1 describes the Diameter AVPs defined in the present document, their AVP Code values, types, possible flag values and whether the AVP ... |
9c251a86380319ca5f337310fb41e781 | 183 017 | 7.3.1 Binding-information AVP | The Binding-Information AVP (AVP code 450) is of type Grouped and is sent between the AF and the SPDF in order to convey binding information required for NA(P)T, hosted NA(P)T and NA(P)T-PT control. AVP format: Binding-information ::= < AVP Header: 450 13019> { Binding-Input-List } ; [ Binding-Output-List ] ; |
9c251a86380319ca5f337310fb41e781 | 183 017 | 7.3.2 Binding-Input-List AVP | The Binding-Input-List AVP (AVP code 451) is of type Grouped and contains a list transport addresses for which a binding is requested. The AF constructs the Binding-Input-List using SDI information. The Binding-Input-List AVP is populated with an even number of V4-Transport-Address AVP or V6-Transport- Address list ele... |
9c251a86380319ca5f337310fb41e781 | 183 017 | 7.3.3 Binding-Output-List AVP | The Binding-Output-List AVP (AVP code 452) is of type Grouped and contains a list of transport addresses which is the result of the binding operation performed by the transport plane functions. The rules for how to populate the Binding-Output-List AVP are the same rules as for how to populate the Binding- Input-list AV... |
9c251a86380319ca5f337310fb41e781 | 183 017 | 7.3.4 V6-Transport-address AVP | The V6-Transport-Address AVP (AVP code 453) is of type Grouped and contains a single IPv6 address and a single port number. AVP format: Transport-Address ::= < AVP Header: 453 13019> { Framed-IPv6-Prefix } ; { Port-Number } ; ETSI ETSI TS 183 017 V3.2.1 (2010-02) 24 |
9c251a86380319ca5f337310fb41e781 | 183 017 | 7.3.5 V4-Transport-address AVP | The V4-Transport-Address AVP (AVP code 454) is of type Grouped and contains a single IPv4 address and a single port number. AVP format: Transport-Address ::= < AVP Header: 454 13019> { Framed-IP-Address } ; { Port-Number } ; |
9c251a86380319ca5f337310fb41e781 | 183 017 | 7.3.6 Port-number AVP | The Port-Number AVP (AVP code 455) is of type Unsigned32 and contains the end point port number. |
9c251a86380319ca5f337310fb41e781 | 183 017 | 7.3.7 Reservation-Class AVP | The Reservation-class AVP (AVP code 456) is of type Unsigned32 and contains an integer used as an index pointing to the traffic characteristic of the flow (e.g. burstiness and packet size). |
9c251a86380319ca5f337310fb41e781 | 183 017 | 7.3.8 Latching-indication AVP | The Latching-Indication AVP (AVP code 457) is of type Enumerated. The following values are defined: • LATCH (0) • RELATCH (1) |
9c251a86380319ca5f337310fb41e781 | 183 017 | 7.3.9 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-... |
9c251a86380319ca5f337310fb41e781 | 183 017 | 7.3.10 Globally-unique-address AVP | The Globally-Unique-Address AVP (AVP code 300) is of type Grouped (see ES 283 034 [15]). AVP Format: Globally-Unique-Address ::= < AVP Header: 300 13019 > [Framed-IP-Address] [Framed-IPv6-Prefix] [Address-Realm] |
9c251a86380319ca5f337310fb41e781 | 183 017 | 7.3.11 Address-realm AVP | The Address-Realm AVP (AVP code 301) is of type Octet String (see ES 283 034 [15]). |
9c251a86380319ca5f337310fb41e781 | 183 017 | 7.3.12 Framed-IP-address AVP | The Framed-IP-Address AVP is defined in the NASREQ application (RFC 4005 [5]). |
9c251a86380319ca5f337310fb41e781 | 183 017 | 7.3.13 Framed-IPv6-prefix AVP | The Framed-IPv6-Prefix AVP is defined in the NASREQ application (RFC 4005 [5]). |
9c251a86380319ca5f337310fb41e781 | 183 017 | 7.3.14 Abort-cause AVP | The Session-Abort-Cause AVP (AVP code 500) is of type Enumerated, and determines the cause of a session abort request or of an RAR indicating a IP-CAN bearer release. The following values are defined: • BEARER_RELEASED (0) - This value is used when the bearer has been deactivated as a result from normal signalling hand... |
9c251a86380319ca5f337310fb41e781 | 183 017 | 7.3.15 AF-application-identifier AVP | The AF-Application-identifier AVP (AVP code 504) is of type Octet String, and it contains information that identifies the particular service that the AF service session belongs to. This information may be used to differentiate QoS for different application services. For example the AF-Application-Identifier may be used... |
9c251a86380319ca5f337310fb41e781 | 183 017 | 7.3.16 AF-charging-identifier AVP | The AF-Charging-Identifier AVP (AVP code 505) is of type Octet String, contains the AF Charging Identifier that is sent by the AF. This information may be used for charging correlation between AF and the RACS functional entities. |
9c251a86380319ca5f337310fb41e781 | 183 017 | 7.3.17 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... |
9c251a86380319ca5f337310fb41e781 | 183 017 | 7.3.18 Flow-grouping AVP | The Flow-Grouping AVP (AVP code 508) is of type Grouped, and it indicates that no other IP Flows shall be transported together with the listed IP Flows in the same IP-CAN bearer. If Flow-Grouping AVP(s) have been provided in earlier service information, but are not provided in subsequent service information, the old fl... |
9c251a86380319ca5f337310fb41e781 | 183 017 | 7.3.19 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 [12]. |
9c251a86380319ca5f337310fb41e781 | 183 017 | 7.3.20 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] |
9c251a86380319ca5f337310fb41e781 | 183 017 | 7.3.21 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 following values are defined: • ENABLED-UPLINK (0): - This value shall be used to enable associated uplink IP flow(s) and to disable associated downlink IP flow(s). If any downlink RTCP IP flow(s)... |
9c251a86380319ca5f337310fb41e781 | 183 017 | 7.3.22 Flow-usage AVP | The Flow-Usage AVP (AVP code 512) is of type Enumerated, and 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 017 V3.2.1 (2010-02) 28 • RTCP (1... |
9c251a86380319ca5f337310fb41e781 | 183 017 | 7.3.23 Specific-action AVP | The Specific-Action AVP (AVP code 513) is of type Enumerated. Within a SPDF initiated Re-Authorization Request, the Specific-Action AVP determines the type of the action. Within an initial AA-request the AF may use the Specific-Action AVP to request specific actions from the server at the bearer events and to limit the... |
9c251a86380319ca5f337310fb41e781 | 183 017 | 7.3.24 Max-requested-bandwidth-DL AVP | The Max-Requested-Bandwidth-DL AVP (AVP code 515) is of type Unsigned32, and it indicates the maximum requested bandwidth in bits per second for a downlink IP flow. The bandwidth contains all the overhead coming from the IP-layer and the layers above, e.g. IP, UDP, RTP and RTP payload. ETSI ETSI TS 183 017 V3.2.1 (2010... |
9c251a86380319ca5f337310fb41e781 | 183 017 | 7.3.25 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 contains all the overhead coming from the IP-layer and the layers above, e.g. IP, UDP, RTP and RTP payload. |
9c251a86380319ca5f337310fb41e781 | 183 017 | 7.3.26 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 an AF session. It may be based on the SDI exchanged between the AF and the AF client in the UE. The information may be used by the server to determine authorized QoS and IP flow... |
9c251a86380319ca5f337310fb41e781 | 183 017 | 7.3.27 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 [12]. ETSI ETSI TS 183 017 V3.2.1 (2010-02) 30 |
9c251a86380319ca5f337310fb41e781 | 183 017 | 7.3.28 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 [12]. Possible Bandwidth information and Flow-Status information provided within the Media-Sub-Com... |
9c251a86380319ca5f337310fb41e781 | 183 017 | 7.3.29 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 media types indicate the type of media in the same way as the SDP media types with the same names defined in [11]. The following values are defined: • AUDIO (0) • VIDEO (1) • DATA (2) • APPLICATION (3) ... |
9c251a86380319ca5f337310fb41e781 | 183 017 | 7.3.30 RR-bandwidth AVP | The RR-Bandwidth AVP (AVP code 521) is of type Unsigned32, and it indicates the maximum required bandwidth in bits per second for RTCP receiver reports within the session component, as specified in RFC 3556 [16]. The bandwidth contains all the overhead coming from the IP-layer and the layers above, i.e. IP, UDP and RTC... |
9c251a86380319ca5f337310fb41e781 | 183 017 | 7.3.31 RS-bandwidth AVP | The RS-Bandwidth AVP (AVP code 522) is of type Unsigned32, and it indicates the maximum required bandwidth in bits per second for RTCP sender reports within the session component, as specified in RFC 3556 [16]. The bandwidth contains all the overhead coming from the IP-layer and the layers above, i.e. IP, UDP and RTCP.... |
9c251a86380319ca5f337310fb41e781 | 183 017 | 7.3.32 SIP-forking-indication AVP | The SIP_Forking AVP (AVP code 523) is of type Enumerated, and describes if several SIP dialogues are related to one Diameter session: • SINGLE_DIALOGUE (0) - This value is used to indicate that the Diameter session relates to a single SIP dialogue. This is the default value applicable if the AVP is omitted. • SEVERAL_D... |
9c251a86380319ca5f337310fb41e781 | 183 017 | 7.3.33 Service-Class AVP | The Service-Class AVP (AVP code 459) is of type UTF8String, and it contains the service class requested by the AF. The service class is to be checked against local policies in the SPDF. |
9c251a86380319ca5f337310fb41e781 | 183 017 | 7.3.34 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). |
9c251a86380319ca5f337310fb41e781 | 183 017 | 7.3.35 Overbooking-indicator | The Overbooking-indicator AVP (AVP code 460) is of type Enumerated. Indicates that the SPDF should require processing the resource request in overbooking mode. The following values are specified The overbooking-indicator may be used when having a session initiation or when having a session modification. • Overbooking-i... |
9c251a86380319ca5f337310fb41e781 | 183 017 | 7.3.36 Codec-Data AVP | The Codec-Data AVP (AVP code 524) is of type OctetString. The Codec-Data AVP shall contain codec related information known at the AF. This information shall be encoded as described in clause 5.3.7 of [19]. |
9c251a86380319ca5f337310fb41e781 | 183 017 | 7.3.37 Authorization-Package-Id | 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. The SPDF forwards this information transparently over the Rq interface (ES 283 026 [14]). 7.3.38 Media-Authorization-Context-Id The Media-Authorization-Context-Id AVP (A... |
9c251a86380319ca5f337310fb41e781 | 183 017 | 7.3.39 Logical-Access-ID AVP | The Logical-Access-ID AVP (AVP code 302 13019) is of type OctetString. It is defined in [15]. ETSI ETSI TS 183 017 V3.2.1 (2010-02) 32 |
9c251a86380319ca5f337310fb41e781 | 183 017 | 7.4 Use of namespaces | This clause contains the namespaces that have either been created in the present document, or the values assigned to existing namespaces managed by IANA. |
9c251a86380319ca5f337310fb41e781 | 183 017 | 7.4.1 AVP codes | The present document assigns the AVP values from the AVP Code namespace managed by ETSI for its Diameter vendor-specific applications. See clause 7.3. |
9c251a86380319ca5f337310fb41e781 | 183 017 | 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 its Diameter vendor-specific applications. See clause 7.2. |
9c251a86380319ca5f337310fb41e781 | 183 017 | 7.4.3 Command code values | The present document does not assign command code values but uses existing command defined by 3GPP and IETF. |
9c251a86380319ca5f337310fb41e781 | 183 017 | 7.4.4 Application-ID value | The present document re-uses the value 16777222 allocated by IANA to the 3GPP Gq interface application. ETSI ETSI TS 183 017 V3.2.1 (2010-02) 33 Annex A (normative): Support for SIP forking A.1 Support for SIP forking The P-CSCF shall be able to handle forking. A.1.1 Authorization of resources for early media for forke... |
0393bb0911a658eac7d7ff03dc30599e | 182 023 | 1 Scope | The present document provides the possible scenarios for: • the interconnection of an Next Generation Corporate Network (NGCN) with a Next Generation Network (NGN); and • the support of NGCN capabilities within an NGN, either towards a User Equipment (UE) or to an NGCN. Unless otherwise specified by reference to other ... |
0393bb0911a658eac7d7ff03dc30599e | 182 023 | 2 References | |
0393bb0911a658eac7d7ff03dc30599e | 182 023 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
0393bb0911a658eac7d7ff03dc30599e | 182 023 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. NOTE: While any hyperlinks in... |
0393bb0911a658eac7d7ff03dc30599e | 182 023 | 3 Definitions and abbreviations | |
0393bb0911a658eac7d7ff03dc30599e | 182 023 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in ETSI TS 124 523 [8] apply. |
0393bb0911a658eac7d7ff03dc30599e | 182 023 | 3.2 Abbreviations | For the purposes of the present document, the terms and definitions given in ETSI TS 124 523 [8] apply. |
0393bb0911a658eac7d7ff03dc30599e | 182 023 | 4 Introduction | The provisions of the present document are contained in ETSI TS 124 523 [8]. |
0393bb0911a658eac7d7ff03dc30599e | 182 023 | 5 General requirements | The provisions of the present document are contained in ETSI TS 124 523 [8]. 6 Scenarios relating to a level of service of IP connectivity The provisions of the present document are contained in ETSI TS 124 523 [8]. 7 Scenarios relating to a level of service of session establishment and control of communication session... |
0393bb0911a658eac7d7ff03dc30599e | 182 023 | 9 Scenarios relating to roaming | The provisions of the present document are contained in ETSI TS 124 523 [8]. ETSI ETSI TS 182 023 V3.0.0 (2015-11) 7 Annex A (informative): Change history Date WG Doc. CR Rev CAT Title / Comment Current Version New Version 3/09/2015 NTECH(15) 12_004 001 D Alignment with 3GPP TS 24.523 2.1.1 3.0.0 ETSI ETSI TS 182 023 V... |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 1 Scope | The present document specifies the, stage three, Protocol Description of the Communications Diversion (CDIV) services, based on stage one and two of the ISDN Communication diversion supplementary services. Within the Next Generation Network (NGN) the stage 3 description is specified using the IP Multimedia Communicatio... |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • 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. • ... |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 3 Definitions and abbreviations | |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in TS 181 002 [1] and the following apply: escaped character: See RFC 3261 [6]. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.