10.4 MCData service configuration document

24.4843GPPMission Critical Services (MCS) configuration managementProtocol specificationRelease 18TS

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

10.4.1 General

The MCData service configuration document is specified in this clause. The MCData service configuration document content is based on requirements of Annex A.5 of 3GPP TS 23.282 [24], and structure and procedures of OMA OMA-TS-XDM_Core-V2_1-20120403-A [2]. The usage of an MCData service configuration in the MCData service is described in 3GPP TS 24.282[25] and 3GPP TS 24.582 [26]. The schema definition is provided in clause 10.4.2.3. Each mission critical organization is configured with an MCData service configuration document.

10.4.2 Coding

10.4.2.1 Structure

The MCData service configuration document structure is specified in this clause.

The <service configuration> document:

1) shall include a "domain" attribute;

2) may include a <common> element;

3) may include an <on-network> element;

4) may include an <off-network> element; and

5) may include any other attribute for the purposes of extensibility.

The <common> element:

1) may include a <tx-and-rx-control> element containing:

a) a <time-temp-data-waiting> element.

The <on-network> element:

1) may include a <tx-and-rx-control> element containing:

a) a <max-data-size-sds-bytes> element;

b) a <max-payload-size-sds-cplane-bytes> element;

c) a <max-data-size-fd-bytes> element;

d) a <max-data-size-auto-recv-bytes> element;

e) a <default-file-availability> element; and

f) a <max-file-availability> element.

2) may contain a <signalling-protection> element containing:

a) a <confidentiality-protection> element; and

b) an <integrity-protection> element;

3) may contain a <protection-between-mcdata-servers> element containing:

a) an <allow-signalling-protection> element;

Editor’s Note: Mechanisms for signaling protection and media protection are yet to be agreed by SA3. It is expected that configuration for security protection will need to be added. P2P signalling protection would cover signalling content in XML (e.g. group-id) and MCData signalling content. Media protection is E2E between clients.

4) may contain an <anyExt> element containing:

a) one <emergency-resource-priority> element containing:

i) one <resource-priority-namespace> string element containing a namespace defined in IETF RFC 8101 [20]; and

ii) one <resource-priority-priority> string element element containing a priority level in the range specified in IETF RFC 8101 [20];

b) one <imminent-peril-resource-priority> element containing:

i) one <resource-priority-namespace> string element containing a namespace defined in IETF RFC 8101 [20]; and

ii) one <resource-priority-priority> string element element containing a priority level in the range specified in IETF RFC 8101 [20];

c) one <normal-resource-priority> element containing:

i) one <resource-priority-namespace> string element containing a namespace defined in IETF RFC 8101 [20]; and

ii) one <resource-priority-priority> string element element containing a priority level in the range specified in IETF RFC 8101 [20];

d) a <max-simultaneous-authorizations> element;

e) a <functional-alias-list> element containing one or more <functional-alias-entry> elements each containing:

i) a <functional-alias> element;

ii) a <max-simultaneous-activations> element;

iii) an <allow-takeover> element;

iv) an <mcdata-user-list> element; and

v) a <functional-alias-priority> element; and

f) a <notificationserver-hostname-list> element containing:

i) one or more <ns-entry> element.

The <off-network> element:

1) may contain a <default-prose-per-packet-priority> element containing:

a) an <mcdata-one-to-one-call-signalling> element; and

b) an <mcdata-one-to-one-call-media> element.

10.4.2.2 Application Unique ID

The AUID shall be set to "org.3gpp.mcdata.service-config".

10.4.2.3 XML Schema

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

<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified"

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

targetNamespace="urn:3gpp:ns:mcdataServiceConfig:1.0"

xmlns:mcdatasc="urn:3gpp:ns:mcdataServiceConfig:1.0">

<xs:import namespace="http://www.w3.org/XML/1998/namespace"

schemaLocation="http://www.w3.org/2001/xml.xsd"/>

<!– the root element –>

<xs:element name="service-configuration-info" type="mcdatasc:service-configuration-info-Type"/>

<!– the root type –>

<!– this is refined with one or more sub-types –>

