7 MMTEL service data definition based on XML

29.3643GPPIP Multimedia Subsystem (IMS) Application Server (AS) service data descriptions for AS interoperabilityRelease 17TS

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

7.1 General principles

The general structure of the MMTEL service data document is shown in Figure 7.1-1

Figure 7.1-1: General structure of MMTEL service document

The MMTEL document consists of the services. Each service consists of a user defined part and an operator defined part. The user defined data is found in each of the MMTEL supplementary service specifications. The operator defined part consists of authorization of the service, and of the subscription options for each of the services.

7.2 MMTEL services specification

7.2.0 Service Indications

A dedicated Service Indication shall be used within the XML option for MMTel services. The value of the Service Indication shall be "MMTEL-Services".

Proprietary extensions shall use not standardized Service Indications. There is no constraint for the data structure of the proprietary Service Data.

7.2.1 MMTEL services schema

The following shows the MMTEL Services schema:

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

<xs:schema xmlns:ss="http://uri.etsi.org/ngn/params/xml/simservs/xcap" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:cp="urn:ietf:params:xml:ns:common-policy" xmlns:ocp="urn:oma:xml:xdm:common-policy" targetNamespace="http://uri.etsi.org/ngn/params/xml/simservs/xcap" elementFormDefault="qualified" attributeFormDefault="unqualified">

<xs:include schemaLocation="XCAP.xsd"/>

<xs:include schemaLocation="operator-common-data.xsd"/>

<xs:include schemaLocation="originating-identity-presentation.xsd"/>

<xs:include schemaLocation="terminating-identity-presentation.xsd"/>

<xs:include schemaLocation="communication-diversion.xsd"/>

<xs:include schemaLocation="communication-waiting.xsd"/>

<xs:include schemaLocation="communication-barring.xsd"/>

<xs:include schemaLocation="operator-originating-identity-presentation.xsd"/>

<xs:include schemaLocation="operator-terminating-identity-presentation.xsd"/>

<xs:include schemaLocation="operator-malicious-communication-identification.xsd"/>

<xs:include schemaLocation="operator-communication-diversion.xsd"/>

<xs:include schemaLocation="operator-communication-waiting.xsd"/>

<xs:include schemaLocation="operator-communication-hold.xsd"/>

<xs:include schemaLocation="operator-communication-barring.xsd"/>

<xs:include schemaLocation="operator-completion-of-communication.xsd"/>

<xs:include schemaLocation="operator-message-waiting-indication.xsd"/>

<xs:include schemaLocation="operator-conference.xsd"/>

<xs:include schemaLocation="operator-advice-of-charge.xsd"/>

<xs:include schemaLocation="operator-explicit-communication-transfer.xsd"/>

<xs:include schemaLocation="operator-customized-alerting-tone.xsd"/>

<xs:include schemaLocation="operator-flexible-alerting.xsd"/>

<xs:include schemaLocation="flexible-alerting.xsd"/>

<xs:element name="MMTelServices" type="ss:tMMTelServicesType"/>

<xs:complexType name="tMMTelServicesType">

<xs:sequence>

<xs:element name="complete-originating-identity-presentation" type="ss:complete-originating-identity-presentation-type" minOccurs="0"/>

<xs:element name="complete-originating-identity-restriction" type="ss:complete-originating-identity-restriction-type" minOccurs="0"/>

<xs:element name="complete-terminating-identity-presentation" type="ss:complete-terminating-identity-presentation-type" minOccurs="0"/>

<xs:element name="complete-terminating-identity-restriction" type="ss:complete-terminating-identity-restriction-type" minOccurs="0"/>

<xs:element name="complete-malicious-communication-identification" type="ss:complete-malicious-communication-identification-type" minOccurs="0"/>

<xs:element name="complete-communication-diversion" type="ss:complete-communication-diversion-type" minOccurs="0"/>

<xs:element name="complete-communication-waiting" type="ss:complete-communication-waiting-type" minOccurs="0"/>

<xs:element name="complete-communication-hold" type="ss:complete-communication-hold-type" minOccurs="0"/>

<xs:element name="complete-communication-barring" type="ss:complete-communication-barring-type" minOccurs="0"/>

<xs:element name="complete-completion-of-communication-busy-subscriber" type="ss:complete-completion-of-communication-busy-subscriber-type" minOccurs="0"/>

