C.2 IUT transfer feature XML schema

24.3373GPPIP Multimedia (IM) Core Network (CN) subsystem IP Multimedia Subsystem (IMS) inter-UE transferRelease 17Stage 3TS

C.2.1 General

This subclause defines XML schema and MIME type related to the IUT transfer features.

C.2.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:element name="controlTransfer" type="TcontrolTransfer"/>

<xs:complexType name="TcontrolTransfer">

<xs:sequence>

<xs:element name="controllee" type="xs:anyURI" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="targetController" type="xs:anyURI" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="activeController" type="xs:anyURI" minOccurs="0" maxOccurs="unbounded"/>

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

</xs:sequence>

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

</xs:complexType>

</xs:schema>

C.2.3 IANA registration template

Editor’s note: The MIME type "application/vnd.3gpp.iut+xml" as defined in this subclause is to be registered in the IANA registry for Application Media Types based upon the following template.

MIME media type name:

application

MIME subtype name:

application/vnd.3gpp.iut+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 IETF RFC 3023 [29].

Encoding considerations:

binary.

Security considerations:

Same as general security considerations for application/xml as specified in section 10 of IETF RFC 3023 [29]. In addition, this content type provides a format for exchanging information in SIP, so the security considerations from IETF RFC 3261 [30] apply.

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

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

Interoperability considerations:

Same as interoperability considerations as specified in section 3.1 of IETF RFC 3023 [29].

Published specification:

3GPP TS 24.337: "IP Multimedia Subsystem (IMS) inter-UE transfer; Stage 3", available via http://www.3gpp.org/specs/numbering.htm.

Applications which use this media:

Applications supporting the Inter UE Transfer as described in the published specification.

Intended usage:

COMMON

Additional information:

1. Magic number(s): none

2. File extension(s): none

3. Macintosh file type code: none

4. Object Identifiers: none