<xs:complexType name="service-configuration-info-Type">

<xs:sequence>

<xs:element name="service-configuration-params" type="mcdatasc:service-configuration-params-Type" minOccurs="0"/>

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

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

</xs:sequence>

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

</xs:complexType>

<!– definition of the service-configuration-params-Type subtype–>

<xs:complexType name="service-configuration-params-Type">

<xs:sequence>

<xs:element name="common" type="mcdatasc:commonType" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="on-network" type="mcdatasc:on-networkType" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="off-network" type="mcdatasc:off-networkType" minOccurs="0" maxOccurs="unbounded"/>

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

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

</xs:sequence>

<xs:attribute name="domain" type="xs:anyURI" use="required"/>

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

</xs:complexType>

<xs:complexType name="commonType">

<xs:sequence>

<xs:element name="tx-and-rx-control" type="mcdatasc:common-tx-and-rx-controlType" minOccurs="0"/>

<xs:element name="anyExt" type="mcdatasc: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="on-networkType">

<xs:sequence>

<xs:element name="tx-and-rx-control" type="mcdatasc:on-network-tx-and-rx-controlType" minOccurs="0"/>

<xs:element name="signalling-protection" type="mcdatasc:signalling-protectionType" minOccurs="0"/>

<xs:element name="protection-between-mcdata-servers" type="mcdatasc:server-protectionType" minOccurs="0"/>

<xs:element name="file-availability" type="mcdatasc:on-network-file-availabilityType"/>

<xs:element name="anyExt" type="mcdatasc: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="emergency-resource-priority" type="mcdatasc:resource-priorityType"/>

<xs:element name="imminent-peril-resource-priority" type="mcdatasc:resource-priorityType"/>

<xs:element name="normal-resource-priority" type="mcdatasc:resource-priorityType"/>

<xs:complexType name="off-networkType">

<xs:sequence>

<xs:element name="default-prose-per-packet-priority" type="mcdatasc:default-prose-per-packet-priorityType" minOccurs="0"/>

<xs:element name="anyExt" type="mcdatasc: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="default-prose-per-packet-priorityType">

<xs:sequence>

<xs:element name="mcdata-one-to-one-call-signalling" type="xs:unsignedShort" minOccurs="0"/>

<xs:element name="mcdata-one-to-one-call-media" type="xs:unsignedShort" minOccurs="0"/>

<xs:element name="anyExt" type="mcdatasc: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="common-tx-and-rx-controlType">

<xs:sequence>

<xs:element name="time-temp-data-waiting" type="xs:duration" minOccurs="0"/>

<xs:element name="time-periodic-announcement" type="xs:duration" minOccurs="0"/>

<xs:element name="anyExt" type="mcdatasc: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="signalling-protectionType">

<xs:sequence>

<xs:element name="confidentiality-protection" type="xs:boolean" minOccurs="0" default="true"/>

<xs:element name="integrity-protection" type="xs:boolean" minOccurs="0" default="true"/>

<xs:element name="anyExt" type="mcdatasc: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="server-protectionType">

<xs:sequence>

<xs:element name="allow-signalling-protection" type="xs:boolean" minOccurs="0" default="true"/>

<xs:element name="anyExt" type="mcdatasc: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="on-network-tx-and-rx-controlType">

<xs:sequence>

<xs:element name="max-data-size-sds-bytes" type="xs:unsignedInt" minOccurs="0"/>

<xs:element name="max-payload-size-sds-cplane-bytes" type="xs:unsignedInt" minOccurs="0"/>

<xs:element name="max-data-size-fd-bytes" type="xs:unsignedInt" minOccurs="0"/>

<xs:element name="max-data-size-auto-recv-bytes" type="xs:unsignedInt" minOccurs="0"/>

<xs:element name="anyExt" type="mcdatasc: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="on-network-file-availabilityType">

<xs:sequence>

<xs:element name="default-file-availability" type="xs:unsignedInt"/>

<xs:element name="max-file-availability" type="xs:unsignedInt" minOccurs="0"/>