<xs:element name="complete-completion-of-communication-no-reply" type="ss:complete-completion-of-communication-no-reply-type" minOccurs="0"/>

<xs:element name="complete-message-waiting-indication" type="ss:complete-message-waiting-indication-type" minOccurs="0"/>

<xs:element name="complete-conference" type="ss:complete-conference-type" minOccurs="0"/>

<xs:element name="complete-advice-of-charge" type="ss:complete-advice-of-charge-type" minOccurs="0"/>

<xs:element name="complete-explicit-communication-transfer" type="ss:complete-explicit-communication-transfer-type" minOccurs="0"/>

<xs:element name="complete-customized-alerting-tone" type="ss:complete-customized-alerting-tone-type" minOccurs="0"/>

<xs:element name="complete-flexible-alerting" type="ss:complete-flexible-alerting-type" minOccurs="0"/>

</xs:sequence>

</xs:complexType>

<xs:complexType name="complete-originating-identity-presentation-type">

<xs:sequence>

<xs:element ref="ss:originating-identity-presentation"/>

<xs:element ref="ss:operator-originating-identity-presentation"/>

</xs:sequence>

</xs:complexType>

<xs:complexType name="complete-originating-identity-restriction-type">

<xs:sequence>

<xs:element ref="ss:originating-identity-presentation-restriction"/>

<xs:element ref="ss:operator-originating-identity-presentation-restriction"/>

</xs:sequence>

</xs:complexType>

<xs:complexType name="complete-terminating-identity-presentation-type">

<xs:sequence>

<xs:element ref="ss:terminating-identity-presentation"/>

<xs:element ref="ss:operator-terminating-identity-presentation"/>

</xs:sequence>

</xs:complexType>

<xs:complexType name="complete-terminating-identity-restriction-type">

<xs:sequence>

<xs:element ref="ss:terminating-identity-presentation-restriction"/>

<xs:element ref="ss:operator-terminating-identity-presentation-restriction"/>

</xs:sequence>

</xs:complexType>

<xs:complexType name="complete-malicious-communication-identification-type">

<xs:sequence>

<xs:element ref="ss:operator-malicious-communication-identification"/>

</xs:sequence>

</xs:complexType>

<xs:complexType name="complete-communication-diversion-type">

<xs:sequence>

<xs:element ref="ss:communication-diversion"/>

<xs:element ref="ss:operator-communication-diversion"/>

</xs:sequence>

</xs:complexType>

<xs:complexType name="complete-communication-waiting-type">

<xs:sequence>

<xs:element ref="ss:communication-waiting"/>

<xs:element ref="ss:operator-communication-waiting"/>

</xs:sequence>

</xs:complexType>

<xs:complexType name="complete-communication-hold-type">

<xs:sequence>

<xs:element ref="ss:operator-communication-hold"/>

</xs:sequence>

</xs:complexType>

<xs:complexType name="complete-communication-barring-type">

<xs:sequence>

<xs:element ref="ss:incoming-communication-barring"/>

<xs:element ref="ss:outgoing-communication-barring"/>

<xs:element ref="ss:operator-incoming-communication-barring"/>

<xs:element ref="ss:operator-outgoing-communication-barring"/>

</xs:sequence>

</xs:complexType>

<xs:complexType name="complete-completion-of-communication-busy-subscriber-type">

<xs:sequence>

<xs:element ref="ss:operator-completion-of-communication-busy-subscriber"/>

</xs:sequence>

</xs:complexType>

<xs:complexType name="complete-completion-of-communication-no-reply-type">

<xs:sequence>

<xs:element ref="ss:operator-completion-of-communication-no-reply"/>

</xs:sequence>

</xs:complexType>

<xs:complexType name="complete-message-waiting-indication-type">

<xs:sequence>

<xs:element ref="ss:operator-message-waiting-indication"/>

</xs:sequence>

</xs:complexType>

<xs:complexType name="complete-conference-type">

<xs:sequence>

<xs:element ref="ss:operator-conference"/>

</xs:sequence>

</xs:complexType>

<xs:complexType name="complete-advice-of-charge-type">

<xs:sequence>

<xs:element ref="ss:operator-advice-of-charge"/>

</xs:sequence>

</xs:complexType>

<xs:complexType name="complete-explicit-communication-transfer-type">

