hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 3 Definitions and abbreviations | |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: Attribute-Value Pair (AVP): corresponds to an Information Element in a Diameter message NOTE: See RFC 3588 [11]. hard-state reservation: type of reservation whereby the requested resources are reserved without time limit NOTE: Hard-sta... |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 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-Resource and Admission Control Function ASA Abort-Session-Answer ASP Application Service Provider ASR Abort-Session-Request ATM VC Asynchronous Transfer Mode Virtual Circuit AV... |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 4 Rq interface | |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 4.1 Overview | In the following clause, the Rq interface is described in detail concerning what type of information that needs to be transported between the SPDF and the A-RACF. The functional requirements and the stage 2 specifications of the Rq interface are contained in ES 282 001 [1] and ES 282 003 [2]. Due to the possible busine... |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 4.2 Rq reference model | The Rq interface is defined between the SPDF and the A-RACF. Rr x - RACF AF SPDF BGF RCEF NASS Re Ia Gq ’ Rd ’ , Ri ’ Rq e4 Transport Processing Functions RACS BTF Rf Rr x - RACF AF SPDF BGF RCEF NASS Re Ia Gq ’ Rd ’ , Ri ’ Rq e4 Transport Processing Functions RACS BTF Rf Figure 1: Rq interface architecture model |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 4.3 Functional elements and capabilities | |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 4.3.1 Service Policy Decision Function (SPDF) | The SPDF is a functional element that coordinates the resource reservations requests received from by 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 via the Rq reference point for admission control purposes. The functi... |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 4.3.2 Access-Resource Admission Control Function (A-RACF) | The A-RACF is a functional element performing resource reservation admission control and network policy assembly. The A-RACF receives resource reservation requests from the SPDF via the Rq reference point. The functionality of the SPDF is further detailed in ES 282 003 [2]. |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 5 Resource control procedures | The resource control procedures are defined in seven interaction procedures: 1) Reservation. 2) Commit. 3) Reservation and commit. 4) Refresh. 5) Modification. 6) Release. ETSI ETSI TS 183 026 V3.1.1 (2010-03) 10 7) Event notification. These interactions are described in the following clauses. During the interactions D... |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 5.1 Procedures at the SPDF | |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 5.1.1 Initial Reservation for a Session | The SPDF may request the A-RACF to allocate resources for a new session (i.e. make an initial reservation request). The SPDF issues such request by sending an AA-Request message to the A-RACF. This message contains one or more Media-Component-Description Attribute-Value-Pair(s) (AVP(s)). Each Media-Component-Descriptio... |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 5.1.2 Session Modification | The SPDF may modify an existing session by sending an AA-Request to the A-RACF with zero or more updated Media-Component-Description AVP(s) and/or Media-Sub-Component AVP(s). The Session-Id shall be an existing one and refer to the session that is to be modified. The Reservation-Priority may be specified as a main AVP ... |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 5.1.3 Session Termination | The SPDF may issue a Session-Termination-Request (STR) command to the A-RACF, in order to terminate the session. This command releases all the resources associated with the session identified by the provided Session-Id AVP. Table 3: Termination operations Message Type Flow-Status AVP at the level of: Meaning Media Sub-... |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 5.1.4 Event notification | Notifications for specific events may be implicitly requested through policies established in the A-RACF. The SPDF may further specify, in the Specific-Action AVP of an initial AA-Request command, the events of which it wants to be informed. The supported events are listed in clause 6.4. As an option, when the SPDF rec... |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 5.2 Procedures at the A-RACF | |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 5.2.1 Initial Reservation for a Session | An initial AA-Request contains one or more Media-Component-Description AVP(s) including one or more Media-Sub-Component AVP(s). For initial reservation requests in which the Session-Id is new the Media-Component-Number(s) and Flow-Number(s) are interpreted by the A-RACF as new ones. The Reservation-Priority AVP may be ... |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 5.2.2 Session Modification | An AA-Request issued to modify an existing session may contain zero or more Media-Component-Description AVP(s) including one or more Media-Sub-Component AVP(s). For modification requests in which the Session-Id is an existing one the Media-Component-Number(s) and Flow-Number(s) of existing reservations shall be existin... |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 5.2.3 Session Termination | If all IP flows within a SPDF session need to be terminated, the A-RACF shall inform the SPDF about this event by sending an Abort-Session-Request (ASR) message with the appropriate Abort-Cause AVP value. The A-RACF may include one or more Session-Bundle-Id AVPs in order to inform the SPDF of that several sessions iden... |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 5.2.4 Event Notification | If an event for which notification is requested occurs, the A-RACF shall send an unsolicited RAR message to the SPDF containing: • The value of the Specific-Action AVP, indicating the event that occurred. • Optionally, the appropriate Abort-Cause AVP value. |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 6 Rq protocol | The Rq protocol is based on Diameter (RFC 3588 [11]). |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 6.1 Protocol support | The Diameter Base Protocol as specified in RFC 3588 [11] used to support information transfer on the Rq interface. RFC 3588 [11] shall apply except as modified by the defined Rq application specific procedures, Attribute-Value-Pairs (AVPs) as well as Experimental-Result-Code AVP and Specific-Action AVP values defined i... |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 6.1.1 Advertising Application Support | The Capabilities-Exchange-Request (CER) and Capabilities-Exchange-Answer (CEA) commands are specified in the Diameter Base Protocol RFC 3588 [11]. Due to the definition of the commands used over the Rq reference point, the Vendor-Specific-Application-Id AVP cannot be used instead of the Auth-Application-Id AVP. Therefo... |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 6.1.2 Transport protocol | Diameter messages over the Rq reference point shall make use of SCTP RFC 2960 [9] and shall utilize the new SCTP checksum method specified in RFC 3309 [10]. ETSI ETSI TS 183 026 V3.1.1 (2010-03) 18 |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 6.1.3 Securing Rq messages | For secure transport of Diameter messages, see TS 133 210 [8]. 6.1.4 Use of sessions The Session-Termination-Request (STR) and Session-Termination-Answer (STA) commands defined in RFC 3588 [11] shall be used in order to terminate the sessions which are established via the AAR and AAA commands. If an RAR command is spec... |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 6.2 Rq messages | Existing Diameter command codes from the Diameter base protocol RFC 3588 [11] and the NASREQ Diameter application RFC 4005 [12] are used at the Rq interface. The Application-ID of 16777222 is used together with the command code to identify the Rq messages. New AVPs are represented in bold. |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 6.2.1 AA-Request (AAR) Command | The AA-Request command (AAR), indicated by the Command-Code field set to 265 and the "R" bit set in the Command Flags field, is sent by the SPDF to the A-RACF for reserve, commit, modify, release and refresh operations. Message Format: <AA-Request> ::= < Diameter Header: 265, REQ, PXY > < Session-Id > { Auth-Applicatio... |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 6.2.2 AA-Answer (AAA) Command | The AA-Answer command (AAA), indicated by the Command-Code field set to 265 and the "R" bit cleared in the Command Flags field, is sent by the RACF to the SDPF in response to the AAR command. The A-RACF may confirm the priority associated with the reservation by echoing the Reservation-Priority AVP (see clause 6.4.23).... |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 6.2.3 Re-Auth-Request (RAR) Command | The RAR command, indicated by the Command-Code field set to 258 and the "R" bit set in the Command Flags field, is sent by the A-RACF to the SPDF 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 Specif... |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 6.2.4 Re-Auth-Answer (RAA) Command | The RAA command, indicated by the Command-Code field set to 258 and the "R" bit cleared in the Command Flags field, is sent by the SPDF to the A-RACF in response to the RAR command. Message Format: <RA-Answer> ::= < Diameter Header: 258, PXY > < Session-Id > { Origin-Host } { Origin-Realm } [ Result-Code ] [ Experiment... |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 6.2.5 Session-Termination-Request (STR) Command | The STR command, indicated by the Command-Code field set to 275 and the "R" bit set in the Command Flags field, is sent by the SPDF to inform the A-RACF that an authorized session shall be terminated. Message Format: <ST-Request> ::= < Diameter Header: 275, REQ, PXY > < Session-Id > { Origin-Host } { Origin-Realm } { D... |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 6.2.6 Session-Termination-Answer (STA) Command | The STA command, indicated by the Command-Code field set to 275 and the "R" bit cleared in the Command Flags field, is sent by the A-RACF to the SPDF in response to the STR command. Message Format: <ST-Answer> ::= < Diameter Header: 275, PXY > < Session-Id > { Origin-Host } { Origin-Realm } [ Result-Code ] [ Experiment... |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 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 A-RACF to inform the SPDF that all resources for the authorized session have become unavailable. Message Format: <AS-Request> ::= < Diameter Header: 274, REQ, PXY > < Session-Id > { Origin-Host... |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 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 SPDF to the A-RACF in response to the ASR command. Message Format: <AS-Answer> ::= < Diameter Header: 274, PXY > < Session-Id > { Origin-Host } { Origin-Realm } [ Result-Code ] [ Experiment... |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 6.3 Experimental-Result-Code AVP values | |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 6.3.1 Experimental-Result-Code AVP values imported from TS 129 209 | The present document reuses existing Experimental-Result-Code AVP values defined in TS 129 209 [7]. This clause defines the specific values of the Experimental-Result-Code AVP: INVALID_SERVICE_INFORMATION (5061). The service information provided by the AF is invalid or insufficient for the server to perform the request... |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 6.4 AVPs | This clause summarizes the AVPs used in the present document, beyond those defined in the Diameter Base Protocol. |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 6.4.1 AVPs defined in the present document | Table 5 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 5: Diameter AVPs defined in the present document AVP Flag rul... |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 6.4.2 AVPs imported from TS 129 209 | The present document reuses existing AVP(s) used already at the Gq interface TS 129 209 [7]. Not all the AVPs defined in TS 129 209 [7] are reused (e.g. Access-Network-Charging-Identifier-Value AVP). Table 6 describes the Diameter AVPs defined for the Gq interface protocol [7] and used in the present document, their AV... |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 6.4.3 AVPs imported from TS 183 017 | Table 7 describes the Diameter AVPs defined for the Gq' interface protocol [5] and used in the present document, their AVP Code values, types, possible flag values and whether the AVP may be encrypted. Flags values are described in the context of the present document rather than in the context of the application where ... |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 6.4.4 AVPs imported from ES 283 034 | Table 8 describes the Diameter AVPs defined for the e4 interface protocol [4] and used in the present document, their AVP Code values, types, possible flag values and whether the AVP may be encrypted. Flags values are described in the context of the present document rather than in the context of the application where t... |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 6.4.5 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 [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. INSUFFICIEN... |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 6.4.6 AF-Application-Identifier AVP | The AF-Application-Identifier AVP (AVP code 504) is of type OctetString, 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 ... |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 6.4.7 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... |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 6.4.8 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... |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 6.4.9 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 [6]. |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 6.4.10 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] |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 6.4.11 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... |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 6.4.12 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 RTCP (1) This value is used to indicate that an IP fl... |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 6.4.13 Specific-Action AVP | The Specific-Action AVP (AVP code 513) is of type Enumerated. Within an initial AA-Request the SPDF may use the Specific-Action AVP to request from the A-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 requ... |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 6.4.14 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 contains all the overhead coming from the IP-layer and the layers above, e.g. IP, UDP, RTP and RTP payload. |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 6.4.15 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. |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 6.4.16 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 A-RACF to determine the QoS requirements. Within... |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 6.4.17 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 [6]. |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 6.4.18 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 [6]. The Media-Sub-Component AVP may contain the Flow-Status AVP, which indicates the particular r... |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 6.4.19 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). • CONTROL (4). • TEXT (5). • MESSAGE (6). • OTHER (0xFFFFFFFF). |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 6.4.20 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). |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 6.4.21 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] |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 6.4.22 Address-Realm AVP | The Address-Realm AVP (AVP code 301) is of type OctetString. ETSI ETSI TS 183 026 V3.1.1 (2010-03) 29 |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 6.4.23 Reservation-Priority AVP | The Reservation-Priority AVP (AVP code 458) is of type Enumerated. It may be specified in an AA-Request as a main AVP in order to associate a priority with a resource reservation or modification request. It may also be specified as part of a Media-Component AVP in order to associate a priority with resource reservation... |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 6.4.24 Session-Bundle-Id AVP | The Session-Bundle-Id (AVP code 400) is of type Unsigned32. It may be specified by the A-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 A-RACF only. It ... |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 6.4.25 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. |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 6.4.26 Service-Class AVP | The Service-Class AVP (AVP code 459) is of type UTF8String, and it contains the service class requested by the SPDF. ETSI ETSI TS 183 026 V3.1.1 (2010-03) 30 |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 6.4.27 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). |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 6.4.28 Overbooking-indicator AVP | 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: • NO-OVERBOOKING (0) Means that no overbooking mode is required • OVERBOOKING (1) Means that overbooking is mode required If... |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 6.4.29 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. This information is used by the A-RACF to derive the policy to be passed to an RCEF through the Re reference point for the session. |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 6.4.30 Media-Authorization-Context-Id AVP | The Media-Authorization-Context-Id AVP (AVP code 462) is of type UTF8String, and it identifies the authorization context requested by the AF for a media component. This information is used by the A-RACF to derive the policy to be passed to an RCEF through the Re reference point for a media component. |
f8b36fc7978d66b44111bf90dcc70b85 | 183 026 | 6.4.31 Logical-Access-ID AVP | The Logical-Access-ID AVP (AVP code 302 13019) is of type OctetString. It is defined in [4]. ETSI ETSI TS 183 026 V3.1.1 (2010-03) 31 Annex A (informative): Resource reservation flow states maintained by A-RACF Table A.1: Flow state transitions State Event Action Next State Idle Received Reservation Request Verify avai... |
b1a4bc91ff14c2bdb7cb623bac770c3d | 183 047 | 1 Scope | The present document specifies the stage three Protocol Description of the Advice Of Charge (AOC) service, based on stage 1 and 2 of the ISDN Supplementary Service Advice Of Charge for all calls (permanent mode). |
b1a4bc91ff14c2bdb7cb623bac770c3d | 183 047 | 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... |
b1a4bc91ff14c2bdb7cb623bac770c3d | 183 047 | 2.1 Normative references | The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] Void. [2] Void. [3] Void. [4] Void. [5] Void. [6] ETS... |
b1a4bc91ff14c2bdb7cb623bac770c3d | 183 047 | 2.2 Informative references | The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. Not applicable. ETSI ETSI TS 183 047 V2.2.0 (2008-06) ... |
b1a4bc91ff14c2bdb7cb623bac770c3d | 183 047 | 3 Definitions and abbreviations | |
b1a4bc91ff14c2bdb7cb623bac770c3d | 183 047 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in TS 124 447 [6] apply. |
b1a4bc91ff14c2bdb7cb623bac770c3d | 183 047 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in TS 124 447 [6] apply. |
b1a4bc91ff14c2bdb7cb623bac770c3d | 183 047 | 4 Advice Of Charge (AOC) | The provisions of the present document are contained in TS 124 447 [6]. ETSI ETSI TS 183 047 V2.2.0 (2008-06) 7 Annex A (informative): Signalling flows Information is contained in TS 124 447 [6]. ETSI ETSI TS 183 047 V2.2.0 (2008-06) 8 Annex B (informative): Example of Filter Criteria Information is contained in TS 124... |
17b379e81f85e568520fb8cfe225fead | 183 045 | 1 Scope | The present document provides the ETSI TISPAN endorsement of, OMA-TS-PoC_ControlPlane-V1 [1], OMA-TS-PoC_UserPlane-V1 [2], and OMA-TS-PoC_XDM-V1 [3] in line with the requirements of TISPAN NGN. The present document is applicable to Application Servers (ASs) and User Equipment (UE) providing Direct Communication functio... |
17b379e81f85e568520fb8cfe225fead | 183 045 | 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. • ... |
17b379e81f85e568520fb8cfe225fead | 183 045 | 3 Definitions, and abbreviations | |
17b379e81f85e568520fb8cfe225fead | 183 045 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in TR 180 000 [5] and the following apply: direct communication client: entity performing the PoC Client functions that resides on the User Equipment in the originating or terminating network that supports the Direct Communication service direct ... |
17b379e81f85e568520fb8cfe225fead | 183 045 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ASs Application Servers DC Direct Communication IMS IP Multimedia Subsystem MMD Multi Media Domain NGN Next Generation Networks OMA Open Mobile Alliance PoC Push to Talk over Cellular SIP Session Invitation Protocol TISPAN Telecommunications a... |
db623e88d161eafea110eb1f3898467d | 183 023 | 1 Scope | The present document defines a protocol used for manipulating data related to PSTN/ISDN Simulation services. The protocol is based on the eXtensible Markup Language (XML) Configuration Access Protocol (XCAP). |
db623e88d161eafea110eb1f3898467d | 183 023 | 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... |
db623e88d161eafea110eb1f3898467d | 183 023 | 2.1 Normative references | The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] Void. [2] Void. [3] Void. [4] Void. [5] Void. [6] Voi... |
db623e88d161eafea110eb1f3898467d | 183 023 | 2.2 Informative references | The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. Not applicable. |
db623e88d161eafea110eb1f3898467d | 183 023 | 3 Definitions and abbreviations | |
db623e88d161eafea110eb1f3898467d | 183 023 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in TS 124 423 [13] apply. |
db623e88d161eafea110eb1f3898467d | 183 023 | 3.2 Abbreviations | For the purposes of the present document, the terms and definitions given in TS 124 423 [13] apply. 4 Architecture for manipulating NGN PSTN/ISDN simulation services settings The provisions of the present document are contained in TS 124 423 [13]. 5 The eXtensible Markup Language (XML) Configuration Access Protocol (XC... |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 1 Scope | The present document defines call control protocols and procedures for use in the IMS-based PSTN/ISDN Emulation subsystem based on the Media Gateway Control Protocol (MEGACO), the Session Initiation Protocol (SIP), and the associated Session Description Protocol (SDP). NOTE: The present document relies on the architect... |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 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... |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 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... |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 2.2 Informative references | The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. [i.1] IETF RFC 4825: "The Extensible Markup Language (... |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 3 Definitions and abbreviations | |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: access gateway: gateway device that interworks a significant number of analogue lines/ISDN accesses (directly or via an V5 Access Network) to a packet network and is located at the operator's premises. An access gateway can take the fo... |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: 3PTY Three-Party Service ACR Automatic Communication Rejection AGCF Access Gateway Control Function AOC Advice Of Charge AS Application Server B2BUA Back-to-Back User Agent BGCF Breakout Gateway Control Function CCBS Call Completion on Busy Su... |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 4.1 General | The IMS-based PSTN/ISDN Emulation Subsystem (PES) supports the emulation of PSTN/ISDN services for analogue/ISDN terminals connected to the TISPAN NGN, through residential gateways or access gateways. The IMS-based PES functional architecture is defined in [3]. Emulating PSTN/ISDN services using the IMS-based PES archi... |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 4.2 URI and address assignments | In case multiple subscribers are connected to the same gateway, there is no need to allocate a private user identity per subscriber. Whether a private user identity is allocated per gateway, group of subscribers or per subscriber is a matter for each operator to decide. The AGCF stores private user identities and publi... |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 4.3.1 General | Figure 1 illustrates the session processing model used by the AGCF and VGW functional entities. An AGCF is modelled as comprising H.248 Media Gateway Controller (MGC), Feature Manager (FM), and SIP UA functionality. An AGCF interfaces to a Media Gateway (MG) and also to the S-CSCF (via P1 and Mw reference points respec... |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 4.3.2 Conventions | The communication between the Feature Manager, MGC and SIP User Agent components of the AGCF or VGW is modelled using primitives. This modelling is used as an ease to describe the AGCF and VGW behaviour and is not intended to constrain implementations. The following primitives are defined: • Service-Change: This primit... |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5 Protocol using SIP and SIP events for PES |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.