C.1 Short-messsage-info XML schema

24.3413GPPRelease 18Stage 3Support of SMS over IP networksTS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

C.1.1 General

This clause defines XML schema and MIME type related to SMS over IP MSISDN less operation.

C.1.2 application/vnd.3gpp.sms+xml

The MIME type is used to carry information related to the MSISDN less operation for SMS over IP. It is coded as an XML document and contains one or more of the following information:

– To

– From

– Correlation-ID

– Delivery-Outcome

NOTE: The information elements cannot be present twice in the XML body.

C.1.3 Data semantics

The <short-message-info> element is the root element of the XML document and contains one or more of the following elements:

1) a <To> element which contains the identity of the receiver of the short message, it is coded as a SIP URI;

2) a <From> element which contains the identity of the sender of the short message, it is coded as a SIP URI;

3) a <Correlation-ID> element which contains the Correlation Identifier to be used for interworking with the short message service center. The <Correlation-ID> consists of:

a) a <Sender> element containing the SIP URI of the sender of the short message that needs to be delivered via the short message centre, it is coded as SIP URI;

b) a <Receiver> element containing the SIP URI of the receiver of the short message that needs to be delivered via the short message centre, it is coded as SIP URI; and

c) a <HLR-ID> element containing the identifier of the HLR to be used for short message delivery reattempts. It is coded as string;

4) a <Delivery-Outcome> element which indicates the status for short message transfer, it is coded as a string. In the present document, it can only have the values specified in table C.1.3-1 for Delivery-Outcome-Values. The usage and semantics of the error indications is described in 3GPP TS 23.040 [3]

Table C.1.3-1: ABNF syntax of values of the <state-info> element

Delivery-Outcome-Values = SuccessfullTransfer-value / AbsentSubscriber-value / UserBusyForMTSMS-value / IllegalUser-value / IllegalEquipment-value -value / SMDeliveryFailure-value / ServiceBarred-value / TeleserviceNotProvisioned-value

SuccessfullTransfer-value = %x53.75.63.63.65.73.73.66.75.6c.6c.54.72.61.6e.73.66.65.72 ; "SuccessfullTransfer"

AbsentSubscriber-value = %x41.62.73.65.6e.74.53.75.62.73.63.72.69.62.65.72 ; "AbsentSubscriber"

UserBusyForMTSMS-value = %x55.73.65.72.42.75.73.79.46.6f.72.4d.54.53.4d.53 ; "UserBusyForMTSMS"

IllegalUser-value = %x49.6c.6c.65.67.61.6c.55.73.65.72; "IllegalUser"

IllegalEquipment-value = %x49.6c.6c.65.67.61.6c.45.71.75.69.70.6d.65.6e.74 ; "IlegalEquipment"

SMDeliveryFailure = %x53.4d.44.65.6c.69.76.65.72.79.46.61.69.6c.75.72.65 ; "SMDeliveryFailure"

ServiceBarred-value = %x53.65.72.76.69.63.65.42.61.72.72.65.64 ; "ServiceBarred"

TeleserviceNotProvisioned-value = %x54.65.6c.65.73.65.72.76.69.63.65.4e.6f.74.50.72.6f.76.69.73.69.6f.6e.65.64 ; "TeleserviceNotProvisioned"

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

An entity receiving the XML body ignores any unknown XML element and any unknown XML attribute.

C.1.4 XML schema

Implementations in compliance with the present document shall implement the XML schema defined below.

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

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

elementFormDefault="qualified"

attributeFormDefault="unqualified">

<xs:annotation>

<xs:documentation>

Info for MSISDN less short messsage service

</xs:documentation>

</xs:annotation>

<xs:element name="short-message-info" type="Tshort-message-info"/>

<xs:complexType name="Tshort-message-info">

<xs:sequence>

<xs:element name="To" type="xs:anyURI" minOccurs="0" maxOccurs="1"/>

<xs:element name="From" type="xs:anyURI" minOccurs="0" maxOccurs="1"/>

<xs:element name="Correlation-ID" type="Tcorrelation-id" minOccurs="0" maxOccurs="1"/>

<xs:element name="Delivery-Outcome" type="xs:string" minOccurs="0" maxOccurs="1"/>

<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:complexType name="Tcorrelation-id">

<xs:sequence>

<xs:element name="Sender" type="xs:anyURI" minOccurs="1" maxOccurs="1"/>

<xs:element name="Receiver" type="xs:anyURI" minOccurs="1" maxOccurs="1"/>

<xs:element name="HLR-ID" type="xs:string" minOccurs="1" maxOccurs="1"/>

<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:complexType name="anyExtType">

<xs:sequence>

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

</xs:sequence>

</xs:complexType>

</xs:schema>

C.1.5 IANA registration

NOTE: RFC 4288 [26], clause 9, states the process that applies in case of changes to the registry of media types. Any changes to the format or to clause 5.1.3.5 after the registration with IANA would invoke this procedure.

C.1.5.1 Name

C.1.5.2 Email

C.1.5.3 MIME media type name

Application

C.1.5.4 MIME subtype name

Vendor Tree – vnd.3gpp.sms+xml

C.1.5.5 Required parameters

None

C.1.5.6 Optional parameters

None

C.1.5.7 Encoding considerations

Binary.

C.1.5.8 Security considerations

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

The information transported in this MIME 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 TS24.229 [10].

C.1.5.9 Interoperability considerations

The MIME type allows interoperability of short message information between mobile networks and other systems.

C.1.5.10 Published specification

3GPP TS 24.341

(http://www.3gpp.org/ftp/Specs/html-info/24341.htm)

C.1.5.11 Applications which use this media

n/a

C.1.5.12 Applications that manipulate MIME typed objects (messaging, download etc.)

n/a

C.1.5.13 Additional information

1. Magic number(s): n/a

2. File extension(s): n/a

3. Macintosh file type code: n/a

4. Object Identifiers: n/a

C.1.5.14 Intended usage

Common.

Short Message Service is supported in mobile networks. The registration of the associated MIME type allows MSISDN less operation of the Short Message Service.

C.1.5.8.15 Other information/general comment

n/a

C.1.5.8.16 Person to contact for further information

1. Name: TBD

2. Email: TBD

3. Author/Change controller: TBD

Annex D (normative):
Feature-capability indicators defined within the current document