<xs:sequence>

<xs:element ref="ss:operator-explicit-communication-transfer"/>

</xs:sequence>

</xs:complexType>

<xs:complexType name="complete-customized-alerting-tone-type">

<xs:sequence>

<xs:element ref="ss:operator-customized-alerting-tone"/>

</xs:sequence>

</xs:complexType>

<xs:complexType name="complete-flexible-alerting-type">

<xs:sequence>

<xs:element ref="ss:flexible-alerting-default"/>

<xs:element ref="ss:flexible-alerting-specific"/>

<xs:choice>

<xs:element ref="ss:operator-flexible-alerting"/>

<xs:element ref="ss:operator-flexible-alerting-group"/>

</xs:choice>

</xs:sequence>

</xs:complexType>

</xs:schema>

The file "operator-common-data.xsd" contains all the common types of the operator data. This schema is defined as

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

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:ss="http://uri.etsi.org/ngn/params/xml/simservs/xcap" targetNamespace="http://uri.etsi.org/ngn/params/xml/simservs/xcap" elementFormDefault="qualified" attributeFormDefault="unqualified">

<!– This schema file contains common types for the operator data–>

<xs:element name="absOperatorService" type="ss:operatorServiceConfigType" abstract="true"/>

<xs:complexType name="operatorServiceConfigType">

<xs:attribute name="authorized" type="xs:boolean" use="required"/>

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

</xs:complexType>

<xs:simpleType name="identityPresentationModeType">

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

<xs:enumeration value="permanent"/>

<xs:enumeration value="temporary"/>

</xs:restriction>

</xs:simpleType>

<xs:simpleType name="identityPresentationRestrictionType">

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

<xs:enumeration value="only-identity"/>

<xs:enumeration value="all-private-information"/>

</xs:restriction>

</xs:simpleType>

<xs:simpleType name="identityPresentationRestrictionOverrideType">

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

<xs:enumeration value="override-active"/>

<xs:enumeration value="override-not-active"/>

</xs:restriction>

</xs:simpleType>

</xs:schema>

7.2.2 OIP service

The OIP service is specified together with OIR service in subclause 7.2.3.

7.2.3 OIR service

7.2.3.1 User defined data

The schema defined in subclause 4.10.2 of 3GPP TS 24.607 [5] shall be used.

7.2.3.2 Operator defined data

7.2.3.2.1 Data semantics

The OIP and OIR services are authorized by the operator by setting the "authorized" attributes of <operator-originating-identity-presentation> and <operator-originating-identity-presentation-restriction>, respectively, to "true".

7.2.3.2.2 XML Schema

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

<xs:annotation>

<xs:documentation xml:lang="en">

Operator part of the Originating Identity Presentation (OIP) and Originating Identity Restriction (OIR) services

</xs:documentation>

</xs:annotation>

<!–xs:include schemaLocation="operator-common-data.xsd"/–>

<xs:element name="operator-originating-identity-presentation" substitutionGroup="ss:absOperatorService" nillable="true">

<xs:complexType>

<xs:complexContent>

<xs:extension base="ss:operatorServiceConfigType">

<xs:sequence>

<xs:element name="restriction-override" type="ss:identityPresentationRestrictionOverrideType" default="override-not-active" minOccurs="0"/>

</xs:sequence>

</xs:extension>

</xs:complexContent>

</xs:complexType>

</xs:element>

<xs:element name="operator-originating-identity-presentation-restriction" substitutionGroup="ss:absOperatorService" nillable="true">

<xs:complexType>

<xs:complexContent>

<xs:extension base="ss:operatorServiceConfigType">

<xs:sequence>

<xs:element name="mode" type="ss:identityPresentationModeType"/>

<xs:element name="restriction" type="ss:identityPresentationRestrictionType"/>

</xs:sequence>

</xs:extension>

</xs:complexContent>

</xs:complexType>

</xs:element>

</xs:schema>

7.2.4 TIP service

The TIP service is specified together with TIR service, see subclause 7.2.5.

7.2.5 TIR service

7.2.5.1 User defined data

The schema defined in subclause 4.9.2 of 3GPP TS 24.608 [6] shall be used.

7.2.5.2 Operator defined data

7.2.5.2.1 Data semantics

