7.5.9 Malicious Communication Identification (MCID)

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

7.5.9.0 General

The protocol specification of the Malicious Communication Identification supplementary service is described in 3GPP TS 24.616 [102]. The XML MCID body used in related SIP messages is also specified in 3GPP TS 24.616 [102].

7.5.9.1 Interworking at the O-MGCF

7.5.9.1.0 General

If the MGCF supports the interworking of the MCID service the O-MGCF shall map a SIP INFO request ("legacy" mode of usage of the INFO method as defined in IETF RFC 6086 [133]) containing a XML mcid body with MCID XML Request schema to an Identification Request (IDR) message and an Identification response (IRS) message to a SIP INFO request containing a XML mcid body with MCID XML Response schema in accordance with table 7.5.9.1.1.

The IDR message shall be generated upon reception of the SIP INFO request containing a XML mcid body with MCID XML Request schema.

The SIP INFO request containing a XML mcid body with MCID XML Response schema shall be generated upon reception of the IRS message.

Table 7.5.9.1.1 Mapping between ISUP IDR and IRS and SIP messages

ISUP Message

SIP Message

IDR

INFO containing a XML mcid body with MCID XML Request schema

IRS

INFO containing a XML mcid body with MCID XML Response schema

7.5.9.1.1 Interworking of the MCID XML Request schema with the ISUP MCID request indicators

If the MGCF supports the interworking of the MCID service O-MGCF shall map the codes in the MCID XML elements to MCID request indicator and holding indicator parameter fields in accordance with table 7.5.9.1.1.1.

Table 7.5.9.1.1.1 Mapping between ISUP MCID request and holding indicators and MCID XML elements

ISUP Parameter

XML Element

bit A:

MCID request indicator

McidRequestIndicator

0

MCID not requested

type=0

1

MCID requested

type=1

bit B:

Holding indicator (national use)

HoldingIndicator

0

holding not requested

type=0

1

holding requested

type=1

7.5.9.1.2 Interworking of the ISUP MCID response indicators with the MCID XML Response schema

If the MGCF supports the interworking of the MCID service the O-MGCF shall map the codes in the MCID response indicator and hold provided indicator parameter field to the MCID XML elements in accordance with table 7.5.9.1.2.1.

Table 7.5.9.1.2.1 Mapping between ISUP MCID response and hold provided indicators and MCID XML elements

ISUP Parameter

XML Element

bit A:

MCID response indicator

McidResponseIndicator

0

MCID not included

type=0

1

MCID included

type=1

bit B:

Hold provided indicator (national use)

HoldingProvidedIndicator

0

holding not provided

type=0

1

holding provided

type=1

7.5.9.1.3 Interworking of the ISUP Calling Party Number in an Identification Response with the OrigPartyIdentity within the MCID XML Response schema

If the O-MGCF supports the interworking of the MCID service and receives an ISUP Identification Response containing a Calling Party Number with the screening indicator set to "user provided, verified and passed" or "network provided", the O-MGCF shall map the Calling Party Number to the MCID XML Response schema OrigPartyIdentity element applying the same mapping procedures as described in table 14 for the mapping into the SIP P-Asserted-Identity header and shall map the Calling Party Number APRI to the MCID XML Response schema OrigPartyPresentationRestriction element. If the Calling Party Number APRI has a value of "presentation allowed" then the MCID XML Response schema OrigPartyPresentationRestriction element shall be set to "false", otherwise it shall be set to "true".

7.5.9.1.4 Interworking of the ISUP Generic Number in an Identification Response with the GenericNumber within the MCID XML Response schema

If the O-MGCF supports the interworking of the MCID service and receives an ISUP Identification Response containing a Generic Number with the screening indicator set to "user provided, verified and passed", or "user provided, not verified", or "network provided", the O-MGCF shall map the Generic Number to the MCID XML Response schema GenericNumber element applying the same mapping procedures as described in table 13 for the mapping into the SIP From header and shall map the Generic Number APRI to the MCID XML Response schema GenericNumberPresentationRestriction element. If the Generic Number APRI has a value of "presentation allowed" then the MCID XML Response schema GenericNumberPresentationRestriction element shall be set to "false", otherwise it shall be set to "true".

7.5.9.2 Interworking at the I-MGCF

7.5.9.2.1 General

If the MGCF supports the interworking of the MCID service the I-MGCF shall map an Identification Request (IDR) message to a SIP INFO request ("legacy" mode of usage of the INFO method as defined in IETF RFC 6086 [133]) containing a XML mcid body with MCID XML Request schema and a SIP INFO request containing a XML mcid body with MCID XML Response schema to an Identification response (IRS) message in accordance with table 7.5.9.1.1.

7.5.9.2.2 Interworking of identification Request

The SIP INFO request containing a XML mcid body with MCID XML Request schema shall be generated upon reception of the IDR message. The I-MGCF shall map the codes in the MCID request indicator and holding indicator parameter fields to the MCID XML elements in accordance with table 7.5.9.1.1.1.

7.5.9.2.3 Interworking of identification Response

The IRS message shall be generated upon reception of the SIP INFO request containing a XML mcid body with MCID XML Response schema. The I-MGCF shall map the codes in the MCID XML elements to the MCID response indicator and hold provided indicator parameter fields in accordance with table 7.5.9.1.2.1.

If the received MCID XML Response schema contains an OrigPartyIdentity element, the I-MGCF shall map the OrigPartyIdentity to the Calling Party Number within the IRS applying the same mapping procedure as described in table 5 for the mapping from the SIP P-Asserted-Identity header, with the exception that the I-MGCF shall map the MCID XML Response schema OrigPartyPresentationRestriction element to the Calling Party Number APRI. If the MCID XML Response schema OrigPartyPresentationRestriction element has the value "true", the Calling Party Number APRI shall be set to "presentation restricted", and otherwise the Calling Party Number APRI shall be set to "presentation allowed".

If the received MCID XML Response schema contains an GenericNumber element, the I-MGCF shall map the GenericNumber to the Generic Number within the IRS applying the same mapping procedure as described in table 6 for the mapping from the From header, with the exception that the I-MGCF shall map the MCID XML Response schema GenericNumber PresentationRestriction element to the Generic Number APRI. If the MCID XML Response schema GenericNumberPresentationRestriction element has the value "true", the Generic Number APRI shall be set to "presentation restricted", and otherwise the Generic Number APRI shall be set to "presentation allowed".