hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
|---|---|---|---|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.5.0 General information regarding the service
|
As a network option the Activation, Deactivation and Interrogation of call forwarding services is performed using service code commands as described in ETSI EN 300 207-1 [34] (ISDN; Diversion supplementary services) and ETSI EN 300 196-1 [25] (ISDN; Generic functional protocol for the support of supplementary services). NOTE: These messages are mapped to the regarding PSTN XML documents described in clause 4.9 of ETSI TS 124 604 [8] and are sent via the Ut-interface to the AS.
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.5.1 Actions at the Outgoing AGCF/VGW
| |
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.5.1.1 Reception of a "call is diverting" notification
|
5.2.5.1.1.0 General clarification According to ETSI TS 124 604 [8], the 181 Being Forwarded may be received. 5.2.5.1.1.1 First diversion The latest history-entry, representing the diverted-to-number, contained in the History-Info header is stored. A notification of diversion is sent to the calling user as shown in table 5.2.5.1.1.1-1. Table 5.2.5.1.1.1-1: First diversion: notification of diversion sent to the calling user ←DSS 1 message ←181 (Call Being Forwarded) (see note) Notification indicator information element Call is diverting NOTE: If no message is to be sent, the notification indicator information element is sent in a NOTIFY message. 5.2.5.1.1.2 Subsequent diversion The latest history-entry, represents the diverted-to-number, contained in the History-info header field is stored if the URI of the history-entry is different to the previous received and stored diverted-to number (i.e. the latest received diverted-to number replaces the one received previously). If notification of diversion is not allowed, no specific interworking action is required towards the calling user. If notification of diversion is allowed, table 5.2.5.1.1.2-1 is applicable. Table 5.2.5.1.1.2-1: Subsequent diversion: notification of diversion sent to the calling user ←DSS 1 message ←181 Call Being Forwarded (see note 1) Notification indicator IE No notification sent History-Info header: latest history-entry Call is diverting cause=487 (Deflection during alerting) or cause=408 (No reply) No notification sent Other cause values NOTE 1: The determination of the DSS 1 message sent upon 181 Being Forwarded is described in clause 5.1. If no message is to be sent, the notification indicator information element is sent in a NOTIFY message. NOTE 2: The latest received diverted to number replaces the one received previously. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 58
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.5.1.2 Evaluation of History-Info header
|
If a backward message (provisional response or 200 OK) is received containing a History-Info header and there is no privacy header is included in the URI of the latest history-entry: • it has been determined, according to ETSI TS 124 604 [8], that the notification of diverted-to number is allowed, a redirection number information element is sent to the calling user as shown in table 5.2.5.1.2-1; • if a Privacy=history is included in the latest history-entry, no information is sent to the calling user. Table 5.2.5.1.2-1: Notification of the diverted-to number ←DSS 1 message (see note 1) Redirection number parameter stored in the originating entity ←181, 183 (in case multiple call diversion), 180 or 200 OK Redirection number information element History-Info header: Latest History-entry Type of number According to the nature of address indicator (see note 2) Numbering plan identification ISDN (telephony) numbering plan Presentation indicator Presentation allowed Number digits Digits received in the userinfo Nature of address indicator National number sip: local-number-digits; phone-context=nat @hostportion; user=phone International number sip: global-number- digits@hostportion; user=phone. Numbering plan indicator ISDN (telephony) numbering plan Address signal: User portion received in the URI; if the country code of the URI: In case for global number and the country code is the same as the AGCF/VGW or line is located, the country code is removed from the number of the Type of number is set to "national number". Mw or Gm Interface No Privacy header included Type of number Unknown Numbering plan identification Unknown Presentation indicator Presentation restricted Number digits Not included Digits or no Information Element is sent Nature of address indicator National number sip: local-number-digits; phone-context=nat @hostportion; user=phone International number sip: global-number- digits@hostportion; user=phone. Numbering plan indicator ISDN (telephony) numbering plan Address signal User portion received in the URI. In case for global number and the country code is the same as the AGCF/VGW or line is located, the country code is removed from the number of the Type of number is set to "national number" Mw Interface Privacy header included and the value is equal to "history" Type of number Unknown Numbering plan identification Unknown Presentation indicator Number not available due to interworking Number digits Not included (see note 3) or no Information Element is sent No redirection number stored Mw or Gm Interface No History-Info header received NOTE 1: The determination of the DSS 1 message sent upon the SIP backward message is described in clause 5.1. If no message is to be sent, the redirection number information element is sent in a NOTIFY message. NOTE 2: As a network option, the type of number may be coded unknown. NOTE 3: This redirection number is sent if e 181 was received and no History-Info header was included in any response. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 59
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.5.1.3 Procedures at the T reference point
|
When the AGCF/VGW receives a SETUP containing a Facility information element including a DivertingLegInformation2 invoke component (ETSI EN 300 207-1 [34], clause 10.4.1), an INVITE is sent containing a History-Info header. Table 5.2.5.1.3-1: Mapping of the DivertingLegInformation2 invoke component into the History-Info header SETUP→ INVITE→ Mapping of sending complete info element see Table 5.1.1.1.0-1: Coding of the BC received see table 5.1.1.1.2-1: DivertingLegInformation2 History-Info header diversionCounter 1 History Index Number of diversions are shown due to the number of Index Entries (see note) Index for divertingNr = 1 Index for Request URI = 1.1 2 Index for originalCalledNr = 1 Index for divertingNr = 1.1 Index for Request URI = 1.1.1 N (max 5) Index for originalCalledNr = 1 Placeholder History entry with Index = 1.1 … Fill up … Index for divertingNr = 1+[(N-1)*".1"] Index for Request URI = 1+N* ".1" (e.g. N=3 1.1.1.1) diversionReason Unknown Cause parameter in latest History entry "404" cfu "302" cfb "486" cfnr "408" cdAlerting "487" cdImmediate "480" divertingNr (mapping see table 5.2.5.1.3-2) 2nd latest entry originalCalledNr (mapping see table 5.2.5.1.3-3) first entry NOTE: The History index is generated according the rules in subclause 4 in IETF RFC 7044 [45]. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 60 Table 5.2.5.1.3-2: Mapping of divertingNr into the History-Info header History-Info divertingNr Privacy- hdr URI Presentation Indicator PartyNumber format ToN NPI NumberDigit s None sip:NumericString; phone- context=xxxx@hostportion; user=phone presentation Allowed Number unknown PartyNumber unknown unknown NumericString (SIZE (1..20)) sip:NumericString; phone context=xxx@hostportion; user=phone public PartyNumber unknown E.164 NumericString (SIZE (1..20)) Global, sip: "+" NumericString@hostportion; user=phone international sip:NumericString; phone context=xxx@hostportion; user=phone national "unavailable@ unknown.invalid" presentation Restricted NULL number Not Available due to Interworking Privacy sip:NumericString; phone context=xxx@hostportion; user=phone presentation Restricted Number public PartyNumber unknown E.164 NumericString (SIZE (1..20)) Global, sip: "+" NumericString@hostportion; user=phone international sip:NumericString; phone context=xxx@hostportion; user=phone national Table 5.2.5.1.3-3: Mapping of originalCalledNr into the History-Info header History-Info (1st entry) originalCalledNr Privacy- hdr URI Presentation Indicator PartyNumber format ToN NPI NumberDigits None sip:NumericString; phone- context=xxxx@hostportion; user=phone presentation Allowed Number unknown PartyNumber unknown unknown NumericString (SIZE (1..20)) sip:NumericString; phone context=xxx@hostportion; user=phone public PartyNumber unknown E.164 NumericString (SIZE (1..20)) Global, sip: "+" NumericString@hostportion; user=phone international sip:NumericString; phone context=xxx@hostportion; user=phone national "unavailable@ unknown.invalid" presentation Restricted NULL number Not Available due to Interworking Privacy sip:NumericString; phone context=xxx@hostportion; user=phone presentation Restricted Number public PartyNumber unknown E.164 NumericString (SIZE (1..20)) Global, sip: "+" NumericString@hostportion; user=phone international sip:NumericString; phone context=xxx@hostportion; user=phone national ETSI ETSI TS 183 036 V3.7.1 (2021-02) 61 When the AGCF/VGW receives a 18x provisional or 200 OK final response, the AGCF/VGW sends a FACILITY, ALERTING or CONNECT message. The value of the Privacy parameter in the latest contained History-Info header is mapped in a DivertingLegInformation3 invoke component. A FACILITY is only sent, if the 181 contains a History-Info header. Table 5.2.5.1.3-4: Mapping of the value of the Privacy parameter in latest History Entry into the DivertingLegInformation2 invoke component ←DSS1 Message ←SIP Message DivertingLegInformation3: presentationAllowedIndicator History-Info header: Privacy parameter in the latest History entry FACILITY true 181 (Being Forwarded) No Privacy parameter false Privacy: "history" ALERTING true 180 (Ringing) No Privacy parameter false Privacy: "history" CONNECT true 200 OK (INVITE) No Privacy parameter false Privacy: "history"
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.5.2 Actions at the incoming AGCF/VGW
|
5.2.5.2.1 Interworking at the AGCF/VGW where a call is diverted within or beyond the private ISDN (T reference point) When the AGCF/VGW receives a DSS1 PROGRESS or ALERTING message, a Provisional Response is sent. When a FACILITY message is received containing a DivertingLegInformation1 invoke component, a 181 Provisional Response is sent. If the DSS1 FACILITY, PROGRESS or ALERTING message contains a DivertingLegInformation1 invoke component Information Element, a History-Info header is sent in concerned response. The mapping is described in tables 5.2.5.2.1-1 and 5.2.5.2.1-2. Table 5.2.5.2.1-1: Interworking of DSS1 messages ←SIP Message ←DSS1 Message 180 (Ringing) ALERTING 181 (Being forwarded) FACILITY 183 (Session Progress) PROGRESS Table 5.2.5.2.1-2: Mapping of the DivertingLegInformation1 invoke component into History-Info header (ETSI EN 300 207-1 [34], clause 10.1.1) ←SIP Message 18x ←ALERTING, FACILITY, PROGRESS History-Info header DivertingLegInformation1 Latest History Entry: cause-param = "cause" EQUAL Status-Code "404" diversionReason unknown "302" cfu "486" cfb "408" cfnr "487" cdAlerting "480" cdImmediate Privacy parameter in the latest History Entry subscriptionOption noNotification (0) "History" notificationWithoutDivertedToNr (1) No Privacy parameter notificationWithDivertedToNr (2) latest Hi-targeted-to URI divertedToNumber If the DivertingLegInformation1 invoke component: subscriptionOption is coded noNotification, no History-Info header is sent in the response message. For the same circumstance, a FACILITY message is not interworked. In addition, if the ALERTING, FACILITY or CONNECT message contains a DivertingLegInformation3 invoke component. The Privacy parameter escaped in the Hi-target-to-uri representing the diverted-to user in the History-Info header (last entry) is set to the value as described in table 5.2.5.2.1-3. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 62 Table 5.2.5.2.1-3: Mapping of the value of the Privacy parameter in latest History Entry into the DivertingLegInformation3 invoke component ←SIP Message ←DSS1 Message History-Info header: Privacy parameter in the latest History entry DivertingLegInformation3: presentationAllowedIndicator 180 (Ringing) No Privacy parameter ALERTING true Privacy: "history" false 181 (Being forwarded) No Privacy parameter FACILITY true Privacy: "history" false 200 OK (INVITE) No Privacy parameter CONNECT true Privacy: "history" false 5.2.5.2.2 Interworking at the coincident S and T reference point where a diverted call is presented Table 5.2.5.2.2-1: Redirecting number information element sent to the called user INVITE→ SETUP→ History-Info header Content index = 1.1 Redirecting number information element (see table 5.2.5.2.2-2) index > 1.1 1st Redirecting number information element (see table 5.2.5.2.2-3) 2nd Redirecting number information element (see table 5.2.5.2.2-2) Table 5.2.5.2.2-2: Coding of the Redirecting number information element containing the information of the first redirection History-Info header Redirecting number first entry; index=1 information element No Privacy header included Type of number: (see notes 1 and 5) Numbering plan identification: (see notes 2 and 5) Presentation indicator: presentation allowed Reason of diversion: (see note 3) Number digits: (see notes 4 and 5) Privacy=history included Type of number: unknown Numbering plan identification: unknown Presentation indicator: presentation restricted Reason of diversion: (see note 3) No Number digits First entry not included Type of number: unknown Numbering plan identification: unknown Presentation indicator: number not available due to interworking Reason of diversion: (see note 3) No Number digits NOTE 1: National if the URI is coded as follows sip: local-number-digits; phone-context=nat @hostportion; user=phone or international if the URI is coded as follows sip: global -number-digits @hostportion; user=phone. NOTE 2: ISDN numbering plan. NOTE 3: If the index of the latest history-entry is set to 1.1: as received in the cause parameter in the latest history-entry. If the index of the latest history-entry is greater than 1.1: unknown. NOTE 4: User portion as received in the second last URI; global-number-digits: if the country code of the URI is the same as the country where the user or line is located, the country code is removed from the user portion. NOTE 5: As a network provider option the prefix is added to the number. In this case the Numbering plan identification and the Type of number are coded unknown. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 63 Table 5.2.5.2.2-3: Coding of the Redirecting number information element containing the information of the last redirection when index > 1.1 History-Info header Redirecting number second last history-entry information element No Privacy header included Type of number: (see notes 1 and 5) Numbering plan identification: (see notes 2 and 5) Presentation indicator: presentation allowed Reason of diversion: (see note 3) Number digits: (see notes 4 and 5) Privacy=history included Type of number: unknown Numbering plan identification: unknown Presentation indicator: presentation restricted Reason of diversion: (see note 3) No Number digits First entry not included Type of number: unknown Numbering plan identification: unknown Presentation indicator: number not available due to interworking Reason of diversion: (see note 3) No Number digits NOTE 1: National if the URI is coded as follows sip: local-number-digits; phone-context=nat @hostportion; user=phone or International if the URI is coded as follows sip: global -number-digits @hostportion; user=phone. NOTE 2: ISDN numbering plan. NOTE 3: As received in the cause parameter of the index of the latest history-entry. NOTE 4: User portion as received in the second last URI; global-number-digits: if the country code of the URI is the same as the country where the user or line is located, the country code is removed from the user portion. NOTE 5: As a network provider option the prefix is added to the number. In this case the Numbering plan identification and the Type of number are coded unknown. Table 5.2.5.2.2-4: Mapping of cause parameter in the history-entry to reason of diversion Cause parameter Reason of diversion unknown "404" Unknown unconditional "302 " Call forwarding unconditional User Busy "486" Call forwarding busy No reply "408" Call forwarding no reply Deflection during alerting "487" Call deflection during alerting Deflection immediate response "480" Call deflection immediate response Mobile subscriber not reachable "503" Unknown ETSI ETSI TS 183 036 V3.7.1 (2021-02) 64 5.2.5.2.3 Interworking at the AGCF/VGW where a diverted call is presented to a private ISDN (T Reference point) When the AGCF/VGW receives an INVITE, a SETUP is sent on the network/user interface. If the INVITE contains a History-Info header, the History-Info header is mapped into a DivertingLegInformation2 invoke component. The History-Info header is stored in the AGCF/VGW (ETSI EN 300 207-1 [34], clause 10.2.1). Table 5.2.5.2.3-1: Mapping of the History-Info header into the DivertingLegInformation2 invoke component INVITE→ SETUP→ History-Info header DivertingLegInformation2 The number of dots in the latest index value represents the diversionCounter value diversionCounter cause-param = "cause" EQUAL Status-Code in latest History entry "404" diversionReason unknown "302" cfu "486" cfb "408" cfnr "487" cdAlerting "480" cdImmediate 2nd latest entry divertingNr (mapping see table 5.2.5.2.3-2) first entry originalCalledNr (see note) (mapping see table 5.2.5.2.3-3) NOTE: This element is not sent, if the diversionCounter is sent with the value 1. Table 5.2.5.2.3-2: Mapping of the History-Info, 2nd latest entry into the Diverting Number History-Info, 2nd latest entry divertingNr Privacy- hdr URI Presentation Indicator PartyNumber format ToN NPI NumberDigits None sip: global-number-digits @hostportion; user=phone presentation Allowed Number public PartyNumber international E.164 NumericString (SIZE (1..20)) sip: local-number-digits; phone-context=nat @hostportion; user=phone national Absent "unavailable@ unknown.invalid" presentation Restricted NULL number Not Available due to Interworking Privacy sip: global-number-digits @hostportion; user=phone presentation Restricted Number public PartyNumber Unknown Unknown NULL sip: local-number-digits; phone-context=nat @hostportion; user=phone ETSI ETSI TS 183 036 V3.7.1 (2021-02) 65 Table 5.2.5.2.3-3: Mapping of the History-Info, 2nd latest entry into the Original Called Number History-Info, first entry originalCalledNr Privacy- hdr URI Presentation Indicator PartyNumber format ToN NPI NumberDigits None sip: global-number-digits @hostportion; user=phone presentation Allowed Number public PartyNumber international E.164 NumericString (SIZE (1..20)) sip: local-number-digits; phone-context=nat @hostportion; user=phone national Absent "unavailable@ unknown.invalid" presentation Restricted NULL number Not Available due to Interworking "Id" or "Header" or "user" sip: global-number-digits @hostportion; user=phone presentation Restricted Number public PartyNumber Unknown Unknown NULL sip: local-number-digits; phone-context=nat @hostportion; user=phone As a response to this call setup, three possibilities are applicable: a) No further diversion occurs When an ALERTING, PROGRESS or CONNECT is received, the messages are interworked on a basic call base. The stored History-Info header received in the previous received INVITE is included in the Provisional Response or 200 OK INVITE. A Privacy parameter with value "history" is escaped in the last entry representing the diverted to user. In response to the DivertingLegInformation2 invoke component, and when the private network has determined whether presentation of the diverted-to number is allowed or not, the private network shall include a DivertingLegInformation3 invoke component in the FACILITY, ALERTING or CONNECT message sent to the public network. The presentationAllowedIndicator parameter shall indicate whether or not presentation of the diverted-to user's ISDN number is allowed to the calling user. b) A call diversion in the private network When an ALERTING, PROGRESS or FACILITY is received containing a DivertingLegInformation1 invoke component, the stored History-Info header received in the previous received INVITE is included in the Provisional Response and a history entry shall be added, interworked from the received DivertingLegInformation1. The sent History-Info header is stored in the AGCF/VGW, the previous stored History-Info header is overwritten. Table 5.2.5.2.3-4: Mapping of the DivertingLegInformation1 invoke component into added history entry ←SIP Message 18x ←ALERTING, FACILITY, PROGRESS History-Info header DivertingLegInformation1 Added (latest) History Entry: cause-param = "cause" EQUAL Status-Code "404" diversionReason unknown "302" cfu "486" cfb "408" cfnr "487" cdAlerting "480" cdImmediate Privacy parameter in the added (latest) History Entry No History-Info header subscriptionOption noNotification "History" notificationWithoutDivertedToNr No Privacy parameter notificationWithDivertedToNr Added (latest) Hi-targeted-to URI divertedToNumber (mapping see table 5.2.5.2.3-5) ETSI ETSI TS 183 036 V3.7.1 (2021-02) 66 Table 5.2.5.2.3-5: Mapping of the divertedToNumber into History-Info (Hi-targeted-to URI) History-Info (Hi-targeted-to URI) divertedToNumber Privacy- hdr URI Presentation Indicator PartyNumber format ToN NPI NumberDigits None sip:NumericString; phone- context=xxxx@hostportion; user=phone presentation Allowed Number unknown PartyNumber unknown unknown NumericString (SIZE (1..20)) sip:NumericString; phone context=xxx@hostportion; user=phone public PartyNumber unknown E.164 NumericString (SIZE (1..20)) Global, sip: "+" NumericString@hostportion; user=phone international sip:NumericString; phone context=xxx@hostportion; user=phone national "unavailable@ unknown.invalid" presentation Restricted NULL number Not Available due to Interworking Privacy sip:NumericString; phone context=xxx@hostportion; user=phone presentation Restricted Number public PartyNumber unknown E.164 NumericString (SIZE (1..20)) Global, sip: "+" NumericString@hostportion; user=phone international sip:NumericString; phone context=xxx@hostportion; user=phone national If the DivertingLegInformation1 invoke component: subscriptionOption is coded noNotification, no History-Info header is sent in the response message. For the same circumstance, a FACILITY message is not interworked. c) A further call diversion beyond the private network In addition, if the ALERTING, FACILITY or CONNECT message contains a DivertingLegInformation3 invoke component. The Privacy parameter escaped in the Hi-target-to-uri representing the diverted-to user in the History-Info header (last entry) is set to the value as described in table 5.2.5.2.1-3. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 67 Figure 5.2.5.2.3-1: Simplified message flow for response to a call setup in case of call forwarding 5.2.5.2.4 Interworking at the AGCF/VGW where partial rerouteing is requested from a private ISDN (T Reference point) After the SETUP was sent, when a FACILITY containing the CallRerouteing invoke component is received, a 302 (Moved Temporarily) is sent. The calledAddress element of the CallRerouteing invoke component is mapped into the URI of the Contact header. If the CallRerouteing invoke component: subscriptionOption is coded noNotification, no History-Info header is sent in the 302 responsemessage. SETUP SETUP CALL PROCEEDING FACILITY (CallRerouteing ) DISC & Call Rerouting Return resullt REL RLC NOTIFY SETUP + FACILTY DiversionLegInformation2 Option a) No further diversion occurs FACILTY; ALERTING; CONNECT DiversionLegInformation3 Option b) A call diversion in the private network FACILTY; PROGRESS; ALERTING DiversionLegInformation1 FACILTY; PROGRESS; ALERTING DiversionLegInformation3 Option c) A further call diversion beyond the private network FACILITY (CallRerouteing ) T Reference Point (2) (PBX) T Reference Point (1) (PBX) LE ETSI ETSI TS 183 036 V3.7.1 (2021-02) 68 Table 5.2.5.2.4-1: Mapping of the CallRerouteing invoke component into 302 (Moved Temporarily); Option A) ←302 (Moved Temporarily) ←FACILITY CallRerouteing invoke component History-Info header: Last History Entry: cause-param = "cause" EQUAL Status-Code "404" rerouteingReason unknown "302" cfu "486" cfb "408" cfnr "487" cdAlerting "480" cdImmediate Contact header URI calledAddress (see table 5.2.5.2.4-2) isub Called PartySubaddress History-Info header: History Index Number of diversions are sown due to the number of Index Entries (see note) Index for lastRerouteingNr = 1 Index for calledAddress = 1.1 rerouteingCounter 1 Index for To header = 1 Index for lastRerouteingNr URI = 1.1 Index for calledAddress = 1.1.1 2 Index for To header = 1 Placeholder History entry with Index = 1.1 … Fill up … Index for lastRerouteingNr URI = 1+[(N-1)*".1"] Index for calledAddress = 1+N* ".1" (e.g. N=3 1.1.1.1) N PSTN XML body BearerCapability q931InfoElement Bearer Capability LowLayerCompatibility Low layer compatibility HighLayerCompatibility High layer compatibility User-to-User header User-user information History-Info header: 2nd latest entry (see table 5.2.5.2.4-3) lastRerouteingNr (see table 5.2.5.2.4-3) History-Info header: Privacy parameter in the last History Entry No History-Info header subscriptionOption noNotification "History" notificationWithoutDivertedToNr No Privacy parameter notificationWithDivertedToNr No mapping (see note) callingPartySubaddress NOTE: The calling subaddress is contained in the From header of the original INVITE. Table 5.2.5.2.4-2: Mapping of the calledAddress into Contact header Contact header calledAddress Privacy- hdr URI PartyNumber format ToN NPI NumberDigits None sip:NumericString; phone- context=xxxx@hostportion; user=phone unknown PartyNumber unknown unknown NumericString (SIZE (1..20)) sip:NumericString; phone context=xxx@hostportion; user=phone public PartyNumber unknown E.164 NumericString (SIZE (1..20)) Global, sip: "+" NumericString@hostportion; user=phone international sip:NumericString; phone context=xxx@hostportion; user=phone national ETSI ETSI TS 183 036 V3.7.1 (2021-02) 69 Table 5.2.5.2.4-3: Mapping of the lastRerouteingNr into History-Info header: 2nd latest entry History-Info header: 2nd latest entry lastRerouteingNr Privacy- hdr URI Presentation Indicator PartyNumber format ToN NPI NumberDigits None sip:NumericString; phone- context=xxxx@hostportion; user=phone presentation Allowed Number unknown PartyNumber unknown unknown NumericString (SIZE (1..20)) sip:NumericString; phone context=xxx@hostportion; user=phone public PartyNumber unknown E.164 NumericString (SIZE (1..20)) Global, sip: "+" NumericString@hostportion; user=phone international sip:NumericString; phone context=xxx@hostportion; user=phone national "unavailable@ unknown.invalid" presentation Restricted NULL number Not Available due to Interworking Privacy sip:NumericString; phone context=xxx@hostportion; user=phone presentation Restricted Number public PartyNumber unknown E.164 NumericString (SIZE (1..20)) Global, sip: "+" NumericString@hostportion; user=phone international sip:NumericString; phone context=xxx@hostportion; user=phone national ETSI ETSI TS 183 036 V3.7.1 (2021-02) 70 Table 5.2.5.2.4-4: Mapping of the CallRerouteing invoke component into REFER; Option B) REFER ←FACILITY CallRerouteing invoke component History-Info header: Last History Entry: cause-param = "cause" EQUAL Status-Code "404" rerouteingReason unknown "302" cfu "486" cfb "408" cfnr "487" cdAlerting "480" cdImmediate Refer-To header URI calledAddress (see table 5.2.5.2.4-5 ) isub Called PartySubaddress History-Info header: History Index Index for lastRerouteingNr = 1 Index for calledAddress = 1.1 rerouteingCounter 1 Index for To header = 1 Index for lastRerouteingNr URI = 1.1 Index for calledAddress = 1.1.1 2 Index for To header = 1 Placeholder History entry with Index = 1.1 … Fill up … Index for lastRerouteingNr URI = 1+[(N-1)*".1"] Index for calledAddress = 1+N* ".1" (e.g. N=3 1.1.1.1) N PSTN XML body BearerCapability q931InfoElement Bearer Capability LowLayerCompatibility Low layer compatibility HighLayerCompatibility High layer compatibility User-to-User header User-user information History-Info header: 2nd latest entry (see table 5.2.5.2.4-2) lastRerouteingNr (see table 5.2.5.2.4-3) History-Info header: Privacy parameter in the last History Entry No History-Info header subscriptionOption noNotification "History" notificationWithoutDivertedToNr No Privacy parameter notificationWithDivertedToNr No mapping (see note) callingPartySubaddress NOTE: The calling subaddress is contained in the From header of the original INVITE. Table 5.2.5.2.4-5: Mapping of the calledAddress into Refer-To header Refer-To header (see note) calledAddress Privacy- hdr URI PartyNumber format ToN NPI NumberDigits None sip:NumericString; phone- context=xxxx@hostportion; user=phone unknown PartyNumber unknown unknown NumericString (SIZE (1..20)) sip:NumericString; phone context=xxx@hostportion; user=phone public PartyNumber unknown E.164 NumericString (SIZE (1..20)) Global, sip: "+" NumericString@hostportion; user=phone international sip:NumericString; phone context=xxx@hostportion; user=phone national NOTE: The Refer-To header field shall indicate the public address of the transferred target. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 71 If the public network cannot accept the call rerouteing invocation request from the private network, it shall send a Facility information element, with a CallRerouteing return error component in the FACILITY message and release the invoke identifier. The mapping of SIP 501 (generated in the ATS) to the Facility I.E is described in table 5.2.5.2.4-6. The reference call flow for Partial Rerouteing Option B successful is contained in figure 5.2.5.2.4-1, the reference call flow for Partial Rerouteing Option B unsuccessful is contained in figure 5.2.5.2.4-2. Table 5.2.5.2.4-6: CallRerouteing return error component in the FACILITY mapping from 501 501 FACILITY Header field Warning returnErrorComp warn-code 399 warn-agent hostport / pseudonym warn-text notSubscribed, error-value notSubscribed, notAvailable, notAvailable, supplementaryServiceInteractionNotAllowed, supplementaryServiceInteractionNotAllowed, resourceUnavailable, resourceUnavailable, InvalidDivertedToNr, InvalidDivertedToNr, SpecialServiceNr, SpecialServiceNr, DiversionToServedUserNr, DiversionToServedUserNr, NumberOfDiversionsExceeded NumberOfDiversionsExceeded Figure 5.2.5.2.4-1: Partial Rerouteing Option B successful ETSI ETSI TS 183 036 V3.7.1 (2021-02) 72 Figure 5.2.5.2.4-2: Partial Rerouteing Option B unsuccessful
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.6 MCID
| |
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.6.1 Actions at the Outgoing AGCF/VGW
|
There is no interworking requirement relating to the Malicious Call Identification (MCID) supplementary service.
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.6.2 Actions at the incoming AGCF/VGW
|
There is no interworking requirement relating to the Malicious Call Identification (MCID) supplementary service. Invocation of the service To invoke the MCID supplementary service, the called user shall send a McidRequest invoke component carried by a Facility information element in a FACILITY message. This invocation can only be sent during the Active state (N10), during the Disconnect Indication state (N12) the invocation is not successful. To indicate that the service invocation has been accepted, the network shall send a McidRequest return result component carried by a Facility information element in a FACILITY message. These messages are mapped to a reINVITE as described in clause 4.5.2.12.1 of ETSI TS 183 016 [46] and are sent to the AS. Table 5.2.6.2-1: MCID request ←INVITE ←FACILITY XML mcid request McidRequestIndicator="1" (network operator option) McidRequest Additionally as an option to invoke the MCID service, as a network option it is possible to use service code commands via in-band dialogue or using the service code via keypad protocol. These requirements to using the keypad protocol are described in annex A of the present document. The result is available in-band (announcement). ETSI ETSI TS 183 036 V3.7.1 (2021-02) 73
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.7 Explicit Communication Transfer (ECT)
| |
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.7.1 Actions at the Outgoing AGCF/VGW
| |
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.7.1.0 General information regarding the service
|
For this service, the separation "incoming call" and "outgoing call" does not apply. This clause describes the interworking at the AGCF/VGW (i.e. the exchange where the served user is connected to). To simulate ECT in the IMS, the Consultative Transfer is applicable.
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.7.1.1 Coincident S and T reference point
|
5.2.7.1.1.1 Service invocation The invocation of ECT in the alerting state should be rejected by the AGCF/VGW. Table 5.2.7.1.1.1-1: ECT invocation Message received from the served user (user A) REFER FACILITY→ Facility information element EctExecute invoke component or ExplicitEctExecute invoke component The request URI shall contain the SIP URI of the transferee as received in the Contact header field. The Refer-To header field shall indicate the public address of the transfer Target. A Replaces header field parameter shall be added to the Refer-To URI together with a Require=replaces header field parameter. Method=INVITE. The ECT procedures are performed by the Application Server and described in ETSI TS 183 029 [36] as a network provider option. The REFER may be interworked in a reINVITE to the Transferee and to the Transfer target. These special REFER handling procedures are described in the ETSI TS 183 028 [32]. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 74
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.7.1.2 T reference point
|
5.2.7.1.2.1 Service invocation Receipt of a notification from the access: Table 5.2.7.1.2.1-1: Receipt of a notification from the access Message received from the access Message sent to the network FACILITY→ Facility information element REFER → EctInform invoke component Alerting No mapping FACILITY→ Facility information element EctInform invoke component active redirectionNumber (see note) The request URI shall contain the SIP URI of the transferee as received in the Contact header field. The Refer-To header field shall indicate the public address of the transfer Target. A Replaces header field parameter shall be added to the Refer-To URI together with a Require=replaces header field parameter. Method=INVITE. Facility information element (see note) SubaddressTransfer invoke component No mapping NOTE: The Access transport parameter is not interworked sent if the SubaddressTransfer invoke component is received. The ECT procedures are performed by the Application Server and described in ETSI TS 183 029 [36] as a network provider option. The REFER may be interworked in a reINVITE to the Transferee and to the Transfer target. These special REFER handling procedures are described in the ETSI TS 183 028 [32].
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.7.2 Actions at the incoming AGCF/VGW
| |
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.7.2.0 General information regarding the service
|
For this service, the separation "outgoing call" and "incoming call" does not apply. This clause describes the interworking at the O/I-AGCF/VGW (i.e. the AGCF/VGW where the remote user(s) is(are) connected to).
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.7.2.1 Coincident S and T reference point
|
5.2.7.2.1.1 Messages received from the network 5.2.7.2.1.1.1 Receipt of an INVITE/UPDATE message The ECT simulation service is performed as described in ETSI TS 183 029 [36] with the additions and clarifications described in ETSI TS 183 028 [32] in special REFER handling procedures. Upon receipt of an INVITE or UPDATE: a) reINVITE the corresponding remote ECT user is in alerting state NOTE 1: This interworking is applicable to the user in "active call state, call held auxiliary state" when the corresponding remote ECT user is in alerting state. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 75 Table 5.2.7.2.1.1.1-1: INVITE/UPDATE Message received from the network INVITE → No mapping No mapping NOTE: This can only occur in case of interaction of ECT with ECT. b) reINVITE the corresponding remote ECT user is in answered state NOTE 2: This interworking is applicable to the user in "active call state, call held auxiliary state" or "active call state, idle auxiliary state" or "call delivered state" when the corresponding remote ECT user is in answered state. Table 5.2.7.2.1.1.1-2: INVITE/UPDATE INVITE → INVITE P-Asserted-Identity Privacy absent or not "id" Connected Subaddress information element as isub parameter in the P-Asserted-Identity No mapping Other cases (see note 2) No mapping NOTE 1: This can only occur in case of interaction of ECT with ECT. NOTE 2: Other cases: - no subaddress in the reINVITE; or - Privacy header value "id"; or - no P-Asserted-Identity in the reINVITE. Table 5.2.7.2.1.1.1-3: INVITE/UPDATE INVITE/UPDATE not completing a Call transfer, alerting notification INVITE/UPDATE → P-Asserted-Identity (see note 2) No mapping No mapping NOTE 1: This can only occur in case of interaction of ECT with ECT. NOTE 2: The P-Asserted-Identity may be absent. 5.2.7.2.1.1.2 Receipt of an UPDATE message for a call in alerting phase This clause applies only for a call in alerting phase. One case is possible: • UPDATE. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 76 Upon receipt of such a message, one case is possible: Table 5.2.7.2.1.1.2-1: UPDATE UPDATE → P-Asserted-Identity, Privacy header absent or not "id". Connected Subaddress information element as isub parameter in the P-Asserted-Identity No mapping Other cases (see note 2) No mapping NOTE 1: This can only occur in case of interaction of ECT with ECT. NOTE 2: Other cases: - no subaddress in the UPDATE; or - Privacy header value "id"; or - no P-Asserted-Identity present in the UPDATE. Table 5.2.7.2.1.1.2-2: UPDATE UPDATE not completing a call-transfer-alerting notification UPDATE→ P-Asserted-Identity No mapping
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.7.2.2 T reference point
|
5.2.7.2.2.1 Service invocation: Messages received from the network 5.2.7.2.2.1.1 Receipt of an INVITE/UPDATE Upon receipt of an INVITE or UPDATE, two cases are possible: a) INVITE the corresponding remote ECT user is in alerting state NOTE 1: This interworking is applicable to the user in "active call state, call held auxiliary state" when the corresponding remote ECT user is in alerting state. b) INVITE the corresponding remote ECT user is in answered state NOTE 2: This interworking is applicable to the user in "active call state, call held auxiliary state" or "active call state, idle auxiliary state" or "call delivered state" when the corresponding remote ECT user is in answered state. Table 5.2.7.2.2.1.1-1: INVITE/UPDATE INVITE/UPDATE → P-Asserted-Identity Privacy header absent or value is not "id" Connected Subaddress information element as isub parameter in the P-Asserted-Identity No mapping Other cases (see note) No mapping NOTE: Other cases: - no subaddress in the reINVITE; or - Privacy header value "id"; or - no P-Asserted-Identity present in the reINVITE. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 77 5.2.7.2.2.1.2 Receipt of an UPDATE for a call in alerting phase One case is possible: • UPDATE. Table 5.2.7.2.2.1.2-1: UPDATE UPDATE→ P-Asserted-Identity, Privacy header absent or value not "id" Connected Subaddress information element as isub parameter in the P-Asserted-Identity No mapping Other cases (see note) No mapping NOTE: Other cases: - No subaddress in the UPDATE; or - Privacy header value "id"; or - No P-Asserted-Identity present in the UPDATE.
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.8 Subaddressing (SUB)
| |
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.8.0 General information regarding the service
|
The Sub-address (SUB) service allows the called (served) user to expand the addressing capacity beyond the one given by the E.164 user number. Subaddressing (SUB). The coding rules according IETF RFC 3966 [47] are not supporting the Type of subaddress (NSAP and user specified) as defined in ISDN (Recommendation ITU-T Q.931 [54]). Only the NSAP Type is mapped. Type of subaddress user specified is defined in ETSI TS 129 163 [1] onwards from the version V15.8. The called party subaddress information element received from the access in the SETUP message is transported in the in the isub parameter of the To header of the INVITE (see IETF RFC 3966 [47]).
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.8.1 Actions at the Outgoing AGCF/VGW
|
Table 5.2.8.1-1: SIP Header information for subaddressing mapping at the I-AGCF/VGW contained in the INVITE SETUP→ INVITE→ Called party sub-address To header Source component value Type of subaddress Octet 4 AFI Source SIP header field and component Derived value of parameter field NSAP 000 AFI x50 IA5 To header isub parameter ";isub=" 1*uric and "isub- encoding=nsap-ia5" NSAP 000 AFI x48 BCD ";isub=" 1*uric and "isub- encoding=nsap-bcd" NSAP 000 No AFI ";isub=" 1*uric and "isub- encoding=nsap" "User Specified" 010 ";isub=" 1*uric and "isub- encoding=user-specified" ETSI ETSI TS 183 036 V3.7.1 (2021-02) 78 Table 5.2.8.1-2: SIP Header information for subaddressing mapping at the I-AGCF contained in the 200 OK INVITE CONNECT 200 OK ISDN Parameter Connected party subaddress SIP Parameter P-Asserted-Identity header Source component value Type of subaddress Octet 4 AFI Source SIP header field and component Derived value of parameter field NSAP 000 AFI x50 IA5 P-Asserted-Identity header including the isub parameter ";isub=" 1*uric and "isub- encoding=nsap-ia5" NSAP 000 AFI x48 BCD ";isub=" 1*uric and "isub- encoding=nsap-bcd" NSAP 000 No AFI ";isub=" 1*uric and "isub- encoding=nsap" "User Specified" 010 ";isub=" 1*uric and "isub- encoding=user-specified"
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.8.2 Actions at the incoming AGCF/VGW
|
The called party subaddress information element received in the isub parameter of the To header of the INVITE (see IETF RFC 3966 [47]) is transferred transparently in the SETUP message. The number type value is a network option, NSAP is recommended. Table 5.2.8.2-1: Sending of the called party subaddress (SUB) SETUP INVITE Called party subaddress To header isub parameter Source component value Type of subaddress Octet 4 AFI Source SIP header field and component Derived value of parameter field NSAP 000 AFI x50 IA5 To header isub parameter ";isub=" 1*uric and "isub- encoding=nsap-ia5" NSAP 000 AFI x48 BCD ";isub=" 1*uric and "isub- encoding=nsap-bcd" NSAP 000 No AFI ";isub=" 1*uric and "isub- encoding=nsap" "User Specified" 010 ";isub=" 1*uric and "isub- encoding=user-specified" Table 5.2.8.2-2: Sending of the calling party subaddress (SUB) SETUP INVITE Calling party subaddress VGW (Gm Interface) From header isub parameter Source component value Type of subaddress Octet 4 AFI Source SIP header field and component Derived value of parameter field NSAP 000 AFI x50 IA5 To header isub parameter ";isub=" 1*uric and "isub- encoding=nsap-ia5" NSAP 000 AFI x48 BCD ";isub=" 1*uric and "isub- encoding=nsap-bcd" NSAP 000 No AFI ";isub=" 1*uric and "isub- encoding=nsap" "User Specified" 010 ";isub=" 1*uric and "isub- encoding=user-specified" AGCF (Mw Interface) P-Asserted-Identity header isub parameter NSAP 000 AFI x50 IA5 To header isub parameter ";isub=" 1*uric and "isub- encoding=nsap-ia5" NSAP 000 AFI x48 BCD ";isub=" 1*uric and "isub- encoding=nsap-bcd" NSAP 000 No AFI ";isub=" 1*uric and "isub- encoding=nsap" "User Specified" 010 ";isub=" 1*uric and "isub- encoding=user-specified" ETSI ETSI TS 183 036 V3.7.1 (2021-02) 79 Table 5.2.8.2-3: receiving of the connected subaddress (SUB) CONNECT 200 OK ISDN Parameter Connected party subaddress information element AGCF (Mw Interface) P-Asserted-Identity isub parameter Source component value Type of subaddress Octet 4 AFI Source SIP header field and component Derived value of parameter field NSAP 000 AFI x50 IA5 P-Asserted-Identity header including the isub parameter ";isub=" 1*uric and "isub- encoding=nsap-ia5" NSAP 000 AFI x48 BCD ";isub=" 1*uric and "isub- encoding=nsap-bcd" NSAP 000 No AFI ";isub=" 1*uric and "isub- encoding=nsap" "User Specified" 010 ";isub=" 1*uric and "isub- encoding=user-specified"
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.9 Closed User Group (CUG)
| |
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.9.0 General information regarding the service
|
An XML element containing the identification of the closed user group transferred in the INVITE between two AS is described in ETSI TS 124 654 [62].
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.9.1 Actions at the Outgoing AGCF/VGW
|
CUG checks at the originating Application Server and determination of the type of call request in correlation with the CUG information received from the calling user in the SETUP message and the CUG attributes of the calling user are described in table 4 of ETSI EN 300 138-1 [21] or for IMS implementations ETSI TS 124 654 [62]. Invocation of Closed User Group Table 5.2.9.1-1: Invocation of Closed User Group SETUP→ INVITE→ Facility CUGCallOperation invoke XML cug cugCallOperation OARerequested outgoingAccessRequest CUGIndex cugIndex NOTE: In case of OARerequested is missing, AGCF may include in the xml an outgoingAccessRequest=FALSE element. A rejection indication may be received in a 500 Server Internal Error. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 80 Table 5.2.9.1-2: Receipt of a rejection indication ←DISCONNECT ← Final Response Cause information element Return error component Response code Implicit request: Cause value No. 29 Facility rejected No return error component Explicit request: 603 Cause value No. 29 Facility rejected Return error value #19 incomingCallsBarredWithinCUG Implicit request or not CUG request: Cause value No. 87 User not member of CUG No return error component Explicit request: 403 Cause value No. 29 Facility rejected Return error value #20 userNotMemberOfCUG Implicit request: Normal handling of the cause value See clause 5.1 No return error component Explicit request: Other Response code Normal handling of the cause value See clause 5.1 Return error value #8 basicServiceNotProvided NOTE 1: This table provides examples of mapping. Another example of mapping is described in ETSI EN 300 138-1 [21], annex C. NOTE 2: In the case when a reason header with a Return error value is received from the application server (in the case of support ETSI TS 124 654 [62]), the reason header from the AS shall be sent to the calling user. If there is no reason header was sent, the mapping in this table should apply.
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.9.2 Actions at the incoming AGCF/VGW
|
CUG checks at the destination Application Server and determination of the type of call request in correlation with the CUG information received in the Initial INVITE message and the CUG attributes of the called user are described in ETSI TS 124 654 [62]. The mapping of the CUG information in the call setup sent to the CUG terminating user is subscription dependent. The mapping for AGCF is described in table 5.2.9.2-1. The mapping for VGW does not contain any CUG information. Table 5.2.9.2-1: Invocation of Closed User Group INVITE→ SETUP→ XML cug Facility CUGCallOperation invoke outgoingAccessRequest OARerequested cugIndex CUGIndex
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.10 User to User Service (UUS)
| |
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.10.0 General information regarding the service
|
The coding of the User-user information element is described within ETSI EN 300 286-1 [38]. The User-to-User header is defined within draft-johnston- sipping-cc-uui-02.txt [i.1]. The content of the uuidata field of the User-to-User header shall start with the first octet being the protocol discriminator and followed by the user information octets. The format of the uuidata field shall be the hexadecimal representation of binary data coded in ascii alphanumeric characters. For example, the 8- bit binary value 0011 - 1111 is 3F in hexadecimal. To code this in ascii, one 8- bit byte containing the ascii code for the character '3' (0011 - 0011 or 033H) and one 8- bit byte containing the ascii code for the character 'F' (0100 - 0110 or 046H) are required. For each byte value, the high-order hexadecimal digit is always the first digit of the pair of hexadecimal digits. The ascii letters used for the hex digits shall always be capital form. EXAMPLE: User-to-User: 04C81031313232333334343535363637373838FA08303900064630E9E0; encoding=hex. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 81 Interworking procedures between the User-user information element and User-to-User header are defined in the following clauses.
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.10.1 Actions at the Outgoing AGCF/VGW
| |
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.10.1.1 Service 1 (UUS1) implicit
|
Service 1 may be requested implicitly by the presence of the user-user information element in the SETUP message which is mapped into the user-to-user information parameter of the initial INVITE. Table 5.2.10.1.1-1: Implicit UUS1 transfer DSS 1 messages SIP messages SETUP→ INVITE→ User-user information element Protocol discriminator and User Information User-to-User header uuidata PROGRESS, ALERTING, CONNECT, DISCONNECT ← 18x, 200 OK, BYE ← User-user information element Protocol discriminator and User Information User-to-User header uuidata DISCONNECT, RELEASE, RELEASE COMPLETE → BYE → User-user information element Protocol discriminator and User Information User-to-User header uuidata
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.10.1.2 Service 1 (UUS1) explicit
|
Table 5.2.10.1.2-1: Explicit UUS1 invocation SETUP→ Content Facility information element UserUserService invoke component Service 1 preferred User-user information element Facility information element UserUserService invoke component Service 1 required User-user information element A service 1 explicit request preferred or required is rejected as described below. Service 1 rejection Rejection initiated by the O-AGCF/VGW when it cannot support the service is not relevant to the interworking and is described in clause 9.1.1.2.2 of ETSI EN 300 286-1 [38]. Table 5.2.10.1.2-2 describes the handling of a rejection indication received from the network when the service 1 was requested as required. Table 5.2.10.1.2-3 describes the handling of a rejection indication received from the network when the service 1 was requested as preferred. Table 5.2.10.1.2-2: Service 1 rejection service requested as "required" DSS1 messages SIP messages ←DISCONNECT Cause information element Value 69 (requested facility not implemented Facility information element UserUserService return error component rejectedByNetwork ETSI ETSI TS 183 036 V3.7.1 (2021-02) 82 Table 5.2.10.1.2-3: UUS1 rejection: service requested as "preferred" DSS 1 messages SIP messages CALL PROCEEDING, ALERTING, PROGRESS, CONNECT, DISCONNECT or RELEASE ← Facility information element UserUserService return error component rejectedByNetwork NOTE: UUS return error component shall be sent in next regular message.
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.10.1.3 Service 2
|
Table 5.2.10.1.3-1: UUS2 invocation SETUP→ SIP messages Content Facility information element UserUserService invoke component Service 2 preferred Facility information element UserUserService invoke component Service 2 required A service 2 is rejected as described below: Service 2 rejection Rejection initiated by the O-AGCF/VGW when it cannot support the service is not relevant to the interworking and is described in clause 9.2.1.2 of ETSI EN 300 286-1 [38]. Table 5.2.10.1.3-2 describes the handling of a rejection indication received from the network when the service 2 was requested as required. Table 5.2.10.1.3-3 describes the handling of a rejection indication received from the network when the service 2 was requested as preferred. Table 5.2.10.1.3-2: UUS2 rejection: service requested as "required" DSS1 messages SIP messages ←DISCONNECT Cause information element Value 69 (requested facility not implemented) Facility information element UserUserService return error component rejectedByNetwork Table 5.2.10.1.3-3: UUS2 rejection: service requested as "preferred" DSS 1 messages SIP messages ←ALERTING, DISCONNECT Facility information element UserUserService return error component rejectedByNetwork ETSI ETSI TS 183 036 V3.7.1 (2021-02) 83
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.10.1.4 Service 3
|
Table 5.2.10.1.4-1: UUS3 invocation SETUP→ SIP messages Content Facility information element UserUserService invoke component Service 3 preferred Facility information element UserUserService invoke component Service 3 required A service 3 request during call setup is rejected as described below. Table 5.2.10.1.4-2: UUS3 activation received from the calling user in active phase FACILITY→ SIP messages Facility information element UserUserService invoke component Service 3 preferred Service 3 rejection Rejection initiated by the O-AGCF/VGW when it cannot support the service is not relevant to the interworking and is described in clause 9.3.1.1.2 of ETSI EN 300 286-1 [38]. Rejection of service 3 requested during call establishment. Table 5.2.10.1.4-3 describes the handling of a rejection indication received from the network when the service 3 was requested as required. Table 5.2.10.1.4-4 describes the handling of a rejection indication received from the network when the service 3 was requested as preferred. Table 5.2.10.1.4-3: UUS3 rejection: service requested as "required" during call establishment DSS1 messages SIP messages ←DISCONNECT Cause information element Value 69 (requested facility not implemented) Facility information element UserUserService return error component rejectedByNetwork Table 5.2.10.1.4-4: UUS3 rejection: service requested as "preferred" during call establishment DSS 1 messages SIP messages ←CONNECT, DISCONNECT Facility information element UserUserService return error component rejectedByNetwork ETSI ETSI TS 183 036 V3.7.1 (2021-02) 84 Rejection of service 3 requested after call establishment Rejection of service 3 requested after call establishment is not relevant to the interworking and is described in clause 9.3.1.2.2 of ETSI EN 300 286-1 [38]. Table 5.2.10.1.4-5: Rejection of UUS3 requested by the calling user after call establishment DSS 1 messages SIP messages ←FACILITY Facility information element UserUserService return error component rejectedByNetwork
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.10.2 Actions at the incoming AGCF/VGW
| |
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.10.2.1 Service 1 (UUS1) implicit
|
Service 1 may be requested implicitly by the presence of the User-to-User header field of the Initial INVITE which is mapped into the user-user information element in the SETUP message. If service 1 is requested: Table 5.2.10.2.1-1: Implicit UUS1 transfer SIP messages DSS 1 messages INVITE→ SETUP→ User-to-User header uuidata User-user information element Protocol discriminator and User Information 18x, 200 OK, BYE (see note) ← ALERTING, CONNECT, DISCONNECT, RELEASE, RELEASE COMPLETE ← User-to-User header uuidata User-user information element Protocol discriminator and User Information BYE → DISCONNECT → User-to-User header uuidata User-user information element Protocol discriminator and User Information NOTE: The correspondences between SIP and DSS 1 messages are described in clause 5.1.1. If there is no user-user information element in the SETUP message, the Application Server shall discard the User-to- User header field possibly received afterwards from the user or from the SIP side.
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.11 Call Waiting (CW)
| |
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.11.1 Actions at the Outgoing AGCF/VGW
|
Table 5.2.11.1-1: Mapping of 18x provisional responses for CW procedure in ISDN access ←ALERTING/PROGRESS/NOTIFY (see note) ←18x Notification indicator information element Alert-Info: <urn:alert:service:call-waiting> Notification description 110 0000 Call is a waiting call NOTE: The criteria of sending of ALERTING or PROGRESS is defined in clause 5.1. If neither ALERTING or PROGRESS has to be sent, a NOTIFY message is sent. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 85
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.11.2 Actions at the incoming AGCF/VGW
| |
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.11.2.1 Procedure at coincident S and T reference point
|
CW indication indicates the call waiting service is activated against the user. AGCF/VGW uses this CW indication in conjunction with the B-channel busy condition, and if both apply, AGCF/VGW shall send SETUP with "no channel" in the information channel selection field of the Channel identification information element. If B-channel busy condition is not met, AGCF/VGW should ignore the CW indication and send SETUP according to clause 5.1.2.1. If CW indication is not present, and B-Channel busy is detected, AGCF/VGW should reject the call with 486 (Busy Here). If CW indication is not present, and B-Channel busy is detected, AGCF/VGW should reject the call with 486 (Busy Here) or AGCF/VGW shall send SETUP with "no channel" in the information channel selection field of the Channel identification information element as a network option. Table 5.2.11.2.1-1: Receipt of CW indication INVITE→ SETUP→ Channel identification information element information channel selection Content-Type: application/3gpp-ims+xml Content_Disposition: 3gpp-alternative-service MIME XML ims-3gpp version="1" alternative-service action call-waiting-indication No channel If the call is presented with indication no channel in the information channel selection field of the channel identification information element in the SETUP message, and depending on the subscription options offered by the network, a notification is contained in the Alert-Info header sent in the network upon receipt of the alerting message. Table 5.2.11.2.1-2: Sending of CW notification ←180 ←ALERTING Alert-Info: <urn:alert:service:call-waiting>
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.11.2.2 Notification received at T reference point
|
A CW notification may be received at T reference point in the ALERTING message. Table 5.2.11.2.2-1: Receipt of a CW notification from a private network ←18x (see note) ←ALERTING/PROGRESS/NOTIFY Notification indicator information element Notification description Alert-Info: <urn:alert:service:call-waiting> 110 0000 Call is a waiting call NOTE: In case of receipt of ALERTING or PROGRESS, 180 or 183 is sent as described in clause 5.1.2.2. In case of receipt of NOTIFY, 183 is sent. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 86
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.12 Terminal Portability (TP)
| |
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.12.1 Actions at the outgoing AGCF/VGW
| |
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.12.1.1 Invocation at coincident S and T reference point
|
Table 5.2.12.1.1-1: TP invocation Message received from the DSS 1→ INVITE/UPDATE→ SUSPEND SDP: a=sendonly RESUME SDP: a=sendrecv The action taken on the access side upon receipt of SUSPEND and RESUME messages are described in clause 5.6 and figure A.6 of Recommendation ITU-T Q.931 [54]. Upon the T307 expiry, a Release message (BYE or CANCEL) is sent with the cause value No. 102, recovery on timer expiry. No action is taken on the DSS 1 side.
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.12.1.2 Notification received at T reference point
|
A TP notification may be received at T reference point from a point-to-point data link in the active phase of the call. Table 5.2.12.1.2-1: Receipt of a TP notification from a private network NOTIFY→ INVITE/UPDATE→ Notification indicator information element Notification description 000 0000 User suspended SDP: a=sendonly 000 0001 User resumed SDP: a=sendrecv
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.12.2 Actions at the incoming AGCF/VGW
| |
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.12.2.1 Invocation at coincident S and T reference point
|
Table 5.2.12.2.1-1: TP invocation ←INVITE /UPDATE ←Message received from the DSS 1 SDP: a=sendonly SUSPEND SDP: a=sendrecv RESUME The actions taken on the access side upon receipt of the SUSPEND and RESUME messages are described in clause 5.2.6 and figure A.6 of Recommendation ITU-T Q.931 [54]. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 87
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.12.2.2 Notification received at T reference point
|
A TP notification may be received at T reference point in the active phase of the call. Table 5.2.12.2.2-1: Receipt of a TP notification from a private network ←INVITE/UPDATE ←NOTIFY Notification indicator information element Notification description SDP: a=sendonly 000 0000 User suspended SDP: a=sendrecv 000 0001 User resumed
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.13 Three-party (3PTY)
| |
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.13.0 General information regarding the service
|
Based on local policy, the AGCF may subscribe for the conference event package on behalf of the ISDN participant after being added to a three party. When the conference event package option is implemented, and one of the following events occurs at the AGCF/VGW: • a 200 OK is received as a response to an initial INVITE request originated by the AGCF/VGW, where the Contact header field contains an "isfocus" parameter; or • an ACK message is received which acknowledges a 200 OK response to the initial INVITE request, and the initial INVITE request is originated by the conferencing AS and contains an "isfocus" parameter in the Contact header field. Then the following steps shall be performed: 1) A SUBSCRIBE request shall be created according to IETF RFC 4575 [44]. 2) The request URI is set to the Contact address of the conferencing AS. 3) The P-Asserted-Identity header field, the From header field and the Privacy header field are set with the same value as: - the P-Asserted-Identity header field, the From header field and the Privacy header field in the initial INVITE request originated by the AGCFF/VGW; or - the P-Asserted-Identity header field, the To header field and the Privacy header field in a 1xx or 2xx response sent by the AGCF/VGW to the initial INVITE request from the conferencing AS. When a full type of notification is received a check is made of the content. If the changes with respect a previous version of the notification have not been sent on to the ISDN user for this session, the AGCF/VGW shall do a DSS1 interaction towards the ISDN user. If the changes with respect a previous version of the notification have been sent to the ISDN user for this session, the AGCF/VGW shall not do an DSS1 interaction towards the ISDN user. When a partial notification is received then it is assumed that a value of a received notification has changed, so the AGCF/VGW shall do an DSS1 interaction towards the ISDN user. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 88
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.13.1 Notification received from the network
|
Table 5.2.13.1-1: 3PTY notification ←NOTIFY ←INVITE Notification indicator information element <conference-info> Notification description <conference-state> 100 0010 Conference established <active>true< active/> 100 0011 Conference disconnected <active>false< active/> 111 1001 Remote hold SDP a=sendonly
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.13.2 Invocation at coincident S and T reference point
|
Before a three way conversation can be established, one of two existing sessions is set on hold by sending a reINVITE with an a attribute set to sendonly in the SDP. To invoke a three party communication after receipt of the Begin3PTY invoke component, the AGCF/VGW shall send an INVITE request with the conference factory URI for the three-way session towards the conference focus as described in ETSI TS 124 605 [9]. It is assumed, that based on an initial filter criterion, the conference AS is involved in the SIP signalling chain. It is assumed, that the conference application server is responsible for the notification "conference-established" etc. The previous basic call sessions are not released. Option A: 3PTY invoke by sending a REFER request to each participant. Table 5.2.13.2-1: Three-party (3PTY) invoke using the REFER request Procedure Message received from served user → Messages sent to the Conference AS or remote user → Beginning the 3PTY FACILITY→ Facility IE Begin3PTY-Inv Call reference IE Call reference of call A-B INVITE Request URI: <userCactive@domain.com> SDP: a=sendonly INVITE Request URI: conference factory URI REFER Request URI: conference factory URI Refer-to: <userBonHold@domain.com> Method=invite REFER Request URI: conference factory URI Refer-to: <userCactive@domain.com> Method=invite ETSI ETSI TS 183 036 V3.7.1 (2021-02) 89 Option B: 3PTY invoke by sending an INVITE request with the conference factory URI for the three-way session towards the conference focus including the participant list containing the two 3PTY participants. Table 5.2.13.2-2: Three-party (3PTY) invoke using the participant list in an INVITE request Procedure Message received from served user → Messages sent to the Conference AS or remote user → Beginning the 3PTY FACILITY→ Facility IE Begin3PTY-Inv Call reference IE Call reference of call A-B INVITE Request URI: <userCactive@domain.com> SDP: a=sendonly INVITE Request URI: conference factory URI To: CONF AS From: userA@domain.com Require: recipient-list-invite <?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="userBonHold@domain.com?Call-ID=1a& From=userA@domain.com%3Btag%3Da&To=B%3Btag%3 Db" cp:copyControl="to"/> <entry uri=userCactive@domain.com?Call-ID=2a& From=userA@domain.com%3Btag%3Da&To=C%3Btag%3 Dc cp:copyControl="to"/> </list> </resource-lists> > ETSI ETSI TS 183 036 V3.7.1 (2021-02) 90 Table 5.2.13.2-3: Three-party (3PTY) invoke Procedure Message received from served user → Messages sent to the Conference AS or remote user → End of three party FACILITY→ Facility IE End3PTY-Inv Call reference IE Call reference of call A-B INVITE Request URI: < userBonHold@domain.com> SDP: a=sendonly (see note) INVITE Request URI: <userCactive@domain.com> <conference-info> <conference-state> <active>false< active/> SDP: a=sendrecv (see note) BYE Request URI: conference factory URI Creation of a private communication with B HOLD→ Call reference IE Call reference of call A-C INVITE Request URI: <userCactive@domain.com> SDP: a=sendonly RETRIEVE→ Call reference IE Call reference of call A-B INVITE Request URI: < userBonHold@domain.com> <conference-info> <conference-state> <active>false< active/> SDP: a=sendrecv Creation of a private communication with C FACILITY→ Facility IE End3PTY-Inv Call reference IE Call reference of call A-C INVITE Request URI: < userBonHold@domain.com> <conference-info> <conference-state> <active>false< active/> SDP: a=sendonly INVITE Request URI: <userCactive@domain.com> <conference-info> <conference-state> <active>false< active/> SDP: a=sendrecv BYE Request URI: conference factory URI Disconnect the remote user B DISCONNECT→ Call reference IE Call reference of call A-B BYE Request URI: userBonHold@domain.com INVITE Request URI: <userCactive@domain.com> <conference-info> <conference-state> <active>false< active/> SDP: a=sendrecv BYE Request URI: conference factory URI Disconnect the remote user C DISCONNECT→ Call reference IE Call reference of call A-C BYE Request URI: userCactive@domain.com INVITE Request URI: < userBonHold@domain.com> SDP: a=sendonly BYE Request URI: conference factory URI RETRIEVE→ Call reference IE Call reference of call A-B INVITE Request URI: < userBonHold@domain.com> <conference-info> <conference-state> <active>false< active/> SDP: a=sendrecv NOTE: The a line attribute depends on the Call reference of the Facility with the End3PTY-Inv component. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 91 Table 5.2.13.2-4 describes the actions taken when user B or user C disconnects. Table 5.2.13.2-4: User B or user C disconnects Messages sent to or received from served user Call A-B: Active-held connection messages sent to B/AS or received from B Call A-C: Active-idle connection message sent to C/AS or received from C ←DISCONNECT Call reference IE Call reference of call A-B ←BYE Request URI <userA@domain.com> INVITE→ Request URI: <userCactive@domain.com> <conference-info> <conference-state> <active>false< active/> SDP: a=sendrecv BYE→ Request URI: conference factory URI ←DISCONNECT Call reference IE Call reference of call A-C INVITE→ Request URI: < userBonHold@domain.com> SDP: a=sendonly BYE→ Request URI: conference factory URI ←BYE Request URI <userA@domain.com> RETRIEVE→ Call reference IE Call reference of call A-B INVITE→ Request URI: < userBonHold@domain.com> <conference-info> <conference-state> <active>false< active/> SDP: a=sendrecv Not applicable
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.13.3 Notification received at T reference point
|
Table 5.2.13.3-1: Receipt of a 3PTY notification from a private network NOTIFY→ UPDATE/INVITE → Notification indicator information element <conference-info> Notification description <conference-state> 100 0010 Conference established <active>true< active/> 100 0011 Conference disconnected <active>false< active/> 111 1001 Remote hold SDP a=sendonly
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.13.4 Notification received at T reference point
|
Table 5.2.13.4-1: Receipt of a 3PTY notification from a private network ←INVITE/UPDATE ←NOTIFY <conference-info> Notification indicator information element <conference-state> Notification description <active>true< active/> 100 0010 Conference established <active>false< active/> 100 0011 Conference disconnected SDP a=sendonly 111 1001 Remote hold ETSI ETSI TS 183 036 V3.7.1 (2021-02) 92
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.14 Completion of Call to Busy Subscriber (CCBS)
| |
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.14.1 Actions at the outgoing AGCF/VGW
|
CCBS Invocation In case the terminating user is busy, a 183 Session Progress is received. The activation of the CCBS service is possible after the announcement is applied by the AS. The user provides the activation by performing in-band dialogue or by sending the proper service code via keypad protocol. The service code received in the Keypad Facility Information Element is used to construct the user part of the Request line of the INVITE request sent to the CCBS Application Server. These requirements are described in annex A of the present document. The result is available in-band (announcement). After the activation procedure was successful, a 486 is received and the connection is terminated according the procedures as described in clause 5.1.1.4. Starting CCBS recall Two procedures are applicable to perform the CCBS recall: 1) When the AGCF/VGW receives a REFER request and the Request-URI is set to the URI of the served user from the original communication, including a "m" SIP URI parameter with a value set to "BS" then a SETUP is sent to the DSS1 user equipment. If a DSS1 CONNECT message is received (the served user accepts the recall) then an INVITE request is sent and the Request URI is set equal to the URI received in the Refer-To header of the previous REFER. The DSS1 dialogue and the INVITE dialogue have to be associated. Table 5.2.14.1-1: Recall procedure by reception of REFER request ←SETUP ←REFER Request URI <served user>; m=BS Refer-To: <user B> 2) When the AGCF/VGW receives an INVITE request including a "m" SIP URI parameter with a value set to "BS", A SETUP is sent to the DSS1 user equipment. When a CONNECT is received, a 200 OK INVITE response is sent. This is the trigger for the AS to send an INVITE request to the monitored user. Table 5.2.14.1-2: Recall procedure by reception of INVITE request ←SETUP ←INVITE Request URI <served user>; m=BS Revocation of CCBS request A CCBS request can be cancelled using the keypad facility protocol. These requirements are described in annex A of the present document. The DSS1 connection and the SIP dialogue are terminated after the revocation was successful according normal DSS1 and SIP procedures. NOTE: All outstanding CCBS requests cancelled.
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.14.2 Actions at the incoming AGCF/VGW
|
No special requirements. Procedures as described in clause 5.1.2.1 apply. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 93
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.15 Completion of Calls on No Reply (CCNR)
| |
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.15.1 Actions at the outgoing AGCF/VGW
|
CCNR Invocation In case the terminating user is not busy, a 180 Ringing is received. The activation of the CCNR service is possible after the announcement is applied by the AS. The user provides the activation by performing in-band dialogue or by sending the proper service code via keypad protocol. The service code received in the Keypad Facility Information Element is used to construct the user part of the Request line of the INVITE request sent to the CCNR Application Server. These requirements are described in annex A of the present document. The result is available in-band (announcement). Starting CCNR recall Two procedures are applicable to perform the CCNR recall: 1) When the AGCF/VGW receives a REFER request and the Request-URI is set to the URI of the served user from the original communication, including a "m" SIP URI parameter with a value set to "NR" then a SETUP is sent to the DSS1 user equipment. If a DSS1 CONNECT message is received (the served user accepts the recall) then an INVITE request is sent and the Request URI is set equal to the URI received in the Refer-To header of the previous REFER. The DSS1 dialogue and the INVITE dialogue have to be associated. Table 5.2.15.1-1: Recall procedure by reception of REFER request ←SETUP ←REFER Request URI <served user>; m=NR Refer-To: <user B> 2) When the AGCF/VGW receives an INVITE request including a "m" SIP URI parameter with a value set to "NR", A SETUP is sent to the DSS1 user equipment. When a CONNECT is received, a 200 OK INVITE response is sent. This is the trigger for the AS to send an INVITE request to the monitored user. Table 5.2.15.1-2: Recall procedure by reception of INVITE request ←SETUP ←INVITE Request URI <served user>; m=NR Revocation of CCNR request A CCNR request can be cancelled by performing in-band dialogue or using the keypad facility protocol. These requirements are described in annex A of the present document. The DSS1 connection and the SIP dialogue are terminated after the revocation was successful according normal DSS1 and SIP procedures. NOTE: All outstanding CCNR requests are cancelled.
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.15.2 Actions at the incoming AGCF/VGW
|
No special requirements. Procedures as described in clause 5.1.2.1 apply. NOTE: Information received from the served user in the recall phase will not be transported to the terminating user. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 94
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.16 Advice Of Charge AOC
| |
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.16.0 General information regarding the service
|
As described in ETSI TS 183 047 [31], three AOC supplementary services exist: a) Charging information at communication set-up time (AOC-S): - The AOC-S service enables a user to receive information about the charging rates at communication set-uptime and also to receive further information during the communication if there is a change of charging rates. b) Charging information during the communication (AOC-D): - The AOC-D service enables a user to receive information on the recorded charges for a communication during the active phase of the communication. c) Charging information at the end of the communication (AOC-E): - The AOC-E service enables a user to receive information on the recorded charges for a communication when the communication is terminated.
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.16.1 Actions at the outgoing AGCF/VGW
|
Transfer of AOC-S charging information The AOC-S charging information is transported during the call establishment, during the call (change in rates). During the call establishment, the AOC-S information shall be carried in SIP 1xx provisional response or a 200 OK response to an INVITE message, in a MIME body type "application/vnd.etsi.aoc+xml" defined in ETSI TS 183 047 [31]. It is mapped to a Facility information element in a DSS1 ALERTING, CALL PROCEEDING, PROGRESS, or CONNECT message. During the call, the AOC-S information shall be carried in a SIP INFO message in a MIME body type "application/vnd.etsi.aoc+xml" defined in ETSI TS 183 047 [31]. It is mapped to a Facility information element in a DSS1 FACILITY message. Table 5.2.16.1-1: Transport of AOC-S SIP messages→ 1xx, 200 OK (INVITE), INFO DSS1 messages→ ALERTING, CALL PROCEEDING, PROGRESS, CONNECT, FACILITY MIME body type "application/vnd.etsi.aoc+xml" aoc aoc-s Facility Information Element ChargingRequest chargingInformationAtCallSetup NOTE: The feature "the served user is the terminating user" does not exist for the ISDN, because of this mapping from the INVITE request to a SETUP message is not possible. Transfer of AOC-D charging information The AOC-D charging information is transported during the call. The AOC-D information shall be carried in a SIP INFO message in a MIME body type "application/vnd.etsi.aoc+xml" defined in ETSI TS 183 047 [31]. It is mapped to a Facility information element in a DSS1 FACILITY message. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 95 Table 5.2.16.1-2: Transport of AOC-D SIP messages→ INFO DSS1 messages→ FACILITY MIME body type "application/vnd.etsi.aoc+xml" aoc aoc-d Facility Information Element ChargingRequest chargingDuringACall Transfer of AOC-E charging information The AOC-E charging information is transported during the call clearing. The AOC-E information shall be carried in a SIP 200 OK response to a BYE message (if the party that has subscribed to the AOC-E service clears the call) or in a SIP BYE message (if the party that has subscribed to the AOC-E service receives the release of the call), in a MIME body type "application/vnd.etsi.aoc+xml" defined in ETSI TS 183 047 [31]. It is mapped to a Facility information element in a DSS1 DISCONNECT, RELEASE, RELEASE COMPLETE message. Table 5.2.16.1-3: Transport of AOC-E SIP messages→ BYE, 200 OK (BYE) DSS1 messages→ DISCONNECT, RELEASE, RELEASE COMPLETE MIME body type "application/vnd.etsi.aoc+xml" aoc aoc-e Facility Information Element ChargingRequest chargingAtTheEndOfACall When processing originating sessions with multiple call legs to be charged, e.g. in 3-party calls or when using the conference service, then the Application server shall send charging information separately for each call leg to the AGCF/VGW. As an alternative dependent on the setting of a network operator option the Application server may send charging information related to the affected call legs in one single AOC xml body in a combined representation. As a consequence the AGCF/VGW in accordance with the Application server shall process charging information received from the Application Server in one of the following manners: • The AGCF/VGW shall be able to process bodies with AOC information which are separately received for the different call legs. • As a network operator option the charging information received may be assumed as a combined representation applying to all call legs. If only one dialog exists between the AGCF/VGW and the AS, the AGCF/VGW is not informed when one of the far parties is released. In order to ensure that charging is accurate, the AS will have to send an INFO request with an XML body each time a far party is added or released, regardless of whether AOC-S, AOC-D, or AOC-E has been chosen as the desired reporting technique.
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.17 Message Waiting Indication (MWI)
|
Upon receipt of a NOTIFY request containing the following headers: • Event: message-summary. • Subscription-State: active. • Content-Type: application/simple-message-summary. • Messages-Waiting: yes. A DSS1 FACILITY message is sent to the DSS1 user equipment. The mapping of the Facility I.E is described in table 5.2.17-1. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 96 Table 5.2.17-1: Mapping of NOTIFY into DSS1 FACILITY NOTIFY→ FACILITY→ Event: message-summary Subscription-State: active Content-Type: application/simple-message-summary Messages-Waiting: yes Facility Information Element: MWIIndicate invoke Message-Account: controllingUserProvidedNr [msg-summary-line] Voice-Message: new/old Fax-Message: new/old Video-Message: new/old (see note) basicService speech telefaxGroup2-3 videotelephony [msg-summary-line] Voice-Message: new/old Fax-Message: new/old Video-Message: new/old (see note) basicService speech telefaxGroup2-3 videotelephony NOTE: All other Internet Message Content Types are not able to map into the basic service. However an ISDN terminal does not have the capability to receive these types. Upon receipt of a NOTIFY request a 200 OK (NOTIFY) is send according normal SIP procedures.
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.3 DSS1 layer 2 failure
|
5.3.1 DSS 1 data link reset and data link failure procedures in the outgoing AGCF/VGW The data link reset and data link failure procedures are respectively described in clauses 5.2.8.8 and 5.2.8.9 of Recommendation ITU-T Q.931 [54]. Table 5.3.1-1: DSS 1 data link reset and data link failure procedures ←DISCONNECT Trigger event BYE/CANCEL→ Cause information element (see note 2) Reason header Cause value No. 41 (temporary failure) Data link reset in overlap sending state Cause value No. 41 (temporary failure) (see note 1) Data link failure in another state than active state Cause value No. 27 (destination out of order) (see note 1) Failure of the data link reestablishment procedure after a data link failure in active state Cause value No. 27 (destination out of order) NOTE 1: The call is cleared internally. No DISCONNECT message is sent on the access. NOTE 2: The location is coded '1010' network beyond interworking point. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 97 5.3.2 DSS 1 data link reset and data link failure procedures in the incoming AGCF/VGW The data link reset and data link failure procedures are respectively described in clauses 5.8.8 and 5.8.9 in Recommendation ITU-T Q.931 [54]. Table 5.3.2-1: DSS 1 Data link reset and Data link failure procedures ←BYE/4xx/5xx Trigger event DISCONNECT→ Reason header Cause information element (see note 2) cause No. 41 (temporary failure) Data link reset in overlap receiving state Cause value No. 41 (temporary failure) cause No. 27 (destination out of order) Data link failure in another state than active state (see note 1) cause No. 27 (destination out of order) Failure of the data link reestablishment procedure after a data link failure in active state (see note 1) NOTE 1: The call is cleared internally. No DISCONNECT message is sent on the access. NOTE 2: The location is coded '1010' network beyond interworking point.
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.3.3 Release by the outgoing AGCF/VGW
|
Table 5.3.3-1: Release from the originating AGCF/VGW ←DISCONNECT Trigger event BYE/CANCEL→ Cause information element (see note 3) Reason header Cause value No. 28 Invalid number format (address incomplete) Determination that the called number information received is incomplete, after an INVITE message has already been sent Cause value No. 28 Invalid number format (address incomplete) Same cause value as in the REL message (see note 1) Other cases of failure on the SIP side Cause value coded according to ETSI EN 300 899-1 [2] Cause value coded according to ETSI EN 300 899-1 [2] Other cases of failure on the DSS 1 side Same cause value as in the DISCONNECT message (see note 2) NOTE 1: If the cause value sent in the BYE/CANCEL message is unknown in DSS 1, the unspecified cause value of the class is sent. NOTE 2: If the cause value sent in the DISCONNECT message is unknown in SIP, the unspecified cause value of the class is sent. NOTE 3: The location is coded '1010' network beyond interworking point. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 98
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.3.4 Release by the AGCF/VGW
|
Table 5.3.4-1: Release from the terminating AGCF/VGW ←Message sent to the SIP Trigger event Message sent to the DSS 1→ (see note 3) Point-to-point data link Broadcast data link 480 Cause value No. 18 No user responding No response to the SETUP message (T303 expiry) DISCONNECT Cause value No. 102 Recovery on timer expiry No action 480 Cause value No. 18 No user responding No ALERTING, CONNECT or DISCONNECT after CALL PROCEEDING (T310 expiry) DISCONNECT Cause value No. 102 Recovery on timer expiry RELEASE Cause value No. 102 Recovery on timer expiry 480 Cause value No. 19 No answer from user (user alerted) No CONNECT or DISCONNECT after ALERTING (T301 expiry) DISCONNECT Cause value No. 102 Recovery on timer expiry RELEASE Cause value No. 102 Recovery on timer expiry 480 Cause value No. 31 Normal, unspecified Unsuccessful termination of the B-channel selection procedure RELEASE Cause 6 Channel unacceptable 500 Cause value coded according to ETSI EN 300 899-1 [2] Other cases of failure on the SIP side DISCONNECT Same cause value as in the REL message (see note 1) 500 Same cause value as in the DISCONNECT message (see note 2) other cases of failure on the DSS 1 side DISCONNECT Cause value coded according to ETSI EN 300 899-1 [2] NOTE 1: If the cause value sent in the 480/500 message is unknown in DSS 1, the unspecified cause value of the class is sent. NOTE 2: If the cause value sent in the DISCONNECT message is unknown in SIP, the unspecified cause value of the class is sent. NOTE 3: The location is coded '1010' network beyond interworking point.
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.4 Service operation
| |
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.4.1 Call related service operation
| |
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.4.1.1 Malicious Call Identification (MCID)
|
The invocation of Malicious Call Identification is described in clause 5.2.6. When a 200 OK INVITE is received as the final response to the reINVITE containing the MCID request, a mCIDRequest return result component is sent to the served user equipment. If an unsuccessful final response is received, a mCIDRequest return error component error code "notAvailable" is sent the user equipment. NOTE: A more accurate mapping between unsuccessful final responses and ISDN operation errors is for further study. The coding of the FACILITY message and the Facility I.E is described in ETSI EN 300 130-1 [20].
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.4.1.2 Explicit Communication Transfer (ECT)
|
The mapping of Explicit Communication Transfer related Facility components is described in clause 5.2.7. When a 202 Accepted is received, and the NOTIFY message/sipfrag part for both communications indicates the successful communication between Transfer target and Transferee, an eCTExecute return result component is sent to the served user equipment in the DISCONNECT messages. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 99 If an unsuccessful final response was received upon the REFER was sent, an eCTExecute return error component value "notAvailable" is sent to the served user equipment. NOTE: A more accurate mapping between unsuccessful final responses and ISDN operation errors is for further study. The coding of the FACILITY message and the Facility I.E is described in ETSI EN 300 369-1 [35].
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.4.1.3 Closed User Group (CUG)
|
The mapping of the CUG request and the handling of unsuccessful final responses is described in clause 5.2.9.
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.4.1.4 Three Party Service (3PTY)
|
The mapping of Three Party Service related Facility components is described in clause 5.2.13. When for the INVITE sent to the conference focus to get a "conference URI" the 200 OK is received and the 202 Accepted for both REFER sent to the remote participants is received, a Begin3PTY return result component is sent to the served user equipment. If an unsuccessful final response was received upon the INVITE to get the "conference URI" was sent, a Begin3PTY return error component value "notAvailable" is sent to the served user equipment. If an unsuccessful final response was received upon the REFER to establish the conference was sent, a Begin3PTY return error component value "notAvailable" is sent to the served user equipment. NOTE: A more accurate mapping between unsuccessful final responses and ISDN operation errors is for further study. The coding of the FACILITY message and the Facility I.E is described in ETSI EN 300 188-1 [24].
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.4.1.5 Completion of Call to Busy Subscriber (CCBS)
|
For further studies.
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.4.1.6 Completion of Calls on No Reply (CCNR)
|
For further studies.
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.4.2 Call independent service configuration
| |
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.4.2.0 General requirements
|
Call independent service can be achieved using either the Gm reference point or the Ut reference point. In case of the Gm reference point the MESSAGE method is used to convey the service related information to the relevant target. In general the information to configure a service is embedded in an XML instance document contained in the MESSAGE request. In the case of the Ut reference point, HTTP PUT, HTTP GET or HTTP DELETE requests are used in accordance with IETF RFC 4825 [48] and the supplementary services application usage specified in ETSI TS 183 023 [49]. The following clauses specify the mapping between the ROSE components embedded in DSS.1 FACILITY messages and the XML document to be created. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 100
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.4.2.1 Communication Diversion Services (CDIV)
| |
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.4.2.1.1 Communication Diversion activation
|
On receipt of a DSS1 FACILITY message containing the ActivationDiversion invoke component, a SIP MESSAGE request or a HTTP request is sent that contains an XML "communication-diversion" instance to the Application Server. The attribute of the communication-diversion element is "true". The mapping of the Facility I.E is described below. Table 5.4.2.1.1-1: Mapping of conditions FACILITY→ MESSAGE or HTTP PUT Request→ ActivationDiversion invoke <communication-diversion active="true" Procedure cfu <cp:ruleset> <cp:rule id="<rule id "> <cp:conditions> (see note 1) cfb <busy/> cfnr <no-answer/> basicService Speech audio3k 64 kbit …. <cp:ruleset> <cp:rule id="<rule id "> <cp:conditions> <media> (see note 2) servedUserNr PartyNumber P-Preferred-Identity or P-Asserted- Identity header (see notes 3 and 4) NOTE 1: In case unconditional call forwarding no corresponding <cp:condition> element is included. NOTE 2: The list of basic services is contained in ETSI EN 300 196-1 [25]. The string value shall be set to ASN1 enumerated numeric value of BasicService type in ETSI EN 300 196-1 [25], clause D.6. Activation of call forwarding for all basic services is achieved by omitting the <media> condition. NOTE 3: The servedUSerNr is mapped to either the P-Preferred-Identity header by a VGW or the P-Asserted-Identity header by an AGCF. NOTE 4: Mapping of the ISDN value "allNumbers" requires further study. Table 5.4.2.1.1-2: Mapping of actions FACILITY→ MESSAGE or HTTP PUT Request→ ActivationDiversion invoke <communication-diversion active="true" forwardedToAddress Public number <cp:ruleset> <cp:rule id="<rule id"> <cp:actions> <ss:forward-to> <ss:target> userC@domain noReplyTimer int <cp:ruleset> <cp:rule id="<rule id"> <cp:actions> <ss:forward-to> <ss:NoReplyTimer> 20 On receipt of a 200 OK MESSAGE or HTTP response, a DSS1 FACILITY message including the ActivationDiversion return result component is sent to the DSS1 user equipment. If an unsuccessful final response is received upon sending a MESSAGE or HTTP Request including an XML communication-diversion instance, a DSS1 FACILITY message including the ActivationDiversion return error component value "notAvailable" is sent to the DSS1 user equipment. NOTE: A more accurate mapping between unsuccessful final responses and ISDN operation errors is for further study. Additionally to activate the CDIV service, as a network option it is possible to use service code commands via in-band dialogue or using the service code via keypad protocol. These requirements to using the keypad protocol are described in annex A of the present document. The result is available in-band (announcement). ETSI ETSI TS 183 036 V3.7.1 (2021-02) 101
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.4.2.1.2 Communication Diversion deactivation
|
On receipt of a DSS1 FACILITY message containing the DeactivationDiversion invoke component, a SIP MESSAGE request or a HTTP Request is sent that contains an XML "communication-diversion" instance to the Application Server. The attribute of the communication-diversion element is "false". The mapping of the Facility I.E is described below. Table 5.4.2.1.2-1: Mapping of conditions FACILITY→ MESSAGE or HTTP PUT Request→ DeactivationDiversion invoke <communication-diversion active="false" procedure cfu <cp:ruleset> <cp:rule id="<rule id "> <cp:conditions> (See note 1) cfb <busy/> cfnr <no-answer/> basicService Speech audio3k 64 kbit …. <cp:ruleset> <cp:rule id="<rule id "> <cp:conditions> <media> (see note 2) servedUserNr PartyNumber P-Preferred-Identity or P-Asserted-Identity header (see notes 3 and 4) NOTE 1: In case unconditional call forwarding no corresponding <cp:condition> element is included. NOTE 2: The list of basic services is contained in ETSI EN 300 196-1 [25]. The string value shall be set to ASN1 enumerated numeric value of BasicService type in ETSI EN 300 196-1 [25], clause D.6. Deactivation of call forwarding for all basic services is achieved by omitting the <media> condition. NOTE 3: The servedUSerNr is mapped to either the P-Preferred-Identity header by a VGW or the P-Asserted-Identity header by an AGCF. NOTE 4: Mapping of the ISDN value "allNumbers" requires further study. On receipt of a 200 OK MESSAGE or HTTP successful response, a DSS1 FACILITY message including the DeactivationDiversion return result component is sent to the DSS1 user equipment. If an unsuccessful final response is received upon sending a MESSAGE or HTTP Request including an XML communication-diversion instance, a DSS1FACILITY message including the DeactivationDiversion return error component value "notAvailable" is sent to the DSS1 user equipment. NOTE: A more accurate mapping between unsuccessful final responses and ISDN operation errors is for further study. Additionally to deactivate the CDIV service, as a network option it is possible to use service code commands via in- band dialogue or using the service code via keypad protocol. The requirements for using the keypad protocol are described in annex A of the present document. The result is available in-band (announcement). ETSI ETSI TS 183 036 V3.7.1 (2021-02) 102
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.4.2.1.3 Communication Diversion interrogation
|
On receipt of a DSS1 FACILITY message containing the InterrogationDiversion invoke component, a SIP MESSAGE or HTTP request is sent that contains an XML "communication-diversion" instance to the Application Server. The mapping of the Facility I.E is described below. Table 5.4.2.1.3-1: Mapping of InterrogationDiversion invoke FACILITY→ MESSAGE request or HTTP GET request→ InterrogationDiversion invoke <communication-diversion> procedure cfu <cp:ruleset> <cp:rule id="<rule id "> <cp:conditions> (see note 1) cfb <busy/> cfnr <no-answer/> basicService Speech audio3k 64 kbit …. <cp:ruleset> <cp:rule id="<rule id "> <cp:conditions> <ss:media> (see note 2) servedUserNr PartyNumber P-Preferred-Identity or P-Asserted-Identity header (see notes 3 and 4) NOTE 1: In case unconditional call forwarding no corresponding <cp:condition> element is included. NOTE 2: The list of basic services is contained in ETSI EN 300 196-1 [25]. The string value shall be set to ASN1 enumerated numeric value of BasicService type in ETSI EN 300 196-1 [25], clause D.6 Interrogation of call forwarding for all basic services is achieved by omitting the <media> condition. NOTE 3: The servedUSerNr is mapped to either the P-Preferred-Identity header by a VGW or the P-Asserted- Identity header by an AGCF. NOTE 4: Mapping of the ISDN value "allNumbers" requires further study. On receipt of a MESSAGE request or HTTP successful response that contains a "communication-diversion" XML instance, a DSS1 FACILITY message is sent to the served user equipment. The mapping of the XML instance into the Facility I.E InterrogationDiversion invoke return result is described below. Table 5.4.2.1.3-2: Mapping of InterrogationDiversion result ←FACILITY ←MESSAGE request or HTTP GET response InterrogationDiversion return result <communication-diversion active="true" procedure cfu <cp:ruleset> <cp:rule id="<rule id "> <cp:conditions> (see note 1) cfb <busy/> cfnr <no-answer/> basicService Speech audio3k 64 kbit …. <cp:ruleset> <cp:rule id="<rule id "> <cp:conditions> <ss:media> (see note 2) servedUserNr PartyNumber P-Preferred-Identity or P-Asserted-Identity header (see notes 4 and 5) forwardedToAddress Public number <cp:ruleset> <cp:rule id="<rule id"> <cp:actions> <ss:forward-to> <ss:target> userC@domain (see note 3) NOTE 1: If the <busy/> and <no-answer/> conditions are absent from the XML document, the "procedure" element is set to "cfu". NOTE 2: The list of basic services is contained in ETSI EN 300 196-1 [25]. The string value shall be set to ASN1 enumerated numeric value of BasicService type in ETSI EN 300 196-1 [25], clause D.6. If the <media> element is absent, the basicService element is set to allServices. NOTE 3: If the country code is equal to the country code where the AGCF/VGW is located, the country code is removed from the number string and the Type of Number is set to "national number" else the number string is sent unchanged and the Type of number is set to "international number". NOTE 4: The servedUSerNr is mapped to either the P-Preferred-Identity header by a VGW or the P-Asserted-Identity header by an AGCF. NOTE 5: Mapping of the ISDN value "allNumbers" requires further study. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 103 If an unsuccessful final response is received upon sending a MESSAGE or HTTP Request including an XML "communication-diversion" instance, a DSS1 FACILITY message including the InterrogationDiversion return error component value "notAvailable" is sent to the DSS1 user equipment. NOTE: A more accurate mapping between unsuccessful final responses and ISDN operation errors is for further study. Additionally to interrogate the status of the CDIV service, as a network option it is possible to use service code commands via in-band dialogue or using the service code via keypad protocol. These requirements to using the keypad protocol are described in annex A of the present document. The result is available in-band (announcement).
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.4.2.1.4 Activation Status Notification Diversion
|
Mapping of this procedure requires further study.
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.4.2.2 Message Waiting Indication (MWI)
| |
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.4.2.2.1 Activation of Message Waiting Indication (MWI)
|
On receipt of a DSS1 FACILITY message containing the MWIActivate invoke component, a SIP SUBSCRIBE request is sent to the Application Server that contains an Event header and the value is set to "message-summary" additionally the Accept header contains the value "application/simple-message-summary". The Expires header contains the subscription duration. The mapping of the Facility I.E is described below. Table 5.4.2.2.1-1: Mapping of MWIActivate invoke FACILITY→ SUBSCRIBE→ Facility Information Element: MWIActivate invoke Event: message-summary Expires: xxxxx (user option) Accept: application/simple-message-summary receivingUserNr From: basicService controllingUserProvidedNr Request URI controllingUserNr (see note) Request URI NOTE: If only the "controllingUserNr" parameter is present, this parameter shall be mapped into the Request URI. In the other case the "controllingUserProvidedNr" parameter has precedence. On receipt of a 200 OK (SUBSCRIBE) or 202 OK (SUBSCRIBE) and the Expires header is not equal to zero, a DSS1 FACILITY message including the MWIActivate return result component is sent to the DSS1 user equipment. If an unsuccessful final response is received upon sending a SUBSCRBE, a DSS1 FACILITY message including the MWIActivate return error component value "resourceUnavailable" is sent to the DSS1 user equipment. NOTE: A more accurate mapping between unsuccessful final responses and ISDN operation errors is for further study. Additionally as to activate the MWI service, as a network option it is possible to use service code commands via in-band dialogue or using the service code via keypad protocol. These requirements to using the keypad protocol are described in annex A of the present document. The result is available in-band (announcement). ETSI ETSI TS 183 036 V3.7.1 (2021-02) 104
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.4.2.2.2 Deactivation of Message Waiting Indication (MWI)
|
On receipt of a DSS1 FACILITY message containing the MWIDeactivate invoke component, a SIP SUBSCRIBE request is sent to the Application Server the Event header I set to "message-summary" and the Expires header is set to zero. The mapping of the Facility I.E is described below. Table 5.4.2.2.2-1: Mapping of MWIDeactivate invoke FACILITY → SUBSCRIBE → Facility Information Element: MWIDeactivate invoke Event: message-summary Expires: 0 receivingUserNr From: basicService controllingUserProvidedNr Request URI controllingUserNr (see note) Request URI NOTE: If only the "controllingUserNr" parameter is present, this parameter shall be mapped into the Request URI. In the other case the "controllingUserProvidedNr" parameter has precedence. On receipt of a 200 OK (SUBSCRIBE), a DSS1 FACILITY message including the MWIDeactivate return result component is sent to the DSS1 user equipment. If an unsuccessful final response is received upon sending a SUBSCRIBE, a DSS1FACILITY message including the MWIDeactivate return error component value "resourceUnavailable" is sent to the DSS1 user equipment. NOTE: A more accurate mapping between unsuccessful final responses and ISDN operation errors is for further study. Additionally as to deactivate the MWI service, as a network option it is possible to use service code commands via in- band dialogue or using the service code via keypad protocol. These requirements to using the keypad protocol are described in annex A of the present document. The result is available in-band (announcement). ETSI ETSI TS 183 036 V3.7.1 (2021-02) 105 Annex A (normative): Keypad Procedures A.1 Generic procedure at the AGCF/VGW side On receipt of a service code included within a Keypad facility information element included within a SETUP and/or INFO Message(s), the AGCF/VGW sends an INVITE request with the following information: • A Request-URI structured as follows: - A user part containing the service code command, excluding the START and FINISH fields. The same Syntax is used as for PSTN. This is shown in clause C.1.2.1.1 in ETSI TS 183 043 [42]. - 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 is 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 command code. Setting the phone-context attribute is required for conformance purposes with IETF RFC 3966 [47]. PES network entities (e.g. CSCF) ignore this attribute. NOTE 2: In cases where Overlap Signalling is used the regarding rules for Overlap are used. The collection of the Service Code Information is done within the related Application Server. • To Header: Same info as in R-URI. • A P-Asserted-Identifier header containing the public user identity of the subscriber issuing the service code command. • An SDP offer for a voice call. NOTE 3: The SDP offer may be used by the Application Server in case an announcement has to be delivered. A.2 Generic procedure at the AS side The procedures used at the AS Side are the same as for PSTN as described within ETSI TS 183 043 [42], clause C.1.2.1.3. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 106 Annex B (normative): SDP mapping for ISDN 7 kHz service and Inter-working B.1 Originating Side DSS1 VGW/AGCF Toward Far End => DSS1 SIP INVITE SDP- OFFER => BC1 = 3,1 kHz audio CLEARMODE, PCMA or PCMU (the codecs appear in one m line) DSS1- VGW or DSS1- AGCF or MGCF or SIP Phone 7 kHz or SIP Phone 3,1 kHz BC2 = Unrestricted Digital Info with tones/announce DSS1 VGW/AGCF From Far End <= DSS1 SIP SDP- ANSWER <= BC = Unrestricted Digital Info with tones/announce (see note 1) CLEARMODE, PCMA or PCMU (at least the CLEARMODE codec is present in one m line) DSS1- VGW DSS1- AGCF or MGCF BC = 3,1 kHz (see note 2) PCMA/PCMU (the codecs appear in one m line) SIP Phone 3,1 kHz or SIP Phone 7 kHz (see notes 1 and 2) NOTE 1: It is assumed that the SIP 7 KHz phone only supports the ITU-T G.722 codec [i.5] natively and thus does not understand the CLEARMODE codec. NOTE 2: It is assumed that the terminating SIP 7 KHz phone supports fallback to the CLEARMODE codec (CLEARMODE, PCMA or PCMU). B.2 Terminating side a) Case 1 DSS1 VGW/AGCF (see note 1) Far end <= DSS1 SIP INVITE SDP- OFFER<= DSS1- VGW DSS1- AGCF or MGCF BC1= 3,1 kHz audio BC2 = Unrestricted Digital Info with tones/announce CLEARMODE, PCMA or PCMU (at least the CLEARMODE codec is present in one m line) =>DSS1 SIP INVITE SDP- ANSWER=> BC2 = Unrestricted Digital Info with tones/announce CLEARMODE, PCMA or PCMU (the codecs appear in one m line) b) Case 2 DSS1 VGW/AGCF (see note 2) Far end <=DSS1 SIP INVITE SDP- OFFER <= SIP Phone 7 kHz BC = 3,1 kHz G.722, PCMA, PCMU =>DSS1 SIP INVITE SDP- ANSWER=> BC = 3,1 kHz PCMA/PCMU ETSI ETSI TS 183 036 V3.7.1 (2021-02) 107 c) Case 3 DSS1 VGW/AGCF (see note 2) Far end <=DSS1 SIP INVITE SDP- OFFER<= SIP Phone 3,1 kHz BC = 3,1 kHz PCMA, PCMU (the codecs appear in one m line) =>DSS1 SIP INVITE SDP- ANSWER=> BC = 3,1 kHz PCMA/PCMU (the codecs appear in one m line) NOTE 1: VGW/AGCF Media handling = H.221 structure is carried transparent from end to end. NOTE 2: VGW/AGCF media handling = PCMA/PCMU is carried transparent. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 108 Annex C (normative): Timers This annex specifies the use of the different ISUP, SIP and ISDN timers. Figure C-1 ETSI ETSI TS 183 036 V3.7.1 (2021-02) 109 Figure C-2 Figure C-3: Overlap with Tinfo Timer ETSI ETSI TS 183 036 V3.7.1 (2021-02) 110 Table C-1: SIP - Timer in the network side Timer number Default time-out value State of call Cause for start Normal stop At the first expiry At the subsequent expiry Tinfo 0,5 s to 2 s Overlap sending SETUP Received Timer expired INVITE with the collected digits received in the SETUP and INFOs Tisdn3 12 s to 17 s (default of 12 s) Overlap sending On receipt of 404 Not Found or 484 Address Incomplete on the latest INVITE transactions for the corresponding call. Subsequent INFO is received, on reception of 180 Ringing, or 183 Session Progress or 200 OK (INVITE). Release call TTIR1 0,1 s to 2 s (default 0,1 s) Session answering On receipt of 200 OK INVITE including the option tag "from- change", no privacy header or privacy value none, and Userinfo of P- Asserted-Identity in the format of a tel URI. At the receipt of an UPDATE map the received 200 OK INVITE to a CONNECT message ETSI ETSI TS 183 036 V3.7.1 (2021-02) 111 Table C-2: ISDN Timers in the AGCF/VGW side- overview Timer number Default time-out value State of call Cause for start Normal stop At the first expiry At the second expiry Cross-reference T301 Minimum 3 min Call received ALERT received CONNECT received Clear call Timer is not restarted (see note 2) T302 10 s to 15 s (see note 3) Overlap sending SETUP ACK sent Receipt of INFO, restarts T302 With sending complete indication, or network alert, or connect request received Clear if call information determined to be definitely incomplete; else send CALL PROC Timer is not restarted Mandatory T303 4 s (see note 1) Call present SETUP sent ALERT, CONNECT CALL PROC or SETUP ACK received, REL COMPLETE received if SETUP sent on point-point data link Retransmit SETUP; restart T303. If REL COMPLETE has been received, clear the call Clear network connection. Enter call abort state Mandatory T304 20 s (provisional value) Overlap receiving SETUP ACK received. Sending of INFO restarts T304 Send INFO; receive CALL PROC, ALERT or CONNECT Clear the call Timer is not restarted Mandatory only if clause 5.2.4 is implemented NOTE 1: This default value assumes the use of default values at layer 2, i.e. [N200 + 1] times T200. Whether these values should be modified when layer 2 default values are modified by an automatic negotiation procedure is for further study. NOTE 2: The network may already have applied an internal alerting supervision timing function, e.g. incorporated within call control. If such a function is known to be operating on the call, then timer T301 is not used. NOTE 3: The value of timer T302 may vary beyond these limits, e.g. as a result of called party number analysis. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 112 Table C-3: Q.931 - ISDN Timers in the user side- overview Timer number Default time-out value State of call Cause for start Normal stop At the first expiry At the second expiry Cross-reference T301 Minimum 3 min. Call Delivered ALERT received CONNECT received Clear call Timer is not restarted Mandatory when annex D is implemented T302 15 s Overlap receiving SETUP ACK sent Restart when INFO received INFO received with sending complete indication; or internal alerting; or internal connection; or a determination that sufficient information has been received Clear if call information determined to be incomplete; else send CALL PROC Timer is not restarted Mandatory only if clause 5.2.4 is implemented T303 4 s Call Initiated SETUP sent ALERT (annex D), CONNECT (annex D), SETUP ACK, CALL PROC or REL COMPLETE received Retransmit SETUP; restart T303. If REL COMPLETE was received, clear the call (annex D) Clear internal connection. Send REL COMPLETE. Enter Null state Mandatory when annex D is implemented; otherwise optional T304 30 s Overlap Sending INFO sent Restarted when INFO sent again CALL PROC, ALERT, CONNECT, DISC or prog. Ind. 1 or 2 received DISC sent Timer is not restarted Optional ETSI ETSI TS 183 036 V3.7.1 (2021-02) 113 Annex D (normative): Overlap Sending D.1 Multiple INVITE Overlap Dialling Procedures (Optional) D.1.1 Actions at the originating VGW/AGCF D.1.1.1 Terminating overlap signalling at originating VGW/AGCF If overlap sending is used, the SETUP message contains either: a) no called number information; b) incomplete called number information; or c) called number information which the network cannot determine to be complete. When the VGW/AGCF has received called number information element from the calling user in a SETUP message (possibly followed by INFORMATION messages), it shall send an INVITE request with all the available called number information in the Request line and the originating SDP (derived from the BC and optionally present HLC for the VGW - else as obtained from the originating AGW (and influenced by the BC and optionally present HLC)) - see table 5.1.1.1.4-2. The AGCF/VGW can contain a configurable digit map which is used to analyse the called party information element contents received in a sequence of called party number information elements. Among other purposes, 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 ETSI TS 183 043 [42], 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. D.1.1.2 Sending of INVITE without determining the end of address signalling On receipt of such a SETUP message, the AGCF/VGW starts the ISDN timer T302, sends a SETUP ACKNOWLEDGE message to the user and enters the overlap sending state: • If no number information is included the network will return dial tone, if required by the tone option. • If the received BC in the SETUP message is coded with speech, 3,1 kHz audio, UDI/TA, it shall include progress indicator No. 8, in-band information or appropriate pattern is now available, in the SETUP ACKNOWLEDGE message. 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; - starts timer Tinfo if not running; and - is prepared to process further incoming INFO as described below; ETSI ETSI TS 183 036 V3.7.1 (2021-02) 114 - is prepared to handle incoming SIP 404 or 484 error responses as detailed in clause D.1.1.3. 2) On receipt of a new DSS1 INFO message, the originating VGW/AGCF shall: - stop timer Tisdn3 (if it is running); - send 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 in a DSS1 INFO message is received after the SIP 404 or 484 error responses has been received, the INVITE request additionally includes the digits received. NOTE: The DSS1 timer 302 is restarted with the receipt of a DSS1 INFO message. At the receipt of a new DSS1 INFO message, a SIP 18x provisional response, or a SIP 200 OK (INVITE), the originating VGW/AGCF shall stop Tisdn3. As a network option the Timer Tinfo can be used , in this case the following procedure apply starting with the first digit received by the AGCF/VGW: • Start timer Tinfo with receiving the SETUP. • Collect all digits received within INFO messages. • At expiry of timer Tinfo the initial INVITE is sent out as described under 1. • If further digits are needed then the AGCF/VGW shall collect further digits until min. length has been reached. As a network Option the first INVITE can be sent with the receipt of the SETUP message and the Tinfo is started. The Tinfo shall not be used if the INVITE has to be sent immediately because e.g. the hotline feature is provided to the originating user. D.1.1.3 Special handling of 404 Not Found and 484 Address Incomplete responses after sending of INVITE without determining the end of address signalling This clause is only applicable when the network option of Sending of INVITE without determining the end of address signalling is being used (see clause D.1.1.2). On receipt of a 404 Not Found or 484 Address Incomplete response, the originating VGW/AGCF starts timer Tisdn3, if there are no other pending INVITE transactions for the corresponding call. At the receipt of fresh address information, or a SIP 18x provisional responses, or a SIP 200 OK (INVITE), the originating VGW/AGCF stops 302 and Tisdn3. The originating VGW/AGCF shall send a RELEASE message with cause value 28 towards the ISDN user if Tisdn3 expires. Option a) Overlap with Tinfo Timer. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 115 Figure D.1.1.3-1: Overlap with Tinfo Timer- no transaction is pending ETSI ETSI TS 183 036 V3.7.1 (2021-02) 116 Figure D.1.1.3-2: Overlap with Tinfo Timer one transaction is pending ETSI ETSI TS 183 036 V3.7.1 (2021-02) 117 Option b) Overlap with Digit Map. Figure D.1.1.3-3: Overlap with digit map ETSI ETSI TS 183 036 V3.7.1 (2021-02) 118 Option c) Overlap with Digit Map and Tinfo Timer. Figure D.1.1.3-4: Overlap with digit map and Tinfo timer digit map matched before Tinfo expiry ETSI ETSI TS 183 036 V3.7.1 (2021-02) 119 Figure D.1.1.3-5: Overlap with digit map and Tinfo timer digit map matched after Tinfo expiry ETSI ETSI TS 183 036 V3.7.1 (2021-02) 120 Option d) 484 message with Min-length X parameter. Figure D.1.1.3-6: Overlap option with 484 message with Min-length x parameter ETSI ETSI TS 183 036 V3.7.1 (2021-02) 121 Option e) 484 message without Min-length X parameter. Figure D.1.1.3-7: 484 message without Min-length X parameter D.1.2 Actions at the terminating VGW/AGCF See annex H for DDI. For all other no further action is needed. D.2 In-Dialog Method (Optional) D.2.1 Actions at the originating VGW/AGCF D.2.1.1 Terminating overlap signalling at originating VGW/AGCF If overlap sending is used, the SETUP message contains either: a) no called number information; b) incomplete called number information; or c) called number information which the network cannot determine to be complete. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 122 When the VGW/AGCF has received the called number information element from the calling user in a SETUP message (possibly followed by INFORMATION messages), it shall send an INVITE request with all the available called number information in the Request line and the originating SDP (derived from the BC and optionally present HLC for the VGW - else as obtained from the originating AGW (and influenced by the BC and optionally present HLC)) - see table 5.1.1.1.4-2. The AGCF/VGW can contain a configurable digit map which is used to analyse the called party information element contents received in a sequence of called party number information elements. Among other purposes, 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 ETSI TS 183 043 [42], 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. D.2.1.2 Sending of INVITE without determining the end of address signalling On receipt of such a SETUP message, the AGCF/VGW starts the ISDN timer T302, sends a SETUP ACKNOWLEDGE message to the user and enters the overlap sending state: • If no number information is included the network will return dial tone, if required by the tone option. • If the received BC in the SETUP message is coded with speech, 3,1 kHz audio, UDI/TA, it shall include progress indicator No. 8, in-band information or appropriate pattern is now available, in the SETUP ACKNOWLEDGE message. 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: - use the SIP precondition extension within the INVITE request; - be prepared to process INFO 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 Tisdn3. 2) On receipt of a new INFO from the DSS1 side, the AGCF/VGW shall: - if an early dialog has been established, send a SIP INFO request including the additional digits for this call; - 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. At the receipt of a new DSS1 INFO message, a SIP 18x provisional response, or a SIP 200 OK (INVITE), the originating VGW/AGCF shall stop Tisdn3. As a network option the Timer Tinfo can be used, in this case the following procedure apply starting with the first digit received by the AGCF/VGW: • start timer Tinfo with receiving the SETUP; • collect all digits received within INFO messages; • at expiry of timer Tinfo the initial INVITE is sent out as described under 1): - If further digits are needed then the AGCF/VGW shall collect further digits until min length has been reached. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 123 As a network Option the first INVITE can be sent with the receipt of the SETUP message and the Tinfo is started. The timer Tinfo 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 shall send a RELEASE message with cause value 28 towards the ISDN user if Tisdn3 expires. Option a) Overlap with Tinfo Timer. Figure D.2.1.2-1: Overlap with Tinfo Timer - no transaction is pending ETSI ETSI TS 183 036 V3.7.1 (2021-02) 124 Figure D.2.1.2-2: Overlap with Tinfo Timer no transaction is pending ETSI ETSI TS 183 036 V3.7.1 (2021-02) 125 Option b) Overlap with Digit Map. Figure D.2.1.2-3: Overlap with digit map ETSI ETSI TS 183 036 V3.7.1 (2021-02) 126 Option c) Overlap with Digit Map and Tinfo Timer. Figure D.2.1.2-4: Overlap with digit map and Tinfo timer digit map matched before Tinfo expiry ETSI ETSI TS 183 036 V3.7.1 (2021-02) 127 Figure D.2.1.2-5: Overlap with digit map and Tinfo timer digit map matched after Tinfo expiry ETSI ETSI TS 183 036 V3.7.1 (2021-02) 128 Option d) 484 message with Min-length X parameter. Figure D.2.1.2-6: Overlap option with 484 message with Min-length x parameter ETSI ETSI TS 183 036 V3.7.1 (2021-02) 129 Option c) 484 message without Min-length X parameter. Figure D.2.1.2-7: 484 message without Min-length X parameter D.2.2 Actions at the terminating VGW/AGCF See annex H for DDI. For all other no further action is needed. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 130 Annex E (normative): Direct Dialling in E.0 General Information This annex describes the handling of Direct Dialling In. E.1 Multiple INVITEs Method (Optional) E.1.1 Actions at the incoming AGCF/VGW E.1.1.1 Receipt of Subsequent INVITE messages If the SETUP message has already been sent and the SETUP ACKNOWLEDGE message has been received, overlap receiving is used, an INFORMATION message will be sent upon receipt of each Subsequent INVITE. When the SETUP ACKNOWLEDGE message is received, the AGCF/VGW shall: stop timer T303; start timer T304; enter the Overlap receiving state; and send the remainder of the call information (if any) in one or more INFORMATION messages, starting timer T304 when each INFORMATION message is sent. At the expiration of timer T304 the network initiates call clearing with cause No. 28, invalid number format (address incomplete) to the calling user and cause No. 102, "recovery on timers expiry" to the called user. Figure E.1.1.1-1: Receipt of Subsequent INVITE messages ETSI ETSI TS 183 036 V3.7.1 (2021-02) 131 Figure E.1.1.1-2: Receipt of Subsequent INVITE messages Receipt of subsequent INVITE messages This clause applies when overlap operation is supported across the AGCF/VGW. If the AGCF/VGW receives an INVITE with the same Call-ID and From tag as a previous INVITE which was associated with a DSS1 call/bearer control instance currently existing on the DSS1 side, then: a) If the number of digits in the Request-URI is a superset of the number of digits already accumulated for the call, the AGCF/VGW shall generate an INFO and pass it to outgoing DSS1 procedures. The INFO shall contain in its called party number parameter only the additional digits received in this Request-URI compared with the digits already accumulated for the call. b) If the number of digits in the Request-URI is fewer than the number of digits already accumulated for the call, then the AGCF/VGW shall immediately send a 484 Address Incomplete response for this INVITE. In this case no INFO is sent to DSS1 procedures. E.2 In-Dialog Method (Optional) E.2.1 Actions at the incoming AGCF/VGW E.2.1.1 Receipt of Subsequent INVITE messages If the SETUP message has already been sent and the SETUP ACKNOWLEDGE message has been received, overlap receiving is used, an INFORMATION message will be sent upon receipt of each SIP INFO request carrying additional digits. When the SETUP ACKNOWLEDGE message is received, the AGCF/VGW shall: stop timer T303; start timer T304; enter the Overlap receiving state; and send the remainder of the call information (if any) in one or more INFORMATION messages, starting timer T304 when each INFORMATION message is sent. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 132 At the expiration of timer T304 the network initiates call clearing with cause No. 28, invalid number format (address incomplete) to the calling user and cause No. 102, "recovery on timers expiry" to the called user. Figure E.2.1.1-1: Receipt of SIP INFO request Figure E.2.1.1-2: Receipt of SIP INFO requests ETSI ETSI TS 183 036 V3.7.1 (2021-02) 133 Receipt of SIP INFO requests This clause applies when overlap operation is supported across the AGCF/VGW. If the AGCF/VGW receives a SIP INFO request within an early dialog created by a previous INVITE, which was associated with a DSS1 call/bearer control instance currently existing on the DSS1 side, then the AGCF/VTW shall generate an INFO and pass it to outgoing DSS1 procedures. The INFO shall contain in its called party number parameter only the additional digits, received in the SIP INFO request, compared with the digits already accumulated for the call. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 134 Annex F (informative): Handling and interworking of DSS1 messages and Information Elements This annex describes the handling and interworking of DSS1 messages and Information Elements at the AGCF/VGW. Table F-1: DSS1 messages DSS1 Message Handling in SIP ALERTING Interworking with 180 Ringing CALL PROCEEDING Interworking with 183 Session Progress or local significance CONNECT Interworking with 200 OK INVITE CONNECT ACKNOWLEDGE Local significance PROGRESS Interworking with 183 Session Progress or local significance SETUP Interworking with INVITE SETUP ACKNOWLEDGE Local significance RESUME Interworking with INVITE or UPDATE containing the P-Service-Notification value "user-resumed" RESUME ACKNOWLEDGE Local significance RESUME REJECT SUSPEND Interworking with INVITE or UPDATE containing the P-Service-Notification value "user-suspended" SUSPEND ACKNOWLEDGE Local significance SUSPEND REJECT DISCONNECT Interworking with BYE, CANCEL or unsuccessful status responses RELEASE Interworking with BYE, CANCEL or unsuccessful status responses RELEASE COMPLETE Interworking with BYE, CANCEL or unsuccessful status responses or local significance INFORMATION Interworking with INVITE in case of overlap procedure NOTIFY Interworking with INVITE or UPDATE SEGMENT No interworking STATUS Local significance STATUS ENQUIRY Local significance USER INFORMATION No interworking CONGESTION CONTROL Local significance RESTART Local significance RESTART ACKNOWLEDGE Local significance HOLD Interworking with INVITE or UPDATE. HOLD procedure based on ETSI TS 124 083 [10] HOLD ACKNOWLEDGE Local significance HOLD REJECT RETRIEVE Interworking with INVITE or UPDATE. HOLD procedure based on ETSI TS 124 083 [10] RETRIEVE ACKNOWLEDGE Local significance RETRIEVE REJECT REGISTER Interworking with CCBS or CCNR FACILITY Operation of the configuration of services or user equipment ETSI ETSI TS 183 036 V3.7.1 (2021-02) 135 Table F-2: DSS1 Information Elements DSS1 Information Element Handling in SIP Protocol discriminator Local significance Call reference Local significance Message type Local significance Channel identification Local significance Bearer capability Interworking with INVITE, 18x, 200 OK High layer compatibility Interworking with INVITE Low layer compatibility Interworking with INVITE Progress indicator Interworking with INVITE, 18x, 200 OK Display Interworking with INVITE, 18x, 200 OK CANCEL, BYE Date/time Local handling Signal Sending complete Indication for end of dialling Keypad facility Maintenance of services Called party number Interworking with INVITE Calling party number Interworking with INVITE Calling party subaddress Interworking with INVITE Called party subaddress Interworking with INVITE Connected number Interworking with 200 OK/UPDATE Connected subaddress Interworking with 200 OK/UPDATE Redirecting number Interworking with INVITE Redirection number Interworking with 181, 180, 200 OK Cause Interworking with unsuccessful final response, BYE or CANCEL Notification indicator Interworking with INVITE, UPDATE, 18x, 200 OK Facility Maintenance of services Call identity Network-specific facilities No interworking Transit network selection No interworking Repeat indicator Call state local User-user Interworking with INVITE, 18x, 200 OK, BYE Information rate End-end transit delay Transit delay selection and indication Packet layer binary parameters (X25) Packet layer window size (X25) Packet size (X25) Closed user group No interworking Reverse charging indication No interworking More data Restart indicator Local significance Locking Shift Non-locking Shift ETSI ETSI TS 183 036 V3.7.1 (2021-02) 136 Annex G (informative): Message flows G.1 Three party NOTE: Two sessions, one on hold one active. Figure G.1-1: Initial position before starting the 3PTY service ETSI ETSI TS 183 036 V3.7.1 (2021-02) 137 NOTE: The media streams should be set on hold before. Figure G.1-2: Invocation of three party session ETSI ETSI TS 183 036 V3.7.1 (2021-02) 138 Figure G.1-3: Release the three part conversation to have a private communication with the previous active user ETSI ETSI TS 183 036 V3.7.1 (2021-02) 139 Figure G.1-4: Release the three part conversation to have a private communication with the previous held user ETSI ETSI TS 183 036 V3.7.1 (2021-02) 140 Figure G.1-5: The served user releases the session with the previous held user Figure G.1-6: The served user releases the session with the previous active user ETSI ETSI TS 183 036 V3.7.1 (2021-02) 141 Figure G.1-7: The previous held user disconnects the own session using basic call procedures Figure G.1-8: The previous active user disconnects the own session using basic call procedures ETSI ETSI TS 183 036 V3.7.1 (2021-02) 142 G.2 Explicit Communication Transfer (ECT) Figures G.2-1 to G.2-2 describe the message flow in case of interworking of the ECT supplementary service into the ECT simulation service. O-AGCF/VGW AS UE B UE C SETUP (CR1) INVITE (CSq1) 180 Ringing 200 OK INVITE ACK ALERTING CONNECT SETUP (CR2) INVITE (CSq2) 180 Ringing 200 OK INVITE ACK ALERTING CONNECT HOLD (CR1) INVITE (CSq1, sendonly) 200 OK INVITE (recvonly) ACK Originating user invokes HOLD Originating user establishes a communication with UE C Figure G.2-1: Basic procedure and remote user is set on HOLD ETSI ETSI TS 183 036 V3.7.1 (2021-02) 143 Figure G.2-2: Invocation of ECT ETSI ETSI TS 183 036 V3.7.1 (2021-02) 144 Annex H (informative): Use of progress indicators This annex describes the use of the different progress indicator values for non-ISDN and IMS terminals. The Progress Indicators for ISDN terminals in the IMS are only applicable for voice connection (speech and 3,1 kHz audio). Examples of use are given. • Progress indicator No. 1 - Indicates that interworking with a non-ISDN has occurred within the network or networks through which the call has traversed. • Progress indicator No. 2 - Indicates that the destination user is not ISDN. • Progress indicator No. 3 - Indicates that the origination user is not ISDN. • The ISDN access indicator (see note) - "originating access ISDN" is transported in the IMS as PSTN XML ProgressIndicator No. 6 . • The ISDN access indicator (see note) - "Terminating access ISDN" is transported in the IMS as PSTN XML ProgressIndicator No. 7. NOTE: The "ISDN access indicator" is defined in the Recommendation ITU-T Q.763 [i.2] in the BCI and FCI and indicates the access type. The access indicator can be not directly mapped to the ISDN progress indicator and is not defined in ETSI EN 300 403-1 [29]. The ISDN access indicator can be created only from the network e.g. VGW, AGCF, SIP/ISUP MGCF, not from the UE and prevents the sending of a progress indicator indicating a non-ISDN connection. The use of progress indicators Nos. 1, 2 and 3 is exemplified in the following. Several interworking situations are identified in figure H.1: a) interworking with another network; b) interworking with a non-ISDN user connected to an ISDN switch; c) interworking with non-ISDN equipment within the calling or called user's premises; d) interworking with another network behind the T reference point; e) interworking with an IMS network behind the S/T reference point (simulated service); f) interworking with an IMS network behind the S/T reference point (simulated /emulated service in the AGCF); g) interworking with an IMS network behind the Gm reference point; h) interworking with non-ISDN equipment within the calling or called user's premises which is connected to an IMS network; i) interworking with another network behind the T reference point which is connected to an IMS network. j) interworking with a non-ISDN (PES) user connected to a VGW which is not supporting XML. Examples of following interworking situations are identified in figures: • Figure H-2: interworking situation IMS, an ISDN (PES) user is calling an ISDN (PES) user. • Figure H-3: interworking situation IMS, an ISDN (PES) user is calling a non-ISDN (PES) user which forwarded the call to an ISDN (PES) user. The non-ISDN (PES) user is connected to a VGW which is not supporting XML. • Figure H-4: Interworking situation IMS to TDM, an ISDN (PES) user is calling an ISDN user with an PBX which has a non-ISDN access. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 145 • Figure H-5: Interworking situation IMS to TDM, an ISDN (PES) user is calling a non-ISDN user which forwarded the call to an ISDN user with an PBX which has a non-ISDN access. The ISDN user is in the same switch. S/T ISDN Tel. PSTN / ISDN A b POTS a NT 2 T Non ISDN c d IMS VGW S/T ISDN Tel. e Gm ISDN Tel. f S/T IP Phone Gm g B C D E NT 2 h i T Non ISDN non-ISDN user non-ISDN user non-ISDN user j B VGW non-ISDN Gm Figure H-1 ETSI ETSI TS 183 036 V3.7.1 (2021-02) 146 As regards calls from A - (ISDN access in an ISDN network) the following applies. Table H-1 Case Originating Terminal A receives PI from the called user PSTN/ISDN (ISUP) MGCF IMS Terminating Terminal sent <----- <----- <----- <----- <----- a PI#1 PI#1 mapped from BCI - - b PI#2 PI#2 mapped from BCI - - c PI#2 PI#2 mapped from ATP - - PI#2 d PI#1 PI#1 mapped from ATP - - PI#1 e BCI: ISDN User Part indicator is: "ISDN User Part used all the way" BCI: ISDN User Part indicator is: "ISDN User Part used all the way" mapped from PI#7 XML PI#7 f BCI: ISDN User Part indicator is: "ISDN User Part used all the way" BCI: ISDN User Part indicator is: "ISDN User Part used all the way" mapped from PI#7 XML PI#7 g PI#1 (PI#1 mapped from BCI) ISDN User Part indicator is: ISDN User Part not used all the way BCI: ISDN User Part indicator is: ISDN User Part not used all the way h PI#2 (PI#2 mapped from ATP) BCI: ISDN User Part indicator is: "ISDN User Part used all the way" mapped from PI#7 ATP: PI#2 BCI: ISDN User Part indicator is: "ISDN User Part used all the way" mapped from PI#7 ATP: PI#2 XML PI#7, XML PI#2 PI#2 i PI#1 (PI#1 mapped from ATP) BCI: ISDN User Part indicator is: "ISDN User Part used all the way" mapped from PI#7 ATP: PI#1 BCI: ISDN User Part indicator is: "ISDN User Part used all the way" mapped from PI#7 ATP: PI#1 XML PI#7, XML PI#1 PI#1 j PI#1 (PI#1 mapped from BCI) BCI: ISDN User Part indicator is: "ISDN User Part not used all the way" ISDN access indicator: Terminating g access non-ISDN BCI: ISDN User Part indicator is: "ISDN User Part not used all the way" ISDN access indicator: Terminating g access non-ISDN As regards calls towards A the following applies. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 147 Table H-2 Case Originating Terminal sends PI IMS MGCF PSTN/ISDN (ISUP) Terminating Terminal A receives PI -----> -----> -----> -----> ----> a - - FCI: ISDN User Part indicator: ISDN User Part not used all the way BC = 3,1 kHz and PI#1 b - - FCI: ISDN User Part indicator: ISDN User Part used all the way ISDN access indicator: originating access non-ISDN BC = 3,1 kHz and PI#3 c PI#3 - - FCI: ISDN User Part indicator: ISDN User Part used all the way ISDN access indicator: originating access ISDN ATP: PI#3 PI#3 d PI#1 - FCI: ISDN User Part indicator: ISDN User Part used all the way ISDN access indicator: originating access ISDN ATP: PI#1 FCI: ISDN User Part indicator: ISDN User Part used all the way ISDN access indicator: originating access ISDN ATP: PI#1 PI#1 e XML PI#6 FCI: ISDN User Part indicator: ISDN User Part used all the way ISDN access indicator: originating access ISDN FCI: ISDN User Part indicator: ISDN User Part used all the way ISDN access indicator: originating access ISDN ETSI ETSI TS 183 036 V3.7.1 (2021-02) 148 Case Originating Terminal sends PI IMS MGCF PSTN/ISDN (ISUP) Terminating Terminal A receives PI -----> -----> -----> -----> ----> f XML PI#6 FCI: ISDN User Part indicator: ISDN User Part used all the way ISDN access indicator: originating access ISDN FCI: ISDN User Part indicator: ISDN User Part used all the way ISDN access indicator: originating access ISDN g FCI: ISDN User Part indicator is: ISDN User Part not used all the way" FCI: ISDN User Part indicator is: ISDN User Part not used all the way" BC = 3,1 kHz and PI#1 h PI#3 XML PI#6, XML PI#3 XML PI#6 is mapped to: FCI: ISDN User Part indicator is: ISDN User Part used all the way) and ISDN access indicator: originating access ISDN PI#3 is mapped to ATP FCI: ISDN User Part indicator is: ISDN User Part used all the way) and ISDN access indicator: originating access ISDN PI#3 is mapped to ATP PI#3 i PI#1 XML PI#6, XML PI#1 XML PI#6 is mapped to: FCI: ISDN User Part indicator is: ISDN User Part used all the way) and ISDN access indicator: originating access ISDN PI#1 is mapped to ATP FCI: ISDN User Part indicator is: ISDN User Part used all the way) and ISDN access indicator: originating access ISDN PI#1 is mapped to ATP j XML PI#6 is mapped to: FCI: ISDN User Part indicator is: ISDN User Part not used all the way) and ISDN access indicator: originating access non- ISDN FCI: ISDN User Part indicator is: ISDN User Part not used all the way) and ISDN access indicator: originating access non- ISDN ETSI ETSI TS 183 036 V3.7.1 (2021-02) 149 As regards calls from C or D (ISDN access in the IMS) the following applies. Table H-3 Case Originating ISDN (PES) C or ISDN D Terminal receives PI IMS MGCF PSTN/ISDN (ISUP) Terminating Terminal sends PI <----- <----- <----- <----- <----- a PI#1 XML PI#1 BCI is mapped to PI#1 BCI parameters ISDN User Part indicator: ISDN User Part not used all the way b PI#2 XML PI#2 BCI is mapped to PI#2 BCI parameters ISDN User Part indicator: ISDN User Part used all the way ISDN access indicator: Terminating access non-ISDN c PI#2 XML PI#7 XML PI#2 BCI is mapped to XML PI#7 ATP is mapped to XML PI#2, BCI parameters: ISDN User Part indicator: ISDN User Part used all the way ISDN access indicator: Terminating access ISDN ATP: PI#2 PI#2 d PI#1 XML PI#7 XML PI#1 BCI is mapped to XML PI#7 ATP is mapped to XML PI#1, BCI parameters ISDN User Part indicator: ISDN User Part used all the way ISDN access indicator: Terminating access ISDN ATP: PI#1 PI#1 e XML PI#7 - - - f XML PI#7 - - - g PI#1 - - - h PI#2 XML PI#7 XML PI#2 - - PI#2 i PI#1 XML PI#7 XML PI#1 - - PI#1 j PI#1 - - - ETSI ETSI TS 183 036 V3.7.1 (2021-02) 150 As regards calls towards C or D (ISDN (PES) does not support XML) the following applies. Table H-4 Case Terminating ISDN Terminals C or D receives PI IMS MGCF PSTN/ISDN (ISUP) Originating Terminal sends PI <----- <----- <----- <----- <----- a BC = 3,1 kHz and PI#1 BCI parameters ISDN User Part indicator ISDN User Part not used all the way b BC = 3,1 kHz and PI#1 BCI parameters ISDN User Part indicator: ISDN User Part used all the way ISDN access indicator: Terminating access non-ISDN c BC = 3,1 kHz and PI#1 BCI parameters: ISDN User Part indicator: ISDN User Part used all the way ISDN access indicator: Terminating access ISDN ATP: PI#2 PI#2 d BC = 3,1 kHz and PI#1 BCI parameters ISDN User Part indicator: ISDN User Part used all the way ISDN access indicator: Terminating access ISDN ATP: PI#1 PI#1 e BC = 3,1 kHz and PI#1 - - f BC = 3,1 kHz and PI#1 - - g BC = 3,1 kHz and PI#1 - - h BC = 3,1 kHz and PI#1 - - PI#2 (User" h" is supporting XML) i BC = 3,1 kHz and PI#1 - - (User "I" is supporting XML) j BC = 3,1 kHz and PI#1 - - ETSI ETSI TS 183 036 V3.7.1 (2021-02) 151 As regards calls towards C or D (ISDN PES access in the IMS) the following applies. Table H-5 Case Originating Terminal sends PI PSTN/ISDN (ISUP) MGCF IMS Terminating Terminal C or D receives PI -----> -----> -----> -----> -----> a FCI ISDN User Part indicator: ISDN User Part not used all the way FCI is mapped to XML PI#1 PI#1 b FCI ISDN User Part indicator: ISDN User Part used all the way ISDN access indicator: originating access non-ISDN FCI is mapped to XML PI#3 PI#3 c PI#3 FCI ISDN User Part indicator: ISDN User Part used all the way ISDN access indicator: originating access ISDN ATP: PI#3 FCI is mapped to XML PI#6 ATP is mapped to XML PI#3 PI#3 d PI#1 FCI ISDN User Part indicator: ISDN User Part used all the way ISDN access indicator: originating access ISDN ATP: PI#1 FCI is mapped to XML PI#6 ATP is mapped to XML PI#1 PI#1 e - - PI#6 f - - PI#6 g - - - BC = 3,1 kHz and PI#1 h PI#3 - - XML PI#6 XML PI#3 PI#3 i PI#1 - - XML PI#6 XML PI#1 PI#1 j - - - PI#1 ETSI ETSI TS 183 036 V3.7.1 (2021-02) 152 IMS AGCF AGCF IMS SIP with XML SIP with XML NT2 NT2 S/T SETUP INVITE PI#6 INVITE PI#6 SETUP CALL PROCEEEDING PI#1 183 PI#7 + PI#1 183 PI#7 + PI#1 PROGRESS PI#1 ALERTING 180 PI#7 180 PI#7 ALERTING 200 OK PI#7 200 OK PI#7 CONNECT CONNECT CALL PROCEEDING Non-ISDN Network Figure H-2: Interworking situation IMS, an ISDN (PES) user is calling an ISDN (PES) user IMS AGCF AGCF/P-CSCF IMS SIP with XML SIP with XML NT2 NT2 S/T SETUP non-ISDN INVITE PI#6 SETUP CALL Proceeding PI#1 183 PI#7 + PI#1 183 PI#7 + PI#1 PROGRESS PI#1 ALERTING 180 PI#7 180 PI#7 ALERTING 200 OK PI#7 200 OK PI#7 CONNECT CONNECT NOTIFY or PROGRESS PI#8 Notification call has been Forwarded (Note 1) (Note 2) INVITE PI#6 181 VGW VGW non-ISDN non-ISDN network NOTE 1: The sending of a notification is a subscription option. NOTE 2: The PROGRESS message will be sent in the case of early media. Figure H-3: interworking situation IMS, an ISDN (PES) user is calling a non-ISDN (PES) user which forwarded the call to an ISDN (PES) user. The non-ISDN (PES) user is connected to a VGW which is not supporting XML ETSI ETSI TS 183 036 V3.7.1 (2021-02) 153 IMS AGCF MGCF IMS SIP with XML SIP with XML NT2 NT2 S/T SETUP INVITE PI#6 INVITE PI#6 SETUP CALL Proceeding PI#2 183 PI#7 + PI#2 183 PI#7 + PI#2 Progress PI#2 ALERTING 180 180 ALERTING 200 OK 200 OK CONNECT CONNECT IAM ACM with BCI ATP#2‚ CPG without BCI ANM without BCI ISUP TDM Switch non-ISDN Figure H-4: Interworking situation IMS to TDM, an ISDN (PES) user is calling an ISDN user with an PBX which has a non-ISDN access IMS AGCF MGCF IMS SIP with XML SIP with XML NT2 NT2 S/T SETUP non-ISDN INVITE PI#6 INVITE PI#6 181 CFU 181 CFU NOTIFY call has been forwarded SETUP CALL Proceeding PI#2 183 PI#7 + PI#2 183 PI#7 + PI#2 Progress PI#2 ALERTING 180 180 ALERTING 200 OK 200 OK CONNECT CONNECT IAM ACM CFU with BCI CPG with BCI ATP#2 CPG ANM SIP-I TDM Switch T non-ISDN Figure H-5: Interworking situation IMS to TDM, an ISDN (PES) user is calling an non-ISDN user which forwarded the call to an ISDN user with an PBX which has a non-ISDN access. The ISDN user is in the same switch ETSI ETSI TS 183 036 V3.7.1 (2021-02) 154 Annex I (informative): Bibliography • ETSI ES 283 003 (V1.8.0): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP) Stage 3 [3GPP TS 24.229 (Release 7), modified]". • ETSI EN 300 485 (V1.2.3): "Integrated Services Digital Network (ISDN); Definition and usage of cause and location in Digital Subscriber Signalling System No. One (DSS1) and Signalling System No.7 ISDN User Part (ISUP) [Recommendation ITU-T Q.850 (1998), modified]". ETSI ETSI TS 183 036 V3.7.1 (2021-02) 155 Annex J (informative): Change History Change history Date WG Doc. CR Re v CA T Title/Comment Current Version New Version 10-06-09 21WTD028 001 B Input draft for Release 3 2.1.1 3.0.0 10-06-09 21WTD028r1 002 B Service related changes to align with ETSI TS 183 043 (PES) 3.0.0 3.0.1 20-08-09 20bTD51r1 003 F Error in clause 5.1.1.2.1.3. 3.1.0 3.1.1 20-08-09 20bTD52r2 004 F Error in clause 5.1.1.2.2.3. 3.1.0 3.1.1 20-08-09 20bTD53r1 005 F Error in annex B 3.1.0 3.1.1 20-08-09 20bTD54r1 006 F Error in annex references in text 3.1.0 3.1.1 20-08-09 20bTD55r1 007 F Error in order of multiple BCs 3.1.0 3.1.1 20-08-09 20bTD56r1 008 D Editorial corrections for PSTN XML. 3.1.0 3.1.1 20-08-09 20bTD57r1 009 F Repeated table row in table 5.1.2.1-2. 3.1.0 3.1.1 Update of change history annex to correctly reflect CRs 001 and 002 and update of WI reference 3.1.1 3.1.2 29-09-09 22WTD44r1 010 F Error in clause 5.1.1.2.2.3. 3.1.2 3.1.3 29-09-09 22WTD45r1 011 D Additions to Definitions clause. 3.1.2 3.1.3 29-09-09 22WTD175r1 012 F Error in reference to annex. 3.1.2 3.1.3 CRS 010 to 012 TB approved at TISPAN#22 3.1.3 3.2.0 05-11-09 22bTD31r1 013 F Error in clause 5.1.2.2. 3.2.0 3.2.1 05-11-09 22bTD32r1 014 F Premature fall-back. 3.2.0 3.2.1 05-11-09 22bTD40r2 015 B CCBS/CCNR changes and mapping of cause <-> SIP response codes. 3.2.0 3.2.1 05-11-09 22bTD43r1 016 C AOC changes for multiple call legs 3.2.0 3.2.1 16-12-09 23WDT033r1 017 F Errors in clause 5.1.1.4 3.2.1 3.2.2 16-12-09 23WDT036r1 018 F Errors in References 3.2.1 3.2.2 16-12-09 23WDT040r3 019 F Correction of assorted typos/errors 3.2.1 3.2.2 16-12-09 23WDT0139r 1 020 F Sending of multiple Pis to DSS1 3.2.1 3.2.2 02-02-10 TISPAN3(10) 0009r2 021 F Reception of Pis. 3.2.2 3.2.3 Publication 3.2.3 3.3.1 27-10-10 TISPAN(10)0 202r1 022 D Corrections & Clarifications 3.3.1 3.3.2 Publication 3.3.2 3.4.1 02-08-12 Publication 3.4.2 3.5.1 ETSI ETSI TS 183 036 V3.7.1 (2021-02) 156 History Document history V2.1.1 January 2009 Publication V3.3.1 April 2010 Publication V3.4.1 February 2011 Publication V3.5.1 August 2012 Publication V3.6.1 June 2019 Publication V3.6.2 April 2020 Publication V3.7.1 February 2021 Publication
|
4cc63473e1390ddeb8fec0b111f7887f
|
183 060
|
1 Scope
|
The present document defines a specification based on DIAMETER for use at the Re Reference Point between the TISPAN NGN Access-Resource Admission Control Function (A-RACF) and the Resource Control Enforcement Function (RCEF). Whenever it is possible the present document specifies the requirements for this protocol by reference to specifications produced by the IETF within the scope of DIAMETER. Where this is not possible, extensions to DIAMETER are defined within the present document.
|
4cc63473e1390ddeb8fec0b111f7887f
|
183 060
|
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.
|
4cc63473e1390ddeb8fec0b111f7887f
|
183 060
|
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 003 (V2.0.0): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control Sub-System (RACS): Functional Architecture". [2] IETF RFC 2960: "Stream Control Transmission Protocol". [3] IETF RFC 3588: "Diameter Base Protocol". [4] IETF RFC 3309: "Stream Control Transmission Protocol (SCTP) Checksum Change". [5] IETF RFC 3554: "On the Use of Stream Control Transmission Protocol (SCTP) with IPSec". [6] ITU-T NGN-GSI/DOC - 127: "ITU-Telecommunication Standardization Sector, Draft Recommendation Q.rcp3.3 - Diameter Alternative Version 0.2.0". [7] ETSI TS 129 212: "Universal Mobile Telecommunications System (UMTS); LTE; Policy and charging control over Gx reference point (3GPP TS 29.212)". [8] IETF RFC 4006 (2005): "Diameter Credit-Control Application". [9] ETSI TS 129 209 (V6.7.0): "Universal Mobile Telecommunications System (UMTS); Policy control over Gq interface (3GPP TS 29.209)". ETSI ETSI TS 183 060 V2.1.1 (2009-04) 7 [10] IETF RFC 4005 (2005): "Diameter Network Access Server Application". [11] IANA Private Enterprise Numbers. NOTE: See http://www.iana.org/assignments/enterprise-numbers [12] ETSI ES 283 026 (V2.4.1): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control; Protocol for QoS reservation information exchange between the Service Policy Decision Function (SPDF) and the Access-Resource and Admission Control Function (A-RACF) in the Resource and Protocol specification" . [13] IETF RFC 5431 (2009):"Diameter ITU-T Rw Policy Enforcement Interface Application". [14] ETSI TS 129 207: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Policy control over Go interface (3GPP TS 29.207)".
|
4cc63473e1390ddeb8fec0b111f7887f
|
183 060
|
2.2 Informative references
|
The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. [i.1] ITU-T Recommendation Q.3303.3: "Protocol at the interface between the policy decision physical entity (PD-PE) and the policy enforcement physical entity (PE-PE) (Rw interface): Diameter". [i.2] ETSI TS 129 210: "Universal Mobile Telecommunications System (UMTS); Charging rule provisioning over Gx interface (3GPP TS 29.210)".
|
4cc63473e1390ddeb8fec0b111f7887f
|
183 060
|
3 Definitions and abbreviations
| |
4cc63473e1390ddeb8fec0b111f7887f
|
183 060
|
3.1 Definitions
|
For the purposes of the present document, the following terms and definitions apply: activation: operation of binding a Policy-Rule to a Transport Resource based on the transport resource classifier Attribute-Value Pair (AVP): corresponds to an Information Element in a DIAMETER message NOTE: See RFC 3588 [3]. deactivation: operation of un-binding a Policy-Rule to a Transport Resource dynamic policy rule: subcategory of policy rules in which the ownership belongs to the A-RACF and any installation/modification/removal of the policy are performed using Re interface Explicit Event Subscription: model for Event Subscription in which the A-RACF explicitly subscribes for the notification of particular event(s) Implicit Event Subscription: model for Event Subscription in which the list of event(s) that needs to be reported to the A-RACF is configured on the RCEF installation: operation of providing a new, non-existing, Policy-Rule to the RCEF modification: operation of modifying an existing Policy-Rule(s), providing a new Policy-Rule(s), or removing an existing Policy-Rule associated with a Transport Resource ETSI ETSI TS 183 060 V2.1.1 (2009-04) 8 Policy Rule: QoS Policy which defines how the data traffic should be handled by the RCEF, including: • cata traffic classification definition; • traffic forwarding definition based on the classification; • traffic statistics generation definition based on the classification. Provisioned Policy Rule: subcategory of policy rules in which the ownership belongs to the provisioning system and any installation/ modification/ removal of the policy can only be triggered by the provisioned system removal: operation of removing an existing Policy-Rule in the RCEF Transport Resource: Network Element on which a Policy Rule needs to be activated Transport Resource Classifier: parameter or set of parameters identifying a given Transport Resource
|
4cc63473e1390ddeb8fec0b111f7887f
|
183 060
|
3.2 Abbreviations
|
For the purposes of the present document, the following abbreviations apply: ABNF Augmented Backus-Naur Form AF Application Function A-RACF Access-Resource and Admission Control Function AVP Attribute-Value Pair CCA Credit-Control Answer CCR Credit-Control Request CEA Capabilities-Exchange-Answer CER Capabilities-Exchange-Request IANA Internet Assigned Numbers Authority IETF Internet Engineering Task Force PIA Policy-Install-Answer PIR Policy-Install-Request RACF Resource and Admission Control Function RACS Resource and Admission Control Subsystem RCEF Resource Control Enforcement Function RFC Request For Comments SCTP Stream Control Transport Protocol SPDF Service-based Policy Decision Function
|
4cc63473e1390ddeb8fec0b111f7887f
|
183 060
|
4 Overview
|
The Resource Control Enforcement Function (RCEF) defined in ES 282 003 [1] performs policy enforcement functions under control of the A-RACF. The RCEF main functions are: • Enforcement of the policies defined by the access provider. • Οpening and closing of gates in order to allow only authorized traffic to flow; marks IP packets in accordance with the filtering criteria received from the A-RACF. Policing of upstream and downstream traffic to ensure that the traffic remains within the authorized limits. The traffic policies are provided by the A-RACF to the RCEF through the Re reference point. ETSI ETSI TS 183 060 V2.1.1 (2009-04) 9 Rr x-RACF AF SPDF BGF RCEF NASS Re Ia Gq’ Rd’, Ri’ Rq e4 Transport Processing Functions RACS BTF Rf Scope of the Present Specification Figure 1: RACS Reference Model
|
4cc63473e1390ddeb8fec0b111f7887f
|
183 060
|
5 Procedure descriptions
| |
4cc63473e1390ddeb8fec0b111f7887f
|
183 060
|
5.1 General
|
The following clauses describe the realization of the functional procedures of the Re Reference Point (defined in the RACS specification ES 282 003 [1]) using the Diameter commands described in clause 7.1. This involves describing a mapping between the Information Elements defined in the RACS specification (ES 282 003 [1]) and DIAMETER AVPs. Procedures across the Re Reference Point can be divided into two categories: • A-RACF initiated procedures (push mode): Policy operations are initiated by A-RACF. A-RACF decides on the appropriate traffic policies and activates those in RCEF. • RCEF initiated procedures (pull mode): Policy operations are initiated by RCEF. In response to a request from RCEF, A-RACF shall decide on and activate the appropriate traffic policies in RCEF. ETSI ETSI TS 183 060 V2.1.1 (2009-04) 10 Figure 2 illustrates the policy-rule life cycle for provisioned type of policy-rules and various states the policy-rule may go through. NOTE 1: Install/Modify/remove transitions may be initiated by the provisioning systems or the network element management system. The details of such interface is outside the scope of the present document. NOTE 2: Activate/Deactivate transitions are initiated using the Re interface. NOTE 3: The activation operation may result in applying quality of service [QoS] parameters and procedures defined in the policy rule to the transport resource. NOTE 4: The deactivation process results in unbinding a policy from the network transport resource. Figure 2: Policy rule life cycle (Provisioned) Figure 3 illustrates the policy-rule life cycle for Dynamic type of policy-rules and varies states it may go through. NOTE 1: Dynamic policy-rule can only exist on the RCEF if and only if it is associated with a transport resource through the interaction between A-RACF and RCEF. NOTE 2: "Deactivate" a policy rule can be a result of: - Modifying transport resource applied policy-rules. For detail on modification, see clause 5.2.1.3. - Terminating the transport resources session. NOTE 3: The activation operation may result in applying quality of service [QoS] parameters and procedures defined in the policy rule to the transport resource. Figure 3: Policy rule life cycle [Dynamic] Active Removed Install and Activate Deactivate Inactive Active Removed Install Modify Activate Deactivate Remove Remove ETSI ETSI TS 183 060 V2.1.1 (2009-04) 11
|
4cc63473e1390ddeb8fec0b111f7887f
|
183 060
|
5.2 A-RACF initiated procedures
| |
4cc63473e1390ddeb8fec0b111f7887f
|
183 060
|
5.2.1 Procedures at the A-RACF
| |
4cc63473e1390ddeb8fec0b111f7887f
|
183 060
|
5.2.1.1 High level description
|
The A-RACF is the DIAMETER Server. The policy operations that the A-RACF may support include the installation, activation, modification, deactivation and removal of Policy Rules on the RCEF: • In order to activate one or several Policy Rules, or to Install and Activate one or several Policy Rules, the A-RACF sends an initial Policy-Install-Request (PIR) Command containing at least one Policy Rule to the RCEF. The PI-Request-Type AVP contains the value INITIAL_REQUEST. Each Policy Rule is described in the Policy-Rule-Install AVP. The Policy-Rule-Install AVP shall contain a Policy-Rule-Definition AVP. At least one Transport Resource Classifier shall be included in the Policy-Rule-Definition AVP, in order to indicate the Transport Resource Classifier(s) associated with the Policy Rule(s). • In order to modify Policy Rule(s) previously activated on a given Transport Resource, the A-RACF sends a PIR Command with the PI-Request-Type AVP set to the value UPDATE_REQUEST. During the Modification procedure, a Policy Rule previously activated for the Transport Resource may be modified or deactivated and removed (uninstalled). • In order to deactivate and remove all Policy Rule(s) previously activated for given Transport Resource Classifier(s), the A-RACF sends a PIR Command to the RCEF, with the PI-Request-Type AVP set to TERMINATION_REQUEST. The Termination Request shall contain the Transport Resource Classifier(s). The A-RACF may query the RCEF for the currently activated Policy Rules: • Query of the supported Policy Rules. • Query of the list of Policy Rules associated with a given Transport Resource. • Query of the details of particular Policy Rules associated with a given Transport Resource.
|
4cc63473e1390ddeb8fec0b111f7887f
|
183 060
|
5.2.1.2 Initial Policy Installation Request
|
The Initial Policy Installation Request is a PIR command with the PI-Request-Type AVP set to INITIAL_REQUEST. The A-RACF shall include the Auth-Session-State AVP with the value NO_STATE_MAINTAINED (1) [3] to indicate implicitly terminated sessions. The A-RACF may include one or several Event-Trigger AVP(s) in order to subscribe to the notification of particular event(s). The Policy-Rule-Install AVP is used to describe the Policy Rule(s). The A-RACF shall include at least one Policy-Rule-Install AVP in the Initial PIR: • In order to install and activate a new Policy Rule, the Policy-Rule-Definition AVP shall be used: - Policy-Rule-Name AVP shall be included in the Policy-Rule-Definition AVP. - The Flow-Status AVP shall be included in the Policy-Rule-Definition AVP. The value shall be set to ENABLED-UPLINK (0) or ENABLED-DOWNLINK (1) in order to request the activation of the corresponding Policy Rule: ENABLED-UPLINK shall be used to describe a Policy Rule relative to the outgoing direction on the RCEF. ENABLED-DOWNLINK shall be used to describe a Policy Rule relative to the incoming direction on the RCEF. ETSI ETSI TS 183 060 V2.1.1 (2009-04) 12 If Policy Rules for each direction need to be specified, several Policy-Rule-Definition AVPs will be included. - The QoS-Information AVP may be included in the Policy-Rule-Definition AVP: The Max-Requested-Bandwidth-UL AVP and Traffic-Descriptor-UL AVP may be included in order to describe the bandwidth profile of a Policy-Rule-Definition AVP with a Flow-Status equal to ENABLED-UPLINK. The Max-Requested-Bandwidth-DL AVP and Traffic-Descriptor-DL AVP may be included in order to describe the bandwidth profile of a Policy-Rule-Definition AVP with a Flow-Status equal to ENABLED-DOWNLINK. The ToS-Traffic-Class AVP may be included in order to associate the Policy Rule with a Traffic Class: - The same ToS-Traffic-Class is associated with both the uplink and the downlink directions when both directions are used. - The Reporting-Level may be included in the Policy-Rule-Definition AVP. - The Precedence AVP shall be included in the Policy-Rule-Definition AVP. • In order to activate a specific Policy Rule predefined at the RCEF, Policy-Rule-Name AVP shall be used as a reference for that Policy Rule. • In order to activate a group of Policy Rules predefined at the RCEF, the Policy-Rule-Base-Name AVP may be used. In order to identify the Transport Resources to which the Policy Rule applies, the A-RACF shall include at least one of the following Transport Resource Classifiers within the Policy-Rule-Definition AVP: • Logical-Access-Id AVP in order to associate the Policy-Rule-Definition AVP(s) with a particular Logical-Access-Id. • Physical-Access-Id AVP in order to associate the Policy-Rule-Definition AVP(s) with a particular bearer resource upon which the Policies should be enforced. • Framed-IP-Address AVP in order to associate the Policy-Rule-Definition AVP(s) with a particular IP Session. - The Address-Realm AVP may be added if the Framed-IP-Address AVP is also included, in order to associate the Policy-Rule-Definition AVP(s) with a particular Globally Unique IP Address. • Called-Station-Id AVP in order to associate the Policy-Rule-Definition AVP(s) with a particular Transport Resource on the RCEF. • The User-Name AVP in order to associate the Policy-Rule-Definition AVP(s) with a particular End User. • Zero, one or several Flow-Description AVP(s) may be included in the Policy-Rule-Definition AVP, in order to associate a given Policy Rule with IP Flows. • ToS-Traffic-Class AVP in order to associate the Policy-Rule-Definition AVP(s) with a particular Traffic Class. • The A-RACF may include one or several of these Transport Resource Classifiers. - In case several Transport Resource Classifiers are included, they shall match with each others. ETSI ETSI TS 183 060 V2.1.1 (2009-04) 13
|
4cc63473e1390ddeb8fec0b111f7887f
|
183 060
|
5.2.1.3 Policy modification request
|
The Policy Modification Request is a PIR Command with the PI-Request-Type AVP with the value UPDATE_REQUEST. The A-RACF shall include the Auth-Session-State AVP with the value NO_STATE_MAINTAINED (1) [3]. The A-RACF may include one or several Event-Trigger AVP(s) in order to subscribe to the notification of particular event(s). Event-Trigger AVPs that were specified in the corresponding Initial PIR or in previous Policy Modification Requests, remain valid even if they are not specified in the Policy Modification Request. In order to remove a previously activated Policy Rule(s) associated with the Transport Resource, the A-RACF may include one or several Policy-Rule-Remove AVP(s) as main AVP(s): • In order to remove a Policy Rule previously activated on the Transport Resource, the A-RACF shall include the Policy-Rule-Name AVP in the Policy-Rule-Remove AVP. • In order to remove a group of Policy Rules previously activated on the Transport Resource, the A-RACF shall include the Policy-Rule-Base-Name AVP in the Policy-Rule-Remove AVP. In order to modify Policy Rules previously activated for the Transport Resource, the A-RACF may include one or several Policy-Rule-Install AVP(s) as main AVP(s): • The A-RACF shall include the Policy-Rule-Definition AVP: - The A-RACF shall include a known Policy-Rule-Name AVP. - The A-RACF may update the Policy-Rule-Definition. In particular, the A-RACF may instruct the RCEF to deactivate and remove a Policy Rule previously associated with the Transport Resource, by changing the Flow-Status in the Policy-Rule-Definition AVP to REMOVED. In order to install and activate new Policy Rule(s) on the RCEF, the A-RACF may include one or several Policy-Rule-Install AVP(s) as main AVP(s). • Each Policy-Rule-Install AVP shall be specified as described in clause 5.2.1.2. - In particular, the A-RACF shall include a new Policy-Rule-Name AVP. In order to activate Policy Rules pre-defined on the RCEF, the A-RACF may include one or several Policy-Rule-Install AVP(s) as main AVP(s). Each Policy-Rule-Install AVP shall be specified as follows: • Policy-Rule-Name AVP shall be used as a reference for that Policy Rule. • The Policy-Rule-Base-Name AVP shall not be included if the Policy-Rule-Name AVP is included. In order to activate a group of Policy Rules pre-defined on the RCEF, the A-RACF may include one or several Policy-Rule-Install AVP(s) as main AVP(s). Each Policy-Rule-Install AVP shall be specified as follows: • Policy-Rule-Base-Name AVP shall be used as a reference for that group of Policy Rules. • The Policy-Rule-Name AVP shall not be included if the Policy-Rule-Base-Name AVP is included.
|
4cc63473e1390ddeb8fec0b111f7887f
|
183 060
|
5.2.1.4 Policy termination request
|
In order to deactivate and remove all Policy Rule(s) previously activated on a Transport Resource, the A-RACF sends a PIR Command to the RCEF, with the PI-Request-Type AVP set to TERMINATION_REQUEST. The Policy Termination-Request shall include the Transport Resource Classifier of the corresponding Transport Resource. In the case of pre-defined Policy Rule on the RCEF (e.g. identified by Policy-Rule-Base-Name), the A-RACF may only be authorized to deactivate the pre-defined Policy Rule. ETSI ETSI TS 183 060 V2.1.1 (2009-04) 14
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.