The TIP and TIR services are authorized by the operator by setting the "authorized" attributes of <operator-terminating-identity-presentation> and <operator-terminating-identity-presentation-restriction>, respectively, to "true".

7.2.5.2.2 XML Schema

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

<xs:annotation>

<xs:documentation xml:lang="en">

Operator part of the Terminating Identity Presentation (TIP) and Terminating Identity Restriction (TIR) services

</xs:documentation>

</xs:annotation>

<!–xs:include schemaLocation="operator-common-data.xsd"/–>

<xs:element name="operator-terminating-identity-presentation" substitutionGroup="ss:absOperatorService" nillable="true">

<xs:complexType>

<xs:complexContent>

<xs:extension base="ss:operatorServiceConfigType">

<xs:sequence>

<xs:element name="restriction-override" type="ss:identityPresentationRestrictionOverrideType" default="override-not-active" minOccurs="0"/>

</xs:sequence>

</xs:extension>

</xs:complexContent>

</xs:complexType>

</xs:element>

<xs:element name="operator-terminating-identity-presentation-restriction" substitutionGroup="ss:absOperatorService" nillable="true">

<xs:complexType>

<xs:complexContent>

<xs:extension base="ss:operatorServiceConfigType">

<xs:sequence>

<xs:element name="mode" type="ss:identityPresentationModeType"/>

</xs:sequence>

</xs:extension>

</xs:complexContent>

</xs:complexType>

</xs:element>

</xs:schema>

7.2.6 MCID service

7.2.6.1 User defined data

No user data associated with MCID service is defined in 3GPP TS 24.616 [10].

7.2.6.2 Operator defined data

7.2.6.2.1 Data semantics

The MCID service is authorized and activated by the operator by setting the "authorized" attribute of <operator-malicious-communication-identification> to "true".

7.2.6.2.2 XML schema

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

<xs:annotation>

<xs:documentation xml:lang="en">

Operator part of the Malicious Communication Identification (MCID) service

</xs:documentation>

</xs:annotation>

<!–xs:include schemaLocation="operator-common-data.xsd"/–>

<xs:element name="operator-malicious-communication-identification" substitutionGroup="ss:absOperatorService" nillable="true">

<xs:complexType>

<xs:complexContent>

<xs:extension base="ss:operatorServiceConfigType">

<xs:sequence>

<xs:element name="mode">

<xs:simpleType>

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

<xs:enumeration value="permanent"/>

<xs:enumeration value="temporary"/>

</xs:restriction>

</xs:simpleType>

</xs:element>

</xs:sequence>

</xs:extension>

</xs:complexContent>

</xs:complexType>

</xs:element>

</xs:schema>

7.2.7 ACR service

ACR is a subset of the ICB service, specified in subclause 7.2.11.

7.2.8 CDIV service

7.2.8.1 User defined data

The schema defined in subclause 4.9.2 of 3GPP TS 24.604 [2] shall be used.

7.2.8.2 Operator defined data

7.2.8.2.1 Data semantics

The CDIV service is authorized by the operator by setting the "authorized" attribute of <operator-communication-diversion> to "true".

7.2.8.2.2 XML Schema

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

<xs:annotation>

<xs:documentation xml:lang="en">

Operator part of the Communication Diversion (CDIV) services

</xs:documentation>

</xs:annotation>

<!–xs:include schemaLocation="operator-common-data.xsd"/–>

<xs:element name="operator-communication-diversion" substitutionGroup="ss:absOperatorService" nillable="true">

<xs:complexType>

<xs:complexContent>

<xs:extension base="ss:operatorServiceConfigType">

<xs:sequence>

<xs:element name="communication-retention-on-invocation" default="clear-communication-on-invocation-of-diversion">

<xs:simpleType>

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

<xs:enumeration value="retain-until-alerting-at-diverted-to-user"/>

<xs:enumeration value="clear-communication-on-invocation-of-diversion"/>

</xs:restriction>

</xs:simpleType>

</xs:element>

<xs:element name="retention-when-diverting-rejected-at-diverted-to-user" default="no-action-at-diverting-user">

<xs:simpleType>

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

<xs:enumeration value="continue-to-alert-diverting-user"/>

<xs:enumeration value="no-action-at-diverting-user"/>

</xs:restriction>

</xs:simpleType>

</xs:element>

<xs:element name="total-number-of-diversions-for-each-communication" type="xs:integer"/>

