7.5.11 CCBS/CCNR

29.1633GPPInterworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched (CS) networksTS

7.5.11.0 General

The protocol specification of the Completion of Communications to Busy Subscriber and Completion of Communications by No Reply supplementary services is described in 3GPP TS 24.642 [112].

SIP SUBSCRIBE and NOTIFY methods shall be used in accordance with the procedures defined in IETF RFC 6665 [138].

7.5.11.1 Interworking at the I-MGCF

If the I-MGCF supports the interworking of CCBS/CCNR supplementary services, the I-MGCF shall map between the SIP and ISUP messages in accordance with table 7.5.11.1.1.

Table 7.5.11.1.1: Mapping of ISUP and SIP messages

SIP Message

Parameter

ISUP Message

Parameter

← 180 Ringing

Call-Info header field with purpose header field parameter set to "call-completion" and "m" header field parameter set to "NR" (no reply)
(NOTE 1)

← ACM

Called party’s status indicator set to "Subscriber free" and

CCNR possible indicator set to "CCNR possible"
(NOTE 2)

← 180 Ringing

Call-Info header field with purpose header field parameter set to "call-completion and "m" header field parameter set to "NR" (no reply)

(NOTE 1)

← CPG

Event indicator set to "Alerting" and

CCNR possible indicator set to "CCNR possible"
(NOTE 2)

← 486 Busy here

Call-Info header field with purpose header field parameter set to "call-completion" and "m" header field parameter set to "BS" (busy subscriber)

(NOTE 1)

← REL

Cause Indicator
cause #17 with Diagnostic (CCBS indicator set to "CCBS possible")
(NOTE 3)

→ INVITE

Request-URI contains "m" SIP URI parameter or Call-Info header field contains "purpose" header field parameter set to "call-completion" and "m" header field parameter.
(NOTE 1)

→ IAM

CCSS parameter set to "CCSS call"
(NOTE 2) (NOTE 4)

NOTE 1: The coding shall be in accordance with IETF RFC 6910 [106].

NOTE 2: The coding shall be in accordance with ITU-T recommendation Q.763 [4].

NOTE 3: The coding shall be in accordance with ITU-T recommendation Q.850 [38].

NOTE 4: CCSS parameter set to the value "CCSS call" is included in the IAM if Request-URI contains the SIP URI parameter "m" i.e. creation of the CCSS parameter does not depend on the received value of the SIP URI parameter "m".

If the I-MGCF supports the interworking of CCBS/CCNR supplementary services, the I-MGCF shall map between the SIP and TCAP messages in accordance with table 7.5.11.1.2 and table 7.5.11.1.3.

Table 7.5.11.1.2: Mapping of SIP messages to TCAP messages

SIP Message

Parameter

TCAP Message

Parameter

SUBSCRIBE with m-parameter in Request-URI set to "BS" or containing Call-Info header field with "purpose" parameter set to "call-completion" and m-parameter set to "BS"
(NOTE 1)

Request-URI (NOTE 5)

TC-Begin CCBS REQUEST (invoke)

CalledPartyNumber (NOTE 3)

P-Asserted-Identity

CallingPartyNumber (NOTE 4)

RetainSupported (NOTE 2)

SUBSCRIBE with m-parameter in Request-URI set to "NR" or containing Call-Info header field with "purpose" parameter set to "call-completion" and m-parameter set to "NR"
(NOTE 1)

Request-URI (NOTE 5)

TC-Begin CCNR REQUEST (invoke)

CalledPartyNumber (NOTE 3)

P-Asserted-Identity

CallingPartyNumber (NOTE 4)

RetainSupported (NOTE 2)

PUBLISH with m-parameter in Request-URI or m-parameter in Call-Info header field set to "BS" and body containing PIDF basic status set to "closed".

TC-Cont CCBS SUSPEND

PUBLISH with m-parameter in Request-URI or m-parameter in Call-Info header field set to "BS" and body containing PIDF basic status set to "open".

TC-Cont CCBS RESUME

PUBLISH with m-parameter in Request-URI or m-parameter in Call-Info header field set to "NR" and body containing PIDF basic status set to "closed".

TC-Cont CCBS SUSPEND

PUBLISH with m-parameter in Request-URI or m-parameter in Call-Info header field set to "NR" and body containing PIDF basic status set to "open".

TC-Cont CCBS RESUME

SUBSCRIBE with m-parameter in Request-URI or m-parameter in Call-Info header field set to "BS" and with Expires header set to "zero".

TC-End CCBS CANCEL

SUBSCRIBE with m-parameter in Request-URI or m-parameter in Call-Info header field set to "NR" and with Expires header set to "zero".

TC-End CCBS CANCEL

NOTE 1: Expires header defines subscription duration / CC service duration timer (CC-T3).

NOTE 2: Parameter is set by default, as retention option is supported in IMS by default.

NOTE 3: Mapping of the Request-URI to the CalledPartyNumber is done according to table 2 in clause 7.2.3.1.2.1.

NOTE 4: Mapping of the P-Asserted-Identity header field to the CallingPartyNumber is done according to table 5 in clause 7.2.3.1.2.6.

NOTE 5: If URI of the MGCF was returned in the Call-Info header field in the 180 Ringing or 486 Busy Here messages described in table 7.5.11.1.1, then the MGCF needs to remember the Request-URI of the original INVITE for mapping to the CalledPartyNumber.

Table 7.5.11.1.3: Mapping of TCAP messages to SIP messages

TCAP Message

Parameter

SIP Message

Parameter

TC-Cont CCBS REQUEST (return result)

RetainSupported

NOTIFY with cc-state parameter set to "queued"

cc-service-retention

TC-End CCBS/CCNR REQUEST (error result)