<xs:element name="anyExt" type="mcdatasc: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="resource-priorityType">

<xs:sequence>

<xs:element name="resource-priority-namespace" type="xs:string"/>

<xs:element name="resource-priority-priority" type="xs:string"/>

<xs:element name="anyExt" type="mcdatasc: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="functional-alias-list" type="mcdatasc:functional-alias-listType"/>

<!– definition of the functional-alias-listType subtype–>

<xs:complexType name="functional-alias-listType">

<xs:sequence>

<xs:element name="functional-alias-entry" type="mcdatasc:functional-alias-entryType" minOccurs="0" maxOccurs="unbounded"/>

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

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

</xs:sequence>

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

</xs:complexType>

<!– definition of the functional-aliasType subtype–>

<xs:complexType name="functional-alias-entryType">

<xs:sequence>

<xs:element name="functional-alias" type="xs:anyURI"/>

<xs:element name="max-simultaneous-activations" type="xs:positiveInteger"/>

<xs:element name="allow-takeover" type="xs:boolean"/>

<xs:element name="mcdata-user-list" type="mcdatasc:ListEntryType"/>

<xs:element name="functional-alias-priority" type="xs:positiveInteger"/>

<xs:element name="anyExt" type="mcdatasc: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="max-simultaneous-authorizations" type="xs:positiveInteger"/>

<xs:element name="notificationserver-hostname-list" type="mcdatasc:notificationserver-hostname-listType"/>

<!– definition of the notificationserver-hostname-listType subtype–>

<xs:complexType name="notificationserver-hostname-listType">

<xs:choice minOccurs="0" maxOccurs="unbounded">

<xs:element name="ns-entry" type="xs:anyURI" minOccurs="0" maxOccurs="unbounded"/>

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

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

</xs:choice>

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

</xs:complexType>

<xs:complexType name="ListEntryType">

<xs:choice minOccurs="0" maxOccurs="unbounded">

<xs:element name="entry" type="mcdatasc:EntryType"/>

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

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

</xs:choice>

<xs:attribute ref="xml:lang"/>

<xs:attributeGroup ref="mcdatasc:IndexType"/>

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

</xs:complexType>

<xs:complexType name="EntryType">

<xs:sequence>

<xs:element name="uri-entry" type="xs:anyURI"/>

<xs:element name="display-name" type="mcdatasc:DisplayNameElementType" minOccurs="0"/>

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

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

</xs:sequence>

<xs:attributeGroup ref="mcdatasc:IndexType"/>

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

</xs:complexType>

<xs:attributeGroup name="IndexType">

<xs:attribute name="index" type="xs:token"/>

</xs:attributeGroup>

<xs:complexType name="DisplayNameElementType">

<xs:simpleContent>

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

<xs:attribute ref="xml:lang"/>

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

</xs:extension>

</xs:simpleContent>

</xs:complexType>

<xs:complexType name="anyExtType">

<xs:sequence>

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

</xs:sequence>

</xs:complexType>

</xs:schema>

10.4.2.4 Default Document Namespace

The default document namespace used in evaluating URIs shall be "urn:3gpp:ns:mcdataServiceConfig:1.0".

10.4.2.5 MIME type

The MIME type for the service configuration document shall be "vnd.3gpp.mcdata-service-config+xml".

10.4.2.6 Validation Constraints

If the AUID value of the document URI or node URI in the Request-URI is other than that specified in clause 10.4.2.2, then the configuration management server shall return an HTTP 409 (Conflict) response including the XCAP error element <constraint-failure>. If included, the "phrase" attribute should be set to "invalid application id used".

If the XUI value of the document URI or node URI in the Request-URI does not match the XUI of the service configuration document URI, the configuration management server shall return an HTTP 409 (Conflict) response including the XCAP error element <constraint-failure>. If included, the "phrase" attribute should be set to "invalid XUI".

The service configuration document shall conform to the XML Schema described in clause 10.4.2.3.

The <service-configuration-info> element is the root element of the XML document. The <service-configuration-info> element can contain sub-elements.