<xs:element name="cdiv-indication-timer">

<xs:simpleType>

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

<xs:minInclusive value="0"/>

<xs:maxInclusive value="60"/>

</xs:restriction>

</xs:simpleType>

</xs:element>

<xs:element name="communication-forwarding-on-no-reply-timer">

<xs:simpleType>

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

<xs:minInclusive value="0"/>

<xs:maxInclusive value="180"/>

</xs:restriction>

</xs:simpleType>

</xs:element>

</xs:sequence>

</xs:extension>

</xs:complexContent>

</xs:complexType>

</xs:element>

</xs:schema>

7.2.9 CW service

7.2.9.1 User defined data

The XML schema as defined in 3GPP TS 24.615 [9] subclause 4.8.3 shall be used.

7.2.9.2 Operator defined data

7.2.9.2.1 Data semantics

The CW service is authorized by the operator by setting the "authorized" attribute of <operator-communication-waiting> to "true".

7.2.9.2.2 XML Schema

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

<xs:annotation>

<xs:documentation xml:lang="en">

Operator part of the Communication Waiting (CW) service

</xs:documentation>

</xs:annotation>

<!–xs:include schemaLocation="operator-common-data.xsd"/–>

<xs:element name="operator-communication-waiting" substitutionGroup="ss:absOperatorService" nillable="true">

<xs:complexType>

<xs:complexContent>

<xs:extension base="ss:operatorServiceConfigType">

<xs:sequence>

<xs:element name="calling-user-receives-notification-his-call-is-waiting" default="false" type="xs:boolean"/>

</xs:sequence>

</xs:extension>

</xs:complexContent>

</xs:complexType>

</xs:element>

</xs:schema>

7.2.10 HOLD service

7.2.10.1 User defined data

No user data is defined in 3GPP TS 24.610 [7]

7.2.10.2 Operator defined data

7.2.10.2.1 Data semantics

The HOLD service is authorized and activated by the operator by setting the "authorized" attribute of <operator-communication-hold> to "true".

7.2.10.2.2 XML Schema

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

<xs:annotation>

<xs:documentation xml:lang="en">

Operator part of the Hold service

</xs:documentation>

</xs:annotation>

<!–xs:include schemaLocation="operator-common-data.xsd"/–>

<xs:element name="operator-communication-hold" substitutionGroup="ss:absOperatorService" nillable="true">

</xs:element>

</xs:schema>

7.2.11 CB service

7.2.11.1 User defined data

The XML schema as defined in 3GPP TS 24.611 [8] subclause 4.9.2 shall be used.

7.2.11.2 Operator defined data

7.2.11.2.1 Data semantics

The ICB and OCB services are authorized by the operator by setting the "authorized" attribute of <operator-incoming-communication-barring> and <operator-outgoing-communication-barring> to "true".

7.2.11.2.2 XML Schema

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

<xs:annotation>

<xs:documentation xml:lang="en">

Operator part of the Communication Barring (CB) service

</xs:documentation>

</xs:annotation>

<!–xs:include schemaLocation="operator-common-data.xsd"/–>

<xs:element name="operator-incoming-communication-barring" substitutionGroup="ss:absOperatorService" nillable="true"/>

<xs:element name="operator-outgoing-communication-barring" substitutionGroup="ss:absOperatorService" nillable="true"/>

</xs:schema>

7.2.12 CCBS/CCNR service

7.2.12.1 User defined data

No user defined data specified in 3GPP TS 24.642 [12].

7.2.12.2 Operator defined data

7.2.12.2.1 Data semantics

The CCBS and CCNR service is authorized and activated by the operator by setting the "authorized" attribute of <operator-completion-of-communication-busy-subscriber> and <operator-completion-of-communication-no-reply>, respectively, to "true".

7.2.12.2.1 XML Schema

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

<xs:annotation>

<xs:documentation xml:lang="en">

Operator part of the Completion of Communication (CC) service

</xs:documentation>

</xs:annotation>

<!–xs:include schemaLocation="operator-common-data.xsd"/–>

<xs:element name="operator-completion-of-communication-busy-subscriber" substitutionGroup="ss:absOperatorService" nillable="true"/>

<xs:element name="operator-completion-of-communication-no-reply" substitutionGroup="ss:absOperatorService" nillable="true"/>

</xs:schema>

