D.3 SRVCC enhancement related XML schema

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

D.3.1 General

This subclause defines XML schema and MIME type for transfer of information for SRVCC enhancement.

D.3.2 XML schema

<?xml version="1.0" encoding="UTF-8"?>

<xs:schema

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

elementFormDefault="qualified"

attributeFormDefault="unqualified">

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

<xs:sequence>

<xs:element name="ATU-STI" type="xs:anyURI" minOccurs="0"/>

<xs:element name="C-MSISDN" type="xs:anyURI" 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="ATCF-Path-URI" type="xs:anyURI"/>

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

</xs:complexType>

<xs:complexType name="SRVCC-infosType">

<xs:sequence>

<xs:element name="SRVCC-info" type="SRVCC-infoType"

minOccurs="1" maxOccurs="unbounded"/>

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

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

</xs:sequence>

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

</xs:complexType>

<xs:element name="SRVCC-infos" type="SRVCC-infosType"/>

<xs:complexType name="anyExtType">

<xs:sequence>

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

</xs:sequence>

</xs:complexType>

<xs:element name="CS2PS-ATU-STI" type="xs:anyURI"/>

</xs:schema>

D.3.3 Semantic

The <SRVCC-infos> element is the root element of the XML document and contains one or more <SRVCC-info> elements.

Each <SRVCC-info> element contains SRVCC-related information related to one registration path (or registration flow, if multiple registration mechanism is used) of a UE with IM CN subsystem. The SRVCC-related information in the <SRVCC-info> element consists of:

1) if the PS to CS SRVCC is usable for the UE (see subclause 6.3.2):

a) <ATU-STI> element containing the ATU-STI for PS to CS SRVCC of the SCC AS; and

b) <C-MSISDN> element containing the Correlation MSISDN of the UE; and

NOTE 1: <ATU-STI> element and <C-MSISDN> element are not included unless the PS to CS SRVCC is usable for the UE (see subclause 6.3.2).

2) if CS to PS SRVCC is supported by SCC AS and enabled for the UE:

a) <anyExt> element containing <CS2PS-ATU-STI> element containing the ATU-STI for CS to PS SRVCC of the SCC AS; and

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

b) <C-MSISDN> element containing the C-MSISDN of the UE.

NOTE 3: If information for both CS to PS SRVCC and PS to CS SRVCC are included, <C-MSISDN> element is included only once.

The "ATCF-Path-URI" attribute of the <SRVCC-info> element contains the ATCF URI for terminating calls of the registration path (or registration flow, if multiple registration mechanism is used).

<anyExt> element contains optional elements defined by future version of this document.

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

D.3.4 IANA registration template

Your Name:

<MCC name>

Your Email Address:

<MCC email address>

Media Type Name:

Application

Subtype name:

vnd.3gpp.SRVCC-info+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>