ShortTermDenial

480 Temporarily Unavailable

TC-End CCBS/CCNR REQUEST (error result)

LongTermDenial

403 Forbidden

TC-End CCBS CANCEL

NOTIFY with the "reason" Subscription-State header field parameter set to "noresource"

TC-Cont REMOTE USER FREE

NOTIFY with cc-state set to "ready" (NOTE)

NOTE: This does not terminate the subscribtion AS-AS.

7.5.11.2 Interworking at the O-MGCF

If the O-MGCF supports the interworking of CCBS/CCNR supplementary services, the O-MGCF shall map between the ISUP and SIP messages in accordance with table 7.5.11.2.1.

Table 7.5.11.2.1: Mapping of SIP and ISUP messages

ISUP Message

Parameter

SIP Message

Parameter

← ACM

Called party’s status indicator set to "Subscriber free" and

CCNR possible indicator set to "CCNR possible"
(NOTE 2)

← 180 Ringing

Call-Info header field with purpose header field parameter set to "call-completion"
(NOTE 1)

← CPG

Event indicator set to "Alerting" and

CCNR possible indicator set to "CCNR possible"
(NOTE 2) (NOTE 4)

← REL

Cause Indicator
cause #17 or #34 with Diagnostic (CCBS indicator set to "CCBS possible")
(NOTE 3)

← 486 Busy here

Call-Info header field with purpose header field parameter set to "call-completion"
(NOTE 1)

→ IAM

CCSS parameter set to "CCSS call"
(NOTE 2)

→ INVITE

Request URI contains m-parameter and a Call-Info header field field, with purpose header field parameter set to "call-completion", and an m-parameter
(NOTE 1) (NOTE 5)

NOTE 1: The coding shall be in accordance with IETF RFC 6910 [106].

NOTE 2: The coding shall be in accordance with ITU-T recommendation Q. 763 [4].

NOTE 3: The coding shall be in accordance with ITU-T recommendation Q. 850 [38].

NOTE 4: A CPG will be sent if an ACM was already sent.

NOTE 5: Based on the operator policy the "m" SIP URI parameter in the Request-URI and m-parameter in Call-Info header field is set to the value "BS" or "NR".

If the O-MGCF supports the interworking of CCBS/CCNR supplementary services, the O-MGCF shall map between the TCAP and SIP messages in accordance with table 7.5.11.2.2 and table 7.5.11.2.3.

Table 7.5.11.2.2: Mapping of TCAP messages to SIP messages

TCAP Message

Parameter

SIP Message

Parameter

TC-Begin CCBS REQUEST (invoke)

CalledPartyNumber

SUBSCRIBE with m-parameter in Request URI and m-parameter in Call-Info header field set to "BS" (NOTE 1)

To header (NOTE 2)

Request-URI (NOTE 2)

CallingPartyNumber

From header (NOTE 3)

P-Asserted-Identity (NOTE 4)

TC-Begin CCNR REQUEST (invoke)

CalledPartyNumber

SUBSCRIBE with m-parameter in Request URI and m-parameter in Call-Info header field set to "NR" (NOTE 1)

To header (NOTE 2)

Request-URI (NOTE 2)

CallingPartyNumber

From header (NOTE 3)

P-Asserted-Identity (NOTE 4)

TC-Cont CCBS SUSPEND

PUBLISH with m-parameter in Request URI and m-parameter in Call-Info header field set to "BS" and body containing PIDF basic status set to "closed".

PUBLISH with m-parameter in Request URI and m-parameter in Call-Info header field set to "NR" and body containing PIDF basic status set to "closed".

TC-Cont CCBS RESUME

PUBLISH with m-parameter in Request URI and m-parameter in Call-Info header field set to "BS" and body containing PIDF basic status set to "open".

PUBLISH with m-parameter in Request URI and m-parameter in Call-Info header field set to "NR" and body containing PIDF basic status set to "open".

TC-End CCBS CANCEL

SUBSCRIBE with m-parameter in Request URI and m-parameter in Call-Info header field set to "BS" and with Expires header set to "0"

SUBSCRIBE with m-parameter in Request URI and m-parameter in Call-Info header field set to "NR" and with Expires header set to "0"

NOTE 1: Expires header defines subscription duration / CC service duration timer (CC-T3).

NOTE 2: For the mapping of the CalledPartyNumber to the To header and Request-URI see table 10a in clause 7.2.3.2.2.1.

NOTE 3: For the mapping of the CallingPartyNumber to the From header see table 15 in clause 7.2.3.2.2.3. If no CallingPartyNumber is available, the From header shall be set to a SIP URI with addr-spec of Unavailable User Identity as defined in TS 23.003 [74].

NOTE 4: For the mapping of the CallingPartyNumber to the P-Asserted-Identity header see table 14 in clause 7.2.3.2.2.3. If no CallingPartyNumber is available, a P-Asserted-Identity header shall not be inserted.

Table 7.5.11.2.3: Mapping of SIP messages to TCAP messages

SIP Message

Parameter

TCAP Message

Parameter

NOTIFY with cc-state parameter set to "queued"

cc-service-retention

TC Cont CCBS/CCNR REQUEST (return result)

RetainSupported

480 Temporarily unavailable

TC-End CCBS/CCNR REQUEST (error result)

ShortTermDenial

403 Forbidden

TC-End CCBS/CCNR REQUEST (error result)

LongTermDenial

NOTIFY with the Subscription-State header field set to "terminated" and the "reason" parameter set to "noresource"

TC-End CCBS CANCEL

NOTIFY with cc-state set to "ready" (NOTE)

TC-Cont REMOTE USER FREE

NOTE: This does not terminate the subscription AS-AS.