7.2.13 MWI service

7.2.13.1 User defined data

No user data is defined in 3GPP TS 24.606 [4].

7.2.13.2 Operator defined data

7.2.13.2.1 Data semantics

The MWI service is authorized and activated by the operator by setting the "authorized" attribute of <operator-message-waiting-indication> to "true".

7.2.13.2.2 XML Schema

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

<xs:annotation>

<xs:documentation xml:lang="en">

Operator part of the Message Waiting Indication (MWI) service

</xs:documentation>

</xs:annotation>

<!–xs:include schemaLocation="operator-common-data.xsd"/–>

<xs:element name="operator-message-waiting-indication" substitutionGroup="ss:absOperatorService" nillable="true">

</xs:element>

</xs:schema>

7.2.14 CONF service

7.2.14.1 User defined data

No user data is defined in 3GPP TS 24.605 [3]

7.2.14.2 Operator defined data

7.2.14.2.1 Data semantics

The Conference service is authorized and activated by the operator by setting the "authorized" attribute of <operator-conference> to "true".

7.2.14.2.2 XML Schema

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

<xs:annotation>

<xs:documentation xml:lang="en">

Operator part of the Conference (CONF) service

</xs:documentation>

</xs:annotation>

<!–xs:include schemaLocation="operator-common-data.xsd"/–>

<xs:element name="operator-conference" substitutionGroup="ss:absOperatorService" nillable="true"/>

</xs:schema>

7.2.15 AOC service

7.2.15.1 User defined data

No user data is defined in 3GPP TS 24.647 [13]

7.2.15.2 Operator defined data

7.2.15.2.1 Data semantics

AOC service is described in 3GPP TS 32.280 [22] and in 3GPP TS 24.647 [13]. It consists of 3 services types AOC-S, AOC-D, AOC-E paired with an AOC Service obligatory type.

Information elements

– Service Authorized (for each service type AOC-S, AOC-D, AOC-E)

– AOC service type as described in 3GPP TS 32.280 [22]

– AOC service obligatory type as described in 3GPP TS 32.280 [22]

– Preferred AOC currency as described in 3GPP TS 32.280 [22]

– AOC format as described in 3GPP TS 32.280 [22]

The AOC services are authorized and activated by the operator by setting the "authorized" attribute of <operator-advice-of-charge-s>, <operator-advice-of-charge-d>, <operator-advice-of-charge-e> to "true".

7.2.15.2.2 XML Schema

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

<xs:annotation>

<xs:documentation xml:lang="en">

Operator part of the Advice of Charge (AOC) service

</xs:documentation>

</xs:annotation>

<!–xs:include schemaLocation="operator-common-data.xsd"/–>

<xs:element name="operator-advice-of-charge" substitutionGroup="ss:absOperatorService" nillable="true">

<xs:complexType>

<xs:complexContent>

<xs:extension base="ss:operatorServiceConfigType">

<xs:sequence>

<xs:element name="service-type" type="ss:service-typeType"/>

<xs:element name="Currency" type="ss:CurrencyType"/>

</xs:sequence>

</xs:extension>

</xs:complexContent>

</xs:complexType>

</xs:element>

<xs:complexType name="service-typeType">

<xs:sequence>

<xs:element name="operator-aoc-d" type="ss:operator-aoc-type" nillable="true" minOccurs="0"/>

<xs:element name="operator-aoc-e" type="ss:operator-aoc-type" nillable="true" minOccurs="0"/>

<xs:element name="operator-aoc-s" type="ss:operator-aoc-type" nillable="true" minOccurs="0"/>

</xs:sequence>

</xs:complexType>

<xs:simpleType name="CurrencyType">

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

<xs:pattern value="[A-Z]{3}"/>

</xs:restriction>

</xs:simpleType>

<xs:complexType name="operator-aoc-type">

<xs:sequence>

<xs:element name="aoc-obligatory-type" type="ss:obligatory-typeType"/>

</xs:sequence>

<xs:attribute name="activated" type="xs:boolean" use="required"/>

</xs:complexType>

<xs:simpleType name="obligatory-typeType">

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

<xs:enumeration value="AoCI"/>

<xs:enumeration value="AoCC"/>

</xs:restriction>

</xs:simpleType>

</xs:schema>

7.2.16 ECT service

7.2.16.1 User defined data