NOTE 1: The sub-elements of the <service-configuration-info> are validated by the <xs:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> particle of the <mcdata-info> element.

The <service-configuration-params> element is a subelement of the <service-configuration-info> element.

If the <service-configuration-info> element does not contain a <service-configuration-params> element, then the configuration management server shall return an HTTP 409 (Conflict) response including the XCAP error element <constraint-failure>. If included, the "phrase" attribute should be set to "mandatory element is missing".

If the <service-configuration-params> element does not include a <common> element, an <on-network> element or an <off-network> element, then the configuration management server shall return an HTTP 409 (Conflict) response including the XCAP error element <constraint-failure>. If included, the "phrase" attribute should be set to "mandatory element is missing".

The <service-configuration-params> element shall contain either:

1) one <common> element only;

2) one <common> element and one <on-network> element;

3) one <common> element and one <off-network> element;

4) one <on-network> element only;

5) one <off-network> element only;

6) one <on-network> element and one <off-network> element; or

7) one <common> element, one <on-network> element and one <off-network> element.

If the <service-configuration-params> element does not confirm to one of the seven choices above, then the configuration management server shall return an HTTP 409 (Conflict) response including the XCAP error element <constraint-failure>. If included, the "phrase" attribute should be set to "semantic error".

If the "domain" attribute does not contain a syntactically correct domain name, then the configuration management server shall return an HTTP 409 (Conflict) response including the XCAP error element <constraint-failure>. If included, the "phrase" attribute should be set to "syntactically incorrect domain name".

If the "domain" attribute contains an unknown domain name, then the configuration management server shall return an HTTP 409 (Conflict) response including the XCAP error element <constraint-failure>. If included, the "phrase" attribute should be set to "unknown domain name".

The following elements conform to the "xs: duration" XML type:

1) <time-temp-data-waiting>; and

2) <time-periodic-announcement>.

The elements of "xs: duration" type specified above shall be represented in seconds using the element value: "PT<h>H<m>M<n>S" where <n> represents a valid value in seconds using decimal notation.

If any of the elements of "xs: duration" type specified above contain values that do not conform to the "PT <n>S" structure then the configuration management server shall return an HTTP 409 (Conflict) response including the XCAP error element <constraint-failure>. If included, the "phrase" attribute should be set to "invalid format for duration".

If an invalid value is received for <n>, then the configuration management server shall return an HTTP 409 (Conflict) response including the XCAP error element <constraint-failure>. If included, the "phrase" attribute should be set to "invalid value for duration".

If the <max-data-size-sds-bytes> element is not included, then there is no size limit imposed on the size of the SDS message.

If the <max-payload-size-sds-cplane-bytes> element is not included, then there is no size limit imposed for the use of C-plane procedures for the SDS message.

If the <max-data-size-fd-bytes> element is not included, then there is no size limit imposed on the size of the FD message.

If the <max-data-size-auto-recv-bytes> element is not included, then there is no size limit imposed on auto receive.

If the <default-file-availability> is not present, then the configuration management server shall return an HTTP 409 (Conflict) response including the XCAP error element <constraint-failure>. If included, the "phrase" attribute should be set to "default file availability not provided".

If the <max-file-availability> element is not included, then there is no limit imposed on file availability time.

If any of the constituent elements of the <default-prose-per-packet-priority> element contain a value less than 1 and greater than 8, then the configuration management server shall return an HTTP 409 (Conflict) response including the XCAP error element <constraint-failure>. If included, the "phrase" attribute should be set to "element value out of range".

NOTE 2: The higher the <default-prose-per-packet-priority> value, the higher the priority given to the signalling or media.

The "resource-priority-namespace" element contained in the "emergency-resource-priority" element shall have an MCPTT namespace value as specified in IETF RFC 8101 [20].

The "resource-priority-priority" element contained in the "emergency-resource-priority" element shall have a value greater than or equal to the value of the "resource-priority-priority" element contained in the "imminent-peril-resource-priority" element and shall be a priority level specified in IETF RFC 8101 [20].

The "resource-priority-namespace" element contained in the "imminent-peril-resource-priority" element shall have an MCPTT namespace value as specified in IETF RFC 8101 [20].

