hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
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. INSUFFICIENT_SERVER_RESOURCES (1) This value is used to indicate that the A-RACF is overloaded and needs to abort the session. INSUFFICIENT_BEARER_RESOURCES (2) This value is used when the bearer has been deactivated due to insufficient bearer resources at a transport gateway (e.g. RCEF for xDSL). |
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 as additional information together with the Media-Type AVP when the QoS class is selected. |
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 the following restrictions: • Only the Action "permit" shall be used. • No "options" shall be used. • The invert modifier "!" for addresses shall not be used. • The keyword "assigned" shall not be used. ETSI ETSI TS 183 026 V3.1.1 (2010-03) 25 If any of these restrictions is not observed by the AF, the server shall send an error response to the AF containing the Experimental-Result-Code AVP with value FILTER_RESTRICTIONS. The Flow description AVP shall be used to describe a single IP flow. The direction "in" refers to uplink IP flows, and the direction "out" refers to downlink IP flows. |
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 flow grouping remains valid. If Flow-Grouping AVP(s) have been provided in earlier service information, and new Flow-Grouping AVP(s) are provided, the new flow grouping information replaces the previous information. Previous flow grouping information is invalidated even if the new Flow-Grouping AVP(s) affect other IP flows. A Flow-Grouping AVP containing no Flows AVP may be used to invalidate flow grouping information provided in earlier service information. A Flow-Grouping AVP containing no Flows AVP shall not be supplied together with other Flow-Grouping AVP(s). If earlier service information has already been provided, flow grouping information in subsequent service information shall not restrict the flow grouping further for IP flows already described in the previous service information. However, new IP flows described for the first time in the subsequent service information may be added to existing flow groups or in new flow groups. AVP Format: Flow-Grouping ::= < AVP Header: 508 > *[Flows] |
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 the corresponding resource reservation in the uplink direction. ENABLED-DOWNLINK (1) This value shall be used to commit the corresponding resource reservation in the downlink direction. ETSI ETSI TS 183 026 V3.1.1 (2010-03) 26 ENABLED (2) This value shall be used to commit a resource reservation in both directions. DISABLED (3) This value shall be used to indicate that the corresponding resource reservation is reserved only and not (yet) committed. REMOVED (4) This value shall be used to release all resources associated with the corresponding resource reservation. |
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 flow is used to transport RTCP. NO_INFORMATION is the default value. NOTE: An SPDF may choose not to identify RTCP flows, e.g. in order to avoid that RTCP flows are always enabled by the A-RACF. |
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 requested. 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 A-RACF reports to the SPDF the release of a bearer (e.g. RCEF policies being removed).In the AAR, this value indicates that the SPDF requests the A-RACF to provide a notification at the removal of a bearer. In case of failure of a multicast request, the RAR message may include the address of the UE that requested the multicast flow and the flow description of the flow. In addition, the present document defines two new events: INDICATION_OF_SUBSCRIBER_DETACHMENT (6) Within a RAR, this value shall be used when the A-RACF reports to the SPDF that a subscriber has been detached. In the AAR, this value indicates that the SPDF requests the A-RACF to provide a notification at the detachment of a subscriber. INDICATION_OF_RESERVATION_EXPIRATION (7) Within a RAR, this value shall be used when the A-RACF reports to the SPDF that a reservation is about to expire. In the AAR, this value indicates that the SPDF requests the A-RACF to provide a notification when a reservation expires. Other events but the above-listed ones defined by TS 129 209 [7] are not relevant at the Rq interface and are not supported. If specified by the SPDF, these values are ignored by the A-RACF. ETSI ETSI TS 183 026 V3.1.1 (2010-03) 27 |
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 one Diameter message, a single IP flow shall not be described by more than one Media-Component-Description AVP. The Media-Component-Description AVP may contain the Flow-Status AVP, which indicates the particular reservation operation to be performed on the media, as described in clauses 5.1 and 5.2. Bandwidth information provided within the Media-Component-Description AVP applies to all those IP flows within the media component, for which no corresponding information is being provided within Media-Sub-Component AVP(s). If a Media-Component-Description AVP is not supplied, or if optional AVP(s) within a Media-Component-Description AVP are omitted, but corresponding information has been provided in previous Diameter messages, the previous information for the corresponding IP flow(s) remains valid. AVP format: Media-Component-Description ::= < AVP Header: 517> { Media-Component-Number } ; Ordinal number of the media comp. *[ Media-Sub-Component ] ; Set of flows for one flow identifier [ AF-Application-Identifier ] [ Media-Type ] [ Max-Requested-Bandwidth-UL ] [ Max-Requested-Bandwidth-DL ] [ Flow-Status ] [ RS-Bandwidth ] [ RR-Bandwidth ] [ Reservation-Priority ] [ Reservation-Class ] [ Transport-Class ] *[ Media-Authorization-Context-Id ] |
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 reservation operation to be performed on the flow, as described in clauses 5.1 and 5.2. ETSI ETSI TS 183 026 V3.1.1 (2010-03) 28 Possible Bandwidth information provided within the Media-Sub-Component AVP takes precedence over information within the encapsulating Media Component Description AVP. If a Media-Sub-Component AVP is not supplied, or if optional AVP(s) within a Media-Sub-Component AVP are omitted, but corresponding information has been provided in previous Diameter messages, the previous information for the corresponding IP flow(s) remains valid, unless new information is provided within the encapsulating Media-Component-Description AVP. If Flow-Description AVP(s) are supplied, they replace all previous Flow-Description AVP(s), even if a new Flow-Description AVP has the opposite direction as the previous Flow-Description AVP. AVP Format: Media-Sub-Component ::= < AVP Header: 519 > { Flow-Number } ; Ordinal number of the IP flow [ Flow-Status ] 0*2[ Flow-Description ] ; UL and/or DL [ Flow-Usage ] [ Max-Requested-Bandwidth-UL ] [ Max-Requested-Bandwidth-DL ] |
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 reservations requested for the media flows identified by the Media-Sub-Component AVP(s) in a Media-Component AVP. The following values of this AVP are specified: • DEFAULT (0): This is the lowest level of priority. If no Reservation-Priority AVP is specified as a main AVP in the AA-Request, this is the priority associated with a resource reservation or modification request. If no Reservation-Priority AVP is specified in a Media-Component-Description AVP, this is the priority associated with resource reservations requested for the media flows identified by the Media-Sub-Component AVP(s) in a Media-Component-Description AVP. - PRIORITY-ONE (1). - PRIORITY-TWO (2). - PRIORITY-THREE (3). - PRIORITY-FOUR (4). - PRIORITY-FIVE (5). - PRIORITY-SIX (6). - PRIORITY-SEVEN (7). - PRIORITY-EIGHT (8). - PRIORITY-NINE (9). - PRIORITY-TEN(10). - PRIORITY-ELEVEN (11). - PRIORITY-TWELVE (12). - PRIORITY-THIRTEEN (13). - PRIORITY-FOURTEEN (14). - PRIORITY-FIFTEEN(15). |
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 may be included by the A-RACF in subsequent Abort-Session-Request (ASR) messages sent to the SPDF. |
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 this AVP is not included, it is assumed that no overbooking is required. |
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 availability of resource. Wait for the Resource Availability event. Idle Idle Received Reservation&Commit Request Verify availability of resource and perform Resource Reservation Commit. Wait for the Successful Enforcement event. Idle Idle Resource Availability Send AAA with the Result-Code AVP set to DIAMETER_SUCCESS. Initialize Authorization-Lifetime and Auth-Grace-Period timers (in case of soft-state). Reserved Idle Resource not available Send AAA with the Experimental-Result-Code AVP set to INSUFFICIENT_RESOURCES. Idle Idle Successful Resource Reservation Enforcement Send AAA with the Result-Code AVP set to DIAMETER_SUCCESS. Initialize Authorization-Lifetime and Auth-Grace-Period timers (in case of soft-state). Committed Idle Unsuccessful Resource Reservation Enforcement Send AAA with the Experimental-Result-Code AVP set to COMMIT_FAILURE. Idle Reserved Received Commit Request Enforce Resource Reservation in network elements (i.e. RCEF). Reserved Reserved Successful Resource Reservation Enforcement Send AAA with the Result-Code AVP set to DIAMETER_SUCCESS. Committed Reserved Unsuccessful Resource Reservation Enforcement Send AAA with the Experimental-Result-Code AVP to COMMIT_FAILURE. Idle Reserved Received STR Send STA, cleanup. Idle Reserved Expiration of Authorization-Lifetime timer Send an unsolicited RAR with the Specific-Action AVP set to INDICATION_OF_RESERVATION_EXPIRATION. Reserved Reserved Expiration of Auth-Grace-Period timer Cleanup. Idle Reserved Received Resource Reservation Refresh Send AAA with the with the Result-Code AVP set to DIAMETER_SUCCESS. Re-initialize Authorization-Lifetime and Auth-Grace-Period timers. Reserved Reserved Received Modification Request Perform Resource Reservation Modification. Reserved Reserved Successful Resource Reservation Modification Send AAA with the Result-Code AVP set to DIAMETER_SUCCESS. Re-initialize Authorization-Lifetime and Auth-Grace-Period timers (in case of soft-state). Reserved Reserved Unsuccessful Resource Reservation Modification Send AAA with the Experimental-Result-Code AVP set to MODIFICATION_FAILURE. Reserved Committed Received Modification Request Perform Resource Reservation Modification. Committed Committed Successful Resource Reservation Modification Send AAA with the Result-Code AVP set to DIAMETER_SUCCESS. Re-initialize Authorization-Lifetime and Auth-Grace-Period timers (in case of soft-state). Committed Committed Unsuccessful Resource Reservation Modification Send AAA with the Experimental-Result-Code AVP set to MODIFICATION_FAILURE. Committed ETSI ETSI TS 183 026 V3.1.1 (2010-03) 32 State Event Action Next State Committed Expiration of Authorization-Lifetime timer Send an unsolicited RAR with the Specific-Action AVP set to INDICATION_OF_RESERVATION_EXPIRATION. Committed Committed Received Resource Reservation Refresh Send AAA with the Result-Code AVP set to DIAMETER_SUCCESS. Re-initialize Authorization-Lifetime and Auth-Grace-Period timers (in case of soft-state). Committed Committed Expiration of Auth-Grace-Period timer Cleanup. Idle Committed Received STR Release resources, cleanup. Idle All Critical Event Detected Send ASR with appropriate Abort-Cause AVP, cleanup. Idle All Non Critical Event Detected Send RAR with appropriate Specific-Action AVP. Unchanged ETSI ETSI TS 183 026 V3.1.1 (2010-03) 33 Annex B (informative): Change history Date WG Doc. CR Rev CAT Title / Comment Current Version New Version 29-06-07 14bTD303r1 001 B Overbooking requirement 1.4.0 2.0.0 07-09-07 14tTD566 002 A Wrong Flow-Status during session modification 2.0.0 2.1.0 29-10-07 15bTD199r1 003 F Rq interface_AAR command_Correction 2.1.0 2.2.0 07-03-08 16bTD207r1 005 B Adding authorization package ID to Rq 2.2.0 2.3.0 30-05-08 17bTD232r1 007 D Rq Reference model update 2.3.0 2.3.1 18-06-08 Update of figure format by rapporteur 2.3.1 2.3.2 19-06-08 Addition of Change History annex by ETSI Secretariat 2.3.2 2.3.3 02-07-08 18WTD298r3 008 1 D Rq overbooking procedures 2.3.3 2.3.4 02-07-08 18WTD303r1 009 D New AVP code allocation 2.3.3 2.3.4 02-07-08 Correction to Change history table 2.3.4 2.3.5 Publication 2.3.5 2.4.1 06-11-09 22bTD080r1 001 F Update of the Reservation priority AVP for Rq 2.4.1 3.0.0 06-11-09 22bTD066r1 002 F WI 3210 AF-Application-Id alignment with 29.209 2.4.1 3.0.0 06-11-09 22bTD079r3 003 B WI3210 – Rq - Multicast notification support 2.4.1 3.0.0 15-12-09 23WTD093r1 004 B Multiple Improvements 3.0.0 3.0.1 Publication 3.0.1 3.1.1 ETSI ETSI TS 183 026 V3.1.1 (2010-03) 34 History Document history V1.1.1 June 2006 Publication as ES 283 026 V1.4.1 September 2007 Publication as ES 283 026 V1.6.0 April 2008 Publication as ES 283 026 V2.4.1 November 2008 Publication as ES 283 026 V3.1.1 March 2010 Publication |
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 accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably, the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the method of access to the referenced document and the full network address, with the same punctuation and use of upper case and lower case letters. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity. |
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] ETSI TS 124 447: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); TISPAN; NGN IMS Supplementary Services; Advice Of Charge (AOC) (Release 8)". |
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) 6 |
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 447 [6]. ETSI ETSI TS 183 047 V2.2.0 (2008-06) 9 Annex C (normative): Charging Information Elements The provisions of the present document are contained in TS 124 447 [6]. ETSI ETSI TS 183 047 V2.2.0 (2008-06) 10 Annex D (normative): AOC XML Schema: The provisions of the present document are contained in TS 124 447 [6]. ETSI ETSI TS 183 047 V2.2.0 (2008-06) 11 History Document history V2.1.1 March 2007 Publication V2.2.0 June 2008 Publication |
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 functionality. TISPAN IMS is based on 3GPP IMS. It shall be possible to: • deploy TISPAN DC using 3GPP2 MMD as long as the related TISPAN requirements on IMS are considered within 3GPP2 MMD; • have interworking of TISPAN DC with 3GPP PoC and 3GPP2 PoC services. |
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. • For a non-specific reference, the latest version applies. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity. [1] OMA-TS- PoC-ControlPlane-V1: "OMA PoC Control Plane". [2] OMA-TS- PoC-UserPlane-V1: "OMA PoC User Plane". [3] OMA-TS- PoC-XDM-V1: "PoC XDM Specification". [4] ETSI ES 283 030: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Presence Service Capability; Protocol Specification [3GPP TS 24.141 V7.0.0, modified and OMA-TS-Presence-SIMPLE-V1-0, modified]". [5] ETSI TR 180 000: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Terminology". [6] ETSI ES 283 003: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP) Stage 3 [3GPP TS 24.229 (Release 7), modified]". [7] ETSI TS 183 033: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IP Multimedia; Diameter based protocol for the interfaces between the Call Session Control Function and the User Profile Server Function/Subscription Locator Function; Signalling flows and protocol details [3GPP TS 29.228 V6.8.0 and 3GPP TS 29.229 V6.6.0, modified]". [8] ETSI TS 181 005: "Telecommunications and Internet Converged Services and Protocols for Advanced Networking (TISPAN); Services and Capabilities Requirements". ETSI ETSI TS 183 045 V2.1.1 (2007-02) 6 |
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 communication server: entity performing the PoC Server functions implementing the 3GPP IMS application level network functionality for the Direct Communication service in the originating and terminating network |
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 and Internet converged Services and Protocols for Advanced Networking UE User Equipment XCAP XML Configuration Access Protocol XDM XCAP Document Management XDMS XCAP Document Management Server XML Extensible Markup Language Endorsement Notice The present document, in conjunction with OMA-TS- PoC_ControlPlane-V1 [1], OMA-TS- PoC_UserPlane-V1 [2] and OMA-TS-PoC_XDM-V1 [3] provides the stage 3 specification for the Direct Communication service for NGNs. When SIP/IP Core is referred in the document, IMS is used. Endorsement of OMA PoC Control Plane This clause provides an endorsement of OMA-TS- PoC_ControlPlane-V1 [1]. The elements of OMA-TS- PoC_ControlPlane-V1 [1] apply, with the following modifications: NOTE: Underlining and/or strike-out are used to highlight detailed modifications where necessary. Throughout the text of the OMA-TS- PoC_ControlPlane-V1 The following rules are valid through the whole document: • Replace "mobile originating/terminating" with "UE originating/terminating". • Replace "mobile device" with "UE". ETSI ETSI TS 183 045 V2.1.1 (2007-02) 7 Release 6 Throughout the document when this text exists: When the SIP/IP Core corresponds with 3GPP/3GPP2 IMS, the PoC Client SHALL use 3GPP/3GPP2 IMS mechanisms according to rules and procedures of [TS24.229] / [3GPP2 X.S0013.4] with the clarifications given in this clause. Replace it with the following: When the SIP/IP Core corresponds to TISPAN IMS the DC Client SHALL use TISPAN IMS mechanisms according to rules and procedures of ES 283 003 [6] with the clarifications given in this clause. Clause 1 Scope In OMA-TS- PoC_Control Plane-V1 [1] does not apply and is replaced by the clause 1 'Scope' in the present document. Clause 2 References In OMA-TS- PoC_Control Plane-V1 [1] applies with the modifications described in table 1. The references listed in table 1 are replaced by references applicable to NGN. Table 1: List of references to be replaced Reference no. Reference in OMA-TS- PoC_ControlPlane-V1 Replaced reference(s) [TS24.229] 3GPP TS 24.229: "IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3" (Release 6), URL:http://www.3gpp.org/ftp/Specs/latest/Rel- 6/24_series/ ETSI ES 283 003 'Telecommunications and Internet converged Services and Protocols for Advanced Networks (TISPAN); IP Multimedia Call Control Protocol based on Session Initiation Protocol 3GPP TS. 24.229 (Release 7), modified '. [OMA- PoC_UP] OMA Push to talk over Cellular (PoC) - User Plane The present document. [OMA PoC_XDM Specification] OMA-PoC_XDM_Specification-V1. The present document. [OMA-Pres- Spec] OMA SIP/SIMPLE Presence Specification (OMA- PAG-SIMPLE-Spec-V1) ETSI TS 283 030 'Telecommunications and Internet converged Services and Protocols for Advanced Networks (TISPAN); Presence Application Service Capability; SIP Protocol Specification'. [TS29.228] 3GPP TS 29.228: "IP Multimedia (IM) Subsystem Cx and Dx interfaces; Signalling flows and message contents", (Release 6) URL:http://www.3gpp.org/ftp/Specs/latest/Rel- 6/29_series/ ETSI TS 183 033 DTS-03060 'Telecommunications and Internet Converged Services and Protocols for Advanced Networking (TISPAN); IP Multimedia; IP Multimedia (IM) Subsystem Cx and Dx Interfaces; Signalling flows and message contents & IP Multimedia (IM) Subsystem Cx and Dx Interfaces; Cx and Dx interfaces based on the Diameter protocol [3GPP TS.29.228 v.6.8.0 and 3GPP TS.29.229 v.6.6.0, modified]' [OMA- PoC_AD] OMA Push to talk over Cellular (PoC) - Architecture ETSI TS 182 017 DTR 02034 WG 2 Workitem on Direct Communication Clause 3 Terminology and Conventions In OMA-TS- PoC_ControlPlane-V1 [1] applies with the additions in the clause 3 "Definitions, and abbreviations" in the present document. Clause 3.2 For the purposes of the present document, the terms and definitions given in OMA-TS- PoC_ControlPlane-V1 [1] apply with the following additions: Instead of PoC the term DC is used. ETSI ETSI TS 183 045 V2.1.1 (2007-02) 8 Release 6 Replace 3GPP/3GPP2 with TISPAN Clause 3.3 For the purposes of the present document, the following abbreviations apply: DC Direct Communication Clause 4 Introduction In OMA-TS- PoC_ControlPlane-V1 applies. Clause 5 Common procedures In OMA-TS- PoC_ControlPlane-V1 applies. Clause 6 Procedures at the PoC Client In OMA-TS- PoC_ControlPlane-V1 applies. Clause 7 Procedures at the PoC Server In OMA-TS- PoC_ControlPlane-V1 applies. Appendix A Static Conformance Requirements (SCR) In OMA-TS- PoC_ControlPlane-V1 applies. Appendix B The parameters to be provisioned for PoC service In OMA-TS- PoC_ControlPlane-V1 applies with the following changes: NGN Direct Communication OMA PoC Device Management general This appendix describes the parameters that are needed for initiation of PoC Direct Communication service, as well as continuous provisioning by service provider. These parameters are specified in Client Provisioning Application Characteristics document (AC file) and Device Management Management Object (DM MOs). The bootstrap function specified in [Provisioning Bootstrap] and [OMA DM] SHALL be used to enforce the security of provisioning. Existing parameters in [Provisioning Content] and [OMA DM] are re-used; those without corresponding parameters are defined in present specification and to be registered in OMNA through OMA official registration procedures. • 1. APPID (Application ID): The application characteristics name for this application, to be used by DM Client to uniquely identify the application. • 2. NAME: Application name. To be displayed in equipment, it's specific for each service provider. • 3. PROVIDER-ID: provides an identifier for the application service access point described by an APPLICATION characteristic. • 4. TO-NAPID: This parameter allows an application to refer to a network access point with a matching NAPID parameter. It is only possible to refer to network access points defined within the same provisioning document. • 5. TO-APPREF: The TO-APPREF parameter links the APPLICATION characteristics to another secondary APPLICATION characteristic with a matching APPREF parameter. • 6. Pre-established Session support: A flag to inform whether the PoC Direct Communication Server supports the Pre-established Session functionality. • 7. Support for Simultaneous PoC Sessions: Maximum number of Simultaneous PoC Sessions supported for this PoC User. The value 0 is used to indicate that Simultaneous PoC Sessions are not supported. ETSI ETSI TS 183 045 V2.1.1 (2007-02) 9 Release 6 • 8. Max Ad-hoc Group size: Maximum number of Participants allowed for an Ad-hoc PoC Group PoC Session. • 9. Conference-Factory-URI: A SIP URI used for setting up an Ad-hoc PoC Group or 1-1 PoC Session. • 10. Exploder-URI: A SIP URI used for sending SIP MESSAGE e.g. Group Advertisement to an URI-list. • 11. Conference-URI Template: A template used by the XDM Client to propose a Conference URI when creating a PoC Group document. • 12. T10 (Talk Burst Release) timer: This parameter indicates the value of the T10 (Talk Burst Release) timer in milliseconds. • 13. T11 (Talk Burst Request) timer: This parameter indicates the value of the T11 (Talk Burst Request)timer in milliseconds. • 14. T13 (End of RTP Media) timer: This parameter indicates the value of the T13 (End of RTP Media) timer in milliseconds. • 15. PoC Direct Communication Server Presence support: This parameter indicates the Presence publish capability of the PoC Direct Communication Server, the PoC status on behalf of a PoC Direct Communication Client. NOTE: The parameters 12 - 14 are parameters needed for OMA PoC User Plane procedures. The parameters from 6 - 15 are defined in the present specification for Direct Communication service. They are to be registered in OMNA. The PoC Direct Communication Client SHALL have provisioned parameters 1, 2, 4, 5, 6, 7, 8, 9, 11, 12, 13 and 15 and the PoC Direct Communication Client SHOULD have the parameters, 3, 10 and 14 provisioned. These parameters SHALL be obtained via the DM-1 reference point, from the data which is provisioned to the DM Client as specified in [Provisioning Content] and [OMA DM]. B.2 OMA PoC Application Characteristics file OMA PoC has defined a client provisioning file called Application characteristics (AC) file based on [OMA Client Provisioning]. It MAY be used for initial provisioning of PoC service configuration to the User Equipment. The file is specified in [OMA- PoC_AC]. B.3 OMA PoC Device Management Management Object (MO) file This clause defines the mobile device Management Object (MO) for Direct CommunicationOMA PoC. The MO MAY be used for initial provisioning of parameters when the DM Profile is to be used (as specified on [OMA-DM-v1-2]), and the MO SHOULD be used for later provisioning of parameters according to [OMA-DM-v1-1-2] or [OMA-DM-v1-2], if required by the service provider to update service configurations. The OMA PoC Management Object consists of relevant parameters required by the OMA PoC Enabler]. It is compatible with OMA Device Management protocol specifications[OMA-DM-v1-1-2], and is defined using the OMA DM Device Description Framework as described in [OMA-SyncML-DMTND-V1-1-2] and [OMA-SyncML-DMStdObj-V1-1-2]. The Management Object Identifier is: org.openmobilealliance/1.0/PoC. Protocol compatibility: This MO is compatible with OMA DM 1.1.2. Management object name: OMA-PoC. Appendix C "Presence information elements and procedures" In OMA-TS- PoC_ControlPlane-V1 applies. Appendix D "Initial Filter Criteria" In OMA-TS- PoC_ControlPlane-V1 applies. ETSI ETSI TS 183 045 V2.1.1 (2007-02) 10 Release 6 Appendix E "Documentation of SIP, SDP and XML" In OMA-TS- PoC_ControlPlane-V1 applies. Appendix F "Examples of signalling flows" In OMA-TS- PoC_ControlPlane-V1 applies. Appendix G "Change History" In OMA-TS- PoC_ControlPlane-V1 is not applicable. Endorsement of OMA PoC User Plane This clause provides an endorsement of OMA-TS- PoC_UserPlane-V1 [2]. The elements of OMA-TS- PoC_UserPlane-V1 [2] apply, with the following modifications: Throughout the text of the OMA-TS- PoC_UserPlane-V1 The following rules are valid through the whole document. Replace 3GPP/3GPP2 IMS with TISPAN IMS. Replace "mobile originating/terminating"' with "UE originating/terminating". Replace "'mobile device" with "'UE"'. Clause 1 "Scope" In OMA-TS- PoC_UserPlane-V1 [2] does not apply and is replaced by the clause 1 "Scope" in the present document. Clause 2 "References" In OMA-TS- PoC_UserPlane-V1 [2] applies with the modifications described in table 2. The references listed in table 2 are replaced by references applicable to NGN. Table 2: List of references to be replaced Reference no. References in OMA-TS- PoC_UserPlane-V1 Replaced reference(s) in the present document [OMA- PoC_CP] 'OMA PoC Control Plane Document', Version 1, Open Mobile Alliance™, OMA-TS- PoC_ControlPlane-V1, URL:http://www.openmobilealliance .org/ The present document. [OMA- PoC_XDMS] OMA-PoC_XDM_Specification' Version 1, Open Mobile Alliance™, OMA-TS-PoC_XDM-V1, URL:http://www.openmobilealliance .org/ The present document. [TS24.229] 3GPP TS 24.229 '3rd Generation Partnership Project; Technical Specification Group Core Network; IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 (Release 6)' ETSI ES 283 003 'Telecommunications and Internet converged Services and Protocols for Advanced Networks (TISPAN); IP Multimedia Call Control Protocol based on Session Initiation Protocol 3GPP TS. 24.229 (Release 7), modified'. ETSI ETSI TS 183 045 V2.1.1 (2007-02) 11 Release 6 Reference no. References in OMA-TS- PoC_UserPlane-V1 Replaced reference(s) in the present document [TS29.228] 3GPP TS 29.228: "IP Multimedia (IM) Subsystem Cx and Dx interfaces; Signalling flows and message contents", (Release 6) URL:http://www.3gpp.org/ftp/Specs/ latest/Rel-6/29_series/ ETSI TS 183 033 DTS-03060 'Telecommunications and Internet Converged Services and Protocols for Advanced Networking (TISPAN); IP Multimedia; IP Multimedia (IM) Subsystem Cx and Dx Interfaces; Signalling flows and message contents & IP Multimedia (IM) Subsystem Cx and Dx Interfaces; Cx and Dx interfaces based on the Diameter protocol [3GPP TS.29.228 v.6.8.0 and 3GPP TS.29.229 v.6.6.0, modified]' [OMA- PoC_AD] OMA Push to talk over Cellular (PoC) – Architecture ETSI TS 182 017 DTR 02034 WG 2 Workitem on Direct Communication Clause 3 "Terminology and Conventions" In OMA-TS- PoC_UserPlane-V1 [2] applies with the clarification additions in the clause 3 "Definitions, and abbreviations" in the present document. Clause 3.2 For the purposes of the present document, the terms and definitions given in OMA-TS- PoC_UserPlane-V1 [2] apply with the flowing additions: Instead of PoC the term DC is used. Clause 3.3 For the purposes of the present document, the following abbreviations apply: DC Direct Communication Clause 4 "Introduction'" In OMA-TS- PoC_UserPlane-V1 [2] applies. Clause 5 "Transport" In OMA-TS- PoC_UserPlane-V1 [2] applies. Clause 6 "Talk burst control" In OMA-TS- PoC_UserPlane-V1 [2] applies. Clause 7 "Media control" In OMA-TS- PoC_UserPlane-V1 [2] applies with the addition of the following text in clause 7.9 "'Codecs": For TISPAN NGN codecs see [8]. Direct Communication server support terminal codec requirements in [8] as reflected in the conformance table in A.2.4. Clause 8 "Talker Identification" In OMA-TS- PoC_UserPlane-V1 [2] applies. Clause 9 "Timers" In OMA-TS- PoC_UserPlane-V1 [2] applies. Appendix A "Static Conformance Requirement (SCR)" ETSI ETSI TS 183 045 V2.1.1 (2007-02) 12 Release 6 In OMA-TS- PoC_UserPlane-V1 [2] applies. A.1 PoC Client Applies with the change as follows: Item Function Reference Status Requirement PoC_UserPlaneV1 -UMC-C-001 Support of quality feed back according to rules and procedures specified in [RFC3550]. Clause 7.1 O PoC_UserPlaneV1 -UMC-C-002 Supports the transmission of RTCP SR/RR compound packets. Clause 7.1.2 O PoC_UserPlaneV1- UMC-C-001 PoC_UserPlaneV1 -UMC-C-003 Uses the reception of the RTCP SR compound packet as indication to trigger the transmission of the RTCP RR compound packet. Clause 7.1.2.2 O PoC_UserPlaneV1- UMC-C-002 PoC_UserPlaneV1 -UMC-C-004 Implement a timer that supervises the reception of the RTCP SR compound packet. Clause 7.1.2.2 O PoC_UserPlaneV1- UMC-C-003 PoC_UserPlaneV1 -UMC-C-005 Support of Media Parameter negotiation. Clause 7.2, 7.2.1.1 and 7.2.1.2 M PoC_UserPlaneV1 -UMC-C-006 Support of User Plane adaptation. Clause 7.3 O PoC_UserPlaneV1 -UMC-C-007 Changes the voice frame packetization or voice codec mode by Out-band signalling using SDP payload within SIP messages. Clause 7.3 O PoC_UserPlaneV1- UMC-C-006 PoC_UserPlaneV1 -UMC-C-008 Void. PoC_UserPlaneV1 -UMC-C-009 Initiate User Plane adaptation (out-band) triggered by e.g. roaming to the system with different media capabilities. Clause 7.3.1 O PoC_UserPlaneV1- UMC-C-006 PoC_UserPlaneV1 -UMC-C-010 Supports Media on and off hold. Clause 7.4.1 O PoC_UserPlaneV1 -UMC-C-011 Sends Talk Bursts, when the Media is on hold. Clause 7.4 O PoC_UserPlaneV1- UMC-C-010 PoC_UserPlaneV1 -UMC-C-012 Supports Simultaneous PoC Sessions. Clause 7.5.1 O PoC_UserPlaneV1 -UMC-C-013 Supports the sending of RTP Media packets to any of the Simultaneous PoC Sessions according to the PoC User selection. Clause 7.5.1 O PoC_UserPlaneV1- UMC-C-012 PoC_UserPlaneV1 -UMC-C-014 Supports RTP Media Session release of the Pre-established Session. Clause 7.6 O PoC_UserPlaneV1- UTB-C-014 PoC_UserPlaneV1 -UMC-C-015 Support of Media transfer. Clause 7.7.1 M PoC_UserPlaneV1 -UMC-C-016 Supports media buffering for handling of variable latency in incoming RTP Media packets. Clause 7.8.1 O PoC_UserPlaneV1 -UMC-C-017 Support coding and decoding of Media Clause 7.9 M PoC_UserPlaneV1- UMC-C-018 OR PoC_UserPlaneV1- UMC-C-019 OR PoC_UserPlaneV1- UMC-C-020 PoC_UserPlaneV1 -UMC-C-018 Supports codecs recommended by 3GPP Clause 7.9 O PoC_UserPlaneV1 -UMC-C-019 Supports codecs recommended by 3GPP2 Clause 7.9 O PoC_UserPlaneV1 -UMC-C-020 Supports codecs recommended by TISPAN NGN Clause 7/9 O ETSI ETSI TS 183 045 V2.1.1 (2007-02) 13 Release 6 A.2 PoC Server performing the Participating PoC Function A.2.4 Media Control Applies with the change as follows: Item Function Reference Status Requirement PoC_UserPlaneV1- PMC-S-001 Support of quality feed back according to rules and procedures specified in [RFC3550]. Clause 7.1.1 O PoC_UserPlaneV1- PPR-S-002 PoC_UserPlaneV1- PMC-S-002 Modify the content of the RTCP SR compound packet send by the PoC Client in an interrupted PoC Session according to rules and procedures specified in [RFC3550]. Clause 7.1.3 O PoC_UserPlaneV1- UMC-S-001 PoC_UserPlaneV1- PMC-S-003 Media parameter negotiation. Clause 7.2.1.2 O PoC_UserPlaneV1- PPR-S-002 PoC_UserPlaneV1- PMC-S-004 Support for putting Media on/off hold. Clause 7.4.2 O PoC_UserPlaneV1- PPR-S-002 PoC_UserPlaneV1- PMC-S-005 User Plane adaptation. Clause 7.3 O PoC_UserPlaneV1- PPR-S-002 PoC_UserPlaneV1- PMC-S-006 Forward the Talk Bursts and TBCP messages between the PoC Client and the PoC Server performing the Controlling PoC Function while Media is placed on hold for a PoC Session. Clause 7.4.2 O PoC_UserPlaneV1- PMC-S-004 PoC_UserPlaneV1- PMC-S-007 Simultaneous PoC Sessions. Clause 7.5.2 O PoC_UserPlaneV1- PTB-S-003 PoC_UserPlaneV1- PMC-S-008 Forwards the TBCP messages of all PoC Sessions from the PoC Server(s) performing the Controlling PoC Function to PoC Client. Clause 7.5.2 O PoC_UserPlaneV1- PMC-S-007 PoC_UserPlaneV1- PMC-S-009 Sends a RTCP SR message to the PoC Client concerning the PoC Session, which was interrupted due to activity in another PoC Session. Clause 7.5.2 O PoC_UserPlaneV1- PMC-S-007 PoC_UserPlaneV1- PMC-S-010 Modifies the RTCP RR and SR messages sent between the PoC Client and the PoC Server to improve the accuracy of the quality feedback in the case of interrupted Talk Burst. Clause 7.5.2 O PoC_UserPlaneV1- PMC-S-007 PoC_UserPlaneV1- PMC-S-011 Sends a TBCP Talk Burst Taken message prior to the first RTP packet being sent to the PoC Client. Clause 7.5.2 O PoC_UserPlaneV1- PMC-S-007 PoC_UserPlaneV1- PMC-S-013 Supports Media transfer. Clause 7.7.2 O PoC_UserPlaneV1- PPR-S-002 AND (PoC_UserPlaneV1- PMC-S-015 OR PoC_UserPlaneV1- PMC-S-016 OR PoC_UserPlaneV1- PMC-S-017) PoC_UserPlaneV1- PMC-S-014 Discards RTP Media of the PoC Sessions not selected for transmitting to the PoC Client. Clause 7.7.2 O PoC_UserPlaneV1- PTB-S-003 PoC_UserPlaneV1- PMC-S-015 Supports codecs recommended by 3GPP. Clause 7.9 O PoC_UserPlaneV1- PMC-S-013 PoC_UserPlaneV1- PMC-S-016 Supports codecs recommended by 3GPP2. Clause 7.9 O PoC_UserPlaneV1- PMC-S-013 PoC_UserPlaneV1- PMC-S-017 Supports codecs recommended by TISPAN NGN. Clause 7.9 O PoC_UserPlaneV1- PMC-S-013 Appendix B "Message flows" In OMA-TS- PoC_UserPlane-V1 [2] applies. Appendix C "Change History" ETSI ETSI TS 183 045 V2.1.1 (2007-02) 14 Release 6 In OMA-TS- PoC_UserPlane-V1 [2] is not applicable. Appendix D "RTP Session description parameters (Informative) " In OMA-TS- PoC_UserPlane-V1 [2] applies. Endorsement of PoC XDM Specification This clause provides an endorsement of OMA-TS-PoC_XDM-V1 [3]. The elements of OMA-TS-PoC_XDM-V1 [3] apply, with the following modifications: Throughout the text of the OMA-TS-PoC_XDM-V1 Clause 1 "Scope" In OMA-TS-PoC_XDM-V1 [3] does not apply and is replaced by the clause 1 "Scope" in the present document. Clause 2 "References" In OMA-TS-PoC_XDM-V1 [3] applies with the modifications described in table 3. The references listed in table 3 are replaced by references applicable to NGN. Table 3: List of references to be replaced Reference no. Reference in OMA-TS-PoC_XDM- V1 Replaced reference(s) in the present document [SHAREDXDM] 'OMA Shared XDM Specification', Version 1, Open Mobile Alliance™, OMA-TS-XDM_Shared-V1, URL:http://www.openmobilealliance. org/ ETSI TS 183 038 'Telecommunications and Internet converged Services and Protocols for Advanced Networks (TISPAN); PSTN/ISDN Simulation Services; Extensible Markup Language (XML) Document Management; Protocol Specification;'. Clause 3 "Terminology and Conventions" In OMA-TS-PoC_XDM-V1 [3] applies with the additions in the clause 3 "Definitions, symbols and abbreviations" in the present document. Clause 3.2 For the purposes of the present document, the terms and definitions given in OMA-TS- PoC_UserPlane-V1 [2] apply with the following additions: Instead of PoC the term DC is used. Replace 3GPP/3GPP2 with TISPAN Clause 3.3 For the purposes of the present document, the following abbreviations apply: DC Direct Communication ETSI ETSI TS 183 045 V2.1.1 (2007-02) 15 Release 6 Clause 4 "Introduction" In OMA-TS-PoC_XDM-V1 [3] applies. Clause 5 "PoC XDM Application Usages" In OMA-TS-PoC_XDM-V1 [3] applies. Clause 6 "PoC Extensions to Shared XDM Application Usages" In OMA-TS-PoC_XDM-V1 [3] applies. Appendix A "Static Conformance Requirements" In OMA-TS-PoC_XDM-V1 [3] applies. Appendix B "Examples" In OMA-TS-PoC_XDM-V1 [3] applies. Appendix C "Change History" Is not applicable. ETSI ETSI TS 183 045 V2.1.1 (2007-02) 16 Release 6 History Document history V2.1.1 February 2007 Publication |
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 accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably, the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the method of access to the referenced document and the full network address, with the same punctuation and use of upper case and lower case letters. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity. |
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] Void. [7] Void. [8] Void. [9] Void. [10] Void. [11] Void. [12] Void. ETSI ETSI TS 183 023 V2.0.0 (2008-06) 6 [13] ETSI TS 124 423 Release 8: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); TISPAN; PSTN/ISDN simulation services; Extensible Markup Language (XML) Configuration Access Protocol (XCAP) over the Ut interface for Manipulating NGN PSTN/ISDN Simulation Services (3GPP TS 24.423 Release 8)". |
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 (XCAP) The provisions of the present document are contained in TS 124 423 [13]. 6 NGN PSTN/ISDN simulation services XCAP application usage The provisions of the present document are contained in TS 124 423 [13]. ETSI ETSI TS 183 023 V2.0.0 (2008-06) 7 Annex A (informative): Bibliography Information is contained in TS 124 423 [13]. ETSI ETSI TS 183 023 V2.0.0 (2008-06) 8 History Document history V2.0.0 June 2008 Publication |
f35b69ccd2199c2dc10834594190c0f0 | 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 architectural framework defined in TS 182 012 [3] for IMS-based PES Emulation and may need to be updated once the open issues identified in the present document are resolved. The present document is applicable to: • the interface between the User Equipment (UE) and the Call Session Control Function (CSCF); • the interface between the Access Gateway Control Function (AGCF) and the Media Gateway Function (MGF); • the interface between the Access Gateway Control Function (AGCF) and the Call Session Control Function (CSCF); • the interface between the CSCF and any other CSCF; • the interface between the CSCF and an Application Server (AS); • the interface between the CSCF and the Media Gateway Control Function (MGCF); • the interface between the S-CSCF and the Multimedia Resource Function Controller (MRFC); • the interface between the CSCF and the Breakout Gateway Control Function (BGCF); • the interface between the BGCF and the MGCF; • the interface between the BGCF and any other BGCF; • the interface between the CSCF and an external Multimedia IP network; • the interface between the CSCF and the IBCF. |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 1.1 Not supported services and capabilities | The present document depends on supported capabilities by some other specifications. This situation may lead to some limitations. See clause 6.3.5 and annex I. |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 2 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 are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 14 |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI ES 282 001: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Functional Architecture". [2] ETSI TS 182 006: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IP Multimedia Subsystem (IMS); Stage 2 description [3GPP TS 23.506 Release 8, modified]". [3] ETSI TS 182 012: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IMS-based PSTN/ISDN Emulation Sub-system (PES); Functional architecture". [4] ETSI TS 124 229: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 (3GPP TS 24.229)". [5] ETSI TS 183 002: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); H.248 Profile Version 3 for controlling Access and Residential Gateways". [6] ETSI TS 124 628: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Common Basic Communication procedures using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.628)". [7] ETSI TS 124 647: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Advice Of Charge (AOC) using IP Multimedia (IM) Core Network (CN) subsystem (3GPP TS 24.647)". [8] ETSI TS 124 610: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Communication HOLD (HOLD) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.610)". [9] ETSI TS 124 604: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Communication Diversion (CDIV) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.604)". [10] ETSI ES 200 659-3: "Access and Terminals (AT); Analogue access to the Public Switched Telephone Network (PSTN); Subscriber line protocol over the local loop for display (and related) services; Part 3: Data link message and parameter codings". [11] Void. [12] ETSI ETS 300 738: "Human Factors (HF); Minimum Man-Machine Interface (MMI) to public network based supplementary services". [13] ITU-T Recommendation H.248.23: "Gateway control protocol: Enhanced Alerting packages". [14] ITU-T Recommendation H.248.26: "Gateway control protocol: Enhanced analog lines packages". [15] IETF draft-ietf-sipping-config-framework-17: "A Framework for Session Initiation Protocol User Agent Profile Delivery". [16] IETF RFC 4240: "Basic Network Media Services with SIP". [17] IETF RFC 4733: "RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals". [18] IETF RFC 3842: "A Message Summary and Message Waiting Indication Event Package for the Session Initiation Protocol (SIP)". [19] IETF RFC 3966: "The tel URI for Telephone Numbers". ETSI ETSI TS 183 043 V3.4.1 (2011-04) 15 [20] ETSI EN 383 001: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Interworking between Session Initiation Protocol (SIP) and Bearer Independent Call Control (BICC) Protocol or ISDN User Part (ISUP) [ITU-T Recommendation Q.1912.5, modified]". [21] IETF RFC 2805: "Media Gateway Control Protocol Architecture and Requirements". [22] ITU-T Recommendation H.248.1: "Gateway control protocol". [23] ITU-T Recommendation G.711: "Pulse code modulation (PCM) of voice frequencies". [24] IETF RFC 3323: "A Privacy Mechanism for the Session Initiation Protocol (SIP)". [25] IETF RFC 3325: "Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks". [26] ETSI TS 124 606: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Message Waiting Indication (MWI) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.606)". [27] ETSI TS 124 611: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Anonymous Communication Rejection (ACR) and Communication Barring (CB) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.611)". [28] ETSI ES 282 010: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Charging management [Endorsement of 3GPP TS 32.240 Release 7, 3GPP TS 32.260 Release 7, 3GPP TS 32.297 Release 7, 3GPP TS 32.298 Release 7 and 3GPP TS 32.299 Release 7, modified]". [29] ITU-T Recommendation Q.763: "Signalling System No. 7 - ISDN User Part formats and codes". [30] ITU-T Recommendation Q.764: "Signalling System No. 7 - ISDN User Part signalling procedures". [31] ITU-T Recommendation Q.1980.1: "The Narrowband Signalling Syntax (NSS) - Syntax definition". [32] ETSI TS 129 163: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched (CS) networks (3GPP TS 29.163)". [33] ETSI TS 124 623: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Extensible Markup Language (XML) Configuration Access Protocol (XCAP) over the Ut interface for Manipulating Simulation Services (3GPP TS 24.623)". [34] ETSI EN 300 356 (all parts): "Integrated Services Digital Network (ISDN); Signalling System No.7 (SS7); ISDN User Part (ISUP) version 4 for the international interface". [35] ITU-T Recommendation Q.735.3: "Stage 3 description for community of interest supplementary services using Signalling System No. 7 : Multi-level precedence and preemption". [36] ITU-T Recommendation Q.735.6: "Stage 3 description for community of interest supplementary services using Signalling System No. 7 : Global Virtual Network Service (GVNS)". [37] ITU-T Recommendation Q.736.3: "Stage 3 description for charging supplementary services using Signalling System No. 7 : Reverse charging (REV)". [38] IETF RFC 3261: "SIP: Session Initiation Protocol". [39] ETSI EN 301 798: "Services and Protocols for Advanced Networks (SPAN); Anonymous Call Rejection (ACR) Supplementary Service; Service description". [40] ETSI TS 183 036: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); ISDN/SIP interworking; Protocol specification". ETSI ETSI TS 183 043 V3.4.1 (2011-04) 16 [41] ETSI EN 300 403-1: "Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS1) protocol; Signalling network layer for circuit-mode basic call control; Part 1: Protocol specification [ITU-T Recommendation Q.931 (1993), modified]". [42] ETSI TS 129 658: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; TISPAN; SIP Transfer of IP Multimedia Service Tariff Information; Protocol specification (3GPP TS 29.658)". [43] ETSI ES 283 035: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Network Attachment Sub-System (NASS); e2 interface based on the DIAMETER protocol". [44] ETSI TS 124 615: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Communication Waiting (CW) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol Specification (3GPP TS 24.615)". [45] IETF RFC 3023: "XML Media Types". [46] Void. [47] ETSI TS 124 642: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Completion of Communications to Busy Subscriber (CCBS) and Completion of Communications by No Reply (CCNR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol Specification (3GPP TS 24.642)". [48] ITU-T Recommendation V.152: "Procedures for supporting voice-band data over IP networks". [49] ITU-T Recommendation T.38: "Procedures for real-time Group 3 facsimile communication over IP networks". [50] IETF RFC 5939: "Session Description Protocol (SDP) Capability Negotiation". [51] IETF draft-ietf-mmusic-sdp-media-capabilities: "SDP media capabilities Negotiation". [52] IETF draft-schwarz-mmusic-sdp-offer-answer-examples: "Session Description Protocol (SDP) - Revised Offer/Answer Protocol (SDPCapNeg & MediaCapNeg) - Offer/Answer Examples". [53] IETF RFC 3388: "Grouping of Media Lines in the Session Description Protocol (SDP)". [54] IETF RFC 3389: "Real-time Transport Protocol (RTP) Payload for Comfort Noise (CN)". [55] ITU-T Recommendation G.168: "Digital network echo cancellers". [56] ITU-T Recommendation T.30: "Procedures for document facsimile transmission in the general switched telephone network". [57] ETSI EN 300 659-1: "Access and Terminals (AT); Analogue access to the Public Switched Telephone Network (PSTN); Subscriber line protocol over the local loop for display (and related) services; Part 1: On-hook data transmission". [58] ETSI EN 300 659-2: "Access and Terminals (AT); Analogue access to the Public Switched Telephone Network (PSTN); Subscriber line protocol over the local loop for display (and related) services; Part 2: Off-hook data transmission". |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] IETF RFC 4825: "The Extensible Markup Language (XML) Configuration Access Protocol (XCAP)". [i.2] IEEE 1003.1-2004: "Standard for information technology - portable operating system interface (POSIX). Shell and utilities". ETSI ETSI TS 183 043 V3.4.1 (2011-04) 17 [i.3] IETF RFC 4488: "Suppression of Session Initiation Protocol (SIP) REFER Method Implicit Subscription". [i.4] IETF RFC 3515: "The Session Initiation Protocol (SIP) REFER Method". [i.5] ETSI TR 183 072: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Emulation Services for PSTN Modem Calls". [i.6] ETSI EG 201 973-2: "Access and Terminals (AT); Public Switched Telephone Network; Support of legacy terminals by Broadband IP networks and equipment; Part 2: Analogue PSTN terminals". [i.7] IETF RFC 3551: "RTP Profile for Audio and Video Conferences with Minimal Control". [i.8] IETF RFC 3362: "Real-time Facsimile (T.38) - image/t38 MIME Sub-type Registration". |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 3 Definitions and abbreviations | |
f35b69ccd2199c2dc10834594190c0f0 | 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 NOTE: An access gateway can take the form of a Media Gateway (A-MGW) or a Voice over IP Gateway (A-VGW). loose coupling: on-hook and flash-hook are analyzed in the AGCF/VGW; much like a simulation endpoint would operate Media GateWay (MGW): gateway device acting at the media/transport plane, providing the functions of an MGF as defined in ES 282 001 [1] NOTE 1: A MGW may additionally relay signalling traffic, in which case it also provides the functions of an SGF as defined in ES 282 001 [1]. NOTE 2: In the present document, Media Gateway refers both to Access Gateways and to Residential Gateways, to form an A-MGW, or an R-MGW, respectively. Media Gateway Controller (MGC): See ITU-T Recommendation H.248.1 [22]. T.38/G3: Is a T.38 endpoint that supports G3FE, but excludes the ITU-T Recommendation T.30 [56] V.34 procedures. NOTE: Also known as "T.38/V.17 G3" or "T.38/non-V.34 G3" endpoint type. T.38/V.34G3: Is a T.38 endpoint that supports G3FE and includes the ITU-T Recommendation T.30 [56] V.34 half-duplex procedures. NOTE: Also known as "Super G3" (SG3) T.38 endpoint type. residential gateway: gateway device that interworks a small number of analogue lines/ISDN accesses NOTE: A residential gateway typically contains one or two analogue lines or ISDN basic accesses and is located at the customer premises. A residential gateway can take the form of a Media Gateway (R-MGW) or a Voice over IP Gateway (R-VGW). tight coupling: on-hook and flash-hook are interpreted by the AS Voice over IP GateWay (VGW): SIP-based gateway device that implements both a media gateway function and a media gateway controller function as defined in RFC 2805 [21] and supports the provision of voice based services to analogue lines/ISDN accesses ETSI ETSI TS 183 043 V3.4.1 (2011-04) 18 NOTE: A Voice over IP Gateways (VGW) whether acting as an Access Voice over IP Gateway (A-VGW) or as a Residential Voice of IP Gateway (R-VGW) plays the role of a PES Endpoint (i.e. acting as an IMS UE with regards to the P-CSCF). |
f35b69ccd2199c2dc10834594190c0f0 | 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 AVP Audio Video Profile (RTP) B2BUA Back-to-Back User Agent BGCF Breakout Gateway Control Function CCBS Call Completion on Busy Subscriber CCNR Call Completion on No Reply CD Call Deflection CDP Charging Determination Point CFB Call Forwarding on Busy CFNR Call Forwarding on No Reply CFU Call Forwarding Unconditional CGP Charging Generation Point CLF Connectivity session Location and repository Function CLIP Calling Line Identification Presentation CLIR Calling Line Identification Restriction CN Core Network COLP COnnected Line identification Presentation COLR COnnected Line identification Restriction CONF CONFerence CPG Call ProGress CSCF Call Session Control Function CUG Closed User Group CW Call Waiting DC Direct Current ECT Explicit Call Transfer FM Feature Manager FoIP Facsimile over IP (T.38) FQDN Fully Qualified Domain Name G3FE Group 3 Facsimile Equipment GoS Grade of Service GPL Generic Parameter List GVNS Global Virtual Network Service HOLD call HOLD IAF Internet-Aware Fax (T.38 device) IBCF Interconnection Border Control Function I-CSCF Interrogating CSCF IM IP Multimedia I-MGCF Incoming - MGCF IMS IP Multimedia core network Subsystem IP Internet Protocol ISDN Integrated Services Digital Network MCID Malicious Call Identification MEGACO MEdia GAteway COntrol protocol MGC Media Gateway Controller MGCF Media Gateway Control Function MGF Media Gateway Function MGW Media GateWay MLPP Multi-Level Precedence and Pre-emption MRF Multimedia Resource Function ETSI ETSI TS 183 043 V3.4.1 (2011-04) 19 MRFC Multimedia Resource Function Controller MRFP Multimedia Resource Function Processor MWI Message Waiting Indicator NCL Negotiated Configuration (Codec) List NGN Next Generation Network NSS Narrowband Signalling Syntax O-MGCF Outgoing - MGCF P-CSCF Proxy - CSCF PCL Preferred Configuration (Codec) List PES PSTN Emulation Subsystem PSTN Public Switched Telephone Network REV REVerse Charging RFC Request For Comments RTP Real-time Transport Protocol S-CSCF Serving CSCF SDP Session Description Protocol SGF Signalling Gateway Function SIP Session Initiation Protocol SOC Switch Order Command SUB SUBaddressing TAS Terminal Alerting Signal TP Terminal Portability UA User Agent UE User Equipment UPSF User Profile Server Function URI Uniform Resource Identifier UUS User-to-User Signalling VBD VoiceBand Data VBDoIP VoiceBand Data over IP (V.152) VGW Voice over IP GateWay VMS Voice Mail System XCAP XML Configuration Access Protocol XML eXtensible Markup Language 4 IMS-based PSTN Emulation Subsystem (PES) overview |
f35b69ccd2199c2dc10834594190c0f0 | 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 architecture assumes that the logic of the service to be emulated resides in one or more application servers playing the role of a PES application server. Analogue/ISDN terminals are connected to residential gateways or access gateways using standard analogue/ISDN interfaces. The protocol running on interfaces between these gateways and the PES is either the gateway control protocol according to ITU-T Recommendation H.248.1 [22] (P1 reference point) or the session initiation protocol (SIP) according to RFC 3261 [38] (Gm reference point), depending on the type of gateway: • H.248-based voice over IP media gateway (MGW); or • SIP-based voice over IP gateway (VGW). Media gateways incorporate the Media Gateway Functional (MGF) entity identified in ES 282 001 [1] and are controlled by an Access Gateway Control Function (AGCF), at the P1 reference point. Media gateways supporting ISDN accesses shall also incorporate a Signalling Gateway Function (SGF) as defined in ES 282 001 [1]. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 20 Further details on the architecture are available in TS 182 012 [3]. Annex C illustrates the use of the PES for implementing usual PSTN services identified in EG 201 973-2 [i.6]. Annex F specifies the interworking of analogue terminals using overlap dialling with SIP overlap signalling. |
f35b69ccd2199c2dc10834594190c0f0 | 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 public user identities in a local data base. |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 4.3 AGCF and VGW session and registration processing model | |
f35b69ccd2199c2dc10834594190c0f0 | 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 respectively). A functional modelling of the VGW contains an entity similar to H.248 Media Gateway Controller, a Feature Manager, a SIP UA, and MGW functionality. The VGW interfaces to the P-CSCF using the Gm reference point. NOTE: The internal architecture of functional entities is not standardized. Any internal interfaces are hidden and not testable. The SIP UA functionality provides the interface to the other components of the IMS-based architecture. It is involved in registration and session processing as well as in event subscription/notification procedures with application servers. The MGC functionality enable the session processing functionality to interface with existing line signalling such as analogue signalling or DSS1. Session and registration processing in the AGCF or VGW involves two halves: H.248 based MGC processing and SIP User Agent (UA) processing (see figure 1). MGC processing focuses on the interactions with the media gateway functions, while SIP UA processing focuses on the interactions with the IMS components. The Feature Manager (FM) coordinates the two processing activities. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 21 MGC SIP UA MGF MGF VGW AGCF RTP FM SIP UA FM MGC S-CSCF S-CSCF AS AS P-CSCF Figure 1: AGCF/VGW session processing model |
f35b69ccd2199c2dc10834594190c0f0 | 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 primitive is used by the MGC in the PES access point or PES endpoint for reporting the ServiceChange event to the Feature Manager. • Register-Request: This primitive is used by the Feature Manager for requesting the SIP User Agent to initiate appropriate SIP registration procedures on behalf of emulation users. • Deregister-Request: This primitive is used by the Feature Manager for requesting the SIP User Agent to initiate appropriate SIP deregistration procedures on behalf of emulation users. • Session-Attempt: This primitive is used to notify the Feature Manager of an outgoing call attempt. • Setup-Request: This primitive is used to request establishment of a session. • Setup-Response: This primitive is used to confirm the establishment of a session. • Session-Update: This primitive is used to update a session description. • Session-Progress: This primitive is used to report intermediate events during session establishment. • Session-Release-Request: This primitive is used to request the release of a session. • Session-Release-Confirm: This primitive is used to confirm release of a session. • Session-Release-Suspend: This primitive is used to suspend a session release procedure. • Session-Resume: This primitive is used to indicate that a session in the release phase is to be resumed. • Feature-Request: This primitive is used to report the occurrence of a service feature activation request from the user. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 22 • Charging-Indication: This primitive is used to report the occurrence of a charging event. • Service-Notification: This primitive is used to report the occurrence of a service notification. The Feature Manager processes the above internal events received from the MGC side and request the SIP UA to generate the appropriate SIP messages based on the mapping described in table 1. Table 1: Mapping from MGC side to SIP UA side Internal primitive SIP message Setup Request INVITE Session Progress (alerting) 180 Ringing Setup Response (no Answer) 480 (Temporary Not Available) Setup Response (answer) 200 OK (INVITE) Setup Response (busy) 486 Busy Here Setup Response (failure indication) 4XX or 6XX response depending on the actual failure Feature Request re-INVITE / INVITE Session Release Request BYE or CANCEL (note) Session Release Confirm 200K (BYE) or 200 OK (CANCEL) (note) NOTE: This mapping applies when the CANCEL requests cancels a pending INVITE request. The Feature Manager processes SIP messages received from the SIP UA side and transmit appropriate internal primitives to the MGC side, based on the mapping described in table 2. Exceptions to the above mapping applicable to calls originating from an analogue line are specified in the following clauses. Table 2: Mapping from SIP UA side to MGC side SIP message Internal primitive INVITE Setup Request 183 Session Progress Session Progress 180 Ringing Session Progress(alerting) 200 OK Setup Response (answer) 603 (Decline), 408 (Request Timeout), 480 (Temporary Not Available) Setup Response (no answer) Other 4xx, 5xx, 6xx Setup Response (failure indication) 486 (Busy Here), 600 (Busy Everywhere) Setup Response (busy) re-INVITE with SDP, UPDATE Session Update (SDP) REFER Without "m" parameter contained in the Request URI: Session Update (refer). Request URI contains the "m" parameter: Setup-Request (refer) INFO (charging) or NOTIFY (charging) Charging Indication NOTIFY (other) Service Notification BYE or CANCEL (note) Session Release Request 200 OK (BYE) or 200 OK (CANCEL) (note) Session Release Confirm NOTE: This mapping applies when the CANCEL requests cancels a pending INVITE request. In case of ISDN access, the feature manager procedures shall conform to TS 183 036 [40]. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 23 |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 5 Protocol using SIP and SIP events for PES | |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 5.1 Introduction | This clause identifies the functional entities of the IMS-based PES architecture [3] that play a specific role in the implementation of PES services with regards to SIP processing. |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 5.2 Functional Entities | |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 5.2.1 User Equipment (UE) | Conventional IMS UEs do not exist in PES. In PES, the User Equipment comprises one or more analogue/ISDN terminals and may include the residential gateway to which they are connected. This residential gateway may be an H.248-controlled media gateway or a Voice over IP Gateway (VGW). Voice over IP Gateways (VGW) appear as conventional IMS UEs with regards to the P-CSCF, i.e. they play the role of a SIP user agent from SIP perspective. Analogue/ISDN terminals are not visible to PES network entities. NOTE: Analogue/ISDN terminals - "user equipment" - can also be connected to PES via an Access Gateway. For the purpose of the PES, a residential VGW, in line with the behaviour of all VGWs, shall implement the role of a PES endpoint as described in clause 5.3.1. |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 5.2.2 Access Gateway Control Function (AGCF) | For the purpose of the PES, the AGCF shall implement the role of the PES access point as described in clause 5.3.2. The AGCF is part of the trust domain. The AGCF entity encompasses the functionality of an H.248 Media Gateway Controller (MGC) as defined in ITU-T Recommendation H.248.1 [22] and of a SIP User Agent as defined in RFC 3261 [38]. Within the AGCF, the MGC and SIP UA components are coordinated by a Feature Manager entity whose logical behaviour is described in annex B. The AGCF shall appear to other CSCFs as if it were a P-CSCF. |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 5.2.3 Application Server (AS) | For the purpose of the PES, the AS shall implement the role of a PES application server, as described in clause 5.3.3. NOTE: The PES architecture does not require that all application servers involved in sessions initiated/addressed by/to PES users adhere to the procedures prescribed for the PES application server role. Any application server that conforms to TS 182 006 [2] may be involved in such sessions. |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 5.2.4 Media Resource Function Controller (MRFC) | For the purpose of the PES, an MRFC shall implement the role of the PES announcement server as described in clause 5.3.4. |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 5.2.5 Media Gateway Controller Function (MGCF) | For the purpose of the PES, the MGCF shall implement the role of a PES interworking application as described in clause 5.3.5. |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 5.2.6 Interconnection Border Control Function (IBCF) | For the purpose of the PES, the IBCF shall implement the role of a PES Interconnection Application as described in clause 5.3.6. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 24 |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 5.2.7 Voice over IP gateway (VGW) acting as Access Gateway | For the purpose of the PES, an access VGW, in line with the behaviour of all VGWs, shall implement the role of the PES end point as described in clause 5.3.1. The VGW entity encompasses the functionality of a Media Gateway Controller (MGC), Media Gateway (MG) and a SIP User Agent as defined in RFC 3261 [38]. Within the VGW, the MGC, MGW and SIP UA components are coordinated by a Feature Manager entity whose logical behaviour is described in annex B. NOTE: The internal interfaces of the VGW are not standardized or testable. |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 5.3 Role | |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 5.3.1 PES Endpoint | |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 5.3.1.1 General | In addition to the procedures specified in the rest of clause 5.3.1, the PES endpoint shall support the procedures specified in TS 124 229 [4] and TS 124 628 [6] appropriate to an IMS UE. |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 5.3.1.2 Subscription for profile delivery | The PES Endpoint shall subscribe to the "ua-profile" event defined in [15] and support the Profile document defined in annex A of the present document and optionally to the "message-summary" event defined in RFC 3842 [18]. The subscription may be implicit or explicit. If explicit subscription is required, the identity of the AS acting as the profile delivery server where the subscription request shall be sent may be provisioned in the functional entity in which the PES endpoint is implemented. Alternatively, the user profile may contain an appropriate Initial Filter Criteria on SUBSCRIBE messages that ensure that such requests are sent to the AS acting as the profile delivery server. On receipt of a NOTIFY request reporting the "ua-profile" event and including an XML document with a Dial Tone Management element, the PES end point shall set the current dial tone to the value indicated by the dial-tone-pattern element received in the present document. On receipt of a NOTIFY request reporting the "message-summary" event with a "Messages-Waiting" field set to "yes", the PES end point shall: • Save the current dial tone value and set the current dial tone to the message waiting tone. • Send a Message Waiting Indicator message (see ES 200 659-3 [10]) to the calling user. If the "message-summary" event is received with a "Messages-Waiting" field set to "no", the PES end point shall restore the previous current dial tone. The contents of the SUBSCRIBE request shall be as follows: • The value of the Request-URI shall be set to a provisioned value or to a public user identity associated to the line/access to which the profile applies. • The From and To header shall be set to the public user identity associated to the line/access to which the profile applies. • The Accept header shall include the "application/simserv+xml". • The Event header shall be set to the "ua-profile" event package. • The Event parameters shall be set as follows: - The "profile-type" parameter shall be set to "user". ETSI ETSI TS 183 043 V3.4.1 (2011-04) 25 NOTE 1: The public user identity contained in the Request-URI and in the From and To header fields may be built from the line or access identifier (e.g. line-identifier@pes.operator.com) or be a directory number obtained by the PES Endpoint through provisioning or at registration in case of line-based registration. The "vendor", "model" and "version" parameter values shall be set to values specified by the implementer of the functional entity in which the PES endpoint is implemented, as specified in [15]. NOTE 2: When implicit subscription is used, the PES endpoint should also be prepared to accept "unsolicited" SIP NOTIFY requests with the "message-summary" event. |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 5.3.1.3 Registration procedures | The allocation of private and public user identities is left to each operator to decide. Two approaches are identified: • Group-based registration: One private user identity is assigned to a group of subscriber. A temporary public user identity is associated with this private user identity. Real public user identities representing the subscribers connected to the analogue or ISDN ports of the VGW are registered using implicit registration procedures defined in TS 124 229 [4]. • Line-based registration: A private user identity and one more public user identities are associated with each analogue port/ISDN access connected to the VGW. The two approaches are not mutually exclusive. Depending on the registration method used, the To and From headers in the REGISTER request shall be set to a SIP URI that contains the temporary public user identity associated with the group to be registered or a temporary public user identity associated with the line/access to be registered or a permanent public user identity (i.e. directory number) associated with the line/access to be registered. NOTE: The temporary public user identity may be provisioned on the VGW or in case of line based registration may be built from the line or access identifier (e.g. line-identifier@pes.operator.com). |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 5.3.1.4 Charging procedures | A PES Endpoint supporting advice of charge services shall support the INFO method and shall accept MIME bodies of type "application/vnd.etsi.aoc+xml" (see annex E), indicating the versions of the AOC XML Schema it supports. If the PES Endpoint receives an INFO request including a body with AOC information, then the Content-Type header field shall include "application/vnd.etsi.aoc+xml", the MIME type associated with AOC information (see annex E), and the "sv" or "schemaversion" parameter's value shall be set to the versions of AOC XML Schema that can be used to validate the AOC information XML body (part). One of the versions - of the MIME type associated with AOC information (see clause 9.1) - indicated shall correspond with a value of the version attribute of the <schema> XML element of an AOC XML Schema (see annex E). If the "sv" and "schemaversion" parameter are absent, the PES Endpoint shall assume that version 1 of the XML Schema for the AOC information XML body is supported. If both the "sv" and "schemaversion" parameters are present, then the PES Endpoint shall use the "sv" parameter. In multiple call leg scenarios like three way conversation or conference calls the PES Endpoint shall process charging information received from the PES Application server as described in clause 5.3.3.6: • The charging information shall be assumed to be received for each call leg separately from the PES Application Server. The PES Endpoint has to combine the AOC information received from the PES Application Server. • As a network operator option the charging information received may be assumed as a combined representation applying to all call legs. The PES Endpoint simply applies the last received charging information to the served user. |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 5.3.1.5 Outgoing Call | |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 5.3.1.5.1 General | Calls initiated by a PES user via a PES end point shall operate following the UE call origination procedures defined in TS 124 229 [4]. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 26 When the role of the PES end point is played by an A-VGW connecting lines sitting at different locations, the PES end point should include a P-Access-Network-Info header with a dsl-location parameter set to a provisioned value associated to the calling line. When the "priority-line" flag included in the user profile is set to "enabled", the PES end point overrides any active overload control procedure that may apply to the call. |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 5.3.1.5.2 Procedures for analogue lines | On receipt of a non-empty Setup-Request the PES Endpoint shall send an INVITE request with the call destination in the Request-URI, an SDP Offer for a voice call. The INVITE shall include a P-Preferred-Identity header field set to the default identity associated with the analogue termination where the off-hook event was detected. If the P-Preferred-Identity is not sent then the PES Endpoint shall ensure that the From header contains the equivalent identity. If line-based registration has been used this default identity is the first one received in the P-Associated-URI header. If group-based registration has been used, this default identity is derived from the analogue termination identifier through a provisioned mapping table or by creating a URI from the analogue termination identifier (e.g. termination-id@pes.operator.com). In the later case, it is assumed that the PES AS will replace the contents of the P-Asserted-Identity with a meaningful public user identity (i.e. a Directory number). On receipt of an empty Setup-Request (i.e. without explicit destination information) the PES Endpoint shall build and send an INVITE Request as described above except that the Request-URI shall be set to a provisioned value (e.g. nodial@pes.operator.com). It is up to the PES Application Server to reject the call by sending back an appropriate response code or to substitute the Request-URI with a subscriber-specific default value before forwarding the INVITE requests towards a destination. |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 5.3.1.5.3 Procedures for ISDN access | The procedures specified TS 183 036 [40] apply. If line-based registration is used, the PES Endpoint shall set the P-Preferred-Identity header according to the calling party number received from the ISDN interface, as specified in TS 183 036 [40]. If group-based registration is used the PES Endpoint shall set the P-Preferred-Identity header to the default identity associated with the ISDN access where the call originates from. This default identity is either a directory number derived from the ISDN access identifier through a provisioned mapping table or a URI created from the ISDN access identifier (e.g. isdn-access-id@pes.operator.com). In the later case, it is assumed that the PES AS will replace the contents of the P-Asserted-Identity with a meaningful public user identity (i.e. a Directory number). NOTE: When the P-Preferred-Identity is set to an identity representing the ISDN access, the actual end user identity is still available in the From header as specified in TS 183 036 [40]. When performing interworking with the DSS.1 protocol, as specified in TS 183 036 [40], the PES end point shall indicate support of the application/vnd.etsi.pstn+xml MIME type. |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 5.3.1.5.4 Use of Overlap Signalling (Optional) | If Overlap Signalling is supported between the PES Endpoint and the originating PES Application Server the Overlap Signalling method used, either the Multiples INVITES method or the IN-Dialog method as described within annex F is dependent on national or network operator option. For ISDN Access the procedures specified in TS 183 036 [40] apply. |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 5.3.1.6 Terminating Call | |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 5.3.1.6.1 General | Calls to a PES user via a PES end point shall operate following the UE call termination procedures defined in TS 124 229 [4]. The contents of the To header field is used to fetch the termination to which the call shall be delivered. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 27 If an "m" parameter is received in an INVITE request containing the values "BS or NR", this indication for the Call Completion recall may be used to inform the user about this event. This indication may be used to select a ring pattern conforming to a "distinctive" ring signal. |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 5.3.1.6.2 Use of Overlap Signalling (Optional) | If Overlap Signalling is supported between the PES Endpoint and the terminating PES Application Server the Overlap Signalling method used, either the Multiples INVITES method or the IN-Dialog method as described within annex F is dependent on national or network operator option. For ISDN Access the procedures specified in TS 183 036 [40] apply. |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 5.3.1.6.3 Receipt of a REFER request outside a session | If a REFER is received outside a dialogue, this may occur in case of a recall procedure, the PES Endpoint acts according the method parameter in the Refer-To header with simultaneous consideration of the URI of the Refer-To header. In this context if a "m" parameter is received containing the values "BS or NR", this indication for the Call Completion recall may be used to inform the user about this event. This indication may be used to select a ring pattern conforming to a "distinctive" ring signal. |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 5.3.1.7 Supplementary services configuration | |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 5.3.1.7.1 Analogue lines | Analogue subscribers can control their supplementary services using service code commands as defined in ETS 300 738 [12] included in the user part of the Request-URI of an INVITE message. Further details are provided in annex C. |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 5.3.1.7.2 ISDN lines | ISDN subscribers can configure supplementary services using procedures applied at either the Gm reference point or the Ut reference point. In the case of the Ut reference point, HTTP PUT, HTTP GET or HTTP DELETE requests are used in accordance with RFC 4825 [i.1] and the supplementary services application usage specified in TS 124 623 [33]. In case of the Gm reference point two procedures are available: • Use of service code commands as for analogue subscribers, when ISDN stimulus procedures are used by the end user terminal. • Use of the MESSAGE method when ISDN functional procedures are used by the end user terminal. The MESSAGE method is used to convey the service related information to the relevant target. The information to configure a service is embedded in an XML instance document contained in the MESSAGE request as specified in TS 183 036 [40]. The P-Preferred-Identity shall be set as specified in clause 5.3.1.5 for an INVITE request. The To and From headers shall be set to the public user identity associated to the supplementary service action. This public user identity may be built from the line or access identifier (e.g. line-identifier@pes.operator.com) or be a directory number obtained by the PES Endpoint through provisioning or at registration in case of line-based registration. When receiving a MESSAGE request conveying a response to an ISDN supplementary service interrogation procedure (see TS 183 036 [40]), the PES endpoint shall look for the In-Reply-To header field and evaluate its contents to identify the initial MESSAGE request to which it is responding. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 28 |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 5.3.2 PES Access Point | |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 5.3.2.1 General | In addition to the procedures specified in the rest of clause 5.3.2, the behaviour of the PES access point shall be equivalent to the concatenation of the behaviour of a UE and a P-CSCF entity, as defined in TS 124 229 [4] and TS 124 628 [6]. NOTE: The above statement does not require AGCF implementations to execute UE and P-CSCF procedures in sequence. |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 5.3.2.2 Subscription for profile delivery | On receipt of a NOTIFY request reporting the "message-summary" event with a "Messages-Waiting" field set to "yes", the PES access point shall: • Save the current dial tone value and set the current dial tone to the message waiting tone. • Send a Message Waiting Indicator message (see ES 200 659-3 [10]) using the procedures described in clause 7.3.1.5. Other procedures specified in clause 5.3.1.2 apply. |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 5.3.2.3 Registration Procedures | The following IMS parameters are assumed to available in a local data base: • a private user identity; • a public user identity; and • a home network domain name to which SIP REGISTER requests are addressed. The allocation of private and public user identities is left to each operator to decide. Two approaches are identified: • Group-based registration: One private user identity is assigned to a group of subscribers. Groups should not contain subscribers connected to different gateways. A temporary public user identity is associated with this private user identity. Public user identities representing the subscribers connected to the analogue/ISDN ports controlled by the AGCF are registered using implicit registration procedures defined in TS 124 229 [4]. NOTE 1: The list of implicitly registered identities is provisioned on the UPSF and transmitted to the assigned S-CSCF during registration. This list may be in the form of one or more individual Tel URIs or SIP URIs with a user=phone qualifier and/or one or more wildcarded Public User Identities. • Line-based registration: A private user identity and one or more public user identities are associated with each analogue port/ ISDN access connected to the MGWs controlled by the AGCF. A combination of the two approaches may also be used. The PES access point populates REGISTER messages as follows: a) an Authorization header, with the username field, set to the value of the private user identity associated with the subscriber or subscriber group to be registered; b) a From header set to the SIP URI that contains the temporary public user identity associated with the group to be registered or the public user identity associated with the subscriber to be registered; c) a To header set to the SIP URI that contains the temporary public user identity associated with the group to be registered or the public user identity associated with the subscriber to be registered; NOTE 2: The temporary public user identity may be provisioned on the AGCF or in case of line based registration may be built from the line or access identifier (e.g. line-identifier@pes.operator.com). d) a Contact header set to include SIP URI(s) containing its own IP address in the hostport parameter or FQDN; ETSI ETSI TS 183 043 V3.4.1 (2011-04) 29 e) a Via header set to include the IP address or FQDN of the AGCF in the sent-by field; f) an Expires header, or the expires parameter within the Contact header, set to the value of 600 000 seconds as the value desired for the duration of the registration; NOTE 3: A greater value may be used as an operator's option when registration applies to access gateways. g) a Request-URI set to the SIP URI of the domain name of the home network associated with the group to be registered; h) the Supported header containing the option tag "path"; i) a Path header including an entry containing: - the SIP URI identifying the AGCF; - an indication that requests routed in this direction of the path (i.e. from the S-CSCF to the AGCF) are expected to be treated as for the terminating case. This indication may e.g. be in a parameter in the URI, a character string in the user part of the URI, or be a port number in the URI. j) a Require header containing the option tag "path"; k) a P-Charging-Vector header with the icid parameter populated as specified in ES 282 010 [28]; l) the P-Access-Network-Info header set as specified for the DSL access network technology; and m) a P-Visited-Network-ID header field, with the value of a pre-provisioned string that identifies the network where the AGCF resides. When group registration applies, the content of the P-Associated-URI header received in the response to the REGISTER request is ignored. When the PES Access Point controls an A-MGW, the dsl-location parameter within the P-Access-Network-Info header field is set to a provisioned value associated to the private user identity. When the PES Access Point controls an R-MGW, the dsl-location parameter is set to a value retrieved from the NASS using the protocol defined in ES 283 035 [43], as described in TS 124 229 [4]. NOTE 4: If multiple public user identities are associated to the gateway termination, a default user identity is used. The default user identity is provisioned on the AGCF on a per-line basis within each registration group. |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 5.3.2.4 Originating Call Control procedures | |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 5.3.2.4.1 General | Calls initiated by a PES user via a PES access point shall operate following the concatenation of UE call origination and P-CSCF procedures as defined in TS 124 229 [4]. When the PES Access Point controls an A-MGW, the dsl-location parameter within the P-Access-Network-Info header field is set to a provisioned value associated to the line or to the media gateway it is connected to. When the PES Access Point controls an R-MGW, the dsl-location parameter is set to the value retrieved from the NASS during registration as described in TS 124 229 [4]. If this information is no longer available, the PES Access Point may query the CLF on a per-call basis. When the "priority-line" flag included in the user profile is set to "enabled", then the PES Access Point overrides any active overload control procedure that may apply to the call. |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 5.3.2.4.2 Procedures for analogue lines | On receipt of a non-empty Setup-Request the PES access point shall send an INVITE request with the call destination in the Request-URI, an SDP Offer set according to the information received from the MGF and a P-Asserted-Identity header field set according to the default identity associated with the analogue termination where the off-hook event was detected. If line-based registration has been used this default identity is the first one received in the P-Associated-URI header. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 30 If group-based registration has been used, this default identity is derived from the analogue termination identifier through a provisioned mapping table or by creating a URI from the analogue termination identifier (e.g. termination-id@pes.operator.com). In the later case, it is assumed that the PES AS will replace the contents of the P-Asserted-Identity with a meaningful public user identity (i.e. a Directory number). On receipt of an empty Setup-Request (i.e. without explicit destination information) the PES access point shall build and send an INVITE Request as described above except that the Request-URI shall be set to a provisioned value (e.g. nodial@pes.operator.com). It is up to the PES Application Server to reject the call by sending back an appropriate response code or to substitute the Request-URI with a subscriber-specific default value before forwarding the INVITE requests towards a destination. |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 5.3.2.4.3 Procedures for ISDN access | The procedures specified TS 183 036 [40] apply. If line-based registration is used, the PES Access Point shall set the P-Asserted-Identity header according to the calling party number received from the ISDN interface, as specified in TS 183 036 [40]. The PES Access Point shallverify that this identity is included in the P-Associated-URI header and otherwise overrides it with the first URI received in the P-Associated-URI. If group-based registration is used the PES Access Point should set the P-Asserted-Identity header to the default identity associated with the ISDN access where the call originates from. This default identity is either a directory number derived from the ISDN access identifier through a provisioned mapping table or a URI created from the ISDN access identifier (e.g. isdn-access-id@pes.operator.com). In the later case, it is assumed that the PES AS will replace the contents of the P-Asserted-Identity with a meaningful public user identity (i.e. a Directory number). When performing interworking with the DSS.1 protocol, as specified in TS 183 036 [40], the PES access point shall indicate support of the application/vnd.etsi.pstn+xml MIME type. |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 5.3.2.4.4 Use of Overlap Signalling (Optional) | If Overlap Signalling is supported between the PES Endpoint and the originating PES Application Server the Overlap Signalling method used, either the Multiples INVITES method or the IN-Dialog method as described within annex F is dependent on national or network operator option. For ISDN Access the procedures specified in TS 183 036 [40] apply. |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 5.3.2.5 Terminating Call Control procedures | |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 5.3.2.5.1 General | Terminating calls received by a PES access point shall operate following the UE call termination procedures defined in TS 124 229 [4]. The contents of the To header field is used to fetch the termination to which the call shall be delivered. When the PES Access Point controls an A-MGW, the dsl-location parameter within the P-Access-Network-Info header field is set to a provisioned value associated to the line or to the media gateway it is connected to. When the PES Access Point controls an R-MGW, the dsl-location parameter is set to the value retrieved from the NASS during registration as described in TS 124 229 [4]. If this information is no longer available, the PES Access Point may query the CLF on a per-call basis. When performing interworking with the DSS.1 protocol, as specified in TS 183 036 [40], the PES access point shall indicate support of the application/vnd.etsi.pstn+xml MIME type. When the "priority-line" flag included in the user profile obtained via Profile delivery XML schema is set to "enabled", then the PES Access Point overrides any active overload control procedure that may apply to the call. If an "m" parameter is received in an INVITE request containing the values "BS or NR", this indication for the Call Completion recall may be used to inform the user about this event. This indication may be used to select a ring pattern conforming to a "distinctive" ring signal. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 31 |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 5.3.2.5.2 Use of Overlap Signalling (Optional) | If Overlap Signalling is supported between the PES Access Point and the terminating PES Application Server the Overlap Signalling method used, either the Multiples INVITES method or the IN-Dialog method as described within annex F is dependent on national or network operator option. For ISDN Access the procedures specified in TS 183 036 [40] apply. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.