No user data is defined in 3GPP TS 24.629 [11].

7.2.16.2 Operator defined data

7.2.16.2.1 Data semantics

The ECT service is authorized and activated by the operator by setting the "authorized" attribute of <operator-explicit-communication-transfer> to "true".

7.2.16.2.2 XML Schema

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

<xs:annotation>

<xs:documentation xml:lang="en">

Operator part of the Explicit Communication Transfer (ECT) service

</xs:documentation>

</xs:annotation>

<!–xs:include schemaLocation="operator-common-data.xsd"/–>

<xs:element name="operator-explicit-communication-transfer" substitutionGroup="ss:absOperatorService" nillable="true"/>

</xs:schema>

7.2.17 Reverse charging service

NOTE: The reverse charging service is not defined

7.2.18 CUG service

7.2.18.1 User defined data

CUG is not supported for the XML option.

7.2.18.2 Operator defined data

CUG is not supported for the XML option.

7.2.19 3PTY service

3PTY service is a subset of the CONF service specified in subclause 7.2.14.

7.2.20 FA service

7.2.20.1 User defined data

The XML schema as defined in 3GPP TS 24.239 [15] subclause 4.8.3 shall be used.

7.2.20.1 Operator defined data

7.2.20.1.1 Data semantics

The FA service is authorized and activated by the operator by setting the "authorized" attribute of <operator-flexible-alerting> to true.

7.2.20.1.2 XML schema

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

<xs:include schemaLocation="operator-common-data.xsd"/>

<xs:element name="operator-flexible-alerting" substitutionGroup="ss:absOperatorService" nillable="true">

<xs:annotation>

<xs:documentation xml:lang="en">

Operator part of the Flexible Alerting (FA) service

</xs:documentation>

</xs:annotation>

<xs:complexType>

<xs:complexContent>

<xs:extension base="ss:operatorServiceConfigType">

<xs:sequence>

<xs:element name="default-group" type="xs:anyURI"/>

</xs:sequence>

</xs:extension>

</xs:complexContent>

</xs:complexType>

</xs:element>

<xs:element name="operator-flexible-alerting-group" substitutionGroup="ss:absOperatorService" nillable="true">

<xs:annotation>

<xs:documentation xml:lang="en">

Operator schema per Flexible Alerting (FA) group

</xs:documentation>

</xs:annotation>

<xs:complexType>

<xs:complexContent>

<xs:extension base="ss:operatorServiceConfigType">

<xs:sequence>

<xs:element name="identity" type="xs:anyURI"/>

<!–Pilot identity of the FA group–>

<xs:element name="group-type">

<xs:simpleType>

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

<xs:enumeration value="single-user"/>

<xs:enumeration value="multiple-users"/>

</xs:restriction>

</xs:simpleType>

</xs:element>

<xs:element name="membership">

<xs:simpleType>

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

<xs:enumeration value="demand"/>

<xs:enumeration value="permanent"/>

</xs:restriction>

</xs:simpleType>

</xs:element>

<xs:element name="members">

<!–List of members of the FA group–>

<xs:complexType>

<xs:sequence>

<xs:element name="member" minOccurs="0" maxOccurs="unbounded">

<xs:complexType>

<xs:simpleContent>

<xs:extension base="xs:anyURI">

<xs:attribute name="active" type="xs:boolean"/>

</xs:extension>

</xs:simpleContent>

</xs:complexType>

</xs:element>

</xs:sequence>

</xs:complexType>

</xs:element>

</xs:sequence>

</xs:extension>

</xs:complexContent>

</xs:complexType>

</xs:element>

</xs:schema>

7.2.21 Void

7.2.22 CAT service

7.2.22.1 User defined data

No user data is defined in 3GPP TS 24.182 [21].

7.2.22.2 Operator defined data

7.2.22.2.1 Data semantics

The CAT service is authorized and activated by the operator by setting the "authorized" attribute of <operator-customized-alerting-tone> to "true".

7.2.22.2.2 XML Schema

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

<xs:annotation>

<xs:documentation xml:lang="en">

Operator part of the Customized Alerting Tone (CAT) service

</xs:documentation>

</xs:annotation>

<xs:element name="operator-customized-alerting-tone" substitutionGroup="ss:absOperatorService" nillable="true">

</xs:element>

</xs:schema>