hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 9.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 9.3.2. The AGCF entity encompasses the functionality of a Media Gateway Controller (MGC) and of a SIP User Agent. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 60 |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 9.2.3 Voice over IP gateway (VGW) | For the purpose of the PES, the VGW shall implement the role of the PES endpoint as described in clause 9.3.1. The VGW entity encompasses the functionality of a Media Gateway Controller (MGC), Media Gateway (MG) and a SIP User Agent. |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 9.2.4 Media Gateway Function (MGF) | For the purpose of the PES, the MGF shall implement the role of the PES media gateway as described in clause 9.3.3. |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 9.3 Roles | |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 9.3.1 PES Endpoint | |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 9.3.1.1 General | The external behaviour of a PES Endpoint is equivalent to the combined behaviour of a PES Access Point and a PES Media Gateway. |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 9.3.1.2 Registration | Registration can be performed on a group basis or on a per line/access basis. This event is passed to the Feature Manager. NOTE: A group may consist of all lines connected to a PES Endpoint or to a subset. When the group basis registration mechanism applies, upon restart or shutdown of the system the PES endpoint shall send a Service-Change primitive to inform the Feature Manager. Change of the status of a physical line within one group shall not cause the PES endpoint to notify the Feature Manager. When the per line basis registration mechanism applies, the PES endpoint shall send a Service-Change primitive to inform the Feature Manager when a physical line is taken out of service or is restored or is added to the system. |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 9.3.1.3 Basic Session control procedures for analogue lines | |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 9.3.1.3.1 Originating side procedures | 9.3.1.3.1.1 Call Initiation Step 0 (Idle) Upon detection of the off-hook event the PES endpoint shall: • Derive the user identity associated with the analogue line where the event was detected. • Report the occurrence of the off-hook event to the Feature Manager using a Session-Attempt primitive. • If the subscriber profile (see annex A) contains a no-dialling-behaviour = immediateCallSetup indication, - send an empty Setup Request primitive to the Feature Manager, - start monitoring the on-hook event, and - proceed to step 2, waiting for either on-hook or an event from the Feature Manager. • Otherwise interact with the Feature Manager to determine which dial tone pattern shall be applied (see clause 5.3.2.2). ETSI ETSI TS 183 043 V3.4.1 (2011-04) 61 • Apply on the subscriber line the signal that correspond to the selected dial tone (cg/dt or srvt/mwt or xcg/spec) according to the value of the dial-tone-pattern element of the Dial Tone Management document described in annex A. • Start monitoring the on-hook event. • Start collecting digits on the subscriber line, according to the digit map in force and proceed with step 1. Step 1(Outgoing Seizure – prior sending of digits) On receipt of the on-hook event, the PES endpoint shall send a Session-Release-Request primitive to the Feature Manager and complete call clearing procedures as specified in clause 9.3.1.3.1.2. On receipt of a digit, the PES endpoint shall evaluate whether sufficient digits have been collected to form a valid sequence according to the dialling plan in force: • If the accumulated digits do not correspond to a valid number but receipt of additional digits may lead to a valid number, the PES Endpoint shall continue monitoring incoming digits. This step may be repeated several times, until a valid number has been collected or the user has abandoned the call attempt by going back on-hook. • If the accumulated digits do not correspond to a valid number and receipt of additional digits cannot lead to a valid number, the PES Endpoint shall initiate call clearing during off-hook procedure as specified in clause 9.3.1.3.1.3. • If the accumulated digits correspond to a complete number, the PES endpoint shall: - send a Setup-Request primitive to the Feature Manager. SDP information shall be set according to the information received in the response to the Add command; - start monitoring the flash-hook event and continue monitoring the on-hook event. - wait for either of these events and for events from the Feature Manager. Proceed to step 2 on the occurrence of any of these events. • If no digits are received, the PES endpoint shall initiate call clearing during off-hook (clause 9.3.1.3.1.3) unless the subscriber profile (see annex A) contains a no-dialling-behaviour = deferredCallSetup indication. In the latter case the PES endpoint shall: - continue monitoring the on-hook event; - send an empty Setup Request primitive to the Feature Manager; - wait for either the on-hook event or an event from the Feature Manager. Proceed to step 2 on the occurrence of any of these events. Step 2(Outgoing Seizure – after sending of digits) On receipt of the notification of the on-hook event, the PES endpoint shall send a Session-Release-Request primitive to the Feature Manager and complete call clearing procedures during on-hook (clause 9.3.1.3.1.2). On receipt of the notification of the flash-hook event, the PES endpoint shall notify its Feature Manager using a Feature Request primitive. On receipt of a Session Progress primitive from the Feature Manager without alerting indication, the PES endpoint shall: • If the primitive contains an early media indication, modify the media path configuration accordingly so that the calling party can perceive in band information. • If the primitive does not contain an early media indication, ignore the event. • Remain in the same state. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 62 On receipt of a Session Progress primitive from the Feature Manager indicating alerting, the PES endpoint shall: • If the primitive contains an early media indication, modify the media path configuration accordingly so that the calling party can perceive in band information. • If the primitive does not contain an early media indication, generate a ringback tone on the subscriber line. • Proceed with step 3. On receipt of an internal Setup-Response primitive reporting a busy condition, the PES endpoint shallInitiate call clearing during off-hook procedure (clause 9.3.1.3.1.3). NOTE: In this case a busy tone is applied at the start of the clearing procedure. On receipt of an internal Setup-Response primitive reporting that no response has been received from the destination, the PES endpoint shall: • Initiate Call Clearing during off-hook procedure (clause 9.3.1.3.1.3). On receipt of an internal Setup-Response primitive reporting any other failure condition, the PES endpoint shall: • Initiate Call Clearing during off-hook procedure (clause 9.3.1.3.1.3). On receipt of an internal Setup-Response primitive reporting answer from the destination, the PES endpoint shall: • Modify the media path configuration to enable bi-directional traffic. • Store the properties associated to the IP side of the media path for use when sending traffic to the remote side. • As an operator's option request apply polarity reversal on the subscriber line. • Proceed with step 4. Step 3(Outgoing Seizure – provisional response received) On receipt of the on-hook event, the PES endpoint shall send a Session-Release-Request primitive to the Feature Manager and complete call clearing procedures as specified in clause 9.3.1.3.1.2. On receipt of the notification of the flash-hook event, the PES endpoint shall notify the feature manager using a Feature Request primitive. On receipt of an internal Setup-Response primitive reporting that no response has been received from the destination or any other failure, the PES endpoint shall: • Stop the ring back tone if application of this signal had been requested before. • Send a Session-Release-Request primitive to the Feature Manager and complete Call Clearing procedures as specified in clause 9.3.1.3.2.2. On receipt of an internal Setup-Response primitive reporting answer from the destination, the PES endpoint shall: • Modify the media path configuration to enable bi-directional traffic, if not performed previously. • Store the properties associated to the IP side of the media path for use when sending traffic to the remote side. • As an operator's option request the PES media gateway to apply the polarity reversal on the subscriber line. • Proceed with step 4. Step 4 (Outgoing session established) On receipt of an internal Session-Release-Request primitive from the Feature Manager, the PES endpoint shall initiate the call clearing during off-hook procedure (clause 9.3.1.3.1.3). On receipt of an internal Charging-Indication primitive, the PES endpoint shall either: • Generate metering pulses by rules described in clause C.2. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 63 • Build an Advice Of Charge message (see ES 200 659-3 [10]) by rules described in annex D and transmit this message over the subscriber line using the procedures for off-hook data transmission specified in EN 300 659-2 [58]. On receipt of an internal Session-Update primitive, the PES endpoint shall modify the properties of the media path accordingly. On receipt of the on-hook event, the PES endpoint shall send a Session-Release-Request primitive to the Feature Mananger and complete call clearing procedures as specified in clause 9.3.1.3.1.2. On receipt of the notification of the flash-hook event, the PES endpoint shall notify the feature manager. 9.3.1.3.1.2 Call Clearing upon On-Hook On receipt of a Session-Release-Confirm primitive from the Feature Manager the PES endpoint shall: • If polarity reversal was applied on the line when entering the active phase, then apply normal polarity to the line. • Release the analog line. • Proceed with step 0. On receipt of a Session-Release-Suspend primitive from the Feature Manager the PES endpoint shall start monitoring the off-hook event. If the off-hook event is detected, the PES endpoint shall send a Session-Resume primitive to the Feature Manager and re-enter Step 4 of the previous phase. 9.3.1.3.1.3 Call Clearing during Off-Hook Upon entering this step, the PES endpoint shall: • Generate an appropriate announcement or tone (e.g. busy tone, congestion tone etc.) on the subscriber line. • If polarity reversal was applied on the termination in Step 3, then apply normal polarity to the line. • Release all IP resources associated to the session. Upon detection of the on-hook event, the PES endpoint shall: • Release the analog line. • If a Session Release-Request primitive has been previously received from the Feature Manager, then send a Session-Release-Confirm to the Feature Manager. • Proceed with step 0. If the calling party is still off-hook upon end of announcement or tone, generate an off-hook warning tone on the subscriber line after expiry of a network configured timer. Upon termination of the off-hook-warning tone, the PES endpoint may, as a network option, apply reduced power feed to the line after expiry of a network-defined timer. |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 9.3.1.3.2 Terminating side procedures | 9.3.1.3.2.1 Call Initiation Step 0 (IDLE) On receipt of a Setup-Request primitive from the internal SIP UA (via the Feature Manager), the PES endpoint shall: • Check that the required bearer service is compatible with analogue lines, otherwise return a Setup-Response to the Feature Manager, with a reject indication. • Determine which physical line(s) are associated with the target public user identity. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 64 • If no physical line is associated with the called party, the PES endpoint shall send a Setup-Response primitive with a failure indication to the internal SIP UA via the Feature Manager. If a single line is associated to the target public user identity, select this line otherwise if multiple lines are associated to the target public user identity, select one line. • Check the administrative status of the selected line. If the line is out of service, the PES endpoint shall send a setup-response primitive with a failure indication to the internal SIP UA via the Feature Manager or select another line if multiple lines are associated to the called number. If all lines are out of service, the PES endpoint shall send a Setup Response primitive with a failure indication to the internal SIP UA via the Feature Manager. • Check whether the selected line is already engaged in a call. NOTE 1: The algorithm for selecting a line in case multiple lines are associated to the same called number (fixed priority, round-robin, etc.) is outside the scope of the present document. NOTE 2: It is expected that only one line will be associated to a public user identity when the tight-coupling mode is used. If the selected line is not engaged in a call, the PES endpoint shall: • Allocate IP resources, based on the session description information received in the Setup-Request. • Add the physical line representing the called party's line to the newly created context. • Apply ringing to the subscriber line. If information has to be displayed on the terminal, the procedure for on-hook "data transmission during ringing or prior to ringing" as specified in EN 300 659-1 [57] shall be applied and the block of data to be displayed shall be set as specified in annex D. As directed by the AS (with a SIP Alert-Info header in the INVITE request), the PES endpoint may apply a distinctive ringing tone. • Send a Session-Progress (Alerting) primitive to the Feature Manager. • Start a no-answer timer. • Start monitoring the off-hook event • Proceed to step 1. If the selected line is already engaged in a call and multiple lines are associated to the same called number, select an alternative line and repeat the above procedures. If the selected line is already engaged in a call and there is no alternative "in-service" line that can be selected, the PES endpoint shall either: • Send a Setup-Response (busy) primitive to the Feature Manager if an explicit indication that the Call Waiting service is not provisioned to the user has been received as part of the profile delivery procedure or as a network option if the incoming Setup-Request does not contain a MIME body indicating that the terminating user is subscribed to the Call Waiting service as defined in TS 124 615 [44]; or • Initiate a call waiting procedure: - Allocate IP resources, based on the session description information received in the Setup-Request. - Apply the call waiting tone to the subscriber line. If information has to be displayed on the terminal, the procedure for off-hook data transmission as specified in EN 300 659-2 [58] shall be applied and the block of data to be displayed shall be set as specified in annex D. As directed by the AS (with a SIP Alert-Info header in the INVITE request), the PES endpoint may apply a distinctive call waiting tone. - Send a Session-Progress (Alerting) primitive to the Feature Manager, including 'urn:alert:service:call-waiting' to be inserted in the Alert-Info header field of the corresponding SIP message. - Start a call-waiting timer. - Proceed to step 1. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 65 If a Session-Release-Request primitive is received from the internal UA, via the feature manager, the PES endpoint shall: • Release IP resources associated with the call. • Release the analog line. • Send a Session-Release-Confirm primitive to the Feature Manager. Step 1 (Incoming Seizure) If an off-hook event is notified, the PES endpoint shall: • Start monitoring the following events: - the flash-hook event; - the on-hook event. • Report the occurrence of the off-hook event to the Feature Manager. • Proceed to step 2. If the no-answer timer (line free) or call-waiting-timer (line busy) expires, the PES endpoint shall: • Send a Setup-Response (no answer) primitive to the internal UA via the Feature Manager. • Stop the signal sent to the called party (ringing or call waiting signal). • Stop the signal sent to the calling party (ring back tone or the announcement). • Release the analog line, unless it is already engaged in another call. • Send a Session-Release-Request primitive to the Feature Manager and complete call clearing procedures as specified in clause 9.3.1.3.2.2. Step 2 (Incoming Session established) If the flash-hook event is detected, notify the Feature Manager using a Feature Request primitive. On receipt of an internal Session-Update primitive, the PES endpoint shall modify the properties of the media path accordingly. If the on-hook event is detected, the PES endpoint shall send a Session-Release-Request internal primitive to the Feature Manager and complete call clearing procedures as per clause 9.3.1.3.2.2. If a Session-Release-Request primitive is received via the Feature Manager from the internal UA, the PES endpoint shall initiate call clearing during off-hook procedure (clause 9.3.1.3.2.3). 9.3.1.3.2.2 Call Clearing upon On-Hook On receipt of a Session-Release-Confirm primitive from the Feature Manager the PES endpoint shall: • Release IP resources associated with the call. • Release the analog line. • Proceed with step 0. On receipt of a Session-Release-Suspend primitive from the Feature Manager the PES endpoint shall start monitoring the off-hook event. If the off-hook event is detected, the PES endpoint shall send a Session-Resume primitive to the Feature Manager and re-enter Step 2 of the previous phase. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 66 9.3.1.3.2.3 Call Clearing during Off-Hook Upon entering this step, the PES endpoint shall: • Release IP resources associated with the call. • Generate an appropriate announcement or tone (e.g. busy tone, congestion tone etc.) on the subscriber line. On receipt of the on-hook event, the PES endpoint shall: • Release the analog line. • Report the occurrence of the on-hook event to the Feature Manager using a Session-Release-Confirm primitive if a Session-Release-Request had been previously received. • Proceed with step 0. If the called party is still off-hook upon end of the announcement or tone, apply the off-hook warning tone on the subscriber line after a network configured timer. Upon termination of the off-hook-warning tone, the PES endpoint may, as a network option, apply reduced power feed to the line after expiry of a network-defined timer. |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 9.3.1.4 Procedures for fax/modems calls over analogue access | In order to be able to properly handle fax and modem calls, the PES endpoint monitors the fax and modem tones listed in TS 183 002 [5], table 92. Upon detection of a fax or modem tone, the PES Endpoint notifies the Feature Manager if the recognized tone corresponds to a supported fax/modem. Otherwise, the event is discarded. NOTE: Modelling of the Feature Manager behaviour for transitioning between Audio mode and VBD mode requires further studies. Alignment with TS 183 002 [5] requires further studies as well. |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 9.3.1.5 Message Waiting Indication for analogue access | On receipt of a Service Notification internal primitive reporting the "message-summary" event, the PES endpoint shall transmit the message indication to the analog line using on-hook "data transmission not associated with ringing" procedures defined in EN 300 659-1 [57] and the block of data shall be set as specified in annex D. The terminal alerting signal may be provisioned on a per line or global basis. If the line is off-hook, the PES Endpoint shall transmit the message indication only upon detecting that the line changed to on-hook. |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 9.3.2 PES Access Point | The PES Access point controls and is aware of analog signalling events through the PES Media Gateway, using the H.248 protocol as specified in clause 7. |
f35b69ccd2199c2dc10834594190c0f0 | 183 043 | 9.3.3 PES Media Gateway | The PES media gateway shall support the H.248 procedures specified in TS 183 002 [5] appropriate to an MG. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 67 Annex A (normative): XML document structure for Profile Delivery Profile documents are sub-trees of the simservs XML document defined in TS 124 623 [33]. The following schema shall be used to describe XML documents that specify the profile elements applicable to an endpoint. The .xsd file is contained in archive ts_183043v030401p0.zip which accompanies the present document. <?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:ss="http://uri.etsi.org/ngn/params/xml/simservs/xcap" xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://uri.etsi.org/ngn/params/xml/simservs/xcap" elementFormDefault="qualified" attributeFormDefault="unqualified"> <xs:complexType name="simservType"> <xs:attribute default="true" name="active" type="xs:boolean" use="optional" /> <xs:anyAttribute namespace="##any" processContents="lax" /> </xs:complexType> <xs:element name="dial-tone-management" substitutionGroup="ss:absService"> <xs:annotation> <xs:documentation>Dial Tone Management </xs:documentation> </xs:annotation> <xs:complexType> <xs:complexContent> <xs:extension base="ss:simservType"> <xs:sequence> <xs:element name="dial-tone-pattern" default="standard-dial-tone" minOccurs="0"> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="standard-dial-tone"/> <xs:enumeration value="special-condition-tone"/> <xs:enumeration value="message-waiting-tone"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="mcid-service" default="mcid-service-withdrawn" minOccurs="0"> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="mcid-service-provisioned"/> <xs:enumeration value="mcid-service-withdrawn"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="no-dialling-behaviour" default="rejectCall" minOccurs="0"> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="rejectCall"/> <xs:enumeration value="immediateCallSetup"/> <xs:enumeration value="deferredCallSetup"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="hold-service" default="hold-service-provisioned" minOccurs="0"> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="hold-service-provisioned"/> <xs:enumeration value="hold-service-withdrawn"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="toggle-service" default="toggle-service-withdrawn" minOccurs="0"> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="toggle-service-provisioned"/> <xs:enumeration value="toggle-service-withdrawn"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="three-pty-service" default="three-pty-service-withdrawn" minOccurs="0"> ETSI ETSI TS 183 043 V3.4.1 (2011-04) 68 <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="three-pty-service-provisioned"/> <xs:enumeration value="three-pty-service-withdrawn"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="cw-service" default="cw-service-provisioned" minOccurs="0"> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="cw-service-provisioned"/> <xs:enumeration value="cw-service-withdrawn"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="priority-line" default="priority-line-disabled" minOccurs="0"> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="priority-line-enabled"/> <xs:enumeration value="priority-line-disabled"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="on-hook-behaviour-calling-subscriber" minOccurs="0"> <xs:complexType> <xs:sequence> <xs:element name="on-hook-behaviour-calling-subscriber-flag" minOccurs="0"> <xs:simpleType> <!--Default value is network specific --> <xs:restriction base="xs:string"> <xs:enumeration value="release-calling-subscriber"/> <xs:enumeration value="hold-calling-subscriber"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="suspend-timer" type="xs:integer" minOccurs="0"> </xs:element> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="on-hook-behaviour-called-subscriber" minOccurs="0"> <!--Default value is network specific --> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="release-called-subscriber"/> <xs:enumeration value="hold-called-subscriber"/> </xs:restriction> </xs:simpleType> </xs:element> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> </xs:element> </xs:schema> ETSI ETSI TS 183 043 V3.4.1 (2011-04) 69 Annex B (normative): AGCF/VGW Feature Manager B.1 Void B.2 Void B.3 Void B.4 Feature manager behaviour B.4.1 Registration procedures Based on the information received from the MGC and local configuration data (mapping between line identities and IMS identities, authentication parameter, etc.) the Feature Manager requests the SIP UA component to initiate appropriate SIP registration procedures (per line registration, group registration). There may a lot of terminations to register and deregister at the same time from the MGC side. In order to avoid the impact of the flood registration and deregistration on the IMS core network, the Feature Manager may use some mechanism to control the number of registration/deregistration during a specified period of time. B.4.1.1 Group state change procedures On receipt of a ServiceChange internal primitive indicating "restart", the Feature Manager sends one or more Register-Request primitives to the SIP UA. On receipt of a ServiceChange internal primitive indicating "forced" or "graceful", the Feature Manager sends one or more Deregister-Request primitives to the SIP UA. The number of primitives sent to the SIP UA depends on the AGCF/VGW configuration with regards to identity management. The following two cases are identified and lead to different procedures: • One private user identity is assigned to the VGW or AGCF (or each MGF). • A private user identity is associated with each termination. In the first case, the Feature Manager sends a single primitive with the private user identity associated with the VGW or AGCF (or the MGF) and a temporary public user identity. The public user identities will be implicitly registered or deregistered using implicit registration procedures defined in TS 124 229 [4]. In the second case, the Feature Manager sends one primitive for each termination connected to the MGF that caused the service change event. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 70 B.4.1.2 Per line/access state change procedures B.4.1.2.1 User-initiated state change transition to "In service" stat On receipt of a Service-Change internal primitive from the MGC component indicating "Restart", the Feature Manager shall: • Lookup the configured data for the public user identities and the private user identities of the related users. • If the related users have not been registered, use a Register-Request primitive to request the SIP UA to initiate appropriate SIP registration procedures. B.4.1.2.2 User-initiated state change to "Out of service" state On receipt of a Service-Change internal primitive from the MGC component indicating "Graceful" or "Forced", the Feature Manager shall: • Lookup the configured data for the public user identities and the private user identities of the related users. • If the related users have been registered, use a Deregister-Request primitive to request SIP UA to initiate appropriate SIP deregistration procedures. B.4.1.2.3 Exception procedures On receipt of a Service-Change internal primitive from the MGC component indicating that the communication between the AGCF and the MGF has been lost, the Feature Manager shall use the Deregister-Request primitive to request the SIP UA to initiate appropriate SIP deregistration procedures for all the registered users belong to the MGF. In order to avoid the impact of the flood deregistration on the IMS core network, the Feature Manager may use some mechanism to control the number of deregistration during a specified period of time. B.4.2 Flash Hook Management B.4.2.1 Void B.4.2.2 Flash-Hook Management for analogue access B.4.2.2.1 General rules Flash-hook events detected by the line side of the AGCF/VGW are reported to the feature manager using a Feature Request internal primitive. For the processing of flash-hook event notifications two different methods exist: • Loose Coupling Method. • Tight Coupling Method. Among others, the methods determine the degree of autonomous processing in the AGCF/VGW after the notification of the flash-hook event to the PES Application Server. The execution of the service independent feature logic is common for both methods of flash-hook management up to the point in time flash-hook is detected. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 71 Both methods are reflected in separate clauses of clause B.4.2.2 for flash-hook management principles and in annex C for individual supplementary services. The different methods can be characterized as follows: • Loose Coupling: The AGCF/VGW implements service-independent feature logic for dealing with register recall events. By evaluating call context and UA profile information, it can make certain decisions such as whether or not to apply dial tone on register recall, collect digits (SOC or SCC), put a party on hold etc. The AS perceives the AGCF/VGW almost as if it was a regular IMS client accessing PSTN/ISDN simulation services. • Tight Coupling: The AS is assumed to have full control over the service. The AGCF/VGW does not implement any service-independent feature logic for dealing with register recall events and does not require UA profile information. The PES AS takes the decisions on the service behaviour (e.g. whether or not to apply dial tone and collect digits), manipulates call legs as needed and instructs the AGCF/VGW on how to proceed based on appropriate SIP messages. The decision to implement tight coupling or loose coupling is left to the network operator. However, it is important that both the AGCF/VGW and the PES application server are configured the same way. B.4.2.2.2 Loose coupling procedures Processing of a Feature-Request depends on the call configuration. Call Configuration: 1-party In this configuration, an unconfirmed INVITE dialog exists between the SIP UA and another endpoint. On receipt of a Feature Request from the MGC component, unless an explicit indication that the HOLD service is not provisioned to the user has been received as part of the profile delivery procedure, the Feature Manager shall request the MGC component to interact with the media gateway in order to play a dial tone and collect digits. If the digit collection succeeds, the Feature Manager shall request the SIP UA to send an INVITE request to the PES application server, with the collected digits as Request-URI. Otherwise, the events shall be discarded. Call Configuration: Stable 2-party In this configuration, one confirmed INVITE dialog exists between the SIP UA and another endpoint. Processing flash-hook notifications depend on whether MCID can be invoked using this command or not. In networks where MCID is invoked by other means the Feature Manager shall proceed to step 1. In networks, where MCID is invoked using a flash hook event, the Feature Manager shall check whether MCID is provisioned for the served user. If MCID is provisioned, the Feature Manager shall proceed to step 2 otherwise it shall proceed to step 1. 1) On receipt of a flash-hook notification from the MGC component, unless an explicit indication that the HOLD service is not provisioned to the user has been received as part of the profile delivery procedure, the Feature Manager shall: - Request the SIP UA to send a re-INVITE request towards the connected party (B party). The re-INVITE request is built as follows: The Request URI is set to the B party's identity. The SDP description for the active media stream is set to a=sendonly. NOTE 1: This information may be used by an AS to request the sending of an announcement to the B Party. - Request the MGC component to initiate an outgoing call process as if an off-hook event had been received. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 72 2) The handling of MCID in stable 2-party configuration depends on the network configuration. - If the MCID service is provisioned and requires initial flash-hook detection then the Feature Manager on receipt of flash-hook notification from the MGC component shall follow one of the following options: assume direct invocation of MCID; or initiate the collection of a feature code and request the MGC component to interact with the media gateway in order to: - Set the stream mode of the IP media termination to "inactive". - Play a dial tone. - Collect a feature code. - If the collected feature code indicates MCID or if no feature code is required, the Feature Manager shall request the SIP UA to send a re-INVITE request towards the AS. The re-INVITE request is built as follows: the Request URI is set to the served user's identity, and include no Body in the re-INVITE; or as a network operator option a re-INVITE including a XML-MIME with XML mcid body with MCID XML Request schema containing a McidRequestIndicator set to 1. - If the collected feature code does not indicate MCID, the Feature Manager shall ignore the flash-hook notification. Call Configuration: Stable 2-party call with additional held/waiting party In this configuration, a confirmed INVITE dialog exists between the SIP UA and some other endpoint (the "active party", and either an unconfirmed dialog exists with a third endpoint (the "waiting party"), or another confirmed dialog exists with a third party that is on hold ("held party"). On receipt of a flash-hook notification from the MGC component, the Feature Manager shall request the MGC component to interact with the media gateway in order to: • Set the stream mode of the IP media termination to "inactive". • Play a dial tone. • Collect a feature code. The number of digits is provisioned in the AGCF/VGW. The AGCF/VGW shall also send a re-INVITE request on the initial dialogue to hold the associated media stream, as described in TS 124 610 [8]. As a Network operator option the sending of a re-INVITE to set the active party to inactive is delayed until the feature logic verifies that the collected feature code is valid. NOTE 2: This information may be used by an AS to request the sending of an announcement to the B Party. With loose coupling, the AGCF/VGW provides call processing logic to manipulate call legs, much like a simulation endpoint would operate. The Feature Manager analyses the feature code according to a local mapping table. For each feature code, this table indicates the user expected feature: • The served user wishes to be connected to a particular held/waiting party and keep the other party held/waiting. • The served user wishes to be connected to a particular held/waiting party and release the other party. • The served user wishes to establish a 3-party conference with both of the other parties. • The served user wishes invoke the MCID service. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 73 If the feature code received does not match any known feature, the FM ignores the feature code and optionally requests the MGC component to interact with the media gateway in order to play an error tone or an announcement to the served user. As a network option when an additional Flash-Hook command received a new dial tone is played and feature code can be received by the MGC component and processed by the AGCF/VGW. If the feature code received indicates that the served user wishes to be connected to a particular held/waiting party, unless an explicit indication that the Call Toggle service is not provisioned to the user has been received as part of the profile delivery procedure, the Feature Manager shall: • Request the SIP UA to send either: - a 200 OK response to the INVITE request received from the waiting party if the dialogue is not confirmed yet; or - a re-INVITE request if the dialogue with the held party is already confirmed. The Re-INVITE request is built as follows: The Request URI is set to the held party's identity. The SDP description for the active media stream is set to a=sendrecv. • If a AGCF is in use then request the MGC component to interact with the media gateway in order to: - modify the Remote Descriptor of the ephemeral termination according to the SDP information received from the held/waiting party; - set the Stream Mode of the IP media termination to sendrecv; - monitor the flash-hook event on the physical termination. • If a VGW is used then: - modify the IP media termination according to the SDP information received from the held/waiting party; - set the Stream Mode of the IP media termination to sendrecv; - monitor the flash-hook event on the physical termination. If the feature code received indicates that the served user wishes to release the call with the other held/waiting party, the Feature Manager shall: • Request the SIP UA to send a 603 response or a BYE request to the waiting/held party depending on the dialogue state. • Request the MGC component to interact with the media gateway in order to monitor the flash-hook event on the physical termination. If the feature code received indicates that the served user wishes to establish a 3-party conference, unless an explicit indication that the 3PTY service is not provisioned to the user has been received as part of the profile delivery procedure, the Feature Manager shall: • Request the MGC component to interact with the media gateway in order to add a termination to the current context based on SDP information associated with the initial held party (i.e. the party that was already held before the flash-hook has been detected). • Request the SIP UA to send a re-INVITE request towards each of the held/waiting parties. The re-INVITE request is built as follows: - the Request URI is set to the held/waiting party's identity; - the SDP description for the active media stream is set to a=sendrecv. If an AGCF is in use the address and port are set according to the contents of the local descriptor of the termination representing this party on the media gateway. Or if a VGW is in use then the address and port are set according to the SDP description of the IP media termination representing this party. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 74 If the feature code received from the internal MGC component indicates that the served user wishes to invoke MCID, the Feature Manager shall request the SIP UA to send a re-INVITE request towards the AS. The re-INVITE request is built as follows: • The Request URI is set to the served user's identity; and: - include no Body in the re-INVITE; or - as a network operator option a re-INVITE including a XML-MIME with XML mcid body with MCID XML Request schema containing a McidRequestIndicator set to 1. B.4.2.2.3 Tight coupling procedures B.4.2.2.3.1 Introduction With tight coupling procedures, all collected digits are reported to the PES application server and the AS determines the appropriate call processing actions to take. Manipulation of call legs for call waiting and 3-party calls is managed by the AS, so feature logic for these services is not required in the AGCF/VGW. Unlike loose coupling, where a flash-hook notification must be followed by dialled digits in order for the AGCF/VGW to generate an INVITE request, tight coupling procedures specify the reporting of a flash-hook event without additional digits dialled by the user. NOTE: Due to the procedures for profile delivery described in clauses 5.3.1.2 and 5.3.2.2 the dial tone is provisioned in the AGCF/VGW. B.4.2.2.3.2 Flash-Hook Reporting On receipt of a Feature Request from the MGC component, the Feature Manager shall request the SIP UA to create a new dialogue and send an INVITE (flash) request to the Application Server, built as follows: • The Request URI is structured as follows: - A user part containing a unique value that signifies that a flash-hook event was detected (such as flash@pes-scc.operator.com). When hook-flash is reported to the AS, it may, as a network option, instruct the AGCF/VGW to perform digit collection and provision of dial tone (see clause B.4.2.2.3.2A). Alternatively it may instruct another entity under its control such as a Media Resource Function to perform digit collection and provision of dial tone as described in annex G. - A domain name which together with the user part provides sufficient information to the S-CSCF to forward the INVITE request to the appropriate AS, based on Initial Filter Criteria stored in the user profile (see annex C). • A P-Asserted-Identity (AGCF) or a P-Preferred-Identity may be sent (VGW) containing the public identity of the subscriber requesting the service. If the P-Preferred-Identity is not send then the PES Endpoint shall ensure that the From header contains the equivalent identity. • An SDP offer for a voice call. One of the following actions is determined by the Application Server and indicated to the VGW/AGCF by appropriate SIP responses. The list is not assumed to be complete, but covers the most likely responses: • 484 Address Incomplete with XML attachments indicating: - the dial-tone pattern to be applied, if needed for service logic; - a minimum number of digits to be collected. NOTE: The definition of the XML schema for dial-tone pattern and minimum number of digits is for further study. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 75 • 200 OK - if the 200 OK contains a SDP (a=inactive) indicating that no path has to be switched then the flash-hook alone has determined the service, no further action has to be performed by the AGCF/VGW. e.g. for simplified Call Waiting; - if the 200 OK returns a SDP (sendrecv, recvonly,) response then the AGCF/VGW will switch the corresponding media path (e.g. dial-tone may be sent by an MRF and inband digit collection at MRF will happen). • 403 Forbidden - indicates that there is no flash-hook invoked service supported on this line. The AGCF/VGW will not apply dial-tone and suppress any dialled digits. It is a network option how to proceed. For example, whether to revert back to active communication, provide an announcement or perform any other action. • 503 Service Unavailable - indicates that the call request will not be processed (e.g. due to an overload condition in the core network). From the end-user perspective, the flash-hook will just be ignored. It is a network option how to proceed. For example, whether to revert back to active communication, provide an announcement or perform any other action. B.4.2.2.3.2A Digit Collection and Reporting If a 484 Address Incomplete message with XML attachment is received, the AGCF/VGW applies the indicated dial tone and collects the indicated number of digits. The collected digit(s) are reported to the AS as the user part of the Request-URI of a re-INVITE request on that same dialogue in which the flash-hook event was reported. The domain name of the request-URI is the same than for reporting the flash-hook event. Inter-digit timer values are assumed to be provisioned in the AGCF/VGW. If a timer expires before the minimum number of digits is collected the AGCF/VGW sets the user part to "null". If no minimum number of digits is indicated in the XML attachment or no XML attachment is received, a default value of "one" is assumed. If no dial tone is indicated, the AGCF/VGW uses the dial tone pattern received as part of the user profile delivery procedure or a default dial tone if none was received. B.4.2.2.3.3 Behaviour and Functional Distribution In the following the principles of behaviour and functional distribution are described: • Multiple dialogs on A-side: - When a subscriber goes off-hook the AGCF/VGW will create a new dialog. - Release of the dialogue opened for the purpose of sending the feature code is the responsibility of the application server. NOTE: The 199 (Early Dialog Terminated) response code may be used to terminate the dialog. This may be specified in a future Release. • Mid call digit and SOC collection: - The entity collecting the digits shall also generate the dial tone. Those functions can either be performed by the AGCF/VGW or an MRF. • The fact whether a SOC has to be collected or a regular telephone number can be determined in one of the following ways, depending on whether the 484 response is including a min-nr-digits-required parameter or not: - 484 including a min-nr-digits-required parameter: The min-nr-digits-required parameter in the 484 response will indicate the number of digits to be collected. The AGCF/VGW notifies the AS as soon as the indicated number of digits is available. No digit map is required in this case. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 76 - 484 not including a min-nr-digits-required parameter: The AGCF/VGW always sends the first digit irrespective of whether a SOC has to be collected or a regular telephone number has to be dialled. The AS controls subsequent actions by appropriate responses as for instance another 484. • Putting the remote party on-hold: - The AS is assumed to take this decision dependent on service logic and to take the necessary steps triggered by a received flash-hook INVITE. • The following elements of the UA profile document defined in annex A are not needed as a result of using a tight-coupling approach: - Mcid-service - Hold-service - Toggle-service - Three-pty-service - Cw-service • Announcement generation: - Typically the AS can determine whether an announcement has to be played or not. - In cases where the VGW needs to invoke an announcement, then the announcement is requested by a dedicated request URI indicating the announcement type. • AGCF/VGW media gateway control: - For an AGCF the Feature Manager shall request the MGC component to interact with the media gateway in order to modify the H.248 Remote Descriptor and stream mode according to the SDP information received in re-INVITE messages sent by the Application Server. - For a VGW the Feature Manager shall request the MGC component to interact with the media gateway component within the VGW in order to modify the IP media termination according to the SDP information received in re-INVITE messages sent by the Application Server. Release of the dialogue opened for the purpose of sending the feature code is the responsibility of the application server: • Establishment of second call fails for CW or 3-party call: - If the user aborts dialling to user C via flash-hook then the AS should keep the held party and trigger the AGCF/VGW to play the appropriate tone to the user or initiate an announcement via a MRF. - If the call to user C has failed (dialling aborted, busy at user C, unknown destination number) and the user A goes on-hook then the AS should keep the held party and apply re-ringing to user A. - On receipt of a feature code which is unknown or cannot be executed by the AS the AS should re-connect the original call by sending a re-INVITE request to user A with appropriate SDP settings or, as a network option, request an MRF to play an announcement. In the latter case, the subscriber can retry by invoking flash-hook or going on-hook (followed by re-ring). B.4.3 Behaviour of Re-ringing In the following example re-ringing is described: • Re-ringing after Hold/Waiting: - Call Configuration: Stable 2 party call with additional held/waiting party. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 77 - If in the normal situation with one active and one held call, the served user (whether or not he is the called user) goes on-hook, the currently connected call shall be released, and the served user shall be rerung immediately for the held call. The held party continues to be held during the ring back period. When the served user answers before the 'CW No Answer timer' expires a normal two party call is established. B.4.3.1 Loose coupling When the served user goes on hook, clause B.4.4.2.1 or clause B.4.4.3.1 applies. When the active call is cleared, the Feature manager knows that there is still a held session and alerts the served user in order to re-establish this session. When the served user accepts the call, the feature manager shall send a re-INVITE to the held party in order to re-establish the session. B.4.3.2 Tight coupling When the served user goes on hook, clause B.4.4.2.2 or clause B.4.4.3.2 applies. When the active call is cleared, the application server of the served user knows that there is still a held session and sends an INVITE to the served user in order to re-establish this session. B.4.4 On-Hook Management B.4.4.1 General B.4.4.1.1 General rules On-hook events detected by the line side of the AGCF/VGW are reported to the feature manager using a Session- Release-Request internal primitive. The behaviour of the feature manager depends on whether the loose coupling or tight coupling mode is used and whether the primitive is received on behalf of an originating or terminating party. B.4.4.1.2 Interaction with other services When the subscriber goes On-hook and a Re-Ring condition exists, the Call Held service is not applicable. NOTE: The Re-Ring conditions exist when a call is in a "stable 2 party call with additional held/waiting party state" and the subscriber goes On-hook. B.4.4.2 Originating side procedures B.4.4.2.1 Loose coupling procedures On receipt of a Session-Release-Request primitive, the Feature Manager shall determine whether to apply the Call Held service depending on the user profile and the type of call. If no explicit indication is received as part of the profile delivery procedure, the Feature Manager determines whether the Call Held service is provisioned or not, based on a network option. If the Call Held service is provisioned, the type of call is evaluated. The Call Held service should be considered applicable for the following type of calls: • Emergency call (call to a Public Safety Answering Point). • As a network option: Other special numbers (e.g. call to operator). The emergency numbers (and optionally other special numbers) should be provisioned in the VGW/AGCF in order to enable type of call evaluation. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 78 NOTE: An alternative method to identify the type of call maybe providing a called party category in 1xx or 200 OK response. This is not specified in this release. If the Call Held service is applicable, the Feature Manager shall respond to the MGC component of the AGCF/VGW with a Session-Release-Suspend primitive and start a suspend timer. Otherwise, it shall respond with a Session- Release-Confirm primitive and send a Session-Release-Request primitive to the internal SIP UA. The value of the suspend timer may be received as part of the profile delivery procedure. Otherwise a default network specific value is used. If the suspend timer expires, the Feature Manager shall respond to the MGC component of the AGCF/VGW with a Session-Release-Confirm primitive and send a Session-Release-Request primitive to the internal SIP UA. If a Session-Resume primitive is received before the timer expires, the Feature Manager shall stop the suspend timer. B.4.4.2.2 Tight coupling procedures On receipt of a Session-Release-Request primitive, the Feature Manager shall determine whether to apply the Call Held service depending on the user profile and the type of call. If no explicit indication is received as part of the profile delivery procedure, the Feature Manager determines whether the Call Held service is provisioned or not, based on a network option. If the Call Held service is provisioned, the type of call is evaluated. The call held service should be considered applicable for the following type of calls: • Emergency call (call to a Public Safety Answering Point). • As a network option: Other special numbers (e.g. call to operator). The emergency numbers (and optionally other special numbers) should be provisioned in the VGW/AGCF in order to enable type of call evaluation. NOTE 1: An alternative method to identify the type of call maybe providing a called party category in 1xx or 200 OK response. This is not specified in this release. If the Call Held service is applicable, the Feature Manager shall respond to the MGC component of the AGCF/VGW with a Session-Release-Suspend primitive and request the SIP UA to send an INVITE (on-hook) request on a new dialogue to the PES Application Server. If the Call Held service is not applicable, the Feature Manager shall respond to the MGC component of the AGCF/VGW with a Session-Release-Confirm primitive and send a Session-Release-Request primitive to the internal SIP UA. In all cases the INVITE (on-hook) request is built as follows: • The Request URI is structured as follows: - A user part containing a unique value that signifies that a on-hook event was detected (such as onhook@pes-scc.operator.com). - A domain name which together with the user part provides sufficient information to the S-CSCF to forward the INVITE request to the appropriate AS, based on Initial Filter Criteria stored in the user profile (see annex C). • A P-Asserted-Identity (AGCF) or a P-Preferred-Identity may be sent (VGW) containing the public identity of the subscriber on behalf of whom the on-hook event is reported. NOTE 2: Upon receipt of the INVITE (on-hook) the Application Server can send a BYE request on the call-associated dialogue if the call is to be released or start a suspend timer and wait for another INVITE reporting the offhook event. If the suspend timer expires the Application Server can send a BYE request on the call-associated dialogue. • An SDP offer for a voice call. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 79 If a Session-Resume primitive is received, the Feature Manager shall request to the SIP UA to send an INVITE (off- hook) request built as follows: • The Request URI is structured as follows: - A user part containing a unique value that signifies that a off-hook event was detected (such as offhook@pes-scc.operator.com). - A domain name which together with the user part provides sufficient information to the S-CSCF to forward the INVITE request to the appropriate AS, based on Initial Filter Criteria stored in the user profile (see annex C). • A P-Asserted-Identity (AGCF) or a P-Preferred-Identity may be sent (VGW) containing the public identity of the subscriber on behalf of whom the off-hook event is reported. • An SDP offer for a voice call. B.4.4.3 Terminating side procedures B.4.4.3.1 Loose coupling procedures On receipt of a Session-Release-Request primitve, the Feature Manager shall determine whether to apply the Call Held service depending on the user profile. If no explicit indication is received as part of the profile delivery procedure, the default value is network specific. If an indication that the Call Held service is not provisioned to the user has been received as part of the profile delivery procedure, the Feature Manager shall respond to the MGC component of the AGCF/VGW with a Session-Release- Confirm primitive and send a Session-Release-Request primitive to the internal SIP UA. Otherwise it shall respond to the MGC component of the AGCF/VGW with a Session-Release-Suspend primitive and start a suspend timer. If the suspend timer expires, the Feature Manager shall respond to the MGC component of the AGCF/VGW with a Session-Release-Confirm primitive and send a Session-Release-Request primitive to the internal SIP UA. If a Session-Resume primitive is received before the timer expires, the Feature Manager shall stop the suspend timer. B.4.4.3.2 Tight coupling procedures On receipt of a Session-Release-Request primitve, the Feature Manager shall determine whether to apply the Call Held service depending on the user profile. If no explicit indication is received as part of the profile delivery procedure, the default value is network specific. If the Call Held service is provisioned, the Feature Manager shall respond to the MGC component of the AGCF/VGW with a Session-Release-Suspend primitive and request the SIP UA to send an INVITE (on-hook) request to the PES Application Server over a new dialogue. If the Call Held service is not provisioned, the Feature Manager shall respond to the MGC component of the AGCF/VGW with a Session-Release-Confirm primitive and send a Session-Release-Request primitive to the internal SIP UA. In all cases the INVITE (on-hook) request is built as follows: • The Request URI is structured as follows: - A user part containing a unique value that signifies that a on-hook event was detected (such as onhook@pes-scc.operator.com). - A domain name which together with the user part provides sufficient information to the S-CSCF to forward the INVITE request to the appropriate AS, based on Initial Filter Criteria stored in the user profile (see annex C). • A P-Asserted-Identity (AGCF) or a P-Preferred-Identity may be sent (VGW) containing the public identity of the subscriber on behalf of whom the on-hook event is reported. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 80 NOTE: Upon receipt of the INVITE (on-hook) the Application Server can send a BYE request on the call- associated dialogue if the call is to be released or start a suspend timer and wait for another INVITE reporting the offhook event. If the suspend timer expires the Application Server can send a BYE request on the call-associated dialogue. • An SDP offer for a voice call. If a Session-Resume primitive is received, the Feature Manager shall request to the SIP UA to send an INVITE (off- hook) request built as follows: • The Request URI is structured as follows: - A user part containing a unique value that signifies that a off-hook event was detected (such as offhook@pes-scc.operator.com). - A domain name which together with the user part provides sufficient information to the S-CSCF to forward the INVITE request to the appropriate AS, based on Initial Filter Criteria stored in the user profile (see annex C). • A P-Asserted-Identity (AGCF) or a P-Preferred-Identity may be sent (VGW) containing the public identity of the subscriber on behalf of whom the off-hook event is reported. • An SDP offer for a voice call. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 81 Annex C (informative): Implementation of Supplementary Services C.1 General principles C.1.1 Introduction This annex describes guiding principles for implementing commonly deployed PSTN supplementary services using the IMS-based PES architecture. The list of services is taken from EG 201 973-2 [i.6]. The actual service logic resides in the Application Server and is outside the scope of standardization. This annex focuses on the interactions between the AGCF and PES application servers. Only the part of the service logic which has an impact on signalling to/from the AGCF is described in this annex. Similar procedures may also be used in case of analogue lines connected to a VGW acting as a UE with regard to a P-CSCF in the PES. The present document will describe these procedures of the VGW in the appropriate clause. AGCF involvement in the execution of these services is limited to the generic capabilities described in the main body of the present document for supporting interworking between SIP and H.248 protocols and in annex B for processing flash-hook events. C.1.2 Supplementary Service control This annex assumes that subscribers can control their supplementary services using service code commands and switching order commands as defined in ETS 300 738 [12]. More than one command can be dialled on a single call. For instance, a caller may dial the "inhibit call waiting" command, followed by the "calling line identity restriction" command, followed by the called party number. C.1.2.1 Service code commands Service codes commands are user requests to perform an action that does not result in a call to another party. Actions such as feature activation, feature deactivation, and feature status inquiries are triggered by service code commands. C.1.2.1.1 Command syntax The format of service code commands as defined in ETS 300 738 [12] is reproduced below: "START PX SC (SR SI) SX" or "PX SC (SR SI) SX FINISH" Where: • START is the start command, e.g. "Off-hook", an alternative to the finish command; • PX is a mandatory service prefix; • SC is a mandatory service code; • SR is one or more separator/s, as required; • SI is one or more units of supplementary information, as required; • SX is a service suffix as required; • FINISH is a finish command, e.g. SEND, an alternative to the start command. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 82 NOTE: Digit maps used by the media gateways or VGW to collect digits, include appropriate alternatives to cope with the syntax of service code commands. C.1.2.1.2 Generic procedure at the AGCF/VGW side On receipt of a service code command from a media gateway, the AGCF/VGW sends an INVITE request to the S-CSCF with the following information: • A Request-URI structured as follows: - A user part containing the service code command, excluding the START and FINISH fields. - A domain name which together with the user part provides sufficient information to the S-CSCF to forward the INVITE request to the appropriate AS, based on Initial Filter Criteria stored in the user profile, e.g.: "PX SC (SR SI) SX"@pes-scc.operator.com NOTE 1: If the service code command includes a square "#" symbol, the userinfo portion of the Request-URI is in the form of a telephone-subscriber. The series of digits that form the service code command are encoded as a local-number. The phone-context attribute is set to a domain name of the PES operator, e.g. phonecontext=pes-scc.homedomain.com that is specific enough to enable the application server to interpret the commandecode. Setting the phone-context attribute is required for conformance purposes with RFC 3966 [19]. PES network entities (e.g. CSCF) ignore this attribute. • An AGCF sends a P-Asserted-Identity header containing the public user identity of the subscriber issuing the service code command or in the case of the VGW a P-Preferred-Identity header may be sent. If the P-Preferred-Identity is not sent then the PES Endpoint ensures that the From header contains the equivalent identity. • An SDP offer for a voice call. NOTE 2: The SDP offer may be used by the Application Server in case an announcement has to be delivered. C.1.2.1.3 Generic procedure at the AS side On receipt of the INVITE request that includes a service code command as Request-URI, the AS sends back a 183 (Session Progress) message. NOTE: An SDP Answer may be included in the 183 (Session Progress) response in case the user is expected to key-in additional digits before the procedure can be completed. In such cases, the AS requests an MRFC/MRFP to play an appropriate prompting announcement and collect digits. The procedure for supporting user interactions during the call establishment phase is described within TS 124 628 [6]. If the procedure identified by the service code command is successfully performed, the AS modifies the subscriber profile according to the service code received, requests an MRFC/MRFP to play a positive acknowledgment tone or announcement and sends a 200 OK response towards the AGCF/VGW when the MRFC is connected. If the service code command corresponds to an interrogation procedure, the AS selects the appropriate announcement to notify the requested information (e.g. current supplementary service status) to the calling user. Release of the dialogue occurs when a BYE request is received from the MRFC or if a BYE/CANCEL request is received from the AGCF/VGW. If the procedure identified by the service code command cannot be performed successfully, the AS requests an MRFC/MRFP to play a negative acknowledgment tone or announcement and releases the call by sending a suitable 4xx or 5xx response to the INVITE request or by sending a BYE request if the dialogue is already established. The procedure for sending a tone or an announcement during the call establishment phase is described within TS 124 628 [6]. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 83 C.1.2.2 Switching order commands Switching order commands are typically used to invoke a service or modify the characteristics of a call, such as establish a three-party call. The format of switching order commands (SOC) is reproduced below: "START SO (SR SI)" or "SO (SR SI) FINISH" Where: • START is a start command, e.g. "Register Recall (R)", an alternative to the finish command, as required; • SO is a mandatory switching order; • SR is one or more separators, as required; • SI is one or more units of supplementary information, as required; • FINISH is a finish command, e.g. "send", an alternative to the start command, as required. Processing of switching order commands where the start command is a Register Recall (also known as Flash-Hook event) is described in annex B. Processing of the Register Recall at the AGCF/VGW depends on the call configuration and loose or tight coupling methods (see clause B.4.2.2). Processing of the Register Recall at the VGW depends on the call configuration and usually the VGW delivers a dial tone and collect digits. C.1.3 Setting of initial filter criteria Emulation of PSTN services requires that Initial Filter Criteria stored in the user profile be set on the following methods: • Originating INVITE methods. • Terminating INVITE methods. • Terminating MESSAGE methods. The user profile is selected based on the contents of the P-Asserted-Identity (originating method) or Request-URI (terminating method) headers. How many Initial Filter Criteria are actually required depend on how many application servers are involved in the provision of these services. When several application servers are involved, each implementing a particular service set or feature set, other service point triggers (SPT) may be added to Initial Filter Criteria so as to route the SIP messages to the appropriate server, in the right order. In case of outgoing calls (including special calls for service control purposes), the Request-URI may typically be part of an Initial Filter Criteria. The content tag will typically contain an Extended Regular Expressions (ERE) as defined in clause 9 in IEEE 1003.1-2004 [i.2] such that any Request-URI that includes a particular pattern (e.g. a domain name) matches the criteria. The following example illustrates the case of an IFC used to trigger an application server dedicated to the processing of service code commands, assuming that the AGCF/VGW appends the pes-scc.homedomain.com domain name to the service code commands. <InitialFilterCriteria> <Priority>0</Priority> <TriggerPoint> <ConditionTypeCNF>0</ConditionTypeCNF> <SPT> <ConditionNegated>0</ConditionNegated> <Group>0</Group> <Method>INVITE</Method> ETSI ETSI TS 183 043 V3.4.1 (2011-04) 84 </SPT> <SPT> <ConditionNegated>0</ConditionNegated> <Group>0</Group> <RequestURI>@pes-scc.homedomain.com$</RequestURI> </SPT> </TriggerPoint> <ApplicationServer> <ServerName>sip:PES-AS1@homedomain.com</ServerName> <DefaultHandling>0</DefaultHandling> </ApplicationServer> </InitialFilterCriteria> C.1.4 Supplementary services using ISUP information Full support of supplementary services may be realized by exchanging service information between peer SIP signalling entities via SIP signalling and/or encapsulated ISUP information. The ISUP information necessary to support each individual service is specified by the corresponding ETSI or ITU-T supplementary service specification; see table C.1. Table C.1: Supplementary Service References Supplementary Service ETSI/ITU-T Reference Calling Line Identification Presentation (CLIP) EN 300 356-3 [34] Calling Line Identification Restriction (CLIR) EN 300 356-4 [34] Connected Line Identification Presentation (COLP) EN 300 356-5 [34] Connected Line Identification Restriction (COLR) EN 300 356-6 [34] Terminal Portability (TP) EN 300 356-7 [34] User-to-User Signalling (UUS) EN 300 356-8 [34] Closed User Group (CUG) EN 300 356-9 [34] Subaddressing (SUB) EN 300 356-10 [34] Malicious Call Identification (MCID) EN 300 356-11 [34] Conference Call (CONF) EN 300 356-12 [34] Explicit Call Transfer (ECT) EN 300 356-14 [34] Call Forwarding Busy (CFB) EN 300 356-15 [34] Call Forwarding No Reply (CFNR) EN 300 356-15 [34] Call Forwarding Unconditional (CFU) EN 300 356-15 [34] Call Deflection (CD) EN 300 356-15 [34] Call Hold (HOLD) EN 300 356-16 [34] Call Waiting (CW) EN 300 356-17 [34] Completion of Calls to Busy Subscriber (CCBS) EN 300 356-18 [34] Three-Party (3PTY) EN 300 356-19 [34] Completion of Calls on No Reply (CCNR) EN 300 356-20 [34] Anonymous Communication Rejection (ACR) EN 301 798 [39] Multi-Level Precedence and Pre-emption (MLPP) ITU-T Recommendation Q.735.3 [35] Global Virtual Network Service (GVNS) ITU-T Recommendation Q.735.6 [36] Reverse charging (REV) ITU-T Recommendation Q.736.3 [37] C.2 Advice of Charge C.2.1 Actions at the Originating AGCF C.2.1.1 General When receiving charging pulses from the Application Server (via the S-CSCF) the AGCF can either as a network option: • generate Metering Pulses by one of the methods described in clause C.2.1.2 and request the media gateway to generate metering pulses by means of one of the signals of the amet package defined in ITU-T Recommendation H.248.26 [14]; or ETSI ETSI TS 183 043 V3.4.1 (2011-04) 85 • build an Advice Of Charge message (see ES 200 659-3 [10]) by rules described in annex D and request the media gateway to transmit this message, using the Generic Data Signalling (data) signal of the Analogue Display Signalling (andisp) package defined in ITU-T Recommendation H.248.23 [13]. In addition to the procedures according to TS 124 229 [4], the Originating AGCF includes the Accept header field with: • "application/vnd.etsi.aoc+xml", the MIME type associated with AOC information (see annex E), and indicate the versions of the AOC XML Schema it supports. One of the versions - of the MIME type associated with AOC information (see annex E) - indicated corresponds with a value of the version attribute of the <schema> XML element of an AOC XML Schema (see annex E); and • any other MIME type the served UE is willing and capable to accept. C.2.1.2 AGCF Metering Pulse generation C.2.1.2.1 Usage of an AOC-D for Metering Pulse generation Upon receipt of an AOC- XML document including AOC-D information (i.e. with an "aocType" element set to "aoc-d"), the AGCF requests the media gateway to generate metering pulses using the Burst Pulses Count parameter of the Metering Pulse Burst signal of the amet package defined in ITU-T Recommendation H.248.26 [14]. The Pulse Repetition Interval for metering burst is provisioned in the MG. C.2.1.2.2 Usage of AOC-S for Metering Pulse generation Annex E extends the TS 124 647 [7] AOC -XML schema for Pulse Metering usage. This method may be used in order to reduce signalling load between AS and AGCF. It does not replace the actual billing information which is stored in CDRs of the responsible Application Servers. When receiving Pulse Metering Instructions from the PES Application Server (via the S-CSCF), the AGCF requests the media gateway to generate metering pulses by means of amet package defined in ITU-T Recommendation H.248.26 [14]. The type and duration of the pulses to be applied are provisioned in the MG. Procedures for Continuous Metering Pulse (Basic Communication continuous charge): Upon reception of AOC-S for basic communication with continuous type of charging (periodic metering), the AGCF requests the media gateway to generate metering pulses using the Pulse Count and Pulse Repetition Interval of the Enable Metering signal of the amet package defined in ITU-T Recommendation H.248.26 [14]. Procedures for single Metering Pulse Burst (e.g. for Communication Set-up charge, Service Add-on charge): Flat rate charging (e.g. at communication set-up or due to add-on charge) requires generation of a metering burst. The AGCF requests the media gateway to generate metering pulses using the Burst Pulses Count parameter of the Metering Pulse Burst signal of the amet package defined in ITU-T Recommendation H.248.26 [14]. The Pulse Repetition Interval for metering burst is provisioned in the MG. Procedures for Repetitive Metering Pulse Burst: The AGCF repetitively requests the media gateway every charging interval to generate metering pulses using the Burst Pulses Count parameter of the Metering Pulse Burst signal of the amet package defined in ITU-T Recommendation H.248.26 [14]. Alternatively, the AGCF may use a single H.248.26 [14] amet/phsm (phased metering) signal in order to request the media gateway to generate metering pulses, if this signal is supported. C.2.2 Actions at the Originating AS C.2.2.1 General Implementation of this service assumes that the AS providing the service is involved in all outgoing calls for which advice of charge information is expected. It is the responsibility of the network operator to configure the appropriate Initial Filter Criteria in the user profile. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 86 Charging pulses or policies for generating charging pulses are transmitted from the Application Server to the AGCF using the method described in [7] when using the AOC-D Type. When using the AOC-S Type, the method defined in [7] requires to be extended per annex E. C.2.2.2 Usage of AOC-D for Metering Pulse generation The PES application server creates an XML document according to the schema defined in TS 124 647 [7], annex D including an "aoc" element with the following content: • The "aocType" element set to "aoc-d". • The "aoc-dType" element set to "recorded-charges". • The "recorded-chargesType" set to "recorded-currency-units". • The "currency-id-amountType" elements is set as follows: - "currency-id" set to "UNIT"; - "currency-amount" set to the number of additional charging units for the purpose pf metering pulses generation or to the accumulated charging units for the purpose of the AOC display service defined in ES 200 659-3 [10]. NOTE: This method requires the application server to be aware about the line type (for analogue line the AOC-D charging information is "additional", for ISDN line the AOC-D charging information is "accumulative"). C.2.2.3 Usage of AOC-S for Metering Pulse generation C.2.2.3.1 Overview of AOC-S usage with extended AOC Charging pulses or policies for generating charging pulses are transmitted from the Application Server to the VGW/AGCF using the following method: • The PES application server creates an XML document complying with the extended AOC XML schema defined in annex E. • The "aoc-extended" element may contain a "pes-transitioning behaviour" attribute element. The "pes-transitioning behaviour" parameter indicates to the VGW/AGCF how the transitioning behaviour on the line occurs. This is primarily related to the determination of pause durations among the last pulse of the previous tariff and the first pulse of the new tariff. • The "aocType" element set to "aoc-s". The "aoc-s" Type of the extended AOC XML schema is defined as a sequence of "aoc-s" metering phases. A sequence of "aoc-s" metering phases provides an entire call tariff in a single message from the AS to the VGW/AGCF. Each charging phase of a call is represented by an "aoc-s" metering phase. The duration of an "aoc-s" metering phase is defined by an "pes_aoc-s_phase_duration" parameter as part of the "charged-items" element. C.2.2.3.2 AOC Information Elements - Extensions to TS 124 647 - Annex C a) Pes-transitioning behaviour: The pes-transitioning behaviour is expressed as "immediate" or "continuous": - Immediate: The new tariff becomes effective immediately as per the rules defined by the network operator. Typically, a still ongoing burst pulse train is finished or an individual pulse is completed and then the first pulse of the new tariff is generated at the least possible delay. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 87 - Continuous: Activating the new tariff takes account of the pauses between individual pulses or bursts of the new tariff and the time that has already elapsed since the last pulse of the previous tariff. The pause between the first pulse of the new tariff and the last pulse of the previous tariff is at least corresponding to the pause duration of the new tariff. The default "pes-transitioning behaviour" is "immediate". b) AOC-S PHASE Duration: Represents the duration of the "aoc-s" metering phase, in seconds. A value of "0" indicates an infinite duration. C.2.2.3.3 AOC-S Parameter settings for Pulse Metering generation For the purpose of Metering Pulse generation the AS uses the AOC XML described in annex E as follows: • The "currency-id" element has to be set to "UNIT". • The "currency-amount" element has to be set as follows: a) For periodic metering pulse generation the "currency-amount" value is set to "0". b) For metering burst pulse generation the "currency-amount" value is set to the number of pulses to be transmitted. • The "length- time- unit" element is used for Basic Communication price-time, continuous charging (periodic metering pulse or repetitive metering burst pulse). The currency-amount value determines the meaning of the "length- time- unit" element as follows: a) For "currency-amount"=0, the "length- time- unit" element is defined as the Pulse Repetition Interval. The Pulse Repetition Interval is defined as the interval from the leading edge of a metering pulse to the leading edge of the next metering pulse. b) For "currency-amount"≥1, the "length- time- unit" element is defined as the Charging Interval. The Charging Interval is defined as the interval at which the metering burst (consisting of N metering pulses) is repeated, in seconds. Metering Pulse Burst at start of call (AOC-S: Communication Set-Up - flat rate charging): The "aocType" element is set to "aoc-s". The optional "pes-transitioning-behaviourType" is specified, if required. The "aoc-sType" element is set to "charged-items". The optional "pes_aoc-s_phase_durationType" is expressed as a time unit in seconds, if required. The "charged-itemsType" is set to "communication-setup". The "communication-setupType" is set to "flat-rate". The "currency-id-amountType" elements is set as follows: - "currency-id" set to "UNIT"; - "currency-amount" set to the number of charging pulses. Periodic Metering Pulse (AOC-S: Basic Communication - price-time, continuous charging): The "aocType" element is set to "aoc-s". The optional "pes-transitioning-behaviourType" is specified, if required. The "aoc-sType" element is set to "charged-items". The optional "pes_aoc-s_phase_durationType" is expressed as a time unit in seconds, if required. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 88 The "charged-itemsType" is set to "basic". The "basicType" is set to "price-time". The "price-timeType" elements is set as follows: - "currency-id" set to "UNIT". - "currency-amount" set to "0". - "length- time- unit" set to Pulse Repetition Interval. - "charging-type" set to "continuous". Periodic Metering Pulse Burst (AOC-S: Basic Communication - price-time, continuous charging): The "aocType" element is set to "aoc-s". The optional "pes-transitioning-behaviourType" is specified, if required. The "aoc-sType" element is set to "charged-items". The optional "pes_aoc-s_phase_durationType" is expressed as a time unit in seconds, if required. The "charged-itemsType" is set to "basic". The "basicType" is set to "price-time". The "price-timeType" elements is set as follows: - "currency-id" set to "UNIT". - "currency-amount" set to "N" (N≥1) charging pulse. - "length- time- unit" set to Charging Interval. - "charging-type" set to "continuous". Metering Pulse Burst for Flat Rate charging (AOC-S: Basic Communication - flat rate charging): The "aocType" element is set to "aoc-s". The "aoc-sType" element is set to "charged-items". The "charged-itemsType" is set to "basic". The "basicType" is set to "flat-rate". The "currency-id-amountType" elements is set as follows: - "currency-id" set to "UNIT". - "currency-amount" set to N (N≥1) charging pulses. Metering Pulse Burst for Add-On charging (AOC-S: Services- Flat-Rate): The "aocType" element is set to "aoc-s". The "aoc-sType" element is set to "charged-items". The "charged-itemsType" is set to "services". The "servicesType" is set to "flat-rate". The "currency-id-amountType" elements is set as follows: - "currency-id" set to "UNIT". - "currency-amount" set to the number of additional charging pulses. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 89 Phase 1 = Metering Pulse Burst (start of call) and Phase 2= Periodic Metering Pulse: The "aocType" element is set to "aoc-s". The optional "pes-transitioning-behaviourType" is specified, if required. The "aoc-sType" consists of a sequence of two "aoc-s" phases as follows: 1st "aoc-s" phase: The "aoc-sType" element is set to "charged-items". The "pes_aoc-s_phase_durationType" is expresses as a time unit in seconds. The "charged-itemsType" is set to "communication-setup". The "communication-setupType" is set to "flat-rate". The "currency-id-amountType" elements is set as follows: "currency-id" set to "UNIT". "currency-amount" set to the number of charging pulses. 2nd "aoc-s" phase: The "aoc-sType" element is set to "charged-items". The "pes_aoc-s_phase_durationType" is set to "0" (infinite duration). The "charged-itemsType" is set to "basic". The "basicType" is set to "price-time". The "price-timeType" elements is set as follows: "currency-id" set to "UNIT". "currency-amount" set to "0". "length- time- unit" set to Pulse Repetition Interval. "charging-type" set to "continuous". Stopping generation of metering pulse (AOC-S: Basic Communication - free-charge): The "aocType" element is set to "aoc-s". The "aoc-sType" element is set to "charged-items". The "charged-itemsType" is set to "basic". The "basicType" is set to "free-charge". C.2.3 Actions at the Terminating AGCF Not applicable. C.2.4 Actions at the Terminating AS Not applicable. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 90 C.2.5 Actions at the originating VGW C.2.5.1 General When receiving charging pulses from the Application Server (via the S-CSCF) the VGW can either as a network option: • generate Metering Pulses by one of the methods described in clause C.2.5.2; or • build an Advice Of Charge message (see ES 200 659-3 [10]) by rules described in annex D and transmit this message. In addition to the procedures according to TS 124 229 [4], the Originating VGW includes the Accept header field with: • "application/vnd.etsi.aoc+xml", the MIME type associated with AOC information (see annex E), and indicate the versions of the AOC XML Schema it supports. One of the versions - of the MIME type associated with AOC information (see annex E) - indicated is corresponding with a value of the version attribute of the <schema> XML element of an AOC XML Schema (see annex E); and • any other MIME type the served UE is willing and capable to accept. C.2.5.2 VGW Metering Pulse generation C.2.5.2.1 Usage of an AOC-D for Metering Pulse generation Upon receipt of an AOC- XML document including AOC-D information (i.e. with an "aocType" element set to "aoc-d"), the VGW generate metering pulses. The Pulse Repetition Interval for metering burst is provisioned in the VGW. C.2.5.2.2 Usage of AOC-S for Metering Pulse generation Annex E extends the TS 124 647 [7] AOC -XML schema for Pulse Metering usage. This method may be used in order to reduce signalling load between AS and VGW. It does not replace the actual billing information which is stored in CDRs of the responsible Application Servers. When receiving Pulse Metering Instructions from the PES Application Server (via the S-CSCF), the VGW generates metering pulses. The type and duration of the pulses to be applied are provisioned in the VGW. Procedures for Continuous Metering Pulse (Basic Communication continuous charge): Upon reception of AOC-S for basic communication with continuous type of charging (periodic metering), the VGW generates metering pulses using the Pulse Repetition Interval. The Pulse repetition interval is applied from the XML schema. Procedures for single Metering Pulse Burst (e.g. for Communication Set-up charge, Service Add-on charge): Flat rate charging (e.g. at communication set-up or due to add-on charge) requires generation of a metering burst. The Pulse Count is applied from the XML schema and the Pulse repetition interval is provisioned in the VGW. Procedures for Repetitive Metering Pulse Burst: The VGW repetitively generates single metering Burst Pulses. The burst repetition interval is applied from the XML schema. C.2.6 Actions at the terminating VGW Not applicable. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 91 C.3 Anonymous Call Rejection C.3.1 Actions at the Originating AGCF This service does not require the originating AGCF to perform any specific action. C.3.2 Actions at the Originating AS This service does not require the originating AS to perform any specific action. C.3.3 Actions at the Terminating AS If the service is activated, the terminating AS rejects the call if the INVITE request includes the P-Asserted-Identity header field and includes the Privacy header field indicates "id", "header", or "user" as specified in RFC 3323 [24] and RFC 3325 [25]. In all other cases the communication proceeds normally. NOTE: If the P-Asserted-Identity header field is not present, the call is not rejected. When the AS rejects a communication, the AS sends an indication to the calling user by sending a 433 (Anonymity Disallowed) response. Additionally, before terminating the communication an announcement can be provided to the originating user. The procedure for invoking an announcement in the call establishment phase is described within TS 124 628 [6]. As a service option the ACR service may forward the communication to a voice message service instead of rejecting the communication with a 433 (Anonymity Disallowed) final response. C.3.4 Actions at the Terminating AGCF The terminating AGCF is not involved in the execution of this service. C.3.5 Actions at the Originating VGW This service does not require the originating VGW to perform any specific action. C.3.6 Actions at the Terminating VGW This service does not require the terminating VGW to perform any specific action. C.4 Automatic Call Return C.4.1 Actions at the AGCF at the invoker side The Automatic Call Return service is invoked using a service code command. On receipt of this service code command, the AGCF builds an INVITE request as described in clause C.1. C.4.2 Actions at the AS at the invoker side Implementation of this service assumes that the AS providing the service is involved in all incoming calls to the served user. It is the responsibility of the network operator to configure the appropriate Initial Filter Criteria in the user profile. The AS keeps track of the most recent incoming call to each served user it manages. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 92 When receiving the service code command that identifies the Automatic Call Return service, the AS acts as a B2BUA and establishes a new call leg to the most recent caller (i.e. it sends an INVITE messages towards this most recent call party as if the number had been dialled by the served user), unless presentation of the corresponding identity was restricted or this identity was not available. C.4.3 Actions at the VGW at the invoker side The Automatic Call Return service is invoked using a service code command. On receipt of this service code command, the VGW builds an INVITE request as described in clause C.1. C.5 Calling Line Identity Presentation/Restriction C.5.1 Actions at the Originating AGCF A service code command may be received by the AGCF in case the calling user wishes to override the default setting for a particular call, in which case the called party number is embedded in the command code as part of the supplementary information. The AGCF generates an INVITE request according to the rules described in clause C.1. Otherwise the originating AGCF is not involved in the provision of this service. C.5.2 Actions at the Originating AS The AS determines whether calling identification is presented or restricted based on user profile data (permanent mode) or based on the contents of the Request-URI (per-call mode). Any service prefix is removed from the Request-URI before forwarding the INVITE request toward the called party. If calling identification restriction is in force, the AS applies the following changes before forwarding the received INVITE request towards the called party via the S-CSCF: • Override the contents of the From header field with an "anonymous" indication. The convention for configuring an anonymous From header field described in RFC 3323 [24] and RFC 3325 [25] should be followed; i.e.: From: "Anonymous" <sip:anonymous@anonymous.invalid>;tag= xxxxxxx. • Include a Privacy header field set to "id" and optionally "header" or/and "user" in accordance with RFC 3323 [24] and RFC 3325 [25]. If the originating user wishes to override the default setting of "presentation restricted" of the OIR service in temporary mode, the originating AS includes a Privacy header field of privacy type "none" in accordance with TS 124 229 [4] and RFC 3323 [24]. On receipt of an INVITE request with a service code command requesting that the calling line identity be presented to the called party, the AS removes the service prefix from the service code command and forwards the INVITE request unchanged towards the called party, via the S-CSCF. Otherwise the originating AS is not involved in the provision of this service. C.5.3 Actions at the Terminating AS If the service is subscription dependent and the called user has not subscribed to the service, the terminating AS removes any P-Asserted-Identity and Privacy header fields included in the request. Additionally, the Application Server may as a network option set the contents of the From header to a default non significant value which is different from the values in the list below: • From: "Anonymous" <sip:anonymous@anonymous.invalid>;tag= xxxxxxx. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 93 • From: "Unavailable" <"sip:unavailable@unknown.invalid>;tag= xxxxxxx. The following From header value is recommended in order to indicate that the subscriber has not subscribed: • From: "Unsubscribed" <sip:unsubscribed@unsubscribed.invalid>;tag= xxxxxxx. If the request includes the Privacy header field set to "header" the AS set the contents of all headers containing private information in accordance with RFC 3323 [24] and RFC 3325 [25]. If the request includes the Privacy header field set to "user" the AS removes or set the contents of all "user configurable" headers in accordance with RFC 3323 [24] and RFC 3325 [25]. In the latter case, the AS may need to act as transparent back-to-back user agent as described in RFC 3323 [24]. NOTE: If the request includes the Privacy header field set to "id", the P-Asserted-Identity header is removed by the S-CSCF. C.5.4 Actions at the Terminating AGCF User Identification information received in an INVITE request ("P-Asserted-Id", "Privacy", and "From" headers) is used by the AGCF to generate the appropriate Call Setup message (see ES 200 659-3 [10]) to be delivered to the called terminal, using the H.248 andisp package. Generation of the Call Setup message is further described in annex D. C.5.5 Actions at the Originating VGW A service code command may be received by the VGW in case the calling user wishes to override the default setting for a particular call, in which case the called party number is embedded in the command code as part of the supplementary information. The VGW generates an INVITE request according to the rules described in clause C.1. Otherwise the originating VGW is not involved in the provision of this service. C.5.6 Actions at the Terminating VGW User Identification information received in an INVITE request ("P-Asserted-Id", "Privacy", and "From" headers) is used by the VGW to generate the appropriate Call Setup message (see ES 200 659-3 [10]) to be delivered to the called terminal. Generation of the Call Setup message is further described in annex D. C.6 Calling Name Delivery C.6.1 Actions at the Originating AGCF No specific action is performed by the AGCF. C.6.2 Actions at the Originating Application Server If the calling user has subscribed to the service and no presentation restriction is invoked, the originating AS inserts a pre-configured calling name in the Display field of the From header and possibly the same or different name in the Display field of the P-Asserted-Identity header. C.6.3 Actions at the Terminating Application Server If the service is subscription dependent and the called user has not subscribed to the service, the terminating AS removes or the From header or set its contents in accordance with RFC 3323 [24]. If the request includes the Privacy header field set to "header" the AS sets the contents of all headers containing private information in accordance with RFC 3323 [24] and RFC 3325 [25]. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 94 If the request includes the Privacy header field set to "user" the AS removes or sets the contents of all "user configurable" headers in accordance with RFC 3323 [24] and RFC 3325 [25]. In the latter case, the AS may need to act as transparent back-to-back user agent as described in RFC 3323 [24]. C.6.4 Actions at the Terminating AGCF User Name information received in an INVITE request ("From" header /or "P-Asserted-Identity") is used by the AGCF to generate the appropriate Call Setup message (see ES 200 659-3 [10]) to be delivered to the called terminal, using the H.248 andisp package. Generation of the Call Setup message is further described in annex D. C.6.5 Actions at the Originating VGW This service does not require the originating VGW to perform any specific action. C.6.6 Actions at the Terminating VGW User Name information received in an INVITE request ("From" header /or "P-Asserted-Identity") is used by the VGW to generate the appropriate Call Setup message (see ES 200 659-3 [10]). Generation of the Call Setup message is further described in annex D. C.7 Call Forwarding C.7.1 Activation/Deactivation/Interrogation C.7.1.1 Actions at the AGCF Registration, Erasure, Activation, Deactivation and Interrogation of call forwarding services is performed using service code commands as described in ETS 300 738 [12]. On receipt of a service code command that corresponds to one of these procedures, the AGCF proceeds as described in clause C.1. C.7.1.2 Actions at the AS On receipt of a service code command, the AS proceeds as described in clause C.1. In case of unconditional call forwarding the AS may also send a NOTIFY request to the AGCF/VGW to update the Dial Tone Management XML document. C.7.1.3 Actions at the VGW Registration, Erasure, Activation, Deactivation and Interrogation of call forwarding services is performed using service code commands as described in ETS 300 738 [12]. On receipt of a service code command that corresponds to one of these procedures, the VGW proceeds as described in clause C.1. C.7.2 Invocation C.7.2.1 Actions at the Originating AGCF No specific action is performed by the AGCF. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 95 C.7.2.2 Actions at the Originating AS No specific action is performed by the AS. C.7.2.3 Actions at the Forwarding AS The AS implements procedures identical or similar to those described in TS 124 604 [9]. C.7.2.4 Actions at the Forwarding AGCF The AGCF at the forwarding side is not involved in the processing of forwarded calls. C.7.2.5 Actions at the Terminating AS No specific action is performed by the AS. C.7.2.6 Actions at the Terminating AGCF Call forwarding information received in an INVITE request ("history-info" header) is used by the AGCF to generate the appropriate Call Setup message (see ES 200 659-3 [10]) to be delivered to the called terminal, using the H.248 andisp package. Generation of the Call Setup message is further described in annex D. C.7.2.7 Actions at the Originating VGW No specific action is performed by the VGW. C.7.2.8 Actions at the Forwarding VGW The VGW at the forwarding side is not involved in the processing of forwarded calls. C.7.2.9 Actions at the Terminating VGW Call forwarding information received in an INVITE request ("history-info" header) is used by the VGW to generate the appropriate Call Setup message (see ES 200 659-3 [10]) Generation of the Call Setup message is further described in annex D. C.8 Distinctive Ringing C.8.1 Actions at the Originating AGCF This service does not require the originating AGCF to perform any specific action. C.8.2 Actions at the Originating Application Server This service does not require the originating AS to perform any specific action. C.8.3 Actions at the Terminating Application Server The terminating AS inserts an "alert-info" header field in the INVITE request with a value selected based on the value of the P-Asserted-Identity header field received in the incoming INVITE request and on the called user profile. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 96 NOTE: The content of "alert-info" header field has to be agreed between the AS and the AGCF / VGW. A suggested default template for encoding the "alert-info" header field value is Alert-Info: <http://localhost/pattern_N>, where pattern_N is associated to a specific ring pattern. C.8.4 Actions at the Terminating AGCF The terminating AGCF uses the value of the "alert-info" header to select the appropriate ring pattern. The pattern identifier is sent to the media gateway as a parameter of the H.248 andisp/dwa signal. C.8.5 Actions at the Originating VGW This service does not require the originating VGW to perform any specific action. C.8.6 Actions at the Terminating VGW The terminating VGW uses the value of the "alert-info" header to select the appropriate ring pattern. C.9 Call Waiting C.9.1 General for Loose Coupling C.9.1.1 Actions at the AGCF at the terminating side • On receipt of an INVITE request for a busy subscriber, the AGCF determines whether to trigger a call waiting procedure as specified in clause 7.3.1.3.2. If the call waiting timer expires the AGCF sends a 486 (Busy Here) or 480 (Temporarily unavailable) response towards the Application Server, depending on the operator policy. As an option, the calling user may be specifically informed that the called user has not answered the communication if a Reason header field set to cause 19 (no answer from user, user alerted) is included in the 480 (Temporarily unavailable) response. If a flash-hook event is reported by the media gateway, the AGCF stops the call-waiting timer and requests the media gateway to perform the following actions unless an explicit indication that the HOLD service is not provisioned to the user has been previously received as part of the profile delivery procedure: • Set the stream mode of the ephemeral termination to inactive. • Apply a dial tone. • Collect a switching order command. NOTE 1: In some networks, applying a dial tone and collecting an explicit switching order command is not required as the register recall is interpreted as a request to accept the waiting call. Subsequent AGCF procedures are executed as if an equivalent switching order command had been received from the user. The number of digits is provisioned in the AGCF. The AGCF also sends a re-INVITE request on the initial dialogue to hold the associated media stream, as described in TS 124 610 [8]. Processing of the switching order command depends on whether loose or tight coupling procedures are applied between the AGCF and the AS. Figure C.1 illustrates the loose coupling case while figure C.2 illustrates the tight-coupling case. NOTE 2: These figures do not take into account all possible service code commands that may be received from the user (e.g. service code command requesting that a waiting call be accepted and the active call be released). ETSI ETSI TS 183 043 V3.4.1 (2011-04) 97 The AGCF evaluates the Switch Order Command based on a provisioned mapping table. If the SOC indicates that the served user wishes to be connected to the waiting party, the AGCF performs the following actions: • Send a 200 OK response to the INVITE request received from the waiting party. • Request the media gateway to: - Modify the Remote Descriptor of the ephemeral termination according to the SDP information received from the waiting party. - Monitor the flash-hook event. If SOC indicates that the served user wishes to reject the waiting call, the AGCF performs the following actions: • Send a provisioned error response code (e.g. 603) to the INVITE request received from the waiting party. • Request the media gateway to: - Set the stream mode to send-receive. - Monitor the flash-hook event. • Send a re-INVITE request towards the held party (i.e. the party that has been held for the purpose of collecting the switching order command). The re-INVITE request is built as follows: - The Request-URI is set to the held party's identity. - The SDP description for the active media stream is set to a=sendrecv. Once the communication is established with the waiting party, the user may decide to switch back to the initial party, using a Register Recall followed by new switching order command. If the value of the switching order command indicates that the initial party is switched back, the AGCF performs the following actions: • Send a re-INVITE request towards the held party. The re-INVITE request is built as follows: - The Request-URI is set to the held party's identity. - The SDP description for the active media stream is set to a=sendrecv. • Send a re-INVITE request towards the active party. The re-INVITE request is built as follows: - The Request URI is set to the active party's identity. - The SDP description for the active media stream is set to a=sendonly. • Request the media gateway to: - Modify the Remote Descriptor of the ephemeral termination according to the SDP information associated with the held party. - Monitor the flash-hook event. If the feature code received from the internal MGC component does not match any known feature, the AGCF ignores the feature code and optionally requests the media gateway to play an error tone or an announcement to the served user. C.9.1.2 Actions at the AS at the terminating side Implementation of this service assumes that the AS providing the service is involved in all calls to/from the subscriber. Based on network operator option the AS determines whether the called user is busy. See note. If the option is not used then the AGCF/VGW determines the busy condition of the terminating party. If the called user is busy and has not subscribed to the call waiting service, the AS sends a 486 (Busy Here) response towards the calling party. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 98 If the called user is busy and has subscribed to the call waiting service, the AS builds an INVITE request using normal rules as for any incoming call. NOTE: Information for the handling of NDUB can be found in TS 124 628 [6], clause B.2. If the AS applies a "call is a waiting call announcement" in addition to the Alert-Info header field set to 'urn:alert:service:call-waiting' in the 180 Ringing sent towards the caller's PES Access point the AS includes the P-Early-Media header as described in clause 5.3.3.3. On receipt of a re-INVITE request with a SDP "sendonly" attribute, the AS interacts with an MRFC is order to play an announcement to the held party, in accordance with TS 124 628 [6]. On receipt of a re-INVITE request with the SDP attribute "sendrecv", the AS interacts with the MRFC to stop any ongoing announcement. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 99 AS MGF TE 1. INVITE (D2, SDP offer from C) 7. Re-INVITE (D1, SDP a=sendonly) AGCF 6. NOTIFY 2. H.248 interaction to apply Call Waiting toneand monitor flash-hook events 16. 200 OK (D2) 5. Flash hook detected 8. H.248 Stream Mode Set inactive 3. CW Tone 4. Register Recall 9. Interaction with held party (B) e.G announcement 10.H.248 interaction to apply dial tone and collect digits 11. Dialtone 12. Digits 13. Digits detected 14. NOTIFY 15 evaluate Switch order code 17 H.248 Remote Descriptor set to SDP-C 18. 603 Decline (D2) 19. Re-INVITE (D1, SDP a=sendrecv) 3a 180 Ringing (D2, Alert-Info: urn:alert:service: call-waiting) 20 H.248 Stream Mode set to send&receive 20a Stop announcement 4a. the AS has the possibility to generate a CW announcement. In this case the P-early-media header has to be added to the 180 Ringing response Figure C.1: Call Waiting with loose AGCF/AS coupling C.9.1.3 Actions at the VGW at the terminating side On receipt of an INVITE request for a busy subscriber, the VGW determines whether to trigger a call waiting procedure as specified in clause 7.3.1.3.2 for an AGCF. If a call waiting procedure is to be invoked, the VGW proceeds as follows: • Apply call waiting tone. • Monitor flash-hook events. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 100 • Send a 180 (Alerting) including an Alert-Info header field set to "urn:service:call-waiting" towards the AS. • Start a call-waiting timer. If the call-waiting timer expires then dependant on network operator policy the VGW sends a 486 (Busy Here) or 480 (Temporarily unavailable) response towards the Application Server. As an option, the calling user could be specifically informed that the called user has not answered the communication if a Reason header field set to cause 19 (no answer from user, user alerted) is included in the 480 (Temporarily unavailable) response. If a flash-hook event is received by the VGW it stops the no-answer timer and requests the media gateway to perform the following actions unless an explicit indication that the HOLD service is not provisioned to the user has been previously received as part of the profile delivery procedure: • Set the stream mode of the IP media termination to inactive. • Apply a dial tone. • Collect a switching order command. NOTE 1: In some networks, applying a dial tone and collecting an explicit switching order command is not required as the register recall is interpreted as a request to accept the waiting call. Subsequent VGW procedures are executed as if an equivalent switching order command had been received from the user. The number of digits is provisioned in the VGW. The VGW also sends a re-INVITE request on the initial dialogue to hold the associated media stream, as described in TS 124 610 [8]. Processing of the switching order command depends on whether loose or tight coupling procedures are applied between the VGW and the AS. Figure C.1 illustrates the loose coupling case while figure C.2 illustrates the tight-coupling case. NOTE 2: These figures do not take into account all possible service code commands that may be received from the user (e.g. service code command requesting that a waiting call be accepted and the active call be released). The VGW evaluates the Switch Order Command based on a provisioned mapping table. If the SOC indicates that the served user wishes to be connected to the waiting party, the VGW performs the following actions: • Send a 200 OK response to the INVITE request received from the waiting party. • The VGW procedures are: - Modify the IP media termination according to the SDP information received from the waiting party. - Monitor the flash-hook event. If SOC indicates that the served user wishes to reject the waiting call, the VGW performs the following actions: • Send a provisioned error response code (e.g. 603) to the INVITE request received from the waiting party. • The VGW. - Set the stream mode of the IP media termination to send-receive. - Monitor the flash-hook event. • Send a re-INVITE request towards the held party (i.e. the party that has been held for the purpose of collecting the switching order command). The re-INVITE request is built as follows: - The Request-URI is set to the held party's identity. - The SDP description for the active media stream is set to a=sendrecv. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 101 Once the communication is established with the waiting party, the user may decide to switch back to the initial party, using a Register Recall followed by new switching order command. If the value of the switching order command indicates that the initial party is switched back, the VGW performs the following actions: • Send a re-INVITE request towards the held party. The re-INVITE request is built as follows: - The Request-URI is set to the held party's identity. - The SDP description for the active media stream is set to a=sendrecv. • Send a re-INVITE request towards the active party. The re-INVITE request is built as follows: - The Request URI is set to the active party's identity. - The SDP description for the active media stream is set to a=sendonly. • The VGW: - Modify the IP media termination according to the SDP information associated with the held party. - Monitor the flash-hook event. If the feature code received does not match any known feature, the VGW ignores the feature code and optionally play an error tone or an announcement to the served user. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 102 S-CSCF P-CSCF VGW 2. INVITE 1. INVITE 5. INVITE AS 3. INVITE 4. INVITE 9a. the AS has the possibility to generate a CW announcement 9. 180 Ringing Alert-Info: urn:alert:service: call-waiting 10. 180 Ringing Alert-Info: urn:alert:service: call-waiting 6. 180 Ringing Alert-Info: urn:alert:service: call-waiting 7. 180 Ringing Alert-Info: urn:alert:service: call-waiting 8. 180 Ringing Alert-Info: urn:alert:service: call-waiting 11. 200 OK 12. 200 OK 13. 200 OK 14. 200 OK 15. 200 OK 6a. Possibility for User B to react: release session, invoke HOLD, ...] 6a. CW Tone Figure C.1A: Call Waiting with loose VGW coupling C.9.2 Void C.9.2.1 Void C.9.2.2 Void C.9.3 General for Tight coupling C.9.3.1 Actions at the AGCF at the terminating side On receipt of an INVITE D2 request for a busy subscriber, the AGCF determines whether to trigger a call waiting procedure as specified in clause 7.3.1.3.2. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 103 If a flash-hook event is reported by the media gateway as shown in figure C.1B, the AGCF requests the media gateway to set the stream mode of the ephemeral termination to inactive. The AGCF sends an INVITE (flash) on dialogue D4 to the AS and await receipt of 200 OK (Invite) and when this is received it sends an ACK. The AGCF then sends a 200 OK (Invite) on dialogue D2 and await receipt of the ACK. The AGCF then awaits receipt of a Re-INVITE on dialogue D2, (which allows re-negotiation of the SDP between user A/B and user C) responds with a 200 OK (Invite) and awaits receipt of an ACK and a BYE (D4). On receipt of this BYE it sends a 200 OK (Bye). C.9.3.2 Actions at the AS at the terminating side Implementation of this service assumes that the AS providing the service is involved in all calls to/from the subscriber. The AS determines the busy condition of the called user based on the procedures described in TS 124 628 [6]. If the called user is busy and has not subscribed to the call waiting service, the AS sends a 486 (Busy Here) response towards the calling party. NOTE 1: The procedures for NDUB are out of scope of the specification of CW procedures. Information for the handling of NDUB can be found in TS 124 628 [6], clause B.2. If the called user is approaching 'ndbu' and has subscribed to the call waiting service, the AS builds an INVITE D2 request using normal rules as for any incoming call. The INVITE request may include as a network operator option a CW MIME body, in compliance with TS 124 615 [44]. On receipt of a 180 (Ringing) response, the AS inserts an Alert-Info header field set to "urn:service:call-waiting" into the 180 and interacts with an MRFC in order to play an announcement to the calling party, and starts a timer (which is stopped on receipt of an INVITE (flash)) to determine the overall call waiting service period (if the CW timer expires, the AS sends a CANCEL (D2) to the AGCF/VGW). When (if) an INVITE (flash) (D4) is received the AS sends a 200 OK response (as this is Simplified Call Waiting) and await receipt of the ACK. The AS awaits receipt of a 200 OK (Invite) on dialogue D2, and respond with an ACK. The AS then re-arranges the bearers to connect the calling party (C) to the called party (A/B) by sending a Re-INVITE (D2) with no SDP to the AGCF/VGW. It then awaits receipt of the 200 OK (Invite) containing the SDP of the A/B party and when received it sends an ACK to the AGCF/VGW containing the SDP of the C party. The AS can also arrange for an announcement to be played to the held party (B/A) via an MRFC/MRFP and arranges for a BYE (D4) to be sent to the AGCF/VGW. The call flow for this service (when accepting the waiting call with a RECALL) is shown in figure C.1B and is described in the previous paragraphs of this clause. The call flow for this service (when accepting the waiting call by going ON HOOK) is shown in figure C.1B. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 104 AGCF AS 3. INVITE 2. INVITE (D2, SDP offer from C) 5. Call Waiting tone burst +FSK S-CSCF 4. INVITE 6. 180 (Ringing) 11. RECALL 10. 180 Ringing Alert-Info: urn:alert:service: call-waiting 14. 200 OK (D4) 1. Line Busy in active phase of incoming or outgoing call 7. 180 (Ringing) 8. 180 (Ringing) 5. Call Waiting tone burst 9. AS initiate Announcement played towards user C 12. INVITE (flash@domain D4) 13. INVITE (flash@domain D4) 15. 200 OK (D4) 16. ACK (D4) 17. ACK 18. 200 OK (D2) 19. 200 OK (D2) 20. 200 OK (D2) 21. 200 OK (D2) Analogue UE 22. ACK (D2) 23. ACK 24. ACK 25. ACK Rearrangement by the AS of the Bearers of Dialog 1 with Re-INVITE on D1 26. re-INVITE (D2, no SDP) 27. re-INVITE (D2, no SDP) 31. ACK (D2) (SDP) 30. ACK (D2) (SDP) 28. 200 OK (D2) (SDP) 29. 200 OK (D2) (SDP) 32 BYE (D4) 34. 200 OK (BYE) 33 BYE (D4) 35. 200 OK (BYE) NOTE: Not all messages (like 100 Trying) and Precondition an PRACK cycle for 180 Ringing are shown in the flow. Figure C.1B: Customer Presses Recall ETSI ETSI TS 183 043 V3.4.1 (2011-04) 105 AGCF AS 3. INVITE 2. INVITE (D2, SDP offer from C) 5. Call Waiting tone burst +FSK S-CSCF 4. INVITE 6. 180 Ringing (D2, SDP A) 11a. AN HOOK 10. 180 Ringing Alert-Info: urn:alert:service: call-waiting 14. 200 OK (D1) 1. Line Busy in active phase of incoming or outgoing call (A/B) 7. 180 Ringing (D2) 8. 180 Ringing (D2) 11. Call Waiting tone burst Tim er 9. AS initiate Announcement played towards user C 12. BYE (D1) 15. 200 OK (D1) 19. ACK (D2) 20. ACK (D2) 21. 183 Session Progress (D3, SDP A/B) 23. PRACK (SDP C) Tim er (in AS) Analogue UE 13. BYE (D1) 15. 410 Gone (D2) 16. 410 Gone (D2) 17. INVITE (D3,no SDP offer) 18. INVITE (D3,no SDP offer) 22. 183 Session Progress (D3, SDP A/B) 24. PRACK (SDP C) 9. AS initiate Announcement played towards user C 10a PRACK cycle with PRACK and 200 OK (PRACK) NOTE: Not all messages (like 100 Trying) and Preconditions "which may be optionally included are shown in the flow". Figure C.1C: Called Customer goes ON HOOK NOTE 2: A no answer timer on the AGCF/VGW to remove the dependence of the AGCF/VGW network on the AS network may be defined in a future Release. Figure C.2: Void C.9.3.3 Actions at the VGW at the terminating side On receipt of an INVITE D2 request for a busy subscriber the VGW determines whether to trigger a call waiting procedure as specified in clause 7.3.1.3.2. If a call waiting procedure is to be triggered, the VGW performs the following actions: • Apply call waiting tone. • Monitor flash-hook events. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 106 • Send a 180 (Ringing) towards the AS. If a flash-hook event is reported as shown in figure C.1B, the VGW sets the IP media termination to inactive. The VGW sends an INVITE (flash) on dialogue D4 to the AS and await receipt of 200 OK (Invite) and when this is received it sends an ACK. The VGW then sends a 200 OK (Invite) on dialogue D2 and await receipt of the ACK. The VGW then awaits receipt of a Re-INVITE on dialogue D2, (which allows re-negotiation of the SDP between user A/B and user C) responds with a 200 OK (Invite) and awaits receipt of an ACK and a BYE (D4). On receipt of this BYE it sends a 200 OK (Bye). S-CSCF P-CSCF VGW 2. INVITE 1. INVITE 5. INVITE [CW indication] AS 3. INVITE [CW indication] 4. INVITE [CW indication] 9a. the AS has the possibility to generate a CW announcement 9. 180 Ringing Alert-Info: urn:alert:service: call-waiting 10. 180 Ringing Alert-Info: urn:alert:service: call-waiting 6. 180 Ringing 7. 180 Ringing 8. 180 Ringing 2a. the AS determines the ‚approaching NDUB’ condition and inserts a CW indication in the INVITE request 11. 200 OK 12. 200 OK 13. 200 OK 14. 200 OK 15. 200 OK 8a. the AS inserts a Alert-Info header with a CW urn into the 180 Ringing response 6a. Possibility for User B to react: release session, invoke HOLD, ...] not part of CW 6a. CW Tone Figure C.2A: Call Waiting with tight VGW coupling ETSI ETSI TS 183 043 V3.4.1 (2011-04) 107 C.10 Incoming Call Barring C.10.1 Activation/Deactivation/Interrogation C.10.1.1 Actions at the AGCF Activation, deactivation and interrogation of incoming call barring is performed using service code commands as described in ETS 300 738 [12]. On receipt of a service code command, the AGCF sends an INVITE request as described in clause C.1. C.10.1.2 Actions at the AS On receipt of the INVITE request that includes a service code command as Request-URI, the AS proceeds as described in clause C.1. C.10.1.3 Actions at the VGW Activation, deactivation and interrogation of incoming call barring is performed using service code commands as described in ETS 300 738 [12]. On receipt of a service code command, the AGCF sends an INVITE request as described in clause C.1. C.10.2 Invocation C.10.2.1 Actions at the Originating AGCF The originating AGCF is not involved in the invocation of the service. C.10.2.2 Actions at the Originating AS The originating AGCF is not involved in the invocation of the service. C.10.2.3 Actions at the Terminating AS On receipt of an INVITE request from a calling user, if incoming call barring is activated, the AS checks the P-Asserted-Identity against the list of allowed/forbidden calling parties. The rules and information used by the AS to evaluate whether the call is accepted are operator dependent. They may be compatible subset of the rules described in TS 124 611 [27]. If the call is rejected, the AS notifies the calling user by sending a 603 (Decline) response. Additionally, before terminating the communication an announcement can be provided to the originating user. The procedure for invoking an announcement in the call establishment phase is described within TS 124 628 [6]. C.10.2.4 Actions at the Terminating AGCF The terminating AGCF is not involved in the provision of the service. C.10.2.5 Actions at the Originating VGW The originating VGW is not involved in the invocation of the service. C.10.2.6 Actions at the Terminating VGW The terminating VGW is not involved in the provision of the service. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 108 C.11 Malicious Call Identification (Loose coupling) C.11.1 Actions at the Originating AGCF The AGCF at the originating side is not involved in the provision of this service. C.11.2 Actions at the Originating AS The AS at the originating side is not involved in the provision of this service. C.11.3 Actions at the Terminating AS Support of the Malicious Call Identification (MCID) service requires that the AS providing the service is involved in all incoming calls to the served user. The AS registers the details of the last incoming call in a special record upon reception of either: • A re-INVITE request with a Request-URI set to the served user's identity and a MCID XML document with an McidRequestIndicator set to 1. • A re-INVITE request with a Request-URI set to the served user's identity without any message body. In the later case, other services that could use the re-INVITE not containing any message body as service invocation is disabled. Processing of this record is outside the scope of standardization. C.11.4 Actions at the Terminating AGCF The AGCF detects invocation of MCID and generates a re-INVITE request as described in clause B.4.2.2.2. As a network option, the AGCF may use the annex A Profile Delivery mechanism for obtaining the subscriber MCID subscription status (provisioned/withdrawn). C.11.5 Actions at the Originating VGW The VGW at the originating side is not involved in the provision of this service. C.11.6 Actions at the Terminating VGW The VGW detects invocation of MCID and generates a re-INVITE request as described in clause B.4.2.2.2. As a network option, the VGW may use the annex A Profile Delivery mechanism for obtaining the subscriber MCID subscription status (provisioned/withdrawn). C.11A Malicious Call Identification (Tight coupling) C.11A.1 Actions at the Originating AGCF The AGCF at the originating side is not involved in the provision of this service. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 109 C.11A.2 Actions at the Originating AS The AS at the originating side is not involved in the provision of this service. C.11A.3 Actions at the Terminating AS Support of the Malicious Call Identification (MCID) service requires that the AS providing the service is involved in all incoming calls to the served user. On receipt of an INVITE request containing a Request-URI representing a flash hook event (e.g. flash@pes scc.operator.com), the AS may either, as a network option: • Interpret the INVITE request as a request for invocation of the MCID service, in which case other services using flash-hook as means for invocation are disabled for this terminating user. • Instruct another entity under its control such as a Media Resource Function to perform digit collection as described in annex G. Alternatively it may instruct the AGCF/VGW to collect a special service code. NOTE: The AS procedure for requesting an AGCF/VGW to collect digits is for further study. When the AS has sufficient information to determine that invocation of the MCID service is requested, the AS registers the details of the last incoming call in a special record. Processing of this record is outside the scope of standardization. C.11A.4 Actions at the Terminating AGCF The MCID service is invoked during the active phase of the communication or after the active phase for a limited period, using either Register Recall or a Register Recall followed by a special service code. On receipt of a flash-hook event, the AGCF sends an INVITE request to the AS as specified in clause B.4.2.2.3. NOTE: As a network option, the AGCF may be instructed by the AS to collect a special service code. C.11A.5 Actions at the Originating VGW The VGW at the originating side is not involved in the provision of this service. C.11A.6 Actions at the Terminating VGW The MCID service is invoked during the active phase of the communication or after the active phase for a limited period, using either Register Recall or a Register Recall followed by a special service code. On receipt of a flash-hook event, the VGW sends an INVITE request to the AS as specified in clause B.4.2.2.3. NOTE: As a network option, the VGW may be instructed by the AS to collect a special service code. C.12 Message Waiting Indicator C.12.1 Actions at the AGCF On receipt of a NOTIFY request reporting the "message-summary" event, the AGCF requests the following actions from the media gateway: • Modify the default dial tone. • Send a Message Waiting Indicator message (see ES 200 659-3 [10]) using the H.248 andisp/data signal. Generation of the Message Waiting Indicator message by the AGCF is described in annex D. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 110 C.12.2 Actions at the AS The AS implements the procedures described in TS 124 606 [26]. C.12.3 Actions at the VGW On receipt of a NOTIFY request reporting the "message-summary" event, the VGW: • Modify the default dial tone. Send a Message Waiting Indicator message (see ES 200 659-3 [10]). Generation of the Message Waiting Indicator message by the VGW is described in annex D. C.13 Outgoing Call Barring C.13.1 Activation/Deactivation/Interrogation C.13.1.1 Actions at the AGCF Activation and deactivation of outgoing call barring is performed using service code commands as described in ETS 300 738 [12]. On receipt of a service code command, the AGCF sends an INVITE request as described in clause C.1. C.13.1.2 Actions at the AS On receipt of the INVITE request that includes a service code command as Request-URI, the AS proceeds as described in clause C.1. C.13.1.3 Actions at the VGW Activation and deactivation of outgoing call barring is performed using service code commands as described in ETS 300 738 [12]. On receipt of a service code command, the VGW sends an INVITE request as described in clause C.1. C.13.2 Invocation C.13.2.1 Actions at the Originating AGCF The originating AGCF is not involved in the invocation of the service. C.13.2.2 Actions at the Originating AS On receipt of an INVITE request from a calling user, if outgoing call barring is activated, the AS checks the Request-URI against the list of allowed/forbidden called destinations. The rules and information used by the AS to evaluate whether the call is accepted are operator dependent. They may be compatible subset of the rules described in TS 124 611 [27]. If the call is rejected, the AS notifies the calling user by sending a 603 (Decline) response. Additionally, before terminating the communication an announcement can be provided to the originating user. The procedure for invoking an announcement in the call establishment phase is described within TS 124 628 [6]. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 111 C.13.2.3 Actions at the Terminating AS The terminating AS is not involved in the provision of the service. C.13.2.4 Actions at the Terminating AGCF The terminating AGCF is not involved in the provision of the service. C.13.2.5 Actions at the Originating VGW The originating VGW is not involved in the invocation of the service. C.13.2.6 Actions at the Terminating VGW The terminating VGW is not involved in the provision of the service. C.14 Three Party Service C.14.0 General Processing of the switching order command depends on whether loose or tight coupling procedures are applied between the AGCF and the AS. Moreover, in loose coupling case, two methods can be used: the INVITE method, described in clause C.14.2, and the REFER method, described in clause C.14.2A. Figure C.4 illustrates the loose coupling case with the INVITE method while figure C.5 illustrates the loose coupling case with the REFER method. The tight coupling case is described in clause C.14.3. For the transport of dialled digits identifying the third party to be called Overlap Signalling may apply. If Overlap Signalling is supported between the AGCF/VGW and the Application Server at the originating side 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. C.14.1 General for Loosely Coupled Options C.14.1.1 Actions at the AGCF at the service invocation side The service is invoked during a stable 2 party call (without any waiting/held call) using the Register Recall. Figure C.3 illustrates the message sequence between the AGCF and the AS. On receipt of a NOTIFY request reporting a flash-hook event, the AGCF performs the following actions unless an explicit indication that the HOLD service is not provisioned to the user has been previously received as part of the profile delivery procedure: • Request the media gateway to play a dial tone on the physical and collect digits. • Send a re-INVITE request to place the current call on hold. On receipt of the dialled digits, the AGCF opens a new dialogue by sending an INVITE request with the following elements: • The dialled digits used as a Request-URI. • An SDP Offer for a voice call. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 112 The AGCF then requests the media gateway to perform the following actions: • monitor the flash-hook event; • set the stream-mode of the ephemeral termination to "inactive"; and • waits for a n incoming SIP message. On receipt of 180 (Ringing) without P-Early-Media header or with a P-Early-Media header set to a value different from "sendonly" or from "sendreceive", the AGCF performs the following actions: • Request the media gateway to play a ringback tone. On receipt of 180 (Ringing) or 183 (Session Progress) with a P-Early-Media header set to "sendonly" or "sendreceive", the AGCF performs the following actions: • Request the media gateway to modify the configuration of the ephemeral termination so as to ensure that the end user will perceive early media. On receipt of an SDP Answer in a 200 (OK) or in one of the above provisional responses, the AGCF performs the following actions: • Request the media gateway to modify the Remote Descriptor of the ephemeral termination associated with the physical termination representing the analogue line. On receipt of a re-INVITE request requesting a call to be placed on hold, the AS applies the procedures described in TS 124 610 [8]. C.14.1.2 Actions at the AS at the service invocation side Support of this service requires that all outgoing and incoming calls to the served user be handled by the same AS. On receipt of a service code command requesting a three party conference, the AS may check that this request is compatible with subscription data held in the user profile. If the user is not entitled to use this service, the AS interacts with an MRFC is order to play an announcement to the invoker and sends a negative response to the re-INVITE request. On receipt of a re-INVITE request with an SDP "a=sendonly" attribute, the AS may interact with an MRFC in order to play an announcement to the held party, in accordance with TS 124 628 [6]. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 113 MG AGCF AS TE (1) H.248 interaction to monitor flash-hook events (4) NOTIFY (2) Register Recall (8) H.248 interaction to apply dial tone and collect digits (9) Dial Tone (10) Digits (11)Digit(s) detected (12) NOTIFY (17) H.248 Remote Descriptor set to SDP-C (3) Flash-hook detected (13) INVITE (D2, digits@pes) (5) RE-INVITE (D1, SDP a=send-only) (7) Interaction with held party (e.g. announcement) (6) H.248 Stream Mode Set to send-only (14) 183 Session Progress (D2) (15) 180 Alerting (D2) (16) 200 OK (D2, SDP-C) (18) H.248 interaction for monitoring flash-hook events Figure C.3: Initiating a 3-Party call C.14.1.3 Actions at the VGW at the service invocation side The service is invoked during a stable 2 party call (without any waiting/held call) using the Register Recall. Figure C.3 illustrates the message sequence between the VGW and the AS. On receipt of a flash-hook event, the VGW performs the following actions unless an explicit indication that the HOLD service is not provisioned to the user has been previously received as part of the profile delivery procedure: • Play a dial tone on the physical and collect digits. • Send a re-INVITE request to place the current call on hold. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 114 On receipt of the dialled digits, the VGW opens a new dialogue by sending an INVITE request with the following elements: • The dialled digits used as a Request-URI. • An SDP Offer for a voice call. The VGW then perform the following actions: • monitor the flash-hook event; • set the stream-mode of the IP media termination to "inactive"; and • waits for an incoming SIP message. On receipt of 180 (Ringing) without P-Early-Media header or with a P-Early-Media header set to a value different from "sendonly" or from "sendreceive", the VGW performs the following actions: • Play a ringback tone. On receipt of 180 (Ringing) or 183 (Session Progress) with a P-Early-Media header set to "sendonly" or "sendreceive", the VGW performs the following actions: • Modify the configuration of the IP media termination so as to ensure that the end user will perceive early media. On receipt of an SDP Answer in a 200 (OK) or in one of the above provisional responses, the VGW performs the following actions: • Modify the IP media termination associated with the physical termination representing the analogue line. On receipt of a re-INVITE request requesting a call to be placed on hold, the AS applies the procedures described in TS 124 610 [8]. Processing of the switching order command depends on whether loose or tight coupling procedures are applied between the VGW and the AS. Moreover, in loose coupling case, two methods can be used: with the INVITE method, described in clause C.14.2, and with the REFER method, described in clause C.14.2A. Figure C.4 illustrates the loose coupling case with the INVITE method while figure C.5 illustrates the loose coupling case with the REFER method. The tight coupling case is described in clause C.14.3. C.14.2 Loose coupling Option1 with INVITE method C.14.2.1 Actions at the AGCF at the invoking side The AGCF evaluates the Switch Order Command based on a provisioned mapping table. If the feature code received from the internal MGC component does not match any known feature, the AGCF ignores the feature code and optionally request the media gateway to play an error tone or an announcement to the served user. As a network option the AGCF can evaluate a Switch Order Command based on a provisioned mapping table to correct a preceding Switch Order Command that was wrong. If the SOC indicates that the user wishes to establish a 3-party conference with the held parties. the AGCF performs the following actions unless an explicit indication that the 3PTY service is not provisioned to the user has been previously received as part of the profile delivery procedure: • Request the media gateway to: - Add a termination to the current context based on SDP information associated with the held party. - Monitor the flash-hook event. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 115 • Send a re-INVITE request towards the first held party (i.e. the party that was already held when the flash-hook event was detected). The re-INVITE request is built as follows: - The Request URI is set to the held party's identity. - The SDP description is set to a=sendrecv. The address and port are set according to the contents of the local descriptor of the new termination. • Send a re-INVITE request towards the second held party (i.e. the party that has been held for the purpose of collecting the Switch Order Command). The re-INVITE request is built as follows: - The Request URI is set to the held party's identity. - The SDP description is set to a=sendrecv. Once the 3-party call is established with the waiting party, processing of the flash-hook event is similar to the call waiting service. If SOC indicates that the served user wishes to reject one of the parties, the AGCF performs the following actions: • Send a BYE request towards the held party. • Request the media gateway to: - Remove the corresponding ephemeral termination. - Monitor the flash-hook event. C.14.2.2 Actions at the Originating AS at the invoking side On receipt of a re-INVITE request with an SDP attribute "sendonly", the AS may interact with an MRFC in order to play an announcement to the held party, in accordance with TS 124 628 [6]. On receipt of a re-INVITE request with the SDP attribute "sendrecv", the AS interacts with the MRFC to stop any ongoing announcement. On receipt of a BYE request, the AS releases the dialogue with the associated party. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 116 MG AGCF AS TE (3) NOTIFY (1) (5) H.248 Remote descriptor set to SDP-C Digits (2) Digits detected (7) re-INVITE (D1, SDP a=sendrecv) (4) Evaluate switch order code (10) 200 OK (6) H.248 interaction for monitoring flash-hook events (9) Stop announcement (8) H.248 Stream mode set to send&receive (11) re-INVITE (D2, SDP a=sendrecv) (13) Stop announcement (12) H.248 Stream mode set to send&receive (13) 200 OK Figure C.4: 3PTY with INVITE method C.14.2.3 Actions at the VGW at the invoking side The VGW evaluates the Switch Order Command based on a provisioned mapping table. If the feature code received does not match any known feature, the VGW ignores the feature code and optionally play an error tone or an announcement to the served user. If the SOC indicates that the user wishes to establish a 3-party conference with the held parties. The VGW performs the following actions unless an explicit indication that the 3PTY service is not provisioned to the user has been previously received as part of the profile delivery procedure: • The VGW: - Add a termination to the current context based on SDP information associated with the held party. - Monitor the flash-hook event. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 117 • Send a re-INVITE request towards the first held party (i.e. the party that was already held when the flash-hook event was detected). The re-INVITE request is built as follows: - The Request URI is set to the held party's identity. - The SDP description is set to a=sendrecv. The address and port are set according to the IP media termination. • Send a re-INVITE request towards the second held party (i.e. the party that has been held for the purpose of collecting the Switch Order Command). The re-INVITE request is built as follows: - The Request URI is set to the held party's identity. - The SDP description is set to a=sendrecv. Once the 3-party call is established with the waiting party, processing of the flash-hook event is similar to the call waiting service. If SOC indicates that the served user wishes to reject one of the parties, the VGW performs the following actions: • Send a BYE request towards the held party. • The VGW: - Remove the corresponding IP media termination. - Monitor the flash-hook event. C.14.2A Loose coupling Option 2 with REFER method C.14.2A.1 Actions at the AGCF at the invoking side The AGCF evaluates the Switch Order Command based on a provisioned mapping table. If the feature code received from the internal MGC component does not match any known feature, the AGCF ignores the feature code and optionally request the media gateway to play an error tone or an announcement to the served user. As a network option the AGCF can evaluate a Switch Order Command based on a provisioned mapping table to correct a preceding Switch Order Command that was wrong. If the SOC indicates that the user wishes to establish a 3-party conference with the held parties, the AGCF performs the following actions unless an explicit indication that the 3PTY service is not provisioned to the user has been previously received as part of the profile delivery procedure: • Request the media gateway to: - Add a termination to the current context based on SDP information associated with the held party. - Monitor the flash-hook event. • Send an initial INVITE with the To and the Request-URI containing the Conference bridge URI provisioned in the AGCF. • Send a REFER request within the existing dialog with user B with the Refer-To header containing the Conference bridge contact URI and the dialog associated with the B party. The ReferredBy header field is set to the served user's identity. • Send a REFER request within the existing dialog with user C with the Refer-To header containing the Conference bridge contact URI and the dialog associated with the C party. The ReferredBy header field is set to the served user's identity. NOTE: The REFER sent is built as specified in RFC 3515 [i.4] without any body. Unlike specified in RFC 3515 [i.4] the terminal will not receive any NOTIFY (see RFC 4488 [i.3]). ETSI ETSI TS 183 043 V3.4.1 (2011-04) 118 When the SIP end-point receives 202 ACCEPTED response to each sent REFER request, it: • performs conference establishment notification; • considers only the call established with the conference bridge as active. The SIP end-point will receive a BYE message in both call established. Once the 3-party call is established with the waiting party, processing of the flash-hook event is similar to the call waiting service. If SOC indicates that the served user wishes to reject one of the parties, the AGCF performs the following actions: • Send a BYE request towards the held party. • Request the media gateway to: - Remove the corresponding ephemeral termination. - Monitor the flash-hook event. C.14.2A.2 Actions at the Originating AS at the invoking side Upon reception of the INVITE addressed to the conference bridge, the AS forwards to the MRFC the INVITE request with SDP offer populated with user information. Upon reception of the first REFER, the AS: • Sends an INVITE message to the bridge with SDP offer populated with first held party information. • Sends a re-INVITE request towards the first held party (i.e. the party that was already held when the flash-hook event was detected). The re-INVITE request is built as follows: - The Request URI is set to the held party's identity. - The SDP description is set to a=sendrecv. The address and port are set according to the contents of the local descriptor of the new termination. • Sends a BYE message to the served-user for end his call with the first held party. Upon reception of the other REFER, the AS: • Sends an INVITE message with SDP offer populated with the second held party information. • Sends a re-INVITE request towards the second held party (i.e. the party that has been held for the purpose of collecting the Switch Order Command). The re-INVITE request is built as follows: - The Request URI is set to the held party's identity. - The SDP description is set to a=sendrecv. • Sends a BYE message to the served-user for end his call with the second held party. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 119 MG AGCF AS TE (3)NOTIFY (1) (5) H.248 Remote descriptor set to SDP-C Digits (2)Digits detected (7) INVITE (Conf Bridge URI) (4) Evaluate switch order code (9) 200 OK (6) H.248 interaction for monitoring flash-hook events (10) REFER (ReferTo: Conf Bridge URI, replaces dialog B) (14) BYE (A) (8) INVITE (MRFC) (11) 202 Accepted (12) INVITE (MRFC) (13) re-INVITE (B, SDP a=sendrecv) (15) REFER (ReferTo: Conf Bridge URI, replaces dialog C) (16) 202 Accepted (17) INVITE (MRFC) (18) re-INVITE (C, SDP a=sendrecv) (19) BYE (A) Figure C.5: 3PTY with REFER method C.14.2A.3 Actions at the VGW at the invoking side The VGW evaluates the Switch Order Command based on a provisioned mapping table. If the feature code received does not match any known feature, the VGW ignores the feature code and optionally play an error tone or an announcement to the served user. If the SOC indicates that the user wishes to establish a 3-party conference with the held parties, the VGW performs the following actions unless an explicit indication that the 3PTY service is not provisioned to the user has been previously received as part of the profile delivery procedure: • The VGW: - Add a termination to the current context based on SDP information associated with the held party. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 120 - Monitor the flash-hook event. • Send an initial INVITE with the To and the Request-URI containing the Conference bridge URI provisioned in the VGW. • Send a REFER request within the existing dialog with user B with the Refer-To header containing the Conference bridge contact URI and the dialog associated with the B party. The ReferredBy header field is set to the served user's identity. • Send a REFER request within the existing dialog with user C with the Refer-To header containing the Conference bridge contact URI and the dialog associated with the C party. The ReferredBy header field is set to the served user's identity. NOTE: The REFER sent is built as specified in RFC 3515 [i.4] without any body. Unlike specified in RFC 3515 [i.4] the terminal will not receive any NOTIFY (see RFC 4488 [i.3]). When the SIP end-point receives 202 ACCEPTED response to each sent REFER request, it: • performs conference establishment notification; • consider only the call established with the conference bridge as active. The SIP end-point will receive a BYE message in both call established. Once the 3-party call is established with the waiting party, processing of the flash-hook event is similar to the call waiting service. If SOC indicates that the served user wishes to reject one of the parties, the VGW performs the following actions: • Send a BYE request towards the held party. • The VGW proceed with the following procedures: - Remove the corresponding IP media termination. - Monitor the flash-hook event. C.14.2B Loose coupling Option 3 by sending INVITE request with URI list C.14.2B.1 Actions at the AGCF at the invoking side The AGCF evaluates the Switch Order Command based on a provisioned mapping table. If the feature code received does not match any known feature, the AGCF ignores the feature code and optionally to play an error tone or an announcement to the served user. Or initiate an announcement due to the procedures described within TS 124 628 [6]. As a network option the AGCF can evaluate a Switch Order Command based on a provisioned mapping table to correct a preceding Switch Order Command that was wrong. If the SOC indicates that the user wishes to establish a 3-party conference with the held parties the AGCF performs the following actions unless an explicit indication that the 3PTY service is not provisioned to the user has been previously received as part of the profile delivery procedure: AGCF creates a conference and invites user B and user C to the conference by sending an INVITE to the Conference Factory URI and including URI list in the INVITE request, AGCF indicates the certain dialogs which be re-used for this conference in the uri list by ? mechanism. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 121 INVITE CONF AS To: CONF AS From: A Require: recipient-list-invite Content-Type: application/resource-lists+xml Content-Disposition: recipient-list <?xml version="1.0" encoding="UTF-8"?> <resource-lists xmlns="urn:ietf:params:xml:ns:resource-lists" xmlns:cp="urn:ietf:params:xml:ns:copyControl"> <list> <entry uri="B?Call-ID=1a&From=A%3Btag%3Da&To=B%3Btag%3Db" cp:copyControl="to"/> <entry uri="C?Call-ID=2a&From=A%3Btag%3Da&To=C%3Btag%3Dc" cp:copyControl="to"/> </list> </resource-lists> Once the 3-party call is established with the waiting party, processing of the flash-hook event is similar to the call waiting service. If SOC indicates that the served user wishes to reject one of the parties, the AGCF performs the following actions: • Send a BYE request towards the Conference Server. • Send a BYE request towards on the held dialog of the party that should be disconnected. • Send a Re-INVITE on the other held party to reactivate that dialog. • Monitor the flash-hook event. C.14.2B.2 Actions at the Originating AS at the invoking side AS verifies if the dialogs in URI list matches to a partial dialog which AS already involved, In the case of a match the AS use this dialog ID information to send re-INVITE request to UA-B and UA-C in the partial dialogs between the AS and the invited users in order to connect the media of the invited users to the MRFP. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 122 Figure C.6: Loose coupling 3PTY with INVITE method C.14.2B.3 Actions at the VGW at the invoking side The AGCF evaluates the Switch Order Command based on a provisioned mapping table. If the feature code received does not match any known feature, the AGCF ignores the feature code and optionally to play an error tone or an announcement to the served user. Or initiate an announcement due to the procedures described within TS 124 628 [6]. As a network option the AVGW can evaluate a Switch Order Command based on a provisioned mapping table to correct a preceding Switch Order Command that was wrong. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 123 If the SOC indicates that the user wishes to establish a 3-party conference with the held parties the AGCF performs the following actions unless an explicit indication that the 3PTY service is not provisioned to the user has been previously received as part of the profile delivery procedure: VGW creates a conference and invites user B and user C to the conference by sending an INVITE to the Conference Factory URI and including URI list in the INVITE request, VGW indicates the certain dialogs which be re-used for this conference in the uri list by ? mechanism. INVITE CONF AS To: CONF AS From: A Require: recipient-list-invite Content-Type: application/resource-lists+xml Content-Disposition: recipient-list <?xml version="1.0" encoding="UTF-8"?> <resource-lists xmlns="urn:ietf:params:xml:ns:resource-lists" xmlns:cp="urn:ietf:params:xml:ns:copyControl"> <list> <entry uri="B?Call-ID=1a&From=A%3Btag%3Da&To=B%3Btag%3Db" cp:copyControl="to"/> <entry uri="C?Call-ID=2a&From=A%3Btag%3Da&To=C%3Btag%3Dc" cp:copyControl="to"/> </list> </resource-lists> Once the 3-party call is established with the waiting party, processing of the flash-hook event is similar to the call waiting service. If SOC indicates that the served user wishes to reject one of the parties, the AGCF performs the following actions: • Send a BYE request towards the Conference Server. • Send a BYE request towards on the held dialog of the party that should be disconnected. • Send a Re-INVITE on the other held party to reactivate that dialog. • Monitor the flash-hook event. C.14.3 General for Tight coupling C.14.3.1 Actions at the AGCF at the originating side On receipt of a notification of Register RECALL from the AGCF, the AGCF opens a new dialogue (D3) and sends an INVITE (flash) to an originating AS. This INVITE includes the following: • The Request URI is structured as follows: - A user part containing "flash". - A domain name that together with the user part provides sufficient information for the AS Network to forward the request to the appropriate AS, based on Initial Filter Criteria stored in the user profile, e.g."flash@pes.operator.com" • A From header containing the public identity of the line on which the RECALL occurred. • An SDP offer for a speech call. The AGCF now awaits receipt of a 484 Address Incomplete from the originating AS, and when received the AGCF takes the following actions: • Requests the A-MGW to play Dial Tone and collect one digit. • Sends an INVITE (D3) containing this single digit (as this is a Recall sequence with more than one active dialogue) and await receipt of 200 OK (Invite) or a failure response code. This INVITE is built in the same way as the previous INVITE except that the dialled digit replaces "flash". ETSI ETSI TS 183 043 V3.4.1 (2011-04) 124 The AGCF then awaits a re-INVITE (D2) with the SDP of a Media Server in the AS Network (acting as a 3 party bridge) and when received it takes the following actions: • Sends an instruction to the A-MGW to change the address to which RTP packets are sent and from which they are received (e.g. it modifies the H.248 Remote Descriptor). Sends a 200 OK (Invite) to the AS, awaits receipt of a BYE to end dialogue D3, and when this is received it sends a 200 OK (Bye). C.14.3.2 Actions at the Originating AS at the originating side On receipt of an INVITE (flash) (D3) the AS takes the following actions: • Sends a 484 Address Incomplete response to the AGCF and awaits receipt of an ACK. • Awaits receipt of an INVITE (D3) with a single digit and when this is received sends a 200 OK (Invite) to the AGCF and awaits receipt of the ACK. • Sends a Re-INVITE (D2) with the SDP of a Media Server (acting as a 3 party bridge) to the AGCF, awaits a 200 OK (Invite) and when this is received it sends an ACK followed by a BYE (D3). • It then awaits a 200 OK (Bye). ETSI ETSI TS 183 043 V3.4.1 (2011-04) 125 Figure C.7: 3PTY Call Establishment for tight coupling ETSI ETSI TS 183 043 V3.4.1 (2011-04) 126 C.14.3.3 Actions at the VGW at the originating side On receipt of a notification of Register RECALL from the VGW, the VGW opens a new dialogue (D3) and sends an INVITE (flash) to an originating AS. This INVITE includes the following: • The Request URI is structured as follows: - A user part containing "flash". - A domain name that together with the user part provides sufficient information for the AS Network to forward the request to the appropriate AS, based on Initial Filter Criteria stored in the user profile, e.g. flash@pes.operator.com. • A From header containing the public identity of the line on which the RECALL occurred. • An SDP offer for a speech call. The VGW now awaits receipt of a 484 Address Incomplete from the originating AS, and when received the VGW takes the following actions: • Play Dial Tone and collect one digit. • Sends an INVITE (D3) containing this single digit (as this is a Recall sequence with more than one active dialogue) and await receipt of 200 OK (Invite) or a failure response code. This INVITE is built in the same way as the previous INVITE except that the dialled digit replaces "flash". The VGW then awaits a re-INVITE (D2) with the SDP of a Media Server in the AS Network (acting as a 3 party bridge) and when received it takes the following actions: • Change the address to which RTP packets are sent and from which they are received. Sends a 200 OK (Invite) to the AS, awaits receipt of a BYE to end dialogue D3, and when this is received it sends a 200 OK (Bye). C.15 Repeat Last Call C.15.1 AGCF at the served user side The Repeat Last Call service is invoked using a service code command. On receipt of this service code command, the AGCF builds an INVITE request as described in clause C.1. C.15.2 AS at the served user side Implementation of this service assumes that the AS providing the service is involved in all outgoing calls to the served user. It is the responsibility of the network operator to configure the appropriate Initial Filter Criteria in the user profile. The AS keeps track of the last incoming call to each served user it manages. When receiving the service code command that identifies the Repeat Last Call service, the AS acts as a B2BUA and establishes a new call leg to the last called party (i.e. it sends an INVITE messages towards this last called party as if the number had been dialled again by the served user). C.15.3 VGW at the served user side The Repeat Last Call service is invoked using a service code command. On receipt of this service code command, the VGW builds an INVITE request as described in clause C.1. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 127 C.16 Call Hold C.16.1 Option 1 (Loose Coupling) C.16.1.1 Actions at the AGCF at the service invocation side The service is invoked during a stable 2 party call using the Register Recall. The AGCF monitors the flash-hook event unless an explicit indication that the Hold service is not provisioned to the user has been previously received as part of the profile delivery procedure. On receipt of a NOTIFY request reporting a flash hook event, the AGCF performs the following actions: • Monitor the flash-hook event. • Send a re INVITE request to place the current call on hold. On receipt of a NOTIFY request reporting a flash hook event, the AGCF performs the following actions: • Send a re INVITE request to resume the call on hold. • Monitor the flash-hook event. On receipt of a re INVITE request requesting a call to be placed on hold, the AS applies the procedures described in TS 124 610 [8]. As a network option the AS of the invoking UE initiates the procedures for the provision of an announcement to the held user in accordance with TS 124 628 [6]. C.16.1.2 Actions at the AS at the service invocation side On receipt of a re INVITE request requesting a call to be placed on hold, the AS applies the procedures described in TS 124 610 [8]. As a network option the AS of the invoking UE initiates the procedures for the provision of an announcement to the held user in accordance with TS 124 628 [6]. C.16.1.3 Actions at the VGW at the service invocation side The service is invoked during a stable 2 party call using the Register Recall. The VGW monitors the flash-hook event unless an explicit indication that the Hold service is not provisioned to the user has been previously received as part of the profile delivery procedure. On receipt of a NOTIFY request reporting a flash hook event, the VGW performs the following actions: • Monitor the flash-hook event. • Send a re INVITE request to place the current call on hold. On receipt of a NOTIFY request reporting a flash hook event, the VGW performs the following actions: • Send a re INVITE request to resume the call on hold. • Monitor the flash-hook event. On receipt of a re INVITE request requesting a call to be placed on hold, the AS applies the procedures described in TS 124 610 [8]. As a network option the AS of the invoking UE initiates the procedures for the provision of an announcement to the held user in accordance with TS 124 628 [6]. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 128 C.16.2 Option 2 (Tight Coupling) C.16.2.1 Actions at the AGCF at the service invocation side The service is invoked during a stable 2 party call using the Register Recall. The handling of the resulting Feature Request in the AGCF is according to clause B.4.2.2.3. The AGCF only reports the flash-hook as a trigger to the AS which has to take and co-ordinate all following actions dependent on the current service configuration. As a network option the AS of the invoking UE initiates the procedures for the provision of an announcement to the held user in accordance with TS 124 628 [6]. C.16.2.2 Actions at the AS at the service invocation side For tight coupling procedures the control of flash-hook invoked services is fully under control of the Application Server. As a consequence the AGCF/VGW only reports the flash-hook as a trigger to the AS which has to take and co-ordinate all following actions dependent on the current service configuration. In the context of 3 way call services the initial INVITE (flash) as described in clause B.4.2.2.3 only triggers the AS to place the current call on hold. Hold and resumption scenarios are specified in the supplementary service specific clauses of annex C. As a network option the AS of the invoking UE initiates the procedures for the provision of an announcement to the held user in accordance with TS 124 628 [6]. C.16.2.3 Actions at the VGW at the service invocation side The service is invoked during a stable 2 party call using the Register Recall. The handling of the resulting Feature Request in the VGW is according to clause B.4.2.2.3. The VGW only reports the flash-hook as a trigger to the AS which has to take and co-ordinate all following actions dependent on the current service configuration. As a network option the AS of the invoking UE initiates the procedures for the provision of an announcement to the held user in accordance with TS 124 628 [6]. C.17 Call Toggle/Broker Call Service C.17.1 General C.17.1.1 Actions at the AGCF at the service invocation side The service is invoked having an active call and a held call using the Register Recall. The AGCF monitors the flash-hook event. C.17.1.2 Actions at the VGW at the service invocation side The service is invoked having an active call and a held call using the Register Recall. The VGW monitors the flash-hook event. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 129 C.17.2 Option 1 (Loose coupling) C.17.2.1 Actions at the AGCF On receipt of a NOTIFY request reporting a flash hook event, the AGCF performs the following actions: • Set the stream mode of the ephemeral termination to inactive. • Apply a dial tone. • Collect a switching order command. The AGCF evaluates the Switch Order Command based on a provisioned mapping table. If the feature code received from the internal MGC component does not match any known feature, the AGCF ignores the feature code and optionally request the media gateway to play an error tone or an announcement to the served user. If the SOC indicates that the user wishes to toggle the active and the held parties the AGCF performs the following actions unless an explicit indication that the Call Toggle service is not provisioned for this user has been previously received as part of the profile delivery procedure: • Send a re INVITE request towards the active party. The re INVITE request is built as follows: - The Request URI is set to the active party's identity. - The SDP description for the active media stream is set to a=sendonly. • Send a re-INVITE request towards the former held party. The re-INVITE request is built as follows: - The Request-URI is set to the held party's identity. - The SDP description for the active media stream is set to a=sendrecv. • Request the media gateway to: - Modify the Remote Descriptor of the ephemeral termination according to the SDP information associated with the held party. - Monitor the flash-hook event. C.17.2.2 Actions at the AS at the terminating side On receipt of a re-INVITE request with a SDP attribute "sendonly", the AS as a network option interacts with an MRFC is order to play an announcement to the held party, in accordance with TS 124 628 [6]. On receipt of a re-INVITE request with the SDP attribute "sendrecv", the AS interacts with the MRFC to stop any ongoing announcement. C.17.2.3 Actions at the VGW On receipt of a NOTIFY request reporting a flash hook event, the VGW performs the following actions: • Set the stream mode of the IP media termination to inactive. • Apply a dial tone. • Collect a switching order command. The VGW evaluates the Switch Order Command based on a provisioned mapping table. If the feature code received does not match any known feature, the VGW ignores the feature code and optionally play an error tone or an announcement to the served user. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 130 If the SOC indicates that the user wishes to toggle the active and the held parties the VGW performs the following actions unless an explicit indication that the Call Toggle service is not provisioned for this user has been previously received as part of the profile delivery procedure: • Send a re INVITE request towards the active party. The re INVITE request is built as follows: - The Request URI is set to the active party's identity. - The SDP description for the active media stream is set to a=sendonly. • Send a re-INVITE request towards the former held party. The re-INVITE request is built as follows: - The Request-URI is set to the held party's identity. - The SDP description for the active media stream is set to a=sendrecv. • The VGW perform the following procedures: - Modify the IP media termination according to the SDP information associated with the held party. - Monitor the flash-hook event. C.17.3 Option 2 (Tight coupling) C.17.3.1 Actions at the AGCF Dependent on the network configuration the service can be invoked by the user: • via flash-hook; or • via flash-hook plus additional digits to be collected at AGCF. On receipt of a notification of Register RECALL the AGCF opens a new dialogue (D3) and sends an INVITE (flash) to an originating AS. This INVITE includes the following: • The Request URI is structured as follows: - A user part containing "flash" NOTE: In networks where no explicit SOC is collected, a preconfigured SOC is used to populate the user part. - A domain name that together with the user part provides sufficient information for the AS Network to forward the request to the appropriate AS, based on Initial Filter Criteria stored in the user profile, e.g. "flash@pes.operator.com" • A From header containing the public identity of the line on which the RECALL occurred. • An SDP offer for a speech call. If the network configuration requires that additional digits have to be collected to identify the desired service, then the AGCF now awaits receipt of a 484 Address Incomplete from the originating AS, and when received the AGCF takes the following actions: • Requests the A-MGW to play Dial Tone and collect the requested number of digits. • Sends an INVITE (D3) containing the collected digits (as this is a Recall sequence with more than one active dialogue) and await receipt of 200 OK (Invite) or a failure response code. This INVITE is built in the same way as the previous INVITE except that the dialled digits replaces "flash". The AGCF then awaits a re-INVITE (D2) with the SDP of the resumed former held party and when received it takes the following actions: • Sends an instruction to the A-MGW to change the address to which RTP packets are sent and from which they are received (e.g. it modifies the H.248 Remote Descriptor). ETSI ETSI TS 183 043 V3.4.1 (2011-04) 131 • Sends a 200 OK (Invite) to the AS, awaits receipt of a BYE to end dialogue D3, and when this is received it sends a 200 OK (Bye). C.17.3.2 Actions at the Originating AS at the originating side In networks where an explicit SoC is collected the AS on receipt of an INVITE (flash) (D3) takes the following actions: • Sends a 484 Address Incomplete response to the AGCF/VGW and awaits receipt of an ACK. • Awaits receipt of an INVITE (D3) with the requested number of digits and when this is received sends a 200 OK (Invite) to the AGCF/VGW and awaits receipt of the ACK. The AS evaluates the Switch Order Command based on the current call configuration and issues appropriate re-INVITE messages putting the former active party on hold and resuming the former held party. If more than one party has been placed on hold or is in a CW condition it depends on the network operator which of the held parties will be selected for resuming. E.g. a rotating list algorithm might apply for service invocation by flash-hook from the user. The maximum number of calls between Call Toggle is possible should be specified by the network operator. The AS interacts with an MRFC is order to play and stop announcements to held party, in accordance with TS 124 628 [6]. C.17.3.3 Actions at the VGW The VGW sends a re-INVITE request to the Application Server on the active call, built as follows: • The Request URI is structured as follows: - A user part containing a provisioned prefix followed by the switching order command without the start and finish fields. NOTE: In networks where no explicit SOC is collected, a preconfigured SOC is used to populate the user part. • A domain name that provides sufficient information to the S-CSCF to forward the INVITE request to the appropriate AS, based on Initial Filter Criteria stored in the user profile, e.g. SOC- "SO (SR SI)"@pes.operator.com. • A P-Asserted-Identity containing the public identity of the subscriber issuing the switching control command. • An SDP offer for a voice call. The VGW modifies the stream mode according to the SDP information received in re-INVITE messages sent by the Application Server. C.18 Completion of Communications to Busy Subscriber (CCBS) and Completion of Communications by No Reply (CCNR) C.18.1 Actions at the Originating AGCF For invoking and revoking of the call completion services, announcement procedures according to TS 124 628 [6] and inband-interaction procedures should be used. The "m" parameter in the request line of the received REFER or INVITE request in the AGCF/VGW is ignored or may be used to select a ring pattern conforming to a "distinctive ring" signal. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 132 C.18.2 Actions at the Originating AS The AS implements the procedures described in TS 124 642 [47], clause 4.5.4.2. C.18.3 Actions at the Terminating AS The AS implements the procedures described in TS 124 642 [47], clause 4.5.4.3. C.18.4 Actions at the Terminating AGCF Basic call procedures according to clauses 5, 6 and 7 of the present document shall apply. C.18.5 Actions at the Originating VGW For invoking and revoking of the call completion services, announcement procedures according to TS 124 628 [6] and inband-interaction procedures should be used. The "m" parameter in the request line of the received REFER or INVITE request in the AGCF/VGW is ignored or may be used to select a ring pattern conforming to a "distinctive ring" signal. C.18.6 Actions at the Terminating VGW Basic call procedures according to clauses 5 and 6 of the present document shall apply. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 133 Annex D (normative): Mapping between SIP and the subscriber line protocol D.1 Introduction This annex describes the mapping between SIP messages received by an AGCF or a VGW acting as a UE and the messages of the subscriber line protocol defined in ES 200 659-3 [10]. D.2 Call Setup message This message is used to send information related to an incoming call. e.g. Calling Line Identification Presentation (CLIP) and related services. This message is built by the AGCF or the VGW on receipt of an initial INVITE request. The AGCF requests the media gateways to send this message over the analogue line using the Display Data Block parameter of the Display With Alerting signal of the andisp package defined in ITU-T Recommendation H.248.23 [13]. The AGCF or VGW populates the message parameters as described in table D.1, based on the contents of the INVITE message and local configuration data. Table D.1: Call set-up message parameters Parameter type O/M Populating rules Date and Time O Set from local clock (see note 1) Calling Line Identity M Set according to the contents of the "From" header or "P-Asserted-Identity" header dependent on national operator requirements. or Or Reason for absence of Calling Line Identity Set from "Privacy" header (see note 2). Called Line Identity O "P-Called-Party-Id" header. Calling Party Name O Set according to the "Display-Name" in the "From" header or "P-Asserted-Identity" header dependent on national operator requirements or Or Reason for absence of Calling Party Name "Privacy" header (see note 2). Complementary Calling Line Identity O Setting of this parameter is based on operator specific rules. Call type O Setting of this parameter is based on operator specific rules. First Called Line Identity O Set according to the "hi-targeted-to-uri " in the first entry in the "History-Info" header Absent if the "Privacy" header set to "history". Number of Messages O Setting of this parameter is based on operator specific rules. Type of Forwarded call O Set according to the "Cause" parameter associated with the "hi-targeted-to-uri" in the last entry of the "History-Indo" header. Absent if the "Privacy" header is set to "history". Type of Calling User O Set from the cpc parameter of the P-Asserted-Identity header Absent if the "Privacy" header set to "header". Redirecting Number O Set according to the "hi-targeted-to-uri" in the last entry in the "History-Info" Absent if the "Privacy" header set to "history". Network Provider Identity O Setting of this parameter is based on operator specific rules. Carrier Identity O Setting of this parameter is based on operator specific rules. Selection of Terminal Function O Setting of this parameter is based on operator specific rules. Display Information O May be set from the contents of the message body. Service Information O May be set from the contents of the message body. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 134 Parameter type O/M Populating rules Extension for network operator use O Setting of this parameter is based on operator specific rules. NOTE 1: The AGCF and the VGW shall support an appropriate clock synchronization mechanism. NOTE 2: If the "Privacy" header is included and set to "id" or "user" or "header", the Reason for Absence is set to "Private" (0101 0000). If the "P-Asserted-Identity" header and the "From" header are absent, the Reason for Absence is set to "unavailable" (0100 1111). D.3 Message Waiting Indicator message This message type is used to handle information related to messages in a message system. This message is built by the AGCF or the VGW on receipt of a NOTIFY request reporting the "message-summary" event. The AGCF requests the media gateways to send this message over the analogue line using the Data Block parameter of the Generic Data Signalling signal of the andisp package defined in ITU-T Recommendation H.248.23 [13]. The value of the TAS parameter is provisioned in the AGCF or MGF, per media gateway or per line. The AGCF or the VGW populates the message parameters as described in table D.2, using the information contained in NOTIFY requests reporting the "message-summary" event and local configuration data. Table D.2: Message Waiting Indicator message parameters Parameter type O/M Populating rules Date and Time O Set from local clock (see note). Calling Line Identity Set according to the contents of the "P-Asserted-Id" header or Or Reason for absence of Calling Line Identity O Privacy header. Calling Party Name Set according to the "P-Asserted-Id" header or Or Reason for absence of Calling Party Name O "Privacy" header. Visual Indicator M Set to "FF"H if the "Messages-Waiting" header is set to "yes". Message Identification O Set according to the "Message-ID" header. Last Message CLI O "From" header associated with the last message. Complementary Date and Time O "Date" header associated with the last message. Complementary Calling Line Identity O Setting of this parameter is based on operator specific rules. Number of Messages O Set according to the "Voice-Message" header. Type of Calling User O Setting of this parameter is based on operator specific rules. Network Provider Identity O Setting of this parameter is based on operator specific rules. Selection of Terminal Function O Setting of this parameter is based on operator specific rules. Display Information O May be set from the contents of the message body. Extension for network operator use O Setting of this parameter is based on operator specific rules. NOTE: The AGCF and the UE shall support an appropriate clock synchronization mechanism. D.4 Advice of Charge message This message is used to send information related to the charge of a call. This message is built by the AGCF or the VGW on receipt of a SIP message that contain information defined in TS 124 647 [7]. The AGCF or the VGW populates the message parameters as described in table D.3, based on information defined in TS 124 647 [7] and local configuration data. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 135 Table D.3: Advice Of Charge message parameters Parameter type O/M Populated From Date and Time O Set from local clock (see note). Calling Line Identity O or Setting of this parameter is based on operator specific rules. Reason for absence of Calling Line Identity Called line identity O Setting of this parameter is based on operator specific rules. Complementary Calling Line Identity O Setting of this parameter is based on operator specific rules. Charge M Set from the "recorded-charges" element defined in TS 124 647 [7]. Additional Charge O Setting of this parameter is based on operator specific rules. Duration of the call O Setting of this parameter is based on operator specific rules. Network Provider Identity O Setting of this parameter is based on operator specific rules. Carrier Identity O Setting of this parameter is based on operator specific rules. Selection of Terminal Function O Setting of this parameter is based on operator specific rules. Display information O Set from the value of the "billing-id" element defined in TS 124 647 [7]. Extension for network operator use O Setting of this parameter is based on operator specific rules. NOTE: The AGCF and the VGW shall support an appropriate clock synchronization mechanism. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 136 Annex E (normative): AOC - Extended XML schema (version 2) E.1 General This annex defines the XML Schema to be used for providing the charging information described in clause C.2 to the served user. The extensions introduced (versus the TS 124 647 [7] AOC XML schema) are indicated by the present document Change Note comment. In addition, the naming of the extension elements uses the prefix "pes". The MIME type (see clause E.2) used to provide the charging information requested by the served user shall be coded as described in clause E.3. E.2 MIME Type Definition E.2.1 Introduction This clause defines the MIME type for "application/vnd.etsi.aoc+xml". An AOC information XML Document can be identified with this media type. NOTE: TS 124 647 [7] includes the IANA Registration template for "application/vnd.etsi.aoc+xml". E.2.2 Syntax The following optional parameters are defined: • "charset": the parameter has identical semantics to the charset parameter of the "application/xml" media type as specified in RFC 3023 [45]. • "sv" or "schemaversion": the syntax for the "sv" or "schemaversion" parameter is specified in table E.1. Table E.1: Syntax of the "sv" or "schemaversion" parameter m-parameter /= ("sv" / "schemaversion") EQUAL LDQUOT [ sv-value-list ] RDQUOT sv-value-list = sv-value-range *( "," sv-value ) sv-value-range = sv-value [ "-" sv-value ] sv-value = number / token number = 1*DIGIT [ "." 1*DIGIT ] The BNF for m-parameter is taken from RFC 3261 [38] and modified accordingly. E.2.3 Operation The encoding considerations for "application/vnd.etsi.aoc+xml" are identical to those of "application/xml" as described in RFC 3023 [45]. The "sv" or "schemaversion" parameter's value is used to indicate: • the versions of the AOC information XML schema that can be used to validate the AOC information XML body (if the MIME type and parameter are present in the Content-Type header); or ETSI ETSI TS 183 043 V3.4.1 (2011-04) 137 • the accepted versions of the AOC information XML body (if the MIME type and parameter are present in the Accept header). If the "sv" or "schemaversion" parameter's value is empty, no versions of the AOC information XML schema are supported. If the "sv" and "schemaversion" parameter are absent, it shall be assumed that version 1 of the XML Schema for the AOC information XML body is supported. E.3 AOC Extended XML Schema The .xsd file is contained in archive ts_183043v030401p0.zip which accompanies the present document. <?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns="http://uri.etsi.org/ngn/params/xml/simservs/aoc " xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://uri.etsi.org/ngn/params/xml/simservs/aoc " elementFormDefault="qualified" attributeFormDefault="unqualified" version="2"> <xs:import namespace="http://www.w3.org/XML/1998/namespace" schemaLocation="http://www.w3.org/2001/xml.xsd"/> <xs:annotation> <xs:documentation xml:lang="en"> XML Schema Definition to the charging information related to the Advice of Charge simulation service. </xs:documentation> </xs:annotation> <xs:element name="aoc-extended" type="aocType"/> <xs:complexType name="aocType"> <xs:sequence> <!--TS 183 043 Change Note: extended optional element has been added bellow--> <xs:element name="pes-transitioning-behaviour" type="pes-transitioning-behaviourType" minOccurs="0"/> <!--TS 183 043 Change Note: "aoc-s”type, maxOccurs=”unbounded” has been added--> <xs:element name="aoc-s" type="aoc-sType" minOccurs="0" maxOccurs="unbounded"/> <xs:element name="aoc-d" type="aoc-dType" minOccurs="0"/> <xs:element name="aoc-e" type="aoc-eType" minOccurs="0"/> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> <xs:anyAttribute namespace="##any" processContents="lax"/> </xs:complexType> <!-- xs:sequence is changed to xs:choice --> <xs:complexType name="aoc-sType"> <xs:choice> <xs:element name="special-arrangement" type="xs:token"/> <xs:element name="charged-items" type="charged-itemsType"/> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:choice> <xs:anyAttribute namespace="##any" processContents="lax"/> </xs:complexType> <xs:complexType name="aoc-dType"> <xs:sequence> <xs:element name="charging-info" type="charging-infoType"/> <xs:element name="recorded-charges" type="recorded-chargesType"/> <xs:element name="billing-id" type="billind-idType" minOccurs="0"/> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> <xs:anyAttribute namespace="##any" processContents="lax"/> </xs:complexType> <xs:complexType name="aoc-eType"> <xs:sequence> <xs:element name="recorded-charges" type="recorded-chargesType"/> <xs:element name="billing-id" type="billind-idType" minOccurs="0"/> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> <xs:anyAttribute namespace="##any" processContents="lax"/> </xs:complexType> <xs:complexType name="charged-itemsType"> <xs:sequence> <!--TS 183 043 Change Note: extended optional element has been added below --> <xs:element name="pes_aoc-s_phase_duration" type="timeType" minOccurs="0"/> <xs:element name="basic" type="basicType" minOccurs="0"/> <xs:element name="communication-attempt" type="communication-attemptType" minOccurs="0"/> <xs:element name="communication-setup" type="communication-setupType" minOccurs="0"/> <xs:element name="services" type="servicesType" minOccurs="0"/> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> ETSI ETSI TS 183 043 V3.4.1 (2011-04) 138 </xs:sequence> <xs:anyAttribute namespace="##any" processContents="lax"/> </xs:complexType> <xs:complexType name="basicType"> <xs:sequence> <xs:element name="price-time" type="price-timeType" minOccurs="0" maxOccurs="unbounded"/> <xs:element name="flat-rate" type="currency-id-amountType" minOccurs="0"/> <xs:element name="free-charge" type="emptyType" minOccurs="0"/> <xs:element name="special-code" type="xs:token" minOccurs="0"/> <xs:element name="not-available" type="emptyType" minOccurs="0"/> </xs:sequence> </xs:complexType> <xs:complexType name="communication-attemptType"> <xs:sequence> <xs:element name="flat-rate" type="currency-id-amountType" minOccurs="0"/> <xs:element name="free-charge" type="emptyType" minOccurs="0"/> <xs:element name="special-code" type="xs:token" minOccurs="0"/> <xs:element name="not-available" type="emptyType" minOccurs="0"/> </xs:sequence> </xs:complexType> <xs:complexType name="communication-setupType"> <xs:sequence> <xs:element name="flat-rate" type="currency-id-amountType" minOccurs="0"/> <xs:element name="free-charge" type="emptyType" minOccurs="0"/> <xs:element name="special-code" type="xs:token" minOccurs="0"/> <xs:element name="not-available" type="emptyType" minOccurs="0"/> </xs:sequence> </xs:complexType> <xs:complexType name="servicesType"> <xs:sequence> <xs:element name="price-time" type="price-timeType" minOccurs="0"/> <xs:element name="flat-rate" type="currency-id-amountType" minOccurs="0"/> <xs:element name="free-charge" type="emptyType" minOccurs="0"/> <xs:element name="special-code" type="xs:token" minOccurs="0"/> <xs:element name="not-available" type="emptyType" minOccurs="0"/> </xs:sequence> </xs:complexType> <!-- length-time-unit: type="timeType" (another possibilty is to keep length-time-unit with type="xs:duration") granularity: type="timeType" (another possibility is type="xs:duration") (xs:duration: the minimum resolution is second) --> <xs:complexType name="price-timeType"> <xs:sequence> <xs:element name="currency-id" type="xs:token" minOccurs="0"/> <!-- The currency-id shall be coded according to ISO 4217 [3] or set to the value "UNIT" for the sending of charging units. --> <xs:element name="currency-amount" type="xs:decimal" minOccurs="0"/> <xs:element name="length-time-unit" type="timeType" minOccurs="0"/> <xs:element name="charging-type" type="charging-typeType" minOccurs="0"/> <xs:element name="granularity" type="timeType" minOccurs="0"/> </xs:sequence> </xs:complexType> <xs:complexType name="currency-id-amountType"> <xs:sequence> <xs:element name="currency-id" type="xs:token" minOccurs="0"/> <!-- The currency-id shall be coded according to ISO 4217 [3] or set to the value "UNIT" for the sending of charging units. --> <xs:element name="currency-amount" type="xs:decimal" minOccurs="0"/> </xs:sequence> </xs:complexType> <!-- timeType is represented with time-unit (unsigned int) * scale (enum) --> <xs:complexType name="timeType"> <xs:sequence> <xs:element name="time-unit" type="xs:unsignedInt"/> <xs:element name="scale" type="scaleType"/> </xs:sequence> </xs:complexType> <xs:simpleType name="scaleType"> <xs:restriction base="xs:token"> <xs:enumeration value="one-hundreth-second"/> <xs:enumeration value="one-tenth-second"/> <xs:enumeration value="one-second"/> <xs:enumeration value="ten-seconds"/> <xs:enumeration value="one-minute"/> <xs:enumeration value="one-hour"/> <xs:enumeration value="twenty-four-hours"/> ETSI ETSI TS 183 043 V3.4.1 (2011-04) 139 </xs:restriction> </xs:simpleType> <!-- end of timeType definition --> <xs:complexType name="emptyType"> <xs:complexContent> <xs:restriction base="xs:anyType"/> </xs:complexContent> </xs:complexType> <!-- simplified --> <xs:simpleType name="charging-infoType"> <xs:restriction base="xs:token"> <xs:enumeration value="total"/> <xs:enumeration value="subtotal"/> </xs:restriction> </xs:simpleType> <!-- xs:sequence is changed to xs:choice --> <xs:complexType name="recorded-chargesType"> <xs:choice> <xs:element name="recorded-currency-units" type="currency-id-amountType"/> <xs:element name="free-charge" type="emptyType"/> <xs:element name="not-available" type="emptyType"/> </xs:choice> </xs:complexType> <xs:simpleType name="billind-idType"> <xs:restriction base="xs:string"> <xs:enumeration value="normal-charging"/> <xs:enumeration value="reverse-charging"/> <xs:enumeration value="credit-card"/> <xs:enumeration value="cfu"/> <xs:enumeration value="cfb"/> <xs:enumeration value="cfnr"/> <xs:enumeration value="cd"/> <xs:enumeration value="ct"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="charging-typeType"> <xs:restriction base="xs:string"> <xs:enumeration value="step-functon"/> <xs:enumeration value="continuous"/> </xs:restriction> </xs:simpleType> <!--TS 183 043 Change Note: simpleType definition for the optional "pes-transitioning-behaviourType” added below --> <xs:simpleType name="pes-transitioning-behaviourType"> <xs:restriction base="xs:string"> <xs:enumeration value="Immediate"/> <xs:enumeration value="Continuous"/> </xs:restriction> </xs:simpleType> </xs:schema> ETSI ETSI TS 183 043 V3.4.1 (2011-04) 140 Annex F (normative): Overlap Sending This annex describes the handling of Overlap Sending according to EN 300 403-1 [41], clause 5.1.3. F.0 General Three methods of signalling are described in this annex: • Clause F.1 describes sending of Invite with determining the end of address signalling. • Clause F.2 describes a signalling procedure without determining the end of address signalling using a multiple INVITE method. • Clause F.3 describes a signalling procedure without determining the end of address signalling using a In-Dialog method. The collection of Digits at the originating VGW/AGCF shall be controlled using the following timers: • T-FirstDigit timer: The amount of time allowed for the user to enter the first digit. • T-InterDigit timer: The amount of time allowed for the user to enter each subsequent digit. • Additional timers which are per signalling method are described in the relevant clauses F.1, F.2 and F.3. The Ta3 timer used in clauses F.2 and F.3, shall be provisioned to a value that is greater than the T-InterDigit timer. Clause F.4 provides a table containing the complete list of Timers. F.1 Sending of Invite with determining the end of address signalling F.1.1 Actions at the originating VGW/AGCF 1. Off-Hook VGW/ AGCF 4. INVITE (n Digits) 2. Digit 1 3. Digit n Figure F.1: Receipt of Digit information at the originating VGW/AGCF After initiating the normal incoming PSTN call establishment procedures, determining the end of address signalling and selecting to route the call to the IMS domain, the originating VGW/AGCF sends the initial INVITE. The initial INVITE contains all digits, i.e. en-bloc sending. The end of address signalling is determined by the earlier of the following criteria: a) by receipt of the maximum number of digits used in the national numbering plan; or b) by analysis of the called party number to indicate that a sufficient number of digits has been received to route the call to the called party. This could be achieved by analysis of a provisioned dial plan; or ETSI ETSI TS 183 043 V3.4.1 (2011-04) 141 c) by observing that timer Ta1 has expired after the receipt of the latest received address digit and the minimum number of digits required for routing the call have been received. If the end of the address signalling is determined in accordance with criteria a) or b), the timer Ta2 is started when INVITE is sent. The AGCF/VGW can contain a configurable digit map which is used to analyse the received address digits. This digit map can be used to identify the required number of digits to be entered for a particular digit sequence. The procedures for Digit maps are described within clause 7.3.1.3.1.1. Even in the absence of a digit map, it is appropriate for the AGCF/VGW to collect dialled digits. The AGCF/VGW shall contain a configurable parameter indicating the minimum number of digits expected in the sequence of Called party number information elements before a Request-URI is constructed and an INVITE request sent. The minimum number could be zero. F.1.2 Actions at the terminating VGW/AGCF No action with regard to overlap is needed. DDI is out of scope of the present document. F.2 multiple INVITE Overlap Dialling Procedures (Optional) F.2.1.1 Actions at the originating VGW/AGCF F.2.1.1.1 Sending of INVITE without determining the end of address signalling On detection of the off-hook event, the AGCF/VGW will return dial tone, if required by the tone option. 1) As a network option, the originating VGW/AGCF may send INVITE requests without determining the end of address signalling. If the originating VGW/AGCF sends an INVITE request before the end of address signalling is determined, the originating VGW/AGCF: - uses the SIP precondition extension within the INVITE request; according to TS 124 229 [4]; - starts timer Ta2; and - is prepared to process further incoming digits as described below; - is prepared to handle incoming SIP 404 or 484 error responses as detailed in this clause. 2) On receipt of fresh address information from the originating side, the originating VGW/AGCF: - stops timer Ta3 (if it is running); - sends an INVITE request complying to the following: the INVITE request uses the SIP preconditions extension; the INVITE request includes all digits received so far for this call in the Request-URI. - if subsequent address information is received after the SIP 404 or 484 error response has been received, the INVITE request additionally includes the digits received; - restarts Ta2. If timer Ta2 has expired, the originating VGW/AGCF cancels the call. On receipt of a 180 Ringing or 183 Provisional Response, the originating VGW/AGCF stops Ta2. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 142 3) As a network option the Timer Ta4 can be used, in this case the following procedure applies starting with the first digit received by the AGCF/VGW: - start timer Ta4 with receiving the first dialled Digit; - collect all digits received; - at expiry of timer Ta4 the initial INVITE is sent out; - proceeds as described under 1; - if further digits are needed then the AGCF/VGW shall collect further digits until min length has been reached. NOTE: The AGCF/VGW contains a configurable parameter indicating the minimum number of digits expected in the sequence of Called party number information elements before a Request-URI is constructed and an INVITE request sent. The minimum number could be zero. As a network Option the first INVITE can be sent with the detection of the "off-hook" event. The Ta4 shall not be used if the INVITE has to be sent immediately because e.g. the hotline feature is provided to the originating user. On receipt of a 404 Not Found or 484 Address Incomplete response while Ta2 is running, the originating VGW/AGCF starts timer Ta3, if there are no other pending INVITE transactions for the corresponding call. At the receipt of fresh address information, or a SIP 180, 183 provisional responses, or a SIP 200 OK (INVITE), the originating VGW/AGCF stops Ta2 and Ta3. As a network optionTimer Ta4 may be started (the communication is then proceeding as described in the rest of this clause). The originating VGW/AGCF clears as described in clause 7.3.1.3.1.2 the call if Ta3 expires. Option a) Overlap with Ta4 Timer AGCF/VGW x-CSCF Off Hook INVITE Cseq 1 Digit 1 Ta4 Digit 2 Digit 3 180 Ringing Cseq 1 Ring Tone Digit n Digit 4 . . . Figure F.2: Overlap with Ta4 Timer- no transaction is pending ETSI ETSI TS 183 043 V3.4.1 (2011-04) 143 AGCF/VGW x-CSCF INVITE Cseq 1 Ta4 180 Ringing Cseq 2 INVITE Cseq 2 484 Cseq 1 ACK Digit n+1 Off Hook Digit 1 Digit 2 Digit 3 Digit n Digit 4 . . . Ringtone Figure F.3: Overlap with Ta4 Timer one transaction is pending ETSI ETSI TS 183 043 V3.4.1 (2011-04) 144 Option b) Overlap with Digit Map AGCF/VGW x-CSCF INVITE Cseq 1 180 Ringing Cseq 3 Ringtone INVITE Cseq 2 484 Cseq 1 ACK Digit map matched INVITE Cseq 3 484 Cseq 2 ACK Off Hook Digit 1 Digit 2 Digit 3 Digit n Digit 4 . . . Digit n+1 Figure F.4: Overlap with digit map ETSI ETSI TS 183 043 V3.4.1 (2011-04) 145 Option c) Overlap with Digit Map and Ta4 Timer AGCF/VGW x-CSCF INVITE Cseq 1 180 Ringing Cseq 3 Ring Tone INVITE Cseq 2 484 Cseq 1 ACK Digit map matched Stop Ta4 INVITE Cseq 3 484 Cseq 2 ACK Ta4 Off Hook Digit 1 Digit 2 Digit 3 Digit n Digit 4 . . . Digit n Figure F.5: Overlap with digit map and Ta4 timer digit map matched before Ta4 expiry ETSI ETSI TS 183 043 V3.4.1 (2011-04) 146 AGCF/VGW x-CSCF INVITE Cseq 1 180 Ringing Ring Tone INVITE Cseq 2 484 Cseq 1 ACK Digit map matched Ta4 Off Hook Digit 1 Digit 2 Digit 3 Digit n Digit 4 . . . Figure F.6: Overlap with digit map and Ta4 timer digit map matched after Ta4 expiry ETSI ETSI TS 183 043 V3.4.1 (2011-04) 147 AGCF/VGW x-CSCF Off Hook INVITE Cseq 2 Digit 1 Ta4 Digit 2 Digit 3 180 Ringing Cseq 2 Ring Tone Digit n Digit 4 . . . 484 Cseq 1 INVITE Cseq 1 Figure F.7: Overlap with Ta4 Timer - using the option to send the first INVITE at the off-hook event F.2.2 Actions at the terminating VGW/AGCF No action with regard to overlap is needed. DDI is out of scope of the present document. F.3 In-Dialog Method (Optional) F.3.1 Actions at the originating VGW/AGCF F.3.1.1 Sending of INVITE without determining the end of address signalling On detection of the off-hook event, the AGCF/VGW will return dial tone, if required by the tone option. 1) As a network option, the originating VGW/AGCF may send INVITE requests without determining the end of address signalling. If the AGCF/VGW sends an INVITE request before the end of address signalling is determined, the AGCF/VGW shall: - use the SIP precondition extension within the INVITE request, according to TS 124 229 [4]; - starts timer Ta2; and - be prepared to process further incoming digits as described below; - be prepared to handle incoming SIP 484 (Address Incomplete) responses; - on receipt of 404 Not Found or 484 Address Incomplete start timer Ta3; - on receipt of 183 Provisional Response without P-Early-Media header authorizing early media, stop Ta2 and start Ta3. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 148 NOTE 1: Based on the network solution the reception of 484 can be avoided. This assumes that an AS behaving as B2BUA is collecting the digits starting with the first INVITE. 2) On receipt of a new Address information, the AGCF/VGW shall: - stop timer Ta3 (if it is running); - if an early dialog has been established and a response has been received for any previously sent SIP INFO request, send a SIP INFO request including the additional digits for this call and start timer Ta2; - if no response has been received for the previous SIP INFO request, the AGCF/VGW shall wait for the response and then apply the procedures in the previous bullet to send the new address information. If more than one digit is received while the AGCF/VGW is waiting for the response for the previous SIP INFO request, all digits within shall be combined; - if an early dialog has not been established, wait for a final error response for the previous INVITE and send an INVITE request including all digits received so far for this call in the Request-URI and start Ta2 if Ta4 is not running. The SIP INVITE request shall include the same Call ID and From tag as the previous SIP INVITE request for the call. NOTE 2: The encoding of the digits within the SIP INFO request is described in clause F.3.4. At the receipt of a SIP 200 OK (INFO) the originating VGW/AGCF shall stop Ta2 and start Ta3. At the receipt of a SIP 180, 183 provisional response with P-Early-Media header authorizing early media, or a SIP 200 OK (INVITE), the originating VGW/AGCF shall stop Ta2 and Ta3. As a network option the Timer Ta4 can be used, in this case the following procedure applies starting with the first digit received by the AGCF/VGW: • start timer Ta4 with receiving the first address information; • collect all digits received; • at expiry of timer Ta4 the initial INVITE is sent out as described under 1); or • if further digits are needed then the AGCF/VGW shall collect further digits until min length has been reached. NOTE 3: The AGCF/VGW contains a configurable parameter indicating the minimum number of digits expected in the sequence of Called party number information elements before a Request-URI is constructed and an INVITE request sent. The minimum number could be zero. As a network Option the first INVITE can be sent with the receipt of the "off-hook" event. The Ta4 shall not be used if the INVITE has to be sent immediately because e.g. the hotline feature is provided to the originating user. The originating VGW/AGCF clears as described in clause 7.3.1.3.1.2 the call if Ta3 expires. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 149 Option a) Overlap with Ta4 Timer AGCF / VGW x-CSCF Off Hook T-FirstDigit T-InterDigit T-InterDigit T-InterDigit T-InterDigit T-InterDigit T-InterDigit Ta4 Ta2 Ta3 Digit 1 Digit 2 Digit 3 Digit 4 Digit n Dial Tone Ring Tone Invite Cseq 1 183 Session progress Cseq 1 180 Ringing Cseq 1 Figure F.8: Overlap with Ta4 Timer- no transaction is pending ETSI ETSI TS 183 043 V3.4.1 (2011-04) 150 AGCF / VGW x-CSCF Off Hook T-FirstDigit T-InterDigit T-InterDigit T-InterDigit T-InterDigit T-InterDigit T-InterDigit T-InterDigit Ta4 Ta2 Ta2 Ta3 Ta3 Digit 1 Digit 2 Digit 3 Digit 4 Digit n Digit n+1 Dial Tone Ring Tone Invite Cseq 1 183 Session progress Cseq 1 INFO Cseq 2 200 Cseq 2 180 Ringing Cseq 1 Figure F.9: Overlap with Ta4 Timer no transaction is pending ETSI ETSI TS 183 043 V3.4.1 (2011-04) 151 Option b) Overlap with Digit Map AGCF/VGW x-CSCF INVITE Cseq 1 180 Ringing Cseq 1 INFO Cseq 2 200 Cseq 2 Digit map matched 183 Session Progress Cseq 1 INFO Cseq 3 200 Cseq 3 Ring Tone Off Hook Digit 1 Digit 2 Digit 3 Digit n+1 Digit n . . . Digit n+2 Figure F.10: Overlap with digit map ETSI ETSI TS 183 043 V3.4.1 (2011-04) 152 Option c) Overlap with Digit Map and Ta4 Timer AGCF/VGW x-CSCF INVITE Cseq 1 180 Ringing Cseq 1 INFO Cseq 2 200 Cseq 2 Digit map matched Stop Ta4 Ta4 INFO Cseq 3 200 Cseq 3 183 Session Progress Cseq 1 Ring Tone Off Hook Digit 1 Digit 2 Digit 3 Digit n Digit 4 . . . Digit n+1 Digit n+2 Figure F.11: Overlap with digit map and Ta4 timer digit map matched before Ta4 expiry ETSI ETSI TS 183 043 V3.4.1 (2011-04) 153 AGCF/VGW x-CSCF INVITE Cseq 1 183 Session Progress Cseq 1 Digit map matched Ta4 INFO Cseq 2 200 Cseq 2 180 Ringing Cseq 1 Ring Tone Digit 1 Digit 2 Digit 3 Digit n Digit 4 . . . Digit n+1 Digit n+2 Off Hook Figure F.12: Overlap with digit map and Ta4 timer digit map matched after Ta4 expiry ETSI ETSI TS 183 043 V3.4.1 (2011-04) 154 AGCF/VGW x-CSCF Off Hook INFO Cseq 2 Digit 1 Ta4 Digit 2 Digit 3 180 Ringing Cseq 1 Ring Tone Digit n Digit 4 . . . INVITE Cseq 1 183 Session Progress Cseq 1 Figure F.13: Overlap with Ta4 Timer - using the option to send the first INVITE at the off-hook event F.3.2 Actions at the terminating VGW/AGCF No action with regard to overlap is needed. DDI is out of scope of the present document. F.3.3 Procedures at the overlap signalling AS (Optional) With receiving the initial INVITE the AS shall query the attached routing HSS or database to find the destination. In case of an indication that more digits are needed the AS creates an early dialog by sending a 183 (Session Progress) response. The AS shall also start a T-InterDigit timer (typically 10 s to15 s) If the T-InterDigit timer expires then the call shall be released by the AS. When additional address information is received within SIP INFO Requests, the AS SHALL add them to the previously received digits, and use them for HSS/database routing queries in order to being able to forward the call. When enough address information has been collected to forward the call to the appropriate destination, the AS SHALL create a SIP INVITE request, which contains all the received address digits, and forward it towards the destination. In cases where it is identified that the call shall be forwarded to networks not supporting overlap in-dialog signalling, the AS shall perform en-bloc conversion. If the minimum number of digits required for routing the call have been received, the AS shall start a short timer Ta1 (typically 4 s to 6 s) and wait for subsequent SIP INFO Requests carrying additional request information. When the Ta1 timer expires, the AS SHALL create a SIP INVITE request, which contains all the received address digits, and forward it towards the destination. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 155 1. INVITE 5. Not found /incomplete 12. Not Found/ Incomplete S-CSCF AS HSS + Routing DB 23. INVITE 8. INFO 24. 180 4. Lookup- procedure 2. INVITE 3. Query 6. 183 7. 183 9. INFO 10. Query 11. Lookup- procedure 13. 200 OK (INFO) 14. 200 OK (INFO) 19. Found 15. INFO 16. INFO 17. Query 18. Lookup- procedure 20. 200 OK (INFO) 21. 200 OK (INFO) 22. INVITE 25. 180 26. 180 27. 180 Figure F.14: IN-Dialog Overlap Signalling with included AS at the originating leg 1. INVITE: Sent from the originating network towards a S-CSCF. 2. INVITE: Forwarded to the AS acting as a B2BUA that will collect the digits. 3. Lookup: The AS is connected to all databases needed for the routing decision like the HSS, ENUM/DNS for Transit or such a Number Portability data base. 4. Lookup procedure within the Database to get more information. 5. The DB sends back that there is not sufficient information on which the call can be routed. 6. 183 (Call Progress) to start the early dialog for the Digit collection via IN-Dialog. 7. 183. 8. INFO; additional address information is sent towards the S-CSCF. 9. INFO: AS collects and merge the digits to and request now the whole number existing from the digits received within the INVITE and the digits received within the INFO. 10. Query of new number. 11. Lookup procedure within the database to get more information. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 156 12. The DB sends back that there is not sufficient information on which the call can be routed. 13. Send a 200 OK (INFO) back to that the digits are received. 14. 200 OK (INFO). 15. INFO; additional address information is sent towards the S-CSCF. 16. INFO: AS collects and merge the digits to and request now the whole number existing from the digits received within the INVITE and the digits received within the INFO. 17. Query of new number. 18. Lookup procedure within the database to get more information. 19. The DB sends back that there are sufficient digits received. 20. Send a 200 OK (INFO) back to that the digits are received. 21. 200 OK (INFO). 22. INVITE will be now forwarded back to the S-CSCF with the complete number/IP address of the terminating P-CSCF. 23. INVITE sent toward the terminating network. 24. 180 (Ringing)received from the terminating network. 25. 180 (Ringing) S-CSCF - AS. 26. 180 (Ringing) AS - S-CSCF. 27. 180 (Ringing) S-CSCF- towards originating network. F.3.4 Overlap digit message body F.3.4.1 Scope This clause defines a message body that shall be used for sending additional digits, which have not previously been sent, in SIP INFO messages when the in-dialog method is used for overlap dialling. The support of this message body is a network option. NOTE: The contents of clause F.3.4 will be inherited in the Release 8 version of TS 129 163 [32], annex G. As a consequence clause F.3.4 will be removed in the NGN Release 3 document which will in general refer to 3GPP Release 8 specifications. F.3.4.2 MIME type The message body defined in the present annex is registered at IANA as "application/x-session-info" MIME type. If the message body is embedded in SIP INFO messages, the Content-Type header shall be set to "application/x-session-info" and the Content-Disposition header shall be set to "signal" with the handling parameter set to "optional". F.3.4.3 ABNF x-session-info = SubsequentDigit SubsequentDigit = "SubsequentDigit" HCOLON phonedigits phonedigits = 1*(HEXDIG / "*" / "#") HEXDIG = DIGIT / "A" / "B" / "C" / "D" / "E" / "F" ETSI ETSI TS 183 043 V3.4.1 (2011-04) 157 F.4 Timers Table F.1: Timers for interworking Symbol Time-out value Cause for initiation Normal termination At expiry T-FirstDigit 1 s to 99 s (default=60 s) Upon start of dial tone injection On receipt of the first dialed digit Release Call T-InterDigit 1 s to 15 s (default=10 s) Upon receipt of a new address message Upon receipt of subsequent address message or 180 Ringing or 183 Session Progress with P-Early Media header authorizing early media a) Disable Digit Receiver; b) if Ta3 is not running then Release Call Ta1 4 s to 6 s (default of 4 s) (see note 1) When last address information is received and the minimum number of digits required for routing the call have been received. At the receipt of fresh address information. Send INVITE Ta2 (Multiple Invite) 10 s to 15 s (see notes 2 and 4) When INVITE is sent. On reception of 180 Ringing, or 183 Session Progress, or 404 Not Found or 484 Address Incomplete for an INVITE transaction for which Ta2is running, or 200 OK (INVITE). Release Call Ta2 (In-Dialog) 10 s to 15 s (see notes 2 and 4) When INVITE is sent or when INFO is sent. On reception of 180 Ringing, or 183 Session Progress, or 404 Not Found or 484 Address Incomplete for an INVITE transaction for which Ta2 is running, or 200 OK (INVITE) or 200 OK (INFO). Release Call Ta3 (Multiple invite) 4 s to 20 s (default of 15 s) (see note 3) On receipt of 404 Not Found or 484 Address Incomplete if there are no other pending INVITE transactions for the corresponding call. At the receipt of fresh address information Release call Ta3 (In-Dialog) 4 s to 20 s (default of 15 s) (see note 3) On receipt of 404 Not Found or 484 Address Incomplete if there are no other pending INVITE transactions for the corresponding call. On receipt of 200 OK (INFO), or 183 Session Progress without early media authorization. At the receipt of fresh address information or 180 Ringing or 183 with P-Early-Media header authorizing early media or 200 OK (INVITE) Release call Ta4 0,5 s to -4 s On receipt of the initial address information. At expiry Send INVITE NOTE 1: This timer is used in clause F.1 when overlap signalling is received from access line and converted to en-block signalling at the AGCF/VGW. NOTE 2: This timer is used in clauses F.2 and F.3 to wait for an 404/484 response. In addition clause F.3 uses this timer for: a) to wait for an 183 response to an INVITE; b) to wait for a 200 OK (INFO) response. NOTE 3: This timer is known as the "SIP dialog protection timer". This timer is only used where the AGCF/VGW is configured to send INVITE before end of address signalling is determined. The Ta3 timer shall be greater than the T-InterDigit timer. NOTE 4: The value of timer Ta2 may vary beyond these limits, e.g. as a result of called party number analysis. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 158 Annex G (informative): Digit collection in MRF after receipt of flash-hook in the tight coupling model G.1 Introduction In the case where the tight coupling model is used for flash-hook invoked services, this annex describes the optional use of the MRF for collection of dialled digits and provision of dial tone. G.2 Management of dial tone and digit collection in the MRF • Upon receipt of a Feature-Request resulting from the detection of a flash-hook event the Feature Manager of the AGCF/VGWrequests the SIP UA to create a new dialogue and to send an INVITE (flash) request built as specified in clause B.4.2.2.3.2 (i.e. including an SDP offer for a voice call) to the AS. As a network option, the AGCF/VGW may also send a re-INVITE request over the existing dialogue with an SDP requesting the B-Party to be put on hold (i.e. a=sendOnly), prior to sending the INVITE request creating the new dialogue In such cases the AGCF/VGW waits for the 200 OK response to the re-INVITE request before sending the new INVITE request. On receipt of an INVITE request from an AGCF/VGW indicating detection of a flash-hook event the AS may perform the following actions: • Create a new dialogue to MRF to arrange the bearers to connect the MRF and the A-Party (i.e. the party having originated the flash-hook event). • Request the MRF to provide dial tone to the caller and to start inband collection of dialled digits. The AS may also arrange for an announcement to be played to the held party via an MRF as described in annex C for the specific services. Collected digits are then reported to the AS which has to interpret them according to the current service configuration as e.g. dialled terminating subscriber number in a Three Party scenario or as a switching order command e.g. during Call Toggle Service. It is the responsibility of the AS to close the dialogue to the MRF after completion of the evaluation of the reported digits. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 159 Annex H (normative): Support of PSTN modem calls H.1 Introduction This annex describes the details for emulation of PSTN modem calls for support of services Voiceband Data in general and Fax over IP in particular. The following flavours of support are taken into consideration: • optional support of Voiceband Data over IP (VBDoIP) according to V.152 [48]; • optional support of Fax over IP (FoIP) according to T.38 [49]. H.2 Voiceband Data over IP emulation service according to V.152 H.2.1 Introduction The support of Voiceband Data (VBD) over IP according V.152 [48] is optional, but recommended as default for the emulation of PSTN modem calls. NOTE: See also clause 8 in TR 183 072 [i.5]. H.2.2 IP transport services for V.152 VBD V.152 VBD defines different transport services, driven e.g. by Grade of Service (GoS) conditions of the IP network or business models for PSTN emulation services. The V.152-capable PES endpoint should explicitly indicate the requested IP transport service, if the PES endpoint want to use the capabilities for enhancing the transport reliability, in his SDP offer and table H.1. NOTE: See also clause 7.1.1 in TR 183 072 [i.5]. This is achieved by the inclusion of an explicit VBD codec in its list of codecs, as described in V.152 [48]. H.2.2.1 Examples H.2.2.1.1 Example 1 "Non-assured VBD mode" Example signalling and SDP encoding for the SDP Offer may be found: • for "revised SDP Offer/Answer": see e.g. table 8 in V.152 [48]; • for "legacy SDP Offer/Answer": see e.g. table 7 in V.152 [48]. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 160 Another example for "legacy SDP Offer/Answer" would be: Table H.1: Example SDP encoding – Offer in Legacy SDP Offer/Answer syntax SDP encoding (shortened SDP description) Comments v=0 o=- 0 0 IN IP4 blabla.domain s=H.248 Context t=0 0 c=IN IP4 11.9.20.01 m=audio 33906 RTP/AVP 8 101 111 a=rtpmap:101 telephone-event/8000 a=rtpmap:111 PCMA/8000 a=gpmd:111 vbd=yes In the example, static payload type '8' and dynamic payload type '111' each represent the encoding format 'PCMA'. The payload type '8' is not associated with VBD. The payload type '111' (PCMA) relates to the V.152 VBD codec. The packetization times for Audio and VBD are both unspecified, thus default values would be supposed. Network telephone events using payload type '101' (RFC 4733 [17] packets). H.2.2.1.2 Example 2 "Assured VBD mode, using RTP packet redundancy" Example signalling and SDP encoding for the SDP Offer may be found: • for "revised SDP Offer/Answer": see e.g. table 14 in V.152 [48]; • for "legacy SDP Offer/Answer": see e.g. table 13 in V.152 [48]. H.2.2.1.3 Example 3 "Assured VBD mode, using Forward Error Correction" Example signalling and SDP encoding for the SDP Offer may be found: • for "revised SDP Offer/Answer": see e.g. table 16 in V.152 [48]; • for "legacy SDP Offer/Answer": see e.g. table 15 in V.152 [48]. H.2.3 Transitioning between Audio and VBD Mode Transitioning between Audio mode and VBD mode is possible in both directions and (in general) can occur multiple times within a single call/session (see also clause 7.6 in TR 183 072 [i.5]). The procedures for transitioning between these two modes of operation are described in clause 10 of V.152 [48]. H.3 Fax over IP relay service according to T.38 H.3.1 Introduction The support of Fax over IP according T.38 [49] is optional. In order to improve the interoperability of T.38 fax gateways (i.e. PSTN-to-IP gateways with T.38 support, but also T.38 Internet-aware fax devices (IAF)) connected to a VGW or a MGW which conform to the present document shall support a minimum set of requirements selected out of the range presented in T.38. NOTE: Additional guidance for the support of T.38 and V.152 at H.248-based gateway control interfaces is available in the ARGW H.248 Profile TS 183 002 [5]. However, TS 183 002 [5] is not considering the codec negotiation process at application (call) control interfaces like SIP/SDP. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 161 H.3.2 T.38 stimuli detection (by PES endpoint) and Transitioning between Audio / T.38 Modes • Connection establishment related aspects: - The gateway should initiate a voice call with audio codec and should reserve resources for T.38 service, and, upon fax detection, the switch-over to T.38 fax capabilities is triggered. • Transitioning between Audio mode and T.38 mode is possible in both directions and (in general) can occur multiple times within a single call/session. The procedures for transitioning between these two modes are described in T.38 [49]. • During this switchover and the facsimile call the voice channel shall be muted. The voice channel may be used again once the end of facsimile transmission is detected (note). • Alternately, some implementations may choose to replace the voice channel with a facsimile channel (note). NOTE: See also note at the end of clause 6.1 in TR 183 072 [i.5]). Reuse or replacement of the "voice channel" may require further studies with respect to autonomous transitioning behaviour and conditions on initial SIP/SDP Offer/Answer exchange. E.g. T.38 Version 4 supports autonomous transitioning (see clause D.2.2.4.3 in [49]). H.3.3 T.38 configuration details NOTE: General aspects of T.38 configurations are outlined in clause 7.1.2.1 in TR 183 072 [i.5]. It is recommended to explicitly indicate and negotiate at least the following minimum set of T.38 configuration parameters: • T.38 protocol version ("there are five versions (0 to 4) up to now"); • T.38 transport mode ("there are the three modes UDTPL/UDP, TPKT/TCP, RTP/UDP"); • T.38 data rate management method; • T.38 error correction; • T.38 fax transcoding ("none", "MMR" or "JBIG"); and • T.38 supported modem ("primarily due to V.34 versus non-V.34-G3FE device"). The following specific configuration details shall be considered by the present document: • T.38 transport mode: IFP packets shall be transferred by means of UDP transport applying IFP encapsulation in UDPTL (Facsimile UDP Transport Layer protocol). • Data rate management method 2: (see T.38 [49], section 8.2) shall be supported as this method is declared as mandatory for UDP. H.3.4 Control plane aspects • SIP/SDP: - Generally annex D of T.38 shall apply to AGCF/VGW conforming to the present document. All parameters specified as an extension to SDP in T.38, clause D.2.1.3.1, shall be negotiated. NOTE: See also guidelines by clauses 7.1.2.1, 7.1.2.2 and 8 by TR 183 072 [i.5]. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 162 H.3.5 Enhancements of T.38 The following general assumptions related to the existing text given in T.38 shall apply. The aspects are given by different modes of the user plane interworking function by T.38 endpoints and correspondent control plane signalling. H.3.5.1 T.38 Versioning • The VGW should support T.38 ASN.1 version number 3 in order to enable transfer rates beyond 14 400 bit/s, e.g. support of V.34 with 33 600 bit/s. For GW offering both V.152 VBD with G.711 and T.38, the gateway based on configuration may transport V.34 in V.152 VBD with G.711 or stay in T.38 with fallback to V.17/V.29 if T.38 version 3 with V.34 is not managed by both peers. T.38, clause D.2.2.5 "Support of T.38/V.34G3 facsimile and fallback to T.38/G3 facsimile" shall be considered in case of V.34 transported facsimile traffic. • The VGW may support T.38 version 4, e.g. in order to indicate support of T.38 parameter "T38ModemType". NOTE: It is expected that the interworking between different T.38 versions will be addressed by ITU-T Recommendation T.38 [49]. The default case should be the same T.38 version negotiated by both "T.38 endpoints". H.3.5.2 T.38 mode concerning G3FE with and without V.34 modem There are two types of G3FE: with and without support of V.34. • The V.34 detection should be done on ANSam detection by the GW. • Principle V.34 support should be indicated by T.38 parameter "T38ModemType" if correspondent T.38 version would be supported. NOTE: The interworking details between "T.38/G3" and "T.38/V.34 G3" capable T.38 endpoints are specified by clause D.2.2.5 in T.38 [49]. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 163 Annex I (normative): Gap analysis - IMS-based PES versus support by 3GPP IMS I.1 Background The present document defines SIP and SDP capabilities, required for the emulation of PSTN modem calls by the IMS domain. These signalling capabilities are primarily subject of 3GPP specifications, resulting in a dependency of the present document to some 3GPP specifications (see clause 6.3). Purpose of this annex: explicit indication of service gaps and possible impact on network deployments. NOTE: This annex may be deleted again in future in case of correspondent SIP/SDP support by the referred 3GPP specifications. I.2 IMS-based PES capabilities: PSTN modem call support I.2.1 Not supported features Missing SDP support (see clause 6.3.5), - SDP parameters and SDP Offer/Answer negotiation capabilities -, limits the usage of emulation services for PSTN modem calls in IMS-based PES installations. See table I.1. Table I.1: Feature gap with regards to PSTN modem calls No. Capability Support? Clause(s) 1 VBDoIP pass-through service (V.152) for PSTN modem calls in general No 6.3.1.2.1.2, 6.3.1.2.1.3 (a), 6.3.1.2.1.4, H.2 2 VBDoIP pass-through service (V.152) for PSTN facsimile/modem calls in particular No see No. 1 3 VBDoIP pass-through service (V.152) for PSTN data/modem calls in particular No see No. 1 4 VBDoIP pass-through service (V.152) for PSTN text/modem calls in particular No see No. 1 5 FoIP packet-relay service (T.38) for PSTN facsimile/modem calls Limited (note 1) 6.3.1.2.1.2, 6.3.1.2.1.3 (b1, b2), 6.3.1.2.1.5, H.3 6 Offering alternative media configurations VBDoIP V.152 vs FoIP T.38 No 6.3.1.2.1.3 (a) 7 VBDoIP-type specific configurations (VBD codec type, VBD transport mode) No see No. 1 and H.2.2 8 FoIP-type specific configurations (T.38 configuration variants) No see No. 5 and H.3.3 9 Check of FoIP T.38 support and required T.38 configuration in detail already during call establishment phase (note 2) No 6.3.1.2.1.3 (b2), 6.3.1.2.1.5 (b2), 6.3.1.4 10 Individual packetization times for media configurations (e.g. between VoIP audio and VBDoIP pass-through) No see No. 1 ETSI ETSI TS 183 043 V3.4.1 (2011-04) 164 No. Capability Support? Clause(s) 11 Support of "G3-Superfax" (i.e. V.34-capable T.38) No see No. 5 and H.3.5.2 12 Fast call establishment phases (single-cycle SIP/SDP Offer/Answer) No (note 3) 6.3.1.2 NOTE 1: The RFC 3362 [i.8] MIME type for T.38 is already supported (by TS 129 163 [32], TS 124 229 [4]), but allows only the indication of a T.38 media stream in SDP, but not any indication and negotiation of T.38 configuration settings in detail. NOTE 2: Requires revised SDP Offer/Answer in general and the latent configuration capability in particular. NOTE 3: Efficient single cycle negotiations may be supported with revised SDP Offer/Answer, but may be not guaranteed with legacy SDP Offer/Answer. I.2.2 Impact on IMS-based PES networks I.2.2.1 Intra-network call Any service guarantees may not be provided for the services indicated in previous clause. There will be a best effort approach in terms of • a minimum FoIP packet-relay (T.38) service; and • a pseudo-VBDoIP pass-through (non-V.152) service. The best effort approach implies associated configuration management activities in all related IMS-based PES entities (in order to avoid different configuration settings; see e.g. also clause H.3 in T.38). I.2.2.2 Inter-network call Peering scenarios with other SIP networks may lead to incoming SIP messages with unsupported SDP. Such SDP elements would be ignored by the receiving SIP instances. I.3 IMS-based PES capabilities: other services None identified. ETSI ETSI TS 183 043 V3.4.1 (2011-04) 165 Annex J (informative): Bibliography • ETSI ES 282 007: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IP Multimedia Subsystem (IMS); Functional architecture". ETSI ETSI TS 183 043 V3.4.1 (2011-04) 166 Annex K (informative): Change history Date WG Doc. CR Rev CAT Title / Comment Current Version New Version 01-05-06 Publication of v1.1.1 Publication of 2.3.1 29-06-09 20WDT040r1 087 F Primitive dialogue between the SIP UA and MGC 2.4.0 3.0.1 29-06-09 20WDT041r1 088 F Clarification of dsl_location_parameter 2.4.0 3.0.1 29-06-09 20WDT198r2 089 F Timer handling for in-Dialog method 2.4.0 3.0.1 29-06-09 20WDT200r2 090 F Tight coupling - align Call Toggle with 3PTY service 2.4.0 3.0.1 10-06-09 20bTD030r1 091 F MCID – Loose coupling 2.4.0 3.0.1 10-06-09 21WTD230r1 092 F Direction of charging messages 2.4.0 3.0.1 10-06-09 21WTD141r2 093 F Signalling Gateway 2.4.0 3.0.1 10-06-09 21WTD099r1 094 F Registration / Deregistration in the feature manager 2.4.0 3.0.1 10-06-09 21WTD098r1 095 F Processing of Switching Order Commands 2.4.0 3.0.1 10-06-09 21WTD139r1 096 F Call Forwarding 2.4.0 3.0.1 10-06-09 21WTD097r1 097 F MWI 2.4.0 3.0.1 10-06-09 21WTD100r3 098 F MRF connection on flash-hook 2.4.0 3.0.1 10-06-09 21WTD138r1 099 B Default coding for alert-info 2.4.0 3.0.1 10-06-09 21WTD140r1 100 F Immediate Call Setup 2.4.0 3.0.1 CRs 087 to 090 TB approved at TISPAN#20, CRs091 to 100 TB approved at TISPAN#21 2.4.0 3.0.1 20-06-09 21BTD040r1 002 F Improvements of MCID specifications 3.0.1 3.0.2 20-06-09 21BTD122r1 003 F Overlap_dialling_option_applying_to_Three_Party_service 3.0.1 3.0.2 20-06-09 21BTD124r1 004 D Editorial_changes_in_B.4.2.2.2_and_F.2.1.1.1 3.0.1 3.0.2 20-06-09 21BTD043r1 005 F Improvements of Call Waiting specifications 3.0.1 3.0.2 01-10-09 22WTD33r1 006 B New clause for CCBS, CCNR 3.0.2 3.0.3 01-10-09 22WTD207 007 A Align AOC information XML Document procedures with 3GPP TS 24.647 3.0.2 3.0.3 01-10-09 22WTD53r3 008 B Support_of_Voiceband_Data_and_Fax_over_IP – new annex H 3.0.2 3.0.3 01-10-09 22WTD56r2 009 B Support_of_T.38 3.0.2 3.0.3 CRs 002 to 009 TB approved at TISPAN#22 3.0.2 3.1.0 13-11-09 22bTD042r3 010 C POTS_pulse_metering_in_multiple_call_leg_scenarios 3.1.0 3.1.1 13-11-09 22bTD143r3 011 B New section: Non-V.152 VBD 3.1.0 3.1.1 13-11-09 22bTD179r3 012 D Clarifications_in_clause_6.3.1 3.1.0 3.1.1 21-12-09 23WTD064r1 014 C Clause 6.3.1 - T.38 modes T.38/V.17 and T.38/V.34 3.1.1 3.1.2 21-12-09 23WTD065r1 015 C Clause 6.3.1 Further Updates 3.1.1 3.1.2 21-12-09 23WTD066r1 016 C Annex H.2 - V.152 Updates 3.1.1 3.1.2 21-12-09 23WTD067r1 017 C Annex H.3 – T.38 Updates 3.1.1 3.1.2 21-12-09 23WTD134r2 018 F Flash Hook handling – tight coupling 3.1.1 3.1.2 CRs 010 to 012 and CRs 014 to 018 TB approved at TISPAN#23 3.1.2 3.2.0 04-02-10 TISPAN03(10) 0036r2 019 F Clause_6.3_editors_notes_update 3.2.0 3.2.1 03-05-10 TISPAN03(10) 0072r1 020 F Clause 6.3.1.4 Preferred Configuration List 3.2.1 3.2.2 03-05-10 TISPAN03(10) 0074r1 021 F cl. H.2.2 Examples for V.152 transport services 3.2.1 3.2.2 03-05-10 TISPAN03(10) 0075r3 022 F Clarification of fax/Modem text 3.2.1 3.2.2 03-05-10 TISPAN03(10) 0077r1 023 F cl. 6.3.1.2 Revised SDP OA option 3.2.1 3.2.2 03-05-10 TISPAN03(10) 0079r1 024 F Use of Digit maps in tigh-coupling mode 3.2.1 3.2.2 03-05-10 TISPAN03(10) 0114r1 025 F Protocol for using analog signalling 3.2.1 3.2.2 03-05-10 TISPAN03(10) 0078r3 026 F On-Hook management 3.2.1 3.2.2 CRs 019 to 026 TB approved at TISPAN#24 3.2.2 3.3.0 08-06-10 TISPAN03(10) 0199r1 027 F Various corrections for clause 7 and annex B 3.3.0 3.3.1 08-06-10 TISPAN03(10) 0180r4 028 F VGW procedures for analog lines 3.3.0 3.3.1 08-06-10 TISPAN03(10) 0192r2 029 F On-Hook management 3.3.0 3.3.1 08-06-10 TISPAN03(10) 0183r3 030 F SDP support for PSTN modem calls 3.3.0 3.3.1 08-06-10 TISPAN03(10) 0189r1 031 D Further updates (editorial alignment) 3.3.0 3.3.1 08-06-10 TISPAN03(10) 0184r1 032 C Align clauses 6.3.2 to 6.3.1 3.3.0 3.3.1 08-06-10 TISPAN03(10) 0186r2 033 F clause 6.3.1 update 3.3.0 3.3.1 08-06-10 TISPAN03(10) 0187r2 034 F Annex H update 3.3.0 3.3.1 15-09-10 TISPAN03(10) 0218r1 035 F clauses 6.3.1 and 6.3.2 updates 3.3.1 3.3.2 15-09-10 TISPAN03(10) 0219r1 036 F Annex H update 3.3.1 3.3.2 ETSI ETSI TS 183 043 V3.4.1 (2011-04) 167 Date WG Doc. CR Rev CAT Title / Comment Current Version New Version 15-09-10 TISPAN03(10) 0220r1 037 F Annex I update 3.3.1 3.3.2 15-09-10 TISPAN03(10) 0221r1 038 F cl. 6.3.5 discussion on SDP support for PSTN modem calls 3.3.1 3.3.2 15-09-10 TISPAN03(10) 0222r1 039 F clauses 9.3.1.4 and B.4.2.2.3 ed notes update 3.3.1 3.3.2 27-10-10 TISPAN03(10) 0257r1 040 F New annex: Gap analysis IMS-based PES vs 3GPP IMS 3.3.2 3.3.3 27-10-10 TISPAN03(10) 0247r1 041 F Priority lines on a VGW 3.3.2 3.3.3 27-10-10 TISPAN03(10) 0264r1 042 F Updating references 3.3.2 3.3.3 27-10-10 TISPAN03(10) 0252r1 043 F P-Access-Network-Info for a VGW 3.3.2 3.3.3 27-10-10 TISPAN03(10) 0248r1 044 A Physical termination selection during incoming calls 3.3.2 3.3.3 27-10-10 TISPAN03(10) 0281r1 045 F Resolving Editor’s Notes 3.3.2 3.3.3 07-12-10 TISPAN03(10) 0286r1 046 F Miscellaneous Corrections 3.3.3 3.3.4 08-12-10 TISPAN03(10) 0286r1 046 F Miscellaneous Corrections (editorial change) 3.3.4 3.3.5 Publication 3.3.5 3.4.1 ETSI ETSI TS 183 043 V3.4.1 (2011-04) 168 History Document history V1.1.1 May 2006 Publication V1.2.1 February 2009 Publication V2.3.1 March 2009 Publication V2.5.1 February 2011 Publication V3.4.1 April 2011 Publication |
86a8cb2417653fdbaee677b0a1930040 | 183 020 | 1 Scope | The present document describes the protocol specifications and profiles for the interface between the UAAF in the visited NGN network (UAAF-proxy) and the UAAF in the home NGN network (UAAF-server). The specifications of this interface will be common for both xDSL and WLAN access networks, including possible other access network types as well. Specific differences, if any, will be called out. |
86a8cb2417653fdbaee677b0a1930040 | 183 020 | 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. [1] ETSI ES 282 001: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Functional Architecture Release 1". [2] ETSI ES 282 004: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Functional Architecture; Network Attachment Sub- System (NASS)". [3] ETSI TS 129 234: "Universal Mobile Telecommunications System (UMTS); 3GPP system to Wireless Local Area Network (WLAN) interworking; Stage 3 (3GPP TS 29.234 Release 6)". [4] Wi-Fi Alliance: "WPA™ Deployment Guidelines for Public Access Wi-Fi® Networks". NOTE: http://www.wi-fi.org/OpenSection/pdf/WPA_for_Public_Access_Final.pdf [5] IETF RFC 3748: "Extensible Authentication Protocol (EAP)". [6] IETF RFC 2486bis: "The Network Access Identifier". [7] ETSI TS 183 019: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Network Attachment; Network Access xDSL and WLAN Access Networks; Interface Protocol Definitions". [8] IETF RFC 2865: "Remote Authentication Dial In User Service (RADIUS)". [9] ETSI ES 283 034: "TISPAN; Network Attachment Sub-System (NASS); e4 interface based on the DIAMETER protocol". [10] ETSI TS 183 017: "Telecommunications and Internet Converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control: DIAMETER protocol for session based policy set-up information exchange between the Application Function (AF) and the Service Policy Decision Function (SPDF); Protocol specification". [11] ETSI ES 283 035: "TISPAN; Network Attachment Sub-System (NASS); e2 interface based on the DIAMETER protocol". [12] IETF RFC 3539: "Authentication, Authorization and Accounting (AAA) Transport Profile". [13] IETF RFC 4005: "Diameter Network Access Server Application". [14] IETF RFC 4072: "Diameter Extensible Authentication Protocol (EAP) Application". ETSI ETSI TS 183 020 V1.1.1 (2006-03) 6 [15] IETF RFC 3588: "Diameter Base Protocol". [16] IETF RFC 4372: "Chargeable User Identity". [17] IETF RFC 2866: "RADIUS Accounting". [18] IETF RFC 3580: "IEEE 802.1X Remote Authentication Dial In User Service (RADIUS) Usage Guidelines". [19] IETF RFC 2548: "Microsoft Vendor-specific RADIUS Attributes". |
86a8cb2417653fdbaee677b0a1930040 | 183 020 | 3 Definitions and abbreviations | |
86a8cb2417653fdbaee677b0a1930040 | 183 020 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: access network: collection of network entities and interfaces that provide the underlying IP transport connectivity between end user devices and NGN entities Attribute-Value Pair: see RFC 3588 [15], it corresponds to an Information Element in a Diameter message functional entity: entity that comprises a specific set of functions at a given location. Functional entities are logical concepts, grouping of functional entities are used to describe practical physical realizations Core Network: portion of the delivery system composed of networks, systems equipment and infrastructures, connecting the service providers to the access network user equipment: one or more devices allowing a user to access services delivered by TISPAN NGN networks NOTE: This includes devices under user control commonly referred to as CPE, IAD, ATA, RGW, TE, etc., but not network controlled entities such as access gateways. visited NGN network: NGN network through which the User Equipment gains network connectivity NOTE: The NGN Network includes both the Access Network and the Core Network. The User Equipment does not have a service relationship with the business entity that operates this network. home NGN network: NGN network through which the User Equipment gains network connectivity NOTE: The NGN Network includes both the Access Network and the Core Network. The User Equipment has a service relationship with the business entity that operates this network. |
86a8cb2417653fdbaee677b0a1930040 | 183 020 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: 3GPP Third Generation Project Partnership AAA Authentication, Authorization and Accounting AAA-H AAA-Home AAA-V AAA-Visited AMF Access Management Function AP Access Point ATA Analogue Terminal Adaptor AVP Attribute Value Pair CNG Customer Network Gateway EAP Extensible Authentication Protocol EAPOL EAP Over Lan GSMA Global System for Mobile communications Association IAD Integrated Access Device IETF Internet Engineering Task Force ETSI ETSI TS 183 020 V1.1.1 (2006-03) 7 IP Internet Protocol NAI Network Access Identifier NASS Network Attachment SubSystem NGN Next Generation Network PEAP Protected EAP RGW Residential GateWay STA Station TE Terminal Equipment TLS Transport Layer Security TTLS Tunnelled TLS UAAF User Access Authorization Function UE User Equipment WLAN Wireless Local Area Network WPA Wi-Fi Protected Access xDSL Digital Subscriber Line |
86a8cb2417653fdbaee677b0a1930040 | 183 020 | 4 NGN General Architecture | ES 282 001 [1] provides a description of the general network architecture of the NGN. The model is depicted in figure 1. UE Visited NGN Network Home NGN Network e1 e5 Figure 1: General NGN Network Model Interface e1 is an access-network-specific interface, and is dependant on the access technology being used (xDSL, WLAN, and so on). Interface e5 is a roaming interface, and is independent of the access technology. Interface e5 is used to provide a consistent method for the visited NGN network to communicate with the home NGN network. ETSI ETSI TS 183 020 V1.1.1 (2006-03) 8 Figure 2 depicts the functional composition of the access network and the NGN core for the roaming scenario, where a UE obtains network access via a visited NGN network and authenticates back with the home NGN network. Details of this model may be found in ES 282 004 [2]. Home NGN Access Network UAAF Visited NGN Access Network PDBF CPE (CNG/TE) e5 ARF a4 Service control subsystems a3 a1 a2 e1 e2 e4 e3 Resource and Admission Control Subsystem CLF NACF CNGCF AMF UAAF Home NGN Access Network UAAF Visited NGN Access Network PDBF UE e5 ARF Visited NGN network Home NGN network Access Transport network e1 Figure 2: NASS mapped onto functional network roles - roaming scenario |
86a8cb2417653fdbaee677b0a1930040 | 183 020 | 4.1 Overview of Interface e5 | The present document details the protocols and profiles for interface e5. This interface is intended to be used between a UAAF-proxy and a UAAF-server, which may be in different distractive domains. This interface allows the UAAF-proxy to request the UAAF-server for user authentication and authorization, based on user profiles. It also allows the UAAF-proxy to forward accounting data for the particular user session to the UAAF-server. The UAAF-proxy will forward access and authorization requests, as well as accounting messages, received over interface a3 from the AMF, to the UAAF-server over interface e5. Responses received back in return from the UAAF-server over interface e5 will be forwarded to the AMF over interface a3. A bilateral trust relationship will need to be setup between the UAAF-proxy and the UAAF-server in order to facilitate this exchange. The specifications for interface e5 will be similar to that of interface a3, between the AMF and the UAAF in the visited network. This interface therefore supports AAA message exchange between the UAAF-proxy and the UAAF-server. RADIUS and Diameter are two possible options for carrier protocols on this interface, and detailed requirements are listed in the present document. Interface e5 supports both authentication/authorization and accounting message exchange. The present document will be common for both xDSL and WLAN access networks, as well as for potential other types of access networks. Specific differences, if any, will be called out in the document. ETSI ETSI TS 183 020 V1.1.1 (2006-03) 9 |
86a8cb2417653fdbaee677b0a1930040 | 183 020 | 5 Protocols and profiles for Interface e5 | |
86a8cb2417653fdbaee677b0a1930040 | 183 020 | 5.1 802.1X-based Authentication | Figure 4 depicts a typical protocol stack for 802.1X-based authentication. Further details may be found in Wi-Fi Alliance [4]. The EAP messages are carried over EAPOL (EAP over LAN) frames between the UE and the AP and then re-encapsulated in RADIUS or Diameter messages when sent from the AP to the home AAA Server (via zero or more AAA proxies). In figure 4, the UE (mobile station) acts as the 802.1X supplicant, the AP acts as the authenticator, and the RADIUS AAA server acts as the authentication server. For security reasons, RADIUS is sometimes also carried over IPsec (RFC 3162 (see Bibliograhy) describes use of RADIUS over IPv6-IPsec, and RFC 3580 [18] also recommends use of IPsec to protect RADIUS). Diameter may also be used instead of or in addition to RADIUS. Figure 3: 802.1X/EAP Authentication Protocol Stack ETSI ETSI TS 183 020 V1.1.1 (2006-03) 10 Figure 5 depicts a typical 802.1X-based authentication scenario. The UE attempts to associate with an AP and is challenged to authenticate. At this point, the UE needs to indicate its user identity. There are usually two parts to this identity: the user name and the realm. Typically, these are combined into a Network Access Identifier (NAI) of the form user@realm. The realm part of the NAI is used to establish a connection with the appropriate AAA-H for that user. This presumes that the visited network recognizes that realm name. If this is not the case, then the visited network will signal an authentication failure back to the UE. The UE can then either try a different account (with a different realm) or can try to establish a new account on the visited network. If those alternatives also fail, the UE will be denied access or will be granted only limited guest access. Figure 4: 802.1X-based authentication with RADIUS as AAA protocol To avoid revealing the true user identity to an entity other than the home service provider, especially across the WLAN radio link, the UE can use a generic user name like "anonymous" or "user" in the NAI given in the initial identity exchange. The realm part of the NAI is the only information the visited network needs to know at this point. If PEAP or TTLS are used to establish a secure tunnel between the STA and the AAA-H, then the protected identity exchange will not be visible to the visited network or to any eavesdroppers. The visited network will eventually need to obtain some identity value for charging and billing purposes if the authentication is successful. The home network can provide the identity that identifies the account for charging. This account is used between the visited network and the home network. This account need not be the same as that used by the home network to bill the subscriber. Furthermore, this identity can be an alias specified by the home provider rather than information that might compromise the true identity of the UE user. The identity used for charging can be shared only with the AAA infrastructure and never needs to be sent unprotected across the WLAN radio link. ETSI ETSI TS 183 020 V1.1.1 (2006-03) 11 |
86a8cb2417653fdbaee677b0a1930040 | 183 020 | 5.2 Intermediaries | An intermediary may be defined as an entity that manages and facilitates AAA transactions in real time between 2 service provider network entities. One or more intermediaries may exist between the visited and the home NGN networks, as shown in figure 5. The existence of these intermediaries should be transparent to the AAA message flow, and each intermediary shall support the requirements as noted in the following clauses. Figure 5: Inclusion of intermediaries |
86a8cb2417653fdbaee677b0a1930040 | 183 020 | 5.3 Requirements of the visited NGN network | One endpoint of interface e5 is the visited NGN network. Specifically, the access network within the visited NGN network should support the following requirements, and interface e5 for AAA logically extends all the way from the access network to the UAAF in the home NGN network. 1) The visited NGN network shall comply with the relevant requirement in TS 129 234 [3], clauses 4 and 5. In TS 129 234 [3], all references to "3GPP AAA Proxy" implies the requirements shall be met by the visited NGN network and all references to "3GPP AAA Server" implies the requirements are to be met by the home NGN network. 2) The visited NGN network shall support either RADIUS or Diameter as the AAA transport. 3) If Diameter is supported, the visited NGN access network shall support the following IETF standards: a) RFC 3539 [12], Authentication, Authorization and Accounting (AAA) Transport Profile. b) RFC 4005 [13], Diameter Network Access Application. c) RFC 4072 [14], Diameter Extensible Authentication Protocol (EAP) Application. 4) If RADIUS is supported, the visited NGN access network shall support the following IETF standards: a) Interpretation of Idle-Timeout attribute in RFC 2865 [8]: If a wireless station is logged on to the network but has not generated outbound IP data traffic (the definition of what constitutes this traffic is being defined in the RADEXT group in the IETF) for a specific interval of time, and if the home NGN network has specified this interval of time via the Idle-Timeout attribute, the visited access network shall proactively disconnect the wireless station and generate an Accounting-Stop message. The actual Idle- Timeout value may be set locally on the access network or via the Idle-Timeout attribute provided by the Home NGN network. If this attribute is present in the AAA message, it shall override any local timeout value set on the access network. b) Interpretation of Session-Timeout attribute in RFC 2865 [8]: The timeout value is typically set according to the expiration time of the prepaid account. If the wireless station remains connected until the timeout expires, the access network either automatically disconnects that wireless station or requests for a re- authentication, depending on the value of the Termination-Action attribute. c) The access network shall be able to appropriately process receipt of at least 5 Class attributes (defined in RFC 2865 [8]). d) RFC 2866 [17], RADIUS Accounting: I) The Accounting-Start message shall be sent when the wireless station successfully authenticates to the network and is authorized for services. ETSI ETSI TS 183 020 V1.1.1 (2006-03) 12 II) The access network shall detect session termination, either via user disconnect/disassociate, inactivity timer expiry, or session-timeout. When this happens, an Accounting-Stop message shall be sent. III) The access network shall send Accounting-Interim records at the interval specified by the home network. IV) The access network shall report the wireless station IP address in the Framed-IP-Address RADIUS attribute in the Accounting-Interim and Accounting-Stop messages. Inclusion of the wireless station IP address in the Framed-IP-Address RADIUS attribute in the Accounting-start message is optional. V) If multiple accounting messages are generated by different physical entities within the access network for the same session, all related accounting messages shall contain the same Session-Id. VI) The NAS shall send the appropriate Accounting On and Off messages to the home network when it undergoes a reset, to enable session state to be cleared on the home AAA server. VII) The access network may attempt to deliver accounting records until an acknowledgement is received. e) RFC 3580 [18], RADIUS Usage Guidelines. f) RFC 3748 [5], Extensible Authentication Protocol (EAP). g) The visited NGN network shall be able to accept WPA keying information contained in Microsoft vendor-specific RADIUS attributes as defined in the following sections of RFC 2548 [19]: 1) Section 2.4.2: MS-MPPE-Send-Key. 2) Section 2.4.3: MS-MPPE-Recv-Key. h) The visited NGN network shall be able to proxy RADIUS Authentication and Accounting messages as defined in RFC 2865 [8] and RFC 2866 [17]. i) The visited NGN network shall be able to send back the Chargeable-User-Identity attribute (RFC 4372 [16]), defined in the RADEXT group in the IETF, in Accounting messages, if it was send in an authorization message by the authenticating AAA server. 5) The visited NGN access network should support IPSec for protecting AAA message flows. |
86a8cb2417653fdbaee677b0a1930040 | 183 020 | 5.4 Requirements of the home NGN network | 1) The home NGN network shall comply with the relevant requirements in TS 129 234 [3], clauses 4 and 5. In TS 129 234 [3], all references to "3GPP AAA Proxy" implies the requirements shall be met by the visited NGN network (specifically the access network), and all references to "3GPP AAA Server" implies the requirements are to be met by the home NGN network. 2) The home NGN network shall support WPA/802.1X: a) The home network shall support EAP methods defined in [7], clause 8.2. b) The home network shall support NAIs as specified by RFC 2486bis [6]. 3) The home NGN network may support WPA2. 4) The visited NGN network shall support either RADIUS or Diameter as the AAA transport. 5) The home NGN network shall support the following IETF standards: a) RFC 3748 [5], Extensible Authentication Protocol (EAP) b) RFC 2486 bis [6], Network Access Identifier 6) If Diameter is supported, the home NGN network shall support the following IETF standards: ETSI ETSI TS 183 020 V1.1.1 (2006-03) 13 a) RFC 3539 [12], Authentication, Authorization and Accounting (AAA) Transport Profile. b) RFC 4005 [13], Diameter Network Access Application. c) RFC 4072 [14], Diameter Extensible Authentication Protocol (EAP) Application. 7) If RADIUS is supported, the home NGN network shall support the following IETF standards: a) RFC 2865 [8], RADIUS Standard. b) RFC 2866 [17] , RADIUS Accounting. c) RFC 3580 [18], RADIUS Usage Guidelines. d) The home NGN network shall support the transmission of WPA keying information to the access network via Microsoft vendor-specific RADIUS attributes as defined in the following sections in RFC 2548 [19]: 1) Section 2.4.2: MS-MPPE-Send-Key. 2) Section 2.4.3.: MS-MPPE-Recv-Key. 8) The home network should support IPSec for protecting AAA message flows. |
86a8cb2417653fdbaee677b0a1930040 | 183 020 | 5.5 Subscriber Profile Transfer | The protocol used on the e5 interface shall support the transport of subscriber profile information as defined in ES 282 004 [2]. Table 1 provides the list of information elements to be carried over the interface for that purpose and indicates the list of Diameter attributes that shall be supported to achieve it. Table 1: Diameter attributes for Subscriber Profile Transfer Information Element Description DIAMETER attribute Defined in SubscriberID The identity of the subscriber requesting IP connectivity. User-Name RFC 3588 [15] GloballyUniqueAddress This information element contains: - The IP address of the user equipment used by the subscriber for which profile information is being pushed. - The addressing domain in which the IP address is significant. Globally-Unique- Address ES 283 034 [9] InitialGateSetting This information element contains: - The list of default destination IP addresses and ports to which traffic can be sent. - The maximum amount of bandwidth that can be used without explicit authorisation in the uplink direction. - The maximum amount of bandwidth that can be used without explicit authorisation in the downlink direction. Initiate-Gate-Setting ES 283 034 [9] ETSI ETSI TS 183 020 V1.1.1 (2006-03) 14 Information Element Description DIAMETER attribute Defined in QoSProfile (NOTE 1) For each subscribed transport service class and application class, this information element contains: - The maximum amount of bandwidth subscribed by the attached user in the uplink direction. - The maximum amount of bandwidth subscribed by the attached user in the downlink direction. - The maximum priority allowed for any reservation request. QoS-Profile ES 283 034 [9] PrivacyIndicator (see note) This information element provides policy rules for disclosure of subscriber profile elements to applications. Privacy-Indicator The present document (clause 5.5.1). NOTE: This information element may be repeated. There is currently no standard solution defined for transferring subscriber profile data across networks where RADIUS is used instead of Diameter. This may be defined in Release 2. |
86a8cb2417653fdbaee677b0a1930040 | 183 020 | 5.5.1 Privacy-Indicator AVP | The Privacy-Indicator AVP (AVP code 440 13019) is of type Grouped and provides policy rules for disclosure of subscriber profile elements to applications. AVP Format: Privacy-Indicator ::= < AVP Header: 440 13019 > * {Requested-Information} * [AF-Application-Identifier] Each Requested-Information AVP identifies a profile element whose disclosure is restricted to the list of applications identified by the AF-Application-Identifier AVPs. The Requested-Information AVP is defined in ES 283 035 [11] while the AF-Application-Identifier AVP is defined in TS 183 017 [10]. ETSI ETSI TS 183 020 V1.1.1 (2006-03) 15 Annex A (informative): Tracking of Standards-related Work A.1 Items to be tracked These are items that are on the standards-track in the standards bodies. Their progress should be monitored, and the relevant requirements reflected appropriately. 1) Carrying Location Objects in RADIUS a) The GEOPRIV task group in the IETF is working on this, and draft-ietf-geopriv-radius-lo (see Bibliography) should be tracked. 2) End to end capabilities support for RADIUS b) The RADEXT task group in the IETF is working on this, and draft-lior-radext-end-to-end-caps (see Bibliography) should be tracked. 3) RADIUS Extensions for IEEE 802 (see Bibliography) c) The RADEXT group in the IETF is working on this, and draft-congdon-radext-ieee802-03X3 (see Bibliography) should be tracked. 4) Network bandwidth parameters for RADIUS d) The RADEXT group in the IETF is working on this, and draft-lior-radius-bandwidth-capability (see Bibliography) should be tracked. ETSI ETSI TS 183 020 V1.1.1 (2006-03) 16 Annex B (informative): Bibliography IETF RFC 4284: "Identity selection hints for Extensible Authentication Protocol (EAP)". Draft-ietf-geopriv-radius-lo-: "Carrying Location Objects in RADIUS". Draft-lior-radext-end-to-end-caps-: "End-to-End Capabilities Support for Remote Authentication Dial In User Service (RADIUS)". VLAN, Prority, and Filtering Attributes NOTE: http://www.ietf.org/internet-drafts/draft-ietf-radext-ieee802-01.txt Draft-lior-radius-bandwidth-capability: "Network Bandwidth Parameters for Remote Authentication Dial In User Service (RADIUS)". ETSI TS 122 234: "Requirements on 3GPP system to Wireless Local Area Network (WLAN) Interworking; Release 6". ETSI TS 123 234: "3GPP system to Wireless Local Area Network (WLAN) Interworking; System descriptions; Release 6". International Roaming Access Protocols (IRAP): "Public WLAN Roaming Interface Specification". NOTE: ftp://download.intel.com/technology/comms/roaming/download/Roaming_Interfaces_v0.95.pdf ETSI TS 124 234: "3GPP system to Wireless Local Area Network (WLAN) Interworking; User Equipment to Network protocols; Stage 3; Release 6". GSMA IR 61: "WLAN Roaming Guidelines". IETF RFC 3162: "RADIUS and IPv6". ETSI ETSI TS 183 020 V1.1.1 (2006-03) 17 History Document history V1.1.1 March 2006 Publication |
f92d6483a77f6b4220575ae1402a53f3 | 183 042 | 1 Scope | The present document specifies the, stage three Protocol Description of the Completion of Communications to Busy Subscriber (CCBS) service and the Completion of Communication on no Reply (CCNR) service |
f92d6483a77f6b4220575ae1402a53f3 | 183 042 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity. |
f92d6483a77f6b4220575ae1402a53f3 | 183 042 | 2.1 Normative references | The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] ETSI 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 (Release 8)". |
f92d6483a77f6b4220575ae1402a53f3 | 183 042 | 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. |
f92d6483a77f6b4220575ae1402a53f3 | 183 042 | 3 Definitions and abbreviations | |
f92d6483a77f6b4220575ae1402a53f3 | 183 042 | 3.1 Definitions | For the purposes of the present document, the terms, definitions given in TS 124 642 [1] apply. |
f92d6483a77f6b4220575ae1402a53f3 | 183 042 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in TS 124 642 [1] apply. ETSI ETSI TS 183 042 V2.1.1 (2009-01) 6 4 Completion of Communications to Busy Subscriber (CCBS) The provisions of the present document are contained in TS 124 642 [1]. ETSI ETSI TS 183 042 V2.1.1 (2009-01) 7 Annex A (informative): Signalling flows Information is contained in TS 124 642 [1] ETSI ETSI TS 183 042 V2.1.1 (2009-01) 8 Annex B (informative): Example of filter criteria Information is contained in TS 124 642 [1] ETSI ETSI TS 183 042 V2.1.1 (2009-01) 9 Annex C (informative): Busy state monitoring procedures Information is contained in TS 124 642 [1] ETSI ETSI TS 183 042 V2.1.1 (2009-01) 10 Annex D (informative): Signalling requirements under discussion Information is contained in TS 124 642 [1] ETSI ETSI TS 183 042 V2.1.1 (2009-01) 11 History Document history V2.1.1 January 2009 Publication |
e142e055458ad4dd142e50ecfb0407b8 | 183 019 | 1 Scope | The present document describes the protocol specifications and profiles for supporting network attachment procedures at the interface between the User Equipment and the access network in an NGN network. |
e142e055458ad4dd142e50ecfb0407b8 | 183 019 | 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. |
e142e055458ad4dd142e50ecfb0407b8 | 183 019 | 2.1 Normative references | The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] ETSI ES 282 001: " Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Functional Architecture Release 1". [2] ETSI TS 124 234: "Universal Mobile Telecommunications System (UMTS); 3GPP system to Wireless Local Area Network (WLAN) interworking; User Equipment (UE) to network protocols; Stage 3 (3GPP TS 24.234 Release 6)". [3] Wi-Fi Alliance: "WPA™ Deployment Guidelines for Public Access Wi-Fi® Networks". NOTE: See: http://www.wi-fi.org/files/wp_6_WPA%20Deployment%20for%20Public%20Access_10-28-04.pdf [4] IETF RFC 4284: "Identity selection hints for Extensible Authentication Protocol (EAP)". [5] IETF RFC 3748: "Extensible Authentication Protocol (EAP)". [6] IETF RFC 4282: "The Network Access Identifier". [7] IEEE 802.1X-2004: "Port Based Network Access Control". [8] IETF RFC 2865: "Remote Authentication Dial In User Service (RADIUS)". [9] DSL Forum TR69. ETSI ETSI TS 183 019 V2.3.0 (2008-02) 6 [10] IETF RFC 2131: "Dynamic Host Configuration Protocol". [11] IETF RFC 2132: "DHCP Options and BOOTP Vendor Extensions". [12] IETF RFC 3004: "The User Class Option for DHCP". [13] IETF RFC 3825: "Dynamic Host Configuration Protocol Option for Coordinate-based Location Configuration Information". [14] IETF RFC 3046: "DHCP Relay Agent Information Option". [15] IETF RFC 3993: "Subscriber-ID Suboption for the Dynamic Host Configuration Protocol (DHCP) Relay Agent Option". [16] IETF RFC 3361: "Dynamic Host Configuration Protocol (DHCP-for-IPv4) Option for Session Initiation Protocol (SIP) Servers". [17] IETF RFC 3315: "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)". [18] IETF RFC 3319: "Dynamic Host Configuration Protocol (DHCPv6) Options for Session Initiation Protocol (SIP) Servers". [19] IETF RFC 3646: "DNS Configuration options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)". [20] IETF RFC 4669: "DHCPv6 Relay Agent Remote ID Option". [21] IETF RFC 4580: "DHCPv6 Relay Agent Subscriber-ID Option". [22] IETF RFC 2516: "A method for transmitting PPP over Ethernet (PPPoE)". [23] Void. [24] IETF RFC 3580: "IEEE 802.1X Remote Authentication Dial In User Service (RADIUS Usage Guidelines". [25] ETSI ES 282 004: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Functional Architecture; Network Attachment Sub-System (NASS)". [26] IETF RFC 4776: "Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Option for Civic Addresses Configuration Information". [27] IETF RFC 3925: "Vendor-Identifying Vendor Options for Dynamic Host Configuration Protocol version 4 (DHCPv4)". [28] IETF RFC 3588 : "Diameter Base Protocol". [29] IETF RFC 4072 : "Diameter Extensible Authentication Protocol (EAP) Application". [30] IETF RFC 3579 : "RADIUS (Remote Authentication Dial In User Service) Support For Extensible Authentication Protocol (EAP)". ETSI ETSI TS 183 019 V2.3.0 (2008-02) 7 |
e142e055458ad4dd142e50ecfb0407b8 | 183 019 | 3 Definitions and abbreviations | |
e142e055458ad4dd142e50ecfb0407b8 | 183 019 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: Access Network (AN): collection of network entities and interfaces that provide the IP transport connectivity between end user devices and NGN entities Core Network (CN): portion of the delivery system composed of networks, systems equipment and infrastructures, connecting the service providers to the access network Functional Entity (FE): entity that comprises a specific set of functions at a given location NOTE: Functional entities are logical concepts, grouping of functional entities are used to describe practical physical realizations. home NGN network: NGN network through which the User Equipment gains network connectivity NOTE: The NGN network includes both the Access Network and the Core Network. The User Equipment has a service relationship with the business entity that operates this network. User Equipment (UE): one or more devices allowing a user to access services delivered by TISPAN NGN networks NOTE: This includes devices under user control commonly referred to as CPE, IAD, ATA, RGW, TE, etc., but not network controlled entities such as access gateways. visited NGN network: NGN network through which the User Equipment gains network connectivity NOTE: The NGN Network includes both the Access Network and the Core Network. The User Equipment does not have a service relationship with the business entity that operates this network. |
e142e055458ad4dd142e50ecfb0407b8 | 183 019 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: 3GPP Third Generation Project Partnership AAA Authentication, Authorization and Accounting AC Access Controller AMF Access Management Function AN Access Network AP Access Point ARF Access Relay Function ATA Analog Terminal Adaptor CHADDR Client Hardware ADDRess CLF Connectivity session Location and repository Function CNG Customer Network Gateway CNGCF CNG Configuration Function DHCP Dynamic Host Configuration Protocol DSLAM Digital Subscriber Line Access Multiplexer EAP Extensible Authentication Protocol EAPOL EAP Over LAN FTTx Fibre To The (x = Cab Cabinet, x = C Curb, x = B Building, x = H Home) GPON Gigabit Passive Optical Network GSMA Global System for Mobile communications Association IAD Integrated Access Device IANA Internet Assigned Numbers Authority IETF Internet Engineering Task Force IP Internet Protocol LAN Local Area Network ETSI ETSI TS 183 019 V2.3.0 (2008-02) 8 MAC Media Access Control MSAN Multi services Access Node NACF Network Access Configuration Function NAI Network Access Identifier NASS Network Attachment SubSystem NGN Next Generation Network OLT Optical Line Termination PADIP PPPoE Active Discovery Initiation PADO PPPoE Active Discovery Offer PADR PPPoE Active Discovery Request PADS PPPoE Active Discovery Session-confirmation PADT PPPoE Active Discovery Terminate PDBF Profile Data Base Function PEAP Protected EAP PPP Point to Point Protocol PPPoE PPP over Ethernet RADIUS Remote Authentication Dial In User Service RGW Residential GateWay SIM Subscriber Identity Module TE Terminal Equipment TLS Transport Layer Security TTLS Tunnelled Transport Layer Security UAAF User Access Authorization Function UAM Universal Access Method UE User Equipment WLAN Wireless Local Area Network xDSL Digital Subscriber Line |
e142e055458ad4dd142e50ecfb0407b8 | 183 019 | 4 NGN general architecture | ES 282 001 [1] provides a description of the general network architecture of the NGN. The model is depicted in figure 1. UE Visited NGN network Home NGN network e1 e5 Figure 1: General NGN network model Interface e1 is a user-network interface supporting attachment of user equipment to a network. The present document provides a description of the procedures applicable to this interface that is essentially independent from the layer 1 access technology being used. Interface e5 is a roaming interface, and is independent of the access technology. Interface e5 is used to provide a consistent method for the visited NGN network to communicate with the home NGN network. Figure 2 depicts the functional composition of the access network and the NGN core for the roaming scenario, where a UE obtains network access via a visited NGN network and authenticates back with the home NGN network. Details of this model may be found in TS 124 234 [2]. ETSI ETSI TS 183 019 V2.3.0 (2008-02) 9 Home NGN Access Network UAAF Visited NGN Access Network PDBF CPE (CNG/TE) e5 ARF a4 Service control subsystems a3 a1 a2 e1 e2 e4 e3 Resource and Admission Control Subsystem CLF NACF CNGCF AMF UAAF Home NGN Access Network UAAF Visited NGN Access Network PDBF UE e5 ARF Visited NGN network Home NGN network Access Transport network e1 Figure 2: NASS mapped onto functional network roles - roaming scenario |
e142e055458ad4dd142e50ecfb0407b8 | 183 019 | 4.1 Overview of interface e1 | The present document details the protocols and profiles for e1 - the interface for authentication, authorization and IP address allocation. This interface enables the UE to initiate authentication and authorization requests, as well as initiate requests for IP address allocation, DNS allocation, and other network configuration parameters in order to access the network. These requests are received by the AMF (Access Management Function). It is assumed that the IP edge in the transport plane includes an ARF (Access Relay Function), which communicates with the UAAF (User Access Authorization Function) and NACF (Network Access Configuration Function) via the AMF. This interface enables the user equipment to provide user credentials (username/password, token, certificates, etc.) to the Network Attachment Subsystem (NASS) [25] in order to perform network access authentication and authorization. This interface may also enable the NASS to provide authentication parameter to the UE to perform the network authentication when mutual authentication procedure is required. Based on the result of the authentication, the AMF authorizes or denies the network access to the user equipment. |
e142e055458ad4dd142e50ecfb0407b8 | 183 019 | 4.1.1 Authentication | This interface specifies the protocols and profiles used for authentication of the UE to the network, and vice-versa. The credentials used for authentication depend on the authentication method used as well as the preferences of the network service provider. Possible credential types include, SIM, certificates and username/password. |
e142e055458ad4dd142e50ecfb0407b8 | 183 019 | 4.1.2 IP address and network configuration | Once the UE is authenticated successfully, it shall be able to obtain an IP address in order to access the different services offered by the service provider. This interface also provides a method to transport IP address and network configuration information to the UE to enable IP access. ETSI ETSI TS 183 019 V2.3.0 (2008-02) 10 |
e142e055458ad4dd142e50ecfb0407b8 | 183 019 | 5 PPP-based access network configuration | |
e142e055458ad4dd142e50ecfb0407b8 | 183 019 | 5.1 Authentication phase | 5.1.1 PPP link establishment phase (LCP) with authentication (PAP/CHAP/EAP) A generic description of the PPP-based authentication model is provided in TS 124 234 [2], clause 7.2 and annex B. There are currently no specific requirements on PPP-based authentication scenarios. This may be further studied and defined in future releases of the TISPAN specifications. |
e142e055458ad4dd142e50ecfb0407b8 | 183 019 | 5.2 Network Configuration Phase (NCP) | |
e142e055458ad4dd142e50ecfb0407b8 | 183 019 | 5.2.1 PPP Network Configuration Phase for IP Networks (NCP/IPCP) | |
e142e055458ad4dd142e50ecfb0407b8 | 183 019 | 5.2.1.1 PPP and ARF | The Access Relay Function (ARF) acts as a relay between the user equipment and the NASS. It receives network access requests from the user equipment and forwards them to the NASS. Before forwarding a request, the ARF may also insert local configuration information and apply protocol conversion procedures. In PPPoE case, the ARF should implement a PPPoE intermediate agent function in order to insert access loop identification. As a PPPoE Intermediate, the ARF intercepts all PPPoE discovery packets, i.e. the PADI, PADO, PADR, PADS and PADT packets, but does not modify the source or destination MAC address of these PPPoE discovery packets. Upon reception of a PADI or PADR packet sent by the PPPoE client, the ARF adds a PPPoE TAG to the packet sent upstream. The TAG contains the identification of the access loop on which the PADI or PADR packet was received in the Access Node where the ARF resides. If a PADI or PADR packet exceeds 1 500 octets after adding the TAG containing the access loop identification, the ARF must not send the packet to the AMF. The ARF should then return a Generic-Error TAG to the sender in the appropriate PPPoE discovery packet (i.e. PADO or PADS). The required syntax for access loop identification is depicted in following table defined in RFC 2516 [22]. +--------------+--------------+--------------+--------------+ | 0x0105 (Vendor-Specific) | TAG_LENGTH | +--------------+--------------+--------------+--------------+ | 0x00000DE9 (3561 decimal, i.e. "ADSL Forum" IANA entry) | +--------------+--------------+--------------+--------------+ | 0x01 | length | Agent Circuit ID value... | +--------------+--------------+--------------+--------------+ | Agent Circuit ID value (cont) | +--------------+--------------+--------------+--------------+ | 0x02 | length | Agent Remote ID value... | +--------------+--------------+--------------+--------------+ | Agent Remote ID value (cont) | +--------------+--------------+--------------+--------------+ ETSI ETSI TS 183 019 V2.3.0 (2008-02) 11 The first four octets of the TAG_VALUE contain the vendor id. Specifically, the enterprise code here is that of the DSL Forum, (i.e. 3561 in decimal, corresponding to the IANA "ADSL Forum" entry in the Private Enterprise Numbers registry). The remainder of the TAG_VALUE is unspecified in RFC 2516 [22]. Note that the sub-options do not have to be aligned on a 32-bit boundary. "Agent Circuit ID" sub-option (sub-option 1). This sub-option uniquely identify the Access Node and the access loop on the Access Node on which the PPPoE discovery packet was received. "Agent Remote ID" sub-option (sub-option 2). The sub-option contains a string that uniquely identifies the subscriber on the associated access loop on the Access Node on which the PPPoE discovery packet was received. For encoding the sub-option, the same sub-option based encoding as in DHCP option 82 is used (see clause 7.1.2). |
e142e055458ad4dd142e50ecfb0407b8 | 183 019 | 5.2.1.2 PPP and AMF | The Access Management Function (AMF) translates network access requests issued by the UE. It forwards the requests for allocation of an IP address and possibly additional network configuration parameters to/from the NACF. In case PPP is applied, the AMF terminates the PPP connection and provides the inter-working with the interface to the network attachment subsystem e.g. using an AAA protocol (RADIUS or Diameter). The AMF acts as a RADIUS client if the UAAF is implemented in a RADIUS server. When ARF implements a PPPoE Intermediate Agent and adds access loop identification TAG. The AMF should be able to support access loop identification carried over PPPoE. The AMF shall accept PADI and PADR packets containing a TAG that is used to convey the access loop identification to AMF. The access loop information present in a TAG in the PADI and PADR packets may be used by the AMF to check whether PPPoE discovery is allowed for the identified subscriber line. This procedure is independent of the PPP authentication phase performed later on. The AMF shall be able to use the access loop identification to construct the proper RADIUS Attributes (e.g. NAS-Port-Id, NAS-Port or Calling-Station-Id) during the PPP authentication phase. These Attributes are sent in a RADIUS Access-Request packet to the UAAF which is a RADIUS server. This allows the UAAF to take the access loop identification into account when performing authentication, authorization and accounting. The AMF shall not send the TAG used to convey the access loop identification in PADO, PADS and downstream PADT messages. The AMF shall be transparent to the DHCP messages on the PPP connection. |
e142e055458ad4dd142e50ecfb0407b8 | 183 019 | 6 Ethernet-based access network configuration | |
e142e055458ad4dd142e50ecfb0407b8 | 183 019 | 6.1 Authentication phase | |
e142e055458ad4dd142e50ecfb0407b8 | 183 019 | 6.1.1 EAP over Ethernet (802.1X) | |
e142e055458ad4dd142e50ecfb0407b8 | 183 019 | 6.1.1.1 General | The 802.1X IEEE standard [7] describes a protocol to exchange authentication information over IEEE 802 networks. This protocol is called EAP over LAN (EAPOL) and aims to carry EAP messages over the access transport network. ETSI ETSI TS 183 019 V2.3.0 (2008-02) 12 802.1X defines three functions involved in the authentication and authorization process: • The Supplicant is a function located in the device that wants to join the network through the access node and needs to be authenticated. It provides authentication credentials. • The Authenticator is a function located on the access node in charge of network access control. • The Authentication Server, which may be co-located or not with the authenticator, provides authentication and authorization decisions. The mapping between the above functions and the TISPAN NGN functional architecture is as follows: The supplicant is a function of the UE. The authenticator is a function of the AMF. The authentication server is a function of the UAAF. As shown in figure 3, the EAP messages are carried over EAPOL between the Supplicant and the Authenticator and then reencapsulated in AAA protocol (RADIUS [8] [24] [30] or Diameter [28] [29]) messages to be sent from the Authenticator to the Authentication Server (through zero or more Authentication proxies). Figure 3: 802.1X functional entities Figure 3bis shows the EAP authentication protocol stack. Figure 3bis: EAP authentication protocol stack EAPoL (EAP over Lan) RADIUS or Diameter EAP 802 (802.11, 802.3/IP etc.) Inner EAP Methods (MD5, PEAP, TLS, TTLS etc.) Supplicant Authenticator Authentication Server (e1) EAP over LAN (a3) EAP over AAA EAP UE AMF/ARF UAAF ETSI ETSI TS 183 019 V2.3.0 (2008-02) 13 Figure 4 depicts a typical 802.1X-based authentication scenario. Figure 4: 802.1X-based authentication with RADIUS as AAA protocol Once the 802 layer is established, the Supplicant (located in the UE) initiates the authentication by sending an EAPOL-Start frame. The Authenticator receiving this message responds by sending an EAP-Request querying the identity of the Supplicant. If the Supplicant supports the authentication mechanism, it sends an EAP-Response message containing its identity. NOTE: There are usually two parts to this identity: the user name and the realm. Typically, these are combined into a Network Access Identifier (NAI) of the form user@realm. The realm part of the NAI is used to establish a connection with the appropriate AAA-H for that user. This presumes that the visited network recognizes that realm name. If this is not the case, then the visited network will signal an authentication failure back to the UE. It can then either try a different NAI (with a different realm) or can try to establish a new NAI on the visited network. If those alternatives also fail, the UE will be denied access or will be granted only limited guest access. The Authenticator extracts this EAP message from the EAPOL PDU, encapsulates it inside a RADIUS Access-Request (as defined in [27]) and sends it to the Authentication Server. Then EAP messages are exchanged between the Supplicant and the Authentication Server. During this exchange, the method of authentication is set and if the Supplicant supports it, it provides information proving its identity. At the end of that EAP exchange the authentication may succeed or fail. The result is signalled either by an EAP-Success or EAP-Failure message sent by the Authentication server. Supplicant Authenticator Authentication server (AAA-H) Authentication proxy (AAA-V) UE ARF / AMF UAAF EAPOL START UAAF EAP - Request / Identity EAP - Response / Identity RADIUS- Access- Request : EAP - Response / Identity RADIUS- Access- Challenge : EAP - Request Challenge - EAP - Request Challenge EAP - Response Challenge RADIUS -Access - Request : EAP - Response Challenge RADIUS- Access- Accept : EAP - Success EAP- Success ETSI ETSI TS 183 019 V2.3.0 (2008-02) 14 To avoid revealing the true user identity to an entity other than the home service provider, the UE can use a generic user name like "anonymous" or "user" in the NAI given in the initial identity exchange. The realm part of the NAI is the only information the visited network needs to know at this point. If PEAP or TTLS are used to establish a secure tunnel between the UE and the AAA server in the home network, then the protected identity exchange will not be visible to the visited network or to any eavesdroppers. The visited network will eventually need to obtain some identity value for charging and billing purposes if the authentication is successful. The home network can provide the identity that identifies the account for charging. This account is used between the visited network and the home network for inter-operator charging purposes only. This account need not be the same as that used by the home network to bill the subscriber. Furthermore, this identity can be an alias specified by the home provider rather than information that might compromise the true identity of the wireless user. The identity used for charging can be shared only with the AAA infrastructure and never needs to be sent unprotected across the accesslink. |
e142e055458ad4dd142e50ecfb0407b8 | 183 019 | 6.1.1.2 802.1X and ARF | The Access Relay Function (ARF) acts as a relay between the user equipment (UE) and the AMF. In the 802.1X case the ARF is always co-located with the AMF. The ARF is in charge of providing access loop identification information and transfer it to the AMF. |
e142e055458ad4dd142e50ecfb0407b8 | 183 019 | 6.1.1.3 802.1X and AMF | In the 802.1X case, the Access Management Function (AMF) incorporates the authenticator function. It shall be implemented one L2 hop far from the Supplicant implemented in the UE. The AMF constructs a proper AAA message sent to the UAAF with the following elements: The access loop identification information provided by the ARF. The EAP message encapsulated inside the EAPOL frame. No modification is applied to the EAP elements by the AMF. Then, the EAP exchange takes place end to end between the UE as Supplicant and the UAAF as Authentication Server, through the Authenticator. |
e142e055458ad4dd142e50ecfb0407b8 | 183 019 | 6.1.2 802.1X-based xDSL/FTTx (wireline) access network | This clause provides further details on the use of 802.1x when the access network uses xDSL or FFTx technology. Authentication process and protocol exchanges between the different entities are compliant with the description provided in clause 6.1.1. The xDSL/FTTx (wireline) access network will physically consist of at least one Access Node (DSLAM, MSAN, OLT for GPON, etc.) which provides the UE with access to aggregation network resources. The UE acts as the 802.1X supplicant, the Access Node acts as the 802.1X authenticator, and the AAA server (which implements the UAAF functionality) acts as the authentication server. When the UE comprises a customer network gateway (CNG) and associated customer network devices, the 802.1X Supplicant function must be located on the CNG. This is a direct consequence of 802.1x specifications which set a limitation of a single L2 hop between the supplicant and the 802.1x authenticator. NOTE: As a consequence of the above limitation, specific users identified at the level of a terminal device connected to a CNG cannot be authenticated by the NASS. ETSI ETSI TS 183 019 V2.3.0 (2008-02) 15 A generic model for xDSL/FTTx 802.1x access to NGN networks is depicted in figure 4bis. Figure 4bis: Generic Model for wireline access (xDSL, FTTH, etc.) |
e142e055458ad4dd142e50ecfb0407b8 | 183 019 | 6.1.3 802.1X-based WLAN access network functional architecture | The WLAN Access Network will physically consist of at least one Access Point (AP), which will provide the radio connectivity for the WLAN UE devices. The Access Network or the core network may also contain an Access Controller (AC), that may manage a number of APs. For the WLAN scenario, the UE (mobile station) acts as the 802.1X supplicant, the AP acts as the 802.1X authenticator, and the AAA server (which implements the UAAF functionality) acts as the authentication server. A generic model for access of WLAN to NGN networks is depicted in figure 5. Figure 5: Generic model for WLAN access to NGN The numbers shown in figure 5 correspond to the following steps of a typical 802.1X-based authentication scenario: 1) The wireless station (UE) discovers an 802.11 Access Point (AP) and initiates a connection request. The AP (or a network authenticator) responds with a request for the UE identity. 2) The AP in the access network forwards the UE identity as an authentication request message to the local authentication server/proxy (AAA-Proxy) that implements the UAAF functionality. This may be forwarded via an Access Controller (AC). Either the AP, or the AC, or a combination of the two could implement the AMF functionality. 3) If the AAA-Proxy is able to authenticate the user credentials, it does so locally. If the AAA-Proxy examines the wireless station identity and decides that this is a roaming user, it forwards the authentication request on to the AAA server of the home provider of that user (AAA-Server) based on the realm name specified in the wireless station identity. ETSI ETSI TS 183 019 V2.3.0 (2008-02) 16 4) The AAA-Server (which also implements the UAAF functionality) authenticates the user via an EAP-based challenge-response method that runs end-to-end between the AAA-Server and the wireless station. A local user database (PDBF) is consulted by AAA-Server to verify the credentials provided by the wireless station. The result of the authentication and session key material are communicated back to the AAA-V and AP respectively. 5) The AP configures link-layer session keys and signals that the wireless station has been successfully authenticated. Prior to this time, the AP blocks any attempt by the wireless station to obtain an address or access the Internet. 6) The AP, through the AAA-Proxy, sends accounting messages to the AAA-Server. When the wireless station disconnects, an accounting stop message is sent as the last message for that session. The AAA-V and AAA-H generate charging records. The AAA-H sends these record to a billing center. |
e142e055458ad4dd142e50ecfb0407b8 | 183 019 | 6.2 Network configuration phase | |
e142e055458ad4dd142e50ecfb0407b8 | 183 019 | 6.2.1 DHCP procedures | The Network Access Configuration Function (NACF) is responsible for the IP address allocation to the UE. It may also distribute other network configuration parameters such as address of DNS server(s) and address of signalling proxies for specific protocols. A NACF may be realized as a DHCP server. Once the UE has been authenticated as described above, it may use DHCP to request an IP address. A local DHCP server that functions as a NACF may respond to this request and assign an IP address with a local subnet prefix to the UE. It maintains a mapping between the UE and the IP address that has been assigned to it, and may forward this information to the CLF. Further specifications are provided in clause 7. |
e142e055458ad4dd142e50ecfb0407b8 | 183 019 | 7 DHCP Support for Interface e1 | |
e142e055458ad4dd142e50ecfb0407b8 | 183 019 | 7.1 Access Network based on IPv4 | |
e142e055458ad4dd142e50ecfb0407b8 | 183 019 | 7.1.1 DHCP support by the UE | The User Equipment (UE) shall behave as an RFC 2131 [10] compliant DHCP v4 client. The UE shall be able to send DHCP messages that support the following options: Option 50 "Requested IP@" RFC 2132 [11], RFC 2131 [10]. Option 55 "Parameter List" RFC 2132 [11]. Option 60 "Vendor Class Identifier" RFC 2132 [11]. Option 61 "Client Identifier" RFC 2132 [11]. In case the DSL Forum TR69 [9] is used to manage remotely a UE, the UE shall insert its own identity in the following option: Option 125 "Vendor Specific information" RFC 3925 [27]. Option 55 shall be set to request the following options: 6, 43, 66, 67, 120 and 123. If option 120 is received from the NACF, its value shall take precedence over any locally configured information and over any information that may be received from the CNGCF to identify outbound SIP proxies. If option 120 is not received from the NACF, the UE shall use information received from the CNGCF (if any) or locally configured information. A UE supporting the autoconfiguration protocol defined by the DSL forum shall identity itself by including the string "dslforum.org" anywhere in the Vendor Class Identifier option (60). This will ensure that the name of the ACS will be sent back in the DHCP offer in the Vendor Specific Information option (43), as described in DSL Forum TR69 [9]. ETSI ETSI TS 183 019 V2.3.0 (2008-02) 17 It is also recommended that the UE send the following options: Option 0 "Padding" RFC 2132 [11]. Option 12 "Host Name" RFC 2132 [11]. Option 53 "DHCP message type" RFC 2132 [11]. Option 77 "User Class" RFC 3004 [12]. The UE shall be able to receive and process DHCP messages that include the following options: Option 6 "Domain Server" RFC 2132 [11]. Option 15 "Domain Name" RFC 2132 [11]. Option 43 "Vendor Specific" RFC 2132 [11]. Option 51 "IP Address Lease Time" RFC 2132 [11]. Option 58 "Timer T1" RFC 2132 [11]. Option 59 "Timer T2" RFC 2132 [11]. Option 120 "SIP Servers DHCP Option" RFC 3361 [16] Support of the following options is also recommended: Option 0 "Padding" RFC 2132 [11]. Option 1 "Subnet Mask" RFC 2132 [11]. Option 3 "Router" RFC 2132 [11]. Option 5 "Name Server" RFC 2132 [11]. Option 33 "Static Route" RFC 2132 [11]. Option 42 "NTP servers" RFC 2132 [11]. Option 53 "DHCP message type" RFC 2132 [11] Option 66 "TFTP Server Name" RFC 2132 [11]. Option 67 "Bootfile-Name" RFC 2132 [11]. Option 72 "WWW Server" Option 123 "GeoConf Option" RFC 3825 [13]. Option 114 "URL option" Option 136 "PANA Authentication Agent" Option 99 "Civic Location" RFC 4776 [26]. |
e142e055458ad4dd142e50ecfb0407b8 | 183 019 | 7.1.2 DHCP support by the ARF | The Access Relay Function (ARF) shall behave as an RFC 2131 [10] compliant DHCP v4 Relay Agent. It shall support the DHCP Relay Agent Information option (Option 82) and insert the following sub-options: Sub-option 1 "Agent Circuit ID" RFC 3046 [14]. Sub-option 2 "Agent Remote ID" RFC 3046 [14]. Sub-option 6 "Subscriber-ID" RFC 3993 [15]. ETSI ETSI TS 183 019 V2.3.0 (2008-02) 18 The following encoding is recommended for the Agent Circuit ID: AgentCircuit-ID = AccessNodeId AggregationType slot/port ":" Layer2Id AccessNodeId = NAME AggregationType = "atm" | "eth" Slot = *DIGIT Port = *DIGIT Layer2Id = ATM_Id | Ethernet_Id ATM_Id = vpi "." vci Ethernet_Id = vlan_tag vpi = *DIGIT ; VP Identifier vci = *DIGIT ; VC Identifier vlan_tag = DIGIT ; VLAN tag DIGIT = %x30-39 ; 0-9 ALPHA = %x41-5A / %x61-7A ; A-Z / a-z NAME = ALPHA *63(ALPHA / DIGIT / "_") The Agent Remote ID shall be in the form of an ASCII string that identifies the subscriber line with regards to the Network Attachment Subsystem. The Subscriber ID shall be in the form of an ASCII string that identifies the subscriber with regards to the Network Attachment Subsystem, independently from the access technology used. When receiving the first message from a MAC address, the ARF shall associate this MAC address with the subscriber-dedicated transport resource (i.e. "user circuit") from which the message was received. The ARF shall associate the IP address assigned by the NACF with the subscriber-dedicated transport resource to which it was forwarded. This association shall be stored in the physical entity hosting the ARF so as to enable this entity to implement antispoofing of IP addresses and prevent forwarding inside the NGN any IP packet those source IP address differs from that associated with the transport resource. In case the subscriber-dedicated transport resource is not terminated on this entity, the ARF shall check consistency between the source MAC@ and the "chaddr" field of the DHCP payload and perform antispoofing based on the association between the IP address and the MAC@. This assumes that the aging time shall be greater than the DHCP Lease Time and that MAC addresses shall not be allowed to move from one "user circuit" to another before the aging time expires. |
e142e055458ad4dd142e50ecfb0407b8 | 183 019 | 7.1.3 DHCP support by the NACF | The Network Access Configuration Function (NACF) shall behave as an RFC 2131 [10] compliant DHCP v4 server. The NACF shall support all options defined in RFC 2132 [11] and RFC 3004 [12], RFC 3046 [14], RFC 3361 [16], RFC 3825 [13] and RFC 3993 [15]. The NACF shall insert the following options in a DHCP Offer: Option 6 "Domain Server": The domain name server option specifies a list of Domain Name System name servers available to the client. Option 15 "Domain Name": specifies the domain name that client should use when resolving hostnames via the Domain Name System. Option 51 "IP Address Lease Time": It is recommended that a long lease time be used. Option 58 "Timer T1": This timer should be set to a value that is less than the default value described in RCF 2131. Option 59 "Timer T2": This timer should be set to a value that is less than the default value described in RCF 2131. Option 50 "Requested IP@" RFC 2132 [11] , RFC 2131 [10]. Option 120 "SIP Server": This option shall contain the P-CSCF identity. The SIP server DHCP option carries either a 32-bit (binary) IPv4 address or, preferably, a DNS name to be used by the SIP client to locate a SIP server. In case the DSL Forum TR69 [9] is used to manage remotely a UE, the NACF shall support the following option, used by the UE to insert its own identity: ETSI ETSI TS 183 019 V2.3.0 (2008-02) 19 Option 125 "Vendor Specific information" RFC 3925 [27]. The NACF shall answer to a DHCPINFORM message, in compliance with RFC 2131 [10] (i.e. receiving the option 120 shall answer providing the P-CSCF identity). The NACF may use any of the following criteria for allocating a SIP outbound proxy to a UE and populating DHCP option 120: Load / processing capacity of the SIP Proxies (i.e. P-CSCF instances in the IMS case). The network address allocated to the UE. The subnet from which the DHCP message was received (if "giaddr" is 0) or the address of the relay agent that forwarded the message ("giaddr" when not 0). Hardware address of the UE as in the chaddr field of the received DHCP message. Contents of the "Hostname" option of the received DHCP message. Contents of the "Client Identifier" option of the received DHCP message. The NACF may also insert the following options in a DHCP Offer: Option 42 "Network Time Protocol Servers". Option 43 "Vendor Specific": Vendor Specific Information option used by clients and servers to exchange vendor- specific information. If a vendor potentially may encode more than one item of information using "Encapsulated vendor-specific options" (e.g. name of the CNGCF). NOTE: If the CNGCF is an autoconfiguration server (ACS) as defined in TR69, the DHCP server includes the two encapsulated Vendor-Specific options (URL of ACS, Provisioning Code) defined in TR69. Option 66 "TFTP Server Name": TFTP server address. Option 67 "Bootfile Name": Identifies a bootfile to be retrieved by the user equipment. Option 72 "WWW server": The WWW server option specifies a list of WWW available to the client. Option 123 "GeoConf Option": Coordinate-based Location Configuration Information option provides the coordinate-based geographic location of the client. Option 114 "URL option" : May be used for authentication. Option 136 "PANA Authentication Agent" the PANA Authentication Agent Option carries either a 32-bit (binary) IPv4 address list or, preferably, a domain name list to be used by the PANA client to locate a PANA authentication Agent. Option 99 "Civic Location": Dynamic Host Configuration Protocol option containing the civic location of the client or the DHCP server. The NACF shall check consistency of DHCP payloads based on the contents of Option 82 and of the CHADDR field. 7.1.4 DHCP support by the AMF The AMF shall be able to relay all DHCP messages received from the UE to the NACF and vice-versa. |
e142e055458ad4dd142e50ecfb0407b8 | 183 019 | 7.2 Access network based on IPv6 | The UE, the ARF and the NACF shall behave as an RFC 3315 [17] compliant DHCPv6 client, DHCPv6 relay agent and DHCP Server (respectively). All options defined in RFC 3315 [17] shall be supported. The following options shall also be supported: DHCPv6 options 21 and 22 for SIP server. ETSI ETSI TS 183 019 V2.3.0 (2008-02) 20 OPTION_SIP_SERVER_D (21) defined in RFC 3319 [18]. OPTION_SIP_SERVER_A (21) defined in RFC 3319 [18]. OPTION_DNS_SERVERS (23) defined in RFC 3646 [19]. The ARF shall insert the following information: OPTION_REMOTE_ID (37) defined in RFC4649 [20]. OPTION_SUBSCRIBER_ID (38) defined in RFC 4580 [21]. |
e142e055458ad4dd142e50ecfb0407b8 | 183 019 | 8 Applicability to WLAN access networks | This certification of WLAN devices by the Wi-Fi Alliance [3] may only be applicable to WLAN devices that are deployed by a service provider, and may not be necessary or enforceable for devices that may be deployed in the customer premises - for example, a wireless AP that is connected to a DSL line coming in to a home. |
e142e055458ad4dd142e50ecfb0407b8 | 183 019 | 8.1 Requirements of the WLAN access network | 1) The WLAN device in the WLAN access network shall be Wi-Fi Alliance [3] certified and: a) The WLAN device shall support either 802.11b or 802.11g. 2) The access network shall support WPA/802.1X. a) The SSID used for WPA/802.1X in the beacon shall be broadcast by the WLAN device in strict accordance with the 802.11 specification. The beacon shall contain the WPA Information Element. b) The access network shall support EAPOL messages, and shall be able to transport at a minimum EAP messages of the EAP method types defined in clause 8.2. c) The access network shall provide a DHCP service, with assignment of wireless station IP address, netmask, gateway IP address and DNS server address. Specific requirements are described in clause 7 of the present document. d) The access network shall support login with username (NAI) as defined in RFC 4282 [6]. 3) The access network may support WPA2. 4) The access network may also support UAM. In this case, the access network shall meet the following requirements simultaneously. a) The SSID used for WPA in the beacon shall be broadcast by the WLAN device in strict accordance with the 802.11 specification. The beacon shall contain the WPA Information Element. b) The SSID used for open authentication in the beacon shall be broadcast by the AP in strict accordance with the 802.11 specification. The beacon shall indicate open authentication by not requiring WEP or 802.1X. 5) If the access network supports UAM method of authentication, it shall also meet the following requirements: a) It may provide a DHCP service, with assignment of wireless station IP address, netmask, gateway IP address and DNS server address. b) It may support redirection of HTTP requests to a login webpage while in unauthenticated mode. c) It shall support login with username (NAI) as defined in RFC 4282 [6]. d) It shall secure authentication of credentials over HTTPS. 6) The access network may support intermediary network discovery and selection to allow a wireless station to select an intermediary when in a visited network. ETSI ETSI TS 183 019 V2.3.0 (2008-02) 21 a) If a user's service provider does not have a service agreement with a visited network provider, it may still be possible to obtain service via a roaming intermediary or exchange. If more than one intermediary is available, the choice of intermediary may affect charges, service, QoS, and other issues. In this case, it is important for the user to have an opportunity to influence that choice. b) Work in this area is being done in the IETF. Work items that should be tracked include the NAI format standard defined by RFC 4282 [6], and the EAP Network Discovery proposal in RFC 4284 [4]). |
e142e055458ad4dd142e50ecfb0407b8 | 183 019 | 8.2 Requirements of the chosen EAP method | 1) The EAP method used shall support: a) Mutual authentication. b) Key-derivation. 2) TS 124 234 [2], clause 6, shall be supported when EAP-SIM and EAP-AKA are used by the WLAN UE and the WLAN access network. NOTE: Requirement 1 of clause 6.5 is satisfied by the following EAP methods. It should be noted that the list below is not restrictive. EAP-SIM. PEAP/EAP-MSCHAPv2. TTLS/MS-CHAPv2. EAP-AKA. EAP-TLS. ETSI ETSI TS 183 019 V2.3.0 (2008-02) 22 Annex A (informative): Requirements of the WLAN station A.1 Requirements of the WLAN station 1) The wireless interface on the WLAN station shall be Wi-Fi Alliance [3] certified, and: a) The WLAN station shall support either 802.11b or 802.11g. 2) The WLAN station shall be able to operate in Wi-Fi Protected Access (WPA)/802.1X mode and: b) WLAN authentication signalling shall be based on Extensible Authentication Protocol (EAP) as specified in RFC 3748 [5]. The EAP method chosen shall follow the EAP method requirements noted in clause 8.2. c) The wireless station shall use an NAI as defined in RFC 4282 [6] and TS 124 234 [2]. 3) The wireless station may operate in UAM mode. d) The wireless station shall be able to successfully associate to the open SSID and be 802.11 authenticated (as per 802.11-1999 specification). 4) The wireless station shall be able to differentiate between multiple BSSID capability information elements, which have the same SSID name. 5) The wireless station may operate in WPA2 mode. 6) The wireless station may support intermediary network discovery and selection to allow a wireless station to select an intermediary when in a visited network. e) If a user's service provider does not have a service agreement with a visited network provider, it may still be possible to obtain service via a roaming intermediary or exchange. If more than one intermediary is available, the choice of intermediary may affect charges, service, QoS, and other issues. In this case, it is important for the user to have an opportunity to influence that choice. f) Work in this area is being done in the IETF. Work items that should be tracked include the NAI format standard defined by RFC 4282 [6], and the EAP Network Discovery proposal in RFC 4284 [4]). ETSI ETSI TS 183 019 V2.3.0 (2008-02) 23 Annex B (informative): Bibliography IETF RFC 3162: "RADIUS and IPv6". ETSI ETSI TS 183 019 V2.3.0 (2008-02) 24 History Document history V2.3.0 February 2008 Publication |
6e795bd50d66978f3253adc5068d22be | 183 031 | 1 Scope | The present document provides the necessary extensions and modifications to 3GPP TS 29.333 [1] required for use in a TISPAN NGN. 3GPP TS 29.333 [1] describes the protocol to be used on the Multimedia Resource Function Controller (MRFC) - Multimedia Resource Function Processor (MRFP) interface (Mp interface). This specification defines a profile of the Gateway Control Protocol (H.248.1), for controlling Multimedia Resource Function Processor supporting in-band user interaction, conferencing and transcoding for multimedia-services. |
6e795bd50d66978f3253adc5068d22be | 183 031 | 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. |
6e795bd50d66978f3253adc5068d22be | 183 031 | 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] 3GPP TS 29.333: "Multimedia Resource Function Controller (MRFC) - Multimedia Resource Function Processor (MRFP) Mp Interface - Stage 3; (Release 7)". [2] ITU-T Recommendation H.imp 248: "Implementors' Guide for the H.248 Sub-series of Recommendations ("Media Gateway Control Protocol")". [3] IETF RFC 2833: "RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals". [4] IETF RFC 3551: "RTP Profile for Audio and Video Conferences with Minimal Control". [5] IETF RFC 3555: "MIME Type Registration of RTP Payload Formats". [6] IETF RFC 3389: "Real-time Transport Protocol (RTP) Payload for Comfort Noise (CN)". [7] ITU-T Recommendation G.711: "Pulse code modulation (PCM) of voice frequencies". ETSI ETSI TS 183 031 V2.0.0 (2008-02) 6 [8] ITU-T Recommendation G.711 Appendix I: "A high quality low-complexity algorithm for packet loss concealment with G.711". [9] ITU-T Recommendation G.711 Appendix II: "A comfort noise payload definition for ITU-T G.711 use in packet-based multimedia communication systems". [10] ITU-T Recommendation H.248.45: "Gateway control protocol: MGC information package". [11] ETSI ES 201 235-3: "Access and Terminals (AT); Specification of Dual-Tone Multi-Frequency (DTMF) Transmitters and Receivers; Part 3: Receivers". |
6e795bd50d66978f3253adc5068d22be | 183 031 | 3 Definitions, symbols and abbreviations | |
6e795bd50d66978f3253adc5068d22be | 183 031 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in 3GPP TS 29.333 [1] apply. |
6e795bd50d66978f3253adc5068d22be | 183 031 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in 3GPP TS 29.333 [1] and the following apply: NGN Next Generation Network Endorsement notice The present document endorses 3GPP TS 29.333 [1], the contents of which apply together with the exception of clause 1 and the modifications being covered herein. Global modifications to 3GPP TS 29.333 Throughout the text of 3GPP TS 29.333 [1] Replace "MGW" with "MRFP" Replace references as shown in table 1. Table 1 Reference(s) in 3GPP TS 29.333 [1] Replaced reference(s) 1 3GPP TS 23.228: IP Multimedia Subsystem (IMS); Stage 2. ETSI TS 182 006 2 3GPP TS 23.002: Network architecture. ETSI ES 282 007 25 3GPP TS 23.333: "Multimedia Resource Function Controller (MRFC) - Multimedia Resource Function Processor (MRFP) Mp interface: Procedures Descriptions". Not Applicable to TISPAN NGN. 26 ITU-T Recommendation H.248.9a1 (03/2007), "Gateway control protocol: Advanced media server package (draft work in progress)". ITU-T Recommendation H.248.9 Amendment 1 (08/2007), "Gateway control protocol: Advanced media server packages - Amendment 1: ASR, TTS and Multimedia enhancements". ETSI ETSI TS 183 031 V2.0.0 (2008-02) 7 5.1 Profile Identification Modify table 5.1.1 as follows: Table 5.1.1: Profile Identification Profile name: MRF or ETSIprof_MediaServer Version: 1 5.3 Gateway Control Protocol Version Modify the text as follows: Version 2 shall be the minimum version supported. Support of this version implies conformance to ITU-T Recommendation H.248 Version 2 [3] and Corrigendum 1, and implementation of the corrections available in the latest version of the H.248 Implementors' Guide [2]. 5.7.1 Stream Descriptor Add the following table: Table 5.7.1.1.2A: Local control properties Properties associated with Local Control Descriptor supported Yes If yes Property IDs Reported Termination type Stream type MGCinfo/db RTP Any nt/jit RTP Any aassm/* RTP Audio/Video aasrec/* RTP Audio/Video vcp/level RTP Audio vlmp/mixlevel RTP Audio vlmp/nspeakmix RTP Audio mvlcp/mixpartnum RTP Audio mvlcp/vollevip RTP Audio 5.7.2 Events Descriptor Add the following three lines to table 5.7.2.1: Event ID Termination Type Stream Type vdp/* RTP Audio aasdc/* RTP Audio xdd/* RTP Audio Modify table 5.7.2.4 as follows: Table 5.7.2.4: Embedding in event Embedded events in an event descriptor: Yes Embedded signals in an event descriptor: Yes ETSI ETSI TS 183 031 V2.0.0 (2008-02) 8 5.7.4 Signals Descriptor Add the following three lines to table 5.7.4.1 Signal ID Termination Type Stream Type/ID aassm/* RTP Audio/Video indview/* RTP Any an/* RTP Audio/Video Modify table 5.7.4.5 as follows: Table 5.7.4.5: Notify completion Notify completion supported: Yes Signal ID Type of completion supported If yes cg/*, svrtn/*, xcg/*, an/*, int/*, biztn/*, conftn/* , tonegen/*, bcg/*, aasb/*, indview ALL Modify table 5.7.4.6 as follows: Table 5.7.4.6: RequestID Parameter RequestID Parameter Supported: Yes NOTE: When the event is provisioned in the media gateway, the Request Id is set to FFFFFFFF'H. Modify table 5.7.4.7 as follows: Table 5.7.4.7: Signals played simultaneously Signals played simultaneously: Yes If yes Signal Ids that can be played simultaneously: - 5.7.5 DigitMap Descriptor Modify table 5.7.5.1 as follows: Table 5.7.5.1: DigitMap Descriptor DigitMaps supported: Yes DigitMap Name Structure Timers If yes 5.8.8 ServiceChange Modify table 5.8.8 as follows: Table 5.8.8.4: Service Change Delay ServiceChangeDelay used: Yes If yes Valid time period: - ETSI ETSI TS 183 031 V2.0.0 (2008-02) 9 5.9 Generic Command Syntax and Encoding Replace table 5.9.1 as follows: Table 5.9.1: Encoding Supported Encodings: Text encoding shall be supported by both the MRFP and the MRFC. Both the long and short form of text encoding shall be supported at the receiving side. 5.14.1 Mandatory Packages Add the following line to table 5.14.1: RTP Package (ITU-T Recommendation H.248.1 [3]) rtp 1 5.14.2 Optional Packages Remove the following line to table 5.14.2 RTP Package (H.248.1, [3]) rtp 1 Add the following lines to table 5.14.2 Extended DTMF Detection (H.248.16 [10]) xdd 1 Support is mandatory if DTMF collection is supported and the AAS Digit Collection package is not supported, optional otherwise. AAS Digit collection (H.248.9 [6]) aasdc 2 Support is mandatory if ADVANCED_UI, optional otherwise. Floor Control (H.248.19 [11]) fcp 1 Support is mandatory if ADVANCED_CONFERENCING is supported, not required otherwise. View (H.248.19 [11]) indview 1 Support is mandatory if ADVANCED_CONFERENCING is supported, not required otherwise. Volume Control (H.248.19 [11]) vcp 1 Support is mandatory if ADVANCED_CONFERENCING is supported, optional otherwise. Volume Detection (H.248.19 [11]) vdt 1 Support is mandatory if ADVANCED_CONFERENCING is supported, optional otherwise. Volume Level Mixing (H.248.19 [11]) vlm 1 Support is mandatory if ADVANCED_CONFERENCING is supported, not required otherwise. Mixing Volume Level Control (H.248.19 [11]) mvlc 1 Support is mandatory if ADVANCED_CONFERENCING is supported, not required otherwise. Inactivity Timer (H.248.14 [9]) it 1 Support is mandatory if UDP transport is enabled for H.248 messages. MGC Information (H.248.45 see note) MGCInfo 1 This package may be supported as an operator option. For this profile the information string shall be limited to 32 octets in length. NOTE: See [10] in TS 183 031. ETSI ETSI TS 183 031 V2.0.0 (2008-02) 10 5.14.3 Package Usage Information Clause 5.14.3 of [1] applies with the following additions: 5.14.3.26A Extended DTMF detection package Table 5.14.3.26a: Package usage information for extended DTMF detection package Properties Mandatory/ Optional Used in command Supported Values Provisioned Value None Not applicable Not applicable Not applicable Not applicable Signals Mandatory/ Optional Used in command Duration Provisioned Value Not applicable Not applicable Not applicable Signal Parameters Mandatory/ Optional Supported Values Duration Provisioned Value None Not applicable Not applicable Not applicable Not applicable Events Mandatory/ Optional Used in command DTMF Digits (see note) M ADD, MODIFY, NOTIFY, AUDITVALUE, AUDITCAPABILITY Event Parameters Mandatory/ Optional Supported Values Provisioned Value None Not applicable Not applicable Not applicable ObservedEvent Parameters Mandatory/ Optional Supported Values Provisioned Value None Not applicable Not applicable Not applicable Extended Digit Map Completion M ADD, MODIFY, NOTIFY, AUDITVALUE, AUDITCAPABILITY Event Parameters Mandatory/ Optional Supported Values Provisioned Value Buffer Control M ALL 0 Extra Digit Disposition M ALL OFF Match Procedure M ALL base ObservedEvent Parameters Mandatory/ Optional Supported Values Provisioned Value digit string M ALL Not applicable termination method M ALL Not applicable Unmatched Event M ALL Not applicable Statistics Mandatory/ Optional Used in command Supported Values None Not applicable Not applicable Not applicable Error Codes Mandatory/Optional None Not applicable NOTE: DTMF detection shall conform to ES 201 235-3 [11]. ETSI ETSI TS 183 031 V2.0.0 (2008-02) 11 5.14.3.26B AAS digit collection package Table 5.14.3.26B: Package usage information for AAS digit collection package Properties Mandatory/ Optional Used in command Supported Values Provisioned Value None Not applicable Not applicable Not applicable Not applicable Signals Mandatory/ Optional Used in command Duration Provisioned Value Play Collect M ADD, MODIFY, AUDITVALUE, AUDITCAPABILITY Not applicable Signal Parameters Mandatory/ Optional Supported Values Duration Provisioned Value Initial Prompt M ALL Not applicable Reprompt M ALL Not applicable Number of Digits Prompt M ALL Not applicable Successful announcement M ALL Not applicable Announcement Failure M ALL Not applicable Non Interruptable Play M ALL FALSE Keep digits M ALL FALSE Clear Digits Buffer M ALL FALSE Maximum Number of Attempts M ALL 1 Digit Map M ALL Not applicable Speed O ALL 0 Volume M ALL 0 Offset M ALL 0 Restart Key M ALL 0 Re-input key M ALL None Return Key M ALL None Iterations M ALL 1 Interval M ALL None End Input Key M ALL None Include End Input Key M ALL FALSE Voice Information M ALL dtmfonly Voice back M ALL novoiceback INPA Prompt timer M ALL None Events Mandatory/ Optional Used in command Audio Operation Failure M ADD, MODIFY, NOTIFY, AUDITVALUE, AUDITCAPABILITY Event Parameters Mandatory/ Optional Supported Values Provisioned Value None Not applicable Not applicable Not applicable ObservedEvent Parameters Mandatory/ Optional Supported Values Provisioned Value Return Code M ALL Not applicable Play Collect Success M ADD, MODIFY, NOTIFY, AUDITVALUE, AUDITCAPABILITY Event Parameters Mandatory/ Optional Supported Values Provisioned Value None Not applicable Not applicable Not applicable ObservedEvent Parameters Mandatory/ Optional Supported Values Provisioned Value Digits Collected M ALL Not applicable (see note) Number of attempts M ALL Not applicable Amount Played O ALL Not applicable ETSI ETSI TS 183 031 V2.0.0 (2008-02) 12 Statistics Mandatory/ Optional Used in command Supported Values None Not applicable Not applicable Not applicable Error Codes Mandatory/Optional None Not applicable NOTE: DTMF detection shall conform to ES 201 235-3 [11]. 5.14.3.26C Floor control package Table 5.14.3.26C: Package usage information for floor controlpackage Properties Mandatory/ Optional Used in command Supported Values Provisioned Value Activate Floor Controller M ADD, MODIFY, AUDITVALUE, AUDITCAPABILITY ALL Not applicable Signals Mandatory/ Optional Used in command Duration Provisioned Value Not applicable Not applicable Not applicable Signal Parameters Mandatory/ Optional Supported Values Duration Provisioned Value Not applicable Not applicable Not applicable Not applicable None Events Mandatory/ Optional Used in command Not applicable Not applicable Event Parameters Mandatory/ Optional Supported Values Provisioned Value Not applicable Not applicable Not applicable Not applicable ObservedEvent Parameters Mandatory/ Optional Supported Values Provisioned Value None Not applicable Not applicable Not applicable Not applicable Statistics Mandatory/ Optional Used in command Supported Values None Not applicable Not applicable Not applicable Error Codes Mandatory/Optional None Not applicable 5.14.3.26D View package Table 5.14.3.26D: Package usage information for view package Properties Mandatory/ Optional Used in command Supported Values Provisioned Value None Not applicable Not applicable Not applicable Not applicable Signals Mandatory/ Optional Used in command Duration Provisioned Value M ADD, MODIFY, AUDITVALUE, AUDITCAPABILITY Not applicable Signal Parameters Mandatory/ Optional Supported Values Duration Provisioned Value Viewed by whom M ALL Not applicable Being Viewed Viewer Identity M ALL Not applicable M ADD, MODIFY, AUDITVALUE, AUDITCAPABILITY Not applicable Signal Parameters Mandatory/ Optional Supported Values Duration Provisioned Value No Viewer None Events Mandatory/ Optional Used in command Not applicable Not applicable None Event Parameters Mandatory/ Optional Supported Values Provisioned Value ETSI ETSI TS 183 031 V2.0.0 (2008-02) 13 Properties Mandatory/ Optional Used in command Supported Values Provisioned Value Not applicable Not applicable Not applicable Not applicable ObservedEvent Parameters Mandatory/ Optional Supported Values Provisioned Value Not applicable Not applicable Not applicable Not applicable Statistics Mandatory/ Optional Used in command Supported Values None Not applicable Not applicable Not applicable Error Codes Mandatory/Optional None Not applicable 5.14.3.26E Volume control package Table 5.14.3.26E: Package usage information for volume control package Properties Mandatory/ Optional Used in command Supported Values Provisioned Value Volume Level M ADD, MODIFY, AUDITVALUE, AUDITCAPABILITY ALL Not applicable Signals Mandatory/ Optional Used in command Duration Provisioned Value Not applicable Not applicable Not applicable Signal Parameters Mandatory/ Optional Supported Values Duration Provisioned Value None Not applicable Not applicable Not applicable Not applicable Events Mandatory/ Optional Used in command Not applicable Not applicable Event Parameters Mandatory/ Optional Supported Values Provisioned Value Not applicable Not applicable Not applicable Not applicable ObservedEvent Parameters Mandatory/ Optional Supported Values Provisioned Value None Not applicable Not applicable Not applicable Not applicable Statistics Mandatory/ Optional Used in command Supported Values None Not applicable Not applicable Not applicable Error Codes Mandatory/Optional None Not applicable 5.14.3.26F Volume detection package Table 5.14.3.26F: Package usage information for volume detection package Properties Mandatory/ Optional Used in command Supported Values Provisioned Value None Not applicable Not applicable Not applicable Not applicable Signals Mandatory/ Optional Used in command Duration Provisioned Value Not applicable Not applicable Not applicable Signal Parameters Mandatory/ Optional Supported Values Duration Provisioned Value None Not applicable Not applicable Not applicable Not applicable Events Mandatory/ Optional Used in command M ADD, MODIFY, NOTIFY, AUDITVALUE, AUDITCAPABILITY Event Parameters Mandatory/ Optional Supported Values Provisioned Value Volume Threshold M ALL Not applicable Volume Activity Detection ObservedEvent Parameters Mandatory/ Optional Supported Values Provisioned Value ETSI ETSI TS 183 031 V2.0.0 (2008-02) 14 Properties Mandatory/ Optional Used in command Supported Values Provisioned Value None Not applicable Not applicable Not applicable Statistics Mandatory/ Optional Used in command Supported Values None Not applicable Not applicable Not applicable Error Codes Mandatory/Optional None Not applicable 5.14.3.26G Volume level mixing package Table 5.14.3.26G: Package usage information for volume level mixing package Properties Mandatory/ Optional Used in command Supported Values Provisioned Value Volume Mixing Level M ADD, MODIFY, AUDITVALUE, AUDITCAPABILITY ALL Not applicable N Speakers Mixing O ADD, MODIFY, AUDITVALUE, AUDITCAPABILITY ALL Not applicable Signals Mandatory/ Optional Used in command Duration Provisioned Value Not applicable Not applicable Not applicable Signal Parameters Mandatory/ Optional Supported Values Duration Provisioned Value None Not applicable Not applicable Not applicable Not applicable Events Mandatory/ Optional Used in command Not applicable Not applicable Event Parameters Mandatory/ Optional Supported Values Provisioned Value Not applicable Not applicable Not applicable Not applicable ObservedEvent Parameters Mandatory/ Optional Supported Values Provisioned Value None Not applicable Not applicable Not applicable Not applicable Statistics Mandatory/ Optional Used in command Supported Values None Not applicable Not applicable Not applicable Error Codes Mandatory/Optional None Not applicable 5.14.3.26H Mixing volume level control package Table 5.14.3.26H: Package usage information for mixing volume level control package Properties Mandatory/ Optional Used in command Supported Values Provisioned Value Mix Participant Number M ADD, MODIFY, AUDITVALUE, AUDITCAPABILITY ALL Not applicable Volume Level Input to Mix M ADD, MODIFY, AUDITVALUE, AUDITCAPABILITY ALL Not applicable Signals Mandatory/ Optional Used in command Duration Provisioned Value Not applicable Not applicable Not applicable Signal Parameters Mandatory/ Optional Supported Values Duration Provisioned Value None Not applicable Not applicable Not applicable Not applicable ETSI ETSI TS 183 031 V2.0.0 (2008-02) 15 Properties Mandatory/ Optional Used in command Supported Values Provisioned Value Events Mandatory/ Optional Used in command Not applicable Not applicable Event Parameters Mandatory/ Optional Supported Values Provisioned Value Not applicable Not applicable Not applicable Not applicable ObservedEvent Parameters Mandatory/ Optional Supported Values Provisioned Value None Not applicable Not applicable Not applicable Not applicable Statistics Mandatory/ Optional Used in command Supported Values None Not applicable Not applicable Not applicable Error Codes Mandatory/Optional None Not applicable 5.17 Procedures Replace the contents of clause 5.17 with the contents of annex ZB of the present document. ETSI ETSI TS 183 031 V2.0.0 (2008-02) 16 Annex ZA (normative): MRFP Functional requirements Support of the packages identified in the profile definition implies support of the underlying functionality. This annex identifies additional functional requirements that media resource function processors conforming to the present document shall comply with: • Media Resource Function Processors (MRFP) shall support IPv4 and may support IPv6. • Media Resource Function Processors (MRFP) shall support G.711 A-law voice codec and may support other codecs. Media Resource Function Processors supporting transcoding are expected to support a wide range of well-known codecs. The list of codecs is outside the scope of the present document. • Media Resource Function Processors (MRFP) shall support the procedures defined in RFC 2833 [3] to generate, detect and forward DTMF digits. DTMF shall be identified by name (see mode "Named Telephone Events" in clause 3 of RFC 2833 [3]), as opposed to their waveform properties. • All properties of tones requested by the MRFC shall be provisioned in the MRFP. The MRFC is not required to send the physical characteristics of tones to Media Resource Function Processors (MRFP). ETSI ETSI TS 183 031 V2.0.0 (2008-02) 17 Annex ZB (normative): Procedures ZB.1 General procedures Media Resource Function Processors shall discard packets with RTP payload types (PT) that do not match the Local Descriptor contents. NOTE: Besides an incorrect RTP PT field might be also other reasons for discarding packets (invalid SSRC field, invalid CRC, etc.). When sending packets from a termination, Media Resource Function Processors shall use the address and port in the Local Descriptor as a source address and port. ZB.2 Use of voice codecs ZB.2.1 Comfort noise insertion and silence suppression for voice codecs If a codec has built-in support for silence suppression and comfort noise insertion, the activation or deactivation of these features shall be indicated using the a= line according to RFC 3551 [4] and RFC 3555 [5]. If the selected codec does not have built in support for silence suppression and Comfort Noise (CN) insertion, the CN payload code [6] may be included in the media description. E.g. for ITU-T Recommendation G.711 [7], A-Law: v= 0 c= IN <address type> <connection address> m = audio <port number> RTP/AVP 8 13 a= ptime: 10 If the CN payload is included in the Local Descriptor, the MRFP shall be prepared to receive CN packets during silence periods. This action also corresponds to an implicit enabling of the silence suppression mode in receiving direction. If the CN payload is included in the Remote Descriptor, the MRFP shall send CN packets during silence periods. This action corresponds to an implicit enabling of the silence suppression mode in sending direction. Comfort noise generation, voice activity detection and discontinuous transmission algorithms are outside the scope of the present document. ZB.2.2 DTMF transmission When a G.711 codec is used, Media Resource Function Processors shall be able to generate, detect and forward DTMF tones inband. When other codecs are used, the MRFC should request the use of the procedures defined in RFC 2833 [3] to send and receive DTMF tones. • If the Local Descriptor sent by the MRFC includes the support for RFC 2833 [3], Media Resource Function Processors (MRFP) shall be prepared to receive and detect DTMF tones in the form of named events. • If the Remote Descriptor indicates that RFC 2833 [3] is supported, Media Resource Function Processors (MRFP) shall be prepared to relay in the form of named events, any DTMF tone that may be received from other ephemeral terminations. ETSI ETSI TS 183 031 V2.0.0 (2008-02) 18 • Media Gateways supporting conferencing or transcoding shall support transcoding between in-band DTMF and named events defined RFC 2833 [3], based on the contents of the Local and Remote descriptors of the involved terminations. A Dynamic Payload type shall be used to indicate support of RFC 2833 [3] for DTMF relay. EXAMPLE: v= 0 c= IN <address type> <connection address> m= audio <port number> RTP/AVP 18 110 a= ptime: 10 a= rtpmap: 110 telephone-event/8000 a= fmtp: 110 0-15 ZB.2.3 Support of G.711 variants ZB.2.3.1 G.711 Encoding law Media Resource Function Processors conforming to the present document are required to support G.711 A-Law and may also support μ-Law in order to avoid call failure or transcoding in case the remote entity supports μ-Law only. How and where to perform transcoding in IP networks in case both terminals/gateways do not support the same variant is outside the scope of this profile. ZB.2.3.2 G.711 packet loss concealment G.711-over-IP may be operated with or without error loss concealment. Typically is that decision dependent on the IP packet loss rate conditions. G.711 error loss concealment is based on RTP packet granularity, therefore called as Packet Loss Concealment (PLC). ITU-T Recommendation G.711 Appendix I [8] provides a framework for G.711 PLC mode. ZB.2.3.3 G.711 silence suppression mode G.711-over-IP may be operated with or without silence suppression. In case of silence suppression, comfort noise generation shall be based on ITU-T Recommendation G.711 Appendix II [9]. These features may be enabled/disabled on a per session basis, using the procedure described in clause ZB.4. ZB.3 Procedures for basic user interaction User Interaction procedures are applied to the ephemeral termination representing the media flow to/from the user involved in the interaction procedure. The ephemeral termination may already be in a context or may have to be created in a new context. Signals representing tones and announcements are applied to this termination and played towards the exterior of the context. Events representing DTMF digits are detected on this termination. ZB.4 Procedures for advanced user interaction User Interaction procedures are applied to the ephemeral termination representing the media flow to/from the user involved in the interaction procedure. The ephemeral termination may already be in a context or may have to be created in a new context. Signals representing tones and announcements are applied to this termination and played towards the exterior of the context. Events representing DTMF digits or recognized speech segments are detected on this termination. Voice-messaging services are implemented by applying the playrec signal from the AAS Recording package and detecting related event on this termination. ETSI ETSI TS 183 031 V2.0.0 (2008-02) 19 ZB.5 Procedures for conferencing Conference services are implemented by creating H.248 contexts with the appropriate number of terminations using native H.248 mixing and transcoding capabilities. Each conference participant is represented by an ephemeral termination. Floor control procedures are implemented according to the procedures described in H.248.19 (reference [11] in 3GPP TS 29.333). ZB.6 Procedures for transcoding The MRFP may be required to perform transcoding in the context of a conference setup or in the context of basic two party calls. This clause describes the procedures for controlling transcoding in case of a two party call. Procedures for controlling transcoding in conferences are described in clause ZB.5. NOTE: Media Transcoding is performed by the MRFP under the control an MRFC. The criteria that trigger the insertion of an MRFC in the SIP signalling path is outside the scope of the present document. On receipt of a transcoding request for a two-party session between A and B, the MRCF shall request the MRFP to create a context with one ephemeral termination representing the A party (Ta) and one ephemeral termination representing the B party (Tb). Remote and Local Descriptors shall be populated as follows: • The Remote Descriptor for termination Ta shall be set according to the SDP Offer initially received from the A party. • The Remote Descriptor for termination Tb shall be set according to the SDP Answer received from the B party. • The media format in the Local Descriptor for termination Ta shall be set according to the SDP Offer initially received from the A party. The IP address and port shall be wildcarded. • The media format in the Local Descriptor for termination Tb shall be set according to the SDP Answer received from the B party. The IP address and port shall be wildcarded. The value of the Local Descriptor returned by the MRFP for the termination Ta shall be sent as an SDP Answer to the A party (via the S-CSCF/AS). The value of the Local Descriptor returned by the MRFP for the termination Tb shall be sent as a new SDP Offer to the B party (via the S-CSCF/AS). The MRFC is responsible for sending the SDP information in SIP messages that are compatible with the state of the SIP dialogue. ETSI ETSI TS 183 031 V2.0.0 (2008-02) 20 History Document history V2.0.0 Febuary 2008 Publication |
bd34fa72f1340d2659f6c02dcc9e311c | 183 029 | 1 Scope | The present document specifies the stage three (protocol description) of the Explicit Communication Transfer (ECT) simulation service, based on stage one and two of the ISDN ECT supplementary service. |
bd34fa72f1340d2659f6c02dcc9e311c | 183 029 | 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. |
bd34fa72f1340d2659f6c02dcc9e311c | 183 029 | 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] ETSI TS 124 429: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); ECT (3GPP TS 24.429 Release 7)". ETSI ETSI TS 183 029 V1.4.0 (2008-06) 6 |
bd34fa72f1340d2659f6c02dcc9e311c | 183 029 | 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. |
bd34fa72f1340d2659f6c02dcc9e311c | 183 029 | 3 Definitions and abbreviations | |
bd34fa72f1340d2659f6c02dcc9e311c | 183 029 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in TS 124 429 [10] apply: |
bd34fa72f1340d2659f6c02dcc9e311c | 183 029 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in TS 124 429 [10] apply: |
bd34fa72f1340d2659f6c02dcc9e311c | 183 029 | 4 Explicit Communication Transfer (ECT) | The provisions of the present document are contained in TS 124 429 [10]. ETSI ETSI TS 183 029 V1.4.0 (2008-06) 7 Annex A (informative): Signalling flows Information is contained in TS 124 429 [10]. ETSI ETSI TS 183 029 V1.4.0 (2008-06) 8 Annex B (informative): Example of filter criteria Information is contained in TS 124 429 [10]. ETSI ETSI TS 183 029 V1.4.0 (2008-06) 9 Annex C (informative): Example charging model Information is contained in TS 124 429 [10]. ETSI ETSI TS 183 029 V1.4.0 (2008-06) 10 Annex D (informative): Bibliography Information is contained in TS 124 429 [10]. ETSI ETSI TS 183 029 V1.4.0 (2008-06) 11 History Document history V1.1.1 April 2006 Publication V1.2.1 April 2007 Publication V1.3.2 October 2007 Publication V1.4.0 June 2008 Publication |
50752ebe4c950afe359a9d1527e5fa13 | 183 016 | 1 Scope | The present document specifies the, stage three, Protocol Description of the Malicious Call Communication Identification (MCID) service. |
50752ebe4c950afe359a9d1527e5fa13 | 183 016 | 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. |
50752ebe4c950afe359a9d1527e5fa13 | 183 016 | 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. ETSI ETSI TS 183 016 V2.6.0 (2008-06) 6 [12] ETSI TS 124 516: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); TISPAN; PSTN/ISDN simulation services; Malicious Communication Identification (MCID); Protocol specification (3GPP TS 24.516 Release 8)". |
50752ebe4c950afe359a9d1527e5fa13 | 183 016 | 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. |
50752ebe4c950afe359a9d1527e5fa13 | 183 016 | 3 Definitions and abbreviations | |
50752ebe4c950afe359a9d1527e5fa13 | 183 016 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in TS 124 516 [12] apply. |
50752ebe4c950afe359a9d1527e5fa13 | 183 016 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in TS 124 516 [12] apply. |
50752ebe4c950afe359a9d1527e5fa13 | 183 016 | 4 Malicious Communication Identification (MCID) | The provisions of the present document are contained in TS 124 516 [12]. ETSI ETSI TS 183 016 V2.6.0 (2008-06) 7 Annex A (informative): Signalling Flows Information is contained in TS 124 516 [12]. ETSI ETSI TS 183 016 V2.6.0 (2008-06) 8 Annex B (informative): Example of filter criteria Information is contained in TS 124 516 [12]. ETSI ETSI TS 183 016 V2.6.0 (2008-06) 9 Annex C (informative): Change history Information is contained in TS 124 516 [12]. ETSI ETSI TS 183 016 V2.6.0 (2008-06) 10 Annex D (informative): Bibliography Information is contained in TS 124 516 [12]. ETSI ETSI TS 183 016 V2.6.0 (2008-06) 11 History Document history V2.5.0 July 2007 Publication V2.6.0 June 2008 Publication |
303e74d8013c9a80fc5072ebde975465 | 183 015 | 1 Scope | The present document specifies the, stage three, Protocol Description of the Communication Waiting (CW) service. |
303e74d8013c9a80fc5072ebde975465 | 183 015 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity. |
303e74d8013c9a80fc5072ebde975465 | 183 015 | 2.1 Normative references | The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] ETSI TS 124 615: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Communication Waiting (CW) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification; (Release 8)". |
303e74d8013c9a80fc5072ebde975465 | 183 015 | 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. |
303e74d8013c9a80fc5072ebde975465 | 183 015 | 3 Definitions and abbreviations | |
303e74d8013c9a80fc5072ebde975465 | 183 015 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in TS 124 615 [1] apply. |
303e74d8013c9a80fc5072ebde975465 | 183 015 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in TS 124 615 [1] apply. ETSI ETSI TS 183 015 V2.1.1 (2009-04) 6 |
303e74d8013c9a80fc5072ebde975465 | 183 015 | 4 Communication Waiting (CW) | The provisions of the present document are contained in TS 124 615 [1]. ETSI ETSI TS 183 015 V2.1.1 (2009-04) 7 Annex A (informative): Signalling Flows Information is contained in TS 124 615 [1]. ETSI ETSI TS 183 015 V2.1.1 (2009-04) 8 Annex B (informative): Example of filter criteria Information is contained in TS 124 615 [1]. ETSI ETSI TS 183 015 V2.1.1 (2009-04) 9 History Document history V2.1.1 April 2009 Publication |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.