D.4 XML schema for CS to PS SRVCC information

24.2373GPPIP Multimedia (IM) Core Network (CN) subsystem IP Multimedia Subsystem (IMS) service continuityRelease 17Stage 3TS

D.4.1 General

This subclause defines XML schema and MIME type for transfer of CS to PS SRVCC information.

D.4.2 XML schema

<?xml version="1.0"?>

<xs:schema

xmlns:xs="http://www.w3.org/2001/XMLSchema"

elementFormDefault="qualified"

attributeFormDefault="unqualified">

<xs:element name="srvcc-ext" type="srvcc-extType"/>

<xs:complexType name="srvcc-extType">

<xs:sequence>

<xs:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:element name="PS-reg-info" type="PS-reg-infoType"/>

<xs:complexType name="PS-reg-infoType">

<xs:sequence>

<xs:element name="ATCF-Management-URI" type="xs:anyURI" minOccurs="0"/>

<xs:element name="C-MSISDN" type="xs:anyURI" minOccurs="0"/>

<xs:element name="cs2ps-srvcc-alerting" type="xs:boolean" minOccurs="0"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:attribute name="Path" type="xs:anyURI" use="optional"/>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:element name="Setup-info" type="Setup-infoType"/>

<xs:complexType name="Setup-infoType">

<xs:sequence>

<xs:element name="C-MSISDN" type="xs:anyURI"/>

<xs:element name="direction" type="directionType"/>

<xs:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:simpleType name="directionType">

<xs:restriction base="xs:string">

<xs:enumeration value="initiator"/>

<xs:enumeration value="receiver"/>

</xs:restriction>

</xs:simpleType>

<xs:complexType name="anyExtType">

<xs:sequence>

<xs:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

</xs:complexType>

</xs:schema>

D.4.3 Semantic

D.4.3.1 General

The <srvcc-ext> element is the root element of the XML document. The <srvcc-ext> element can contain subelements.

NOTE: The subelements of the <srvcc-ext> are validated by the <xs:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> particle of the <srvcc-ext> element.

When the <srvcc-ext> element contains the <PS-reg-info> element, then the <PS-reg-info> element contains:

– if the information relates to a registration of MSC server with IMS, then the "Path" attribute identifying the MSC URI for terminating calls used by MSC server when registering the UE;

– optionally the <ATCF-Management-URI> element containing the ATCF management URI of the ATCF used in the registration path of the UE over a PS domain. Absence of this element indicates that the CS to PS SRVCC is disabled;

– optionally the <C-MSISDN> element containing the C-MSISDN of the served SC UE. Absence of this element indicates that the CS to PS SRVCC is disabled;

– the <cs2ps-srvcc-alerting> element indicates whether the CS to PS SRVCC of calls in alerting phase is supported by both the served SC UE and the SCC AS; and

– optionally, <anyExt> element containing elements defined by future version of this document.

When the <srvcc-ext> element contains the <Setup-info> element, then the <Setup-info> element contains:

– the <C-MSISDN> element containing the C-MSISDN of the served SC UE;

– the <direction> element indicating the role of the MSC server in the session set up.

Recipient of the XML ignores any unknown element and any unknown attribute.

D.4.4 IANA registration template

Your Name:

<MCC name>

Your Email Address:

<MCC email address>

Media Type Name:

Application

Subtype name:

vnd.3gpp.srvcc-ext+xml

Required parameters:

None

Optional parameters:

"charset" the parameter has identical semantics to the charset parameter of the "application/xml" media type as specified in section 9.1 of IETF RFC 7303.

Encoding considerations:

binary.

Security considerations:

Same as general security considerations for application/xml media type as specified in section 9.1 of IETF RFC 7303. In addition, this media type provides a format for exchanging information in SIP, so the security considerations from IETF RFC 3261apply.

The information transported in this media type does not include active or executable content.

Mechanisms for privacy and integrity protection of protocol parameters exist. Those mechanisms as well as authentication and further security mechanisms are described in 3GPP TS 24.229.

This media type does not include provisions for directives that institute actions on a recipient’s files or other resources.

This media type does not include provisions for directives that institute actions that, while not directly harmful to the recipient, may result in disclosure of information that either facilitates a subsequent attack or else violates a recipient’s privacy in any way.

This media type does not employ compression.

Interoperability considerations:

Same as general interoperability considerations for application/xml media type as specified in section 9.1 of IETF RFC 7303. Any unknown XML elements and any unknown XML attributes are to be ignored by recipient of the MIME body.

Published specification:

3GPP TS 24.237 "IP Multimedia Subsystem (IMS) Service Continuity", version 13.1.0, available via http://www.3gpp.org/specs/numbering.htm.

Applications which use this media type:

Applications supporting the service continuity as described in the published specification.

Fragment identifier considerations:

The handling in section 5 of IETF RFC 7303 applies.

Restrictions on usage:

None

Provisional registration? (standards tree only):

N/A

Additional information:

1. Deprecated alias names for this type: none

2. Magic number(s): none

3. File extension(s): none

4. Macintosh File Type Code(s): none

5. Object Identifier(s) or OID(s): none

Intended usage:

Common

Person to contact for further information:

– Name: <MCC name>

– Email: <MCC email address>

– Author/Change controller:

i) Author: 3GPP CT1 Working Group/3GPP_TSG_CT_WG1@LIST.ETSI.ORG

ii) Change controller: <MCC name>/<MCC email address>