The "resource-priority-priority" element contained in the "imminent-peril-resource-priority" element shall have a value greater than or equal to the value of the "resource-priority-priority" element contained in the "normal-resource-priority" element and shall be a priority level specified in IETF RFC 8101 [20].

The "resource-priority-namespace" element contained in the "normal-resource-priority" element shall have an MCPTT namespace value as specified in IETF RFC 8101 [20].

NOTE 3: The IETF RFC 8101 [20] defines the priority levels for the MCPTT namespaces, which are applicable to all MC services.

NOTE 4: The values used for the "emergency-resource-priority", "imminent-peril-resource-priority" and "normal-resource-priority" elements need to be carefully agreed to by the MCData operator and the network operator.

The values used for the "emergency-resource-priority", "imminent-peril-resource-priority" and "normal-resource-priority" elements need to be carefully agreed to by the MCData operator and network operator.

The default value for the <confidentiality-protection> element of the <signalling-protection> element is "true" indicating that confidentiality protection is enabled.

The default value for the <integrity-protection> element of the <signalling-protection> element is "true" indicating that integrity protection is enabled.

The default value for the <allow-signalling-protection> element of the <protection-between-mcdata-servers> element is "true" indicating that signaling protection between MCData servers is enabled.

The service configuration server ignores any unknown element and any unknown attribute.

If the configuration management server receives a duplicate element or attribute, it shall return an HTTP 409 (Conflict) response including the XCAP error element <constraint-failure>. If included, the "phrase" attribute should be set to "duplicate attribute or element received".

10.4.2.7 Data Semantics

The "domain" attribute of the <service-configuration-params> element contains the domain name of the mission critical organization.

The <common> element contains service configuration data common to both on and off network service.

The <on-network> element contains service configuration data for on-network service only.

The <off-network> element contains service configuration data for off-network service only.

In the <common> element:

1) the <time-temp-data-waiting> element of the <tx-and-rx-control> element contains the time limit for the temporarily stored data that is waiting to be delivered to a receiving user which corresponds to the "TimeTempDataWaiting" element as specified in clause 11.2.7 of 3GPP TS 24.483 [4]; and

2) the <time-periodic-announcement> element of the <tx-and-rx-control> element contains the timer for the periodic announcement which contains a list of available recently invited data group communications which corresponds to the "TimePeriodicAnnouncement" element as specified in clause 11.2.8 of 3GPP TS 24.483 [4].

In the <on-network> element:

1) the <max-data-size-sds-bytes> element of the <tx-and-rx-control> element contains the maximum data that the originating client can send in an SDS message;

2) the <max-payload-size-sds-cplane-bytes> element of the <tx-and-rx-control> element contains the maximum payload data that the originating client can send in an SDS message over C-plane;

3) the <max-data-size-fd-bytes> element of the <tx-and-rx-control> element contains the maximum data that the originating client can send in an FD message;

4) the <max-data-size-auto-recv-bytes> element of the <tx-and-rx-control> element contains the maximum data that the server can send to the terminating client without requesting the user to indicate a present need for the data;

5) the <default-file-availability> element of the <file-availability> element contains the default time for which a file is available on the server for download, if a explicit time period is not requested by the originating client;

6) the <max-file-availability> element of the <file-availability> element contains the maximum time for which a file can be made available on the server for download.

7) the <confidentiality-protection> element of the <signalling-protection> element contains a boolean indicating whether confidentiality protection of MCData signalling is enabled or disabled between the MCData client and MCData server;

8) the <integrity-protection> element of the <signalling-protection> element contains a boolean indicating whether integrity protection of MCData signalling is enabled or disabled between the MCData client and MCData server;

9) The <emergency-resource-priority> element of the <anyExt> element is of type "resource-priorityType" and indicates how a Resource-Priority header field is to be populated for MCData emergency communications;

10) The <imminent-peril-resource-priority> element of the <anyExt> element is of type "resource-priorityType" and indicates how a Resource-Priority header field is to be populated for MCData Imminent Peril communications;

11) The <normal-resource-priority> element of the <anyExt> element is of type "resource-priorityType" and indicates how a Resource-Priority header field is to be populated when downgrading to normal priority from an MCData emergency communication or MCData imminent peril communication;

12) the <allow-signalling-protection> element of the <protection-between-mcdata-servers> element contains a boolean indicating whether protection of MCData signalling is enabled between MCData servers;

13) the <max-simultaneous-authorizations> element of the <anyExt> element is of type "positiveInteger" and indicates the maximum allowed number of simultaneous service authorizations for an MCData user.

NOTE 1: The default values of the <confidentiality-protection> element, the <integrity-protection> element, the <allow-signalling-protection> element and the <allow-floor-control-protection> element are "true";

14) the <functional-alias> element of the <functional-alias-entry> element of the <functional-alias-list> element is of type "anyURI" and contains the identity of a functional alias;

15) the <max-simultaneous-activations> element of the <functional-alias-entry> element of the <functional-alias> element of the <functional-alias-list> element is of type "positiveInteger" and contains the allowed number of concurrent activations that are allowed for the functional alias contained in the corresponding <functional-alias> element;

16) the <allow-takeover> element of the <functional-alias-entry> element of the <functional-alias-list> element is of type "boolean" and indicates whether take over by another MCData user is allowed for a currently activated functional alias contained in the corresponding <functional-alias> element;

17) the <entry> element of the <mcdata-user-list> element of the <functional-alias-entry> element of the <functional-alias-list> element is of type "entryType" and contains the MCData ID of an MCData user that is allowed to activate the functional alias contained in the corresponding <functional-alias> element;

18) the <functional-alias-priority> element of the <functional-alias-entry> element of the <functional-alias-list> element is of type "positiveInteger" and indicates the relative priority level of the functional alias contained in the corresponding <functional-alias> element; and

NOTE 2: The usage of this parameter by the MCData server is up to implementation.

19) the <ns-entry> element of the <notificationservers> element contains the hostname of the notification server, and corresponds to the leaf node of the "NotificationServer" element of clause 11.2.16 in 3GPP TS 24.483 [4].

In the <off-network> element:

1) the <default-prose-per-packet-priority> element contains priority values for off-network calls, for each of the following constituent elements:

a) <mcdata-one-to-one-call-signalling> element, which corresponds to the "MCDataOneToOneSignalling" element as specified in clause 11.2.11 of 3GPP TS 24.483 [4]; and

b) <mcdata-one-to-one-call-media> element, which corresponds to the "MCDataOneToOneMedia" element as specified in clause 11.2.12 of 3GPP TS 24.483 [4].

10.4.2.8 Naming Conventions

The MCData service configuration document name shall be called mcdata-service-config.xml.

10.4.2.9 Global documents

The MCData service configuration document is a global document. This document resides under the global tree for the CMSXCAPROOT. Since there is only one document for each mission critical organization, the CMSXCAPROOT may be used to distinguish different MCData service configuration documents. Otherwise, a subdirectory under the global tree, named by the mission critical organization name can be used to distinguish different service configuration documents. For example, if the CMSXCAPROOTURI respresents a single one mission critical organization, then the document URI would be:

mc-org-domain/mcorg12345/org.3gpp.mcdata.service-config/global/mcdata-service-config.xml

otherwise, if it services multiple organizations then the document URI would be:

CMSXCAPROOTURI/org.3gpp.mcdata.service-config/global/mc-org-name/mcdata-service-config.xml

Since the MCData service configuration is a global document, all users will have read-only access. Read-write access is only allowed for the system administrators of the mission critical organization.

10.4.2.10 Resource interdependencies

There are no resource interdependencies.

10.4.2.11 Authorization Policies

The authorization policies for manipulating a service configuration document shall conform to those described in OMA OMA-TS-XDM_Core-V2_1-20120403-A [2] clause 5.1.5 "Authorization".

10.4.2.12 Subscription to Changes

The service configuration document application usage shall support subscription to changes as specified in clause 6.3.13.3.

Annex A (informative):
Signalling flows